Tuxedo
2018-09-19 08:06:28 UTC
Hello,
Can Slackware Live be used to boot into an existing HD Slackware
installation?
Having downloaded and made a Slackware Live USB from a slackware64-live-
current.iso image, the version uname returns is 4.14.68 #2 SMP Wed Sep 5.
Slackware current is working on the system and boots fine via LILO, but in
case of an emergency boot failure, such as if regular MBR booting might
break for whatever reason, an alternative booting method will be needed.
The version uname returns for the HD installed Slackware current is 4.14.67
#2 SMP Fri Aug 24.
Can for example booting of the HD version be done simply by entering certain
parameters at the 'boot:' prompt of the live version?
The regular flash boot stick created at the HD installation stage doesn't
work because the flash disk creation process is not compatible with
LVM+LUKS.
Regular booting of the HD installed Slackware is done via an unencrypted
/boot partition at /dev/nvme0n1p2, which contains the following:
README.initrd
System.map
System.map-generic-4.14.67
System.map-huge-4.14.67
boot.10300
boot_message.txt
coffee.dat
config
config-generic-4.14.67.x64
config-huge-4.14.67.x64
elilo-ia32.efi
elilo-x86_64.efi
grub
initrd-tree
initrd.gz
inside.bmp
inside.dat
lost+found
map
onlyblue.bmp
onlyblue.dat
slack.bmp
tuxlogo.bmp
tuxlogo.dat
vmlinuz
vmlinuz-generic
vmlinuz-generic-4.14.67
vmlinuz-huge
vmlinuz-huge-4.14.67
The /etc/lilo.conf file on /dev/nvme0n1p3 as used when installing LILO to
MBR on /dev/nvme0n1 contains the following:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
lba32 # Allow booting past 1024th cylinder with a recent BIOS
boot = /dev/nvme0n1
# Append any additional kernel parameters:
append=" "
prompt
timeout = 50
# Normal VGA console
vga = normal
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-4.14.67
initrd = /boot/initrd.gz
root = /dev/cryptvg/root
label = Linux
read-only # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/nvme0n1p1
label = Windows
# map-drive = 0x80
# to = 0x81
# map-drive = 0x81
# to = 0x80
table = /dev/nvme0n1
# Windows bootable partition config ends
Thanks for any ideas how to start the system in case of an MBR boot failure.
Tuxedo
Can Slackware Live be used to boot into an existing HD Slackware
installation?
Having downloaded and made a Slackware Live USB from a slackware64-live-
current.iso image, the version uname returns is 4.14.68 #2 SMP Wed Sep 5.
Slackware current is working on the system and boots fine via LILO, but in
case of an emergency boot failure, such as if regular MBR booting might
break for whatever reason, an alternative booting method will be needed.
The version uname returns for the HD installed Slackware current is 4.14.67
#2 SMP Fri Aug 24.
Can for example booting of the HD version be done simply by entering certain
parameters at the 'boot:' prompt of the live version?
The regular flash boot stick created at the HD installation stage doesn't
work because the flash disk creation process is not compatible with
LVM+LUKS.
Regular booting of the HD installed Slackware is done via an unencrypted
/boot partition at /dev/nvme0n1p2, which contains the following:
README.initrd
System.map
System.map-generic-4.14.67
System.map-huge-4.14.67
boot.10300
boot_message.txt
coffee.dat
config
config-generic-4.14.67.x64
config-huge-4.14.67.x64
elilo-ia32.efi
elilo-x86_64.efi
grub
initrd-tree
initrd.gz
inside.bmp
inside.dat
lost+found
map
onlyblue.bmp
onlyblue.dat
slack.bmp
tuxlogo.bmp
tuxlogo.dat
vmlinuz
vmlinuz-generic
vmlinuz-generic-4.14.67
vmlinuz-huge
vmlinuz-huge-4.14.67
The /etc/lilo.conf file on /dev/nvme0n1p3 as used when installing LILO to
MBR on /dev/nvme0n1 contains the following:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
lba32 # Allow booting past 1024th cylinder with a recent BIOS
boot = /dev/nvme0n1
# Append any additional kernel parameters:
append=" "
prompt
timeout = 50
# Normal VGA console
vga = normal
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-4.14.67
initrd = /boot/initrd.gz
root = /dev/cryptvg/root
label = Linux
read-only # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/nvme0n1p1
label = Windows
# map-drive = 0x80
# to = 0x81
# map-drive = 0x81
# to = 0x80
table = /dev/nvme0n1
# Windows bootable partition config ends
Thanks for any ideas how to start the system in case of an MBR boot failure.
Tuxedo