| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
New parameter to the script:
-l|--lukshome <name> Custom path to the containerfile for your LUKS
encrypted /home (slhome by default).
Note: not only (just as with the persistence container) can you choose
a custom name for the the LUKS container file but you can also create it
in a subdirectory instead of in the filesystem root now.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-r|--refresh =>
Refresh an existing Live USB stick with new ISO content.
The refresh option "-r" can be used when you have a Live USB stick and you
want to update the liveslak files with new versions on an ISO image file
which you downloaded/created.
The USB stick will not be formatted in this case, and user modifications
like LUKS-encrypted homedirectory or persistence data will not be touched.
The "system" squashfs modules will be replaced with the versions on the ISO
file and any squashfs module not present in the system/ directory of the ISO
will be deleted.
The "optional" and "addons" directories are treated a bit differently:
The files in there that you added yourself will not be deleted when
the content of these directories is refreshed with the content from the ISO
(unless of course your added files have the same name as one of the files
in the ISO).
The content of the /boot and /EFI directories will both be replaced with
whatever is on the ISO image.
|
|
|
|
|
|
| |
It appears that other distros do not always contain "iso-info" which
is part of "libcdio". The "isoinfo" program ion the other hand,
which is part of "cdrtools" is more widely used.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This requires functionality in grub which is currently not enabled
in Slackware's grub package.
If you want a 32-bit Live ISO that boots on UEFI computers, you need
to recompile Slackware's grub with the patch for grub.SlackBuild which
you can find in the ./patches subdirectory.
Then you need to set the variable "EFI32" to "YES" in the
'make_slackware_live.sh' script and (re-)generate your 32-bit ISO.
The resulting 32-bit Live ISO will be UEFI-bootable.
|
|
|
|
|
|
|
|
|
|
|
| |
Syntax of the new parameter:
-C|--cryptpersistfile size|perc
Explanation:
Use a LUKS-encrypted 'persistence' file instead of a directory
or an un-encrypted file (which is created using the "-P" parameter).
The filename will be 'persistence.img' just like the unencrypted version.
A numerical size in K,M,G or a percentage of available free space
is needed as input value with the "-C" parameter.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds an option to store persistent data in a container file instead of
a directory in the USB stick's Linux filesystem.
Theoretically, this would allow the Slackware Live files to be copied to
a VFAT partition on a stick without erasing it, as long as the stick is
made bootable and the Live kernel & initrd are added to the boot menu.
To create a USB stick from the Live ISO which uses a persistence file instead
of a persistence directory, run the 'iso2usb.sh' script with a new parameter:
-P|--persistfile Use a 'persistence' container file instead of
a directory (for use on FAT filesystem).
The following example creates a 750 MB LUKS-encrypted container file
'slhome.img' which will contain /home ; as well as a file '/persistence.img'
in the root of the USB's Linux partition which will be used to store the
Live OS' persistent data:
./iso2usb.sh -i slackware64-live-current.iso -o /dev/sdX -c 750M -P
NOTE:
The persistence container file will be created as a 'sparse' file which
starts as an empty file not using up any disk space, but is allowed to
grow dynamically to consume a maximum value of 90% of the free disk space
on the Linux partition of the USB stick.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using iso2usb.sh script's new '-c' parameter, you can define the size for
a container file in the root of the USB stick's Linux partition.
- The container file will be loop-mounted and LUKS-encrypted and the
Live OS will mount the filesystem inside the container on /home/.
- The LUKS passphrase will be defined when executing the 'iso2usb.sh' script.
- The original /home content of the ISO will be copied into the
LUKS-encrypted container during execution of the 'iso2usb.sh' script.
- If for whatever reason you do not want to unlock & mount the LUKS container
during boot, you must add the boot parameter " luksvol= " to the syslinux
or grub commandline.
|
| |
|
|
|
|
|
|
|
|
|
| |
Two new parameters '--force' and '--persistence'. Read "usb2iso.sh --help".
Size of the EFI partition was reduced from 200 to 100 MB.
The wait-for-root time in the initrd.img file is changed for both BIOS
and UEFI boot; this should make boot work out of the box for most computers.
More robustness was added in handling race conditions.
Only make the USB stick UEFI-bootable if the ISO file is capable of the same.
|
| |
|
| |
|
| |
|
|
This is Beta 2.
Read http://alien.slackbook.org/blog/slackware-live-edition-beta-2
for all the details.
|