| Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
Currently not working and commented-out, but we'll figure it out.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The XDM man page is a bit vague about this functionality but the default
Xresources file which ships with xdm has the support added.
I had removed it for liveslak but added it back in part now.
When entering your credentials and pressing ENTER, still the default X11
session will be started. But now instead of ENTER, when you press:
F1: failsafe session will be started.
F2: kde session will be started.
F3: xfce session will be started.
F4: fvwm2 session will be started.
F5: fluxbox session will be started.
|
|
The mtr tool depends on it. When booting the Console OS (min and noxbase
modules only) the jansson library is not found
|
|
|
|
|
|
- PXE boot of a UEFI computer finally works.
Note that if it does not work for you out of the box, look at the section
where a section of 'dhcp-match' and 'dhcp-boot' lines is commented out.
If you remove the comment characters from these 8 lines and instead,
add a comment character '#' in front of the 'dhcp-match' and 'pxe-service'
lines a bit higher up, your UEFI computer might actually succeed in
booting over the network.
- Optionally, the script can hide its PXE clients behind a NAT router
in case external network is not accessible via normal routing.
- Correct nmcli syntax is being used now...
- Network interface will be de-configured when the script ends, likewise
any NAT iptables rules will be removed afterwards.
|
|
We already had several smaller font sizes, perhaps liveslak will use
this larger font someday.
|
|
|
|
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.
|
|
Some people prefer tmux over screen, moreso because other distros seem
to only ship tmux and omit screen. Why?
|
|
This needed some changes because the Slackware rc.0 and rc.6 scripts have
evolved and my old hacks no longer worked.
|
|
|
|
|
|
Since early 2019, when you dd-ed or cp-ed a live ISO directly to a USB stick,
and you booted from this stick on a UEFI computer, you would end up in the
GRUB commandline, because $prefix would not be defined and GRUB would be
unable to find its files.
My 2019 modification fixed PXE boot but broke this specific case of UEFI boot.
And now it has finally been fixed after I had a brain fart.
|
|
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).
|
|
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.
|
|
|
Eric Hameleers
