| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The syntax for the 'persistence' boot parameter has been extended.
The persistence directory/container no longer needs to be in the root
of the filesystem; you can specify an absolute path.
Additionally, you can specify the partition containing the filesystem
on which the persistence is located, or simply specify 'scandev',
to request that liveslak tries to find the partition for you:
persistence=/dev/sdX:/path/to/mypersistence
persistence=scandev:/path/to/mypersistence
In addition, a UUID or LABEL value of the filesystem will be accepted:
persistence=cd68b6f5-5b5a-4d27-9649-7827489f94a5:/path/to/mypersistence
This functionality will be useful if you need the persistence directory
or container to be located somewhere else than on the Live USB stick,
for instance on a local hard disk partition.
Useful for network (PXE) boot because the overlayfs does not support a
writable upper layer of your live filesystem over NFS. If you still want
to offer persistence to users of PXE-booted Slackware Live, you can now
use the local harddisk partitions or a local USB stick for persistence.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Excerpt from RFC 8375 (https://tools.ietf.org/html/rfc8375):
Users and devices within a home network (hereafter referred to as
"homenet") require devices and services to be identified by names
that are unique within the boundaries of the homenet [RFC7368]. The
naming mechanism needs to function without configuration from the
user. While it may be possible for a name to be delegated by an ISP,
homenets must also function in the absence of such a delegation.
This document reserves the name 'home.arpa.' to serve as the default
name for this purpose, with a scope limited to each individual
homenet.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This uses two squashfs modules that are currently only found in the
LEAN and XFCE images: 'min' and 'noxbase'.
These two provide a functional console-only Slackware with a lot of useful
programs. It will connect to a DHCP server automatically and it also
contains the 'setup2hd' script to be able to install Slackware from a network
mirror.
And since the Console OS gets loaded into RAM, you can remove your USB stick
after booting and use that stick for other purposes.
Use-case:
- You have one computer with a network connection and one USB stick, and want
to create a persistent Slackware Live on USB.
- Download an ISO supporting 'Console OS' to the computer's hard drive, and
transfer the ISO to the USB stick using the computer's ISO imaging tools,
making the stick bootable but not persistent.
- Boot from the USB stick, select the "Console OS in RAM" option.
- After you logged into the Console Slackware, mount the computer's hard drive.
- Use the 'iso2usb.sh' script that comes with liveslak to extract the ISO
content to the USB stick, making it persistent. See the README.txt for
instructions.
-----------------------------------------------------------------------------
Implemented as an extension of the liveslak 'toram' boot parameter.
Adding 'toram=core' to the boot commandline will load circa 500 MB of squashfs
modules into RAM and boot into a sparse but functional console environment.
For supported Live variants (currently LEAN and XFCE) the script
'make_slackware_live.sh' will automatically add a menu item "Console OS in RAM"
to the Syslinux and Grub bootloaders, using this 'toram=core' parameter.
TODO: add this as an option to all liveslak variants. Not so trivial to do.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
toram=all
Prevent writes to disk since we are supposed to run from RAM;
equivalent to parameter "toram".
toram=os
Load OS modules into RAM, but write persistent data to USB.
|
|
|
|
|
| |
New boot parameter: "domain=your_custom_domain",
The domain component defaults to 'example.net'.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using a squashfs module created from nvidia-kernel and nvidia-driver packages.
A sample script for creating this nvidia module was added to liveslak, see:
./contrib/scripts/makemod_nvidia.
These two packages were created using the scripts from slackbuilds.org:
https://slackbuilds.org/repository/14.2/system/nvidia-kernel/
https://slackbuilds.org/repository/14.2/system/nvidia-driver/
Note that the nvidia-driver package was created on a multilib system so that
it could pick up 32bit compat libraries (needed for Steam among others),
and the CURRENT variable was set to 'yes' so that the nvidia drivers are
fully separated from mesa and xorg-server and do not overwrite system libraries:
# COMPAT32="yes" CURRENT="yes" ./nvidia-driver.SlackBuild
|
|
|
|
|
|
|
|
|
|
|
| |
Liveslak can optionally load a OS config file "@DISTRO@_os.cfg" from within
the 'livemain' directory on the boot medium, which contains "VARIABLE=value"
lines, where VARIABLE is one of the following variables:
BLACKLIST, KEYMAP, LIVE_HOSTNAME, LOAD, LOCALE, LUKSVOL,
NOLOAD, RUNLEVEL, TWEAKS, TZ, XKB.
During boot, any variable from that file will be set in the boot environment
if it has not yet been defined in the init script.
You can prevent this behaviour by adding 'cfg=skip' to the boot commandline.
|
|
|
|
|
| |
These lines became obsolete with Linux kernel 2.6 (Slackware >= 11)
when the kernel module extension changed from .o to .ko.
|
|
|
|
|
|
|
| |
The default for 'udevadm trigger' is 'change', not 'add', so the scriptline
basically did nothing. This prevented some network devices from getting
initialized because their subsystem is 'pci' and not 'net'.
Thanks to Kanaya for debugging this with his Nvidia MCP51 ethernet device.
|
|
|
|
|
| |
Do not make assumptions about how partitions and block devices are named.
but check the OS instead (in /sys/block and /sys/class/block).
|
|
|
|
| |
Note that UEFI PXE-boot is not yet working, I do not know why.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The live init script creates a /etc/fastboot file to prevent any
file system check on boot. This is cleaner than hacking rc.S and failing.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added a new parameter to 'make_slackware_live.sh' script:
-l <localization>
For example, create a liveslak ISO with dutch as the default language
instead of US english:
# ./make_slackware_live.sh -l nl
Using this parameter you can onfigure a different default language
for the resulting ISO image. The default localization if you do not
supply this parameter remains "us" as before.
The boot menu offers a selection of other languages/localizations
to pick from (currently you can select any of 'be br da gb de de_ch es
fr fr_ch it ja nl pt ru se us') but now you can create your own brand
of liveslak ISO with your own language as the default.
|
|
|
|
|
| |
Variables defined on the boot commandline have preference over
any variable set in the .cfg file.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new zstd compression support for squashfs modules allows for a much
snappier system because zstd decompression is 5 times faster than that of
xz (see https://sourceforge.net/p/squashfs/mailman/message/35989805/), but
at the expense of ISO sizes that are at least 10% bigger. The latter means
that we have to do some more pruning of the XFCE and PLASMA5 images to make
these fit in a CDROM and DVD image, respectively.
Here are some initial benchmarks with PLASMA5 Live ISO images,
booting in QEMU (times are in minutes:seconds):
Stage ZSTD XZ
---------------------------------------
Boot to runlevel 4 start 0:39 0:50
SDDM Login Manager visible 0:55 1:26
Plasma5 desktop ready 1:42 3:17
I also tested two of the bigger applications, measuring the time between
entering the command in a terminal and having a usable application window:
Stage ZSTD XZ
----------------------------------------
LO Writer window visible 0:17 0:34
Chromium window visible 0:09 0:14
It is obvious that a big Desktop Environment like Plasma5 where a lot of
binaries have to be loaded from their squashfs modules benefits a lot
from zstd, because after booting, the Plasma5 DE is available in
roughly 53% of the time it takes when using xz compression.
Zstd support in squashfs was added to Linux kernel 4.14. That means,
no customimzation of Slackware is required to make the Live OS work from
zstd-compressed squashfs modules.
In order to *create* these zstd-compressed squashfs modules, you will need
some custom packages at the moment, until they get added to Slackware-current:
zstd and a rebuild squashfs-tools to add the lacking zstd support to
mksqhashfs/unsquashfs.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The configuration file must be in the liveslak main directory ('/liveslak'
by default) and be called 'DISTRO_os.cfg' where DISTRO is the lower-case
name of the distro ('slackware' by default).
The following variables can be defined in the configuration file,
one per line, in the format VAR=value:
BLACKLIST, INIT, KEYMAP, LIVE_HOSTNAME, LOAD, LOCALE, LUKSVOL, NOLOAD,
RUNLEVEL, TWEAKS, TZ, XKB.
Since the configuration file is sourced by the live init script, it is OK
to have comments in it that are prefixed with '#'.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose: to update the content of a Slackware Live USB stick.
upslak.sh accepts the following parameters:
-b|--nobackup Do not try to backup original kernel and modules.
-d|--devices List removable devices on this computer.
-h|--help This help.
-i|--init <filename> Replacement init script.
-k|--kernel <filename> The kernel file (or package).
-m|--kmoddir <name> The kernel modules directory (or package).
-n|--netsupport Add network boot support if not yet present.
-o|--outdev <filename> The device name of your USB drive.
-p|--persistence Move persistent data into new Live module.
-r|--restore Restore previous kernel and modules.
-s|--scan Scan for insertion of new USB device instead of
providing a devicename (using option '-o').
-v|--verbose Show verbose messages.
-w|--wait<number> Add <number> seconds wait time to initialize USB.
|
| |
|
|
|
|
|
|
|
| |
Use the 'scandev' keyword instead of specifying an actual partition name
if you want liveslak to scan all partitions for the ISO.
Use this if you are not sure of the devicename and have no means of
figuring it out.
|
|
|
|
|
|
|
|
|
|
|
| |
Freetype has enabled a 'new style' of sub-pixel hinting, based on the
Infinality patch but simplified for speed.
Some people feel that this new type of hinting is resulting in worse font
rendering than with the old auto-hinter built into Freetype.
The new tweak 'nsh' effectively disables the new type of sub-pixel hinting
and makes Freetype fall back to the old behaviour.
Usage: add "tweaks=nsh" to the boot commandline of the Live OS.
|
|
|
|
|
|
|
|
|
| |
New supported LIVEDE value: DLACK
This merge adds Dlackware as a DE choice when generating the ISO.
Dlackware is Slackware with PAM, systemd and Gnome3 (and without KDE4).
I think this is an interesting experiment. Know your enemy ;-)
Thanks to bartgymnast of the Dlackware team who provided the patches.
|
|
This file was forgotten in the previous commit.
It has now also been given a '.tpl' extension in the liveslak sources,
to indicate that it is a template and not usable as-is.
The 'make_slackware_live.sh' script parses the template file and performs
a series of variable substitutions to generate the final 'init' script
inside the initrd of the ISO image.
|