-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 2019 Oct. 12. Dear Piz lifeboat occupants, This cookbook is a CORRECTED AND HAND-TESTED version of the 'dulap_construction_kit_r2.txt' instruction posted on Oct. 11. Please do not use the earlier recipes. 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-r2.tar.gz SHA512 : 51b339fd922497bbd11abc38375b54beb01a9737af55dd4114c328023927ce07e2bd90a6c9b1a3f793b862dc951b0ae438bfd3591c295254982c880c89190787 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 these instructions 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-11) 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-12) sync 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/portage/make.conf and where : MAKEOPTS="-j24" ... replace the 24 with 1+your cpu count. 3-19) 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.) If you have e.g. FG, be sure to enable 'usb serial' in the kernel, for the particular cable(s) you own. 3-20) 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-21) Run 'lilo' as root. This will make the gentoo bootable. Optionally you may use 'grub' bootloader. In which case must write own config. 3-22) Use 'passwd' command to set a root password. 3-23) Exit the chroot and attempt to boot machine via the newly-prepared disk. 3-24) If your machine configuration differs substantially from the original's, you may encounter a problem booting. Do not hesitate to ask for help. 3-25) Create user accounts. 3-26) 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) iQEcBAEBCgAGBQJdoeqvAAoJELmCKKABq//HoRIH/jjFu1SU/4Tb2ngDselOk9Mw Vw5O9PHsij3JPGsvsOE7i9+1aVYwavHi2F4M+ty3k3KcU4hPPtKg22J8aAAZAXmS sT3pkhTdXT9d1nMfJ3ZfvIwadUPxDlHFG+UoL8ze4HyTCpyD0o/b72XalVJFuXaj A3/Yj5SQzA1Gr7nDiwYYYu3fjQow0e8ioM9hK88Ll9ZHFO3+lV2xlYrZBSm38aFB dAuhPvUIKy1Fj+CkKxtPWtnMEqh6gLETyxBpgbQn1DuCFH3aM7MiLBMRGaK9lSUo 6fFZSXjuFjJ2RGZ/kbJ7+dGJgWJz4k9OAKV2PZpOh2O93njVEUVqRL1fCxpQkuE= =548n -----END PGP SIGNATURE-----