-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 2019 Oct. 11. Dear Piz lifeboat occupants, This cookbook is a CORRECTED AND HAND-TESTED version of the 'dulap_construction_kit.txt' instruction posted on Oct. 10. Please do not use the earlier recipe -- it contained mistakes and omissions. It was physically verified on a 'AMD Dual-Core Zacate E350/E350D APU' machine on Oct. 11. This machine now contains a working 'dulap-gentoo'. - ---- Obtain a gentoo boot stick. Vintage is not known to matter, but the following: - ---- http://distfiles.gentoo.org/releases/amd64/20160704/livedvd-amd64-multilib-20160704.iso SHA512: 88fa7f2f700fac8caae2691b7797f80f5c47813f4b63b75cdeca6b7dcc8223c24b1e1a9ae7b57e4d86109716c2c638f5b9998ed385bb9f2528ef34bf02c8b115 - ---- ... item is known to work. Prepare a conventional gentoo boot USB from the above via, e.g. : dd if=livedvd-amd64-multilib-20160704.iso of=/dev/sdb bs=4 ... where e.g. /dev/sdb is an empty usb stick. Be careful not to overwrite your workstation's primary HDD! - ---- The following tarball : http://loper-os.org/pub/dulap.tar.gz SHA512 : fa425a03d38f09d3cdb4a6883547aef52e58dfa19123c2b6ba62471a03feda48a1a8c76008a4a524d916ead44bd571c21887c45570498eb5d44c069c59821523 contains a standard Dulap Gentoo kit, as prepared by myself for my own use. For those who require a machine with this kit, please follow the following instruction and ask as needed for assistance: 1A) Verify checksum. Place the tarball on a separate stick which you will be able to mount from within the chroot after 3-16B, e.g.: mount /dev/sdc /mnt/cdrom ... or wherever /dev/xxx it ends up when then plugged in. 1B) Ensure that you have a backup of your machine's current contents. If you make certain kinds of mistakes, you WILL nuke them. 2A) Obtain a suitable disk (100GB+) and a means of attaching to your machine. It is even possible to install to a usb stick, or a HDD on a usb snake, or the like. 2B) Ensure that 'LBA32' disk access mode is enabled in BIOS, if your machine is of a vintage where this is a selectable toggle. 2C) save the output of 'lsmod' and 'dmesg' commands for use in kernel config editing in step 3-20. On the 'E350' test bed machine (circa 2010), NO changes were required !! to the kernel config. 3) In a machine where said disk is installed, and running a e.g. boot stick linux, supposing the NEW disk being installed to is seen as /dev/sda : (if it is NOT 'sda', STOP and adjust your BIOS boot order until it is !) 3-1) parted -s /dev/sda mklabel gpt 3-2) parted -s -a optimal /dev/sda unit s mkpart boot ext3 64 262143 3-3) parted -s -a optimal /dev/sda unit s mkpart primary ext4 262144 100% 3-4) parted -s -a optimal /dev/sda set 1 boot on 3-5) sync 3-6) mkfs.ext3 /dev/sda1 3-7) mkfs.ext4 /dev/sda2 3-8) sync 3-10) mount /dev/sda2 /mnt/usb 3-11A) mount the tarball-containing usb stick (see 1A.) cd /mnt/whereyoumountedthetarballstick tar pxvfz dulap.tar.gz --strip-components=2 -C /mnt/usb (unpack the snapshot to the newly created root partition) 3-11B) sync 3-12) re-create the missing 'home' and 'root' directories: mkdir /mnt/usb/root mkdir /mnt/usb/home 3-13) /dev/sda1 will be your boot partition. there is a working kernel source in /usr/src/linux. 3-14) To create a bootable dulap-like: 3-15) mount /dev/sda1 /mnt/usb/boot (mounts the new boot partition.) 3-16) mount -o bind /dev /mnt/usb/dev mount -o bind /proc /mnt/usb/proc mount -o bind /sys /mnt/usb/sys chroot /mnt/usb /bin/bash You are now working from 'inside' the new userland. 3-17) edit /etc/conf.d/hostname and /etc/conf.d/net appropriately, to get the thing onto your LAN when it boots up. The latter, e.g.: config_eth0="10.0.0.254 netmask 255.255.255.0" routes_eth0="default via 10.0.0.1" dns_servers_eth0="8.8.8.8" # public toilet, or replace with isp's The former, e.g. : hostname="dulap" 3-18) edit /etc/fstab and change the 'reiserfs' of /dev/sda2 to ext4. This assumes that you chose ext4 in step 3-3 and 3-7 , it is possible to use another FS if you so wish. 3-19) edit /etc/portage/make.conf and where : MAKEOPTS="-j24" ... replace the 24 with 1+your cpu count. 3-20) cd /usr/src/linux genkernel --no-zfs --menuconfig all Make modifications to config as required. Then exit, and let it build and install the kernel. This may take an hour or longer on a very slow box with few CPU cores (see prev. step.) 3-21) You will need bootloader. There is a lilo.conf in /etc. Please adjust as required for your iron and kernel image names. If your disk being installed to is 'sda', no changes are required. 3-22) Run 'lilo' as root. This will make the gentoo bootable. Optionally you may use 'grub' bootloader. In which case must write own config. 3-23) Use 'passwd' command to set a root password. 3-24) Exit the chroot and attempt to boot machine via the newly-prepared disk. 3-25) If your machine configuration differs substantially from the original's, you may encounter a problem booting. Do not hesitate to ask for help. 3-26) Create user accounts. 3-27) You will be initially able to SSH to this machine as 'root'. Disable remote passworded login, and regen the machine's SSH host keys (see gentoo docs, this is beyong the scope of this cookbook.) Please ask me for assistance if needed. Yours, - -S -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBCgAGBQJdoT37AAoJELmCKKABq//He+sH/2pGwICZk6r6nmm27LKfPmsd tkkaDMwjK59HTnV7pnvMWPavfXwz7efKKQiYuR2bcgv188HOEnzRKPKI+1zmtmgu ZO4z2UT2DBa/G8M1tpvEnZPL/YDQE1EX4BCT7UpgclSvKlzlCcUiFI7af99cumxs /DuS5PEqwUBKDfwldpYO72RDvXY5/GuU+BeSgcAwtim3lM3PUuR6+z4kYVpzKU9Q LlDpZdGWRO8Xk8kq7jEW51NvHDKL+cTHhwMsarKmVYMdoVC//z2fnUE8PgJ8bvYY YpM4os4bn//0RwA8p23yk/moEveHmuhfS+eG/Xqp1A8n4N+1e4yILxUZQ7Y/alg= =I7tS -----END PGP SIGNATURE-----