| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This is not necessary, annoying and pollutes the screen during boot-up.
|
|
|
|
| |
Just because Google is not everything.
|
|
|
|
|
| |
The pxeserver.tpl will start using @KAPPEND@ template, so the $KAPPEND
variable needs to be defined when we get there.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To name the most important:
- The filesystem inside the containers is no longer limited to ext4 and can
now be btrfs, ext2, ext4, f2fs, jfs or xfs. The scripts 'iso2usb.sh' and
'isocomp.sh' now support this filesystem choice via a new '-F' switch.
- The 'upslak.sh' script can now extend the size of your home and persistence
container files, in case you run out of storage there.
- The internal functions used in 'iso2usb.sh' 'isocomp.sh' and 'upslak.sh'
are mostly unified now, and I intend to split all functions off into a
separate file which makes maintenance as well as adding new functionaliy
easier.
- The 'upslak.sh' script will now create a 'kernelmodules' squashfs module
and copies it to liveslak's 'addons' directory after updating the boot
kernel on the USB stick and the kernel-modules inside the initrd image.
This way, you no longer end up with a broken Live OS if you forgot to
install a Slackware kernel-modules package inside the persistent Live OS
prior to running 'upslak.sh' with the '-k' and '-m' parameters.
In addition, the README.txt was updated with these enhancements so that
the liveslak documentation is again completely up to date.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Changes in Slackware-current in March and May 2023 broke support for
detection of Ventoy disk on UEFI computers.
Liveslak's initrd needed to have efivarfs module added, so that
/sys/firmware/efi/efivars can be mounted by the live init script.
With kernel 6.x the content of what's found under efivars
has changed - instead of being represented as a directory with the
efi datastructures as files, liveslak now needs to deal with
a single file instead and find the offset in there.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For kdesu to work with the sudo backend in KDE5 with newer
versions of sudo (since 2022), we need to disable use_pty for kdesu.
KDE5 fixed this in git on 04-aug-2023, see
https://bugs.kde.org/show_bug.cgi?id=452532 but it does not hurt
to implement the workaround in liveslak, as it helps to support
older KDE releases.
This is the KDE commit message, see https://invent.kde.org/frameworks/kdesu/-/commit/732dd812d67c7fa62bd187c1171950ca85259b0b :
Recent versions of sudo have use_pty enabled by default, which means that sudo
creates a PTY for starting the user process inside after successful
authentication. This PTY inherits the configuration of sudo's TTY, but later
changes are not transferred. Make sure that echo is already disabled when sudo
is started, as disabling it later has no effect on the nested PTY.
|
| |
|
| |
|
|
|
|
|
|
| |
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).
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
| |
So we do a string comparison instead.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
In particular, trimming 'waste' will not remove lots of dynamic and static
libraries, which 'bloat' will do for you.
|
| |
|
| |
|
|
|
|
|
| |
Frameworks 5.94.0 changed the file where the value of the
'defaultWallpaperTheme' property is defined.
|
| |
|
|
|
|
| |
Adding rtsx_pci:rtsx_pci_sdmmc modules to the initrd.
|
| |
|
| |
|
| |
|
|
|
|
| |
Thanks to GigglesUK for pointing it out.
|
| |
|
| |
|
|
|
|
| |
To accompany the release of Slackware 15.0 stable!
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The firewall will be configured and installed only when you use setup2hd
to install the Live OS to your hard drive.
The scripts are not particular to Slackware Live; you can easily copy
the resulting files /usr/sbin/myfwconfig, /etc/rc.d/rc.firewall
and /var/lib/pkgtools/setup/setup.firewall out of the installed system
and use them anywhere on a Slackware-compatible OS.
- The 'myfwconfig' script will ask a few simple questions and generate the
ipv4 and ipv6 configuration in /etc/firewall/.
- The 'rc.firewall' script will load/save its iptables/ip6tables
configuration from /etc/firewall/ files.
- The 'setup.firewall' script is a convenient way to call the firewall
configurator from pkgtools or during Slackware's installation to harddisk.
|
| |
|