| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
| |
Thanks to Juan Fernandez for reporting.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
This functionality has been present for more than three years already,
but was never properly documented. Fixing that now.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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'.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 '#'.
|
|
|
|
|
|
|
| |
- Explanation of the partition layout of a USB stick
when created with iso2usb.sh
- Updated URLS
- Many small fixes, mostly typos
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
'2' enables verbose script execution;
'4' dumps you into a debug shell right before the switch_root.
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
Specifically, stress the fact that generating an ISO requires that you
create a local Slackware mirror prior to running 'make_slackware_live.sh',
since the script will not download official Slackware packages,
only 3rd party packages.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
The 'min' package list contains the generic kernel.
This package list is special because the 'make_slackware_live.sh' script
will also take care of the ISO boot configuration while processing it.
A custom Live OS may want to use a custom filename instead of "min.lst",
so the variable $MINLIST was created for that purpose.
|
| |
|
|
|
|
|
|
| |
This allows people to find the instructions on how to edit the boot
commandline in syslinux or grub more easily. Now it is here:
http://docs.slackware.com/slackware:liveslak#booting_the_live_os
|
|
|
|
|
|
|
|
|
|
|
| |
* iso2usb.sh: added '-r' parameter to refresh an existing USB Live stick
with data from a new Live ISO.
* boot: added 'nop=wipe' parameter which will cause all persistent data
(in the persistence directory or a persistent data container) to be
erased. This allows you to repair a case of corrupted persistent
data which can occur after you modified files that are part of a
squashfs module.
Note that this boot option will leave an encrypted /home un-touched!
|
| |
|
|
|
|
|
|
| |
For some people, an ISO generated with xorriso instead of using
mkisofs/isohybrid is more compatible with other tools or hardware.
You need to install xorriso separately, it is not included with Slackware.
|
| |
|
| |
|
|
|
|
| |
Allows the user to start the SSH server, now that it is disabled by default.
|
| |
|
|
|
|
| |
Provided by GigglesUK, thanks.
|
| |
|