exec switch_root /mnt/root /sbin/init || rescue_shell umount /proc umount /sys umount /mnt/usb # Boot the real thing. cryptsetup create -cipher aes-xts-plain64 -key-file /mnt/usb/keyfile cryptmd1 /dev/md1 #sleep 2 lvm vgchange -ay || rescue_shell lvm vgscan -mknodes > /dev/null 2>&1 mount -o ro /dev/mapper/vg-root /mnt/root || rescue_shell # Clean up. mdadm -As sleep 2 mount LABEL=Keyfile /mnt/usb || rescue_shell #The label is an ext filesystem label, not the label of the partition. mount -t proc none /proc mount -t sysfs none /sys mount -t devtmpfs none /dev #load_modules || rescue_shell #The kernel was made with the essential modules so that the initramfs does not need to be rebuilt every time with a new kernel. #!/bin/busybox sh #load_modules() # Mount the /proc and /sys filesystems. Gentoo will be installed on the following stack Except, /dev/sda2 is used to store bootable ISOs and /dev/sdb2 is swap. Both disks are partitioned about the same. The dm-crypt is put onto a /dev/md1 RAID 1 device, just to add a little protection from disk failure. The physical volume is therefore a dm-crypt device. I don't want my data to go wandering through physical theft or disk RMA's. There doesn't seem much point in containerising the operating system without putting them in containers, so everything, including root, is put into a logical volume. Also networking under LXC is more flexible. The change was undertaken because one is not in the kernel, whereas the other is.
This latest incarnation of the server is a migration from vserver to LXC. Ext4 was chosen as its recent and current. Gentoo was chosen because maintenance is tremendous. The document describes a server built for home use. Accordingly it is written in first person. This is a "how I did it", not a "how to".
0 kommentar(er)
