Examine individual changes
From Gentoo Wiki
This page allows you to examine the variables generated by the Abuse Filter for an individual change, and test it against filters.
Variables generated for this change
| Variable | Value |
|---|---|
Edit count of the user (user_editcount) | 80 |
Name of the user account (user_name) | 'Glibg10b' |
Age of the user account (user_age) | 75414131 |
Page ID (page_id) | 312518 |
Page namespace (page_namespace) | 561 |
Page title (without namespace) (page_title) | 'AMD64/Full/Installation/Archive' |
Full page title (page_prefixedtitle) | 'Handbook Talk:AMD64/Full/Installation/Archive' |
Action (action) | 'edit' |
Edit summary/reason (summary) | '/* improve suggested partitions and use of grub-install */ Move from Handbook_Talk:AMD64/Full/Installation' |
Old content model (old_content_model) | 'wikitext' |
New content model (new_content_model) | 'wikitext' |
Old page wikitext, before the edit (old_wikitext) | 'The following sections are [[Article description::completed discussions previously found on the [[Handbook Talk:AMD64/Full/Installation]] page.]] They have been moved here for archival purposes.
== 5.4 Viewing Documentation During Install ==
{{Talk|done}}
The documentation recommends creating a new user account and logging in on a separate virtual tty to load links with the install docs, then switching back and forth between a command tty and the docs tty. This will work but it's clumsy, slow, and aggravating. A better solution is to use "screen" which is already included on the minimal install CD. The docs can be viewed side-by-side with one or more command shells on the same terminal with the following commands:
* screen links Gentoo.org
* ^A ^C
* ^A | (for vertical split) or ^A S (for horizontal split)
Each "screen" can be split further into more windows. I would suggest including these instructions in the install docs in addition to or instead of the virtual terminal switching method.
{{Unsigned|Handle2001|21 July 2016}}
: I can make mention of this as an option and add a link to our article on [[Screen]], although I would not summarize logging in on multiple tty's "clumsy, slow, and aggravating". It is the simplest way of proceeding. Screen takes knowledge that many newcomers many not immediately possess. Seasoned system admins will probably think of using screen without it being mentioned. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 22:08, 26 January 2017 (UTC)
:: It is now mentioned as a possibility for seasoned Linux enthusiasts (who know how to use it). Closing discussion. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 22:59, 26 January 2017 (UTC)
== Choosing the right profile ==
{{Talk|done}}
While not a recommendation, this section suggests using "no-multilib" for a pure 64-bit environment. I think this should be followed by the disclaimer on the AMD64 FAQ:
{{Warning|Switching from a no-multilib to a multilib-enabled profile is currently not supported ([http://jkroon.blogs.uls.co.za/it/gentoo/gentoo-converting-no-multilib-to-multilib conversion hints]), so think over your decision twice before you use the no-multilib profile.}}
--[[User:Astronome|Astronome]] ([[User talk:Astronome|talk]]) 23:29, 6 February 2016 (UTC)
: I added [[Handbook:AMD64/Full/Installation#No-multilib_.28pure_64-bit.29|a small section]] noting the caveats of no-multilib. Should be better now. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 18:20, 13 January 2017 (UTC)
== Optional: Selecting mirrors ==
{{Talk|done}}
If you use >=sys-apps/portage-2.2.16, you not have to use
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>mirrorselect -i -r -o >> /mnt/gentoo/etc/portage/make.conf</code></div></div>
As, the SYNC variable in make.conf is deprecated and no longer used by portage.<br>
You will should use
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>mkdir /mnt/gentoo/etc/portage/repos.conf</code></div></div>
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>cp /usr/share/portage/config/repos.conf /mnt/gentoo/etc/portage/repos.conf/gentoo.conf</code></div></div>
If you want to be updated from other mirror, you can run
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>mirrorselect -i -r -o</code></div></div>
select mirror and paste received URI here /mnt/gentoo/etc/portage/repos.conf/gentoo.conf in variable "sync-uri" <br>
example:<br>
sync-uri = rsync://rsync.ru.gentoo.org/gentoo-portage
More info {{Link|Project:Portage/Sync}} <br><br>
P.S. Sorry my bad english.
{{Unsigned|Geronek|26 April 2015}}
: The repos.conf method is [[Handbook:AMD64/Full/Installation#Main_Gentoo_repository|now explained]] in the Handbook. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 18:22, 13 January 2017 (UTC)
== Unpacking the stage tarball ==
{{Talk|done}}
Is "--xattrs" required on some versions of tar to keep the extended attributes when extracting the archive or is this a mistake and as the manpage says, is only used to "save the user/root xattrs to the archive" (while when extracting, one would have to specify "--no-xattrs" to bypass them). {{Unsigned|Lepaperwan|1 November 2015}}
: Where do you see that in the GNU tar man page? Seems like bad information to me. I tested your theory using tar v1.29 and verified the <code>--xattrs</code> option must be added both for compression and extraction in order for {{c|tar}} handle extended attributes properly. See [http://www.lesbonscomptes.com/pages/extattrs.html#_archiving_and_backup this link] for someone else who tested. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 06:27, 24 January 2017 (UTC)
== Setting the date and time ==
{{Talk|done}}
Is there a reason Handbook doesn't suggest "ntpdate pool.ntp.org" instead of typing date manually? {{Unsigned|Vkuzkokov|7 March 2015}}
: It is less thinking and more accurate to use ntpd. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 18:23, 13 January 2017 (UTC)
== Typo "there are e a" ==
{{Talk|done}}
There's an apparent typo on a whole series of these wiki pages.
I created and validated wiki account for myself, but alas, it doesn't (yet) give me the option to edit the pages - so apparently I can't correct it.
Anyway, the error:
"there are e a couple"
should apparently be:
"there are a couple"
on at least these pages:
{{CodeBox|title=List of pages with typo in them|1=
{{Link|Handbook:AMD64/Full/Installation}}
{{Link|Handbook:AMD64/Installation/Stage}}
{{Link|Handbook:Alpha/Full/Installation}}
{{Link|Handbook:Alpha/Full/Installation/es}}
{{Link|Handbook:Alpha/Installation/Stage}}
{{Link|Handbook:HPPA/Full/Installation}}
{{Link|Handbook:HPPA/Full/Installation/es}}
{{Link|Handbook:HPPA/Installation/Stage}}
{{Link|Handbook:IA64/Full/Installation}}
{{Link|Handbook:IA64/Full/Installation/es}}
{{Link|Handbook:IA64/Installation/Stage}}
{{Link|Handbook:MIPS/Full/Installation}}
{{Link|Handbook:MIPS/Installation/Stage}}
{{Link|Handbook:PPC/Full/Installation}}
{{Link|Handbook:PPC/Full/Installation/es}}
{{Link|Handbook:PPC/Installation/Stage}}
{{Link|Handbook:PPC64/Full/Installation}}
{{Link|Handbook:PPC64/Full/Installation/es}}
{{Link|Handbook:PPC64/Installation/Stage}}
{{Link|Handbook:Parts/Full/Installation}}
{{Link|Handbook:Parts/Installation/Stage}}
{{Link|Handbook:SPARC/Full/Installation}}
{{Link|Handbook:SPARC/Full/Installation/es}}
{{Link|Handbook:SPARC/Installation/Stage}}
{{Link|Handbook:X86/Full/Installation}}
{{Link|Handbook:X86/Installation/Stage}}
{{Link|Handbook:X86/Installation/Stage/es}}
}}
'''(Above posted by Michael Paoli, fixed for wikification)'''
: Thanks, corrected. --[[User:SwifT|SwifT]] ([[User talk:SwifT|talk]]) 14:41, 27 December 2014 (UTC)
== systemd needed for Banshee Too! ==
{{talk|done}}
About the optional systemd and Gnome, could you mention that systemd is also required for programs like Banshee that highly depend on Gnome architecture.
<small>— The preceding [[Help:Signatures|unsigned]] comment was added by [[User:Gary987|Gary987]] ([[User talk:Gary987|talk]] • [[Special:Contributions/Gary987|contribs]]) 12 May 2015</small>
: It would seem Banshee is no longer available in the main ebuild repository, however I get the point. I have made a note of this in the Handbook's systemd section ({{Link|Handbook:Parts/Blocks/Systemd}}). Thanks for the tip! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 03:32, 5 March 2017 (UTC)
== 404 link on Introduction ==
{{Talk|done}}
The link to the Gentoo AMD64 project site (https://www.gentoo.org/proj/en/base/amd64/), on the Hardware Requirements section of the Introduction, leads to a 404 error. {{Unsigned|Rrzippert|3 August 2015}}
: Link has been long since fixed. Thanks! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 22:28, 13 January 2017 (UTC)
== Minor typo & systemd creep ==
{{Talk|done}}
Correct "on a amd64" to "on an amd64" if possible.
I'm here to do a clean openRC installation. Let's keep systemd in check.
The "--make-rslave" operation creeps in without mention of it being optional, if it is, and without yet mention that it is because of systemd.
If these operations are unnecessary without systemd, then please move the "--make-rslave" operations into, and/or under, the note. For example:
'''Note'''<br>
The --make-rslave operations are needed for systemd support later in the installation.
<pre>
root #mount --make-rslave /mnt/gentoo/sys
root #mount --make-rslave /mnt/gentoo/dev
</pre>
: It is in intention to support systemd as an ''optional'' init system. systemd is probably, at the time of writing, the ''most popular'' system in existence, although the majority of Gentoo users probably are not using it. The <code>--make-rslave</code> option passed to {{c|mount}} does not conflict with any options needed for those choosing either init system (OpenRC or systemd), and therefore is fine either way. Typos are corrected by now. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 01:34, 17 January 2017 (UTC)
== Re: Banshee ==
{{Talk|done}}
Banshee is software that is loaded with commercial interests, namely Amazon.com. If it has dependency issues then those should be dealt with at the Banshee development site, not here.
: Agreed. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 01:35, 17 January 2017 (UTC)
== Configuring the network ==
{{Talk|done}}
The Handbook heavily relies on the assumption that the network interface name is eth0, which is highly unlikely with the new udev naming rules.
Recommending the use of
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>ip link show up</code></div></div>
from a Gentoo-based installation medium or
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>udevadm test-builtin net_id /sys/class/net/eth0 2> /dev/null</code></div></div>
if coming from a different installation medium would allow users still unfamiliar with Gentoo to avoid errors during setup.
{{Unsigned|Lepaperwan|1 November 2015}}
: Agreed...I solved this by simply running
: {{RootCmd|touch /etc/udev/rules.d/80-net-name-slot.rules}}
: Likely works for 95% of all users with a single network card that doesn't change slots
:: For the purposes of the Handbook, it shouldn't matter what the network interface is named. It's just a handle created by udev. The Handbook [[Handbook:AMD64/Full/Installation#ip_command|does mention]] the {{c|ip}} command now. I'm not sure what the point of using {{c|udevadm}} would get the readers? If you still feel like there's more to this discussion then re-open it. Seems like we covered all the bases. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 06:36, 24 January 2017 (UTC)
== Installing the sources ==
{{Talk|done}}
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>emerge --ask sys-kernel/gentoo-sources</code></div></div>
This command execution recommends to control its status in another terminal by doing:
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>tail -f /var/log/emerge-fetch.log</code></div></div>
But we have previously chrooted into /mnt/gentoo/. So I suggest to specify that if we log into another terminal we should tail the file inside the mounted folder by doing:
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>tail -f /mnt/gentoo/var/log/emerge-fetch.log</code></div></div>
: Hi, I don't think instructions on how to {{c|tail}} the {{Path|emerge-fetch.log}} file needs to be mentioned in the Handbook. Hopefully the reader will be able to figure this out on their own by reading the message from the gentoo-sources ebuild. If you'd like to re-open and write up a mock wording for me to copy/paste into the Handbook I will consider it! Kind regards, --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 06:40, 24 January 2017 (UTC)
== Kernel config for USB support ==
{{Talk|done}}
This section is out of date:
{{KernelBox|title=Activating USB Support for input devices|<pre>
Device Drivers --->
[*] HID Devices --->
<*> USB Human Interface Device (full HID) support
</pre>}}
I believe the relevant options have been moved to:
{{KernelBox|title=Activating USB Support for input devices|<pre>
Device Drivers --->
HID support --->
-*- HID bus support
USB HID support --->
<*> USB HID transport layer
[*] USB support --->
Select relevant USB drivers
</pre>}}
--[[User:Astronome|Astronome]] ([[User talk:Astronome|talk]]) 19:35, 20 July 2016 (UTC)
: Hi {{U|Astronome}}, Thanks for the tip, and you are correct the example used in the Handbooks is certainly out of date! I have updated it! Thank you kindly for the productive feedback. Cheers, --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 04:31, 5 March 2017 (UTC)
== Kernel config for efi stub ==
{{Talk|done}}
Please edit configuration of kernel for efi support, else kernel not load a root file system.
{{KernelBox|title=Enable built-in kernel parameters|1=
Processor type and features --->
[*] Built-in kernel command line
(root=/dev/sda2 rw)
}}
: The [[Project:Handbook|Handbook]] team is trying to move away from supporting the UEFI stub kernel functionality as it is less flexible than using a bootloader to load the kernel into memory. That kind of of stuff can be ''left out'' of the Handbook and be included in other kernel related articles around the wiki. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 21:13, 13 January 2017 (UTC)
== Link to "other arches" on download page ==
{{Talk|done}}
In the "[[Handbook:AMD64/Full/Installation#Download the media|Download the media]]" section which discusses the "minimal installation CDs", the link to "the [//www.gentoo.org/downloads/#other-arches downloads page] (recommended)" is to the "Advanced Choices and other Architectures" section of that page. Shouldn't it be to the top of the page (no section anchor) where links to download the "normal" amd64 Minimal Installation CD, LiveDVD, and Stage 3 files are to be found? - [[User:Dcljr|dcljr]] ([[User talk:Dcljr|talk]]) 18:32, 13 April 2016 (UTC)
: The link has been updated. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 21:14, 13 January 2017 (UTC)
== Remove Parted ==
{{Talk|done}}
Remove Parted from handbook! fdisk have support GPT layout, and part of coreutils (default)
: I need to revise the disk section. I'll add this as a ''possibility'' to review. After reworking the disk section it parted may or may not be used. That's all I can say for now. Thanks! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 18:28, 13 January 2017 (UTC)
: I don't see why parted should be removed if it *works great*. --[[User:Vieri|Vieri]] ([[User talk:Vieri|talk]]) 12:12, 17 February 2017 (UTC)
== EFI partition mount ==
{{Talk|done|date=Jan 13th 2017}}
I see the Handbook mentions that Grub2 can't be used, and efibootmgr should be used instead. However, using grub2 is a suitable option.
The EFI partition should be mounted to /boot/efi:
# mkdir /mnt/gentoo/boot/efi
# mount /dev/sda1 /mnt/gentoo/boot/efi
[[User:ILMostro|ILMostro]] ([[User talk:ILMostro|talk]])
: Hi {{U|ILMostro}}, I saw your message in IRC. We are still very much active in monitoring and updating the wiki, although we're not always able to immediately respond on IRC. I agree, GRUB2 is a suitable option for EFI on Gentoo. I use it myself. With that being said we have to be careful with how much we try to support in the various handbooks. The purpose of it is to help users get Gentoo installed; not to walk them through all the configuration options (Gentoo is far too flexible for that!). :)
: I don't remember the Handbook ever saying GRUB2 can't be used for EFI on {{Keyword|amd64}} systems, but I will take a look and fix anything that doesn't seem right. Kind regards, --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 02:05, 21 June 2016 (UTC)
== GPT or MBR ==
{{Talk|closed|date=2022-02-22}}
It's definitely possible to dual-boot with Windows using GPT on a BIOS-based system. I'm able to do so with the following GRUB entry:
{{FileBox|filename=/etc/grub.d/40_custom|title=Dual-boot with Windows|<pre>
menuentry "Windows 10" {
insmod ntfs
insmod ntldr
insmod part_msdos
insmod search_fs_uuid
search --no-floppy --fs-uuid --set=root 1AECC5A1ECC57811
ntldr /bootmgr
}
</pre>}}
--[[User:Astronome|Astronome]] ([[User talk:Astronome|talk]]) 03:17, 21 January 2017 (UTC)
: Hi Astronome, if you're serious about having your discussions looked after please remember to use the {{Tl|Talk}} template. We can't really track what work is left for us to do without them.
: With that being said, to confirm: does the disk have a GPT partition table, or is it an MSDOS table? Also, is your copy of Windows installed in MSDOS mode? Kind regards, --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 06:47, 24 January 2017 (UTC)
: Revisiting here... Closing discussion due to no reply from author. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 08:50, 22 February 2022 (UTC)
== Mounting the necessary filesystems ==
{{Talk|done|date=Jan 26th 2017}}
I've always found this part confusing. Should this
{{RootCmd|mount -t proc proc /mnt/gentoo/proc}}
be changed to this?
{{RootCmd|mount -t proc /proc /mnt/gentoo/proc}}
Otherwise, if you're following the instructions exactly, your PWD will be {{Path|/mnt/gentoo}} and you'll be mounting {{Path|/mnt/gentoo/proc}} to itself. --[[User:Astronome|Astronome]] ([[User talk:Astronome|talk]]) 19:55, 21 January 2017 (UTC)
: Yes, it's a good point. We should have the {{Path|/}} on the second mention of proc. I'll update this. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 06:47, 24 January 2017 (UTC)
:: This assertion is wrong (but doesn't hurt). man mount:
::''The proc filesystem is not associated with a special device, and when mounting it, an arbitrary keyword, such as proc can be used instead of a device specification. (The customary choice none is less fortunate: the error message `none busy' from umount can be confusing.).''
::It was probably "proc" due to it being suggested to use that in the man page as that arbitrary keyword (but you can use "asdf" or whatever, pretty much anything except for "none'). That argument is the first one - that of the device node to use, -t proc doesn't have one, so it's ignored (unless special "none" is encountered). In "mount -t proc proc /mnt/gentoo/proc" the first "proc" is the type given with -t, "proc" is the device node and /mnt/gentoo/proc is the path - there is no proc path and no way this would have mounted itself (device node != directory). --[[User:Leio|Leio]] ([[User talk:Leio|talk]]) 15:26, 26 January 2017 (UTC)
::: That's funny, I was editing this page at the same time as you to say the same thing :) --[[User:Astronome|Astronome]] ([[User talk:Astronome|talk]]) 15:52, 26 January 2017 (UTC)
:::: So it doesn't really matter. It could be <code>proc</code> or it could be <code>/proc</code>. {{c|mount}} doesn't care. If there's nothing left to do here please close this discussion. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 21:52, 26 January 2017 (UTC)
:::: Well fine. --[[User:Astronome|Astronome]] ([[User talk:Astronome|talk]]) 02:29, 27 January 2017 (UTC)
== GPG verification when behind a firewall ==
{{Talk|done}}
If the default gpg port cannot be opened in the firewall then you might want to use something like:
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>gpg --keyserver hkp://hkps.pool.sks-keyservers.net:80 --recv-keys 0xBB572E0E2D182910</code></div></div>
BTW the user can also specify any other keyserver such as:
hkp://keyserver.ubuntu.com:80
This may be useful when some servers don't respond.
The following handbook section could be updated to reflect this:
{{Link|Handbook:AMD64/Full/Installation#Linux_based_verification}}
--[[User:Vieri|Vieri]] ([[User talk:Vieri|talk]]) 16 February 2017
: Hi {{U|Vieri}}, I'm rocking {{c|gpg}} version 2.1.19 and it would seem the syntax you used to specify a specific port has been deprecated. I couldn't get it to work by trying your example above. Also, from the man page ({{c|man 1 gpg}}), "The scheme is the type of keyserver: "hkp" for the HTTP (or compatible) keyservers". This indicates to me that HTTP is the default, so there is no need to specify port 80 in the example... Kind regards, --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 03:59, 5 March 2017 (UTC)
:: No, hkp uses port 11371 by default. What the OP neglected to mention is that not all keyservers support port 80. The general solution is to use the p80 pool at <code>hkp://p80.pool.sks-keyservers.net:80</code>. However, I think that it would be more preferable still to use the hkps pool at <code>hkps://hkps.pool.sks-keyservers.net</code>. This has the advantage of using HTTPS on the standard port of 443. Incidentally, portage and gemato are both inflexible in this regard. --[[User:kerframil|kerframil]] ([[User talk:kerframil|talk]]) 02:36, 21 July 2018 (UTC)
::: Thanks, added that URI. --[[User:Grknight|Grknight]] ([[User talk:Grknight|talk]]) 15:30, 7 November 2018 (UTC)
== DavidC improvements section ==
As I'm reading through this doco I'm writing a bunch of suggestions, some of which are sure to be misguided, so the only discussion I require is "yes/no/maybe later". Hopefully some of this helps but I know not all of it will be implemented.
=== Preparing the disk ===
{{Talk|done|2024-04-01}}
Prior to "Introduction to block devices" it would be nice if there was a title that said something like preparing the disk, since that is what is referred to above in the document. [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 17:57, 18 November 2017 (UTC)
: This would require a significant amount of work. It would require a lower-level heading than the one used for "Introduction to block devices" and subsequent sections. Since there is none, the headings for all sections on the page would have to be shifted up one level, but that change would automatically get copied to the non-full installation parts of the handbook (e.g. {{Link|Handbook:AMD64/Installation/Disks}}).
:
: The non-full installation parts should get priority since {{Handbook:AMD64}} takes the user there. Thus, taking no action is the best option here.
:
: I'm closing this discussion since I don't know whether you will respond. If you do, feel free to reopen it. [[User:Glibg10b|Glibg10b]] ([[User talk:Glibg10b|talk]]) 07:39, 1 April 2024 (UTC)
=== Open more than one chroot terminal ===
{{Talk|closed|date=October 29th, 2021}}
I'd probably get the user to chroot a couple terminals at least because then they would be able to do some reading while something is going on it another window, or easily compare say the output of lspci to what they're inputting in makeconfig, etc. [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 15:13, 19 November 2017 (UTC)
We mention screen for this purpose, but I have also have added a tip to explictly show readers how to switch between the seven available terminals: [[Special:Diff/1015767/024956]]. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 20:35, 29 October 2021 (UTC)
=== This and that ===
{{Talk|closed|date=2024-02-14}}
I am lost at [[Handbook:AMD64/Full/Installation#Introduction_to_block_devices]]. Looking at "If that is the case, it might be..." I understand what "that" case is, but when it says "In this case, launch..." I do not understand what "this" case is. Perhaps after "using the MBR format." A sentence could be added directing MBR users to "Default partitioning scheme". Someone suggested this be split into 3 sections "bios with mbr, efi with gpt, bios with gpt" [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 19:37, 18 November 2017 (UTC)
=== I am overwhelmed with mirrors ===
{{Talk|closed|date=October 29th, 2021}}
"links https://www.gentoo.org/downloads/mirrors/" So if you follow the first link for Canadians, you end up going to a LONG list of files and it's not entirely clear what to download (even if you follow it all the way to Gentoo, so it's probably best just to link people straight to https://gentoo.org/downloads/. [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 19:58, 18 November 2017 (UTC)
: If you are referring this section, there are no instructions to download anything from the mirrors directly. It's just giving an example on how to use links to determine what mirror URLs are avaialble. No where in the instruction are you supposed to download anything in this section. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 20:35, 29 October 2021 (UTC)
=== Variables ===
{{Talk|closed|date=October 29th, 2021}}
"variables which impacts" --> "impact" [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 20:02, 18 November 2017 (UTC)
: Fixed. See [[Special:Diff/1023606/1024968]]. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 20:35, 29 October 2021 (UTC)
=== Path differences for examples ===
{{Talk|closed|date=October 29th, 2021}}
"To keep the settings, Portage reads in the /etc/portage/make.conf file" ok so this line is talking about what is currently /mnt/gentoo/etc/... but the light blue section afterwards refers to /mnt/gentoo/usr/share/... explicitly, as does the black section starting with nano -w, so there should be consistency across all those three things. [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 20:14, 18 November 2017 (UTC)
I seems like you're splitting hairs on ths one. The tip is about Portage. The path is different because you're operating out of an extracted state3 during this section of the handbook. I'll just change it to make.conf to avoid confusion. See [[Special:Diff/1023606/1024968]]. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 20:35, 29 October 2021 (UTC)
=== Custom prompt is reverted ===
{{Talk|done}}
After "root #eselect locale set 9", the shell tells the user to run something like . /etc/profile, which results in removing the custom prompt "(chroot)" and it's a little disconcerting. So I think the best option here is to tell the user not to follow the prompting of the shell before giving the set 9 command. Further, afterwards there is a black box that has maybe 3 commands in it separated by & and those commands could easily be given as a series of single lines, which would probably be better. [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 14:53, 19 November 2017 (UTC)
: This has been solved. Closing. [[User:Glibg10b|Glibg10b]] ([[User talk:Glibg10b|talk]]) 09:53, 1 April 2024 (UTC)
=== Current USE flags in profile ===
{{Talk|done}}
In the USE flag section, it might be a good idea to suggest something like <profile_file> | grep ^USE >> <make.conf> so that people can see their profile USE flags at the same time that they're putting in their custom values; they would have to comment it out if they did that, though. [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 15:08, 19 November 2017 (UTC)
: I really like the idea of explaining how to view USE flags already set in the profile. I'll implement something like this soon. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 20:35, 29 October 2021 (UTC)
:
: Completed ({{Link|Handbook:AMD64/Full/Installation#Optional:_Configuring_the_USE_variable}}). Closing. [[User:Glibg10b|Glibg10b]] ([[User talk:Glibg10b|talk]]) 09:54, 1 April 2024 (UTC)
=== devtmpfs cannot be unselected ===
{{Talk|closed|date=2023=02-19}}
" [*] Maintain a devtmpfs filesystem to mount at /dev" You can not unselect this, therefore this section can be removed safely. [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 15:19, 19 November 2017 (UTC)
: We'll safely leave it. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 09:28, 20 February 2023 (UTC)
=== Blank line requested ===
{{Talk|done}}
"Executable file formats / Emulations --->" Put a blank line prior to this to strongly indicate that it's denested. [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 16:04, 19 November 2017 (UTC)
: I no longer see that line in this AMD64/Full/Installation page, so can this be closed {{u|DavidC}} ? Thanks -- [[User:Ris|Ris]] ([[User talk:Ris|talk]]) 16:57, 1 March 2024 (UTC)
=== GRUB install issue ===
{{Talk|closed|date=2023-02-20}}
For grub-install with EFI, please include the 2 steps for EFI vars. Otherwise, grub-install will silently fail. From {{Link|Efibootmgr#Creating_a_boot_entry}}:
root #mount | grep efivars
efivarfs on /sys/firmware/efi/efivars type efivarfs (ro,relatime)
root #mount -o remount,rw -t efivarfs efivarfs /sys/firmware/efi/efivars
{{Unsigned2|19:27, December 18, 2017|Dman777}}
: This should NOT be the case when using official Gentoo installation live images. We do cover that in the [[Handbook:AMD64/Installation/Bootloader#Install|GRUB install section]], we just don't currently specify the <code>--type</code> option, as your example does. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 09:39, 20 February 2023 (UTC)
=== Fix nesting ===
{{Talk|done|date=14 July 2022}}
"Pseudo Filesystems --->" needs to be nested one step inwards. [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 16:10, 19 November 2017 (UTC)
: A fix was provided ([[Special:Diff/1018950/1023486]]). --[[User:Blacki|Blacki]] ([[User talk:Blacki|talk]]) 04:44, 14 July 2022 (UTC)
=== Combine all kernel sections ===
{{Talk|closed|date=October 29th, 2021}}
There seems to be a lot of random traversal of the kernel configuration. It would be beneficial to group all sections together which access similar hierarchies. It would probably also be good to include the hotkeys in this menu so that the user can traverse it more quickly. [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 16:14, 19 November 2017 (UTC)
I do not believe it would suit well to have all kernel sections together in one big block. Regarding hotkeys: we have other articles availabe on the wiki that mention hotkeys (see [[Kernel]] articles)... This is not something I think is worth adding to the basic installation requirements for Gentoo. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 20:35, 29 October 2021 (UTC)
=== How to read documenation file ===
{{Talk|done|date=14 July 2022}}
"Please read /usr/share/doc/netifrc-*/net.example.bz2 for a list of all available options." The document does not say how to do this. Also in this section, observe: " But don't fear, everything is explained below." This breaks style, but I like it. [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 20:01, 19 November 2017 (UTC)
: A little bit higher in the document, it was already mentionned that net.example.bz2 ''"can be read using bzless"''. --[[User:Blacki|Blacki]] ([[User talk:Blacki|talk]]) 10:10, 14 July 2022 (UTC)
== CFLAGS Section links ==
{{Talk|closed|date=October 27, 2021}}
Suggestion: The [[Handbook:AMD64/Full/Installation#CFLAGS_and_CXXFLAGS|CFLAGS Section]]
might as well contain additional references to [[GCC_optimization]] and [[CPU_FLAGS_X86]]?
These wiki pages seem more comprehensible for n00bs like me than the referenced gnu manual.
[[User:atari800]] (2019/02/19 11:54am)
: The [[GCC optimization]] and [[Safe CFLAGS]] articles are now listed in a tip at the [[Handbook:AMD64/Full/Installation#CFLAGS_and_CXXFLAGS|bottom of the section]]. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 22:52, 27 October 2021 (UTC)
== delete: Prior to Windows 7==
{{Talk|closed|date=October 27, 2021}}
Suggestion: Delete section to explain how to burn CD on a 10 year old windows system. If someone still runs it, he/she knows how to burn CD's. --[[User:Jstein|Jonas Stein]] ([[User talk:Jstein|talk]]) 01:06, 16 May 2020 (UTC)
: {{U|Jstein}}, thank you for reporting. This was fixed a while back. We now cover Windows 7 and above as a 'catch all' to include Windows 10 and 11. See [[Handbook:AMD64/Full/Installation#Burning_with_Microsoft_Windows_7_and_above]]. Thank you! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 21:08, 27 October 2021 (UTC)
== Reiserfs ==
{{talk|done}}
Reiserfs is included in mainline Linux--[[User:Nikitastepanov|Nikitastepanov]] ([[User talk:Nikitastepanov|talk]]) 11:26, 30 August 2020 (UTC)
: Duplicate of [[Handbook Talk:Parts/Installation/Disks#Reiserfs]] (as this page inherits that article) --[[User:Grknight|Grknight]] ([[User talk:Grknight|talk]]) 13:19, 31 August 2020 (UTC)' |
New page wikitext, after the edit (new_wikitext) | 'The following sections are [[Article description::completed discussions previously found on the [[Handbook Talk:AMD64/Full/Installation]] page.]] They have been moved here for archival purposes.
== 5.4 Viewing Documentation During Install ==
{{Talk|done}}
The documentation recommends creating a new user account and logging in on a separate virtual tty to load links with the install docs, then switching back and forth between a command tty and the docs tty. This will work but it's clumsy, slow, and aggravating. A better solution is to use "screen" which is already included on the minimal install CD. The docs can be viewed side-by-side with one or more command shells on the same terminal with the following commands:
* screen links Gentoo.org
* ^A ^C
* ^A | (for vertical split) or ^A S (for horizontal split)
Each "screen" can be split further into more windows. I would suggest including these instructions in the install docs in addition to or instead of the virtual terminal switching method.
{{Unsigned|Handle2001|21 July 2016}}
: I can make mention of this as an option and add a link to our article on [[Screen]], although I would not summarize logging in on multiple tty's "clumsy, slow, and aggravating". It is the simplest way of proceeding. Screen takes knowledge that many newcomers many not immediately possess. Seasoned system admins will probably think of using screen without it being mentioned. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 22:08, 26 January 2017 (UTC)
:: It is now mentioned as a possibility for seasoned Linux enthusiasts (who know how to use it). Closing discussion. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 22:59, 26 January 2017 (UTC)
== Choosing the right profile ==
{{Talk|done}}
While not a recommendation, this section suggests using "no-multilib" for a pure 64-bit environment. I think this should be followed by the disclaimer on the AMD64 FAQ:
{{Warning|Switching from a no-multilib to a multilib-enabled profile is currently not supported ([http://jkroon.blogs.uls.co.za/it/gentoo/gentoo-converting-no-multilib-to-multilib conversion hints]), so think over your decision twice before you use the no-multilib profile.}}
--[[User:Astronome|Astronome]] ([[User talk:Astronome|talk]]) 23:29, 6 February 2016 (UTC)
: I added [[Handbook:AMD64/Full/Installation#No-multilib_.28pure_64-bit.29|a small section]] noting the caveats of no-multilib. Should be better now. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 18:20, 13 January 2017 (UTC)
== Optional: Selecting mirrors ==
{{Talk|done}}
If you use >=sys-apps/portage-2.2.16, you not have to use
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>mirrorselect -i -r -o >> /mnt/gentoo/etc/portage/make.conf</code></div></div>
As, the SYNC variable in make.conf is deprecated and no longer used by portage.<br>
You will should use
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>mkdir /mnt/gentoo/etc/portage/repos.conf</code></div></div>
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>cp /usr/share/portage/config/repos.conf /mnt/gentoo/etc/portage/repos.conf/gentoo.conf</code></div></div>
If you want to be updated from other mirror, you can run
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>mirrorselect -i -r -o</code></div></div>
select mirror and paste received URI here /mnt/gentoo/etc/portage/repos.conf/gentoo.conf in variable "sync-uri" <br>
example:<br>
sync-uri = rsync://rsync.ru.gentoo.org/gentoo-portage
More info {{Link|Project:Portage/Sync}} <br><br>
P.S. Sorry my bad english.
{{Unsigned|Geronek|26 April 2015}}
: The repos.conf method is [[Handbook:AMD64/Full/Installation#Main_Gentoo_repository|now explained]] in the Handbook. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 18:22, 13 January 2017 (UTC)
== Unpacking the stage tarball ==
{{Talk|done}}
Is "--xattrs" required on some versions of tar to keep the extended attributes when extracting the archive or is this a mistake and as the manpage says, is only used to "save the user/root xattrs to the archive" (while when extracting, one would have to specify "--no-xattrs" to bypass them). {{Unsigned|Lepaperwan|1 November 2015}}
: Where do you see that in the GNU tar man page? Seems like bad information to me. I tested your theory using tar v1.29 and verified the <code>--xattrs</code> option must be added both for compression and extraction in order for {{c|tar}} handle extended attributes properly. See [http://www.lesbonscomptes.com/pages/extattrs.html#_archiving_and_backup this link] for someone else who tested. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 06:27, 24 January 2017 (UTC)
== Setting the date and time ==
{{Talk|done}}
Is there a reason Handbook doesn't suggest "ntpdate pool.ntp.org" instead of typing date manually? {{Unsigned|Vkuzkokov|7 March 2015}}
: It is less thinking and more accurate to use ntpd. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 18:23, 13 January 2017 (UTC)
== Typo "there are e a" ==
{{Talk|done}}
There's an apparent typo on a whole series of these wiki pages.
I created and validated wiki account for myself, but alas, it doesn't (yet) give me the option to edit the pages - so apparently I can't correct it.
Anyway, the error:
"there are e a couple"
should apparently be:
"there are a couple"
on at least these pages:
{{CodeBox|title=List of pages with typo in them|1=
{{Link|Handbook:AMD64/Full/Installation}}
{{Link|Handbook:AMD64/Installation/Stage}}
{{Link|Handbook:Alpha/Full/Installation}}
{{Link|Handbook:Alpha/Full/Installation/es}}
{{Link|Handbook:Alpha/Installation/Stage}}
{{Link|Handbook:HPPA/Full/Installation}}
{{Link|Handbook:HPPA/Full/Installation/es}}
{{Link|Handbook:HPPA/Installation/Stage}}
{{Link|Handbook:IA64/Full/Installation}}
{{Link|Handbook:IA64/Full/Installation/es}}
{{Link|Handbook:IA64/Installation/Stage}}
{{Link|Handbook:MIPS/Full/Installation}}
{{Link|Handbook:MIPS/Installation/Stage}}
{{Link|Handbook:PPC/Full/Installation}}
{{Link|Handbook:PPC/Full/Installation/es}}
{{Link|Handbook:PPC/Installation/Stage}}
{{Link|Handbook:PPC64/Full/Installation}}
{{Link|Handbook:PPC64/Full/Installation/es}}
{{Link|Handbook:PPC64/Installation/Stage}}
{{Link|Handbook:Parts/Full/Installation}}
{{Link|Handbook:Parts/Installation/Stage}}
{{Link|Handbook:SPARC/Full/Installation}}
{{Link|Handbook:SPARC/Full/Installation/es}}
{{Link|Handbook:SPARC/Installation/Stage}}
{{Link|Handbook:X86/Full/Installation}}
{{Link|Handbook:X86/Installation/Stage}}
{{Link|Handbook:X86/Installation/Stage/es}}
}}
'''(Above posted by Michael Paoli, fixed for wikification)'''
: Thanks, corrected. --[[User:SwifT|SwifT]] ([[User talk:SwifT|talk]]) 14:41, 27 December 2014 (UTC)
== systemd needed for Banshee Too! ==
{{talk|done}}
About the optional systemd and Gnome, could you mention that systemd is also required for programs like Banshee that highly depend on Gnome architecture.
<small>— The preceding [[Help:Signatures|unsigned]] comment was added by [[User:Gary987|Gary987]] ([[User talk:Gary987|talk]] • [[Special:Contributions/Gary987|contribs]]) 12 May 2015</small>
: It would seem Banshee is no longer available in the main ebuild repository, however I get the point. I have made a note of this in the Handbook's systemd section ({{Link|Handbook:Parts/Blocks/Systemd}}). Thanks for the tip! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 03:32, 5 March 2017 (UTC)
== 404 link on Introduction ==
{{Talk|done}}
The link to the Gentoo AMD64 project site (https://www.gentoo.org/proj/en/base/amd64/), on the Hardware Requirements section of the Introduction, leads to a 404 error. {{Unsigned|Rrzippert|3 August 2015}}
: Link has been long since fixed. Thanks! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 22:28, 13 January 2017 (UTC)
== Minor typo & systemd creep ==
{{Talk|done}}
Correct "on a amd64" to "on an amd64" if possible.
I'm here to do a clean openRC installation. Let's keep systemd in check.
The "--make-rslave" operation creeps in without mention of it being optional, if it is, and without yet mention that it is because of systemd.
If these operations are unnecessary without systemd, then please move the "--make-rslave" operations into, and/or under, the note. For example:
'''Note'''<br>
The --make-rslave operations are needed for systemd support later in the installation.
<pre>
root #mount --make-rslave /mnt/gentoo/sys
root #mount --make-rslave /mnt/gentoo/dev
</pre>
: It is in intention to support systemd as an ''optional'' init system. systemd is probably, at the time of writing, the ''most popular'' system in existence, although the majority of Gentoo users probably are not using it. The <code>--make-rslave</code> option passed to {{c|mount}} does not conflict with any options needed for those choosing either init system (OpenRC or systemd), and therefore is fine either way. Typos are corrected by now. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 01:34, 17 January 2017 (UTC)
== Re: Banshee ==
{{Talk|done}}
Banshee is software that is loaded with commercial interests, namely Amazon.com. If it has dependency issues then those should be dealt with at the Banshee development site, not here.
: Agreed. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 01:35, 17 January 2017 (UTC)
== Configuring the network ==
{{Talk|done}}
The Handbook heavily relies on the assumption that the network interface name is eth0, which is highly unlikely with the new udev naming rules.
Recommending the use of
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>ip link show up</code></div></div>
from a Gentoo-based installation medium or
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>udevadm test-builtin net_id /sys/class/net/eth0 2> /dev/null</code></div></div>
if coming from a different installation medium would allow users still unfamiliar with Gentoo to avoid errors during setup.
{{Unsigned|Lepaperwan|1 November 2015}}
: Agreed...I solved this by simply running
: {{RootCmd|touch /etc/udev/rules.d/80-net-name-slot.rules}}
: Likely works for 95% of all users with a single network card that doesn't change slots
:: For the purposes of the Handbook, it shouldn't matter what the network interface is named. It's just a handle created by udev. The Handbook [[Handbook:AMD64/Full/Installation#ip_command|does mention]] the {{c|ip}} command now. I'm not sure what the point of using {{c|udevadm}} would get the readers? If you still feel like there's more to this discussion then re-open it. Seems like we covered all the bases. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 06:36, 24 January 2017 (UTC)
== Installing the sources ==
{{Talk|done}}
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>emerge --ask sys-kernel/gentoo-sources</code></div></div>
This command execution recommends to control its status in another terminal by doing:
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>tail -f /var/log/emerge-fetch.log</code></div></div>
But we have previously chrooted into /mnt/gentoo/. So I suggest to specify that if we log into another terminal we should tail the file inside the mounted folder by doing:
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>tail -f /mnt/gentoo/var/log/emerge-fetch.log</code></div></div>
: Hi, I don't think instructions on how to {{c|tail}} the {{Path|emerge-fetch.log}} file needs to be mentioned in the Handbook. Hopefully the reader will be able to figure this out on their own by reading the message from the gentoo-sources ebuild. If you'd like to re-open and write up a mock wording for me to copy/paste into the Handbook I will consider it! Kind regards, --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 06:40, 24 January 2017 (UTC)
== Kernel config for USB support ==
{{Talk|done}}
This section is out of date:
{{KernelBox|title=Activating USB Support for input devices|<pre>
Device Drivers --->
[*] HID Devices --->
<*> USB Human Interface Device (full HID) support
</pre>}}
I believe the relevant options have been moved to:
{{KernelBox|title=Activating USB Support for input devices|<pre>
Device Drivers --->
HID support --->
-*- HID bus support
USB HID support --->
<*> USB HID transport layer
[*] USB support --->
Select relevant USB drivers
</pre>}}
--[[User:Astronome|Astronome]] ([[User talk:Astronome|talk]]) 19:35, 20 July 2016 (UTC)
: Hi {{U|Astronome}}, Thanks for the tip, and you are correct the example used in the Handbooks is certainly out of date! I have updated it! Thank you kindly for the productive feedback. Cheers, --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 04:31, 5 March 2017 (UTC)
== Kernel config for efi stub ==
{{Talk|done}}
Please edit configuration of kernel for efi support, else kernel not load a root file system.
{{KernelBox|title=Enable built-in kernel parameters|1=
Processor type and features --->
[*] Built-in kernel command line
(root=/dev/sda2 rw)
}}
: The [[Project:Handbook|Handbook]] team is trying to move away from supporting the UEFI stub kernel functionality as it is less flexible than using a bootloader to load the kernel into memory. That kind of of stuff can be ''left out'' of the Handbook and be included in other kernel related articles around the wiki. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 21:13, 13 January 2017 (UTC)
== Link to "other arches" on download page ==
{{Talk|done}}
In the "[[Handbook:AMD64/Full/Installation#Download the media|Download the media]]" section which discusses the "minimal installation CDs", the link to "the [//www.gentoo.org/downloads/#other-arches downloads page] (recommended)" is to the "Advanced Choices and other Architectures" section of that page. Shouldn't it be to the top of the page (no section anchor) where links to download the "normal" amd64 Minimal Installation CD, LiveDVD, and Stage 3 files are to be found? - [[User:Dcljr|dcljr]] ([[User talk:Dcljr|talk]]) 18:32, 13 April 2016 (UTC)
: The link has been updated. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 21:14, 13 January 2017 (UTC)
== Remove Parted ==
{{Talk|done}}
Remove Parted from handbook! fdisk have support GPT layout, and part of coreutils (default)
: I need to revise the disk section. I'll add this as a ''possibility'' to review. After reworking the disk section it parted may or may not be used. That's all I can say for now. Thanks! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 18:28, 13 January 2017 (UTC)
: I don't see why parted should be removed if it *works great*. --[[User:Vieri|Vieri]] ([[User talk:Vieri|talk]]) 12:12, 17 February 2017 (UTC)
== improve suggested partitions and use of grub-install ==
{{Talk|closed|date=2024-02-14}}
In my opinion, the handbook (amd64) is a bit confusing regarding partitioning.
First of all, I think it should try to keep the "parted" and "fdisk" examples as coherent as possible.
Furthermore, it would be preferable (more complete) to explain how to install Gentoo to a device that can then be booted both with UEFI and Legacy BIOS. Emphasis should be put on GPT, letting go MBR.
So here are my suggestions.
1) the "fdisk alternative" described at https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Alternative:_Using_fdisk_to_partition_the_disk warns that fdisk might still have bugs when supporting GPT (-t gpt). However, it does use an example partitioning scheme with bios boot and boot (see below).
2) the "fdisk alternative" starts with this partitioning scheme:
/dev/sda1 BIOS boot partition
/dev/sda2 Boot partition
and then ends telling the user to mark partition 1 (BIOS boot) for UEFI and create partition 2 as "boot".
The end results is:
[BIOS boot] /dev/sda1 1 3 5198+ ef EFI (FAT-12/16/32)
[boot/grub] /dev/sda2 * 3 14 105808+ 83 Linux
[swap] /dev/sda3 15 81 506520 82 Linux swap
[root] /dev/sda4 82 3876 28690200 83 Linux
3) in this section (https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Applying_a_filesystem_to_a_partition) the handbook suggests to format partition 2 as ext2:
# mkfs.ext2 /dev/sda2
4) in this other section (https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Using_UEFI) the handbook *suggests* to do the following:
# mkfs.fat -F 32 /dev/sda2
This suggestion is incoherent with point 2. It also doesn't guide the user to a UEFI installation.
5) There's one thing the user should be aware of and is not clearly stated in the handbook. For a UEFI installation, the live install system (or the liveCD) must boot via UEFI, not Legacy BIOS. In fact, it can happen that the BIOS will silently fail to boot a UEFI device and switch to booting via Legacy BIOS. Also, it should be clear to the reader that the current Gentoo Minimal CD is UNABLE to boot with UEFI (work in progress). Either use the LiveDVD or another system such as SystemRescueCD. In any case, the handbook should suggest to check for the existance of /sys/firmware/efi as soon as the live system has booted.
The user cannot install to a UEFI-bootable HDD if the live medium hasn't been booted with UEFI.
In particular, the user will fail to grub-install with EFI, as suggested in the handbook.
6) The default partitioning scheme described at
https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Default_partitioning_scheme
differs with point 2 because:
[BIOS boot] /dev/sda1 (bootloader) 2M BIOS boot partition
[boot/grub or UEFI] /dev/sda2 ext2 (or fat32 if UEFI is being used) 128M Boot/EFI system partition
7) The parted instructions at https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Default:_Using_parted_to_partition_the_disk
suggest to install BIOS boot on partition 1 and boot on partition 2.
In case the user wants to boot with UEFI, the handbook suggests to set UEFI on partition 2 (boot).
This is incoherent with point 2.
8) Finally, I think it would be better if the handbook could explain how to install to a UEFI&BIOS-aware device.<br />
There should be two scenarios:<br />
a) user wants to boot with ONLY UEFI or ONLY Legacy BIOS:<br />
in this case, use:<br />
a1) if Legacy BIOS:<br />
- boot with BIOS (not UEFI)<br />
- check /sys/firmware/efi does not exist<br />
- partitions:
[BIOS boot] /dev/sda1
[boot/grub] /dev/sda2 (ext2)
- filesystem:
# mkfs.ext2 /dev/sda2
# mount /dev/sda2 /boot
- install bootloader:
# grub-install /dev/sda
a2) if UEFI:<br />
- boot with UEFI (not BIOS)<br />
- check /sys/firmware/efi exists<br />
- partitions:
[BIOS boot] /dev/sda1
[UEFI] /dev/sda2 (fat32)
- filesystem:
# mkfs.fat -F 32 /dev/sda2
# mount /dev/sda2 /boot
- install bootloader:
# grub-install --target=x86_64-efi --efi-directory=/boot /dev/sda
(actually, grub-install /dev/sda should be enough)
b) user wants to boot with BOTH UEFI AND Legacy BIOS:<br />
b1) grub and efi on different partitions:<br />
- boot with UEFI (not BIOS)<br />
- check /sys/firmware/efi exists<br />
- partitions:
[BIOS boot] /dev/sda1
[UEFI] /dev/sda2 (fat32)
[boot/grub] /dev/sda3 (ext2)
- filesystem:
# mkfs.fat -F 32 /dev/sda2
# mkfs.ext2 /dev/sda3
# mount /dev/sda3 /boot
# mkdir /boot/efi
# mount /dev/sda2 /boot/efi
- install bootloader:
# grub-install --target=x86_64-efi --efi-directory=/boot/efi /dev/sda
( actually, grub-install --efi-directory=/boot/efi /dev/sda should be enough)
# grub-install --target=i386-pc /dev/sda
b2) grub and efi on same partition:<br />
- boot with UEFI (not BIOS)<br />
- check /sys/firmware/efi exists<br />
- partitions:
[BIOS boot] /dev/sda1
[UEFI/boot/grub] /dev/sda2 (fat32)
- filesystem:
# mkfs.fat -F 32 /dev/sda2
# mount /dev/sda2 /boot
- install bootloader:
# grub-install --target=x86_64-efi --efi-directory=/boot /dev/sda
( actually, grub-install /dev/sda should be enough)
# grub-install --target=i386-pc /dev/sda
--[[User:Vieri|Vieri]] ([[User talk:Vieri|talk]]) 11:17, 17 February 2017 (UTC)
: We have moved away from supporting Hybrid MBR/GPT configuration within the handbook, due to this configuration being unnecessary, niche, and cumbersome to explain. There are other places on the wiki that may detail this setup and instructions can be enhanced there if necessary (feel free to add something if it's missing).
: Installing GRUB to more than one disk is also beyond the cases covered in the handbook. We only detail a single drive installation - again, there is guidance and information other places on the wiki and within the GRUB manual. Thank you! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 12:24, 14 February 2024 (UTC)
== EFI partition mount ==
{{Talk|done|date=Jan 13th 2017}}
I see the Handbook mentions that Grub2 can't be used, and efibootmgr should be used instead. However, using grub2 is a suitable option.
The EFI partition should be mounted to /boot/efi:
# mkdir /mnt/gentoo/boot/efi
# mount /dev/sda1 /mnt/gentoo/boot/efi
[[User:ILMostro|ILMostro]] ([[User talk:ILMostro|talk]])
: Hi {{U|ILMostro}}, I saw your message in IRC. We are still very much active in monitoring and updating the wiki, although we're not always able to immediately respond on IRC. I agree, GRUB2 is a suitable option for EFI on Gentoo. I use it myself. With that being said we have to be careful with how much we try to support in the various handbooks. The purpose of it is to help users get Gentoo installed; not to walk them through all the configuration options (Gentoo is far too flexible for that!). :)
: I don't remember the Handbook ever saying GRUB2 can't be used for EFI on {{Keyword|amd64}} systems, but I will take a look and fix anything that doesn't seem right. Kind regards, --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 02:05, 21 June 2016 (UTC)
== GPT or MBR ==
{{Talk|closed|date=2022-02-22}}
It's definitely possible to dual-boot with Windows using GPT on a BIOS-based system. I'm able to do so with the following GRUB entry:
{{FileBox|filename=/etc/grub.d/40_custom|title=Dual-boot with Windows|<pre>
menuentry "Windows 10" {
insmod ntfs
insmod ntldr
insmod part_msdos
insmod search_fs_uuid
search --no-floppy --fs-uuid --set=root 1AECC5A1ECC57811
ntldr /bootmgr
}
</pre>}}
--[[User:Astronome|Astronome]] ([[User talk:Astronome|talk]]) 03:17, 21 January 2017 (UTC)
: Hi Astronome, if you're serious about having your discussions looked after please remember to use the {{Tl|Talk}} template. We can't really track what work is left for us to do without them.
: With that being said, to confirm: does the disk have a GPT partition table, or is it an MSDOS table? Also, is your copy of Windows installed in MSDOS mode? Kind regards, --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 06:47, 24 January 2017 (UTC)
: Revisiting here... Closing discussion due to no reply from author. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 08:50, 22 February 2022 (UTC)
== Mounting the necessary filesystems ==
{{Talk|done|date=Jan 26th 2017}}
I've always found this part confusing. Should this
{{RootCmd|mount -t proc proc /mnt/gentoo/proc}}
be changed to this?
{{RootCmd|mount -t proc /proc /mnt/gentoo/proc}}
Otherwise, if you're following the instructions exactly, your PWD will be {{Path|/mnt/gentoo}} and you'll be mounting {{Path|/mnt/gentoo/proc}} to itself. --[[User:Astronome|Astronome]] ([[User talk:Astronome|talk]]) 19:55, 21 January 2017 (UTC)
: Yes, it's a good point. We should have the {{Path|/}} on the second mention of proc. I'll update this. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 06:47, 24 January 2017 (UTC)
:: This assertion is wrong (but doesn't hurt). man mount:
::''The proc filesystem is not associated with a special device, and when mounting it, an arbitrary keyword, such as proc can be used instead of a device specification. (The customary choice none is less fortunate: the error message `none busy' from umount can be confusing.).''
::It was probably "proc" due to it being suggested to use that in the man page as that arbitrary keyword (but you can use "asdf" or whatever, pretty much anything except for "none'). That argument is the first one - that of the device node to use, -t proc doesn't have one, so it's ignored (unless special "none" is encountered). In "mount -t proc proc /mnt/gentoo/proc" the first "proc" is the type given with -t, "proc" is the device node and /mnt/gentoo/proc is the path - there is no proc path and no way this would have mounted itself (device node != directory). --[[User:Leio|Leio]] ([[User talk:Leio|talk]]) 15:26, 26 January 2017 (UTC)
::: That's funny, I was editing this page at the same time as you to say the same thing :) --[[User:Astronome|Astronome]] ([[User talk:Astronome|talk]]) 15:52, 26 January 2017 (UTC)
:::: So it doesn't really matter. It could be <code>proc</code> or it could be <code>/proc</code>. {{c|mount}} doesn't care. If there's nothing left to do here please close this discussion. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 21:52, 26 January 2017 (UTC)
:::: Well fine. --[[User:Astronome|Astronome]] ([[User talk:Astronome|talk]]) 02:29, 27 January 2017 (UTC)
== GPG verification when behind a firewall ==
{{Talk|done}}
If the default gpg port cannot be opened in the firewall then you might want to use something like:
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>gpg --keyserver hkp://hkps.pool.sks-keyservers.net:80 --recv-keys 0xBB572E0E2D182910</code></div></div>
BTW the user can also specify any other keyserver such as:
hkp://keyserver.ubuntu.com:80
This may be useful when some servers don't respond.
The following handbook section could be updated to reflect this:
{{Link|Handbook:AMD64/Full/Installation#Linux_based_verification}}
--[[User:Vieri|Vieri]] ([[User talk:Vieri|talk]]) 16 February 2017
: Hi {{U|Vieri}}, I'm rocking {{c|gpg}} version 2.1.19 and it would seem the syntax you used to specify a specific port has been deprecated. I couldn't get it to work by trying your example above. Also, from the man page ({{c|man 1 gpg}}), "The scheme is the type of keyserver: "hkp" for the HTTP (or compatible) keyservers". This indicates to me that HTTP is the default, so there is no need to specify port 80 in the example... Kind regards, --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 03:59, 5 March 2017 (UTC)
:: No, hkp uses port 11371 by default. What the OP neglected to mention is that not all keyservers support port 80. The general solution is to use the p80 pool at <code>hkp://p80.pool.sks-keyservers.net:80</code>. However, I think that it would be more preferable still to use the hkps pool at <code>hkps://hkps.pool.sks-keyservers.net</code>. This has the advantage of using HTTPS on the standard port of 443. Incidentally, portage and gemato are both inflexible in this regard. --[[User:kerframil|kerframil]] ([[User talk:kerframil|talk]]) 02:36, 21 July 2018 (UTC)
::: Thanks, added that URI. --[[User:Grknight|Grknight]] ([[User talk:Grknight|talk]]) 15:30, 7 November 2018 (UTC)
== DavidC improvements section ==
As I'm reading through this doco I'm writing a bunch of suggestions, some of which are sure to be misguided, so the only discussion I require is "yes/no/maybe later". Hopefully some of this helps but I know not all of it will be implemented.
=== Preparing the disk ===
{{Talk|done|2024-04-01}}
Prior to "Introduction to block devices" it would be nice if there was a title that said something like preparing the disk, since that is what is referred to above in the document. [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 17:57, 18 November 2017 (UTC)
: This would require a significant amount of work. It would require a lower-level heading than the one used for "Introduction to block devices" and subsequent sections. Since there is none, the headings for all sections on the page would have to be shifted up one level, but that change would automatically get copied to the non-full installation parts of the handbook (e.g. {{Link|Handbook:AMD64/Installation/Disks}}).
:
: The non-full installation parts should get priority since {{Handbook:AMD64}} takes the user there. Thus, taking no action is the best option here.
:
: I'm closing this discussion since I don't know whether you will respond. If you do, feel free to reopen it. [[User:Glibg10b|Glibg10b]] ([[User talk:Glibg10b|talk]]) 07:39, 1 April 2024 (UTC)
=== Open more than one chroot terminal ===
{{Talk|closed|date=October 29th, 2021}}
I'd probably get the user to chroot a couple terminals at least because then they would be able to do some reading while something is going on it another window, or easily compare say the output of lspci to what they're inputting in makeconfig, etc. [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 15:13, 19 November 2017 (UTC)
We mention screen for this purpose, but I have also have added a tip to explictly show readers how to switch between the seven available terminals: [[Special:Diff/1015767/024956]]. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 20:35, 29 October 2021 (UTC)
=== This and that ===
{{Talk|closed|date=2024-02-14}}
I am lost at [[Handbook:AMD64/Full/Installation#Introduction_to_block_devices]]. Looking at "If that is the case, it might be..." I understand what "that" case is, but when it says "In this case, launch..." I do not understand what "this" case is. Perhaps after "using the MBR format." A sentence could be added directing MBR users to "Default partitioning scheme". Someone suggested this be split into 3 sections "bios with mbr, efi with gpt, bios with gpt" [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 19:37, 18 November 2017 (UTC)
=== I am overwhelmed with mirrors ===
{{Talk|closed|date=October 29th, 2021}}
"links https://www.gentoo.org/downloads/mirrors/" So if you follow the first link for Canadians, you end up going to a LONG list of files and it's not entirely clear what to download (even if you follow it all the way to Gentoo, so it's probably best just to link people straight to https://gentoo.org/downloads/. [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 19:58, 18 November 2017 (UTC)
: If you are referring this section, there are no instructions to download anything from the mirrors directly. It's just giving an example on how to use links to determine what mirror URLs are avaialble. No where in the instruction are you supposed to download anything in this section. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 20:35, 29 October 2021 (UTC)
=== Variables ===
{{Talk|closed|date=October 29th, 2021}}
"variables which impacts" --> "impact" [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 20:02, 18 November 2017 (UTC)
: Fixed. See [[Special:Diff/1023606/1024968]]. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 20:35, 29 October 2021 (UTC)
=== Path differences for examples ===
{{Talk|closed|date=October 29th, 2021}}
"To keep the settings, Portage reads in the /etc/portage/make.conf file" ok so this line is talking about what is currently /mnt/gentoo/etc/... but the light blue section afterwards refers to /mnt/gentoo/usr/share/... explicitly, as does the black section starting with nano -w, so there should be consistency across all those three things. [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 20:14, 18 November 2017 (UTC)
I seems like you're splitting hairs on ths one. The tip is about Portage. The path is different because you're operating out of an extracted state3 during this section of the handbook. I'll just change it to make.conf to avoid confusion. See [[Special:Diff/1023606/1024968]]. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 20:35, 29 October 2021 (UTC)
=== Custom prompt is reverted ===
{{Talk|done}}
After "root #eselect locale set 9", the shell tells the user to run something like . /etc/profile, which results in removing the custom prompt "(chroot)" and it's a little disconcerting. So I think the best option here is to tell the user not to follow the prompting of the shell before giving the set 9 command. Further, afterwards there is a black box that has maybe 3 commands in it separated by & and those commands could easily be given as a series of single lines, which would probably be better. [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 14:53, 19 November 2017 (UTC)
: This has been solved. Closing. [[User:Glibg10b|Glibg10b]] ([[User talk:Glibg10b|talk]]) 09:53, 1 April 2024 (UTC)
=== Current USE flags in profile ===
{{Talk|done}}
In the USE flag section, it might be a good idea to suggest something like <profile_file> | grep ^USE >> <make.conf> so that people can see their profile USE flags at the same time that they're putting in their custom values; they would have to comment it out if they did that, though. [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 15:08, 19 November 2017 (UTC)
: I really like the idea of explaining how to view USE flags already set in the profile. I'll implement something like this soon. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 20:35, 29 October 2021 (UTC)
:
: Completed ({{Link|Handbook:AMD64/Full/Installation#Optional:_Configuring_the_USE_variable}}). Closing. [[User:Glibg10b|Glibg10b]] ([[User talk:Glibg10b|talk]]) 09:54, 1 April 2024 (UTC)
=== devtmpfs cannot be unselected ===
{{Talk|closed|date=2023=02-19}}
" [*] Maintain a devtmpfs filesystem to mount at /dev" You can not unselect this, therefore this section can be removed safely. [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 15:19, 19 November 2017 (UTC)
: We'll safely leave it. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 09:28, 20 February 2023 (UTC)
=== Blank line requested ===
{{Talk|done}}
"Executable file formats / Emulations --->" Put a blank line prior to this to strongly indicate that it's denested. [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 16:04, 19 November 2017 (UTC)
: I no longer see that line in this AMD64/Full/Installation page, so can this be closed {{u|DavidC}} ? Thanks -- [[User:Ris|Ris]] ([[User talk:Ris|talk]]) 16:57, 1 March 2024 (UTC)
=== GRUB install issue ===
{{Talk|closed|date=2023-02-20}}
For grub-install with EFI, please include the 2 steps for EFI vars. Otherwise, grub-install will silently fail. From {{Link|Efibootmgr#Creating_a_boot_entry}}:
root #mount | grep efivars
efivarfs on /sys/firmware/efi/efivars type efivarfs (ro,relatime)
root #mount -o remount,rw -t efivarfs efivarfs /sys/firmware/efi/efivars
{{Unsigned2|19:27, December 18, 2017|Dman777}}
: This should NOT be the case when using official Gentoo installation live images. We do cover that in the [[Handbook:AMD64/Installation/Bootloader#Install|GRUB install section]], we just don't currently specify the <code>--type</code> option, as your example does. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 09:39, 20 February 2023 (UTC)
=== Fix nesting ===
{{Talk|done|date=14 July 2022}}
"Pseudo Filesystems --->" needs to be nested one step inwards. [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 16:10, 19 November 2017 (UTC)
: A fix was provided ([[Special:Diff/1018950/1023486]]). --[[User:Blacki|Blacki]] ([[User talk:Blacki|talk]]) 04:44, 14 July 2022 (UTC)
=== Combine all kernel sections ===
{{Talk|closed|date=October 29th, 2021}}
There seems to be a lot of random traversal of the kernel configuration. It would be beneficial to group all sections together which access similar hierarchies. It would probably also be good to include the hotkeys in this menu so that the user can traverse it more quickly. [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 16:14, 19 November 2017 (UTC)
I do not believe it would suit well to have all kernel sections together in one big block. Regarding hotkeys: we have other articles availabe on the wiki that mention hotkeys (see [[Kernel]] articles)... This is not something I think is worth adding to the basic installation requirements for Gentoo. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 20:35, 29 October 2021 (UTC)
=== How to read documenation file ===
{{Talk|done|date=14 July 2022}}
"Please read /usr/share/doc/netifrc-*/net.example.bz2 for a list of all available options." The document does not say how to do this. Also in this section, observe: " But don't fear, everything is explained below." This breaks style, but I like it. [[User:DavidC|DavidC]] ([[User talk:DavidC|talk]]) 20:01, 19 November 2017 (UTC)
: A little bit higher in the document, it was already mentionned that net.example.bz2 ''"can be read using bzless"''. --[[User:Blacki|Blacki]] ([[User talk:Blacki|talk]]) 10:10, 14 July 2022 (UTC)
== CFLAGS Section links ==
{{Talk|closed|date=October 27, 2021}}
Suggestion: The [[Handbook:AMD64/Full/Installation#CFLAGS_and_CXXFLAGS|CFLAGS Section]]
might as well contain additional references to [[GCC_optimization]] and [[CPU_FLAGS_X86]]?
These wiki pages seem more comprehensible for n00bs like me than the referenced gnu manual.
[[User:atari800]] (2019/02/19 11:54am)
: The [[GCC optimization]] and [[Safe CFLAGS]] articles are now listed in a tip at the [[Handbook:AMD64/Full/Installation#CFLAGS_and_CXXFLAGS|bottom of the section]]. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 22:52, 27 October 2021 (UTC)
== delete: Prior to Windows 7==
{{Talk|closed|date=October 27, 2021}}
Suggestion: Delete section to explain how to burn CD on a 10 year old windows system. If someone still runs it, he/she knows how to burn CD's. --[[User:Jstein|Jonas Stein]] ([[User talk:Jstein|talk]]) 01:06, 16 May 2020 (UTC)
: {{U|Jstein}}, thank you for reporting. This was fixed a while back. We now cover Windows 7 and above as a 'catch all' to include Windows 10 and 11. See [[Handbook:AMD64/Full/Installation#Burning_with_Microsoft_Windows_7_and_above]]. Thank you! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 21:08, 27 October 2021 (UTC)
== Reiserfs ==
{{talk|done}}
Reiserfs is included in mainline Linux--[[User:Nikitastepanov|Nikitastepanov]] ([[User talk:Nikitastepanov|talk]]) 11:26, 30 August 2020 (UTC)
: Duplicate of [[Handbook Talk:Parts/Installation/Disks#Reiserfs]] (as this page inherits that article) --[[User:Grknight|Grknight]] ([[User talk:Grknight|talk]]) 13:19, 31 August 2020 (UTC)' |
Unified diff of changes made by edit (edit_diff) | '@@ -250,4 +250,124 @@
: I don't see why parted should be removed if it *works great*. --[[User:Vieri|Vieri]] ([[User talk:Vieri|talk]]) 12:12, 17 February 2017 (UTC)
+
+== improve suggested partitions and use of grub-install ==
+
+{{Talk|closed|date=2024-02-14}}
+
+In my opinion, the handbook (amd64) is a bit confusing regarding partitioning.
+
+First of all, I think it should try to keep the "parted" and "fdisk" examples as coherent as possible.
+Furthermore, it would be preferable (more complete) to explain how to install Gentoo to a device that can then be booted both with UEFI and Legacy BIOS. Emphasis should be put on GPT, letting go MBR.
+
+So here are my suggestions.
+
+1) the "fdisk alternative" described at https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Alternative:_Using_fdisk_to_partition_the_disk warns that fdisk might still have bugs when supporting GPT (-t gpt). However, it does use an example partitioning scheme with bios boot and boot (see below).
+
+2) the "fdisk alternative" starts with this partitioning scheme:
+ /dev/sda1 BIOS boot partition
+ /dev/sda2 Boot partition
+and then ends telling the user to mark partition 1 (BIOS boot) for UEFI and create partition 2 as "boot".
+
+The end results is:
+ [BIOS boot] /dev/sda1 1 3 5198+ ef EFI (FAT-12/16/32)
+ [boot/grub] /dev/sda2 * 3 14 105808+ 83 Linux
+ [swap] /dev/sda3 15 81 506520 82 Linux swap
+ [root] /dev/sda4 82 3876 28690200 83 Linux
+
+3) in this section (https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Applying_a_filesystem_to_a_partition) the handbook suggests to format partition 2 as ext2:
+
+ # mkfs.ext2 /dev/sda2
+
+4) in this other section (https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Using_UEFI) the handbook *suggests* to do the following:
+
+ # mkfs.fat -F 32 /dev/sda2
+
+This suggestion is incoherent with point 2. It also doesn't guide the user to a UEFI installation.
+
+5) There's one thing the user should be aware of and is not clearly stated in the handbook. For a UEFI installation, the live install system (or the liveCD) must boot via UEFI, not Legacy BIOS. In fact, it can happen that the BIOS will silently fail to boot a UEFI device and switch to booting via Legacy BIOS. Also, it should be clear to the reader that the current Gentoo Minimal CD is UNABLE to boot with UEFI (work in progress). Either use the LiveDVD or another system such as SystemRescueCD. In any case, the handbook should suggest to check for the existance of /sys/firmware/efi as soon as the live system has booted.
+The user cannot install to a UEFI-bootable HDD if the live medium hasn't been booted with UEFI.
+In particular, the user will fail to grub-install with EFI, as suggested in the handbook.
+
+6) The default partitioning scheme described at
+https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Default_partitioning_scheme
+differs with point 2 because:
+ [BIOS boot] /dev/sda1 (bootloader) 2M BIOS boot partition
+ [boot/grub or UEFI] /dev/sda2 ext2 (or fat32 if UEFI is being used) 128M Boot/EFI system partition
+
+7) The parted instructions at https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Default:_Using_parted_to_partition_the_disk
+suggest to install BIOS boot on partition 1 and boot on partition 2.
+In case the user wants to boot with UEFI, the handbook suggests to set UEFI on partition 2 (boot).
+This is incoherent with point 2.
+
+8) Finally, I think it would be better if the handbook could explain how to install to a UEFI&BIOS-aware device.<br />
+There should be two scenarios:<br />
+
+a) user wants to boot with ONLY UEFI or ONLY Legacy BIOS:<br />
+in this case, use:<br />
+
+a1) if Legacy BIOS:<br />
+- boot with BIOS (not UEFI)<br />
+- check /sys/firmware/efi does not exist<br />
+- partitions:
+ [BIOS boot] /dev/sda1
+ [boot/grub] /dev/sda2 (ext2)
+- filesystem:
+ # mkfs.ext2 /dev/sda2
+ # mount /dev/sda2 /boot
+- install bootloader:
+ # grub-install /dev/sda
+
+a2) if UEFI:<br />
+- boot with UEFI (not BIOS)<br />
+- check /sys/firmware/efi exists<br />
+- partitions:
+ [BIOS boot] /dev/sda1
+ [UEFI] /dev/sda2 (fat32)
+- filesystem:
+ # mkfs.fat -F 32 /dev/sda2
+ # mount /dev/sda2 /boot
+- install bootloader:
+ # grub-install --target=x86_64-efi --efi-directory=/boot /dev/sda
+(actually, grub-install /dev/sda should be enough)
+
+b) user wants to boot with BOTH UEFI AND Legacy BIOS:<br />
+
+b1) grub and efi on different partitions:<br />
+- boot with UEFI (not BIOS)<br />
+- check /sys/firmware/efi exists<br />
+- partitions:
+ [BIOS boot] /dev/sda1
+ [UEFI] /dev/sda2 (fat32)
+ [boot/grub] /dev/sda3 (ext2)
+- filesystem:
+ # mkfs.fat -F 32 /dev/sda2
+ # mkfs.ext2 /dev/sda3
+ # mount /dev/sda3 /boot
+ # mkdir /boot/efi
+ # mount /dev/sda2 /boot/efi
+- install bootloader:
+ # grub-install --target=x86_64-efi --efi-directory=/boot/efi /dev/sda
+( actually, grub-install --efi-directory=/boot/efi /dev/sda should be enough)
+ # grub-install --target=i386-pc /dev/sda
+
+b2) grub and efi on same partition:<br />
+- boot with UEFI (not BIOS)<br />
+- check /sys/firmware/efi exists<br />
+- partitions:
+ [BIOS boot] /dev/sda1
+ [UEFI/boot/grub] /dev/sda2 (fat32)
+- filesystem:
+ # mkfs.fat -F 32 /dev/sda2
+ # mount /dev/sda2 /boot
+- install bootloader:
+ # grub-install --target=x86_64-efi --efi-directory=/boot /dev/sda
+( actually, grub-install /dev/sda should be enough)
+ # grub-install --target=i386-pc /dev/sda
+
+--[[User:Vieri|Vieri]] ([[User talk:Vieri|talk]]) 11:17, 17 February 2017 (UTC)
+
+: We have moved away from supporting Hybrid MBR/GPT configuration within the handbook, due to this configuration being unnecessary, niche, and cumbersome to explain. There are other places on the wiki that may detail this setup and instructions can be enhanced there if necessary (feel free to add something if it's missing).
+
+: Installing GRUB to more than one disk is also beyond the cases covered in the handbook. We only detail a single drive installation - again, there is guidance and information other places on the wiki and within the GRUB manual. Thank you! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 12:24, 14 February 2024 (UTC)
== EFI partition mount ==
' |
Old page size (old_size) | 33662 |
Lines added in edit (added_lines) | [
0 => '',
1 => '== improve suggested partitions and use of grub-install ==',
2 => '',
3 => '{{Talk|closed|date=2024-02-14}}',
4 => '',
5 => 'In my opinion, the handbook (amd64) is a bit confusing regarding partitioning.',
6 => '',
7 => 'First of all, I think it should try to keep the "parted" and "fdisk" examples as coherent as possible.',
8 => 'Furthermore, it would be preferable (more complete) to explain how to install Gentoo to a device that can then be booted both with UEFI and Legacy BIOS. Emphasis should be put on GPT, letting go MBR.',
9 => '',
10 => 'So here are my suggestions.',
11 => '',
12 => '1) the "fdisk alternative" described at https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Alternative:_Using_fdisk_to_partition_the_disk warns that fdisk might still have bugs when supporting GPT (-t gpt). However, it does use an example partitioning scheme with bios boot and boot (see below).',
13 => '',
14 => '2) the "fdisk alternative" starts with this partitioning scheme:',
15 => ' /dev/sda1 BIOS boot partition',
16 => ' /dev/sda2 Boot partition',
17 => 'and then ends telling the user to mark partition 1 (BIOS boot) for UEFI and create partition 2 as "boot".',
18 => '',
19 => 'The end results is:',
20 => ' [BIOS boot] /dev/sda1 1 3 5198+ ef EFI (FAT-12/16/32)',
21 => ' [boot/grub] /dev/sda2 * 3 14 105808+ 83 Linux',
22 => ' [swap] /dev/sda3 15 81 506520 82 Linux swap',
23 => ' [root] /dev/sda4 82 3876 28690200 83 Linux',
24 => '',
25 => '3) in this section (https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Applying_a_filesystem_to_a_partition) the handbook suggests to format partition 2 as ext2:',
26 => '',
27 => ' # mkfs.ext2 /dev/sda2',
28 => '',
29 => '4) in this other section (https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Using_UEFI) the handbook *suggests* to do the following:',
30 => '',
31 => ' # mkfs.fat -F 32 /dev/sda2',
32 => '',
33 => 'This suggestion is incoherent with point 2. It also doesn't guide the user to a UEFI installation.',
34 => '',
35 => '5) There's one thing the user should be aware of and is not clearly stated in the handbook. For a UEFI installation, the live install system (or the liveCD) must boot via UEFI, not Legacy BIOS. In fact, it can happen that the BIOS will silently fail to boot a UEFI device and switch to booting via Legacy BIOS. Also, it should be clear to the reader that the current Gentoo Minimal CD is UNABLE to boot with UEFI (work in progress). Either use the LiveDVD or another system such as SystemRescueCD. In any case, the handbook should suggest to check for the existance of /sys/firmware/efi as soon as the live system has booted.',
36 => 'The user cannot install to a UEFI-bootable HDD if the live medium hasn't been booted with UEFI.',
37 => 'In particular, the user will fail to grub-install with EFI, as suggested in the handbook.',
38 => '',
39 => '6) The default partitioning scheme described at',
40 => 'https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Default_partitioning_scheme',
41 => 'differs with point 2 because:',
42 => ' [BIOS boot] /dev/sda1 (bootloader) 2M BIOS boot partition',
43 => ' [boot/grub or UEFI] /dev/sda2 ext2 (or fat32 if UEFI is being used) 128M Boot/EFI system partition',
44 => '',
45 => '7) The parted instructions at https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Default:_Using_parted_to_partition_the_disk',
46 => 'suggest to install BIOS boot on partition 1 and boot on partition 2.',
47 => 'In case the user wants to boot with UEFI, the handbook suggests to set UEFI on partition 2 (boot).',
48 => 'This is incoherent with point 2.',
49 => '',
50 => '8) Finally, I think it would be better if the handbook could explain how to install to a UEFI&BIOS-aware device.<br />',
51 => 'There should be two scenarios:<br />',
52 => '',
53 => 'a) user wants to boot with ONLY UEFI or ONLY Legacy BIOS:<br />',
54 => 'in this case, use:<br />',
55 => '',
56 => 'a1) if Legacy BIOS:<br />',
57 => '- boot with BIOS (not UEFI)<br />',
58 => '- check /sys/firmware/efi does not exist<br />',
59 => '- partitions:',
60 => ' [BIOS boot] /dev/sda1',
61 => ' [boot/grub] /dev/sda2 (ext2)',
62 => '- filesystem:',
63 => ' # mkfs.ext2 /dev/sda2',
64 => ' # mount /dev/sda2 /boot',
65 => '- install bootloader:',
66 => ' # grub-install /dev/sda',
67 => '',
68 => 'a2) if UEFI:<br />',
69 => '- boot with UEFI (not BIOS)<br />',
70 => '- check /sys/firmware/efi exists<br />',
71 => '- partitions:',
72 => ' [BIOS boot] /dev/sda1',
73 => ' [UEFI] /dev/sda2 (fat32)',
74 => '- filesystem:',
75 => ' # mkfs.fat -F 32 /dev/sda2',
76 => ' # mount /dev/sda2 /boot',
77 => '- install bootloader:',
78 => ' # grub-install --target=x86_64-efi --efi-directory=/boot /dev/sda',
79 => '(actually, grub-install /dev/sda should be enough)',
80 => '',
81 => 'b) user wants to boot with BOTH UEFI AND Legacy BIOS:<br />',
82 => '',
83 => 'b1) grub and efi on different partitions:<br />',
84 => '- boot with UEFI (not BIOS)<br />',
85 => '- check /sys/firmware/efi exists<br />',
86 => '- partitions:',
87 => ' [BIOS boot] /dev/sda1',
88 => ' [UEFI] /dev/sda2 (fat32)',
89 => ' [boot/grub] /dev/sda3 (ext2)',
90 => '- filesystem:',
91 => ' # mkfs.fat -F 32 /dev/sda2',
92 => ' # mkfs.ext2 /dev/sda3',
93 => ' # mount /dev/sda3 /boot',
94 => ' # mkdir /boot/efi',
95 => ' # mount /dev/sda2 /boot/efi',
96 => '- install bootloader:',
97 => ' # grub-install --target=x86_64-efi --efi-directory=/boot/efi /dev/sda',
98 => '( actually, grub-install --efi-directory=/boot/efi /dev/sda should be enough)',
99 => ' # grub-install --target=i386-pc /dev/sda',
100 => '',
101 => 'b2) grub and efi on same partition:<br />',
102 => '- boot with UEFI (not BIOS)<br />',
103 => '- check /sys/firmware/efi exists<br />',
104 => '- partitions:',
105 => ' [BIOS boot] /dev/sda1',
106 => ' [UEFI/boot/grub] /dev/sda2 (fat32)',
107 => '- filesystem:',
108 => ' # mkfs.fat -F 32 /dev/sda2',
109 => ' # mount /dev/sda2 /boot',
110 => '- install bootloader:',
111 => ' # grub-install --target=x86_64-efi --efi-directory=/boot /dev/sda',
112 => '( actually, grub-install /dev/sda should be enough)',
113 => ' # grub-install --target=i386-pc /dev/sda',
114 => '',
115 => '--[[User:Vieri|Vieri]] ([[User talk:Vieri|talk]]) 11:17, 17 February 2017 (UTC)',
116 => '',
117 => ': We have moved away from supporting Hybrid MBR/GPT configuration within the handbook, due to this configuration being unnecessary, niche, and cumbersome to explain. There are other places on the wiki that may detail this setup and instructions can be enhanced there if necessary (feel free to add something if it's missing).',
118 => '',
119 => ': Installing GRUB to more than one disk is also beyond the cases covered in the handbook. We only detail a single drive installation - again, there is guidance and information other places on the wiki and within the GRUB manual. Thank you! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 12:24, 14 February 2024 (UTC)'
] |
Lines removed in edit (removed_lines) | [] |
New page text, stripped of any markup (new_text) | 'The following sections are completed discussions previously found on the Handbook Talk:AMD64/Full/Installation page. They have been moved here for archival purposes.
Contents
1 5.4 Viewing Documentation During Install
2 Choosing the right profile
3 Optional: Selecting mirrors
4 Unpacking the stage tarball
5 Setting the date and time
6 Typo "there are e a"
7 systemd needed for Banshee Too!
8 404 link on Introduction
9 Minor typo & systemd creep
10 Re: Banshee
11 Configuring the network
12 Installing the sources
13 Kernel config for USB support
14 Kernel config for efi stub
15 Link to "other arches" on download page
16 Remove Parted
17 improve suggested partitions and use of grub-install
18 EFI partition mount
19 GPT or MBR
20 Mounting the necessary filesystems
21 GPG verification when behind a firewall
22 DavidC improvements section
22.1 Preparing the disk
22.2 Open more than one chroot terminal
22.3 This and that
22.4 I am overwhelmed with mirrors
22.5 Variables
22.6 Path differences for examples
22.7 Custom prompt is reverted
22.8 Current USE flags in profile
22.9 devtmpfs cannot be unselected
22.10 Blank line requested
22.11 GRUB install issue
22.12 Fix nesting
22.13 Combine all kernel sections
22.14 How to read documenation file
23 CFLAGS Section links
24 delete: Prior to Windows 7
25 Reiserfs
5.4 Viewing Documentation During Install[edit source]
Talk status
This discussion is done.
The documentation recommends creating a new user account and logging in on a separate virtual tty to load links with the install docs, then switching back and forth between a command tty and the docs tty. This will work but it's clumsy, slow, and aggravating. A better solution is to use "screen" which is already included on the minimal install CD. The docs can be viewed side-by-side with one or more command shells on the same terminal with the following commands:
screen links Gentoo.org
^A ^C
^A | (for vertical split) or ^A S (for horizontal split)
Each "screen" can be split further into more windows. I would suggest including these instructions in the install docs in addition to or instead of the virtual terminal switching method.
— The preceding unsigned comment was added by Handle2001 (talk • contribs) 21 July 2016
I can make mention of this as an option and add a link to our article on Screen, although I would not summarize logging in on multiple tty's "clumsy, slow, and aggravating". It is the simplest way of proceeding. Screen takes knowledge that many newcomers many not immediately possess. Seasoned system admins will probably think of using screen without it being mentioned. --Maffblaster (talk) 22:08, 26 January 2017 (UTC)
It is now mentioned as a possibility for seasoned Linux enthusiasts (who know how to use it). Closing discussion. --Maffblaster (talk) 22:59, 26 January 2017 (UTC)
Choosing the right profile[edit source]
Talk status
This discussion is done.
While not a recommendation, this section suggests using "no-multilib" for a pure 64-bit environment. I think this should be followed by the disclaimer on the AMD64 FAQ:
WarningSwitching from a no-multilib to a multilib-enabled profile is currently not supported (conversion hints), so think over your decision twice before you use the no-multilib profile.
--Astronome (talk) 23:29, 6 February 2016 (UTC)
I added a small section noting the caveats of no-multilib. Should be better now. --Maffblaster (talk) 18:20, 13 January 2017 (UTC)
Optional: Selecting mirrors[edit source]
Talk status
This discussion is done.
If you use >=sys-apps/portage-2.2.16, you not have to use
root #mirrorselect -i -r -o >> /mnt/gentoo/etc/portage/make.conf
As, the SYNC variable in make.conf is deprecated and no longer used by portage.
You will should use
root #mkdir /mnt/gentoo/etc/portage/repos.conf
root #cp /usr/share/portage/config/repos.conf /mnt/gentoo/etc/portage/repos.conf/gentoo.conf
If you want to be updated from other mirror, you can run
root #mirrorselect -i -r -o
select mirror and paste received URI here /mnt/gentoo/etc/portage/repos.conf/gentoo.conf in variable "sync-uri"
example:
sync-uri = rsync://rsync.ru.gentoo.org/gentoo-portage
More info Project:Portage/Sync
P.S. Sorry my bad english.
— The preceding unsigned comment was added by Geronek (talk • contribs) 26 April 2015
The repos.conf method is now explained in the Handbook. --Maffblaster (talk) 18:22, 13 January 2017 (UTC)
Unpacking the stage tarball[edit source]
Talk status
This discussion is done.
Is "--xattrs" required on some versions of tar to keep the extended attributes when extracting the archive or is this a mistake and as the manpage says, is only used to "save the user/root xattrs to the archive" (while when extracting, one would have to specify "--no-xattrs" to bypass them). — The preceding unsigned comment was added by Lepaperwan (talk • contribs) 1 November 2015
Where do you see that in the GNU tar man page? Seems like bad information to me. I tested your theory using tar v1.29 and verified the --xattrs option must be added both for compression and extraction in order for tar handle extended attributes properly. See this link for someone else who tested. --Maffblaster (talk) 06:27, 24 January 2017 (UTC)
Setting the date and time[edit source]
Talk status
This discussion is done.
Is there a reason Handbook doesn't suggest "ntpdate pool.ntp.org" instead of typing date manually? — The preceding unsigned comment was added by Vkuzkokov (talk • contribs) 7 March 2015
It is less thinking and more accurate to use ntpd. --Maffblaster (talk) 18:23, 13 January 2017 (UTC)
Typo "there are e a"[edit source]
Talk status
This discussion is done.
There's an apparent typo on a whole series of these wiki pages.
I created and validated wiki account for myself, but alas, it doesn't (yet) give me the option to edit the pages - so apparently I can't correct it.
Anyway, the error:
"there are e a couple"
should apparently be:
"there are a couple"
on at least these pages:
CODE List of pages with typo in them [[:Handbook:AMD64/Full/Installation|Handbook:AMD64/Full/Installation]]
[[:Handbook:AMD64/Installation/Stage|Handbook:AMD64/Installation/Stage]]
[[:Handbook:Alpha/Full/Installation|Handbook:Alpha/Full/Installation]]
[[:Handbook:Alpha/Full/Installation/es|Handbook:Alpha/Full/Installation/es]]
[[:Handbook:Alpha/Installation/Stage|Handbook:Alpha/Installation/Stage]]
[[:Handbook:HPPA/Full/Installation|Handbook:HPPA/Full/Installation]]
[[:Handbook:HPPA/Full/Installation/es|Handbook:HPPA/Full/Installation/es]]
[[:Handbook:HPPA/Installation/Stage|Handbook:HPPA/Installation/Stage]]
[[:Handbook:IA64/Full/Installation|Handbook:IA64/Full/Installation]]
[[:Handbook:IA64/Full/Installation/es|Handbook:IA64/Full/Installation/es]]
[[:Handbook:IA64/Installation/Stage|Handbook:IA64/Installation/Stage]]
[[:Handbook:MIPS/Full/Installation|Handbook:MIPS/Full/Installation]]
[[:Handbook:MIPS/Installation/Stage|Handbook:MIPS/Installation/Stage]]
[[:Handbook:PPC/Full/Installation|Handbook:PPC/Full/Installation]]
[[:Handbook:PPC/Full/Installation/es|Handbook:PPC/Full/Installation/es]]
[[:Handbook:PPC/Installation/Stage|Handbook:PPC/Installation/Stage]]
[[:Handbook:PPC64/Full/Installation|Handbook:PPC64/Full/Installation]]
[[:Handbook:PPC64/Full/Installation/es|Handbook:PPC64/Full/Installation/es]]
[[:Handbook:PPC64/Installation/Stage|Handbook:PPC64/Installation/Stage]]
[[:Handbook:Parts/Full/Installation|Handbook:Parts/Full/Installation]]
[[:Handbook:Parts/Installation/Stage|Handbook:Parts/Installation/Stage]]
[[:Handbook:SPARC/Full/Installation|Handbook:SPARC/Full/Installation]]
[[:Handbook:SPARC/Full/Installation/es|Handbook:SPARC/Full/Installation/es]]
[[:Handbook:SPARC/Installation/Stage|Handbook:SPARC/Installation/Stage]]
[[:Handbook:X86/Full/Installation|Handbook:X86/Full/Installation]]
[[:Handbook:X86/Installation/Stage|Handbook:X86/Installation/Stage]]
[[:Handbook:X86/Installation/Stage/es|Handbook:X86/Installation/Stage/es]]
(Above posted by Michael Paoli, fixed for wikification)
Thanks, corrected. --SwifT (talk) 14:41, 27 December 2014 (UTC)
systemd needed for Banshee Too![edit source]
Talk status
This discussion is done.
About the optional systemd and Gnome, could you mention that systemd is also required for programs like Banshee that highly depend on Gnome architecture.
— The preceding unsigned comment was added by Gary987 (talk • contribs) 12 May 2015
It would seem Banshee is no longer available in the main ebuild repository, however I get the point. I have made a note of this in the Handbook's systemd section (Handbook:Parts/Blocks/Systemd). Thanks for the tip! --Maffblaster (talk) 03:32, 5 March 2017 (UTC)
404 link on Introduction[edit source]
Talk status
This discussion is done.
The link to the Gentoo AMD64 project site (https://www.gentoo.org/proj/en/base/amd64/), on the Hardware Requirements section of the Introduction, leads to a 404 error. — The preceding unsigned comment was added by Rrzippert (talk • contribs) 3 August 2015
Link has been long since fixed. Thanks! --Maffblaster (talk) 22:28, 13 January 2017 (UTC)
Minor typo & systemd creep[edit source]
Talk status
This discussion is done.
Correct "on a amd64" to "on an amd64" if possible.
I'm here to do a clean openRC installation. Let's keep systemd in check.
The "--make-rslave" operation creeps in without mention of it being optional, if it is, and without yet mention that it is because of systemd.
If these operations are unnecessary without systemd, then please move the "--make-rslave" operations into, and/or under, the note. For example:
Note
The --make-rslave operations are needed for systemd support later in the installation.
root #mount --make-rslave /mnt/gentoo/sys
root #mount --make-rslave /mnt/gentoo/dev
It is in intention to support systemd as an optional init system. systemd is probably, at the time of writing, the most popular system in existence, although the majority of Gentoo users probably are not using it. The --make-rslave option passed to mount does not conflict with any options needed for those choosing either init system (OpenRC or systemd), and therefore is fine either way. Typos are corrected by now. --Maffblaster (talk) 01:34, 17 January 2017 (UTC)
Re: Banshee[edit source]
Talk status
This discussion is done.
Banshee is software that is loaded with commercial interests, namely Amazon.com. If it has dependency issues then those should be dealt with at the Banshee development site, not here.
Agreed. --Maffblaster (talk) 01:35, 17 January 2017 (UTC)
Configuring the network[edit source]
Talk status
This discussion is done.
The Handbook heavily relies on the assumption that the network interface name is eth0, which is highly unlikely with the new udev naming rules.
Recommending the use of
root #ip link show up
from a Gentoo-based installation medium or
root #udevadm test-builtin net_id /sys/class/net/eth0 2> /dev/null
if coming from a different installation medium would allow users still unfamiliar with Gentoo to avoid errors during setup.
— The preceding unsigned comment was added by Lepaperwan (talk • contribs) 1 November 2015
Agreed...I solved this by simply running
root #touch /etc/udev/rules.d/80-net-name-slot.rules
Likely works for 95% of all users with a single network card that doesn't change slots
For the purposes of the Handbook, it shouldn't matter what the network interface is named. It's just a handle created by udev. The Handbook does mention the ip command now. I'm not sure what the point of using udevadm would get the readers? If you still feel like there's more to this discussion then re-open it. Seems like we covered all the bases. --Maffblaster (talk) 06:36, 24 January 2017 (UTC)
Installing the sources[edit source]
Talk status
This discussion is done.
root #emerge --ask sys-kernel/gentoo-sources
This command execution recommends to control its status in another terminal by doing:
root #tail -f /var/log/emerge-fetch.log
But we have previously chrooted into /mnt/gentoo/. So I suggest to specify that if we log into another terminal we should tail the file inside the mounted folder by doing:
root #tail -f /mnt/gentoo/var/log/emerge-fetch.log
Hi, I don't think instructions on how to tail the emerge-fetch.log file needs to be mentioned in the Handbook. Hopefully the reader will be able to figure this out on their own by reading the message from the gentoo-sources ebuild. If you'd like to re-open and write up a mock wording for me to copy/paste into the Handbook I will consider it! Kind regards, --Maffblaster (talk) 06:40, 24 January 2017 (UTC)
Kernel config for USB support[edit source]
Talk status
This discussion is done.
This section is out of date:
KERNEL Activating USB Support for input devices '"`UNIQ--pre-00000007-QINU`"'
I believe the relevant options have been moved to:
KERNEL Activating USB Support for input devices '"`UNIQ--pre-0000000A-QINU`"'
--Astronome (talk) 19:35, 20 July 2016 (UTC)
Hi Astronome , Thanks for the tip, and you are correct the example used in the Handbooks is certainly out of date! I have updated it! Thank you kindly for the productive feedback. Cheers, --Maffblaster (talk) 04:31, 5 March 2017 (UTC)
Kernel config for efi stub[edit source]
Talk status
This discussion is done.
Please edit configuration of kernel for efi support, else kernel not load a root file system.
KERNEL Enable built-in kernel parameters Processor type and features --->
[*] Built-in kernel command line
(root=/dev/sda2 rw)
The Handbook team is trying to move away from supporting the UEFI stub kernel functionality as it is less flexible than using a bootloader to load the kernel into memory. That kind of of stuff can be left out of the Handbook and be included in other kernel related articles around the wiki. --Maffblaster (talk) 21:13, 13 January 2017 (UTC)
Link to "other arches" on download page[edit source]
Talk status
This discussion is done.
In the "Download the media" section which discusses the "minimal installation CDs", the link to "the downloads page (recommended)" is to the "Advanced Choices and other Architectures" section of that page. Shouldn't it be to the top of the page (no section anchor) where links to download the "normal" amd64 Minimal Installation CD, LiveDVD, and Stage 3 files are to be found? - dcljr (talk) 18:32, 13 April 2016 (UTC)
The link has been updated. --Maffblaster (talk) 21:14, 13 January 2017 (UTC)
Remove Parted[edit source]
Talk status
This discussion is done.
Remove Parted from handbook! fdisk have support GPT layout, and part of coreutils (default)
I need to revise the disk section. I'll add this as a possibility to review. After reworking the disk section it parted may or may not be used. That's all I can say for now. Thanks! --Maffblaster (talk) 18:28, 13 January 2017 (UTC)
I don't see why parted should be removed if it *works great*. --Vieri (talk) 12:12, 17 February 2017 (UTC)
improve suggested partitions and use of grub-install[edit source]
Talk status
This discussion is done as of 2024-02-14.
In my opinion, the handbook (amd64) is a bit confusing regarding partitioning.
First of all, I think it should try to keep the "parted" and "fdisk" examples as coherent as possible.
Furthermore, it would be preferable (more complete) to explain how to install Gentoo to a device that can then be booted both with UEFI and Legacy BIOS. Emphasis should be put on GPT, letting go MBR.
So here are my suggestions.
1) the "fdisk alternative" described at https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Alternative:_Using_fdisk_to_partition_the_disk warns that fdisk might still have bugs when supporting GPT (-t gpt). However, it does use an example partitioning scheme with bios boot and boot (see below).
2) the "fdisk alternative" starts with this partitioning scheme:
/dev/sda1 BIOS boot partition
/dev/sda2 Boot partition
and then ends telling the user to mark partition 1 (BIOS boot) for UEFI and create partition 2 as "boot".
The end results is:
[BIOS boot] /dev/sda1 1 3 5198+ ef EFI (FAT-12/16/32)
[boot/grub] /dev/sda2 * 3 14 105808+ 83 Linux
[swap] /dev/sda3 15 81 506520 82 Linux swap
[root] /dev/sda4 82 3876 28690200 83 Linux
3) in this section (https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Applying_a_filesystem_to_a_partition) the handbook suggests to format partition 2 as ext2:
# mkfs.ext2 /dev/sda2
4) in this other section (https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Using_UEFI) the handbook *suggests* to do the following:
# mkfs.fat -F 32 /dev/sda2
This suggestion is incoherent with point 2. It also doesn't guide the user to a UEFI installation.
5) There's one thing the user should be aware of and is not clearly stated in the handbook. For a UEFI installation, the live install system (or the liveCD) must boot via UEFI, not Legacy BIOS. In fact, it can happen that the BIOS will silently fail to boot a UEFI device and switch to booting via Legacy BIOS. Also, it should be clear to the reader that the current Gentoo Minimal CD is UNABLE to boot with UEFI (work in progress). Either use the LiveDVD or another system such as SystemRescueCD. In any case, the handbook should suggest to check for the existance of /sys/firmware/efi as soon as the live system has booted.
The user cannot install to a UEFI-bootable HDD if the live medium hasn't been booted with UEFI.
In particular, the user will fail to grub-install with EFI, as suggested in the handbook.
6) The default partitioning scheme described at
https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Default_partitioning_scheme
differs with point 2 because:
[BIOS boot] /dev/sda1 (bootloader) 2M BIOS boot partition
[boot/grub or UEFI] /dev/sda2 ext2 (or fat32 if UEFI is being used) 128M Boot/EFI system partition
7) The parted instructions at https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Default:_Using_parted_to_partition_the_disk
suggest to install BIOS boot on partition 1 and boot on partition 2.
In case the user wants to boot with UEFI, the handbook suggests to set UEFI on partition 2 (boot).
This is incoherent with point 2.
8) Finally, I think it would be better if the handbook could explain how to install to a UEFI&BIOS-aware device.
There should be two scenarios:
a) user wants to boot with ONLY UEFI or ONLY Legacy BIOS:
in this case, use:
a1) if Legacy BIOS:
- boot with BIOS (not UEFI)
- check /sys/firmware/efi does not exist
- partitions:
[BIOS boot] /dev/sda1
[boot/grub] /dev/sda2 (ext2)
- filesystem:
# mkfs.ext2 /dev/sda2
# mount /dev/sda2 /boot
- install bootloader:
# grub-install /dev/sda
a2) if UEFI:
- boot with UEFI (not BIOS)
- check /sys/firmware/efi exists
- partitions:
[BIOS boot] /dev/sda1
[UEFI] /dev/sda2 (fat32)
- filesystem:
# mkfs.fat -F 32 /dev/sda2
# mount /dev/sda2 /boot
- install bootloader:
# grub-install --target=x86_64-efi --efi-directory=/boot /dev/sda
(actually, grub-install /dev/sda should be enough)
b) user wants to boot with BOTH UEFI AND Legacy BIOS:
b1) grub and efi on different partitions:
- boot with UEFI (not BIOS)
- check /sys/firmware/efi exists
- partitions:
[BIOS boot] /dev/sda1
[UEFI] /dev/sda2 (fat32)
[boot/grub] /dev/sda3 (ext2)
- filesystem:
# mkfs.fat -F 32 /dev/sda2
# mkfs.ext2 /dev/sda3
# mount /dev/sda3 /boot
# mkdir /boot/efi
# mount /dev/sda2 /boot/efi
- install bootloader:
# grub-install --target=x86_64-efi --efi-directory=/boot/efi /dev/sda
( actually, grub-install --efi-directory=/boot/efi /dev/sda should be enough)
# grub-install --target=i386-pc /dev/sda
b2) grub and efi on same partition:
- boot with UEFI (not BIOS)
- check /sys/firmware/efi exists
- partitions:
[BIOS boot] /dev/sda1
[UEFI/boot/grub] /dev/sda2 (fat32)
- filesystem:
# mkfs.fat -F 32 /dev/sda2
# mount /dev/sda2 /boot
- install bootloader:
# grub-install --target=x86_64-efi --efi-directory=/boot /dev/sda
( actually, grub-install /dev/sda should be enough)
# grub-install --target=i386-pc /dev/sda
--Vieri (talk) 11:17, 17 February 2017 (UTC)
We have moved away from supporting Hybrid MBR/GPT configuration within the handbook, due to this configuration being unnecessary, niche, and cumbersome to explain. There are other places on the wiki that may detail this setup and instructions can be enhanced there if necessary (feel free to add something if it's missing).
Installing GRUB to more than one disk is also beyond the cases covered in the handbook. We only detail a single drive installation - again, there is guidance and information other places on the wiki and within the GRUB manual. Thank you! --Maffblaster (talk) 12:24, 14 February 2024 (UTC)
EFI partition mount[edit source]
Talk status
This discussion is done as of Jan 13th 2017.
I see the Handbook mentions that Grub2 can't be used, and efibootmgr should be used instead. However, using grub2 is a suitable option.
The EFI partition should be mounted to /boot/efi:
# mkdir /mnt/gentoo/boot/efi
# mount /dev/sda1 /mnt/gentoo/boot/efi
ILMostro (talk)
Hi ILMostro , I saw your message in IRC. We are still very much active in monitoring and updating the wiki, although we're not always able to immediately respond on IRC. I agree, GRUB2 is a suitable option for EFI on Gentoo. I use it myself. With that being said we have to be careful with how much we try to support in the various handbooks. The purpose of it is to help users get Gentoo installed; not to walk them through all the configuration options (Gentoo is far too flexible for that!). :)
I don't remember the Handbook ever saying GRUB2 can't be used for EFI on amd64 systems, but I will take a look and fix anything that doesn't seem right. Kind regards, --Maffblaster (talk) 02:05, 21 June 2016 (UTC)
GPT or MBR[edit source]
Talk status
This discussion is done as of 2022-02-22.
It's definitely possible to dual-boot with Windows using GPT on a BIOS-based system. I'm able to do so with the following GRUB entry:
FILE /etc/grub.d/40_customDual-boot with Windows '"`UNIQ--pre-0000000F-QINU`"'
--Astronome (talk) 03:17, 21 January 2017 (UTC)
Hi Astronome, if you're serious about having your discussions looked after please remember to use the {{Talk}} template. We can't really track what work is left for us to do without them.
With that being said, to confirm: does the disk have a GPT partition table, or is it an MSDOS table? Also, is your copy of Windows installed in MSDOS mode? Kind regards, --Maffblaster (talk) 06:47, 24 January 2017 (UTC)
Revisiting here... Closing discussion due to no reply from author. --Maffblaster (talk) 08:50, 22 February 2022 (UTC)
Mounting the necessary filesystems[edit source]
Talk status
This discussion is done as of Jan 26th 2017.
I've always found this part confusing. Should this
root #mount -t proc proc /mnt/gentoo/proc
be changed to this?
root #mount -t proc /proc /mnt/gentoo/proc
Otherwise, if you're following the instructions exactly, your PWD will be /mnt/gentoo and you'll be mounting /mnt/gentoo/proc to itself. --Astronome (talk) 19:55, 21 January 2017 (UTC)
Yes, it's a good point. We should have the / on the second mention of proc. I'll update this. --Maffblaster (talk) 06:47, 24 January 2017 (UTC)
This assertion is wrong (but doesn't hurt). man mount:
The proc filesystem is not associated with a special device, and when mounting it, an arbitrary keyword, such as proc can be used instead of a device specification. (The customary choice none is less fortunate: the error message `none busy' from umount can be confusing.).
It was probably "proc" due to it being suggested to use that in the man page as that arbitrary keyword (but you can use "asdf" or whatever, pretty much anything except for "none'). That argument is the first one - that of the device node to use, -t proc doesn't have one, so it's ignored (unless special "none" is encountered). In "mount -t proc proc /mnt/gentoo/proc" the first "proc" is the type given with -t, "proc" is the device node and /mnt/gentoo/proc is the path - there is no proc path and no way this would have mounted itself (device node != directory). --Leio (talk) 15:26, 26 January 2017 (UTC)
That's funny, I was editing this page at the same time as you to say the same thing :) --Astronome (talk) 15:52, 26 January 2017 (UTC)
So it doesn't really matter. It could be proc or it could be /proc. mount doesn't care. If there's nothing left to do here please close this discussion. --Maffblaster (talk) 21:52, 26 January 2017 (UTC)
Well fine. --Astronome (talk) 02:29, 27 January 2017 (UTC)
GPG verification when behind a firewall[edit source]
Talk status
This discussion is done.
If the default gpg port cannot be opened in the firewall then you might want to use something like:
root #gpg --keyserver hkp://hkps.pool.sks-keyservers.net:80 --recv-keys 0xBB572E0E2D182910
BTW the user can also specify any other keyserver such as:
hkp://keyserver.ubuntu.com:80
This may be useful when some servers don't respond.
The following handbook section could be updated to reflect this:
Handbook:AMD64/Full/Installation#Linux_based_verification
--Vieri (talk) 16 February 2017
Hi Vieri , I'm rocking gpg version 2.1.19 and it would seem the syntax you used to specify a specific port has been deprecated. I couldn't get it to work by trying your example above. Also, from the man page (man 1 gpg), "The scheme is the type of keyserver: "hkp" for the HTTP (or compatible) keyservers". This indicates to me that HTTP is the default, so there is no need to specify port 80 in the example... Kind regards, --Maffblaster (talk) 03:59, 5 March 2017 (UTC)
No, hkp uses port 11371 by default. What the OP neglected to mention is that not all keyservers support port 80. The general solution is to use the p80 pool at hkp://p80.pool.sks-keyservers.net:80. However, I think that it would be more preferable still to use the hkps pool at hkps://hkps.pool.sks-keyservers.net. This has the advantage of using HTTPS on the standard port of 443. Incidentally, portage and gemato are both inflexible in this regard. --kerframil (talk) 02:36, 21 July 2018 (UTC)
Thanks, added that URI. --Grknight (talk) 15:30, 7 November 2018 (UTC)
DavidC improvements section[edit source]
As I'm reading through this doco I'm writing a bunch of suggestions, some of which are sure to be misguided, so the only discussion I require is "yes/no/maybe later". Hopefully some of this helps but I know not all of it will be implemented.
Preparing the disk[edit source]
Talk status
This discussion is done.
Prior to "Introduction to block devices" it would be nice if there was a title that said something like preparing the disk, since that is what is referred to above in the document. DavidC (talk) 17:57, 18 November 2017 (UTC)
This would require a significant amount of work. It would require a lower-level heading than the one used for "Introduction to block devices" and subsequent sections. Since there is none, the headings for all sections on the page would have to be shifted up one level, but that change would automatically get copied to the non-full installation parts of the handbook (e.g. Handbook:AMD64/Installation/Disks).
The non-full installation parts should get priority since
<translate>
</translate>
takes the user there. Thus, taking no action is the best option here.
I'm closing this discussion since I don't know whether you will respond. If you do, feel free to reopen it. Glibg10b (talk) 07:39, 1 April 2024 (UTC)
Open more than one chroot terminal[edit source]
Talk status
This discussion is done as of October 29th, 2021.
I'd probably get the user to chroot a couple terminals at least because then they would be able to do some reading while something is going on it another window, or easily compare say the output of lspci to what they're inputting in makeconfig, etc. DavidC (talk) 15:13, 19 November 2017 (UTC)
We mention screen for this purpose, but I have also have added a tip to explictly show readers how to switch between the seven available terminals: Special:Diff/1015767/024956. --Maffblaster (talk) 20:35, 29 October 2021 (UTC)
This and that[edit source]
Talk status
This discussion is done as of 2024-02-14.
I am lost at Handbook:AMD64/Full/Installation#Introduction_to_block_devices. Looking at "If that is the case, it might be..." I understand what "that" case is, but when it says "In this case, launch..." I do not understand what "this" case is. Perhaps after "using the MBR format." A sentence could be added directing MBR users to "Default partitioning scheme". Someone suggested this be split into 3 sections "bios with mbr, efi with gpt, bios with gpt" DavidC (talk) 19:37, 18 November 2017 (UTC)
I am overwhelmed with mirrors[edit source]
Talk status
This discussion is done as of October 29th, 2021.
"links https://www.gentoo.org/downloads/mirrors/" So if you follow the first link for Canadians, you end up going to a LONG list of files and it's not entirely clear what to download (even if you follow it all the way to Gentoo, so it's probably best just to link people straight to https://gentoo.org/downloads/. DavidC (talk) 19:58, 18 November 2017 (UTC)
If you are referring this section, there are no instructions to download anything from the mirrors directly. It's just giving an example on how to use links to determine what mirror URLs are avaialble. No where in the instruction are you supposed to download anything in this section. --Maffblaster (talk) 20:35, 29 October 2021 (UTC)
Variables[edit source]
Talk status
This discussion is done as of October 29th, 2021.
"variables which impacts" --> "impact" DavidC (talk) 20:02, 18 November 2017 (UTC)
Fixed. See Special:Diff/1023606/1024968. --Maffblaster (talk) 20:35, 29 October 2021 (UTC)
Path differences for examples[edit source]
Talk status
This discussion is done as of October 29th, 2021.
"To keep the settings, Portage reads in the /etc/portage/make.conf file" ok so this line is talking about what is currently /mnt/gentoo/etc/... but the light blue section afterwards refers to /mnt/gentoo/usr/share/... explicitly, as does the black section starting with nano -w, so there should be consistency across all those three things. DavidC (talk) 20:14, 18 November 2017 (UTC)
I seems like you're splitting hairs on ths one. The tip is about Portage. The path is different because you're operating out of an extracted state3 during this section of the handbook. I'll just change it to make.conf to avoid confusion. See Special:Diff/1023606/1024968. --Maffblaster (talk) 20:35, 29 October 2021 (UTC)
Custom prompt is reverted[edit source]
Talk status
This discussion is done.
After "root #eselect locale set 9", the shell tells the user to run something like . /etc/profile, which results in removing the custom prompt "(chroot)" and it's a little disconcerting. So I think the best option here is to tell the user not to follow the prompting of the shell before giving the set 9 command. Further, afterwards there is a black box that has maybe 3 commands in it separated by & and those commands could easily be given as a series of single lines, which would probably be better. DavidC (talk) 14:53, 19 November 2017 (UTC)
This has been solved. Closing. Glibg10b (talk) 09:53, 1 April 2024 (UTC)
Current USE flags in profile[edit source]
Talk status
This discussion is done.
In the USE flag section, it might be a good idea to suggest something like <profile_file> | grep ^USE >> <make.conf> so that people can see their profile USE flags at the same time that they're putting in their custom values; they would have to comment it out if they did that, though. DavidC (talk) 15:08, 19 November 2017 (UTC)
I really like the idea of explaining how to view USE flags already set in the profile. I'll implement something like this soon. --Maffblaster (talk) 20:35, 29 October 2021 (UTC)
Completed (Handbook:AMD64/Full/Installation#Optional:_Configuring_the_USE_variable). Closing. Glibg10b (talk) 09:54, 1 April 2024 (UTC)
devtmpfs cannot be unselected[edit source]
Talk status
This discussion is done.
" [*] Maintain a devtmpfs filesystem to mount at /dev" You can not unselect this, therefore this section can be removed safely. DavidC (talk) 15:19, 19 November 2017 (UTC)
We'll safely leave it. --Maffblaster (talk) 09:28, 20 February 2023 (UTC)
Blank line requested[edit source]
Talk status
This discussion is done.
"Executable file formats / Emulations --->" Put a blank line prior to this to strongly indicate that it's denested. DavidC (talk) 16:04, 19 November 2017 (UTC)
I no longer see that line in this AMD64/Full/Installation page, so can this be closed DavidC  ? Thanks -- Ris (talk) 16:57, 1 March 2024 (UTC)
GRUB install issue[edit source]
Talk status
This discussion is done as of 2023-02-20.
For grub-install with EFI, please include the 2 steps for EFI vars. Otherwise, grub-install will silently fail. From Efibootmgr#Creating_a_boot_entry:
root #mount | grep efivars
efivarfs on /sys/firmware/efi/efivars type efivarfs (ro,relatime)
root #mount -o remount,rw -t efivarfs efivarfs /sys/firmware/efi/efivars
— The preceding unsigned comment was added by Dman777 (talk • contribs) 19:27, December 18, 2017
This should NOT be the case when using official Gentoo installation live images. We do cover that in the GRUB install section, we just don't currently specify the --type option, as your example does. --Maffblaster (talk) 09:39, 20 February 2023 (UTC)
Fix nesting[edit source]
Talk status
This discussion is done as of 14 July 2022.
"Pseudo Filesystems --->" needs to be nested one step inwards. DavidC (talk) 16:10, 19 November 2017 (UTC)
A fix was provided (Special:Diff/1018950/1023486). --Blacki (talk) 04:44, 14 July 2022 (UTC)
Combine all kernel sections[edit source]
Talk status
This discussion is done as of October 29th, 2021.
There seems to be a lot of random traversal of the kernel configuration. It would be beneficial to group all sections together which access similar hierarchies. It would probably also be good to include the hotkeys in this menu so that the user can traverse it more quickly. DavidC (talk) 16:14, 19 November 2017 (UTC)
I do not believe it would suit well to have all kernel sections together in one big block. Regarding hotkeys: we have other articles availabe on the wiki that mention hotkeys (see Kernel articles)... This is not something I think is worth adding to the basic installation requirements for Gentoo. --Maffblaster (talk) 20:35, 29 October 2021 (UTC)
How to read documenation file[edit source]
Talk status
This discussion is done as of 14 July 2022.
"Please read /usr/share/doc/netifrc-*/net.example.bz2 for a list of all available options." The document does not say how to do this. Also in this section, observe: " But don't fear, everything is explained below." This breaks style, but I like it. DavidC (talk) 20:01, 19 November 2017 (UTC)
A little bit higher in the document, it was already mentionned that net.example.bz2 "can be read using bzless". --Blacki (talk) 10:10, 14 July 2022 (UTC)
CFLAGS Section links[edit source]
Talk status
This discussion is done as of October 27, 2021.
Suggestion: The CFLAGS Section
might as well contain additional references to GCC_optimization and CPU_FLAGS_X86?
These wiki pages seem more comprehensible for n00bs like me than the referenced gnu manual.
User:atari800 (2019/02/19 11:54am)
The GCC optimization and Safe CFLAGS articles are now listed in a tip at the bottom of the section. --Maffblaster (talk) 22:52, 27 October 2021 (UTC)
delete: Prior to Windows 7[edit source]
Talk status
This discussion is done as of October 27, 2021.
Suggestion: Delete section to explain how to burn CD on a 10 year old windows system. If someone still runs it, he/she knows how to burn CD's. --Jonas Stein (talk) 01:06, 16 May 2020 (UTC)
Jonas Stein (Jstein) , thank you for reporting. This was fixed a while back. We now cover Windows 7 and above as a 'catch all' to include Windows 10 and 11. See Handbook:AMD64/Full/Installation#Burning_with_Microsoft_Windows_7_and_above. Thank you! --Maffblaster (talk) 21:08, 27 October 2021 (UTC)
Reiserfs[edit source]
Talk status
This discussion is done.
Reiserfs is included in mainline Linux--Nikitastepanov (talk) 11:26, 30 August 2020 (UTC)
Duplicate of Handbook Talk:Parts/Installation/Disks#Reiserfs (as this page inherits that article) --Grknight (talk) 13:19, 31 August 2020 (UTC)' |
Parsed HTML source of the new revision (new_html) | '<div class="mw-parser-output"><p>The following sections are completed discussions previously found on the <a href="/wiki/Handbook_Talk:AMD64/Full/Installation" title="Handbook Talk:AMD64/Full/Installation">Handbook Talk:AMD64/Full/Installation</a> page. They have been moved here for archival purposes.
</p>
<div id="toc" class="toc" role="navigation" aria-labelledby="mw-toc-heading"><input type="checkbox" role="button" id="toctogglecheckbox" class="toctogglecheckbox" style="display:none" /><div class="toctitle" lang="en" dir="ltr"><h2 id="mw-toc-heading">Contents</h2><span class="toctogglespan"><label class="toctogglelabel" for="toctogglecheckbox"></label></span></div>
<ul>
<li class="toclevel-1 tocsection-1"><a href="#5.4_Viewing_Documentation_During_Install"><span class="tocnumber">1</span> <span class="toctext">5.4 Viewing Documentation During Install</span></a></li>
<li class="toclevel-1 tocsection-2"><a href="#Choosing_the_right_profile"><span class="tocnumber">2</span> <span class="toctext">Choosing the right profile</span></a></li>
<li class="toclevel-1 tocsection-3"><a href="#Optional:_Selecting_mirrors"><span class="tocnumber">3</span> <span class="toctext">Optional: Selecting mirrors</span></a></li>
<li class="toclevel-1 tocsection-4"><a href="#Unpacking_the_stage_tarball"><span class="tocnumber">4</span> <span class="toctext">Unpacking the stage tarball</span></a></li>
<li class="toclevel-1 tocsection-5"><a href="#Setting_the_date_and_time"><span class="tocnumber">5</span> <span class="toctext">Setting the date and time</span></a></li>
<li class="toclevel-1 tocsection-6"><a href="#Typo_.22there_are_e_a.22"><span class="tocnumber">6</span> <span class="toctext">Typo "there are e a"</span></a></li>
<li class="toclevel-1 tocsection-7"><a href="#systemd_needed_for_Banshee_Too.21"><span class="tocnumber">7</span> <span class="toctext">systemd needed for Banshee Too!</span></a></li>
<li class="toclevel-1 tocsection-8"><a href="#404_link_on_Introduction"><span class="tocnumber">8</span> <span class="toctext">404 link on Introduction</span></a></li>
<li class="toclevel-1 tocsection-9"><a href="#Minor_typo_.26_systemd_creep"><span class="tocnumber">9</span> <span class="toctext">Minor typo & systemd creep</span></a></li>
<li class="toclevel-1 tocsection-10"><a href="#Re:_Banshee"><span class="tocnumber">10</span> <span class="toctext">Re: Banshee</span></a></li>
<li class="toclevel-1 tocsection-11"><a href="#Configuring_the_network"><span class="tocnumber">11</span> <span class="toctext">Configuring the network</span></a></li>
<li class="toclevel-1 tocsection-12"><a href="#Installing_the_sources"><span class="tocnumber">12</span> <span class="toctext">Installing the sources</span></a></li>
<li class="toclevel-1 tocsection-13"><a href="#Kernel_config_for_USB_support"><span class="tocnumber">13</span> <span class="toctext">Kernel config for USB support</span></a></li>
<li class="toclevel-1 tocsection-14"><a href="#Kernel_config_for_efi_stub"><span class="tocnumber">14</span> <span class="toctext">Kernel config for efi stub</span></a></li>
<li class="toclevel-1 tocsection-15"><a href="#Link_to_.22other_arches.22_on_download_page"><span class="tocnumber">15</span> <span class="toctext">Link to "other arches" on download page</span></a></li>
<li class="toclevel-1 tocsection-16"><a href="#Remove_Parted"><span class="tocnumber">16</span> <span class="toctext">Remove Parted</span></a></li>
<li class="toclevel-1 tocsection-17"><a href="#improve_suggested_partitions_and_use_of_grub-install"><span class="tocnumber">17</span> <span class="toctext">improve suggested partitions and use of grub-install</span></a></li>
<li class="toclevel-1 tocsection-18"><a href="#EFI_partition_mount"><span class="tocnumber">18</span> <span class="toctext">EFI partition mount</span></a></li>
<li class="toclevel-1 tocsection-19"><a href="#GPT_or_MBR"><span class="tocnumber">19</span> <span class="toctext">GPT or MBR</span></a></li>
<li class="toclevel-1 tocsection-20"><a href="#Mounting_the_necessary_filesystems"><span class="tocnumber">20</span> <span class="toctext">Mounting the necessary filesystems</span></a></li>
<li class="toclevel-1 tocsection-21"><a href="#GPG_verification_when_behind_a_firewall"><span class="tocnumber">21</span> <span class="toctext">GPG verification when behind a firewall</span></a></li>
<li class="toclevel-1 tocsection-22"><a href="#DavidC_improvements_section"><span class="tocnumber">22</span> <span class="toctext">DavidC improvements section</span></a>
<ul>
<li class="toclevel-2 tocsection-23"><a href="#Preparing_the_disk"><span class="tocnumber">22.1</span> <span class="toctext">Preparing the disk</span></a></li>
<li class="toclevel-2 tocsection-24"><a href="#Open_more_than_one_chroot_terminal"><span class="tocnumber">22.2</span> <span class="toctext">Open more than one chroot terminal</span></a></li>
<li class="toclevel-2 tocsection-25"><a href="#This_and_that"><span class="tocnumber">22.3</span> <span class="toctext">This and that</span></a></li>
<li class="toclevel-2 tocsection-26"><a href="#I_am_overwhelmed_with_mirrors"><span class="tocnumber">22.4</span> <span class="toctext">I am overwhelmed with mirrors</span></a></li>
<li class="toclevel-2 tocsection-27"><a href="#Variables"><span class="tocnumber">22.5</span> <span class="toctext">Variables</span></a></li>
<li class="toclevel-2 tocsection-28"><a href="#Path_differences_for_examples"><span class="tocnumber">22.6</span> <span class="toctext">Path differences for examples</span></a></li>
<li class="toclevel-2 tocsection-29"><a href="#Custom_prompt_is_reverted"><span class="tocnumber">22.7</span> <span class="toctext">Custom prompt is reverted</span></a></li>
<li class="toclevel-2 tocsection-30"><a href="#Current_USE_flags_in_profile"><span class="tocnumber">22.8</span> <span class="toctext">Current USE flags in profile</span></a></li>
<li class="toclevel-2 tocsection-31"><a href="#devtmpfs_cannot_be_unselected"><span class="tocnumber">22.9</span> <span class="toctext">devtmpfs cannot be unselected</span></a></li>
<li class="toclevel-2 tocsection-32"><a href="#Blank_line_requested"><span class="tocnumber">22.10</span> <span class="toctext">Blank line requested</span></a></li>
<li class="toclevel-2 tocsection-33"><a href="#GRUB_install_issue"><span class="tocnumber">22.11</span> <span class="toctext">GRUB install issue</span></a></li>
<li class="toclevel-2 tocsection-34"><a href="#Fix_nesting"><span class="tocnumber">22.12</span> <span class="toctext">Fix nesting</span></a></li>
<li class="toclevel-2 tocsection-35"><a href="#Combine_all_kernel_sections"><span class="tocnumber">22.13</span> <span class="toctext">Combine all kernel sections</span></a></li>
<li class="toclevel-2 tocsection-36"><a href="#How_to_read_documenation_file"><span class="tocnumber">22.14</span> <span class="toctext">How to read documenation file</span></a></li>
</ul>
</li>
<li class="toclevel-1 tocsection-37"><a href="#CFLAGS_Section_links"><span class="tocnumber">23</span> <span class="toctext">CFLAGS Section links</span></a></li>
<li class="toclevel-1 tocsection-38"><a href="#delete:_Prior_to_Windows_7"><span class="tocnumber">24</span> <span class="toctext">delete: Prior to Windows 7</span></a></li>
<li class="toclevel-1 tocsection-39"><a href="#Reiserfs"><span class="tocnumber">25</span> <span class="toctext">Reiserfs</span></a></li>
</ul>
</div>
<h2><span class="mw-headline" id="5.4_Viewing_Documentation_During_Install">5.4 Viewing Documentation During Install</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=1" title="Edit section: 5.4 Viewing Documentation During Install">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done.</span></div>
</div>
<p>The documentation recommends creating a new user account and logging in on a separate virtual tty to load links with the install docs, then switching back and forth between a command tty and the docs tty. This will work but it's clumsy, slow, and aggravating. A better solution is to use "screen" which is already included on the minimal install CD. The docs can be viewed side-by-side with one or more command shells on the same terminal with the following commands:
</p>
<ul><li>screen links Gentoo.org</li>
<li>^A ^C</li>
<li>^A | (for vertical split) or ^A S (for horizontal split)</li></ul>
<p>Each "screen" can be split further into more windows. I would suggest including these instructions in the install docs in addition to or instead of the virtual terminal switching method.
</p><p><small>— The preceding <a href="/wiki/Help:Signatures" title="Help:Signatures">unsigned</a> comment was added by <a href="/index.php?title=User:Handle2001&action=edit&redlink=1" class="new" title="User:Handle2001 (page does not exist)">Handle2001</a> (<a href="/index.php?title=User_talk:Handle2001&action=edit&redlink=1" class="new" title="User talk:Handle2001 (page does not exist)">talk</a> • <a href="/wiki/Special:Contributions/Handle2001" title="Special:Contributions/Handle2001">contribs</a>) 21 July 2016</small>
</p>
<dl><dd>I can make mention of this as an option and add a link to our article on <a href="/wiki/Screen" title="Screen">Screen</a>, although I would not summarize logging in on multiple tty's "clumsy, slow, and aggravating". It is the simplest way of proceeding. Screen takes knowledge that many newcomers many not immediately possess. Seasoned system admins will probably think of using screen without it being mentioned. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 22:08, 26 January 2017 (UTC)</dd></dl>
<dl><dd><dl><dd>It is now mentioned as a possibility for seasoned Linux enthusiasts (who know how to use it). Closing discussion. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 22:59, 26 January 2017 (UTC)</dd></dl></dd></dl>
<h2><span class="mw-headline" id="Choosing_the_right_profile">Choosing the right profile</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=2" title="Edit section: Choosing the right profile">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done.</span></div>
</div>
<p>While not a recommendation, this section suggests using "no-multilib" for a pure 64-bit environment. I think this should be followed by the disclaimer on the AMD64 FAQ:
</p>
<div class="alert alert-danger gw-box" style="padding-top: 8px; padding-bottom: 8px;"><strong><i class="fa fa-exclamation-triangle"></i> Warning</strong><br />Switching from a no-multilib to a multilib-enabled profile is currently not supported (<a rel="nofollow" class="external text" href="http://jkroon.blogs.uls.co.za/it/gentoo/gentoo-converting-no-multilib-to-multilib">conversion hints</a>), so think over your decision twice before you use the no-multilib profile.</div>
<p>--<a href="/index.php?title=User:Astronome&action=edit&redlink=1" class="new" title="User:Astronome (page does not exist)">Astronome</a> (<a href="/index.php?title=User_talk:Astronome&action=edit&redlink=1" class="new" title="User talk:Astronome (page does not exist)">talk</a>) 23:29, 6 February 2016 (UTC)
</p>
<dl><dd>I added <a href="/wiki/Handbook:AMD64/Full/Installation#No-multilib_.28pure_64-bit.29" title="Handbook:AMD64/Full/Installation">a small section</a> noting the caveats of no-multilib. Should be better now. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 18:20, 13 January 2017 (UTC)</dd></dl>
<h2><span class="mw-headline" id="Optional:_Selecting_mirrors">Optional: Selecting mirrors</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=3" title="Edit section: Optional: Selecting mirrors">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done.</span></div>
</div>
<p>If you use >=sys-apps/portage-2.2.16, you not have to use
</p>
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>mirrorselect -i -r -o >> /mnt/gentoo/etc/portage/make.conf</code></div></div>
<p>As, the SYNC variable in make.conf is deprecated and no longer used by portage.<br />
You will should use
</p>
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>mkdir /mnt/gentoo/etc/portage/repos.conf</code></div></div>
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>cp /usr/share/portage/config/repos.conf /mnt/gentoo/etc/portage/repos.conf/gentoo.conf</code></div></div>
<p>If you want to be updated from other mirror, you can run
</p>
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>mirrorselect -i -r -o</code></div></div>
<p>select mirror and paste received URI here /mnt/gentoo/etc/portage/repos.conf/gentoo.conf in variable "sync-uri" <br />
example:<br />
sync-uri = rsync://rsync.ru.gentoo.org/gentoo-portage
</p><p>More info <a href="/wiki/Project:Portage/Sync" title="Project:Portage/Sync">Project:Portage/Sync</a> <br /><br />
P.S. Sorry my bad english.
</p><p><small>— The preceding <a href="/wiki/Help:Signatures" title="Help:Signatures">unsigned</a> comment was added by <a href="/index.php?title=User:Geronek&action=edit&redlink=1" class="new" title="User:Geronek (page does not exist)">Geronek</a> (<a href="/index.php?title=User_talk:Geronek&action=edit&redlink=1" class="new" title="User talk:Geronek (page does not exist)">talk</a> • <a href="/wiki/Special:Contributions/Geronek" title="Special:Contributions/Geronek">contribs</a>) 26 April 2015</small>
</p>
<dl><dd>The repos.conf method is <a href="/wiki/Handbook:AMD64/Full/Installation#Main_Gentoo_repository" title="Handbook:AMD64/Full/Installation">now explained</a> in the Handbook. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 18:22, 13 January 2017 (UTC)</dd></dl>
<h2><span class="mw-headline" id="Unpacking_the_stage_tarball">Unpacking the stage tarball</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=4" title="Edit section: Unpacking the stage tarball">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done.</span></div>
</div>
<p>Is "--xattrs" required on some versions of tar to keep the extended attributes when extracting the archive or is this a mistake and as the manpage says, is only used to "save the user/root xattrs to the archive" (while when extracting, one would have to specify "--no-xattrs" to bypass them). <small>— The preceding <a href="/wiki/Help:Signatures" title="Help:Signatures">unsigned</a> comment was added by <a href="/index.php?title=User:Lepaperwan&action=edit&redlink=1" class="new" title="User:Lepaperwan (page does not exist)">Lepaperwan</a> (<a href="/index.php?title=User_talk:Lepaperwan&action=edit&redlink=1" class="new" title="User talk:Lepaperwan (page does not exist)">talk</a> • <a href="/wiki/Special:Contributions/Lepaperwan" title="Special:Contributions/Lepaperwan">contribs</a>) 1 November 2015</small>
</p>
<dl><dd>Where do you see that in the GNU tar man page? Seems like bad information to me. I tested your theory using tar v1.29 and verified the <code>--xattrs</code> option must be added both for compression and extraction in order for <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">tar</span> handle extended attributes properly. See <a rel="nofollow" class="external text" href="http://www.lesbonscomptes.com/pages/extattrs.html#_archiving_and_backup">this link</a> for someone else who tested. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 06:27, 24 January 2017 (UTC)</dd></dl>
<h2><span class="mw-headline" id="Setting_the_date_and_time">Setting the date and time</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=5" title="Edit section: Setting the date and time">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done.</span></div>
</div>
<p>Is there a reason Handbook doesn't suggest "ntpdate pool.ntp.org" instead of typing date manually? <small>— The preceding <a href="/wiki/Help:Signatures" title="Help:Signatures">unsigned</a> comment was added by <a href="/index.php?title=User:Vkuzkokov&action=edit&redlink=1" class="new" title="User:Vkuzkokov (page does not exist)">Vkuzkokov</a> (<a href="/index.php?title=User_talk:Vkuzkokov&action=edit&redlink=1" class="new" title="User talk:Vkuzkokov (page does not exist)">talk</a> • <a href="/wiki/Special:Contributions/Vkuzkokov" title="Special:Contributions/Vkuzkokov">contribs</a>) 7 March 2015</small>
</p>
<dl><dd>It is less thinking and more accurate to use ntpd. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 18:23, 13 January 2017 (UTC)</dd></dl>
<h2><span id="Typo_"there_are_e_a""></span><span class="mw-headline" id="Typo_.22there_are_e_a.22">Typo "there are e a"</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=6" title="Edit section: Typo "there are e a"">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done.</span></div>
</div>
<p>There's an apparent typo on a whole series of these wiki pages.
I created and validated wiki account for myself, but alas, it doesn't (yet) give me the option to edit the pages - so apparently I can't correct it.
</p><p>Anyway, the error:
"there are e a couple"
should apparently be:
"there are a couple"
on at least these pages:
</p>
<div class="gw-box"><div class="box-caption"><span class="label" style="margin-right: .5em; background-color: #204A87">CODE</span> <strong>List of pages with typo in them</strong></div> <div class="mw-highlight mw-highlight-lang-text mw-content-ltr" dir="ltr"><pre><span></span>[[:Handbook:AMD64/Full/Installation|Handbook:AMD64/Full/Installation]]
[[:Handbook:AMD64/Installation/Stage|Handbook:AMD64/Installation/Stage]]
[[:Handbook:Alpha/Full/Installation|Handbook:Alpha/Full/Installation]]
[[:Handbook:Alpha/Full/Installation/es|Handbook:Alpha/Full/Installation/es]]
[[:Handbook:Alpha/Installation/Stage|Handbook:Alpha/Installation/Stage]]
[[:Handbook:HPPA/Full/Installation|Handbook:HPPA/Full/Installation]]
[[:Handbook:HPPA/Full/Installation/es|Handbook:HPPA/Full/Installation/es]]
[[:Handbook:HPPA/Installation/Stage|Handbook:HPPA/Installation/Stage]]
[[:Handbook:IA64/Full/Installation|Handbook:IA64/Full/Installation]]
[[:Handbook:IA64/Full/Installation/es|Handbook:IA64/Full/Installation/es]]
[[:Handbook:IA64/Installation/Stage|Handbook:IA64/Installation/Stage]]
[[:Handbook:MIPS/Full/Installation|Handbook:MIPS/Full/Installation]]
[[:Handbook:MIPS/Installation/Stage|Handbook:MIPS/Installation/Stage]]
[[:Handbook:PPC/Full/Installation|Handbook:PPC/Full/Installation]]
[[:Handbook:PPC/Full/Installation/es|Handbook:PPC/Full/Installation/es]]
[[:Handbook:PPC/Installation/Stage|Handbook:PPC/Installation/Stage]]
[[:Handbook:PPC64/Full/Installation|Handbook:PPC64/Full/Installation]]
[[:Handbook:PPC64/Full/Installation/es|Handbook:PPC64/Full/Installation/es]]
[[:Handbook:PPC64/Installation/Stage|Handbook:PPC64/Installation/Stage]]
[[:Handbook:Parts/Full/Installation|Handbook:Parts/Full/Installation]]
[[:Handbook:Parts/Installation/Stage|Handbook:Parts/Installation/Stage]]
[[:Handbook:SPARC/Full/Installation|Handbook:SPARC/Full/Installation]]
[[:Handbook:SPARC/Full/Installation/es|Handbook:SPARC/Full/Installation/es]]
[[:Handbook:SPARC/Installation/Stage|Handbook:SPARC/Installation/Stage]]
[[:Handbook:X86/Full/Installation|Handbook:X86/Full/Installation]]
[[:Handbook:X86/Installation/Stage|Handbook:X86/Installation/Stage]]
[[:Handbook:X86/Installation/Stage/es|Handbook:X86/Installation/Stage/es]]
</pre></div></div>
<p><b>(Above posted by Michael Paoli, fixed for wikification)</b>
</p>
<dl><dd>Thanks, corrected. --<a href="/wiki/User:SwifT" title="User:SwifT">SwifT</a> (<a href="/wiki/User_talk:SwifT" title="User talk:SwifT">talk</a>) 14:41, 27 December 2014 (UTC)</dd></dl>
<h2><span id="systemd_needed_for_Banshee_Too!"></span><span class="mw-headline" id="systemd_needed_for_Banshee_Too.21">systemd needed for Banshee Too!</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=7" title="Edit section: systemd needed for Banshee Too!">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done.</span></div>
</div>
<p>About the optional systemd and Gnome, could you mention that systemd is also required for programs like Banshee that highly depend on Gnome architecture.
<small>— The preceding <a href="/wiki/Help:Signatures" title="Help:Signatures">unsigned</a> comment was added by <a href="/index.php?title=User:Gary987&action=edit&redlink=1" class="new" title="User:Gary987 (page does not exist)">Gary987</a> (<a href="/index.php?title=User_talk:Gary987&action=edit&redlink=1" class="new" title="User talk:Gary987 (page does not exist)">talk</a> • <a href="/wiki/Special:Contributions/Gary987" title="Special:Contributions/Gary987">contribs</a>) 12 May 2015</small>
</p>
<dl><dd>It would seem Banshee is no longer available in the main ebuild repository, however I get the point. I have made a note of this in the Handbook's systemd section (<a href="/wiki/Handbook:Parts/Blocks/Systemd" title="Handbook:Parts/Blocks/Systemd">Handbook:Parts/Blocks/Systemd</a>). Thanks for the tip! --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 03:32, 5 March 2017 (UTC)</dd></dl>
<h2><span class="mw-headline" id="404_link_on_Introduction">404 link on Introduction</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=8" title="Edit section: 404 link on Introduction">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done.</span></div>
</div>
<p>The link to the Gentoo AMD64 project site (<a rel="nofollow" class="external free" href="https://www.gentoo.org/proj/en/base/amd64/">https://www.gentoo.org/proj/en/base/amd64/</a>), on the Hardware Requirements section of the Introduction, leads to a 404 error. <small>— The preceding <a href="/wiki/Help:Signatures" title="Help:Signatures">unsigned</a> comment was added by <a href="/index.php?title=User:Rrzippert&action=edit&redlink=1" class="new" title="User:Rrzippert (page does not exist)">Rrzippert</a> (<a href="/index.php?title=User_talk:Rrzippert&action=edit&redlink=1" class="new" title="User talk:Rrzippert (page does not exist)">talk</a> • <a href="/wiki/Special:Contributions/Rrzippert" title="Special:Contributions/Rrzippert">contribs</a>) 3 August 2015</small>
</p>
<dl><dd>Link has been long since fixed. Thanks! --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 22:28, 13 January 2017 (UTC)</dd></dl>
<h2><span id="Minor_typo_&_systemd_creep"></span><span class="mw-headline" id="Minor_typo_.26_systemd_creep">Minor typo & systemd creep</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=9" title="Edit section: Minor typo & systemd creep">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done.</span></div>
</div>
<p>Correct "on a amd64" to "on an amd64" if possible.
</p><p>I'm here to do a clean openRC installation. Let's keep systemd in check.
</p><p>The "--make-rslave" operation creeps in without mention of it being optional, if it is, and without yet mention that it is because of systemd.
</p><p>If these operations are unnecessary without systemd, then please move the "--make-rslave" operations into, and/or under, the note. For example:
</p><p><b>Note</b><br />
The --make-rslave operations are needed for systemd support later in the installation.
</p>
<pre>root #mount --make-rslave /mnt/gentoo/sys
root #mount --make-rslave /mnt/gentoo/dev
</pre>
<dl><dd>It is in intention to support systemd as an <i>optional</i> init system. systemd is probably, at the time of writing, the <i>most popular</i> system in existence, although the majority of Gentoo users probably are not using it. The <code>--make-rslave</code> option passed to <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">mount</span> does not conflict with any options needed for those choosing either init system (OpenRC or systemd), and therefore is fine either way. Typos are corrected by now. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 01:34, 17 January 2017 (UTC)</dd></dl>
<h2><span class="mw-headline" id="Re:_Banshee">Re: Banshee</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=10" title="Edit section: Re: Banshee">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done.</span></div>
</div>
<p>Banshee is software that is loaded with commercial interests, namely Amazon.com. If it has dependency issues then those should be dealt with at the Banshee development site, not here.
</p>
<dl><dd>Agreed. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 01:35, 17 January 2017 (UTC)</dd></dl>
<h2><span class="mw-headline" id="Configuring_the_network">Configuring the network</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=11" title="Edit section: Configuring the network">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done.</span></div>
</div>
<p>The Handbook heavily relies on the assumption that the network interface name is eth0, which is highly unlikely with the new udev naming rules.
Recommending the use of
</p>
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>ip link show up</code></div></div>
<p>from a Gentoo-based installation medium or
</p>
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>udevadm test-builtin net_id /sys/class/net/eth0 2> /dev/null</code></div></div>
<p>if coming from a different installation medium would allow users still unfamiliar with Gentoo to avoid errors during setup.
</p><p><small>— The preceding <a href="/wiki/Help:Signatures" title="Help:Signatures">unsigned</a> comment was added by <a href="/index.php?title=User:Lepaperwan&action=edit&redlink=1" class="new" title="User:Lepaperwan (page does not exist)">Lepaperwan</a> (<a href="/index.php?title=User_talk:Lepaperwan&action=edit&redlink=1" class="new" title="User talk:Lepaperwan (page does not exist)">talk</a> • <a href="/wiki/Special:Contributions/Lepaperwan" title="Special:Contributions/Lepaperwan">contribs</a>) 1 November 2015</small>
</p>
<dl><dd>Agreed...I solved this by simply running</dd>
<dd><div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root <span style="color:royalblue;">#</span></code><span class="tripleclick-separator"></span><code>touch /etc/udev/rules.d/80-net-name-slot.rules</code></div></div></dd>
<dd>Likely works for 95% of all users with a single network card that doesn't change slots</dd></dl>
<dl><dd><dl><dd>For the purposes of the Handbook, it shouldn't matter what the network interface is named. It's just a handle created by udev. The Handbook <a href="/wiki/Handbook:AMD64/Full/Installation#ip_command" title="Handbook:AMD64/Full/Installation">does mention</a> the <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">ip</span> command now. I'm not sure what the point of using <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">udevadm</span> would get the readers? If you still feel like there's more to this discussion then re-open it. Seems like we covered all the bases. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 06:36, 24 January 2017 (UTC)</dd></dl></dd></dl>
<h2><span class="mw-headline" id="Installing_the_sources">Installing the sources</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=12" title="Edit section: Installing the sources">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done.</span></div>
</div>
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>emerge --ask sys-kernel/gentoo-sources</code></div></div>
<p>This command execution recommends to control its status in another terminal by doing:
</p>
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>tail -f /var/log/emerge-fetch.log</code></div></div>
<p>But we have previously chrooted into /mnt/gentoo/. So I suggest to specify that if we log into another terminal we should tail the file inside the mounted folder by doing:
</p>
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>tail -f /mnt/gentoo/var/log/emerge-fetch.log</code></div></div>
<dl><dd>Hi, I don't think instructions on how to <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">tail</span> the <span style="font-family: monospace; font-size: 95%; color: #3c763d; font-weight: 600;">emerge-fetch.log</span> file needs to be mentioned in the Handbook. Hopefully the reader will be able to figure this out on their own by reading the message from the gentoo-sources ebuild. If you'd like to re-open and write up a mock wording for me to copy/paste into the Handbook I will consider it! Kind regards, --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 06:40, 24 January 2017 (UTC)</dd></dl>
<h2><span class="mw-headline" id="Kernel_config_for_USB_support">Kernel config for USB support</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=13" title="Edit section: Kernel config for USB support">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done.</span></div>
</div>
<p>This section is out of date:
</p>
<div class="box-caption"><span class="label" style="margin-right: .5em; background-color: #4E9A06">KERNEL</span> <strong>Activating USB Support for input devices</strong></div> <div class="mw-highlight mw-highlight-lang-text mw-content-ltr" dir="ltr"><pre><span></span>'"`UNIQ--pre-00000007-QINU`"'
</pre></div>
<p>I believe the relevant options have been moved to:
</p>
<div class="box-caption"><span class="label" style="margin-right: .5em; background-color: #4E9A06">KERNEL</span> <strong>Activating USB Support for input devices</strong></div> <div class="mw-highlight mw-highlight-lang-text mw-content-ltr" dir="ltr"><pre><span></span>'"`UNIQ--pre-0000000A-QINU`"'
</pre></div>
<p>--<a href="/index.php?title=User:Astronome&action=edit&redlink=1" class="new" title="User:Astronome (page does not exist)">Astronome</a> (<a href="/index.php?title=User_talk:Astronome&action=edit&redlink=1" class="new" title="User talk:Astronome (page does not exist)">talk</a>) 19:35, 20 July 2016 (UTC)
</p>
<dl><dd>Hi <a href="/index.php?title=User:Astronome&action=edit&redlink=1" class="new" title="User:Astronome (page does not exist)">Astronome <i class="fa fa-user"></i></a>, Thanks for the tip, and you are correct the example used in the Handbooks is certainly out of date! I have updated it! Thank you kindly for the productive feedback. Cheers, --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 04:31, 5 March 2017 (UTC)</dd></dl>
<h2><span class="mw-headline" id="Kernel_config_for_efi_stub">Kernel config for efi stub</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=14" title="Edit section: Kernel config for efi stub">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done.</span></div>
</div>
<p>Please edit configuration of kernel for efi support, else kernel not load a root file system.
</p>
<div class="box-caption"><span class="label" style="margin-right: .5em; background-color: #4E9A06">KERNEL</span> <strong>Enable built-in kernel parameters</strong></div> <div class="mw-highlight mw-highlight-lang-text mw-content-ltr" dir="ltr"><pre><span></span>Processor type and features --->
[*] Built-in kernel command line
(root=/dev/sda2 rw)
</pre></div>
<dl><dd>The <a href="/wiki/Project:Handbook" title="Project:Handbook">Handbook</a> team is trying to move away from supporting the UEFI stub kernel functionality as it is less flexible than using a bootloader to load the kernel into memory. That kind of of stuff can be <i>left out</i> of the Handbook and be included in other kernel related articles around the wiki. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 21:13, 13 January 2017 (UTC)</dd></dl>
<h2><span id="Link_to_"other_arches"_on_download_page"></span><span class="mw-headline" id="Link_to_.22other_arches.22_on_download_page">Link to "other arches" on download page</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=15" title="Edit section: Link to "other arches" on download page">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done.</span></div>
</div>
<p>In the "<a href="/wiki/Handbook:AMD64/Full/Installation#Download_the_media" title="Handbook:AMD64/Full/Installation">Download the media</a>" section which discusses the "minimal installation CDs", the link to "the <a rel="nofollow" class="external text" href="//www.gentoo.org/downloads/#other-arches">downloads page</a> (recommended)" is to the "Advanced Choices and other Architectures" section of that page. Shouldn't it be to the top of the page (no section anchor) where links to download the "normal" amd64 Minimal Installation CD, LiveDVD, and Stage 3 files are to be found? - <a href="/wiki/User:Dcljr" title="User:Dcljr">dcljr</a> (<a href="/wiki/User_talk:Dcljr" title="User talk:Dcljr">talk</a>) 18:32, 13 April 2016 (UTC)
</p>
<dl><dd>The link has been updated. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 21:14, 13 January 2017 (UTC)</dd></dl>
<h2><span class="mw-headline" id="Remove_Parted">Remove Parted</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=16" title="Edit section: Remove Parted">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done.</span></div>
</div>
<p>Remove Parted from handbook! fdisk have support GPT layout, and part of coreutils (default)
</p>
<dl><dd>I need to revise the disk section. I'll add this as a <i>possibility</i> to review. After reworking the disk section it parted may or may not be used. That's all I can say for now. Thanks! --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 18:28, 13 January 2017 (UTC)</dd></dl>
<dl><dd>I don't see why parted should be removed if it *works great*. --<a href="/index.php?title=User:Vieri&action=edit&redlink=1" class="new" title="User:Vieri (page does not exist)">Vieri</a> (<a href="/index.php?title=User_talk:Vieri&action=edit&redlink=1" class="new" title="User talk:Vieri (page does not exist)">talk</a>) 12:12, 17 February 2017 (UTC)</dd></dl>
<h2><span class="mw-headline" id="improve_suggested_partitions_and_use_of_grub-install">improve suggested partitions and use of grub-install</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=17" title="Edit section: improve suggested partitions and use of grub-install">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done as of 2024-02-14.</span></div>
</div>
<p>In my opinion, the handbook (amd64) is a bit confusing regarding partitioning.
</p><p>First of all, I think it should try to keep the "parted" and "fdisk" examples as coherent as possible.
Furthermore, it would be preferable (more complete) to explain how to install Gentoo to a device that can then be booted both with UEFI and Legacy BIOS. Emphasis should be put on GPT, letting go MBR.
</p><p>So here are my suggestions.
</p><p>1) the "fdisk alternative" described at <a rel="nofollow" class="external free" href="https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Alternative:_Using_fdisk_to_partition_the_disk">https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Alternative:_Using_fdisk_to_partition_the_disk</a> warns that fdisk might still have bugs when supporting GPT (-t gpt). However, it does use an example partitioning scheme with bios boot and boot (see below).
</p><p>2) the "fdisk alternative" starts with this partitioning scheme:
</p>
<pre> /dev/sda1 BIOS boot partition
/dev/sda2 Boot partition
</pre>
<p>and then ends telling the user to mark partition 1 (BIOS boot) for UEFI and create partition 2 as "boot".
</p><p>The end results is:
</p>
<pre> [BIOS boot] /dev/sda1 1 3 5198+ ef EFI (FAT-12/16/32)
[boot/grub] /dev/sda2 * 3 14 105808+ 83 Linux
[swap] /dev/sda3 15 81 506520 82 Linux swap
[root] /dev/sda4 82 3876 28690200 83 Linux
</pre>
<p>3) in this section (<a rel="nofollow" class="external free" href="https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Applying_a_filesystem_to_a_partition">https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Applying_a_filesystem_to_a_partition</a>) the handbook suggests to format partition 2 as ext2:
</p>
<pre># mkfs.ext2 /dev/sda2
</pre>
<p>4) in this other section (<a rel="nofollow" class="external free" href="https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Using_UEFI">https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Using_UEFI</a>) the handbook *suggests* to do the following:
</p>
<pre># mkfs.fat -F 32 /dev/sda2
</pre>
<p>This suggestion is incoherent with point 2. It also doesn't guide the user to a UEFI installation.
</p><p>5) There's one thing the user should be aware of and is not clearly stated in the handbook. For a UEFI installation, the live install system (or the liveCD) must boot via UEFI, not Legacy BIOS. In fact, it can happen that the BIOS will silently fail to boot a UEFI device and switch to booting via Legacy BIOS. Also, it should be clear to the reader that the current Gentoo Minimal CD is UNABLE to boot with UEFI (work in progress). Either use the LiveDVD or another system such as SystemRescueCD. In any case, the handbook should suggest to check for the existance of /sys/firmware/efi as soon as the live system has booted.
The user cannot install to a UEFI-bootable HDD if the live medium hasn't been booted with UEFI.
In particular, the user will fail to grub-install with EFI, as suggested in the handbook.
</p><p>6) The default partitioning scheme described at
<a rel="nofollow" class="external free" href="https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Default_partitioning_scheme">https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Default_partitioning_scheme</a>
differs with point 2 because:
</p>
<pre> [BIOS boot] /dev/sda1 (bootloader) 2M BIOS boot partition
[boot/grub or UEFI] /dev/sda2 ext2 (or fat32 if UEFI is being used) 128M Boot/EFI system partition
</pre>
<p>7) The parted instructions at <a rel="nofollow" class="external free" href="https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Default:_Using_parted_to_partition_the_disk">https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Default:_Using_parted_to_partition_the_disk</a>
suggest to install BIOS boot on partition 1 and boot on partition 2.
In case the user wants to boot with UEFI, the handbook suggests to set UEFI on partition 2 (boot).
This is incoherent with point 2.
</p><p>8) Finally, I think it would be better if the handbook could explain how to install to a UEFI&BIOS-aware device.<br />
There should be two scenarios:<br />
</p><p>a) user wants to boot with ONLY UEFI or ONLY Legacy BIOS:<br />
in this case, use:<br />
</p><p>a1) if Legacy BIOS:<br />
- boot with BIOS (not UEFI)<br />
- check /sys/firmware/efi does not exist<br />
- partitions:
</p>
<pre> [BIOS boot] /dev/sda1
[boot/grub] /dev/sda2 (ext2)
</pre>
<p>- filesystem:
</p>
<pre># mkfs.ext2 /dev/sda2
# mount /dev/sda2 /boot
</pre>
<p>- install bootloader:
</p>
<pre># grub-install /dev/sda
</pre>
<p>a2) if UEFI:<br />
- boot with UEFI (not BIOS)<br />
- check /sys/firmware/efi exists<br />
- partitions:
</p>
<pre> [BIOS boot] /dev/sda1
[UEFI] /dev/sda2 (fat32)
</pre>
<p>- filesystem:
</p>
<pre># mkfs.fat -F 32 /dev/sda2
# mount /dev/sda2 /boot
</pre>
<p>- install bootloader:
</p>
<pre># grub-install --target=x86_64-efi --efi-directory=/boot /dev/sda
</pre>
<p>(actually, grub-install /dev/sda should be enough)
</p><p>b) user wants to boot with BOTH UEFI AND Legacy BIOS:<br />
</p><p>b1) grub and efi on different partitions:<br />
- boot with UEFI (not BIOS)<br />
- check /sys/firmware/efi exists<br />
- partitions:
</p>
<pre> [BIOS boot] /dev/sda1
[UEFI] /dev/sda2 (fat32)
[boot/grub] /dev/sda3 (ext2)
</pre>
<p>- filesystem:
</p>
<pre># mkfs.fat -F 32 /dev/sda2
# mkfs.ext2 /dev/sda3
# mount /dev/sda3 /boot
# mkdir /boot/efi
# mount /dev/sda2 /boot/efi
</pre>
<p>- install bootloader:
</p>
<pre># grub-install --target=x86_64-efi --efi-directory=/boot/efi /dev/sda
</pre>
<p>( actually, grub-install --efi-directory=/boot/efi /dev/sda should be enough)
</p>
<pre># grub-install --target=i386-pc /dev/sda
</pre>
<p>b2) grub and efi on same partition:<br />
- boot with UEFI (not BIOS)<br />
- check /sys/firmware/efi exists<br />
- partitions:
</p>
<pre> [BIOS boot] /dev/sda1
[UEFI/boot/grub] /dev/sda2 (fat32)
</pre>
<p>- filesystem:
</p>
<pre># mkfs.fat -F 32 /dev/sda2
# mount /dev/sda2 /boot
</pre>
<p>- install bootloader:
</p>
<pre># grub-install --target=x86_64-efi --efi-directory=/boot /dev/sda
</pre>
<p>( actually, grub-install /dev/sda should be enough)
</p>
<pre># grub-install --target=i386-pc /dev/sda
</pre>
<p>--<a href="/index.php?title=User:Vieri&action=edit&redlink=1" class="new" title="User:Vieri (page does not exist)">Vieri</a> (<a href="/index.php?title=User_talk:Vieri&action=edit&redlink=1" class="new" title="User talk:Vieri (page does not exist)">talk</a>) 11:17, 17 February 2017 (UTC)
</p>
<dl><dd>We have moved away from supporting Hybrid MBR/GPT configuration within the handbook, due to this configuration being unnecessary, niche, and cumbersome to explain. There are other places on the wiki that may detail this setup and instructions can be enhanced there if necessary (feel free to add something if it's missing).</dd></dl>
<dl><dd>Installing GRUB to more than one disk is also beyond the cases covered in the handbook. We only detail a single drive installation - again, there is guidance and information other places on the wiki and within the GRUB manual. Thank you! --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 12:24, 14 February 2024 (UTC)</dd></dl>
<h2><span class="mw-headline" id="EFI_partition_mount">EFI partition mount</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=18" title="Edit section: EFI partition mount">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done as of Jan 13th 2017.</span></div>
</div>
<p>I see the Handbook mentions that Grub2 can't be used, and efibootmgr should be used instead. However, using grub2 is a suitable option.
</p><p>The EFI partition should be mounted to /boot/efi:
</p>
<pre># mkdir /mnt/gentoo/boot/efi
# mount /dev/sda1 /mnt/gentoo/boot/efi
</pre>
<p><a href="/wiki/User:ILMostro" title="User:ILMostro">ILMostro</a> (<a href="/index.php?title=User_talk:ILMostro&action=edit&redlink=1" class="new" title="User talk:ILMostro (page does not exist)">talk</a>)
</p>
<dl><dd>Hi <a href="/wiki/User:ILMostro" title="User:ILMostro">ILMostro <i class="fa fa-user"></i></a>, I saw your message in IRC. We are still very much active in monitoring and updating the wiki, although we're not always able to immediately respond on IRC. I agree, GRUB2 is a suitable option for EFI on Gentoo. I use it myself. With that being said we have to be careful with how much we try to support in the various handbooks. The purpose of it is to help users get Gentoo installed; not to walk them through all the configuration options (Gentoo is far too flexible for that!). :)</dd></dl>
<dl><dd>I don't remember the Handbook ever saying GRUB2 can't be used for EFI on <b><span style="font-family: monospace; font-size: 95%; color: #54487a">amd64</span></b> systems, but I will take a look and fix anything that doesn't seem right. Kind regards, --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 02:05, 21 June 2016 (UTC)</dd></dl>
<h2><span class="mw-headline" id="GPT_or_MBR">GPT or MBR</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=19" title="Edit section: GPT or MBR">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done as of 2022-02-22.</span></div>
</div>
<p>It's definitely possible to dual-boot with Windows using GPT on a BIOS-based system. I'm able to do so with the following GRUB entry:
</p>
<div class="box-caption"><span class="label" style="margin-right: .5em; background-color: #54487A">FILE</span> <strong><code style="border: none; background: none; color: #54487A; margin-right: .5em;">/etc/grub.d/40_custom</code></strong><strong>Dual-boot with Windows</strong></div> <div class="mw-highlight mw-highlight-lang-text mw-content-ltr" dir="ltr"><pre><span></span>'"`UNIQ--pre-0000000F-QINU`"'
</pre></div>
<p>--<a href="/index.php?title=User:Astronome&action=edit&redlink=1" class="new" title="User:Astronome (page does not exist)">Astronome</a> (<a href="/index.php?title=User_talk:Astronome&action=edit&redlink=1" class="new" title="User talk:Astronome (page does not exist)">talk</a>) 03:17, 21 January 2017 (UTC)
</p>
<dl><dd>Hi Astronome, if you're serious about having your discussions looked after please remember to use the <a href="/wiki/Template:Talk" title="Template:Talk">{{Talk}}</a> template. We can't really track what work is left for us to do without them.</dd></dl>
<dl><dd>With that being said, to confirm: does the disk have a GPT partition table, or is it an MSDOS table? Also, is your copy of Windows installed in MSDOS mode? Kind regards, --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 06:47, 24 January 2017 (UTC)</dd></dl>
<dl><dd>Revisiting here... Closing discussion due to no reply from author. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 08:50, 22 February 2022 (UTC)</dd></dl>
<h2><span class="mw-headline" id="Mounting_the_necessary_filesystems">Mounting the necessary filesystems</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=20" title="Edit section: Mounting the necessary filesystems">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done as of Jan 26th 2017.</span></div>
</div>
<p>I've always found this part confusing. Should this
</p>
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root <span style="color:royalblue;">#</span></code><span class="tripleclick-separator"></span><code>mount -t proc proc /mnt/gentoo/proc</code></div></div>
<p>be changed to this?
</p>
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root <span style="color:royalblue;">#</span></code><span class="tripleclick-separator"></span><code>mount -t proc /proc /mnt/gentoo/proc</code></div></div>
<p>Otherwise, if you're following the instructions exactly, your PWD will be <span style="font-family: monospace; font-size: 95%; color: #3c763d; font-weight: 600;">/mnt/gentoo</span> and you'll be mounting <span style="font-family: monospace; font-size: 95%; color: #3c763d; font-weight: 600;">/mnt/gentoo/proc</span> to itself. --<a href="/index.php?title=User:Astronome&action=edit&redlink=1" class="new" title="User:Astronome (page does not exist)">Astronome</a> (<a href="/index.php?title=User_talk:Astronome&action=edit&redlink=1" class="new" title="User talk:Astronome (page does not exist)">talk</a>) 19:55, 21 January 2017 (UTC)
</p>
<dl><dd>Yes, it's a good point. We should have the <span style="font-family: monospace; font-size: 95%; color: #3c763d; font-weight: 600;">/</span> on the second mention of proc. I'll update this. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 06:47, 24 January 2017 (UTC)</dd></dl>
<dl><dd><dl><dd>This assertion is wrong (but doesn't hurt). man mount:</dd>
<dd><i>The proc filesystem is not associated with a special device, and when mounting it, an arbitrary keyword, such as proc can be used instead of a device specification. (The customary choice none is less fortunate: the error message `none busy' from umount can be confusing.).</i></dd></dl></dd></dl>
<dl><dd><dl><dd>It was probably "proc" due to it being suggested to use that in the man page as that arbitrary keyword (but you can use "asdf" or whatever, pretty much anything except for "none'). That argument is the first one - that of the device node to use, -t proc doesn't have one, so it's ignored (unless special "none" is encountered). In "mount -t proc proc /mnt/gentoo/proc" the first "proc" is the type given with -t, "proc" is the device node and /mnt/gentoo/proc is the path - there is no proc path and no way this would have mounted itself (device node != directory). --<a href="/wiki/User:Leio" title="User:Leio">Leio</a> (<a href="/index.php?title=User_talk:Leio&action=edit&redlink=1" class="new" title="User talk:Leio (page does not exist)">talk</a>) 15:26, 26 January 2017 (UTC)</dd></dl></dd></dl>
<dl><dd><dl><dd><dl><dd>That's funny, I was editing this page at the same time as you to say the same thing :) --<a href="/index.php?title=User:Astronome&action=edit&redlink=1" class="new" title="User:Astronome (page does not exist)">Astronome</a> (<a href="/index.php?title=User_talk:Astronome&action=edit&redlink=1" class="new" title="User talk:Astronome (page does not exist)">talk</a>) 15:52, 26 January 2017 (UTC)</dd></dl></dd></dl></dd></dl>
<dl><dd><dl><dd><dl><dd><dl><dd>So it doesn't really matter. It could be <code>proc</code> or it could be <code>/proc</code>. <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">mount</span> doesn't care. If there's nothing left to do here please close this discussion. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 21:52, 26 January 2017 (UTC)</dd></dl></dd></dl></dd></dl></dd></dl>
<dl><dd><dl><dd><dl><dd><dl><dd>Well fine. --<a href="/index.php?title=User:Astronome&action=edit&redlink=1" class="new" title="User:Astronome (page does not exist)">Astronome</a> (<a href="/index.php?title=User_talk:Astronome&action=edit&redlink=1" class="new" title="User talk:Astronome (page does not exist)">talk</a>) 02:29, 27 January 2017 (UTC)</dd></dl></dd></dl></dd></dl></dd></dl>
<h2><span class="mw-headline" id="GPG_verification_when_behind_a_firewall">GPG verification when behind a firewall</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=21" title="Edit section: GPG verification when behind a firewall">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done.</span></div>
</div>
<p>If the default gpg port cannot be opened in the firewall then you might want to use something like:
</p>
<div class="cmd-box"><div><code style="color: #ef2929; font-weight: bold;">root #</code><span class="tripleclick-separator"></span><code>gpg --keyserver hkp://hkps.pool.sks-keyservers.net:80 --recv-keys 0xBB572E0E2D182910</code></div></div>
<p>BTW the user can also specify any other keyserver such as:
hkp://keyserver.ubuntu.com:80
</p><p>This may be useful when some servers don't respond.
</p><p>The following handbook section could be updated to reflect this:
</p><p><a href="/wiki/Handbook:AMD64/Full/Installation#Linux_based_verification" title="Handbook:AMD64/Full/Installation">Handbook:AMD64/Full/Installation#Linux_based_verification</a>
</p><p>--<a href="/index.php?title=User:Vieri&action=edit&redlink=1" class="new" title="User:Vieri (page does not exist)">Vieri</a> (<a href="/index.php?title=User_talk:Vieri&action=edit&redlink=1" class="new" title="User talk:Vieri (page does not exist)">talk</a>) 16 February 2017
</p>
<dl><dd>Hi <a href="/index.php?title=User:Vieri&action=edit&redlink=1" class="new" title="User:Vieri (page does not exist)">Vieri <i class="fa fa-user"></i></a>, I'm rocking <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">gpg</span> version 2.1.19 and it would seem the syntax you used to specify a specific port has been deprecated. I couldn't get it to work by trying your example above. Also, from the man page (<span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">man 1 gpg</span>), "The scheme is the type of keyserver: "hkp" for the HTTP (or compatible) keyservers". This indicates to me that HTTP is the default, so there is no need to specify port 80 in the example... Kind regards, --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 03:59, 5 March 2017 (UTC)</dd></dl>
<dl><dd><dl><dd>No, hkp uses port 11371 by default. What the OP neglected to mention is that not all keyservers support port 80. The general solution is to use the p80 pool at <code>hkp://p80.pool.sks-keyservers.net:80</code>. However, I think that it would be more preferable still to use the hkps pool at <code>hkps://hkps.pool.sks-keyservers.net</code>. This has the advantage of using HTTPS on the standard port of 443. Incidentally, portage and gemato are both inflexible in this regard. --<a href="/index.php?title=User:Kerframil&action=edit&redlink=1" class="new" title="User:Kerframil (page does not exist)">kerframil</a> (<a href="/index.php?title=User_talk:Kerframil&action=edit&redlink=1" class="new" title="User talk:Kerframil (page does not exist)">talk</a>) 02:36, 21 July 2018 (UTC)</dd></dl></dd></dl>
<dl><dd><dl><dd><dl><dd>Thanks, added that URI. --<a href="/wiki/User:Grknight" title="User:Grknight">Grknight</a> (<a href="/wiki/User_talk:Grknight" title="User talk:Grknight">talk</a>) 15:30, 7 November 2018 (UTC)</dd></dl></dd></dl></dd></dl>
<h2><span class="mw-headline" id="DavidC_improvements_section">DavidC improvements section</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=22" title="Edit section: DavidC improvements section">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>As I'm reading through this doco I'm writing a bunch of suggestions, some of which are sure to be misguided, so the only discussion I require is "yes/no/maybe later". Hopefully some of this helps but I know not all of it will be implemented.
</p>
<h3><span class="mw-headline" id="Preparing_the_disk">Preparing the disk</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=23" title="Edit section: Preparing the disk">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done.</span></div>
</div>
<p>Prior to "Introduction to block devices" it would be nice if there was a title that said something like preparing the disk, since that is what is referred to above in the document. <a href="/index.php?title=User:DavidC&action=edit&redlink=1" class="new" title="User:DavidC (page does not exist)">DavidC</a> (<a href="/index.php?title=User_talk:DavidC&action=edit&redlink=1" class="new" title="User talk:DavidC (page does not exist)">talk</a>) 17:57, 18 November 2017 (UTC)
</p>
<dl><dd>This would require a significant amount of work. It would require a lower-level heading than the one used for "Introduction to block devices" and subsequent sections. Since there is none, the headings for all sections on the page would have to be shifted up one level, but that change would automatically get copied to the non-full installation parts of the handbook (e.g. <a href="/wiki/Handbook:AMD64/Installation/Disks" title="Handbook:AMD64/Installation/Disks">Handbook:AMD64/Installation/Disks</a>).</dd>
<dd></dd>
<dd>The non-full installation parts should get priority since</dd></dl>
<p><translate>
</p><p></translate>
</p>
<pre>takes the user there. Thus, taking no action is the best option here.
</pre>
<dl><dd></dd>
<dd>I'm closing this discussion since I don't know whether you will respond. If you do, feel free to reopen it. <a href="/wiki/User:Glibg10b" title="User:Glibg10b">Glibg10b</a> (<a href="/wiki/User_talk:Glibg10b" title="User talk:Glibg10b">talk</a>) 07:39, 1 April 2024 (UTC)</dd></dl>
<h3><span class="mw-headline" id="Open_more_than_one_chroot_terminal">Open more than one chroot terminal</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=24" title="Edit section: Open more than one chroot terminal">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done as of October 29th, 2021.</span></div>
</div>
<p>I'd probably get the user to chroot a couple terminals at least because then they would be able to do some reading while something is going on it another window, or easily compare say the output of lspci to what they're inputting in makeconfig, etc. <a href="/index.php?title=User:DavidC&action=edit&redlink=1" class="new" title="User:DavidC (page does not exist)">DavidC</a> (<a href="/index.php?title=User_talk:DavidC&action=edit&redlink=1" class="new" title="User talk:DavidC (page does not exist)">talk</a>) 15:13, 19 November 2017 (UTC)
</p><p>We mention screen for this purpose, but I have also have added a tip to explictly show readers how to switch between the seven available terminals: <a href="/wiki/Special:Diff/1015767/024956" title="Special:Diff/1015767/024956">Special:Diff/1015767/024956</a>. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 20:35, 29 October 2021 (UTC)
</p>
<h3><span class="mw-headline" id="This_and_that">This and that</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=25" title="Edit section: This and that">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done as of 2024-02-14.</span></div>
</div>
<p>I am lost at <a href="/wiki/Handbook:AMD64/Full/Installation#Introduction_to_block_devices" title="Handbook:AMD64/Full/Installation">Handbook:AMD64/Full/Installation#Introduction_to_block_devices</a>. Looking at "If that is the case, it might be..." I understand what "that" case is, but when it says "In this case, launch..." I do not understand what "this" case is. Perhaps after "using the MBR format." A sentence could be added directing MBR users to "Default partitioning scheme". Someone suggested this be split into 3 sections "bios with mbr, efi with gpt, bios with gpt" <a href="/index.php?title=User:DavidC&action=edit&redlink=1" class="new" title="User:DavidC (page does not exist)">DavidC</a> (<a href="/index.php?title=User_talk:DavidC&action=edit&redlink=1" class="new" title="User talk:DavidC (page does not exist)">talk</a>) 19:37, 18 November 2017 (UTC)
</p>
<h3><span class="mw-headline" id="I_am_overwhelmed_with_mirrors">I am overwhelmed with mirrors</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=26" title="Edit section: I am overwhelmed with mirrors">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done as of October 29th, 2021.</span></div>
</div>
<p>"links <a rel="nofollow" class="external free" href="https://www.gentoo.org/downloads/mirrors/">https://www.gentoo.org/downloads/mirrors/</a>" So if you follow the first link for Canadians, you end up going to a LONG list of files and it's not entirely clear what to download (even if you follow it all the way to Gentoo, so it's probably best just to link people straight to <a rel="nofollow" class="external free" href="https://gentoo.org/downloads/">https://gentoo.org/downloads/</a>. <a href="/index.php?title=User:DavidC&action=edit&redlink=1" class="new" title="User:DavidC (page does not exist)">DavidC</a> (<a href="/index.php?title=User_talk:DavidC&action=edit&redlink=1" class="new" title="User talk:DavidC (page does not exist)">talk</a>) 19:58, 18 November 2017 (UTC)
</p>
<dl><dd>If you are referring this section, there are no instructions to download anything from the mirrors directly. It's just giving an example on how to use links to determine what mirror URLs are avaialble. No where in the instruction are you supposed to download anything in this section. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 20:35, 29 October 2021 (UTC)</dd></dl>
<h3><span class="mw-headline" id="Variables">Variables</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=27" title="Edit section: Variables">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done as of October 29th, 2021.</span></div>
</div>
<p>"variables which impacts" --> "impact" <a href="/index.php?title=User:DavidC&action=edit&redlink=1" class="new" title="User:DavidC (page does not exist)">DavidC</a> (<a href="/index.php?title=User_talk:DavidC&action=edit&redlink=1" class="new" title="User talk:DavidC (page does not exist)">talk</a>) 20:02, 18 November 2017 (UTC)
</p>
<dl><dd>Fixed. See <a href="/wiki/Special:Diff/1023606/1024968" title="Special:Diff/1023606/1024968">Special:Diff/1023606/1024968</a>. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 20:35, 29 October 2021 (UTC)</dd></dl>
<h3><span class="mw-headline" id="Path_differences_for_examples">Path differences for examples</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=28" title="Edit section: Path differences for examples">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done as of October 29th, 2021.</span></div>
</div>
<p>"To keep the settings, Portage reads in the /etc/portage/make.conf file" ok so this line is talking about what is currently /mnt/gentoo/etc/... but the light blue section afterwards refers to /mnt/gentoo/usr/share/... explicitly, as does the black section starting with nano -w, so there should be consistency across all those three things. <a href="/index.php?title=User:DavidC&action=edit&redlink=1" class="new" title="User:DavidC (page does not exist)">DavidC</a> (<a href="/index.php?title=User_talk:DavidC&action=edit&redlink=1" class="new" title="User talk:DavidC (page does not exist)">talk</a>) 20:14, 18 November 2017 (UTC)
</p><p>I seems like you're splitting hairs on ths one. The tip is about Portage. The path is different because you're operating out of an extracted state3 during this section of the handbook. I'll just change it to make.conf to avoid confusion. See <a href="/wiki/Special:Diff/1023606/1024968" title="Special:Diff/1023606/1024968">Special:Diff/1023606/1024968</a>. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 20:35, 29 October 2021 (UTC)
</p>
<h3><span class="mw-headline" id="Custom_prompt_is_reverted">Custom prompt is reverted</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=29" title="Edit section: Custom prompt is reverted">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done.</span></div>
</div>
<p>After "root #eselect locale set 9", the shell tells the user to run something like . /etc/profile, which results in removing the custom prompt "(chroot)" and it's a little disconcerting. So I think the best option here is to tell the user not to follow the prompting of the shell before giving the set 9 command. Further, afterwards there is a black box that has maybe 3 commands in it separated by & and those commands could easily be given as a series of single lines, which would probably be better. <a href="/index.php?title=User:DavidC&action=edit&redlink=1" class="new" title="User:DavidC (page does not exist)">DavidC</a> (<a href="/index.php?title=User_talk:DavidC&action=edit&redlink=1" class="new" title="User talk:DavidC (page does not exist)">talk</a>) 14:53, 19 November 2017 (UTC)
</p>
<dl><dd>This has been solved. Closing. <a href="/wiki/User:Glibg10b" title="User:Glibg10b">Glibg10b</a> (<a href="/wiki/User_talk:Glibg10b" title="User talk:Glibg10b">talk</a>) 09:53, 1 April 2024 (UTC)</dd></dl>
<h3><span class="mw-headline" id="Current_USE_flags_in_profile">Current USE flags in profile</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=30" title="Edit section: Current USE flags in profile">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done.</span></div>
</div>
<p>In the USE flag section, it might be a good idea to suggest something like <profile_file> | grep ^USE >> <make.conf> so that people can see their profile USE flags at the same time that they're putting in their custom values; they would have to comment it out if they did that, though. <a href="/index.php?title=User:DavidC&action=edit&redlink=1" class="new" title="User:DavidC (page does not exist)">DavidC</a> (<a href="/index.php?title=User_talk:DavidC&action=edit&redlink=1" class="new" title="User talk:DavidC (page does not exist)">talk</a>) 15:08, 19 November 2017 (UTC)
</p>
<dl><dd>I really like the idea of explaining how to view USE flags already set in the profile. I'll implement something like this soon. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 20:35, 29 October 2021 (UTC)</dd>
<dd></dd>
<dd>Completed (<a href="/wiki/Handbook:AMD64/Full/Installation#Optional:_Configuring_the_USE_variable" title="Handbook:AMD64/Full/Installation">Handbook:AMD64/Full/Installation#Optional:_Configuring_the_USE_variable</a>). Closing. <a href="/wiki/User:Glibg10b" title="User:Glibg10b">Glibg10b</a> (<a href="/wiki/User_talk:Glibg10b" title="User talk:Glibg10b">talk</a>) 09:54, 1 April 2024 (UTC)</dd></dl>
<h3><span class="mw-headline" id="devtmpfs_cannot_be_unselected">devtmpfs cannot be unselected</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=31" title="Edit section: devtmpfs cannot be unselected">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done.</span></div>
</div>
<p>" [*] Maintain a devtmpfs filesystem to mount at /dev" You can not unselect this, therefore this section can be removed safely. <a href="/index.php?title=User:DavidC&action=edit&redlink=1" class="new" title="User:DavidC (page does not exist)">DavidC</a> (<a href="/index.php?title=User_talk:DavidC&action=edit&redlink=1" class="new" title="User talk:DavidC (page does not exist)">talk</a>) 15:19, 19 November 2017 (UTC)
</p>
<dl><dd>We'll safely leave it. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 09:28, 20 February 2023 (UTC)</dd></dl>
<h3><span class="mw-headline" id="Blank_line_requested">Blank line requested</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=32" title="Edit section: Blank line requested">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done.</span></div>
</div>
<p>"Executable file formats / Emulations --->" Put a blank line prior to this to strongly indicate that it's denested. <a href="/index.php?title=User:DavidC&action=edit&redlink=1" class="new" title="User:DavidC (page does not exist)">DavidC</a> (<a href="/index.php?title=User_talk:DavidC&action=edit&redlink=1" class="new" title="User talk:DavidC (page does not exist)">talk</a>) 16:04, 19 November 2017 (UTC)
</p>
<dl><dd>I no longer see that line in this AMD64/Full/Installation page, so can this be closed <a href="/index.php?title=User:DavidC&action=edit&redlink=1" class="new" title="User:DavidC (page does not exist)">DavidC <i class="fa fa-user"></i></a> ? Thanks -- <a href="/wiki/User:Ris" title="User:Ris">Ris</a> (<a href="/wiki/User_talk:Ris" title="User talk:Ris">talk</a>) 16:57, 1 March 2024 (UTC)</dd></dl>
<h3><span class="mw-headline" id="GRUB_install_issue">GRUB install issue</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=33" title="Edit section: GRUB install issue">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done as of 2023-02-20.</span></div>
</div>
<p>For grub-install with EFI, please include the 2 steps for EFI vars. Otherwise, grub-install will silently fail. From <a href="/wiki/Efibootmgr#Creating_a_boot_entry" title="Efibootmgr">Efibootmgr#Creating_a_boot_entry</a>:
</p>
<pre> root #mount | grep efivars
efivarfs on /sys/firmware/efi/efivars type efivarfs (ro,relatime)
</pre>
<pre> root #mount -o remount,rw -t efivarfs efivarfs /sys/firmware/efi/efivars
</pre>
<p><small>— The preceding <a href="/wiki/Help:Signatures" title="Help:Signatures">unsigned</a> comment was added by <a href="/index.php?title=User:Dman777&action=edit&redlink=1" class="new" title="User:Dman777 (page does not exist)">Dman777</a> (<a href="/index.php?title=User_talk:Dman777&action=edit&redlink=1" class="new" title="User talk:Dman777 (page does not exist)">talk</a> • <a href="/wiki/Special:Contributions/Dman777" title="Special:Contributions/Dman777">contribs</a>) 19:27, December 18, 2017</small>
</p>
<dl><dd>This should NOT be the case when using official Gentoo installation live images. We do cover that in the <a href="/wiki/Handbook:AMD64/Installation/Bootloader#Install" title="Handbook:AMD64/Installation/Bootloader">GRUB install section</a>, we just don't currently specify the <code>--type</code> option, as your example does. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 09:39, 20 February 2023 (UTC)</dd></dl>
<h3><span class="mw-headline" id="Fix_nesting">Fix nesting</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=34" title="Edit section: Fix nesting">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done as of 14 July 2022.</span></div>
</div>
<p>"Pseudo Filesystems --->" needs to be nested one step inwards. <a href="/index.php?title=User:DavidC&action=edit&redlink=1" class="new" title="User:DavidC (page does not exist)">DavidC</a> (<a href="/index.php?title=User_talk:DavidC&action=edit&redlink=1" class="new" title="User talk:DavidC (page does not exist)">talk</a>) 16:10, 19 November 2017 (UTC)
</p>
<dl><dd>A fix was provided (<a href="/wiki/Special:Diff/1018950/1023486" title="Special:Diff/1018950/1023486">Special:Diff/1018950/1023486</a>). --<a href="/wiki/User:Blacki" title="User:Blacki">Blacki</a> (<a href="/wiki/User_talk:Blacki" title="User talk:Blacki">talk</a>) 04:44, 14 July 2022 (UTC)</dd></dl>
<h3><span class="mw-headline" id="Combine_all_kernel_sections">Combine all kernel sections</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=35" title="Edit section: Combine all kernel sections">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done as of October 29th, 2021.</span></div>
</div>
<p>There seems to be a lot of random traversal of the kernel configuration. It would be beneficial to group all sections together which access similar hierarchies. It would probably also be good to include the hotkeys in this menu so that the user can traverse it more quickly. <a href="/index.php?title=User:DavidC&action=edit&redlink=1" class="new" title="User:DavidC (page does not exist)">DavidC</a> (<a href="/index.php?title=User_talk:DavidC&action=edit&redlink=1" class="new" title="User talk:DavidC (page does not exist)">talk</a>) 16:14, 19 November 2017 (UTC)
</p><p>I do not believe it would suit well to have all kernel sections together in one big block. Regarding hotkeys: we have other articles availabe on the wiki that mention hotkeys (see <a href="/wiki/Kernel" title="Kernel">Kernel</a> articles)... This is not something I think is worth adding to the basic installation requirements for Gentoo. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 20:35, 29 October 2021 (UTC)
</p>
<h3><span class="mw-headline" id="How_to_read_documenation_file">How to read documenation file</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=36" title="Edit section: How to read documenation file">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done as of 14 July 2022.</span></div>
</div>
<p>"Please read /usr/share/doc/netifrc-*/net.example.bz2 for a list of all available options." The document does not say how to do this. Also in this section, observe: " But don't fear, everything is explained below." This breaks style, but I like it. <a href="/index.php?title=User:DavidC&action=edit&redlink=1" class="new" title="User:DavidC (page does not exist)">DavidC</a> (<a href="/index.php?title=User_talk:DavidC&action=edit&redlink=1" class="new" title="User talk:DavidC (page does not exist)">talk</a>) 20:01, 19 November 2017 (UTC)
</p>
<dl><dd>A little bit higher in the document, it was already mentionned that net.example.bz2 <i>"can be read using bzless"</i>. --<a href="/wiki/User:Blacki" title="User:Blacki">Blacki</a> (<a href="/wiki/User_talk:Blacki" title="User talk:Blacki">talk</a>) 10:10, 14 July 2022 (UTC)</dd></dl>
<p><br />
</p>
<h2><span class="mw-headline" id="CFLAGS_Section_links">CFLAGS Section links</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=37" title="Edit section: CFLAGS Section links">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done as of October 27, 2021.</span></div>
</div>
<p>Suggestion: The <a href="/wiki/Handbook:AMD64/Full/Installation#CFLAGS_and_CXXFLAGS" title="Handbook:AMD64/Full/Installation">CFLAGS Section</a>
might as well contain additional references to <a href="/wiki/GCC_optimization" title="GCC optimization">GCC_optimization</a> and <a href="/wiki/CPU_FLAGS_X86" class="mw-redirect" title="CPU FLAGS X86">CPU_FLAGS_X86</a>?
These wiki pages seem more comprehensible for n00bs like me than the referenced gnu manual.
</p><p><a href="/index.php?title=User:Atari800&action=edit&redlink=1" class="new" title="User:Atari800 (page does not exist)">User:atari800</a> (2019/02/19 11:54am)
</p>
<dl><dd>The <a href="/wiki/GCC_optimization" title="GCC optimization">GCC optimization</a> and <a href="/wiki/Safe_CFLAGS" title="Safe CFLAGS">Safe CFLAGS</a> articles are now listed in a tip at the <a href="/wiki/Handbook:AMD64/Full/Installation#CFLAGS_and_CXXFLAGS" title="Handbook:AMD64/Full/Installation">bottom of the section</a>. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 22:52, 27 October 2021 (UTC)</dd></dl>
<h2><span class="mw-headline" id="delete:_Prior_to_Windows_7">delete: Prior to Windows 7</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=38" title="Edit section: delete: Prior to Windows 7">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done as of October 27, 2021.</span></div>
</div>
<p>Suggestion: Delete section to explain how to burn CD on a 10 year old windows system. If someone still runs it, he/she knows how to burn CD's. --<a href="/wiki/User:Jstein" title="User:Jstein">Jonas Stein</a> (<a href="/wiki/User_talk:Jstein" title="User talk:Jstein">talk</a>) 01:06, 16 May 2020 (UTC)
</p>
<dl><dd><a href="/wiki/User:Jstein" title="User:Jstein"> Jonas Stein (Jstein) <i class="fa fa-user"></i></a>, thank you for reporting. This was fixed a while back. We now cover Windows 7 and above as a 'catch all' to include Windows 10 and 11. See <a href="/wiki/Handbook:AMD64/Full/Installation#Burning_with_Microsoft_Windows_7_and_above" title="Handbook:AMD64/Full/Installation">Handbook:AMD64/Full/Installation#Burning_with_Microsoft_Windows_7_and_above</a>. Thank you! --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 21:08, 27 October 2021 (UTC)</dd></dl>
<h2><span class="mw-headline" id="Reiserfs">Reiserfs</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Full/Installation/Archive&action=edit&section=39" title="Edit section: Reiserfs">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<div id="infobox-stack" class="list-group" style="width: 25em; float: right; clear: right; font-size: 90%; margin-left: 1em;">
<div class="list-group-item text-center" style="padding-top: 3px; padding-bottom: 3px; background-color: #463C65; color: white;"><b>Talk status</b></div>
<div id="infobox" class="list-group-item" style="display: flex; align-items: center; padding: 5px; min-height: 3em;"><span style="display: inline-block; width: 3em; overflow: hidden; text-align: center;"><span class="fa fa-check fa-fw fa-2x"></span></span><span>This discussion is done.</span></div>
</div>
<p>Reiserfs is included in mainline Linux--<a href="/index.php?title=User:Nikitastepanov&action=edit&redlink=1" class="new" title="User:Nikitastepanov (page does not exist)">Nikitastepanov</a> (<a href="/index.php?title=User_talk:Nikitastepanov&action=edit&redlink=1" class="new" title="User talk:Nikitastepanov (page does not exist)">talk</a>) 11:26, 30 August 2020 (UTC)
</p>
<dl><dd>Duplicate of <a href="/wiki/Handbook_Talk:Parts/Installation/Disks#Reiserfs" title="Handbook Talk:Parts/Installation/Disks">Handbook Talk:Parts/Installation/Disks#Reiserfs</a> (as this page inherits that article) --<a href="/wiki/User:Grknight" title="User:Grknight">Grknight</a> (<a href="/wiki/User_talk:Grknight" title="User talk:Grknight">talk</a>) 13:19, 31 August 2020 (UTC)</dd></dl>
' |
Unix timestamp of change (timestamp) | 1711966561 |