Talk:Installation alternatives

Note
Before creating a discussion or leaving a comment, please read about using talk pages. To create a new discussion, click here. Comments on an existing discussion should be signed using ~~~~:

A comment [[User:Larry|Larry]] 13:52, 13 May 2024 (UTC)
: A reply [[User:Sally|Sally]] 13:41, 5 November 2024 (UTC)
:: Your reply ~~~~

Parted resize command

Talk status

This discussion is done as of 2022-02-22.

Parted resize command has been removed since version 2.4. Currently there are no prior version in the Gentoo repository. Should we remove the whole "Building parted to resize partition" section? I just need some feedback before making such a disruptive edit. Fturco (talk) 18:32, 21 May 2017 (UTC)

Parted just renamed resize to resizepart. I don't see why there floppy disk involvement, this part largely outdated. Rewrote section for more recent version. --Winterheart (talk) 20:35, 22 June 2020 (UTC)

Netboot PXE

Talk status

This discussion is still ongoing as of 2018-01-01.

Happy New Year!

The LiveCD patch is still working over the years; only a 3-line displacement from the original! :D I used it today to install on my PC when the USB stick failed to get into the kernel insides. My experience with this wiki section inspired some changes.

The LiveCD patcher has universal script that can support different PXE implementations. I abstracted it out so you can run the base LiveCD patcher for whatever flavor of PXE you're trying to support. After the base patch, sections are broken up by flavor of PXE ala Grub and iPXE for starters.

The CD Patcher now ensures you have root privileges via the "base-installed" coreutils `id -u` rather than half-successfully executing the script and failing awkwardly if not root (eg via sudo).

Script status reports rather than line-by-line program echoing are friendlier as a general user script I think. It can be confusing reading the output sometimes because of the `-e` flag in the bash shebang (#!/bin/bash -xe). I thought about replacing that behavior with status reports that printed as the script progressed, but I will not risk insulting the original programmer.

The sections have been reordered so that the user first learns how to emerge the tftp server (and learn how to configure it) before sending files to the tftproot.

There's more work to be done on explaining the TFTP server setup. It's rather bare.

Same goes for the DHCP server setup.

iPXE section needs coverage but I "peaked" before getting to it. The alternative iPXE-without-server setup will be an approachable section for beginners of PXE who can't accomplish the relatively complicated setup PXE requires. For instance, a user could host the images on a HTTP server (even over the WWW), and boot iPXE directly to them without need for self-run TFTP and DHCP servers.

Is it known whether the LiveCD patcher works with the LiveDVD? Please update wiki with the answer.

\0/ Larry wishes you lots of love for 2018! \0/

 Larry loves Gentoo (Linux)

_______________________
Have you mooed today?
-----------------------
         \   ^__^
          \  (oo)\_______
             (__)\       )\/\\
               ||----w |
               ||     ||

Bazz (talk) 01:03, 1 January 2018 (UTC)

Remove patch and simplify scripts?

Talk status

This discussion is still ongoing as of 2021-07-19.

I would like to change the whole Netboot section, no actual patching is needed, only combine gentoo.igz and image.squashfs (with cpio header) and it is bootable as is, and at the same time remove initial NFS mention. My suggestion is something like:

CODE

mkdir -p /tftpboot/gentoo/
cd /tftpboot/gentoo/
emerge -uv1 app-cdr/cdrtools
isoname=/tftpboot/ISO-IMAGES/install-amd64-minimal-20210725T170534Z.iso
isoinfo -R -i ${isoname} -X -find -path /boot/gentoo && mv boot/gentoo kernel && rmdir boot
isoinfo -R -i ${isoname} -X -find -path /image.squashfs
# combine initrd + squashfs
(isoinfo -R -i ${isoname} -x /boot/gentoo.igz; (echo image.squashfs | cpio -H newc -o)) > network.igz && rm image.squashfs
ls -lhF kernel network.igz

Also trying to keep iPXE script up2date. Currently trying to work on and get releng team to distribute the needed files so it can be loaded over http - but it is on a "as time permits" basis. I have some PoCs up on github (and local server) using iPXE, not sure if it is ok to "promote" that? and then there is also netboot.xyz that now should have working support for Gentoo using same method.

--NiKiZe (talk) 15:34, 19 July 2021 (UTC)

Above tested with iPXE and PXELINUX in pcbios mode, grub pains me, non bootable in pcbios mode, and efi gives "error: timeout reading 'combined.igz'". This is probably all issues that could be solved by using recent versions of the programs. IMO iPXE using http is the best approach here, working in both pcbios and efi mode, downside being signing of EFI, but kernel is not signed anyway. --NiKiZe (talk) 13:41, 23 July 2021 (UTC)

Decided to do the above mentioned change after testing newer versions of grub and getting report of working: https://forums.gentoo.org/viewtopic-p-8636881.html#8636881 as well as cleaning up the script a bit as mentioned in earlier edit. Still trying to work on official mirror hosting in https://bugs.gentoo.org/494300#c4. Will also try to improve both TFTP and DHCP sections if I can find the time.

--NiKiZe (talk) 09:05, 29 July 2021 (UTC)

For anyone wondering the back and forth on the CodeBox is my original misstake, it is not meant to be typed out, and a CmdBox makes it difficult to copy.

--NiKiZe (talk) 21:36, 9 August 2021 (UTC)

pxe-craft-initrd-kernel script needs updating

Talk status

This discussion is still ongoing as of 2018-07-18.

The bash script given for generating kernel and initrd files from the minimal install ISO image is out of date.

Specifically, in the patching section wherever you've got

if [ /dev/nfs != "$REAL_ROOT" ] && [ sgimips != "$LOOPTYPE" ] && [ 1 != "$aufs" ]; then

Instead it needs to read

if [ /dev/nfs != "$REAL_ROOT" ] && [ sgimips != "$LOOPTYPE" ] && [ 1 != "$aufs" ] && [ 1 != "$overlayfs" ]; then

After making that change, the script worked for me.

While you're at it, suggest changing the usage output toward the beginning to reflect the intended name of the file. --Jlhubbs (talk) 20:46, 18 July 2018 (UTC)

CodeBox vs RootCmd

Talk status

This discussion is done as of 2022-02-22.

I would like to ask Matthew Marchese (Maffblaster) to resolve this issue arbitrarily before this becomes an edit war. Christian Nilsson (‪NiKiZe) believes a Template:CodeBox is in order when I believe that Template:RootCmd is correct. Before there are bad feelings all around, more perspective is needed. --Grknight (talk) 12:33, 10 August 2021 (UTC)

Brian Evans (Grknight) and Christian Nilsson (‪NiKiZe) , "Code" vs "Command" is sort of a matter of semantics I guess. Both are true... bash can be code and code can be bash. But in terms of our wiki Guidelines, if the content in the CodeBox (in this section) is supposed to be a script, then use the FileBox template should be used with appropriate example file name and lang=bash. The content is supposed to be entered into a root prompt in a multi-command sequence (not scripted), then the RootCmd should be used. Hope this helps. --Maffblaster (talk) 19:57, 10 August 2021 (UTC)