| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
| |
Therefore, pruning starts for the SLACKWARE Live ISO. Too bad really.
Removed are some packages that are relatively big and arbitrarily
not used that much (quite a personal opinion of course).
|
|
|
|
|
| |
More and more, non-KDE software starts depending on packages that were
introduced for KDE Plasma5.
|
|
|
|
| |
Input text for login and password was no longer visible.
|
|
|
|
|
|
| |
Even when running -current, the KDE Info Center will show Slackware's
stable version number. Therefore, add a line of text informing about the
development status of Slackware -current when the ISO is based on it.
|
| |
|
|
|
|
| |
New picture taken on the beach near Groede, Zeeland, NL
|
| |
|
|
|
|
| |
Thanks again to Richard Hoyle for reporting.
|
|
|
|
| |
Thanks to Richard Hoyle for pointing this out.
|
| |
|
|
|
|
|
| |
Adding autoconf, automake, gettext, libtool and m4
Thanks to Gunther.
|
|
|
|
| |
From 'Fri Apr 21 06:02:04 UTC 2023' update in Slackware.
|
| |
|
| |
|
|
|
|
| |
The nano binary in XFCE ISO needs it.
|
| |
|
|
|
|
|
| |
Grub 2.0.6 stumbles over metadata_csum_seed which is enabled by default
since E2fsprogs 1.47.0, so let's disable that too
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
So we do a string comparison instead.
|
|
|
|
|
|
|
|
|
|
|
| |
Liveslak used to assign the label 'EFI' to the FAT filesystem on the
EFI System Partition (ESP). Some UEFI firmwares however cannot cope
with a volume- or labelname that is identical to the EFI directory name.
When that happens, the buggy firmware decides that an EFI directory
does not exist. The computer will not boot.
To make liveslak work on those buggy firmwares, it needs to use any name
*except* 'EFI'. Let's pick 'ESP' instead, which is still informative
about the 'EFI System Partition'.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Notably kpipewire, kio-zeroconf, ksanecore, skanpage, kColorPicker
and kImageAnnotator are new packages, some are required for scanning paper,
and without kpipewire the Plasma taskbar does not want to appear on-screen.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This was changed in commit dd0327d77f2741474245ecd3026cf66e55581733 when
adding full Ventoy support but I had not thought through all the consequences.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
New features:
Ventoy is now fully supported.
Liveslak implements the "Ventoy-compatible" guideline. There is nothing you
have to do, this works out of the box.
When you are booting from an ISO file (whether via Ventoy, or through your own
hand-crafted Grub menu entry, or Windows BCD), Operating System persistence
and an encrypted homedirectory are now supported, as well as the ability
to load additional live modules (as 'addons' or 'optional') that are not
part of the ISO.
All of this is possible without the need for any modification to the ISO image.
The configuration is stored in a file next to the ISO.
A new script, "isocomp.sh" aka the ISO Companion script, has been added.
Like with all of my scripts, it accepts a "--help" parameter which will
show you how to use it.
This script allows you to:
- create encrypted containers for OS persistence and a persistent homedirectory
(actually not just for /home but you can create as many containers as
fit on the disk and mount them wherever you want)
- size extension of existing encrypted containers if they threaten to run
out of space
- creating a secondary liveslak root on the disk partition where you can
add more (optional/add-on) live modules that you need in the Live OS
but are not contained in the ISO
The configuration of these new features is stored in a file with the same
name and full path as the ISO file but with a ".cfg" file extension instead
of ".iso". The "isocomp.sh" script manages this configuration file for you,
but you can safely edit and modify it manually if you want to. The "isocomp.sh"
script will leave your customizations alone.
Here is an example of such a configuration file; it is copied from
my own Ventoy disk, for a Slackware LEAN Live ISO image:
LIVESLAKROOT=/liveslak
LUKSVOL=/liveslak/myhome.icc:/home
ISOPERSISTENCE=/liveslak/persistence.icc
TZ=Europe/Amsterdam
LIVE_HOSTNAME=zelazny
I added the variables "TZ" and "LIVE_HOSTNAME" manually by opening the
configuration file in an editor.
The following variables are supported in the isocomp configuration file,
but not managed by "isocomp.sh"; they all correspond to liveslak
boot parameters by the way:
BLACKLIST, KEYMAP, LIVE_HOSTNAME, LOAD, LOCALE,
NOLOAD, RUNLEVEL, TWEAKS, TZ and XKB.
The value of the "LUKSVOL" variable can hold multiple
"containerfile:mountpoint" definitions, separated by commas.
The variable "LIVESLAKROOT" defines the root of a secondary liveslak
directory tree on your disk.
|