Skip to content

Commit

Permalink
Mon May 28 19:12:29 UTC 2018
Browse files Browse the repository at this point in the history 
a/pkgtools-15.0-noarch-13.txz:  Rebuilt.
  installpkg: default line length for --terselength is the number of columns.
  removepkg: added --terse mode.
  upgradepkg: default line length for --terselength is the number of columns.
  upgradepkg: accept -option in addition to --option.
ap/vim-8.1.0026-x86_64-1.txz:  Upgraded.
d/bison-3.0.5-x86_64-1.txz:  Upgraded.
e/emacs-26.1-x86_64-1.txz:  Upgraded.
kde/kopete-4.14.3-x86_64-8.txz:  Rebuilt.
  Recompiled against libidn-1.35.
n/conntrack-tools-1.4.5-x86_64-1.txz:  Upgraded.
n/libnetfilter_conntrack-1.0.7-x86_64-1.txz:  Upgraded.
n/libnftnl-1.1.0-x86_64-1.txz:  Upgraded.
n/links-2.16-x86_64-2.txz:  Rebuilt.
  Rebuilt to enable X driver for -g mode.
n/lynx-2.8.9dev.19-x86_64-1.txz:  Upgraded.
n/nftables-0.8.5-x86_64-1.txz:  Upgraded.
n/p11-kit-0.23.11-x86_64-1.txz:  Upgraded.
n/ulogd-2.0.7-x86_64-1.txz:  Upgraded.
n/whois-5.3.1-x86_64-1.txz:  Upgraded.
xap/network-manager-applet-1.8.12-x86_64-1.txz:  Upgraded.
xap/vim-gvim-8.1.0026-x86_64-1.txz:  Upgraded.
  • Loading branch information
@alienbob
Patrick J Volkerding authored and alienbob committed May 31, 2018
1 parent d31c508 commit 646a5c1
Show file tree
Hide file tree
Showing 4,010 changed files with 223,107 additions and 499,061 deletions.
The diff you're trying to view is too large. We only load the first 3000 changed files.
378 changes: 149 additions & 229 deletions CHANGES_AND_HINTS.TXT
View file

Large diffs are not rendered by default.

15,300 changes: 8,399 additions & 6,901 deletions ChangeLog.txt
View file

Large diffs are not rendered by default.

4 changes: 2 additions & 2 deletions EFI/BOOT/grub.cfg
View file
Original file line number Diff line number Diff line change
Expand Up @@ -9,13 +9,13 @@ set hidden_timeout_quiet=false

#terminal_output gfxterm

menuentry "Slackware 14.2 huge.s kernel"{
menuentry "Slackware 15.0 huge.s kernel"{
echo "Loading huge.s kernel and installer initrd. Please wait..."
linux /kernels/huge.s/bzImage vga=normal load_ramdisk=1 prompt_ramdisk=0 ro printk.time=0 nomodeset SLACK_KERNEL=huge.s
initrd /isolinux/initrd.img
}

menuentry "Slackware 14.2 huge.s kernel (use KMS console)"{
menuentry "Slackware 15.0 huge.s kernel (use KMS console)"{
echo "Loading huge.s kernel (with KMS) and installer initrd. Please wait..."
linux /kernels/huge.s/bzImage vga=normal load_ramdisk=1 prompt_ramdisk=0 ro printk.time=0 SLACK_KERNEL=huge.s
initrd /isolinux/initrd.img
Expand Down
4 changes: 2 additions & 2 deletions EFI/BOOT/make-grub.sh
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
#!/bin/sh

# Copyright 2013 Patrick J. Volkerding, Sebeka, Minnesota, USA
# Copyright 2013, 2018 Patrick J. Volkerding, Sebeka, Minnesota, USA
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
Expand All @@ -25,7 +25,7 @@
# UEFI systems.

# First, build bootx64.efi, which will be installed here in /EFI/BOOT:
grub-mkimage --format=x86_64-efi --output=bootx64.efi --config=grub-embedded.cfg --compression=xz --prefix=/EFI/BOOT part_gpt part_msdos fat ext2 hfs hfsplus iso9660 udf ufs1 ufs2 zfs chain linux boot appleldr ahci configfile normal regexp minicmd reboot halt search search_fs_file search_fs_uuid search_label gfxterm gfxmenu efi_gop efi_uga all_video loadbios gzio echo true probe loadenv bitmap_scale font cat help ls png jpeg tga test at_keyboard usb_keyboard
grub-mkimage --format=x86_64-efi --output=bootx64.efi --config=grub-embedded.cfg --compression=xz --prefix=/EFI/BOOT part_gpt part_msdos fat ext2 hfs hfsplus iso9660 udf ufs1 ufs2 zfs chain linux boot appleldr configfile normal regexp minicmd reboot halt search search_fs_file search_fs_uuid search_label gfxterm gfxmenu efi_gop efi_uga all_video loadbios gzio echo true probe loadenv bitmap_scale font cat help ls png jpeg tga test at_keyboard usb_keyboard

# Then, create a FAT formatted image that contains bootx64.efi in the
# /EFI/BOOT directory. This is used to bootstrap GRUB from the ISO image.
Expand Down
15,752 changes: 10,572 additions & 5,180 deletions FILELIST.TXT
View file

Large diffs are not rendered by default.

62 changes: 31 additions & 31 deletions README.initrd
View file
Original file line number Diff line number Diff line change
@@ -1,85 +1,85 @@

Slackware initrd mini HOWTO
by Patrick Volkerding, [email protected]
Fri Jun 24 13:32:40 CDT 2016
Fri May 25 23:01:32 UTC 2018

This document describes how to create and install an initrd, which may be
required to use the 4.x kernel. Also see "man mkinitrd".
required to use the 4.x kernel. Also see "man mkinitrd".

1. What is an initrd?
2. Why to I need an initrd?
3. How do I build the initrd?
4. Now that I've built an initrd, how do I use it?
1. What is an initrd?
2. Why to I need an initrd?
3. How do I build the initrd?
4. Now that I've built an initrd, how do I use it?


1. What is an initrd?
1. What is an initrd?

Initrd stands for "initial ramdisk". An initial ramdisk is a very small
Initrd stands for "initial ramdisk". An initial ramdisk is a very small
Linux filesystem that is loaded into RAM and mounted as the kernel boots,
and before the main root filesystem is mounted.

2. Why do I need an initrd?
2. Why do I need an initrd?

The usual reason to use an initrd is because you need to load kernel
modules before mounting the root partition. Usually these modules are
modules before mounting the root partition. Usually these modules are
required to support the filesystem used by the root partition (ext3, ext4,
btrfs, xfs), or perhaps the controller that the hard drive is attached
to (SCSI, RAID, etc). Essentially, there are so many different options
to (SCSI, RAID, etc). Essentially, there are so many different options
available in modern Linux kernels that it isn't practical to try to ship
many different kernels to try to cover everyone's needs. It's a lot more
many different kernels to try to cover everyone's needs. It's a lot more
flexible to ship a generic kernel and a set of kernel modules for it.

3. How do I build the initrd?
3. How do I build the initrd?

The easiest way to make the initrd is to use the mkinitrd script included
in Slackware's mkinitrd package. We'll walk through the process of
upgrading to the generic 4.4.14 Linux kernel using the packages
in Slackware's mkinitrd package. We'll walk through the process of
upgrading to the generic 4.14.44 Linux kernel using the packages
found in Slackware's slackware/a/ directory.

First, make sure the kernel, kernel modules, and mkinitrd package are
installed (the current version numbers might be a little different, so
this is just an example):

installpkg kernel-generic-4.4.14-x86_64-1.txz
installpkg kernel-modules-4.4.14-x86_64-1.txz
installpkg mkinitrd-1.4.8-x86_64-8.txz
installpkg kernel-generic-4.14.44-x86_64-1.txz
installpkg kernel-modules-4.14.44-x86_64-1.txz
installpkg mkinitrd-1.4.11-x86_64-6.txz

Change into the /boot directory:

cd /boot

Now you'll want to run "mkinitrd". I'm using ext4 for my root filesystem,
Now you'll want to run "mkinitrd". I'm using ext4 for my root filesystem,
and since the disk controller requires no special support the ext4 module
will be the only one I need to load:

mkinitrd -c -k 4.4.14 -m ext4
mkinitrd -c -k 4.14.44 -m ext4

This should do two things. First, it will create a directory
/boot/initrd-tree containing the initrd's filesystem. Then it will
create an initrd (/boot/initrd.gz) from this tree. If you wanted to,
This should do two things. First, it will create a directory
/boot/initrd-tree containing the initrd's filesystem. Then it will
create an initrd (/boot/initrd.gz) from this tree. If you wanted to,
you could make some additional changes in /boot/initrd-tree/ and
then run mkinitrd again without options to rebuild the image. That's
then run mkinitrd again without options to rebuild the image. That's
optional, though, and only advanced users will need to think about that.

Here's another example: Build an initrd image using Linux 4.4.14
Here's another example: Build an initrd image using Linux 4.14.44
kernel modules for a system with an ext4 root partition on /dev/sdb3:

mkinitrd -c -k 4.4.14 -m ext4 -f ext4 -r /dev/sdb3
mkinitrd -c -k 4.14.44 -m ext4 -f ext4 -r /dev/sdb3


4. Now that I've built an initrd, how do I use it?
4. Now that I've built an initrd, how do I use it?

Now that you've got an initrd (/boot/initrd.gz), you'll want to load
it along with the kernel at boot time. If you use LILO for your boot
it along with the kernel at boot time. If you use LILO for your boot
loader you'll need to edit /etc/lilo.conf and add a line to load the
initrd. Here's an example section of lilo.conf showing how this is
initrd. Here's an example section of lilo.conf showing how this is
done:

# Linux bootable partition config begins
image = /boot/vmlinuz-generic-4.4.14
image = /boot/vmlinuz-generic
initrd = /boot/initrd.gz
root = /dev/sda6
label = Lnx4414
label = Slackware
read-only
# Linux bootable partition config ends

Expand Down
60 changes: 30 additions & 30 deletions README_CRYPT.TXT
View file
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ left unencrypted. This partition must contain the kernel(s) you want to boot
from, and the initrd image that is needed with encrypted volumes. You need
to install LILO either to the MBR - or if that is not possible, into the
root sector of this small unencrypted partition. You will probably guess
why we can not use an encrypted partition for this...
why we cannot use an encrypted partition for this...


Using cryptsetup during Slackware installation
Expand Down Expand Up @@ -140,18 +140,20 @@ an ordinary disk partition when we get to the TARGET selection in 'setup'. The
mapped device nodes will be created in the directory '/dev/mapper'. The command
will ask you for the passphrase which you entered during the "luksFormat"
operation. The last argument that the command takes is the name of the mapped
device. We will call our mapped device 'crypthome' (any name will do). It
will be available for use as the block device '/dev/mapper/crypthome'.
device. We will call our mapped device 'lukssdx2' (note that LUKS expects the
mapped device name to be in the format of "luks<rawdevname>"). It will be
available for use as the block device '/dev/mapper/lukssdx2', e.g. if the raw
device name is "/dev/sda2", then the mapped name will be "/dev/mapper/lukssda2".

# cryptsetup luksOpen /dev/sdx2 crypthome
# cryptsetup luksOpen /dev/sdx2 lukssdx2

* We've now finished our preparations, and it is time to start the 'setup'
program and install Slackware. This setup does not differ at all from the
setup you have become used to. The only notable difference lies in the
names of the devices you will select for your target partitions. Be sure
to read until the end of the story though, because we will have to do some
postprocessing in order to make your encrypted partitions available after
reboot (setup can not yet do all of this automatically).
reboot (setup cannot yet do all of this automatically).

* In setup, under "ADDSWAP", proceed as usual and configure a normal
unencrypted swap partition, even if you want to have your swap encrypted.
Expand All @@ -160,8 +162,8 @@ finishes.

* In setup, when you choose "TARGET" in the main menu, you will notice that
the mapped device is available in the 'Linux partition' selection as
"/dev/mapper/crypthome". Select the partition you designated for your
root ('/') filesystem, and next select "/dev/mapper/crypthome" for your
"/dev/mapper/lukssdx2". Select the partition you designated for your
root ('/') filesystem, and next select "/dev/mapper/lukssdx2" for your
'/home' filesystem. Create any filesystem you like on them. My favorite
fstype is ext4, but you can choose xfs or jfs for stability and speed.

Expand All @@ -179,14 +181,14 @@ it to the correct device name. The file '/etc/crypttab' contains lines of the
format: "mappedname devicename password options". Since we are still inside
the installer, the root filesystem of our fresh Slackware installation is
still mounted under '/mnt'. For our example where we encrypted '/dev/sdx2'
and mapped the unlocked device to '/dev/mapper/crypthome', we need this
and mapped the unlocked device to '/dev/mapper/lukssdx2', we need this
single line in '/etc/crypttab':

crypthome /dev/sdx2
lukssdx2 /dev/sdx2

So, we need to run the command:

# echo "crypthome /dev/sdx2" > /mnt/etc/crypttab
# echo "lukssdx2 /dev/sdx2" > /mnt/etc/crypttab

in order to create the file with the required content (I am assuming here
that the file did not yet exist... the above command will overwrite the
Expand Down Expand Up @@ -244,7 +246,7 @@ NOTE: the swap partition is encrypted with a new randomly generated key every
There is no need to ever enter a passphrase!

NOTE: having an encrypted swap like this causes a re-format of the swap
partition on avery boot-up and shutdown. This is perfectly OK as long
partition on every boot-up and shutdown. This is perfectly OK as long
as you do not change the order of your hard disks. If you add a disk,
or move this disk to another computer, the device name may change (for
instance from sda to sdb) and if you forget to modify '/etc/crypttab'
Expand Down Expand Up @@ -286,8 +288,8 @@ the /boot partition then.
* Perform a Slackware install just like I described above, creating
additional encrypted partitions and mapping them to appropriate names -
for this example I assume that you map the encrypted root partition
'/dev/sdx1' to 'cryptroot'. When the LILO configuration pops up, tell lilo
that your root partition is '/dev/mapper/cryptroot'. Lilo will try to
'/dev/sdx2' to 'lukssdx2'. When the LILO configuration pops up, tell lilo
that your root partition is '/dev/mapper/lukssdx2'. Lilo will try to
install and fail, and will tell you so. It will however have written a
'lilo.conf' file which we can edit in a follow-up action. Proceed with
the installation and at the end, exit the setup program but do _not_
Expand All @@ -311,7 +313,7 @@ image I assume that the root filesystem is 'ext4', we used the mapped device
and are running the Slackware 14.2 default SMP kernel '4.4.14-smp'
and we did not use Logical Volumes (more about that in the next section):

# mkinitrd -c -k 4.4.14-smp -m ext4 -f ext4 -r cryptroot -C /dev/sdx1
# mkinitrd -c -k 4.4.14-smp -m ext4 -f ext4 -r lukssdx2 -C /dev/sdx2

* The resulting initrd image will be written to the file '/boot/initrd.gz'
by default. We still need to tell lilo about this initrd. Open the
Expand All @@ -329,25 +331,25 @@ range of computers and that is why they are 'huge'. The linux part of

image = /boot/vmlinuz-generic-smp-4.4.14-smp
initrd = /boot/initrd.gz
root = /dev/mapper/cryptroot
root = /dev/mapper/lukssdx2
label = linux
read-only

If you add the above section as an extra instead of editing what's already
present, make sure that the label you use ('linux' in the example above)
is unique in the configuration file.

* If you have another OS on your computer and can not install lilo to the
* If you have another OS on your computer and cannot install lilo to the
MBR, you will have selected "Install to superblock (Root)" instead. In
that case, we have one additional change to make, and that is almost at the
top of the file. Look up the line that says "boot = /dev/mapper/cryptroot"
top of the file. Look up the line that says "boot = /dev/mapper/lukssdx2"
which is the device for your root partition and which was the reason for
lilo failing to install. Change the boot device to the name of the small
*unencrypted* partition you've created at the beginning and which is
mounted under '/boot'. Assuming the name of that partition is '/dev/sdx4',
mounted under '/boot'. Assuming the name of that partition is '/dev/sdx1',
the "boot =" line must become like this:

boot = /dev/sdx4
boot = /dev/sdx1

We are done. Write the changes, exit the editor and run the command 'lilo'.
Lilo will issue a couple of warnings concerning a difference in what
Expand Down Expand Up @@ -378,7 +380,7 @@ passphrase to unlock and allows for hibernation (suspend-to-disk).

We are assuming that Slackware will be the only Operating System on your
computer. In case you already have an OS installed (such as MS Windows), the
procedure may be a little different because you can not always install lilo to
procedure may be a little different because you cannot always install lilo to
the MBR. After booting from the Slackware installation medium, we will
create a small unencrypted partition that will contain the Linux kernels and
the initrd image(s). The rest of the disk's free space will be dedicated to
Expand Down Expand Up @@ -409,26 +411,22 @@ default cipher is 'aes', with mode 'cbc-essiv:sha256' which is safe enough.
which exposes the partition as an unencrypted block device. The command
will ask you for the passphrase which you entered during the "luksFormat"
operation. The last argument that the command takes is the name of the mapped
device. We will call our mapped device 'slackluks' because I am not feeling
original today. The mapped device which we will be using for unencrypted
operations will therefore be '/dev/mapper/slackluks'. However, note that the
installed system will name it 'lukssdx2' instead - it doesn't really matter
what you call it right now, but it's worth knowing for potential later
troubleshooting.
device. We will call our mapped device 'lukssdx2' because the installed
system will use that name (predictability is a good thing).

# cryptsetup luksOpen /dev/sdx2 slackluks
# cryptsetup luksOpen /dev/sdx2 lukssdx2

* The LVM part is next. Create a Physical Volume (PV) on device
'/dev/mapper/slackluks', a Volume Group (VG) called 'cryptvg' - any name will
'/dev/mapper/lukssdx2', a Volume Group (VG) called 'cryptvg' - any name will
do - on the PV, and three Logical Volumes (LV's) in the VG, one for your
root partition (7 GB in size), one for the /home partition (10 GB in size)
and a third which we will use for swap (1 GB in size). You will probably
use different sizes depending on your environment and wishes, but keep the
sum of the LV sizes less than the total size of the Physical Volume:

# pvcreate /dev/mapper/slackluks
# pvcreate /dev/mapper/lukssdx2

# vgcreate cryptvg /dev/mapper/slackluks
# vgcreate cryptvg /dev/mapper/lukssdx2

# lvcreate -L 7G -n root cryptvg

Expand Down Expand Up @@ -660,6 +658,8 @@ Good luck with your fresh Slackware installion on encrypted partition(s)!
==============================================================================
Author:
Eric Hameleers <[email protected]> 18-sep-2012
Edits by:
Robby Workman <[email protected]> 9 March 2017
URLs:
http://www.slackware.com/~alien/dokuwiki/doku.php?id=slackware:setup

Loading

0 comments on commit 646a5c1

Please sign in to comment.