| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
| |
The non-SMP kernels refuse to start the init script in initramfs since 5.15.x
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Read the updates in the README for more background and guidance.
User notice:
As a one-time action the very first time you boot a Secure Boot enabled
liveslak ISO, you will have to enroll the liveslak certificate
(/EFI/BOOT/liveslak.der) with which the Slackware boot-up binaries
(grub and kernel) were signed into your computer's MOK (Machine Owner Key
database).
This enrollment request will show on-screen during initial boot,
just follow the prompts to 'enroll from disk'. Afterwards the computer
will reboot and from then on, your liveslak will boot without any
user intervention on your Secure Boot computer.
Note:
liveslak uses Fedora's initial boot loader (the 'shim') which
has been signed by Microsoft. In future we may get our own
signed shim for liveslak and/or Slackware, but don't hold your breath.
|
| |
|
|
|
| |
Goal is to keep the XFCE image below 700 MB (CDROM size) while adding
programs that are needed.
|
| |
|
|
|
| |
Micro version bump for the DAW Live ISO respin to address icu4c and llvm
library updates in -current,
|
| | |
|
| | |
|
| |
|
|
|
| |
Using rc.local to post-configure the kernel was nice,
but this solution is cleaner and less lines of code.
|
| |
|
|
|
| |
Micro version bump for the DAW Live ISO,
which will get a full pre-emptive kernel.
|
| |
|
|
|
|
| |
The old way was not wrong, until I added the possibility to liveslak
to use a package in ./testing . This part of the code needed an overhaul
as a result of that, and now it looks cleaner than before.
|
| |
|
|
|
| |
Note: this was enabled in kernel 5.14.15 in Slackware-current.
On older / non-preemptive kernels the above will do nothing.
|
| | |
|
| | |
|
| | |
|
| | |
|
Eric Hameleers