Abuse filter log

From Gentoo Wiki
Abuse Filter navigation (Home | Recent filter changes | Examine past edits | Abuse log)
Jump to:navigation Jump to:search
Details for log entry 4,776

16:14, 20 January 2024: Schnecki (talk | contribs) triggered filter 30, performing the action "edit" on Handbook Talk:AMD64/Installation/Base. Actions taken: Disallow; Filter description: Disable writing internal wiki links as external besides required links. If absolutely necessary, use wiki.g.o as a workaround. (examine)

Changes made in edit

  
 
== Move Selecting Mirrors section after the chroot entry ==
 
== Move Selecting Mirrors section after the chroot entry ==
{{talk|closed|date=2024-01-03}}
+
{{talk|open}}
  
 
If a user is not using the Gentoo installation media (and in #gentoo, we often note that it's not necessary to use Gentoo's media), they may not have access to the {{c|mirrorselect}} tool until they enter the chroot.
 
If a user is not using the Gentoo installation media (and in #gentoo, we often note that it's not necessary to use Gentoo's media), they may not have access to the {{c|mirrorselect}} tool until they enter the chroot.
  
 
: Finally getting around to make this change. Apologies it took so many years to implement! See [[Special:Diff/1272298/1272302]]. Thanks, {{U|sam}}! {{unsigned2|2024-01-04T08:10:45‎|Maffblaster}}
 
: Finally getting around to make this change. Apologies it took so many years to implement! See [[Special:Diff/1272298/1272302]]. Thanks, {{U|sam}}! {{unsigned2|2024-01-04T08:10:45‎|Maffblaster}}
 +
:: Mirrorselect is not part of all (any?) stage3 tarballs, so moving the "mirrorselect" section below the chroot does not work in its current state as I experienced. One has to either select the mirrors before chrooting, select them manually or install app-portage/mirrorselect in the chroot (which has to be done after syncing, when already selected mirrors would be preferred (i guess)). Also the green tip is obsolete. I'd suggest moving it before the chroot while preserving the tip. Maybe an edit to https://wiki.gentoo.org/wiki/Installation_alternatives#Installation_from_non-Gentoo_live_environments? --~~~~
  
 
== The "locale.gen" file doesn't have template like in the handbook base steps ==
 
== The "locale.gen" file doesn't have template like in the handbook base steps ==

Action parameters

VariableValue
Edit count of the user (user_editcount)
1
Name of the user account (user_name)
'Schnecki'
Age of the user account (user_age)
1107846
Page ID (page_id)
124710
Page namespace (page_namespace)
561
Page title (without namespace) (page_title)
'AMD64/Installation/Base'
Full page title (page_prefixedtitle)
'Handbook Talk:AMD64/Installation/Base'
Action (action)
'edit'
Edit summary/reason (summary)
''
Old content model (old_content_model)
'wikitext'
New content model (new_content_model)
'wikitext'
Old page wikitext, before the edit (old_wikitext)
'{{Talk page}} == True multilib needs modification in make.conf == {{InfoBox stack |{{InfoBox talk done}} }} When installing selecting the multilib profile itself wasn't sufficient. I only got true multilib support after adding the follwing in make.conf. I think it's worth mentioning it upfront so that people wouldn't have to recompile @world <pre> ABI_X86="64 32" </pre> : No, this is not a good suggestion to make for all Gentoo users to read the Handbook. We recommend only setting enable <code>abi_x86_32</code> as-needed on a per-package basis, not globally. As explained by {{U|iamben}}, "if you enable ABI_X86="32" globally up front, you save a little bit of user configuration time up front but you waste a lot of compile time '''on every upgrade''' '''forever'''". Also, if this was set globally as you suggest, revising those packages later can cause headaches. Kind regards, --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 19:30, 3 October 2016 (UTC) == Chroot on one line == {{InfoBox stack |{{InfoBox talk done|date=Jun 6 2015}} }} It would be imo convenient to have one-liner for the mounts before the chrooting, instead of five separate commands, so that one could easily copy-paste the one command to terminal and execute it in one take I.e., instead of (or, placed after) <pre> root #mount -t proc proc /mnt/gentoo/proc root #mount --rbind /sys /mnt/gentoo/sys root #mount --make-rslave /mnt/gentoo/sys root #mount --rbind /dev /mnt/gentoo/dev root #mount --make-rslave /mnt/gentoo/dev </pre> there ought to be also <pre>mount -t proc proc /mnt/gentoo/proc && mount --rbind /sys /mnt/gentoo/sys && mount --make-rslave /mnt/gentoo/sys && mount --rbind /dev /mnt/gentoo/dev && mount --make-rslave /mnt/gentoo/dev</pre> --[[User:Renergy|Renergy]] ([[User talk:Renergy|talk]]) 19:39, 6 June 2015 (UTC) : Renergy, I can see that may be easier to copy and paste a one line command such as you posted above. Part of the purpose of the Handbook is to teach people how to install Gentoo Linux, not to make the install as fast as possible, which is why we have each command on a separate line. I will think about putting a one-liner like you suggest as a secondary option for people who are in a hurry. Sincerely, --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 22:14, 21 December 2015 (UTC) == Potential security problem == {{InfoBox stack |{{InfoBox talk open|date=Jun 28 2015}} }} Going though the handbook normally leads you through getting the minimal .iso and stage 3 tarball over https, checking hashes and verifying with gpg. All good so far. Here, it tells users to run emerge-webrsync, without any warning that it defaults to using http - enabling a MITM attack. If I understand correctly, this is for downloading and setting up portage, while running as root. By default, emerge-webrsync does not verify gpg signatures, so at this point the system must be considered fundamentally insecure. The user stanley on irc suggested using this procedure: [[Handbook:AMD64/Working/Features#Pulling_validated_Gentoo_ebuild_tree_snapshots]] - it should definitely be mentioned as an option at this stage, since doing it with an already insecure system at the later stage will make little difference. Also, emerge-webrsync should default to using HTTPS. --[[User:OliverUv|OliverUv]] ([[User talk:OliverUv|talk]]) 12:26, 28 June 2015 (UTC) : But this affects all arches, right? See [[Handbook_Talk:Parts/Installation/Base]] --[[User:Charles17|Charles17]] ([[User talk:Charles17|talk]]) 17:43, 20 January 2016 (UTC) :: Hm...I'll see what we can do about this upstream. It would be nice if the mirrors used HTTPS, but I'm not sure we have a good way of enforcing it. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 18:21, 18 November 2016 (UTC) ::: So, the good news is that current Gentoo minimal install images ship with a sufficiently modern Portage (>=2.3.42, with the <code>rsync-verify</code> <var>USE</var> flag set) such that for a vanilla {{c|rsync}}-based {{c|emerge --sync}} (under the recommended {{Path|/etc/portage/repos.conf/gentoo.conf}} settings from the guide: <code>sync-rsync-verify-metamanifest = yes</code> etc.), [https://gentoo.org/support/news-items/2018-01-30-portage-rsync-verification.html signature verification] with [https://gentoo.org/support/news-items/2018-07-11-portage-sync-allow-hardlinks.html failure quarantine] will be carried out. ::: The not so good news is that in [[{{SUBJECTPAGENAME}}#Installing_an_ebuild_repository_snapshot_from_the_web|this section of the handbook]], it is still recommended first to carry out a vanilla {{c|emerge-webrsync}}, which for some mirrors anyway will use unauthenticated HTTP (e.g. http://trumpetti.atm.tut.fi/gentoo), and which does ''not'' (by default) signature verify the downloaded tree. ::: This is easy enough to work around though - just set <code>sync-webrsync-verify-signature = true</code> in the {{c|[gentoo]}} section of {{Path|/etc/portage/repos.conf/gentoo.conf}}, temporarily set <code>sync-type = webrsync</code> in that file also (rather than <code>sync-type = rsync</code>) and then issue <code>emaint sync --auto</code>. This will do all the necessary signature updating etc and then download and verify the daily snapshot (NB - {{c|emerge-webrsync}} will complain if you try to directly invoke it with <code>sync-webrsync-verify-signature = true</code> set; you need to use {{c|emaint sync}} or {{c|emerge --sync}}). Then, once done, just flip back to using <code>sync-type = rsync</code>. This ensures all updates are validated, and doesn't mess the flow of the guide up too much. (I'm just in the process of switching over to recommending this workflow for my own EFI install guide, incidentally.) --[[User:Sakaki|Sakaki]] ([[User talk:Sakaki|talk]]) 13:33, 11 October 2018 (UTC) == Choosing profiles == {{Talk|closed|date=2024-01-04}} I believe profiles should be chosen after the initial reboot at least for {{Keyword|amd64}} and {{Keyword|x86}}. Choosing a desktop profile, in particular, too early causes increased and unnecessary install time added to a user's experience. I think it should be saved until the first reboot. --[[User:Grknight|Grknight]] ([[User talk:Grknight|talk]]) 01:46, 22 October 2015 (UTC) : I will experiment on a virtual machine with this. My initial thoughts are that you're right. Rebuilding world after the profile selection is ''probably'' not a necessary part of the process. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 23:28, 1 February 2016 (UTC) : Also, the profile selection should be updated to 17.0, maybe with a little warning regarding 17.1 which got stabilized recently.--[[User:Charles17|Charles17]] ([[User talk:Charles17|talk]]) 10:28, 27 December 2017 (UTC) Update in progress... --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 02:44, 28 April 2018 (UTC) Revisiting again after some time and many changes made by Gentoo's release engineer team and desktop stage files. I do not believe updating the @world set should increase install time enough to be a concern and it is an important part of the learning process. Especially when considering the introduction of the (optional) {{Link|Handbook:AMD64/Installation/Base#Optional:_Adding_a_binary_package_host|binary package host}} section which I have recently added and if a (relatively recently produced) ''desktop'' stage file is used there are generally only a few dozen packages updates to be performed... modern hardware can handle the compiling and other hardware (at least AMD64 and ARM64) can use the binhost. It also fits nicely into this section so I think it's safe to keep, but perhaps I'll add a little note that installations which are pressed for time can avoid it. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 08:58, 4 January 2024 (UTC) Finished here: [[Special:Diff/1272306/1272318]]. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 10:02, 4 January 2024 (UTC) == Add -qt5 USE flag == {{Talk|closed|date=May 13, 2017}} Let me quote: "gnome gtk -kde -qt4 will compile programs with GNOME (and GTK) support, and not with KDE (and Qt) support, making the system fully tweaked for GNOME (if the architecture supports it)." Please add -qt5 to the previous sentence as well. [[User:Fturco|Fturco]] ([[User talk:Fturco|talk]]) 15:25, 16 April 2017 (UTC) : Good suggestion. Consider it done. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 06:35, 14 May 2017 (UTC) == Will we need Section of "Mounting the boot partition"? == {{Talk|closed|date=2024-01-04}} Hello, Operation of this section is already executed in section of "Preparing the disks".<br /> Haven't we mounting /dev/sda2 on /boot already? Kind regards, --[[User:Komainu8|Komainu8]] ([[User talk:Komainu8|talk]]) 11:04, 13 May 2017 (UTC) : It depends on what install path you take. With this being said, the entire disk section(s) of the Handbook need a major reworking, so I would not be surprised if mounting is inconsistently noted here. I'll leave this open for now since no one is ready to work on fixing the disk section yet... --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 06:39, 14 May 2017 (UTC) : It would be great to have such thing mentioned. --[[User:Wowpetr|Wowpetr]] ([[User talk:Wowpetr|talk]]) 09:25, 12 July 2017 (UTC) :: In this [[Handbook_Talk:AMD64/Installation/Base#Remove_command_to_create_.2Fboot|discussion]], undoing the creation of the ''/boot'' directory was accepted, but mounting is still required depending "on what install path you take". If so, wouldn't be informative to display this in the instructions? I know that if you try to re-mount a partition to the same directory is harmless (no messages are displayed on the shell after execution) but it would be even more educational to the new user to know if this is expected. If not, maybe consider delete [[Handbook:AMD64/Installation/Base#Mounting_the_boot_partition|this]] subsection?--[[User:Neyuru|Neyuru]] ([[User talk:Neyuru|talk]]) 20:03, 5 April 2020 (UTC) : This should now be fixed with the section: [[Handbook:AMD64/Installation/Base#Preparing_for_a_bootloader]]. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 08:48, 4 January 2024 (UTC) == Mounting the necessary filesystems == {{talk|closed|date=July 25, 2017}} It is good to mention that if you interrupt the installation process at any stage later (e.g. by rebooting), you may need to mount these partitions again. --[[User:Wowpetr|Wowpetr]] ([[User talk:Wowpetr|talk]]) 09:25, 12 July 2017 (UTC) : Thanks for the tip. Your suggestion has been implemented! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 23:34, 25 July 2017 (UTC) == Entering the new environment == {{talk|closed|date=July 25, 2017}} It is good to mention that if you interrupt the installation process at any stage inside chroot environment (e.g. by rebooting), you need to chroot again. --[[User:Wowpetr|Wowpetr]] ([[User talk:Wowpetr|talk]]) 09:39, 12 July 2017 (UTC) : Thanks for the tip. Your suggestion has been implemented! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 23:34, 25 July 2017 (UTC) == Warning about 17.x profiles == {{talk|done|date=April 27, 2018}} Please add a big warning before the profile selection instructions, to tell users not to use 17.0 or 17.1 profiles until they have read the corresponding news items and are prepared to follow the migration instructions. [[User:Iamben|Iamben]] ([[User talk:Iamben|talk]]) 15:34, 29 December 2017 (UTC) : Done. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 02:39, 28 April 2018 (UTC) == Typo correction == {{Talk|done|date=July 25, 2019}} Right at the bottom of the page, the line <pre> root #env-update && source /etc/profile && export PS1="(chroot) $PS1" </pre> should read <pre> root #env-update && source /etc/profile && export PS1="(chroot) ${PS1}" </pre> to properly maintain consistency with the previous command under Entering the New Environment [[User:Redchillipadi|Redchillipadi]] ([[User talk:Redchillipadi|talk]]) 02:54, 27 April 2018 (UTC) : It looks that way to me, {{U|Redchillipadi}}. What's the exact link that you're seeing just <code>$PS1</code>? --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 02:38, 28 April 2018 (UTC) My browser says [[{{SUBJECTPAGENAME}}]] PS1 is mentioned under Entering the new environment as <code>${PS1}</code> and at the bottom under Configure Locales as <code>$PS1</code> [[User:Redchillipadi|Redchillipadi]] ([[User talk:Redchillipadi|talk]]) 02:55, 28 April 2018 (UTC) : Fixed ([[Special:Diff/816541/prev]])! For some reason I wasn't seeing it the first time. Thank you! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 17:23, 25 July 2019 (UTC) == Remind the user to fat32 format the esp partition == {{Talk|done|date=18 July 2022}} I'm a new gentoo user but I guess it's not a bad thing to have a novice's view on how this guide is structured. The thing I noticed, following the uefi route is that it would be better to get reminded further down again to format sda2 (the esp partition) as FAT32. It isnt mentioned at the appropriate place. The first time doing this guide, I didn't notice that, ended up installing everything and then the bootloader setup failed because I had the esp as ext2 instead of fat32 (and wasn't able to fix it). Now I'm on my second try due to that. <pre> [...] root #mkfs.ext2 /dev/sda2 root #mkfs.ext4 /dev/sda4 Now create the filesystems on the newly created partitions (or logical volumes)." </pre> It should be placed (or at least mentioned again) here. [[User:AnukWolf|AnukWolf]] ([[User talk:AnukWolf|talk]]) 16:00, 13 October 2018 (UTC : While I agree with the partitioning reminder, do yo really believe that it should be included in this section [[Handbook:AMD64/Installation/Base|Installing the Gentoo base system]]? I think it is more appropriate to include an enhancement in [[Handbook:AMD64/Installation/Disks|Preparing the disks]] section. There are, to this date, 3 discussions regarding this issue there.--[[User:Neyuru|Neyuru]] ([[User talk:Neyuru|talk]]) 19:24, 5 April 2020 (UTC) :: As a new Gentoo user too, I had no problem to use the right filesystem. :: In the [[Handbook:AMD64/Installation/Disks|Preparing the disks]] chapter of 2018 : :: - The "Using UEFI" section explained all that ; it even emphasized the necessity of a FAT variant for the ESP with a "Important" box, and the risk of not being able to boot otherwise. :: - The "Default partitioning scheme" section also indicated and summarized the need for FAT32 for the ESP. :: - The "Applying a filesystem to a partition" section showed the command to create a boot partition in ext2, that's true, but it explicitly stated this was an example (today, this same example is using FAT32, which may be the change you wanted). :: So, the information is already mentioned 2 times (3 times if you're counting the example), at the appropriate place, and with emphasis. :: Also, I agree with {{U|Neyuru}} : there is no use in reminding these things after the [[Handbook:AMD64/Installation/Disks|Preparing the disks]] chapter, as the user is supposed to have applied the relevant filesystems to the partitions after that. :: --[[User:Blacki|Blacki]] ([[User talk:Blacki|talk]]) 07:39, 18 July 2022 (UTC) == Add instructions for bind mounting udev == {{talk|closed|date=2-22-11-27}} os-prober needs {{c|/run/udev}} to function properly and will hang indefinitely if it's not bind mounted from outside. Consider adding a line for bind mounting it from outside the chroot, or at least a small blurb under the mounting to say that other things might need to be mounted. See [[GRUB#os-prober_and_UEFI_in_chroot|this section of the GRUB wiki page]] for details. {{unsigned2|12:21, December 29, 2018‎|Sielicki}} : Thank you for the feedback, {{U|Sielicki}}. I would like to test on a current LiveCD suggested the change before implementing. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 18:24, 25 July 2019 (UTC) :: Uncertain if it was added at the time of your comment here, however the virtual filesystem mount instructions do say to bind mount the {{Path|/run}} directory, which would include the {{Path|udev}} subdirectory. See [[Handbook:AMD64/Installation/Base#Mounting_the_necessary_filesystems]]. This discussion can be closed. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 13:21, 27 November 2022 (UTC) == Remove command to create /boot == {{Talk|closed|date=July 25, 2019}} The /boot directory is already present in the stage3 tarball, so `mkdir /boot' can be removed. Also the paragraph just above needs to be adjusted slightly. --[[User:Rafo|Rafo]] ([[User talk:Rafo|talk]]) 19:02, 1 January 2019 (UTC) : Good point. Suggested changes implemented ([[Special:Diff/816547/prev]]). Thank you, {{U|Rafo}}! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 17:53, 25 July 2019 (UTC) == Minor English grammar correction == {{Talk|done|date=July 25, 2019}} Where it says, "updates can be delayed after the Gentoo installation has finished," I think it should say "delayed '''until''' after." I would change it myself, but I don't have such permissions. --[[User:Dhirsbrunner|Dhirsbrunner]] ([[User talk:Dhirsbrunner|talk]]) 03:58, 24 July 2019 (UTC) : You got it. I have made the suggested change (see [[Special:Diff/816511/prev]]). Thank you for the input! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 17:06, 25 July 2019 (UTC) == Unclear instructions in section 'Configuring Portage' == {{Talk|closed|date=2024-01-04}} In the first subsection 'Installing an ebuild repository snapshot from the web', we tell users that they can skip this subsection if they have no firewalls and a fast network. But in the second subsection 'Optional: Updating the Gentoo ebuild repository', we don't tell those users that they must run 'emerge --sync', because they skipped 'emerge-webrsync'. Instead, we tell them that 'emerge --sync' is optional. So they might skip this subsection as well and won't have a Gentoo ebuild repository. --[[User:Mike155|Mike155]] ([[User talk:Mike155|talk]]) 03:22, 5 November 2019 (UTC) :: Yes. The {{C|emerge --sync}} should be the normal and not optional. Recommending {{C|emerge-webrsync}} without the [[Project:Portage/Repository_Verification#Security_comparison|required manual setup]] as described in [[Handbook:AMD64/Working/Features#Validated_Gentoo_repository_snapshots]] is a bad idea. Better drop it completely or move it to a <code>Tip: In case of limited bandwidth ...</code>.--[[User:Charles17|Charles17]] ([[User talk:Charles17|talk]]) 08:57, 5 November 2019 (UTC) :: Can we make this more clear somehow? We just had this same situation play out on IRC. --[[User:Sam|Sam]] ([[User talk:Sam|talk]]) 17:57, 15 March 2020 (UTC) ::: Same topic [[Handbook_Talk:Parts/Installation/Base#Use_validated_snapshots|here]] and [[Handbook_Talk:Parts/Installation/Base#.28non-validated.29_emerge-webrsync|there]] (talk page for »Parts«)--[[User:Charles17|Charles17]] ([[User talk:Charles17|talk]]) 08:08, 16 March 2020 (UTC) :: With Portage feature enhancements and the flow of the handbook at this point, I believe this concern is no longer an issue. {{C|emerge-webrsync}} performs signature check; {{C|emerge --sync}} is entirely optional. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 08:43, 4 January 2024 (UTC) == Incomprehensible sentence: '... as carefully chosen USE flag defaults may be configured in some ebuilds ...' == {{Talk|closed|date=2019-11-05}} Do we configure USE flag defaults in ebuilds? --[[User:Mike155|Mike155]] ([[User talk:Mike155|talk]]) 18:36, 5 November 2019 (UTC) : You are right, it is poorly worded. I have [[Special:Diff/827128/835781|made it more clear]]. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 00:21, 6 November 2019 (UTC) == Incomprehensible sentence: '... without prompting the user for the licenses previously accepted.' == {{Talk|closed|date=2024-01-04}} The sentence 'Portage uses the ACCEPT_LICENSE variable to determine which packages to allow without prompting the user for the licenses previously accepted.' doesn't seem to be right. Maybe something like: 'Portage uses the ACCEPT_LICENSE variable to determine which packages are allowed to be installed.' --[[User:Mike155|Mike155]] ([[User talk:Mike155|talk]]) 18:36, 5 November 2019 (UTC) : This section has undergone a major reorg and rework. This discussion is stale. See [[Special:Diff/1272302/1272304]]. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 08:36, 4 January 2024 (UTC) == Confusion about per-package exceptions for ACCEPT_LICENSE == {{Talk|closed|date=2022-11-27}} One of the first sentences in paragraph 'Optional: Configuring the ACCEPT_LICENSE variable' is: 'Exceptions can be made per-package in /etc/portage/package.license as well.' The last example of the section shows how to define exceptions in /etc/portage/package.license/kernel. Why is it etc/portage/package.license in one case and /etc/portage/package.license/kernel in the other? I doubt that new users will understand this. --[[User:Mike155|Mike155]] ([[User talk:Mike155|talk]]) 21:24, 5 November 2019 (UTC) : This has been clarified in the following diff: [[Special:Diff/1167615/1169737]]. == Section 'Configure locales': missing reference to /usr/share/i18n/SUPPORTED == {{Talk|closed|date=2020-04-06}} The section tells users that they can/should configure locales in /etc/locale.gen. The section should also tell users that only locales shown in /usr/share/i18n/SUPPORTED are allowed and that they must pay attention to small and capital letters. Maybe we can add a box like the one below (I added such a box in the German translation): {{Tip|A list of supported values is given in file {{Path|/usr/share/i18n/SUPPORTED}}. Please pay attention to small and capital letters and do not use values that are not shown in this file.}} --[[User:Mike155|Mike155]] ([[User talk:Mike155|talk]]) 22:39, 5 November 2019 (UTC) Hello {{U|Mike155}}, this is a welcome enhancement. Thank you for following the recommended format for submitting improvements. I have made the [[Special:Diff/862922/862937|change here]]. Thank you again! Kind regards, --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 08:06, 6 April 2020 (UTC) == What is an 'rsync tree'? == {{Talk|closed|date=2020-04-06}} 'News items were created to provide a communication medium to push critical messages to users via the rsync tree.' What is an 'rsync tree'? Maybe 'Gentoo ebuild tree'? --[[User:Mike155|Mike155]] ([[User talk:Mike155|talk]]) 22:27, 6 November 2019 (UTC) : This terminology has been [[Special:Diff/835997/862907|removed here]] Thank you. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 07:24, 6 April 2020 (UTC) == Add warning about arch-chroot == {{Talk|closed|date=2020-04-06}} Some users in #gentoo seeking support run into issues with 'bad file descriptor' after using <code>arch-chroot</code>. We should warn about this and recommend they stick to the given commands. --[[User:Sam|Sam]] ([[User talk:Sam|talk]]) 02:47, 30 March 2020 (UTC) : Thank you for the comment however, we cannot provide warnings for all non-recommended software. If someone is having problems using software that is Arch specific (and not available at this time in Gentoo), then they can work that out on the Arch wiki in an Arch bug tracker. We provide instructions to use our [[Handbook:AMD64/Installation/Media#Gentoo_Linux_installation_media|official installation media]] and direction on [[Handbook:AMD64/Installation/Base#Chrooting|properly chrooting]]. Kind regards, --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 07:35, 6 April 2020 (UTC) == Missing locale options for America/Monterrey == {{talk|closed|date=2020-04-06}} Maybe this is a bug of the package and not to be discussed here but, just to inform my findings. I selected the timezone "America/Monterrey" and when configuring the locale with "''nano -w /etc/locale.gen''" I only found the option: "''es_MX ISO-8859-1''" in the file, so I selected it (no other option was present for my language). This is dangerous, as the wiki explains: "'''We strongly suggest to use at least one UTF-8 locale because some applications may require it.'''". I found out the hard way too: I had several compile time problems when emerging GNOME, which where gone if '''adding''' the line "''es_MX.UTF-8 UTF-8''" to the "''/etc/locale.gen''" file. Although this option was not present as an option, I can testify that adding it removed the aforementioned compile errors. Can someone help me file this bug?--[[User:Neyuru|Neyuru]] ([[User talk:Neyuru|talk]]) 03:22, 6 April 2020 (UTC) : Hello. Yes, this is not an issue specific to our installation instructions. If you are confident that you have done everything correctly in your installation and you still believe this is an issue with a package, then you'll probably want to file a bug with GNOME's upstream (NOT Gentoo's Bugzilla). If you otherwise have something you believe is necessary to add to these installation instructions, then please follow our [[Handbook:Main_Page#How_do_I_improve_the_Handbook.3F|recommended format for submitting improvements]]. Kind regards, --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 07:39, 6 April 2020 (UTC) Hello and thank you for the rapid response. Yes, I agree there is nothing wrong in the instructions, but I wonder, is the main problem in the omission of the correct encoding options available in "America/Monterrey"? or in GNOME not supporting some encodings? I tend to gravitate to the first option. It is strange that by specifying this locale only *one* of the options belong to the official language spoken there, and it is not even in UTF-8. This is a list of the options available: {#en_US ISO-8859-1, #en_US.UTF-8 UTF-8, #ja_JP.EUC-JP EUC-JP, #ja_JP.UTF-8 UTF-8, #ja_JP EUC-JP, #en_HK ISO-8859-1, #en_PH ISO-8859-1, #de_DE ISO-8859-1, #de_DE@euro ISO-8859-15, '''#es_MX ISO-8859-1''', #fa_IR UTF-8, #fr_FR ISO-8859-1, #fr_FR@euro ISO-8859-15, #it_IT ISO-8859-1}. I sincerely apologize as this conversation does not belong here but, I wanted to share my experience, if someone could find that useful. --[[User:Neyuru|Neyuru]] ([[User talk:Neyuru|talk]]) 16:50, 7 April 2020 (UTC) : Search for '''/usr/share/i18n/SUPPORTED''' (has been added lately) in the article. --[[User:Charles17|Charles17]] ([[User talk:Charles17|talk]]) 17:57, 7 April 2020 (UTC) == Move Selecting Mirrors section after the chroot entry == {{talk|closed|date=2024-01-03}} If a user is not using the Gentoo installation media (and in #gentoo, we often note that it's not necessary to use Gentoo's media), they may not have access to the {{c|mirrorselect}} tool until they enter the chroot. Perhaps it should be moved after the chroot section. --[[User:Sam|Sam]] ([[User talk:Sam|talk]]) 01:51, 24 April 2020 (UTC) : Finally getting around to make this change. Apologies it took so many years to implement! See [[Special:Diff/1272298/1272302]]. Thanks, {{U|sam}}! {{unsigned2|2024-01-04T08:10:45‎|Maffblaster}} == The "locale.gen" file doesn't have template like in the handbook base steps == {{talk|open}} Hi there. During installation of the fresh gentoo, I found that "locale.gen" file from the stage3-amd64-20200607T214504Z doesn't have template like in the handbook steps. I think that it was good idea, if user can uncomment a language that he needs in the locale.gen file instead of to looking for this language param in the man page of locale! What do you think about it? Thanks in advance! --[[User:t0ha|t0ha]] ([[User talk:t0ha|talk]]) 21:15, 12 June 2020 (UTC) == Use "--changed-use" instead of "--newuse" while updating @world == {{talk|open}} "--changed-use" is better for daily Gentoo user. "--newuse" leads to unnecessary rebuild of packages which didn't really change since last build. Recently, the cleanup of ABI_RISCV and related use flags caused rebuild of hundreds of packages, due to the widely use of "--newuse". Many Gentoo users don't realize the existence of "--changed-use". They just follow the Handbook and keep using "--newuse". I heard that "--newuse" was put here to remind base system team not to forget revbmp. But since this Handbook is mostly used by new users, maybe we can add a note about the difference between "--changed-use" and "--newuse" at least. And let the user choose which one they want to use. [[User:Imrebuild|Imrebuild]] ([[User talk:Imrebuild|talk]]) 08:54, 17 October 2020 (UTC) == Gnome no longer requires systemd == {{talk|done}} There are gnome profiles without systemd that use elogind instead. Should the sentence about using >= gnome 3.8 be removed? [[User:Trainz-are-kul|Trainz-are-kul]] ([[User talk:Trainz-are-kul|talk]]) 20:17, 21 November 2020 (UTC) : Done --[[User:Grknight|Grknight]] ([[User talk:Grknight|talk]]) 13:15, 22 November 2020 (UTC) == Mounting of btrfs == {{talk|closed|date=2024-01-03}} I often failed with the handbook when it later comes to <pre> grub-mkconfig -o /boot/grub/grub.cfg /usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?). </pre> ...because there is no / in the 'mount' list. I usually do a mount -a inside the chroot in order to mount all the btrfs subvolumes configured in the fstab there. But / wasn't mounted like that. The simple workaround is and please mention that in the handbook: mount / After that / is mounted again from the internal fstab and grub-mkconfig works. --[[User:Massimo B.|Massimo B.]] ([[User talk:Massimo B.|talk]]) 11:55, 15 December 2021 (UTC) : Hello, {{U|Massimo B.}}, did you put your btrfs rootfs in a separate, non-default btrfs subvolume? Either that, or I'm wondering if you just didn't <code>--rbind</code> {{Path|/dev}} into the chroot... what are the steps for someone to reproduce? If the Handbook is missing a step we'll try to change it, but creating subvolumes is outside Handbook scope... and recursively mounting /dev is already in the Handbook. Thank you, --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 23:13, 20 December 2021 (UTC) : Hi, I have the rootfs on a non-default btrfs subvolume, yes. You mean setting it as default would solve the issue? However grub-mkconfig just parses 'mount' for / and doesn't find it. This is my fstab which I just apply by mount -a && mount / after entering the chroot, mount -a alone does not seem to (re)mount /: <pre>  grep btrfs /etc/fstab LABEL=gentoo / btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes/root 0 1 LABEL=gentoo /mnt/btrfs-top-lvl btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=/ 0 1 #LABEL=gentoo /mnt/snapshots btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=snapshots 0 1 LABEL=gentoo /home btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes/home 0 1 LABEL=gentoo /mnt/data btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes/data 0 1 LABEL=gentoo /tmp btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/tmp 0 1 LABEL=gentoo /usr/portage btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/usr.portage 0 1 LABEL=gentoo /usr/src btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/usr.src 0 1 LABEL=gentoo /var/cache btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/var.cache 0 1 LABEL=gentoo /var/db/repos btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/var.db.repos 0 1 LABEL=gentoo /var/lib/layman btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/var.lib.layman 0 1 LABEL=gentoo /var/tmp btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/var.tmp 0 1 </pre> --[[User:Massimo B.|Massimo B.]] ([[User talk:Massimo B.|talk]]) 10:52, 22 December 2021 (UTC) : Unfortunately I am uncertain what is causing the issue. The handbook doesn't go into detail about btrfs sub-volumes and I don't plan on adding that level of detail in the future. If you figure out the cause of the issue please return here, re-open the discussion so that we notice it, and share the solution. Perhaps a small note could be added specific to btrfs installs which put rootfs on a non-default sub-volume... You could try asking on the mailing list or {{IRC|gentoo}}? Thanks! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 07:01, 4 January 2024 (UTC) == Link to recovery section of tips and tricks == {{talk|open}} There is a section on [[Gentoo_installation_tips_and_tricks#Recovering_from_a_malfunctioning_installation|recovering from a malfunctioning installation]] on the tips and tricks article. Would it not be a good idea to link to that section from the [[Handbook:AMD64/Installation/Base#Entering_the_new_environment|tip that mentions the possibility of recovering an installation]]? -- [[User:Ris|Ris]] ([[User talk:Ris|talk]]) 10:25, 13 March 2023 (UTC) : I want to be able to link out, but it generates a lot of maintenance when anchors within the main change...and they can change unexpectedly. I'd rather write up a new Handbook section that covers how to resume a partially complete installation instead which is inspired by the section you linked... == Minor spellchecking == {{Talk|closed|date=2024-01-03}} * In ''Configuring USE Variables'': With Gentoo users can... --> With Gentoo, users can... * In ''Ready, set go!'': "Then continue withInstalling [sic] the Gentoo base system." This link is unnecessarily redirecting to the next section of the same page. * design principal --> design principle * uncertainty whether --> uncertainty about whether * Microsoft Windows based verification --> Microsoft-Windows-based verification [[User:Avidseeker|Avidseeker]] ([[User talk:Avidseeker|talk]]) 23:52, 28 May 2023 (UTC) : In ''Preparing for a bootloader'': it is necessary prepare the... --> it is necessary to prepare the...--[[User:Lknows|Lknows]] ([[User talk:Lknows|talk]]) 04:36, 26 December 2023 (UTC) :: Good hunting! There are probably more. At least these have been fixed now. Thank you! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 06:55, 4 January 2024 (UTC) == Add info about the new binhost == {{talk|closed|date=2024-01-03}} Recently it was [https://www.gentoo.org/news/2023/12/29/Gentoo-binary.html announced] that Gentoo now has an official binary package host, perhaps there should be info added to {{Link|1=Handbook:AMD64/Installation/Base|section=#Optional:_Selecting_mirrors|2=selecting mirrors}} telling users how to add this if they wish? A POC can be (formatting intentionally removed): <nowiki>==== {{Anchor|Binary package host}} Binary package host ==== </nowiki> <nowiki>Adding a binary package mirror could greatly decrease the install time needed and could be useful for older hardware. The repository configuration for the "binhost" is found in the directory {{Path|/etc/portage/binhost.conf}}, much like how {{Path|{{Link|/etc/portage/repos.conf|repos.conf}}}} functions.</nowiki> <nowiki>{{FileBox|filename=/mnt/gentoo/etc/portage/binhosts.conf/gentoobinhost.conf|title=UK mirror example|1=</nowiki> <nowiki>[binhost]</nowiki> <nowiki>priority = 9999</nowiki> <nowiki>sync-uri = https://mirror.bytemark.co.uk/gentoo/releases/amd64/binpackages/17.1/x86-64/</nowiki> <nowiki>}}</nowiki> [[User:Xarvatium|Xarvatium]] ([[User talk:Xarvatium|talk]]) 21:26, 3 January 2024 (UTC)\ : Good idea. I used your POC as inspiration and this request has been implemented. See [[Special:Diff/1272283/1272285]]. This section may need some tuning in the near future. Curious to know what happens with the system profile number (17.1) and binhost number in the <var>sync-uri</var> value do not line up... I hope there is a mechanism to notify the sysadmin in such a condition. Thanks! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 06:36, 4 January 2024 (UTC) == Make it clearer that the base 'desktop' profile does ''not'' install a default DE == In the "Choosing the right profile" section, there's currently a "Tip" box saying: > Desktop profiles are not exclusively for desktop environments. They are also suitable for minimal window managers like i3 or sway. However, this doesn't make it clear that using a desktop profile doesn't ''inherently'' set up a default DE, and that the base 'desktop' profile in particular certainly doesn't do so. i've seen a couple of posts on the forums recently where people had assumed that they would get a DE installed, rather than the profile merely setting appropriate USE flags. -- [[User:Flexibeast|Flexibeast]] ([[User talk:Flexibeast|talk]]) 06:45, 11 January 2024 (UTC)'
New page wikitext, after the edit (new_wikitext)
'{{Talk page}} == True multilib needs modification in make.conf == {{InfoBox stack |{{InfoBox talk done}} }} When installing selecting the multilib profile itself wasn't sufficient. I only got true multilib support after adding the follwing in make.conf. I think it's worth mentioning it upfront so that people wouldn't have to recompile @world <pre> ABI_X86="64 32" </pre> : No, this is not a good suggestion to make for all Gentoo users to read the Handbook. We recommend only setting enable <code>abi_x86_32</code> as-needed on a per-package basis, not globally. As explained by {{U|iamben}}, "if you enable ABI_X86="32" globally up front, you save a little bit of user configuration time up front but you waste a lot of compile time '''on every upgrade''' '''forever'''". Also, if this was set globally as you suggest, revising those packages later can cause headaches. Kind regards, --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 19:30, 3 October 2016 (UTC) == Chroot on one line == {{InfoBox stack |{{InfoBox talk done|date=Jun 6 2015}} }} It would be imo convenient to have one-liner for the mounts before the chrooting, instead of five separate commands, so that one could easily copy-paste the one command to terminal and execute it in one take I.e., instead of (or, placed after) <pre> root #mount -t proc proc /mnt/gentoo/proc root #mount --rbind /sys /mnt/gentoo/sys root #mount --make-rslave /mnt/gentoo/sys root #mount --rbind /dev /mnt/gentoo/dev root #mount --make-rslave /mnt/gentoo/dev </pre> there ought to be also <pre>mount -t proc proc /mnt/gentoo/proc && mount --rbind /sys /mnt/gentoo/sys && mount --make-rslave /mnt/gentoo/sys && mount --rbind /dev /mnt/gentoo/dev && mount --make-rslave /mnt/gentoo/dev</pre> --[[User:Renergy|Renergy]] ([[User talk:Renergy|talk]]) 19:39, 6 June 2015 (UTC) : Renergy, I can see that may be easier to copy and paste a one line command such as you posted above. Part of the purpose of the Handbook is to teach people how to install Gentoo Linux, not to make the install as fast as possible, which is why we have each command on a separate line. I will think about putting a one-liner like you suggest as a secondary option for people who are in a hurry. Sincerely, --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 22:14, 21 December 2015 (UTC) == Potential security problem == {{InfoBox stack |{{InfoBox talk open|date=Jun 28 2015}} }} Going though the handbook normally leads you through getting the minimal .iso and stage 3 tarball over https, checking hashes and verifying with gpg. All good so far. Here, it tells users to run emerge-webrsync, without any warning that it defaults to using http - enabling a MITM attack. If I understand correctly, this is for downloading and setting up portage, while running as root. By default, emerge-webrsync does not verify gpg signatures, so at this point the system must be considered fundamentally insecure. The user stanley on irc suggested using this procedure: [[Handbook:AMD64/Working/Features#Pulling_validated_Gentoo_ebuild_tree_snapshots]] - it should definitely be mentioned as an option at this stage, since doing it with an already insecure system at the later stage will make little difference. Also, emerge-webrsync should default to using HTTPS. --[[User:OliverUv|OliverUv]] ([[User talk:OliverUv|talk]]) 12:26, 28 June 2015 (UTC) : But this affects all arches, right? See [[Handbook_Talk:Parts/Installation/Base]] --[[User:Charles17|Charles17]] ([[User talk:Charles17|talk]]) 17:43, 20 January 2016 (UTC) :: Hm...I'll see what we can do about this upstream. It would be nice if the mirrors used HTTPS, but I'm not sure we have a good way of enforcing it. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 18:21, 18 November 2016 (UTC) ::: So, the good news is that current Gentoo minimal install images ship with a sufficiently modern Portage (>=2.3.42, with the <code>rsync-verify</code> <var>USE</var> flag set) such that for a vanilla {{c|rsync}}-based {{c|emerge --sync}} (under the recommended {{Path|/etc/portage/repos.conf/gentoo.conf}} settings from the guide: <code>sync-rsync-verify-metamanifest = yes</code> etc.), [https://gentoo.org/support/news-items/2018-01-30-portage-rsync-verification.html signature verification] with [https://gentoo.org/support/news-items/2018-07-11-portage-sync-allow-hardlinks.html failure quarantine] will be carried out. ::: The not so good news is that in [[{{SUBJECTPAGENAME}}#Installing_an_ebuild_repository_snapshot_from_the_web|this section of the handbook]], it is still recommended first to carry out a vanilla {{c|emerge-webrsync}}, which for some mirrors anyway will use unauthenticated HTTP (e.g. http://trumpetti.atm.tut.fi/gentoo), and which does ''not'' (by default) signature verify the downloaded tree. ::: This is easy enough to work around though - just set <code>sync-webrsync-verify-signature = true</code> in the {{c|[gentoo]}} section of {{Path|/etc/portage/repos.conf/gentoo.conf}}, temporarily set <code>sync-type = webrsync</code> in that file also (rather than <code>sync-type = rsync</code>) and then issue <code>emaint sync --auto</code>. This will do all the necessary signature updating etc and then download and verify the daily snapshot (NB - {{c|emerge-webrsync}} will complain if you try to directly invoke it with <code>sync-webrsync-verify-signature = true</code> set; you need to use {{c|emaint sync}} or {{c|emerge --sync}}). Then, once done, just flip back to using <code>sync-type = rsync</code>. This ensures all updates are validated, and doesn't mess the flow of the guide up too much. (I'm just in the process of switching over to recommending this workflow for my own EFI install guide, incidentally.) --[[User:Sakaki|Sakaki]] ([[User talk:Sakaki|talk]]) 13:33, 11 October 2018 (UTC) == Choosing profiles == {{Talk|closed|date=2024-01-04}} I believe profiles should be chosen after the initial reboot at least for {{Keyword|amd64}} and {{Keyword|x86}}. Choosing a desktop profile, in particular, too early causes increased and unnecessary install time added to a user's experience. I think it should be saved until the first reboot. --[[User:Grknight|Grknight]] ([[User talk:Grknight|talk]]) 01:46, 22 October 2015 (UTC) : I will experiment on a virtual machine with this. My initial thoughts are that you're right. Rebuilding world after the profile selection is ''probably'' not a necessary part of the process. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 23:28, 1 February 2016 (UTC) : Also, the profile selection should be updated to 17.0, maybe with a little warning regarding 17.1 which got stabilized recently.--[[User:Charles17|Charles17]] ([[User talk:Charles17|talk]]) 10:28, 27 December 2017 (UTC) Update in progress... --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 02:44, 28 April 2018 (UTC) Revisiting again after some time and many changes made by Gentoo's release engineer team and desktop stage files. I do not believe updating the @world set should increase install time enough to be a concern and it is an important part of the learning process. Especially when considering the introduction of the (optional) {{Link|Handbook:AMD64/Installation/Base#Optional:_Adding_a_binary_package_host|binary package host}} section which I have recently added and if a (relatively recently produced) ''desktop'' stage file is used there are generally only a few dozen packages updates to be performed... modern hardware can handle the compiling and other hardware (at least AMD64 and ARM64) can use the binhost. It also fits nicely into this section so I think it's safe to keep, but perhaps I'll add a little note that installations which are pressed for time can avoid it. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 08:58, 4 January 2024 (UTC) Finished here: [[Special:Diff/1272306/1272318]]. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 10:02, 4 January 2024 (UTC) == Add -qt5 USE flag == {{Talk|closed|date=May 13, 2017}} Let me quote: "gnome gtk -kde -qt4 will compile programs with GNOME (and GTK) support, and not with KDE (and Qt) support, making the system fully tweaked for GNOME (if the architecture supports it)." Please add -qt5 to the previous sentence as well. [[User:Fturco|Fturco]] ([[User talk:Fturco|talk]]) 15:25, 16 April 2017 (UTC) : Good suggestion. Consider it done. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 06:35, 14 May 2017 (UTC) == Will we need Section of "Mounting the boot partition"? == {{Talk|closed|date=2024-01-04}} Hello, Operation of this section is already executed in section of "Preparing the disks".<br /> Haven't we mounting /dev/sda2 on /boot already? Kind regards, --[[User:Komainu8|Komainu8]] ([[User talk:Komainu8|talk]]) 11:04, 13 May 2017 (UTC) : It depends on what install path you take. With this being said, the entire disk section(s) of the Handbook need a major reworking, so I would not be surprised if mounting is inconsistently noted here. I'll leave this open for now since no one is ready to work on fixing the disk section yet... --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 06:39, 14 May 2017 (UTC) : It would be great to have such thing mentioned. --[[User:Wowpetr|Wowpetr]] ([[User talk:Wowpetr|talk]]) 09:25, 12 July 2017 (UTC) :: In this [[Handbook_Talk:AMD64/Installation/Base#Remove_command_to_create_.2Fboot|discussion]], undoing the creation of the ''/boot'' directory was accepted, but mounting is still required depending "on what install path you take". If so, wouldn't be informative to display this in the instructions? I know that if you try to re-mount a partition to the same directory is harmless (no messages are displayed on the shell after execution) but it would be even more educational to the new user to know if this is expected. If not, maybe consider delete [[Handbook:AMD64/Installation/Base#Mounting_the_boot_partition|this]] subsection?--[[User:Neyuru|Neyuru]] ([[User talk:Neyuru|talk]]) 20:03, 5 April 2020 (UTC) : This should now be fixed with the section: [[Handbook:AMD64/Installation/Base#Preparing_for_a_bootloader]]. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 08:48, 4 January 2024 (UTC) == Mounting the necessary filesystems == {{talk|closed|date=July 25, 2017}} It is good to mention that if you interrupt the installation process at any stage later (e.g. by rebooting), you may need to mount these partitions again. --[[User:Wowpetr|Wowpetr]] ([[User talk:Wowpetr|talk]]) 09:25, 12 July 2017 (UTC) : Thanks for the tip. Your suggestion has been implemented! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 23:34, 25 July 2017 (UTC) == Entering the new environment == {{talk|closed|date=July 25, 2017}} It is good to mention that if you interrupt the installation process at any stage inside chroot environment (e.g. by rebooting), you need to chroot again. --[[User:Wowpetr|Wowpetr]] ([[User talk:Wowpetr|talk]]) 09:39, 12 July 2017 (UTC) : Thanks for the tip. Your suggestion has been implemented! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 23:34, 25 July 2017 (UTC) == Warning about 17.x profiles == {{talk|done|date=April 27, 2018}} Please add a big warning before the profile selection instructions, to tell users not to use 17.0 or 17.1 profiles until they have read the corresponding news items and are prepared to follow the migration instructions. [[User:Iamben|Iamben]] ([[User talk:Iamben|talk]]) 15:34, 29 December 2017 (UTC) : Done. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 02:39, 28 April 2018 (UTC) == Typo correction == {{Talk|done|date=July 25, 2019}} Right at the bottom of the page, the line <pre> root #env-update && source /etc/profile && export PS1="(chroot) $PS1" </pre> should read <pre> root #env-update && source /etc/profile && export PS1="(chroot) ${PS1}" </pre> to properly maintain consistency with the previous command under Entering the New Environment [[User:Redchillipadi|Redchillipadi]] ([[User talk:Redchillipadi|talk]]) 02:54, 27 April 2018 (UTC) : It looks that way to me, {{U|Redchillipadi}}. What's the exact link that you're seeing just <code>$PS1</code>? --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 02:38, 28 April 2018 (UTC) My browser says [[{{SUBJECTPAGENAME}}]] PS1 is mentioned under Entering the new environment as <code>${PS1}</code> and at the bottom under Configure Locales as <code>$PS1</code> [[User:Redchillipadi|Redchillipadi]] ([[User talk:Redchillipadi|talk]]) 02:55, 28 April 2018 (UTC) : Fixed ([[Special:Diff/816541/prev]])! For some reason I wasn't seeing it the first time. Thank you! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 17:23, 25 July 2019 (UTC) == Remind the user to fat32 format the esp partition == {{Talk|done|date=18 July 2022}} I'm a new gentoo user but I guess it's not a bad thing to have a novice's view on how this guide is structured. The thing I noticed, following the uefi route is that it would be better to get reminded further down again to format sda2 (the esp partition) as FAT32. It isnt mentioned at the appropriate place. The first time doing this guide, I didn't notice that, ended up installing everything and then the bootloader setup failed because I had the esp as ext2 instead of fat32 (and wasn't able to fix it). Now I'm on my second try due to that. <pre> [...] root #mkfs.ext2 /dev/sda2 root #mkfs.ext4 /dev/sda4 Now create the filesystems on the newly created partitions (or logical volumes)." </pre> It should be placed (or at least mentioned again) here. [[User:AnukWolf|AnukWolf]] ([[User talk:AnukWolf|talk]]) 16:00, 13 October 2018 (UTC : While I agree with the partitioning reminder, do yo really believe that it should be included in this section [[Handbook:AMD64/Installation/Base|Installing the Gentoo base system]]? I think it is more appropriate to include an enhancement in [[Handbook:AMD64/Installation/Disks|Preparing the disks]] section. There are, to this date, 3 discussions regarding this issue there.--[[User:Neyuru|Neyuru]] ([[User talk:Neyuru|talk]]) 19:24, 5 April 2020 (UTC) :: As a new Gentoo user too, I had no problem to use the right filesystem. :: In the [[Handbook:AMD64/Installation/Disks|Preparing the disks]] chapter of 2018 : :: - The "Using UEFI" section explained all that ; it even emphasized the necessity of a FAT variant for the ESP with a "Important" box, and the risk of not being able to boot otherwise. :: - The "Default partitioning scheme" section also indicated and summarized the need for FAT32 for the ESP. :: - The "Applying a filesystem to a partition" section showed the command to create a boot partition in ext2, that's true, but it explicitly stated this was an example (today, this same example is using FAT32, which may be the change you wanted). :: So, the information is already mentioned 2 times (3 times if you're counting the example), at the appropriate place, and with emphasis. :: Also, I agree with {{U|Neyuru}} : there is no use in reminding these things after the [[Handbook:AMD64/Installation/Disks|Preparing the disks]] chapter, as the user is supposed to have applied the relevant filesystems to the partitions after that. :: --[[User:Blacki|Blacki]] ([[User talk:Blacki|talk]]) 07:39, 18 July 2022 (UTC) == Add instructions for bind mounting udev == {{talk|closed|date=2-22-11-27}} os-prober needs {{c|/run/udev}} to function properly and will hang indefinitely if it's not bind mounted from outside. Consider adding a line for bind mounting it from outside the chroot, or at least a small blurb under the mounting to say that other things might need to be mounted. See [[GRUB#os-prober_and_UEFI_in_chroot|this section of the GRUB wiki page]] for details. {{unsigned2|12:21, December 29, 2018‎|Sielicki}} : Thank you for the feedback, {{U|Sielicki}}. I would like to test on a current LiveCD suggested the change before implementing. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 18:24, 25 July 2019 (UTC) :: Uncertain if it was added at the time of your comment here, however the virtual filesystem mount instructions do say to bind mount the {{Path|/run}} directory, which would include the {{Path|udev}} subdirectory. See [[Handbook:AMD64/Installation/Base#Mounting_the_necessary_filesystems]]. This discussion can be closed. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 13:21, 27 November 2022 (UTC) == Remove command to create /boot == {{Talk|closed|date=July 25, 2019}} The /boot directory is already present in the stage3 tarball, so `mkdir /boot' can be removed. Also the paragraph just above needs to be adjusted slightly. --[[User:Rafo|Rafo]] ([[User talk:Rafo|talk]]) 19:02, 1 January 2019 (UTC) : Good point. Suggested changes implemented ([[Special:Diff/816547/prev]]). Thank you, {{U|Rafo}}! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 17:53, 25 July 2019 (UTC) == Minor English grammar correction == {{Talk|done|date=July 25, 2019}} Where it says, "updates can be delayed after the Gentoo installation has finished," I think it should say "delayed '''until''' after." I would change it myself, but I don't have such permissions. --[[User:Dhirsbrunner|Dhirsbrunner]] ([[User talk:Dhirsbrunner|talk]]) 03:58, 24 July 2019 (UTC) : You got it. I have made the suggested change (see [[Special:Diff/816511/prev]]). Thank you for the input! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 17:06, 25 July 2019 (UTC) == Unclear instructions in section 'Configuring Portage' == {{Talk|closed|date=2024-01-04}} In the first subsection 'Installing an ebuild repository snapshot from the web', we tell users that they can skip this subsection if they have no firewalls and a fast network. But in the second subsection 'Optional: Updating the Gentoo ebuild repository', we don't tell those users that they must run 'emerge --sync', because they skipped 'emerge-webrsync'. Instead, we tell them that 'emerge --sync' is optional. So they might skip this subsection as well and won't have a Gentoo ebuild repository. --[[User:Mike155|Mike155]] ([[User talk:Mike155|talk]]) 03:22, 5 November 2019 (UTC) :: Yes. The {{C|emerge --sync}} should be the normal and not optional. Recommending {{C|emerge-webrsync}} without the [[Project:Portage/Repository_Verification#Security_comparison|required manual setup]] as described in [[Handbook:AMD64/Working/Features#Validated_Gentoo_repository_snapshots]] is a bad idea. Better drop it completely or move it to a <code>Tip: In case of limited bandwidth ...</code>.--[[User:Charles17|Charles17]] ([[User talk:Charles17|talk]]) 08:57, 5 November 2019 (UTC) :: Can we make this more clear somehow? We just had this same situation play out on IRC. --[[User:Sam|Sam]] ([[User talk:Sam|talk]]) 17:57, 15 March 2020 (UTC) ::: Same topic [[Handbook_Talk:Parts/Installation/Base#Use_validated_snapshots|here]] and [[Handbook_Talk:Parts/Installation/Base#.28non-validated.29_emerge-webrsync|there]] (talk page for »Parts«)--[[User:Charles17|Charles17]] ([[User talk:Charles17|talk]]) 08:08, 16 March 2020 (UTC) :: With Portage feature enhancements and the flow of the handbook at this point, I believe this concern is no longer an issue. {{C|emerge-webrsync}} performs signature check; {{C|emerge --sync}} is entirely optional. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 08:43, 4 January 2024 (UTC) == Incomprehensible sentence: '... as carefully chosen USE flag defaults may be configured in some ebuilds ...' == {{Talk|closed|date=2019-11-05}} Do we configure USE flag defaults in ebuilds? --[[User:Mike155|Mike155]] ([[User talk:Mike155|talk]]) 18:36, 5 November 2019 (UTC) : You are right, it is poorly worded. I have [[Special:Diff/827128/835781|made it more clear]]. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 00:21, 6 November 2019 (UTC) == Incomprehensible sentence: '... without prompting the user for the licenses previously accepted.' == {{Talk|closed|date=2024-01-04}} The sentence 'Portage uses the ACCEPT_LICENSE variable to determine which packages to allow without prompting the user for the licenses previously accepted.' doesn't seem to be right. Maybe something like: 'Portage uses the ACCEPT_LICENSE variable to determine which packages are allowed to be installed.' --[[User:Mike155|Mike155]] ([[User talk:Mike155|talk]]) 18:36, 5 November 2019 (UTC) : This section has undergone a major reorg and rework. This discussion is stale. See [[Special:Diff/1272302/1272304]]. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 08:36, 4 January 2024 (UTC) == Confusion about per-package exceptions for ACCEPT_LICENSE == {{Talk|closed|date=2022-11-27}} One of the first sentences in paragraph 'Optional: Configuring the ACCEPT_LICENSE variable' is: 'Exceptions can be made per-package in /etc/portage/package.license as well.' The last example of the section shows how to define exceptions in /etc/portage/package.license/kernel. Why is it etc/portage/package.license in one case and /etc/portage/package.license/kernel in the other? I doubt that new users will understand this. --[[User:Mike155|Mike155]] ([[User talk:Mike155|talk]]) 21:24, 5 November 2019 (UTC) : This has been clarified in the following diff: [[Special:Diff/1167615/1169737]]. == Section 'Configure locales': missing reference to /usr/share/i18n/SUPPORTED == {{Talk|closed|date=2020-04-06}} The section tells users that they can/should configure locales in /etc/locale.gen. The section should also tell users that only locales shown in /usr/share/i18n/SUPPORTED are allowed and that they must pay attention to small and capital letters. Maybe we can add a box like the one below (I added such a box in the German translation): {{Tip|A list of supported values is given in file {{Path|/usr/share/i18n/SUPPORTED}}. Please pay attention to small and capital letters and do not use values that are not shown in this file.}} --[[User:Mike155|Mike155]] ([[User talk:Mike155|talk]]) 22:39, 5 November 2019 (UTC) Hello {{U|Mike155}}, this is a welcome enhancement. Thank you for following the recommended format for submitting improvements. I have made the [[Special:Diff/862922/862937|change here]]. Thank you again! Kind regards, --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 08:06, 6 April 2020 (UTC) == What is an 'rsync tree'? == {{Talk|closed|date=2020-04-06}} 'News items were created to provide a communication medium to push critical messages to users via the rsync tree.' What is an 'rsync tree'? Maybe 'Gentoo ebuild tree'? --[[User:Mike155|Mike155]] ([[User talk:Mike155|talk]]) 22:27, 6 November 2019 (UTC) : This terminology has been [[Special:Diff/835997/862907|removed here]] Thank you. --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 07:24, 6 April 2020 (UTC) == Add warning about arch-chroot == {{Talk|closed|date=2020-04-06}} Some users in #gentoo seeking support run into issues with 'bad file descriptor' after using <code>arch-chroot</code>. We should warn about this and recommend they stick to the given commands. --[[User:Sam|Sam]] ([[User talk:Sam|talk]]) 02:47, 30 March 2020 (UTC) : Thank you for the comment however, we cannot provide warnings for all non-recommended software. If someone is having problems using software that is Arch specific (and not available at this time in Gentoo), then they can work that out on the Arch wiki in an Arch bug tracker. We provide instructions to use our [[Handbook:AMD64/Installation/Media#Gentoo_Linux_installation_media|official installation media]] and direction on [[Handbook:AMD64/Installation/Base#Chrooting|properly chrooting]]. Kind regards, --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 07:35, 6 April 2020 (UTC) == Missing locale options for America/Monterrey == {{talk|closed|date=2020-04-06}} Maybe this is a bug of the package and not to be discussed here but, just to inform my findings. I selected the timezone "America/Monterrey" and when configuring the locale with "''nano -w /etc/locale.gen''" I only found the option: "''es_MX ISO-8859-1''" in the file, so I selected it (no other option was present for my language). This is dangerous, as the wiki explains: "'''We strongly suggest to use at least one UTF-8 locale because some applications may require it.'''". I found out the hard way too: I had several compile time problems when emerging GNOME, which where gone if '''adding''' the line "''es_MX.UTF-8 UTF-8''" to the "''/etc/locale.gen''" file. Although this option was not present as an option, I can testify that adding it removed the aforementioned compile errors. Can someone help me file this bug?--[[User:Neyuru|Neyuru]] ([[User talk:Neyuru|talk]]) 03:22, 6 April 2020 (UTC) : Hello. Yes, this is not an issue specific to our installation instructions. If you are confident that you have done everything correctly in your installation and you still believe this is an issue with a package, then you'll probably want to file a bug with GNOME's upstream (NOT Gentoo's Bugzilla). If you otherwise have something you believe is necessary to add to these installation instructions, then please follow our [[Handbook:Main_Page#How_do_I_improve_the_Handbook.3F|recommended format for submitting improvements]]. Kind regards, --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 07:39, 6 April 2020 (UTC) Hello and thank you for the rapid response. Yes, I agree there is nothing wrong in the instructions, but I wonder, is the main problem in the omission of the correct encoding options available in "America/Monterrey"? or in GNOME not supporting some encodings? I tend to gravitate to the first option. It is strange that by specifying this locale only *one* of the options belong to the official language spoken there, and it is not even in UTF-8. This is a list of the options available: {#en_US ISO-8859-1, #en_US.UTF-8 UTF-8, #ja_JP.EUC-JP EUC-JP, #ja_JP.UTF-8 UTF-8, #ja_JP EUC-JP, #en_HK ISO-8859-1, #en_PH ISO-8859-1, #de_DE ISO-8859-1, #de_DE@euro ISO-8859-15, '''#es_MX ISO-8859-1''', #fa_IR UTF-8, #fr_FR ISO-8859-1, #fr_FR@euro ISO-8859-15, #it_IT ISO-8859-1}. I sincerely apologize as this conversation does not belong here but, I wanted to share my experience, if someone could find that useful. --[[User:Neyuru|Neyuru]] ([[User talk:Neyuru|talk]]) 16:50, 7 April 2020 (UTC) : Search for '''/usr/share/i18n/SUPPORTED''' (has been added lately) in the article. --[[User:Charles17|Charles17]] ([[User talk:Charles17|talk]]) 17:57, 7 April 2020 (UTC) == Move Selecting Mirrors section after the chroot entry == {{talk|open}} If a user is not using the Gentoo installation media (and in #gentoo, we often note that it's not necessary to use Gentoo's media), they may not have access to the {{c|mirrorselect}} tool until they enter the chroot. Perhaps it should be moved after the chroot section. --[[User:Sam|Sam]] ([[User talk:Sam|talk]]) 01:51, 24 April 2020 (UTC) : Finally getting around to make this change. Apologies it took so many years to implement! See [[Special:Diff/1272298/1272302]]. Thanks, {{U|sam}}! {{unsigned2|2024-01-04T08:10:45‎|Maffblaster}} :: Mirrorselect is not part of all (any?) stage3 tarballs, so moving the "mirrorselect" section below the chroot does not work in its current state as I experienced. One has to either select the mirrors before chrooting, select them manually or install app-portage/mirrorselect in the chroot (which has to be done after syncing, when already selected mirrors would be preferred (i guess)). Also the green tip is obsolete. I'd suggest moving it before the chroot while preserving the tip. Maybe an edit to https://wiki.gentoo.org/wiki/Installation_alternatives#Installation_from_non-Gentoo_live_environments? --~~~~ == The "locale.gen" file doesn't have template like in the handbook base steps == {{talk|open}} Hi there. During installation of the fresh gentoo, I found that "locale.gen" file from the stage3-amd64-20200607T214504Z doesn't have template like in the handbook steps. I think that it was good idea, if user can uncomment a language that he needs in the locale.gen file instead of to looking for this language param in the man page of locale! What do you think about it? Thanks in advance! --[[User:t0ha|t0ha]] ([[User talk:t0ha|talk]]) 21:15, 12 June 2020 (UTC) == Use "--changed-use" instead of "--newuse" while updating @world == {{talk|open}} "--changed-use" is better for daily Gentoo user. "--newuse" leads to unnecessary rebuild of packages which didn't really change since last build. Recently, the cleanup of ABI_RISCV and related use flags caused rebuild of hundreds of packages, due to the widely use of "--newuse". Many Gentoo users don't realize the existence of "--changed-use". They just follow the Handbook and keep using "--newuse". I heard that "--newuse" was put here to remind base system team not to forget revbmp. But since this Handbook is mostly used by new users, maybe we can add a note about the difference between "--changed-use" and "--newuse" at least. And let the user choose which one they want to use. [[User:Imrebuild|Imrebuild]] ([[User talk:Imrebuild|talk]]) 08:54, 17 October 2020 (UTC) == Gnome no longer requires systemd == {{talk|done}} There are gnome profiles without systemd that use elogind instead. Should the sentence about using >= gnome 3.8 be removed? [[User:Trainz-are-kul|Trainz-are-kul]] ([[User talk:Trainz-are-kul|talk]]) 20:17, 21 November 2020 (UTC) : Done --[[User:Grknight|Grknight]] ([[User talk:Grknight|talk]]) 13:15, 22 November 2020 (UTC) == Mounting of btrfs == {{talk|closed|date=2024-01-03}} I often failed with the handbook when it later comes to <pre> grub-mkconfig -o /boot/grub/grub.cfg /usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?). </pre> ...because there is no / in the 'mount' list. I usually do a mount -a inside the chroot in order to mount all the btrfs subvolumes configured in the fstab there. But / wasn't mounted like that. The simple workaround is and please mention that in the handbook: mount / After that / is mounted again from the internal fstab and grub-mkconfig works. --[[User:Massimo B.|Massimo B.]] ([[User talk:Massimo B.|talk]]) 11:55, 15 December 2021 (UTC) : Hello, {{U|Massimo B.}}, did you put your btrfs rootfs in a separate, non-default btrfs subvolume? Either that, or I'm wondering if you just didn't <code>--rbind</code> {{Path|/dev}} into the chroot... what are the steps for someone to reproduce? If the Handbook is missing a step we'll try to change it, but creating subvolumes is outside Handbook scope... and recursively mounting /dev is already in the Handbook. Thank you, --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 23:13, 20 December 2021 (UTC) : Hi, I have the rootfs on a non-default btrfs subvolume, yes. You mean setting it as default would solve the issue? However grub-mkconfig just parses 'mount' for / and doesn't find it. This is my fstab which I just apply by mount -a && mount / after entering the chroot, mount -a alone does not seem to (re)mount /: <pre>  grep btrfs /etc/fstab LABEL=gentoo / btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes/root 0 1 LABEL=gentoo /mnt/btrfs-top-lvl btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=/ 0 1 #LABEL=gentoo /mnt/snapshots btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=snapshots 0 1 LABEL=gentoo /home btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes/home 0 1 LABEL=gentoo /mnt/data btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes/data 0 1 LABEL=gentoo /tmp btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/tmp 0 1 LABEL=gentoo /usr/portage btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/usr.portage 0 1 LABEL=gentoo /usr/src btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/usr.src 0 1 LABEL=gentoo /var/cache btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/var.cache 0 1 LABEL=gentoo /var/db/repos btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/var.db.repos 0 1 LABEL=gentoo /var/lib/layman btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/var.lib.layman 0 1 LABEL=gentoo /var/tmp btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/var.tmp 0 1 </pre> --[[User:Massimo B.|Massimo B.]] ([[User talk:Massimo B.|talk]]) 10:52, 22 December 2021 (UTC) : Unfortunately I am uncertain what is causing the issue. The handbook doesn't go into detail about btrfs sub-volumes and I don't plan on adding that level of detail in the future. If you figure out the cause of the issue please return here, re-open the discussion so that we notice it, and share the solution. Perhaps a small note could be added specific to btrfs installs which put rootfs on a non-default sub-volume... You could try asking on the mailing list or {{IRC|gentoo}}? Thanks! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 07:01, 4 January 2024 (UTC) == Link to recovery section of tips and tricks == {{talk|open}} There is a section on [[Gentoo_installation_tips_and_tricks#Recovering_from_a_malfunctioning_installation|recovering from a malfunctioning installation]] on the tips and tricks article. Would it not be a good idea to link to that section from the [[Handbook:AMD64/Installation/Base#Entering_the_new_environment|tip that mentions the possibility of recovering an installation]]? -- [[User:Ris|Ris]] ([[User talk:Ris|talk]]) 10:25, 13 March 2023 (UTC) : I want to be able to link out, but it generates a lot of maintenance when anchors within the main change...and they can change unexpectedly. I'd rather write up a new Handbook section that covers how to resume a partially complete installation instead which is inspired by the section you linked... == Minor spellchecking == {{Talk|closed|date=2024-01-03}} * In ''Configuring USE Variables'': With Gentoo users can... --> With Gentoo, users can... * In ''Ready, set go!'': "Then continue withInstalling [sic] the Gentoo base system." This link is unnecessarily redirecting to the next section of the same page. * design principal --> design principle * uncertainty whether --> uncertainty about whether * Microsoft Windows based verification --> Microsoft-Windows-based verification [[User:Avidseeker|Avidseeker]] ([[User talk:Avidseeker|talk]]) 23:52, 28 May 2023 (UTC) : In ''Preparing for a bootloader'': it is necessary prepare the... --> it is necessary to prepare the...--[[User:Lknows|Lknows]] ([[User talk:Lknows|talk]]) 04:36, 26 December 2023 (UTC) :: Good hunting! There are probably more. At least these have been fixed now. Thank you! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 06:55, 4 January 2024 (UTC) == Add info about the new binhost == {{talk|closed|date=2024-01-03}} Recently it was [https://www.gentoo.org/news/2023/12/29/Gentoo-binary.html announced] that Gentoo now has an official binary package host, perhaps there should be info added to {{Link|1=Handbook:AMD64/Installation/Base|section=#Optional:_Selecting_mirrors|2=selecting mirrors}} telling users how to add this if they wish? A POC can be (formatting intentionally removed): <nowiki>==== {{Anchor|Binary package host}} Binary package host ==== </nowiki> <nowiki>Adding a binary package mirror could greatly decrease the install time needed and could be useful for older hardware. The repository configuration for the "binhost" is found in the directory {{Path|/etc/portage/binhost.conf}}, much like how {{Path|{{Link|/etc/portage/repos.conf|repos.conf}}}} functions.</nowiki> <nowiki>{{FileBox|filename=/mnt/gentoo/etc/portage/binhosts.conf/gentoobinhost.conf|title=UK mirror example|1=</nowiki> <nowiki>[binhost]</nowiki> <nowiki>priority = 9999</nowiki> <nowiki>sync-uri = https://mirror.bytemark.co.uk/gentoo/releases/amd64/binpackages/17.1/x86-64/</nowiki> <nowiki>}}</nowiki> [[User:Xarvatium|Xarvatium]] ([[User talk:Xarvatium|talk]]) 21:26, 3 January 2024 (UTC)\ : Good idea. I used your POC as inspiration and this request has been implemented. See [[Special:Diff/1272283/1272285]]. This section may need some tuning in the near future. Curious to know what happens with the system profile number (17.1) and binhost number in the <var>sync-uri</var> value do not line up... I hope there is a mechanism to notify the sysadmin in such a condition. Thanks! --[[User:Maffblaster|Maffblaster]] ([[User talk:Maffblaster|talk]]) 06:36, 4 January 2024 (UTC) == Make it clearer that the base 'desktop' profile does ''not'' install a default DE == In the "Choosing the right profile" section, there's currently a "Tip" box saying: > Desktop profiles are not exclusively for desktop environments. They are also suitable for minimal window managers like i3 or sway. However, this doesn't make it clear that using a desktop profile doesn't ''inherently'' set up a default DE, and that the base 'desktop' profile in particular certainly doesn't do so. i've seen a couple of posts on the forums recently where people had assumed that they would get a DE installed, rather than the profile merely setting appropriate USE flags. -- [[User:Flexibeast|Flexibeast]] ([[User talk:Flexibeast|talk]]) 06:45, 11 January 2024 (UTC)'
Unified diff of changes made by edit (edit_diff)
'@@ -333,5 +333,5 @@ == Move Selecting Mirrors section after the chroot entry == -{{talk|closed|date=2024-01-03}} +{{talk|open}} If a user is not using the Gentoo installation media (and in #gentoo, we often note that it's not necessary to use Gentoo's media), they may not have access to the {{c|mirrorselect}} tool until they enter the chroot. @@ -342,4 +342,5 @@ : Finally getting around to make this change. Apologies it took so many years to implement! See [[Special:Diff/1272298/1272302]]. Thanks, {{U|sam}}! {{unsigned2|2024-01-04T08:10:45‎|Maffblaster}} +:: Mirrorselect is not part of all (any?) stage3 tarballs, so moving the "mirrorselect" section below the chroot does not work in its current state as I experienced. One has to either select the mirrors before chrooting, select them manually or install app-portage/mirrorselect in the chroot (which has to be done after syncing, when already selected mirrors would be preferred (i guess)). Also the green tip is obsolete. I'd suggest moving it before the chroot while preserving the tip. Maybe an edit to https://wiki.gentoo.org/wiki/Installation_alternatives#Installation_from_non-Gentoo_live_environments? --~~~~ == The "locale.gen" file doesn't have template like in the handbook base steps == '
Old page size (old_size)
37182
Lines added in edit (added_lines)
[ 0 => '{{talk|open}}', 1 => ':: Mirrorselect is not part of all (any?) stage3 tarballs, so moving the "mirrorselect" section below the chroot does not work in its current state as I experienced. One has to either select the mirrors before chrooting, select them manually or install app-portage/mirrorselect in the chroot (which has to be done after syncing, when already selected mirrors would be preferred (i guess)). Also the green tip is obsolete. I'd suggest moving it before the chroot while preserving the tip. Maybe an edit to https://wiki.gentoo.org/wiki/Installation_alternatives#Installation_from_non-Gentoo_live_environments? --~~~~' ]
Lines removed in edit (removed_lines)
[ 0 => '{{talk|closed|date=2024-01-03}}' ]
New page text, stripped of any markup (new_text)
' NoteThis is a Talk page - please see the documentation about using talk pages. Add newer comments below older ones, sign comments using four tildes (&#126;&#126;&#126;&#126;), and indent successive comments with colons (:). Add new sections at the bottom of the page, under a heading (== ==). Please remember to mark sections as "open for discussion" using {{talk|open}}, so they will show up in the list of open discussions. Contents 1 True multilib needs modification in make.conf 2 Chroot on one line 3 Potential security problem 4 Choosing profiles 5 Add -qt5 USE flag 6 Will we need Section of "Mounting the boot partition"? 7 Mounting the necessary filesystems 8 Entering the new environment 9 Warning about 17.x profiles 10 Typo correction 11 Remind the user to fat32 format the esp partition 12 Add instructions for bind mounting udev 13 Remove command to create /boot 14 Minor English grammar correction 15 Unclear instructions in section 'Configuring Portage' 16 Incomprehensible sentence: '... as carefully chosen USE flag defaults may be configured in some ebuilds ...' 17 Incomprehensible sentence: '... without prompting the user for the licenses previously accepted.' 18 Confusion about per-package exceptions for ACCEPT_LICENSE 19 Section 'Configure locales': missing reference to /usr/share/i18n/SUPPORTED 20 What is an 'rsync tree'? 21 Add warning about arch-chroot 22 Missing locale options for America/Monterrey 23 Move Selecting Mirrors section after the chroot entry 24 The "locale.gen" file doesn't have template like in the handbook base steps 25 Use "--changed-use" instead of "--newuse" while updating @world 26 Gnome no longer requires systemd 27 Mounting of btrfs 28 Link to recovery section of tips and tricks 29 Minor spellchecking 30 Add info about the new binhost 31 Make it clearer that the base 'desktop' profile does not install a default DE True multilib needs modification in make.conf[edit source] Talk status This discussion is done. When installing selecting the multilib profile itself wasn't sufficient. I only got true multilib support after adding the follwing in make.conf. I think it's worth mentioning it upfront so that people wouldn't have to recompile @world ABI_X86="64 32" No, this is not a good suggestion to make for all Gentoo users to read the Handbook. We recommend only setting enable abi_x86_32 as-needed on a per-package basis, not globally. As explained by Ben Kohler (iamben) , "if you enable ABI_X86="32" globally up front, you save a little bit of user configuration time up front but you waste a lot of compile time on every upgrade forever". Also, if this was set globally as you suggest, revising those packages later can cause headaches. Kind regards, --Maffblaster (talk) 19:30, 3 October 2016 (UTC) Chroot on one line[edit source] Talk status This discussion is done&#160;as of Jun 6 2015. It would be imo convenient to have one-liner for the mounts before the chrooting, instead of five separate commands, so that one could easily copy-paste the one command to terminal and execute it in one take I.e., instead of (or, placed after) root #mount -t proc proc /mnt/gentoo/proc root #mount --rbind /sys /mnt/gentoo/sys root #mount --make-rslave /mnt/gentoo/sys root #mount --rbind /dev /mnt/gentoo/dev root #mount --make-rslave /mnt/gentoo/dev there ought to be also mount -t proc proc /mnt/gentoo/proc &amp;&amp; mount --rbind /sys /mnt/gentoo/sys &amp;&amp; mount --make-rslave /mnt/gentoo/sys &amp;&amp; mount --rbind /dev /mnt/gentoo/dev &amp;&amp; mount --make-rslave /mnt/gentoo/dev --Renergy (talk) 19:39, 6 June 2015 (UTC) Renergy, I can see that may be easier to copy and paste a one line command such as you posted above. Part of the purpose of the Handbook is to teach people how to install Gentoo Linux, not to make the install as fast as possible, which is why we have each command on a separate line. I will think about putting a one-liner like you suggest as a secondary option for people who are in a hurry. Sincerely, --Maffblaster (talk) 22:14, 21 December 2015 (UTC) Potential security problem[edit source] Talk status This discussion is still ongoing&#160;as of Jun 28 2015. Going though the handbook normally leads you through getting the minimal .iso and stage 3 tarball over https, checking hashes and verifying with gpg. All good so far. Here, it tells users to run emerge-webrsync, without any warning that it defaults to using http - enabling a MITM attack. If I understand correctly, this is for downloading and setting up portage, while running as root. By default, emerge-webrsync does not verify gpg signatures, so at this point the system must be considered fundamentally insecure. The user stanley on irc suggested using this procedure: Handbook:AMD64/Working/Features#Pulling_validated_Gentoo_ebuild_tree_snapshots - it should definitely be mentioned as an option at this stage, since doing it with an already insecure system at the later stage will make little difference. Also, emerge-webrsync should default to using HTTPS. --OliverUv (talk) 12:26, 28 June 2015 (UTC) But this affects all arches, right? See Handbook_Talk:Parts/Installation/Base --Charles17 (talk) 17:43, 20 January 2016 (UTC) Hm...I'll see what we can do about this upstream. It would be nice if the mirrors used HTTPS, but I'm not sure we have a good way of enforcing it. --Maffblaster (talk) 18:21, 18 November 2016 (UTC) So, the good news is that current Gentoo minimal install images ship with a sufficiently modern Portage (&gt;=2.3.42, with the rsync-verify USE flag set) such that for a vanilla rsync-based emerge --sync (under the recommended /etc/portage/repos.conf/gentoo.conf settings from the guide: sync-rsync-verify-metamanifest = yes etc.), signature verification with failure quarantine will be carried out. The not so good news is that in this section of the handbook, it is still recommended first to carry out a vanilla emerge-webrsync, which for some mirrors anyway will use unauthenticated HTTP (e.g. http://trumpetti.atm.tut.fi/gentoo), and which does not (by default) signature verify the downloaded tree. This is easy enough to work around though - just set sync-webrsync-verify-signature = true in the [gentoo] section of /etc/portage/repos.conf/gentoo.conf, temporarily set sync-type = webrsync in that file also (rather than sync-type = rsync) and then issue emaint sync --auto. This will do all the necessary signature updating etc and then download and verify the daily snapshot (NB - emerge-webrsync will complain if you try to directly invoke it with sync-webrsync-verify-signature = true set; you need to use emaint sync or emerge --sync). Then, once done, just flip back to using sync-type = rsync. This ensures all updates are validated, and doesn't mess the flow of the guide up too much. (I'm just in the process of switching over to recommending this workflow for my own EFI install guide, incidentally.) --Sakaki (talk) 13:33, 11 October 2018 (UTC) Choosing profiles[edit source] Talk status This discussion is done&#160;as of 2024-01-04. I believe profiles should be chosen after the initial reboot at least for amd64 and x86. Choosing a desktop profile, in particular, too early causes increased and unnecessary install time added to a user's experience. I think it should be saved until the first reboot. --Grknight (talk) 01:46, 22 October 2015 (UTC) I will experiment on a virtual machine with this. My initial thoughts are that you're right. Rebuilding world after the profile selection is probably not a necessary part of the process. --Maffblaster (talk) 23:28, 1 February 2016 (UTC) Also, the profile selection should be updated to 17.0, maybe with a little warning regarding 17.1 which got stabilized recently.--Charles17 (talk) 10:28, 27 December 2017 (UTC) Update in progress... --Maffblaster (talk) 02:44, 28 April 2018 (UTC) Revisiting again after some time and many changes made by Gentoo's release engineer team and desktop stage files. I do not believe updating the @world set should increase install time enough to be a concern and it is an important part of the learning process. Especially when considering the introduction of the (optional) binary package host section which I have recently added and if a (relatively recently produced) desktop stage file is used there are generally only a few dozen packages updates to be performed... modern hardware can handle the compiling and other hardware (at least AMD64 and ARM64) can use the binhost. It also fits nicely into this section so I think it's safe to keep, but perhaps I'll add a little note that installations which are pressed for time can avoid it. --Maffblaster (talk) 08:58, 4 January 2024 (UTC) Finished here: Special:Diff/1272306/1272318. --Maffblaster (talk) 10:02, 4 January 2024 (UTC) Add -qt5 USE flag[edit source] Talk status This discussion is done&#160;as of May 13, 2017. Let me quote: "gnome gtk -kde -qt4 will compile programs with GNOME (and GTK) support, and not with KDE (and Qt) support, making the system fully tweaked for GNOME (if the architecture supports it)." Please add -qt5 to the previous sentence as well. Fturco (talk) 15:25, 16 April 2017 (UTC) Good suggestion. Consider it done. --Maffblaster (talk) 06:35, 14 May 2017 (UTC) Will we need Section of "Mounting the boot partition"?[edit source] Talk status This discussion is done&#160;as of 2024-01-04. Hello, Operation of this section is already executed in section of "Preparing the disks". Haven't we mounting /dev/sda2 on /boot already? Kind regards, --Komainu8 (talk) 11:04, 13 May 2017 (UTC) It depends on what install path you take. With this being said, the entire disk section(s) of the Handbook need a major reworking, so I would not be surprised if mounting is inconsistently noted here. I'll leave this open for now since no one is ready to work on fixing the disk section yet... --Maffblaster (talk) 06:39, 14 May 2017 (UTC) It would be great to have such thing mentioned. --Wowpetr (talk) 09:25, 12 July 2017 (UTC) In this discussion, undoing the creation of the /boot directory was accepted, but mounting is still required depending "on what install path you take". If so, wouldn't be informative to display this in the instructions? I know that if you try to re-mount a partition to the same directory is harmless (no messages are displayed on the shell after execution) but it would be even more educational to the new user to know if this is expected. If not, maybe consider delete this subsection?--Neyuru (talk) 20:03, 5 April 2020 (UTC) This should now be fixed with the section: Handbook:AMD64/Installation/Base#Preparing_for_a_bootloader. --Maffblaster (talk) 08:48, 4 January 2024 (UTC) Mounting the necessary filesystems[edit source] Talk status This discussion is done&#160;as of July 25, 2017. It is good to mention that if you interrupt the installation process at any stage later (e.g. by rebooting), you may need to mount these partitions again. --Wowpetr (talk) 09:25, 12 July 2017 (UTC) Thanks for the tip. Your suggestion has been implemented! --Maffblaster (talk) 23:34, 25 July 2017 (UTC) Entering the new environment[edit source] Talk status This discussion is done&#160;as of July 25, 2017. It is good to mention that if you interrupt the installation process at any stage inside chroot environment (e.g. by rebooting), you need to chroot again. --Wowpetr (talk) 09:39, 12 July 2017 (UTC) Thanks for the tip. Your suggestion has been implemented! --Maffblaster (talk) 23:34, 25 July 2017 (UTC) Warning about 17.x profiles[edit source] Talk status This discussion is done&#160;as of April 27, 2018. Please add a big warning before the profile selection instructions, to tell users not to use 17.0 or 17.1 profiles until they have read the corresponding news items and are prepared to follow the migration instructions. Iamben (talk) 15:34, 29 December 2017 (UTC) Done. --Maffblaster (talk) 02:39, 28 April 2018 (UTC) Typo correction[edit source] Talk status This discussion is done&#160;as of July 25, 2019. Right at the bottom of the page, the line root #env-update &amp;&amp; source /etc/profile &amp;&amp; export PS1="(chroot) $PS1" should read root #env-update &amp;&amp; source /etc/profile &amp;&amp; export PS1="(chroot) ${PS1}" to properly maintain consistency with the previous command under Entering the New Environment Redchillipadi (talk) 02:54, 27 April 2018 (UTC) It looks that way to me, Redchillipadi . What's the exact link that you're seeing just $PS1? --Maffblaster (talk) 02:38, 28 April 2018 (UTC) My browser says Handbook:AMD64/Installation/Base PS1 is mentioned under Entering the new environment as ${PS1} and at the bottom under Configure Locales as $PS1 Redchillipadi (talk) 02:55, 28 April 2018 (UTC) Fixed (Special:Diff/816541/prev)! For some reason I wasn't seeing it the first time. Thank you! --Maffblaster (talk) 17:23, 25 July 2019 (UTC) Remind the user to fat32 format the esp partition[edit source] Talk status This discussion is done&#160;as of 18 July 2022. I'm a new gentoo user but I guess it's not a bad thing to have a novice's view on how this guide is structured. The thing I noticed, following the uefi route is that it would be better to get reminded further down again to format sda2 (the esp partition) as FAT32. It isnt mentioned at the appropriate place. The first time doing this guide, I didn't notice that, ended up installing everything and then the bootloader setup failed because I had the esp as ext2 instead of fat32 (and wasn't able to fix it). Now I'm on my second try due to that. [...] root #mkfs.ext2 /dev/sda2 root #mkfs.ext4 /dev/sda4 Now create the filesystems on the newly created partitions (or logical volumes)." It should be placed (or at least mentioned again) here. AnukWolf (talk) 16:00, 13 October 2018 (UTC While I agree with the partitioning reminder, do yo really believe that it should be included in this section Installing the Gentoo base system? I think it is more appropriate to include an enhancement in Preparing the disks section. There are, to this date, 3 discussions regarding this issue there.--Neyuru (talk) 19:24, 5 April 2020 (UTC) As a new Gentoo user too, I had no problem to use the right filesystem. In the Preparing the disks chapter of 2018&#160;: - The "Using UEFI" section explained all that&#160;; it even emphasized the necessity of a FAT variant for the ESP with a "Important" box, and the risk of not being able to boot otherwise. - The "Default partitioning scheme" section also indicated and summarized the need for FAT32 for the ESP. - The "Applying a filesystem to a partition" section showed the command to create a boot partition in ext2, that's true, but it explicitly stated this was an example (today, this same example is using FAT32, which may be the change you wanted). So, the information is already mentioned 2 times (3 times if you're counting the example), at the appropriate place, and with emphasis. Also, I agree with Neyuru &#160;: there is no use in reminding these things after the Preparing the disks chapter, as the user is supposed to have applied the relevant filesystems to the partitions after that. --Blacki (talk) 07:39, 18 July 2022 (UTC) Add instructions for bind mounting udev[edit source] Talk status This discussion is done. os-prober needs /run/udev to function properly and will hang indefinitely if it's not bind mounted from outside. Consider adding a line for bind mounting it from outside the chroot, or at least a small blurb under the mounting to say that other things might need to be mounted. See this section of the GRUB wiki page for details. —&#160;The preceding unsigned comment was added by Sielicki (talk • contribs) 12:21, December 29, 2018‎ Thank you for the feedback, Sielicki . I would like to test on a current LiveCD suggested the change before implementing. --Maffblaster (talk) 18:24, 25 July 2019 (UTC) Uncertain if it was added at the time of your comment here, however the virtual filesystem mount instructions do say to bind mount the /run directory, which would include the udev subdirectory. See Handbook:AMD64/Installation/Base#Mounting_the_necessary_filesystems. This discussion can be closed. --Maffblaster (talk) 13:21, 27 November 2022 (UTC) Remove command to create /boot[edit source] Talk status This discussion is done&#160;as of July 25, 2019. The /boot directory is already present in the stage3 tarball, so `mkdir /boot' can be removed. Also the paragraph just above needs to be adjusted slightly. --Rafo (talk) 19:02, 1 January 2019 (UTC) Good point. Suggested changes implemented (Special:Diff/816547/prev). Thank you, Rafo ! --Maffblaster (talk) 17:53, 25 July 2019 (UTC) Minor English grammar correction[edit source] Talk status This discussion is done&#160;as of July 25, 2019. Where it says, "updates can be delayed after the Gentoo installation has finished," I think it should say "delayed until after." I would change it myself, but I don't have such permissions. --Dhirsbrunner (talk) 03:58, 24 July 2019 (UTC) You got it. I have made the suggested change (see Special:Diff/816511/prev). Thank you for the input! --Maffblaster (talk) 17:06, 25 July 2019 (UTC) Unclear instructions in section 'Configuring Portage'[edit source] Talk status This discussion is done&#160;as of 2024-01-04. In the first subsection 'Installing an ebuild repository snapshot from the web', we tell users that they can skip this subsection if they have no firewalls and a fast network. But in the second subsection 'Optional: Updating the Gentoo ebuild repository', we don't tell those users that they must run 'emerge --sync', because they skipped 'emerge-webrsync'. Instead, we tell them that 'emerge --sync' is optional. So they might skip this subsection as well and won't have a Gentoo ebuild repository. --Mike155 (talk) 03:22, 5 November 2019 (UTC) Yes. The emerge --sync should be the normal and not optional. Recommending emerge-webrsync without the required manual setup as described in Handbook:AMD64/Working/Features#Validated_Gentoo_repository_snapshots is a bad idea. Better drop it completely or move it to a Tip: In case of limited bandwidth ....--Charles17 (talk) 08:57, 5 November 2019 (UTC) Can we make this more clear somehow? We just had this same situation play out on IRC. --Sam (talk) 17:57, 15 March 2020 (UTC) Same topic here and there (talk page for »Parts«)--Charles17 (talk) 08:08, 16 March 2020 (UTC) With Portage feature enhancements and the flow of the handbook at this point, I believe this concern is no longer an issue. emerge-webrsync performs signature check; emerge --sync is entirely optional. --Maffblaster (talk) 08:43, 4 January 2024 (UTC) Incomprehensible sentence: '... as carefully chosen USE flag defaults may be configured in some ebuilds ...'[edit source] Talk status This discussion is done&#160;as of 2019-11-05. Do we configure USE flag defaults in ebuilds? --Mike155 (talk) 18:36, 5 November 2019 (UTC) You are right, it is poorly worded. I have made it more clear. --Maffblaster (talk) 00:21, 6 November 2019 (UTC) Incomprehensible sentence: '... without prompting the user for the licenses previously accepted.'[edit source] Talk status This discussion is done&#160;as of 2024-01-04. The sentence 'Portage uses the ACCEPT_LICENSE variable to determine which packages to allow without prompting the user for the licenses previously accepted.' doesn't seem to be right. Maybe something like: 'Portage uses the ACCEPT_LICENSE variable to determine which packages are allowed to be installed.' --Mike155 (talk) 18:36, 5 November 2019 (UTC) This section has undergone a major reorg and rework. This discussion is stale. See Special:Diff/1272302/1272304. --Maffblaster (talk) 08:36, 4 January 2024 (UTC) Confusion about per-package exceptions for ACCEPT_LICENSE[edit source] Talk status This discussion is done&#160;as of 2022-11-27. One of the first sentences in paragraph 'Optional: Configuring the ACCEPT_LICENSE variable' is: 'Exceptions can be made per-package in /etc/portage/package.license as well.' The last example of the section shows how to define exceptions in /etc/portage/package.license/kernel. Why is it etc/portage/package.license in one case and /etc/portage/package.license/kernel in the other? I doubt that new users will understand this. --Mike155 (talk) 21:24, 5 November 2019 (UTC) This has been clarified in the following diff: Special:Diff/1167615/1169737. Section 'Configure locales': missing reference to /usr/share/i18n/SUPPORTED[edit source] Talk status This discussion is done&#160;as of 2020-04-06. The section tells users that they can/should configure locales in /etc/locale.gen. The section should also tell users that only locales shown in /usr/share/i18n/SUPPORTED are allowed and that they must pay attention to small and capital letters. Maybe we can add a box like the one below (I added such a box in the German translation): TipA list of supported values is given in file /usr/share/i18n/SUPPORTED. Please pay attention to small and capital letters and do not use values that are not shown in this file. --Mike155 (talk) 22:39, 5 November 2019 (UTC) Hello Mike155 , this is a welcome enhancement. Thank you for following the recommended format for submitting improvements. I have made the change here. Thank you again! Kind regards, --Maffblaster (talk) 08:06, 6 April 2020 (UTC) What is an 'rsync tree'?[edit source] Talk status This discussion is done&#160;as of 2020-04-06. 'News items were created to provide a communication medium to push critical messages to users via the rsync tree.' What is an 'rsync tree'? Maybe 'Gentoo ebuild tree'? --Mike155 (talk) 22:27, 6 November 2019 (UTC) This terminology has been removed here Thank you. --Maffblaster (talk) 07:24, 6 April 2020 (UTC) Add warning about arch-chroot[edit source] Talk status This discussion is done&#160;as of 2020-04-06. Some users in #gentoo seeking support run into issues with 'bad file descriptor' after using arch-chroot. We should warn about this and recommend they stick to the given commands. --Sam (talk) 02:47, 30 March 2020 (UTC) Thank you for the comment however, we cannot provide warnings for all non-recommended software. If someone is having problems using software that is Arch specific (and not available at this time in Gentoo), then they can work that out on the Arch wiki in an Arch bug tracker. We provide instructions to use our official installation media and direction on properly chrooting. Kind regards, --Maffblaster (talk) 07:35, 6 April 2020 (UTC) Missing locale options for America/Monterrey[edit source] Talk status This discussion is done&#160;as of 2020-04-06. Maybe this is a bug of the package and not to be discussed here but, just to inform my findings. I selected the timezone "America/Monterrey" and when configuring the locale with "nano -w /etc/locale.gen" I only found the option: "es_MX ISO-8859-1" in the file, so I selected it (no other option was present for my language). This is dangerous, as the wiki explains: "We strongly suggest to use at least one UTF-8 locale because some applications may require it.". I found out the hard way too: I had several compile time problems when emerging GNOME, which where gone if adding the line "es_MX.UTF-8 UTF-8" to the "/etc/locale.gen" file. Although this option was not present as an option, I can testify that adding it removed the aforementioned compile errors. Can someone help me file this bug?--Neyuru (talk) 03:22, 6 April 2020 (UTC) Hello. Yes, this is not an issue specific to our installation instructions. If you are confident that you have done everything correctly in your installation and you still believe this is an issue with a package, then you'll probably want to file a bug with GNOME's upstream (NOT Gentoo's Bugzilla). If you otherwise have something you believe is necessary to add to these installation instructions, then please follow our recommended format for submitting improvements. Kind regards, --Maffblaster (talk) 07:39, 6 April 2020 (UTC) Hello and thank you for the rapid response. Yes, I agree there is nothing wrong in the instructions, but I wonder, is the main problem in the omission of the correct encoding options available in "America/Monterrey"? or in GNOME not supporting some encodings? I tend to gravitate to the first option. It is strange that by specifying this locale only *one* of the options belong to the official language spoken there, and it is not even in UTF-8. This is a list of the options available: {#en_US ISO-8859-1, #en_US.UTF-8 UTF-8, #ja_JP.EUC-JP EUC-JP, #ja_JP.UTF-8 UTF-8, #ja_JP EUC-JP, #en_HK ISO-8859-1, #en_PH ISO-8859-1, #de_DE ISO-8859-1, #de_DE@euro ISO-8859-15, #es_MX ISO-8859-1, #fa_IR UTF-8, #fr_FR ISO-8859-1, #fr_FR@euro ISO-8859-15, #it_IT ISO-8859-1}. I sincerely apologize as this conversation does not belong here but, I wanted to share my experience, if someone could find that useful. --Neyuru (talk) 16:50, 7 April 2020 (UTC) Search for /usr/share/i18n/SUPPORTED (has been added lately) in the article. --Charles17 (talk) 17:57, 7 April 2020 (UTC) Move Selecting Mirrors section after the chroot entry[edit source] Talk status This discussion is still ongoing. If a user is not using the Gentoo installation media (and in #gentoo, we often note that it's not necessary to use Gentoo's media), they may not have access to the mirrorselect tool until they enter the chroot. Perhaps it should be moved after the chroot section. --Sam (talk) 01:51, 24 April 2020 (UTC) Finally getting around to make this change. Apologies it took so many years to implement! See Special:Diff/1272298/1272302. Thanks, Sam James (sam) ! —&#160;The preceding unsigned comment was added by Maffblaster (talk • contribs) 2024-01-04T08:10:45‎ Mirrorselect is not part of all (any?) stage3 tarballs, so moving the "mirrorselect" section below the chroot does not work in its current state as I experienced. One has to either select the mirrors before chrooting, select them manually or install app-portage/mirrorselect in the chroot (which has to be done after syncing, when already selected mirrors would be preferred (i guess)). Also the green tip is obsolete. I'd suggest moving it before the chroot while preserving the tip. Maybe an edit to https://wiki.gentoo.org/wiki/Installation_alternatives#Installation_from_non-Gentoo_live_environments? --Schnecki (talk) 16:14, 20 January 2024 (UTC) The "locale.gen" file doesn't have template like in the handbook base steps[edit source] Talk status This discussion is still ongoing. Hi there. During installation of the fresh gentoo, I found that "locale.gen" file from the stage3-amd64-20200607T214504Z doesn't have template like in the handbook steps. I think that it was good idea, if user can uncomment a language that he needs in the locale.gen file instead of to looking for this language param in the man page of locale! What do you think about it? Thanks in advance! --t0ha (talk) 21:15, 12 June 2020 (UTC) Use "--changed-use" instead of "--newuse" while updating @world[edit source] Talk status This discussion is still ongoing. "--changed-use" is better for daily Gentoo user. "--newuse" leads to unnecessary rebuild of packages which didn't really change since last build. Recently, the cleanup of ABI_RISCV and related use flags caused rebuild of hundreds of packages, due to the widely use of "--newuse". Many Gentoo users don't realize the existence of "--changed-use". They just follow the Handbook and keep using "--newuse". I heard that "--newuse" was put here to remind base system team not to forget revbmp. But since this Handbook is mostly used by new users, maybe we can add a note about the difference between "--changed-use" and "--newuse" at least. And let the user choose which one they want to use. Imrebuild (talk) 08:54, 17 October 2020 (UTC) Gnome no longer requires systemd[edit source] Talk status This discussion is done. There are gnome profiles without systemd that use elogind instead. Should the sentence about using &gt;= gnome 3.8 be removed? Trainz-are-kul (talk) 20:17, 21 November 2020 (UTC) Done --Grknight (talk) 13:15, 22 November 2020 (UTC) Mounting of btrfs[edit source] Talk status This discussion is done&#160;as of 2024-01-03. I often failed with the handbook when it later comes to grub-mkconfig -o /boot/grub/grub.cfg /usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?). ...because there is no / in the 'mount' list. I usually do a mount -a inside the chroot in order to mount all the btrfs subvolumes configured in the fstab there. But / wasn't mounted like that. The simple workaround is and please mention that in the handbook: mount / After that / is mounted again from the internal fstab and grub-mkconfig works. --Massimo B. (talk) 11:55, 15 December 2021 (UTC) Hello, Massimo B. , did you put your btrfs rootfs in a separate, non-default btrfs subvolume? Either that, or I'm wondering if you just didn't --rbind /dev into the chroot... what are the steps for someone to reproduce? If the Handbook is missing a step we'll try to change it, but creating subvolumes is outside Handbook scope... and recursively mounting /dev is already in the Handbook. Thank you, --Maffblaster (talk) 23:13, 20 December 2021 (UTC) Hi, I have the rootfs on a non-default btrfs subvolume, yes. You mean setting it as default would solve the issue? However grub-mkconfig just parses 'mount' for / and doesn't find it. This is my fstab which I just apply by mount -a &amp;&amp; mount / after entering the chroot, mount -a alone does not seem to (re)mount /: &#160;grep btrfs /etc/fstab LABEL=gentoo / btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes/root 0 1 LABEL=gentoo /mnt/btrfs-top-lvl btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=/ 0 1 #LABEL=gentoo /mnt/snapshots btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=snapshots 0 1 LABEL=gentoo /home btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes/home 0 1 LABEL=gentoo /mnt/data btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes/data 0 1 LABEL=gentoo /tmp btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/tmp 0 1 LABEL=gentoo /usr/portage btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/usr.portage 0 1 LABEL=gentoo /usr/src btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/usr.src 0 1 LABEL=gentoo /var/cache btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/var.cache 0 1 LABEL=gentoo /var/db/repos btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/var.db.repos 0 1 LABEL=gentoo /var/lib/layman btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/var.lib.layman 0 1 LABEL=gentoo /var/tmp btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/var.tmp 0 1 --Massimo B. (talk) 10:52, 22 December 2021 (UTC) Unfortunately I am uncertain what is causing the issue. The handbook doesn't go into detail about btrfs sub-volumes and I don't plan on adding that level of detail in the future. If you figure out the cause of the issue please return here, re-open the discussion so that we notice it, and share the solution. Perhaps a small note could be added specific to btrfs installs which put rootfs on a non-default sub-volume... You could try asking on the mailing list or #gentoo (webchat)? Thanks! --Maffblaster (talk) 07:01, 4 January 2024 (UTC) Link to recovery section of tips and tricks[edit source] Talk status This discussion is still ongoing. There is a section on recovering from a malfunctioning installation on the tips and tricks article. Would it not be a good idea to link to that section from the tip that mentions the possibility of recovering an installation? -- Ris (talk) 10:25, 13 March 2023 (UTC) I want to be able to link out, but it generates a lot of maintenance when anchors within the main change...and they can change unexpectedly. I'd rather write up a new Handbook section that covers how to resume a partially complete installation instead which is inspired by the section you linked... Minor spellchecking[edit source] Talk status This discussion is done&#160;as of 2024-01-03. In Configuring USE Variables: With Gentoo users can... --&gt; With Gentoo, users can... In Ready, set go!: "Then continue withInstalling [sic] the Gentoo base system." This link is unnecessarily redirecting to the next section of the same page. design principal --&gt; design principle uncertainty whether --&gt; uncertainty about whether Microsoft Windows based verification --&gt; Microsoft-Windows-based verification Avidseeker (talk) 23:52, 28 May 2023 (UTC) In Preparing for a bootloader: it is necessary prepare the... --&gt; it is necessary to prepare the...--Lknows (talk) 04:36, 26 December 2023 (UTC) Good hunting! There are probably more. At least these have been fixed now. Thank you! --Maffblaster (talk) 06:55, 4 January 2024 (UTC) Add info about the new binhost[edit source] Talk status This discussion is done&#160;as of 2024-01-03. Recently it was announced that Gentoo now has an official binary package host, perhaps there should be info added to selecting mirrors telling users how to add this if they wish? A POC can be (formatting intentionally removed): ==== {{Anchor|Binary package host}} Binary package host ==== Adding a binary package mirror could greatly decrease the install time needed and could be useful for older hardware. The repository configuration for the "binhost" is found in the directory {{Path|/etc/portage/binhost.conf}}, much like how {{Path|{{Link|/etc/portage/repos.conf|repos.conf}}}} functions. {{FileBox|filename=/mnt/gentoo/etc/portage/binhosts.conf/gentoobinhost.conf|title=UK mirror example|1= [binhost] priority = 9999 sync-uri = https://mirror.bytemark.co.uk/gentoo/releases/amd64/binpackages/17.1/x86-64/ }} Xarvatium (talk) 21:26, 3 January 2024 (UTC)\ Good idea. I used your POC as inspiration and this request has been implemented. See Special:Diff/1272283/1272285. This section may need some tuning in the near future. Curious to know what happens with the system profile number (17.1) and binhost number in the sync-uri value do not line up... I hope there is a mechanism to notify the sysadmin in such a condition. Thanks! --Maffblaster (talk) 06:36, 4 January 2024 (UTC) Make it clearer that the base 'desktop' profile does not install a default DE[edit source] In the "Choosing the right profile" section, there's currently a "Tip" box saying: &gt; Desktop profiles are not exclusively for desktop environments. They are also suitable for minimal window managers like i3 or sway. However, this doesn't make it clear that using a desktop profile doesn't inherently set up a default DE, and that the base 'desktop' profile in particular certainly doesn't do so. i've seen a couple of posts on the forums recently where people had assumed that they would get a DE installed, rather than the profile merely setting appropriate USE flags. -- Flexibeast (talk) 06:45, 11 January 2024 (UTC)'
Parsed HTML source of the new revision (new_html)
'<div class="mw-parser-output"><div class="alert alert-info gw-box" style="padding-top: 8px; padding-bottom: 8px;"><strong><i class="fa fa-sticky-note-o fa-rotate-180"></i> Note</strong><br />This is a <i>Talk page</i> - please see the documentation about <a href="/wiki/Help:Talk_pages" title="Help:Talk pages">using talk pages</a>. Add newer <i>comments</i> below older ones, <b><a href="/wiki/Help:Signatures" title="Help:Signatures">sign comments</a> using four tildes</b> (<code>&#126;&#126;&#126;&#126;</code>), and indent successive comments with colons (<code>:</code>). Add new <i>sections</i> at the bottom of the page, under a heading (<code>== ==</code>). Please remember to <b>mark sections as "open for discussion"</b> using <code>{{talk|open}}</code>, so they will show up in the list of <a href="/wiki/Category:Open_discussions" title="Category:Open discussions">open discussions</a>.</div> <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="#True_multilib_needs_modification_in_make.conf"><span class="tocnumber">1</span> <span class="toctext">True multilib needs modification in make.conf</span></a></li> <li class="toclevel-1 tocsection-2"><a href="#Chroot_on_one_line"><span class="tocnumber">2</span> <span class="toctext">Chroot on one line</span></a></li> <li class="toclevel-1 tocsection-3"><a href="#Potential_security_problem"><span class="tocnumber">3</span> <span class="toctext">Potential security problem</span></a></li> <li class="toclevel-1 tocsection-4"><a href="#Choosing_profiles"><span class="tocnumber">4</span> <span class="toctext">Choosing profiles</span></a></li> <li class="toclevel-1 tocsection-5"><a href="#Add_-qt5_USE_flag"><span class="tocnumber">5</span> <span class="toctext">Add -qt5 USE flag</span></a></li> <li class="toclevel-1 tocsection-6"><a href="#Will_we_need_Section_of_.22Mounting_the_boot_partition.22.3F"><span class="tocnumber">6</span> <span class="toctext">Will we need Section of "Mounting the boot partition"?</span></a></li> <li class="toclevel-1 tocsection-7"><a href="#Mounting_the_necessary_filesystems"><span class="tocnumber">7</span> <span class="toctext">Mounting the necessary filesystems</span></a></li> <li class="toclevel-1 tocsection-8"><a href="#Entering_the_new_environment"><span class="tocnumber">8</span> <span class="toctext">Entering the new environment</span></a></li> <li class="toclevel-1 tocsection-9"><a href="#Warning_about_17.x_profiles"><span class="tocnumber">9</span> <span class="toctext">Warning about 17.x profiles</span></a></li> <li class="toclevel-1 tocsection-10"><a href="#Typo_correction"><span class="tocnumber">10</span> <span class="toctext">Typo correction</span></a></li> <li class="toclevel-1 tocsection-11"><a href="#Remind_the_user_to_fat32_format_the_esp_partition"><span class="tocnumber">11</span> <span class="toctext">Remind the user to fat32 format the esp partition</span></a></li> <li class="toclevel-1 tocsection-12"><a href="#Add_instructions_for_bind_mounting_udev"><span class="tocnumber">12</span> <span class="toctext">Add instructions for bind mounting udev</span></a></li> <li class="toclevel-1 tocsection-13"><a href="#Remove_command_to_create_.2Fboot"><span class="tocnumber">13</span> <span class="toctext">Remove command to create /boot</span></a></li> <li class="toclevel-1 tocsection-14"><a href="#Minor_English_grammar_correction"><span class="tocnumber">14</span> <span class="toctext">Minor English grammar correction</span></a></li> <li class="toclevel-1 tocsection-15"><a href="#Unclear_instructions_in_section_.27Configuring_Portage.27"><span class="tocnumber">15</span> <span class="toctext">Unclear instructions in section 'Configuring Portage'</span></a></li> <li class="toclevel-1 tocsection-16"><a href="#Incomprehensible_sentence:_.27..._as_carefully_chosen_USE_flag_defaults_may_be_configured_in_some_ebuilds_....27"><span class="tocnumber">16</span> <span class="toctext">Incomprehensible sentence: '... as carefully chosen USE flag defaults may be configured in some ebuilds ...'</span></a></li> <li class="toclevel-1 tocsection-17"><a href="#Incomprehensible_sentence:_.27..._without_prompting_the_user_for_the_licenses_previously_accepted..27"><span class="tocnumber">17</span> <span class="toctext">Incomprehensible sentence: '... without prompting the user for the licenses previously accepted.'</span></a></li> <li class="toclevel-1 tocsection-18"><a href="#Confusion_about_per-package_exceptions_for_ACCEPT_LICENSE"><span class="tocnumber">18</span> <span class="toctext">Confusion about per-package exceptions for ACCEPT_LICENSE</span></a></li> <li class="toclevel-1 tocsection-19"><a href="#Section_.27Configure_locales.27:_missing_reference_to_.2Fusr.2Fshare.2Fi18n.2FSUPPORTED"><span class="tocnumber">19</span> <span class="toctext">Section 'Configure locales': missing reference to /usr/share/i18n/SUPPORTED</span></a></li> <li class="toclevel-1 tocsection-20"><a href="#What_is_an_.27rsync_tree.27.3F"><span class="tocnumber">20</span> <span class="toctext">What is an 'rsync tree'?</span></a></li> <li class="toclevel-1 tocsection-21"><a href="#Add_warning_about_arch-chroot"><span class="tocnumber">21</span> <span class="toctext">Add warning about arch-chroot</span></a></li> <li class="toclevel-1 tocsection-22"><a href="#Missing_locale_options_for_America.2FMonterrey"><span class="tocnumber">22</span> <span class="toctext">Missing locale options for America/Monterrey</span></a></li> <li class="toclevel-1 tocsection-23"><a href="#Move_Selecting_Mirrors_section_after_the_chroot_entry"><span class="tocnumber">23</span> <span class="toctext">Move Selecting Mirrors section after the chroot entry</span></a></li> <li class="toclevel-1 tocsection-24"><a href="#The_.22locale.gen.22_file_doesn.27t_have_template_like_in_the_handbook_base_steps"><span class="tocnumber">24</span> <span class="toctext">The "locale.gen" file doesn't have template like in the handbook base steps</span></a></li> <li class="toclevel-1 tocsection-25"><a href="#Use_.22--changed-use.22_instead_of_.22--newuse.22_while_updating_.40world"><span class="tocnumber">25</span> <span class="toctext">Use "--changed-use" instead of "--newuse" while updating @world</span></a></li> <li class="toclevel-1 tocsection-26"><a href="#Gnome_no_longer_requires_systemd"><span class="tocnumber">26</span> <span class="toctext">Gnome no longer requires systemd</span></a></li> <li class="toclevel-1 tocsection-27"><a href="#Mounting_of_btrfs"><span class="tocnumber">27</span> <span class="toctext">Mounting of btrfs</span></a></li> <li class="toclevel-1 tocsection-28"><a href="#Link_to_recovery_section_of_tips_and_tricks"><span class="tocnumber">28</span> <span class="toctext">Link to recovery section of tips and tricks</span></a></li> <li class="toclevel-1 tocsection-29"><a href="#Minor_spellchecking"><span class="tocnumber">29</span> <span class="toctext">Minor spellchecking</span></a></li> <li class="toclevel-1 tocsection-30"><a href="#Add_info_about_the_new_binhost"><span class="tocnumber">30</span> <span class="toctext">Add info about the new binhost</span></a></li> <li class="toclevel-1 tocsection-31"><a href="#Make_it_clearer_that_the_base_.27desktop.27_profile_does_not_install_a_default_DE"><span class="tocnumber">31</span> <span class="toctext">Make it clearer that the base 'desktop' profile does <i>not</i> install a default DE</span></a></li> </ul> </div> <h2><span class="mw-headline" id="True_multilib_needs_modification_in_make.conf">True multilib needs modification in make.conf</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=1" title="Edit section: True multilib needs modification in make.conf">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>When installing selecting the multilib profile itself wasn't sufficient. I only got true multilib support after adding the follwing in make.conf. I think it's worth mentioning it upfront so that people wouldn't have to recompile @world </p> <pre>ABI_X86="64 32" </pre> <dl><dd>No, this is not a good suggestion to make for all Gentoo users to read the Handbook. We recommend only setting enable <code>abi_x86_32</code> as-needed on a per-package basis, not globally. As explained by <a href="/wiki/User:Iamben" title="User:Iamben"> Ben Kohler (iamben) <i class="fa fa-user"></i></a>, "if you enable ABI_X86="32" globally up front, you save a little bit of user configuration time up front but you waste a lot of compile time <b>on every upgrade</b> <b>forever</b>". Also, if this was set globally as you suggest, revising those packages later can cause headaches. Kind regards, --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 19:30, 3 October 2016 (UTC)</dd></dl> <h2><span class="mw-headline" id="Chroot_on_one_line">Chroot on one line</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=2" title="Edit section: Chroot on one line">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&#160;as of Jun 6 2015.</span></div> </div> <p>It would be imo convenient to have one-liner for the mounts before the chrooting, instead of five separate commands, so that one could easily copy-paste the one command to terminal and execute it in one take </p><p>I.e., instead of (or, placed after) </p> <pre>root #mount -t proc proc /mnt/gentoo/proc root #mount --rbind /sys /mnt/gentoo/sys root #mount --make-rslave /mnt/gentoo/sys root #mount --rbind /dev /mnt/gentoo/dev root #mount --make-rslave /mnt/gentoo/dev </pre> <p>there ought to be also </p> <pre>mount -t proc proc /mnt/gentoo/proc &amp;&amp; mount --rbind /sys /mnt/gentoo/sys &amp;&amp; mount --make-rslave /mnt/gentoo/sys &amp;&amp; mount --rbind /dev /mnt/gentoo/dev &amp;&amp; mount --make-rslave /mnt/gentoo/dev</pre> <p>--<a href="/index.php?title=User:Renergy&amp;action=edit&amp;redlink=1" class="new" title="User:Renergy (page does not exist)">Renergy</a> (<a href="/index.php?title=User_talk:Renergy&amp;action=edit&amp;redlink=1" class="new" title="User talk:Renergy (page does not exist)">talk</a>) 19:39, 6 June 2015 (UTC) </p> <dl><dd>Renergy, I can see that may be easier to copy and paste a one line command such as you posted above. Part of the purpose of the Handbook is to teach people how to install Gentoo Linux, not to make the install as fast as possible, which is why we have each command on a separate line. I will think about putting a one-liner like you suggest as a secondary option for people who are in a hurry. Sincerely, --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 22:14, 21 December 2015 (UTC)</dd></dl> <h2><span class="mw-headline" id="Potential_security_problem">Potential security problem</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=3" title="Edit section: Potential security problem">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-clock-o fa-fw fa-2x"></span></span><span>This discussion is still ongoing&#160;as of Jun 28 2015.</span></div> </div> <p>Going though the handbook normally leads you through getting the minimal .iso and stage 3 tarball over https, checking hashes and verifying with gpg. All good so far. Here, it tells users to run emerge-webrsync, without any warning that it defaults to using http - enabling a MITM attack. If I understand correctly, this is for downloading and setting up portage, while running as root. By default, emerge-webrsync does not verify gpg signatures, so at this point the system must be considered fundamentally insecure. </p><p>The user stanley on irc suggested using this procedure: <a href="/wiki/Handbook:AMD64/Working/Features#Pulling_validated_Gentoo_ebuild_tree_snapshots" title="Handbook:AMD64/Working/Features">Handbook:AMD64/Working/Features#Pulling_validated_Gentoo_ebuild_tree_snapshots</a> - it should definitely be mentioned as an option at this stage, since doing it with an already insecure system at the later stage will make little difference. </p><p>Also, emerge-webrsync should default to using HTTPS. </p><p>--<a href="/index.php?title=User:OliverUv&amp;action=edit&amp;redlink=1" class="new" title="User:OliverUv (page does not exist)">OliverUv</a> (<a href="/index.php?title=User_talk:OliverUv&amp;action=edit&amp;redlink=1" class="new" title="User talk:OliverUv (page does not exist)">talk</a>) 12:26, 28 June 2015 (UTC) </p> <dl><dd>But this affects all arches, right? See <a href="/wiki/Handbook_Talk:Parts/Installation/Base" title="Handbook Talk:Parts/Installation/Base">Handbook_Talk:Parts/Installation/Base</a> --<a href="/wiki/User:Charles17" class="mw-redirect" title="User:Charles17">Charles17</a> (<a href="/wiki/User_talk:Charles17" class="mw-redirect" title="User talk:Charles17">talk</a>) 17:43, 20 January 2016 (UTC)</dd></dl> <dl><dd><dl><dd>Hm...I'll see what we can do about this upstream. It would be nice if the mirrors used HTTPS, but I'm not sure we have a good way of enforcing it. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 18:21, 18 November 2016 (UTC)</dd></dl></dd></dl> <dl><dd><dl><dd><dl><dd>So, the good news is that current Gentoo minimal install images ship with a sufficiently modern Portage (&gt;=2.3.42, with the <code>rsync-verify</code> <var>USE</var> flag set) such that for a vanilla <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">rsync</span>-based <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">emerge --sync</span> (under the recommended <span style="font-family: monospace; font-size: 95%; color: #3c763d; font-weight: 600;">/etc/portage/repos.conf/gentoo.conf</span> settings from the guide: <code>sync-rsync-verify-metamanifest = yes</code> etc.), <a rel="nofollow" class="external text" href="https://gentoo.org/support/news-items/2018-01-30-portage-rsync-verification.html">signature verification</a> with <a rel="nofollow" class="external text" href="https://gentoo.org/support/news-items/2018-07-11-portage-sync-allow-hardlinks.html">failure quarantine</a> will be carried out.</dd></dl></dd></dl></dd></dl> <dl><dd><dl><dd><dl><dd>The not so good news is that in <a href="/wiki/Handbook:AMD64/Installation/Base#Installing_an_ebuild_repository_snapshot_from_the_web" title="Handbook:AMD64/Installation/Base">this section of the handbook</a>, it is still recommended first to carry out a vanilla <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">emerge-webrsync</span>, which for some mirrors anyway will use unauthenticated HTTP (e.g. <a rel="nofollow" class="external free" href="http://trumpetti.atm.tut.fi/gentoo">http://trumpetti.atm.tut.fi/gentoo</a>), and which does <i>not</i> (by default) signature verify the downloaded tree.</dd></dl></dd></dl></dd></dl> <dl><dd><dl><dd><dl><dd>This is easy enough to work around though - just set <code>sync-webrsync-verify-signature = true</code> in the <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">[gentoo]</span> section of <span style="font-family: monospace; font-size: 95%; color: #3c763d; font-weight: 600;">/etc/portage/repos.conf/gentoo.conf</span>, temporarily set <code>sync-type = webrsync</code> in that file also (rather than <code>sync-type = rsync</code>) and then issue <code>emaint sync --auto</code>. This will do all the necessary signature updating etc and then download and verify the daily snapshot (NB - <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">emerge-webrsync</span> will complain if you try to directly invoke it with <code>sync-webrsync-verify-signature = true</code> set; you need to use <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">emaint sync</span> or <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">emerge --sync</span>). Then, once done, just flip back to using <code>sync-type = rsync</code>. This ensures all updates are validated, and doesn't mess the flow of the guide up too much. (I'm just in the process of switching over to recommending this workflow for my own EFI install guide, incidentally.) --<a href="/wiki/User:Sakaki" title="User:Sakaki">Sakaki</a> (<a href="/wiki/User_talk:Sakaki" title="User talk:Sakaki">talk</a>) 13:33, 11 October 2018 (UTC)</dd></dl></dd></dl></dd></dl> <h2><span class="mw-headline" id="Choosing_profiles">Choosing profiles</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=4" title="Edit section: Choosing profiles">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&#160;as of 2024-01-04.</span></div> </div> <p>I believe profiles should be chosen after the initial reboot at least for <b><span style="font-family: monospace; font-size: 95%; color: #54487a">amd64</span></b> and <b><span style="font-family: monospace; font-size: 95%; color: #54487a">x86</span></b>. Choosing a desktop profile, in particular, too early causes increased and unnecessary install time added to a user's experience. </p><p>I think it should be saved until the first reboot. </p><p>--<a href="/wiki/User:Grknight" title="User:Grknight">Grknight</a> (<a href="/wiki/User_talk:Grknight" title="User talk:Grknight">talk</a>) 01:46, 22 October 2015 (UTC) </p> <dl><dd>I will experiment on a virtual machine with this. My initial thoughts are that you're right. Rebuilding world after the profile selection is <i>probably</i> not a necessary part of the process. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 23:28, 1 February 2016 (UTC)</dd></dl> <dl><dd>Also, the profile selection should be updated to 17.0, maybe with a little warning regarding 17.1 which got stabilized recently.--<a href="/wiki/User:Charles17" class="mw-redirect" title="User:Charles17">Charles17</a> (<a href="/wiki/User_talk:Charles17" class="mw-redirect" title="User talk:Charles17">talk</a>) 10:28, 27 December 2017 (UTC)</dd></dl> <p>Update in progress... --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 02:44, 28 April 2018 (UTC) </p><p>Revisiting again after some time and many changes made by Gentoo's release engineer team and desktop stage files. I do not believe updating the @world set should increase install time enough to be a concern and it is an important part of the learning process. Especially when considering the introduction of the (optional) <a href="/wiki/Handbook:AMD64/Installation/Base#Optional:_Adding_a_binary_package_host" title="Handbook:AMD64/Installation/Base">binary package host</a> section which I have recently added and if a (relatively recently produced) <i>desktop</i> stage file is used there are generally only a few dozen packages updates to be performed... modern hardware can handle the compiling and other hardware (at least AMD64 and ARM64) can use the binhost. It also fits nicely into this section so I think it's safe to keep, but perhaps I'll add a little note that installations which are pressed for time can avoid it. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 08:58, 4 January 2024 (UTC) </p><p>Finished here: <a href="/wiki/Special:Diff/1272306/1272318" title="Special:Diff/1272306/1272318">Special:Diff/1272306/1272318</a>. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 10:02, 4 January 2024 (UTC) </p> <h2><span class="mw-headline" id="Add_-qt5_USE_flag">Add -qt5 USE flag</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=5" title="Edit section: Add -qt5 USE flag">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&#160;as of May 13, 2017.</span></div> </div> <p>Let me quote: "gnome gtk -kde -qt4 will compile programs with GNOME (and GTK) support, and not with KDE (and Qt) support, making the system fully tweaked for GNOME (if the architecture supports it)." </p><p>Please add -qt5 to the previous sentence as well. </p><p><a href="/wiki/User:Fturco" title="User:Fturco">Fturco</a> (<a href="/wiki/User_talk:Fturco" title="User talk:Fturco">talk</a>) 15:25, 16 April 2017 (UTC) </p> <dl><dd>Good suggestion. Consider it done. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 06:35, 14 May 2017 (UTC)</dd></dl> <h2><span id="Will_we_need_Section_of_&quot;Mounting_the_boot_partition&quot;?"></span><span class="mw-headline" id="Will_we_need_Section_of_.22Mounting_the_boot_partition.22.3F">Will we need Section of "Mounting the boot partition"?</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=6" title="Edit section: Will we need Section of &quot;Mounting the boot partition&quot;?">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&#160;as of 2024-01-04.</span></div> </div> <p>Hello, Operation of this section is already executed in section of "Preparing the disks".<br /> Haven't we mounting /dev/sda2 on /boot already? </p><p>Kind regards, --<a href="/index.php?title=User:Komainu8&amp;action=edit&amp;redlink=1" class="new" title="User:Komainu8 (page does not exist)">Komainu8</a> (<a href="/index.php?title=User_talk:Komainu8&amp;action=edit&amp;redlink=1" class="new" title="User talk:Komainu8 (page does not exist)">talk</a>) 11:04, 13 May 2017 (UTC) </p> <dl><dd>It depends on what install path you take. With this being said, the entire disk section(s) of the Handbook need a major reworking, so I would not be surprised if mounting is inconsistently noted here. I'll leave this open for now since no one is ready to work on fixing the disk section yet... --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 06:39, 14 May 2017 (UTC)</dd></dl> <dl><dd>It would be great to have such thing mentioned. --<a href="/index.php?title=User:Wowpetr&amp;action=edit&amp;redlink=1" class="new" title="User:Wowpetr (page does not exist)">Wowpetr</a> (<a href="/index.php?title=User_talk:Wowpetr&amp;action=edit&amp;redlink=1" class="new" title="User talk:Wowpetr (page does not exist)">talk</a>) 09:25, 12 July 2017 (UTC)</dd></dl> <dl><dd><dl><dd>In this <a href="/wiki/Handbook_Talk:AMD64/Installation/Base#Remove_command_to_create_.2Fboot" title="Handbook Talk:AMD64/Installation/Base">discussion</a>, undoing the creation of the <i>/boot</i> directory was accepted, but mounting is still required depending "on what install path you take". If so, wouldn't be informative to display this in the instructions? I know that if you try to re-mount a partition to the same directory is harmless (no messages are displayed on the shell after execution) but it would be even more educational to the new user to know if this is expected. If not, maybe consider delete <a href="/wiki/Handbook:AMD64/Installation/Base#Mounting_the_boot_partition" title="Handbook:AMD64/Installation/Base">this</a> subsection?--<a href="/index.php?title=User:Neyuru&amp;action=edit&amp;redlink=1" class="new" title="User:Neyuru (page does not exist)">Neyuru</a> (<a href="/index.php?title=User_talk:Neyuru&amp;action=edit&amp;redlink=1" class="new" title="User talk:Neyuru (page does not exist)">talk</a>) 20:03, 5 April 2020 (UTC)</dd></dl></dd></dl> <dl><dd>This should now be fixed with the section: <a href="/wiki/Handbook:AMD64/Installation/Base#Preparing_for_a_bootloader" title="Handbook:AMD64/Installation/Base">Handbook:AMD64/Installation/Base#Preparing_for_a_bootloader</a>. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 08:48, 4 January 2024 (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/Installation/Base&amp;action=edit&amp;section=7" 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&#160;as of July 25, 2017.</span></div> </div> <p>It is good to mention that if you interrupt the installation process at any stage later (e.g. by rebooting), you may need to mount these partitions again. --<a href="/index.php?title=User:Wowpetr&amp;action=edit&amp;redlink=1" class="new" title="User:Wowpetr (page does not exist)">Wowpetr</a> (<a href="/index.php?title=User_talk:Wowpetr&amp;action=edit&amp;redlink=1" class="new" title="User talk:Wowpetr (page does not exist)">talk</a>) 09:25, 12 July 2017 (UTC) </p> <dl><dd>Thanks for the tip. Your suggestion has been implemented! --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 23:34, 25 July 2017 (UTC)</dd></dl> <h2><span class="mw-headline" id="Entering_the_new_environment">Entering the new environment</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=8" title="Edit section: Entering the new environment">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&#160;as of July 25, 2017.</span></div> </div> <p>It is good to mention that if you interrupt the installation process at any stage inside chroot environment (e.g. by rebooting), you need to chroot again. --<a href="/index.php?title=User:Wowpetr&amp;action=edit&amp;redlink=1" class="new" title="User:Wowpetr (page does not exist)">Wowpetr</a> (<a href="/index.php?title=User_talk:Wowpetr&amp;action=edit&amp;redlink=1" class="new" title="User talk:Wowpetr (page does not exist)">talk</a>) 09:39, 12 July 2017 (UTC) </p> <dl><dd>Thanks for the tip. Your suggestion has been implemented! --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 23:34, 25 July 2017 (UTC)</dd></dl> <h2><span class="mw-headline" id="Warning_about_17.x_profiles">Warning about 17.x profiles</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=9" title="Edit section: Warning about 17.x profiles">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&#160;as of April 27, 2018.</span></div> </div> <p>Please add a big warning before the profile selection instructions, to tell users not to use 17.0 or 17.1 profiles until they have read the corresponding news items and are prepared to follow the migration instructions. </p><p><a href="/wiki/User:Iamben" title="User:Iamben">Iamben</a> (<a href="/wiki/User_talk:Iamben" title="User talk:Iamben">talk</a>) 15:34, 29 December 2017 (UTC) </p> <dl><dd>Done. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 02:39, 28 April 2018 (UTC)</dd></dl> <h2><span class="mw-headline" id="Typo_correction">Typo correction</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=10" title="Edit section: Typo correction">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&#160;as of July 25, 2019.</span></div> </div> <p>Right at the bottom of the page, the line </p> <pre>root #env-update &amp;&amp; source /etc/profile &amp;&amp; export PS1="(chroot) $PS1" </pre> <p>should read </p> <pre>root #env-update &amp;&amp; source /etc/profile &amp;&amp; export PS1="(chroot) ${PS1}" </pre> <p>to properly maintain consistency with the previous command under Entering the New Environment </p><p><a href="/index.php?title=User:Redchillipadi&amp;action=edit&amp;redlink=1" class="new" title="User:Redchillipadi (page does not exist)">Redchillipadi</a> (<a href="/index.php?title=User_talk:Redchillipadi&amp;action=edit&amp;redlink=1" class="new" title="User talk:Redchillipadi (page does not exist)">talk</a>) 02:54, 27 April 2018 (UTC) </p> <dl><dd>It looks that way to me, <a href="/index.php?title=User:Redchillipadi&amp;action=edit&amp;redlink=1" class="new" title="User:Redchillipadi (page does not exist)">Redchillipadi <i class="fa fa-user"></i></a>. What's the exact link that you're seeing just <code>$PS1</code>? --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 02:38, 28 April 2018 (UTC)</dd></dl> <p>My browser says <a href="/wiki/Handbook:AMD64/Installation/Base" title="Handbook:AMD64/Installation/Base">Handbook:AMD64/Installation/Base</a> PS1 is mentioned under Entering the new environment as <code>${PS1}</code> and at the bottom under Configure Locales as <code>$PS1</code> <a href="/index.php?title=User:Redchillipadi&amp;action=edit&amp;redlink=1" class="new" title="User:Redchillipadi (page does not exist)">Redchillipadi</a> (<a href="/index.php?title=User_talk:Redchillipadi&amp;action=edit&amp;redlink=1" class="new" title="User talk:Redchillipadi (page does not exist)">talk</a>) 02:55, 28 April 2018 (UTC) </p> <dl><dd>Fixed (<a href="/wiki/Special:Diff/816541/prev" title="Special:Diff/816541/prev">Special:Diff/816541/prev</a>)! For some reason I wasn't seeing it the first time. Thank you! --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 17:23, 25 July 2019 (UTC)</dd></dl> <h2><span class="mw-headline" id="Remind_the_user_to_fat32_format_the_esp_partition">Remind the user to fat32 format the esp partition</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=11" title="Edit section: Remind the user to fat32 format the esp partition">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&#160;as of 18 July 2022.</span></div> </div> <p>I'm a new gentoo user but I guess it's not a bad thing to have a novice's view on how this guide is structured. </p><p>The thing I noticed, following the uefi route is that it would be better to get reminded further down again to format sda2 (the esp partition) as FAT32. It isnt mentioned at the appropriate place. </p><p>The first time doing this guide, I didn't notice that, ended up installing everything and then the bootloader setup failed because I had the esp as ext2 instead of fat32 (and wasn't able to fix it). Now I'm on my second try due to that. </p> <pre>[...] root #mkfs.ext2 /dev/sda2 root #mkfs.ext4 /dev/sda4 Now create the filesystems on the newly created partitions (or logical volumes)." </pre> <p>It should be placed (or at least mentioned again) here. </p><p><a href="/index.php?title=User:AnukWolf&amp;action=edit&amp;redlink=1" class="new" title="User:AnukWolf (page does not exist)">AnukWolf</a> (<a href="/index.php?title=User_talk:AnukWolf&amp;action=edit&amp;redlink=1" class="new" title="User talk:AnukWolf (page does not exist)">talk</a>) 16:00, 13 October 2018 (UTC </p> <dl><dd>While I agree with the partitioning reminder, do yo really believe that it should be included in this section <a href="/wiki/Handbook:AMD64/Installation/Base" title="Handbook:AMD64/Installation/Base">Installing the Gentoo base system</a>? I think it is more appropriate to include an enhancement in <a href="/wiki/Handbook:AMD64/Installation/Disks" title="Handbook:AMD64/Installation/Disks">Preparing the disks</a> section. There are, to this date, 3 discussions regarding this issue there.--<a href="/index.php?title=User:Neyuru&amp;action=edit&amp;redlink=1" class="new" title="User:Neyuru (page does not exist)">Neyuru</a> (<a href="/index.php?title=User_talk:Neyuru&amp;action=edit&amp;redlink=1" class="new" title="User talk:Neyuru (page does not exist)">talk</a>) 19:24, 5 April 2020 (UTC)</dd></dl> <dl><dd><dl><dd>As a new Gentoo user too, I had no problem to use the right filesystem.</dd></dl></dd></dl> <dl><dd><dl><dd>In the <a href="/wiki/Handbook:AMD64/Installation/Disks" title="Handbook:AMD64/Installation/Disks">Preparing the disks</a> chapter of 2018&#160;:</dd> <dd>- The "Using UEFI" section explained all that&#160;; it even emphasized the necessity of a FAT variant for the ESP with a "Important" box, and the risk of not being able to boot otherwise.</dd> <dd>- The "Default partitioning scheme" section also indicated and summarized the need for FAT32 for the ESP.</dd> <dd>- The "Applying a filesystem to a partition" section showed the command to create a boot partition in ext2, that's true, but it explicitly stated this was an example (today, this same example is using FAT32, which may be the change you wanted).</dd></dl></dd></dl> <dl><dd><dl><dd>So, the information is already mentioned 2 times (3 times if you're counting the example), at the appropriate place, and with emphasis.</dd></dl></dd></dl> <dl><dd><dl><dd>Also, I agree with <a href="/index.php?title=User:Neyuru&amp;action=edit&amp;redlink=1" class="new" title="User:Neyuru (page does not exist)">Neyuru <i class="fa fa-user"></i></a>&#160;: there is no use in reminding these things after the <a href="/wiki/Handbook:AMD64/Installation/Disks" title="Handbook:AMD64/Installation/Disks">Preparing the disks</a> chapter, as the user is supposed to have applied the relevant filesystems to the partitions after that.</dd></dl></dd></dl> <dl><dd><dl><dd>--<a href="/wiki/User:Blacki" title="User:Blacki">Blacki</a> (<a href="/wiki/User_talk:Blacki" title="User talk:Blacki">talk</a>) 07:39, 18 July 2022 (UTC)</dd></dl></dd></dl> <h2><span class="mw-headline" id="Add_instructions_for_bind_mounting_udev">Add instructions for bind mounting udev</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=12" title="Edit section: Add instructions for bind mounting udev">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>os-prober needs <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">/run/udev</span> to function properly and will hang indefinitely if it's not bind mounted from outside. Consider adding a line for bind mounting it from outside the chroot, or at least a small blurb under the mounting to say that other things might need to be mounted. See <a href="/wiki/GRUB#os-prober_and_UEFI_in_chroot" title="GRUB">this section of the GRUB wiki page</a> for details. <small>—&#160;The preceding <a href="/wiki/Help:Signatures" title="Help:Signatures">unsigned</a> comment was added by <a href="/index.php?title=User:Sielicki&amp;action=edit&amp;redlink=1" class="new" title="User:Sielicki (page does not exist)">Sielicki</a> (<a href="/index.php?title=User_talk:Sielicki&amp;action=edit&amp;redlink=1" class="new" title="User talk:Sielicki (page does not exist)">talk</a> • <a href="/wiki/Special:Contributions/Sielicki" title="Special:Contributions/Sielicki">contribs</a>) 12:21, December 29, 2018‎</small> </p> <dl><dd>Thank you for the feedback, <a href="/index.php?title=User:Sielicki&amp;action=edit&amp;redlink=1" class="new" title="User:Sielicki (page does not exist)">Sielicki <i class="fa fa-user"></i></a>. I would like to test on a current LiveCD suggested the change before implementing. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 18:24, 25 July 2019 (UTC)</dd></dl> <dl><dd><dl><dd>Uncertain if it was added at the time of your comment here, however the virtual filesystem mount instructions do say to bind mount the <span style="font-family: monospace; font-size: 95%; color: #3c763d; font-weight: 600;">/run</span> directory, which would include the <span style="font-family: monospace; font-size: 95%; color: #3c763d; font-weight: 600;">udev</span> subdirectory. See <a href="/wiki/Handbook:AMD64/Installation/Base#Mounting_the_necessary_filesystems" title="Handbook:AMD64/Installation/Base">Handbook:AMD64/Installation/Base#Mounting_the_necessary_filesystems</a>. This discussion can be closed. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 13:21, 27 November 2022 (UTC)</dd></dl></dd></dl> <h2><span id="Remove_command_to_create_/boot"></span><span class="mw-headline" id="Remove_command_to_create_.2Fboot">Remove command to create /boot</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=13" title="Edit section: Remove command to create /boot">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&#160;as of July 25, 2019.</span></div> </div> <p>The /boot directory is already present in the stage3 tarball, so `mkdir /boot' can be removed. Also the paragraph just above needs to be adjusted slightly. </p><p>--<a href="/wiki/User:Rafo" title="User:Rafo">Rafo</a> (<a href="/index.php?title=User_talk:Rafo&amp;action=edit&amp;redlink=1" class="new" title="User talk:Rafo (page does not exist)">talk</a>) 19:02, 1 January 2019 (UTC) </p> <dl><dd>Good point. Suggested changes implemented (<a href="/wiki/Special:Diff/816547/prev" title="Special:Diff/816547/prev">Special:Diff/816547/prev</a>). Thank you, <a href="/wiki/User:Rafo" title="User:Rafo">Rafo <i class="fa fa-user"></i></a>! --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 17:53, 25 July 2019 (UTC)</dd></dl> <h2><span class="mw-headline" id="Minor_English_grammar_correction">Minor English grammar correction</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=14" title="Edit section: Minor English grammar correction">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&#160;as of July 25, 2019.</span></div> </div> <p>Where it says, "updates can be delayed after the Gentoo installation has finished," I think it should say "delayed <b>until</b> after." I would change it myself, but I don't have such permissions. --<a href="/index.php?title=User:Dhirsbrunner&amp;action=edit&amp;redlink=1" class="new" title="User:Dhirsbrunner (page does not exist)">Dhirsbrunner</a> (<a href="/index.php?title=User_talk:Dhirsbrunner&amp;action=edit&amp;redlink=1" class="new" title="User talk:Dhirsbrunner (page does not exist)">talk</a>) 03:58, 24 July 2019 (UTC) </p> <dl><dd>You got it. I have made the suggested change (see <a href="/wiki/Special:Diff/816511/prev" title="Special:Diff/816511/prev">Special:Diff/816511/prev</a>). Thank you for the input! --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 17:06, 25 July 2019 (UTC)</dd></dl> <h2><span id="Unclear_instructions_in_section_&#39;Configuring_Portage&#39;"></span><span class="mw-headline" id="Unclear_instructions_in_section_.27Configuring_Portage.27">Unclear instructions in section 'Configuring Portage'</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=15" title="Edit section: Unclear instructions in section &#039;Configuring Portage&#039;">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&#160;as of 2024-01-04.</span></div> </div> <p>In the first subsection 'Installing an ebuild repository snapshot from the web', we tell users that they can skip this subsection if they have no firewalls and a fast network. </p><p>But in the second subsection 'Optional: Updating the Gentoo ebuild repository', we don't tell those users that they must run 'emerge --sync', because they skipped 'emerge-webrsync'. Instead, we tell them that 'emerge --sync' is optional. So they might skip this subsection as well and won't have a Gentoo ebuild repository. </p><p>--<a href="/index.php?title=User:Mike155&amp;action=edit&amp;redlink=1" class="new" title="User:Mike155 (page does not exist)">Mike155</a> (<a href="/index.php?title=User_talk:Mike155&amp;action=edit&amp;redlink=1" class="new" title="User talk:Mike155 (page does not exist)">talk</a>) 03:22, 5 November 2019 (UTC) </p> <dl><dd><dl><dd>Yes. The <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">emerge --sync</span> should be the normal and not optional. Recommending <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">emerge-webrsync</span> without the <a href="/wiki/Project:Portage/Repository_Verification#Security_comparison" class="mw-redirect" title="Project:Portage/Repository Verification">required manual setup</a> as described in <a href="/wiki/Handbook:AMD64/Working/Features#Validated_Gentoo_repository_snapshots" title="Handbook:AMD64/Working/Features">Handbook:AMD64/Working/Features#Validated_Gentoo_repository_snapshots</a> is a bad idea. Better drop it completely or move it to a <code>Tip: In case of limited bandwidth ...</code>.--<a href="/wiki/User:Charles17" class="mw-redirect" title="User:Charles17">Charles17</a> (<a href="/wiki/User_talk:Charles17" class="mw-redirect" title="User talk:Charles17">talk</a>) 08:57, 5 November 2019 (UTC)</dd></dl></dd></dl> <dl><dd><dl><dd>Can we make this more clear somehow? We just had this same situation play out on IRC. --<a href="/wiki/User:Sam" title="User:Sam">Sam</a> (<a href="/wiki/User_talk:Sam" title="User talk:Sam">talk</a>) 17:57, 15 March 2020 (UTC)</dd></dl></dd></dl> <dl><dd><dl><dd><dl><dd>Same topic <a href="/wiki/Handbook_Talk:Parts/Installation/Base#Use_validated_snapshots" title="Handbook Talk:Parts/Installation/Base">here</a> and <a href="/wiki/Handbook_Talk:Parts/Installation/Base#.28non-validated.29_emerge-webrsync" title="Handbook Talk:Parts/Installation/Base">there</a> (talk page for »Parts«)--<a href="/wiki/User:Charles17" class="mw-redirect" title="User:Charles17">Charles17</a> (<a href="/wiki/User_talk:Charles17" class="mw-redirect" title="User talk:Charles17">talk</a>) 08:08, 16 March 2020 (UTC)</dd></dl></dd></dl></dd></dl> <dl><dd><dl><dd>With Portage feature enhancements and the flow of the handbook at this point, I believe this concern is no longer an issue. <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">emerge-webrsync</span> performs signature check; <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">emerge --sync</span> is entirely optional. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 08:43, 4 January 2024 (UTC)</dd></dl></dd></dl> <h2><span id="Incomprehensible_sentence:_&#39;..._as_carefully_chosen_USE_flag_defaults_may_be_configured_in_some_ebuilds_...&#39;"></span><span class="mw-headline" id="Incomprehensible_sentence:_.27..._as_carefully_chosen_USE_flag_defaults_may_be_configured_in_some_ebuilds_....27">Incomprehensible sentence: '... as carefully chosen USE flag defaults may be configured in some ebuilds ...'</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=16" title="Edit section: Incomprehensible sentence: &#039;... as carefully chosen USE flag defaults may be configured in some ebuilds ...&#039;">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&#160;as of 2019-11-05.</span></div> </div> <p>Do we configure USE flag defaults in ebuilds? </p><p>--<a href="/index.php?title=User:Mike155&amp;action=edit&amp;redlink=1" class="new" title="User:Mike155 (page does not exist)">Mike155</a> (<a href="/index.php?title=User_talk:Mike155&amp;action=edit&amp;redlink=1" class="new" title="User talk:Mike155 (page does not exist)">talk</a>) 18:36, 5 November 2019 (UTC) </p> <dl><dd>You are right, it is poorly worded. I have <a href="/wiki/Special:Diff/827128/835781" title="Special:Diff/827128/835781">made it more clear</a>. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 00:21, 6 November 2019 (UTC)</dd></dl> <h2><span id="Incomprehensible_sentence:_&#39;..._without_prompting_the_user_for_the_licenses_previously_accepted.&#39;"></span><span class="mw-headline" id="Incomprehensible_sentence:_.27..._without_prompting_the_user_for_the_licenses_previously_accepted..27">Incomprehensible sentence: '... without prompting the user for the licenses previously accepted.'</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=17" title="Edit section: Incomprehensible sentence: &#039;... without prompting the user for the licenses previously accepted.&#039;">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&#160;as of 2024-01-04.</span></div> </div> <p>The sentence </p><p>'Portage uses the ACCEPT_LICENSE variable to determine which packages to allow without prompting the user for the licenses previously accepted.' </p><p>doesn't seem to be right. Maybe something like: 'Portage uses the ACCEPT_LICENSE variable to determine which packages are allowed to be installed.' </p><p>--<a href="/index.php?title=User:Mike155&amp;action=edit&amp;redlink=1" class="new" title="User:Mike155 (page does not exist)">Mike155</a> (<a href="/index.php?title=User_talk:Mike155&amp;action=edit&amp;redlink=1" class="new" title="User talk:Mike155 (page does not exist)">talk</a>) 18:36, 5 November 2019 (UTC) </p> <dl><dd>This section has undergone a major reorg and rework. This discussion is stale. See <a href="/wiki/Special:Diff/1272302/1272304" title="Special:Diff/1272302/1272304">Special:Diff/1272302/1272304</a>. --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 08:36, 4 January 2024 (UTC)</dd></dl> <h2><span class="mw-headline" id="Confusion_about_per-package_exceptions_for_ACCEPT_LICENSE">Confusion about per-package exceptions for ACCEPT_LICENSE</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=18" title="Edit section: Confusion about per-package exceptions for ACCEPT LICENSE">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&#160;as of 2022-11-27.</span></div> </div> <p>One of the first sentences in paragraph 'Optional: Configuring the ACCEPT_LICENSE variable' is: 'Exceptions can be made per-package in /etc/portage/package.license as well.' </p><p>The last example of the section shows how to define exceptions in /etc/portage/package.license/kernel. </p><p>Why is it etc/portage/package.license in one case and /etc/portage/package.license/kernel in the other? I doubt that new users will understand this. </p><p>--<a href="/index.php?title=User:Mike155&amp;action=edit&amp;redlink=1" class="new" title="User:Mike155 (page does not exist)">Mike155</a> (<a href="/index.php?title=User_talk:Mike155&amp;action=edit&amp;redlink=1" class="new" title="User talk:Mike155 (page does not exist)">talk</a>) 21:24, 5 November 2019 (UTC) </p> <dl><dd>This has been clarified in the following diff: <a href="/wiki/Special:Diff/1167615/1169737" title="Special:Diff/1167615/1169737">Special:Diff/1167615/1169737</a>.</dd></dl> <h2><span id="Section_&#39;Configure_locales&#39;:_missing_reference_to_/usr/share/i18n/SUPPORTED"></span><span class="mw-headline" id="Section_.27Configure_locales.27:_missing_reference_to_.2Fusr.2Fshare.2Fi18n.2FSUPPORTED">Section 'Configure locales': missing reference to /usr/share/i18n/SUPPORTED</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=19" title="Edit section: Section &#039;Configure locales&#039;: missing reference to /usr/share/i18n/SUPPORTED">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&#160;as of 2020-04-06.</span></div> </div> <p>The section tells users that they can/should configure locales in /etc/locale.gen. </p><p>The section should also tell users that only locales shown in /usr/share/i18n/SUPPORTED are allowed and that they must pay attention to small and capital letters. </p><p>Maybe we can add a box like the one below (I added such a box in the German translation): </p> <div class="alert alert-success gw-box" style="padding-top: 8px; padding-bottom: 8px;"><strong><i class="fa fa-check-circle"></i> Tip</strong><br />A list of supported values is given in file <span style="font-family: monospace; font-size: 95%; color: #3c763d; font-weight: 600;">/usr/share/i18n/SUPPORTED</span>. Please pay attention to small and capital letters and do not use values that are not shown in this file.</div> <p>--<a href="/index.php?title=User:Mike155&amp;action=edit&amp;redlink=1" class="new" title="User:Mike155 (page does not exist)">Mike155</a> (<a href="/index.php?title=User_talk:Mike155&amp;action=edit&amp;redlink=1" class="new" title="User talk:Mike155 (page does not exist)">talk</a>) 22:39, 5 November 2019 (UTC) </p><p>Hello <a href="/index.php?title=User:Mike155&amp;action=edit&amp;redlink=1" class="new" title="User:Mike155 (page does not exist)">Mike155 <i class="fa fa-user"></i></a>, this is a welcome enhancement. Thank you for following the recommended format for submitting improvements. I have made the <a href="/wiki/Special:Diff/862922/862937" title="Special:Diff/862922/862937">change here</a>. Thank you again! Kind regards, --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 08:06, 6 April 2020 (UTC) </p> <h2><span id="What_is_an_&#39;rsync_tree&#39;?"></span><span class="mw-headline" id="What_is_an_.27rsync_tree.27.3F">What is an 'rsync tree'?</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=20" title="Edit section: What is an &#039;rsync tree&#039;?">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&#160;as of 2020-04-06.</span></div> </div> <p>'News items were created to provide a communication medium to push critical messages to users via the rsync tree.' </p><p>What is an 'rsync tree'? Maybe 'Gentoo ebuild tree'? </p><p>--<a href="/index.php?title=User:Mike155&amp;action=edit&amp;redlink=1" class="new" title="User:Mike155 (page does not exist)">Mike155</a> (<a href="/index.php?title=User_talk:Mike155&amp;action=edit&amp;redlink=1" class="new" title="User talk:Mike155 (page does not exist)">talk</a>) 22:27, 6 November 2019 (UTC) </p> <dl><dd>This terminology has been <a href="/wiki/Special:Diff/835997/862907" title="Special:Diff/835997/862907">removed here</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>) 07:24, 6 April 2020 (UTC)</dd></dl> <h2><span class="mw-headline" id="Add_warning_about_arch-chroot">Add warning about arch-chroot</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=21" title="Edit section: Add warning about arch-chroot">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&#160;as of 2020-04-06.</span></div> </div> <p>Some users in #gentoo seeking support run into issues with 'bad file descriptor' after using <code>arch-chroot</code>. We should warn about this and recommend they stick to the given commands. </p><p>--<a href="/wiki/User:Sam" title="User:Sam">Sam</a> (<a href="/wiki/User_talk:Sam" title="User talk:Sam">talk</a>) 02:47, 30 March 2020 (UTC) </p> <dl><dd>Thank you for the comment however, we cannot provide warnings for all non-recommended software. If someone is having problems using software that is Arch specific (and not available at this time in Gentoo), then they can work that out on the Arch wiki in an Arch bug tracker. We provide instructions to use our <a href="/wiki/Handbook:AMD64/Installation/Media#Gentoo_Linux_installation_media" title="Handbook:AMD64/Installation/Media">official installation media</a> and direction on <a href="/wiki/Handbook:AMD64/Installation/Base#Chrooting" title="Handbook:AMD64/Installation/Base">properly chrooting</a>. Kind regards, --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 07:35, 6 April 2020 (UTC)</dd></dl> <h2><span id="Missing_locale_options_for_America/Monterrey"></span><span class="mw-headline" id="Missing_locale_options_for_America.2FMonterrey">Missing locale options for America/Monterrey</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=22" title="Edit section: Missing locale options for America/Monterrey">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&#160;as of 2020-04-06.</span></div> </div> <p>Maybe this is a bug of the package and not to be discussed here but, just to inform my findings. I selected the timezone "America/Monterrey" and when configuring the locale with "<i>nano -w /etc/locale.gen</i>" I only found the option: "<i>es_MX ISO-8859-1</i>" in the file, so I selected it (no other option was present for my language). This is dangerous, as the wiki explains: "<b>We strongly suggest to use at least one UTF-8 locale because some applications may require it.</b>". I found out the hard way too: I had several compile time problems when emerging GNOME, which where gone if <b>adding</b> the line "<i>es_MX.UTF-8 UTF-8</i>" to the "<i>/etc/locale.gen</i>" file. Although this option was not present as an option, I can testify that adding it removed the aforementioned compile errors. Can someone help me file this bug?--<a href="/index.php?title=User:Neyuru&amp;action=edit&amp;redlink=1" class="new" title="User:Neyuru (page does not exist)">Neyuru</a> (<a href="/index.php?title=User_talk:Neyuru&amp;action=edit&amp;redlink=1" class="new" title="User talk:Neyuru (page does not exist)">talk</a>) 03:22, 6 April 2020 (UTC) </p> <dl><dd>Hello. Yes, this is not an issue specific to our installation instructions. If you are confident that you have done everything correctly in your installation and you still believe this is an issue with a package, then you'll probably want to file a bug with GNOME's upstream (NOT Gentoo's Bugzilla). If you otherwise have something you believe is necessary to add to these installation instructions, then please follow our <a href="/wiki/Handbook:Main_Page#How_do_I_improve_the_Handbook.3F" title="Handbook:Main Page">recommended format for submitting improvements</a>. Kind regards, --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 07:39, 6 April 2020 (UTC)</dd></dl> <p>Hello and thank you for the rapid response. Yes, I agree there is nothing wrong in the instructions, but I wonder, is the main problem in the omission of the correct encoding options available in "America/Monterrey"? or in GNOME not supporting some encodings? I tend to gravitate to the first option. It is strange that by specifying this locale only *one* of the options belong to the official language spoken there, and it is not even in UTF-8. This is a list of the options available: {#en_US ISO-8859-1, #en_US.UTF-8 UTF-8, #ja_JP.EUC-JP EUC-JP, #ja_JP.UTF-8 UTF-8, #ja_JP EUC-JP, #en_HK ISO-8859-1, #en_PH ISO-8859-1, #de_DE ISO-8859-1, #de_DE@euro ISO-8859-15, <b>#es_MX ISO-8859-1</b>, #fa_IR UTF-8, #fr_FR ISO-8859-1, #fr_FR@euro ISO-8859-15, #it_IT ISO-8859-1}. I sincerely apologize as this conversation does not belong here but, I wanted to share my experience, if someone could find that useful. --<a href="/index.php?title=User:Neyuru&amp;action=edit&amp;redlink=1" class="new" title="User:Neyuru (page does not exist)">Neyuru</a> (<a href="/index.php?title=User_talk:Neyuru&amp;action=edit&amp;redlink=1" class="new" title="User talk:Neyuru (page does not exist)">talk</a>) 16:50, 7 April 2020 (UTC) </p> <dl><dd>Search for <b>/usr/share/i18n/SUPPORTED</b> (has been added lately) in the article. --<a href="/wiki/User:Charles17" class="mw-redirect" title="User:Charles17">Charles17</a> (<a href="/wiki/User_talk:Charles17" class="mw-redirect" title="User talk:Charles17">talk</a>) 17:57, 7 April 2020 (UTC)</dd></dl> <p><br /> </p> <h2><span class="mw-headline" id="Move_Selecting_Mirrors_section_after_the_chroot_entry">Move Selecting Mirrors section after the chroot entry</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=23" title="Edit section: Move Selecting Mirrors section after the chroot entry">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-clock-o fa-fw fa-2x"></span></span><span>This discussion is still ongoing.</span></div> </div> <p>If a user is not using the Gentoo installation media (and in #gentoo, we often note that it's not necessary to use Gentoo's media), they may not have access to the <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">mirrorselect</span> tool until they enter the chroot. </p><p>Perhaps it should be moved after the chroot section. </p><p>--<a href="/wiki/User:Sam" title="User:Sam">Sam</a> (<a href="/wiki/User_talk:Sam" title="User talk:Sam">talk</a>) 01:51, 24 April 2020 (UTC) </p> <dl><dd>Finally getting around to make this change. Apologies it took so many years to implement! See <a href="/wiki/Special:Diff/1272298/1272302" title="Special:Diff/1272298/1272302">Special:Diff/1272298/1272302</a>. Thanks, <a href="/wiki/User:Sam" title="User:Sam"> Sam James (sam) <i class="fa fa-user"></i></a>! <small>—&#160;The preceding <a href="/wiki/Help:Signatures" title="Help:Signatures">unsigned</a> comment was added by <a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a> • <a href="/wiki/Special:Contributions/Maffblaster" title="Special:Contributions/Maffblaster">contribs</a>) 2024-01-04T08:10:45‎</small> <dl><dd>Mirrorselect is not part of all (any?) stage3 tarballs, so moving the "mirrorselect" section below the chroot does not work in its current state as I experienced. One has to either select the mirrors before chrooting, select them manually or install app-portage/mirrorselect in the chroot (which has to be done after syncing, when already selected mirrors would be preferred (i guess)). Also the green tip is obsolete. I'd suggest moving it before the chroot while preserving the tip. Maybe an edit to <a rel="nofollow" class="external free" href="https://wiki.gentoo.org/wiki/Installation_alternatives#Installation_from_non-Gentoo_live_environments">https://wiki.gentoo.org/wiki/Installation_alternatives#Installation_from_non-Gentoo_live_environments</a>? --<a href="/index.php?title=User:Schnecki&amp;action=edit&amp;redlink=1" class="new" title="User:Schnecki (page does not exist)">Schnecki</a> (<a href="/index.php?title=User_talk:Schnecki&amp;action=edit&amp;redlink=1" class="new" title="User talk:Schnecki (page does not exist)">talk</a>) 16:14, 20 January 2024 (UTC)</dd></dl></dd></dl> <h2><span id="The_&quot;locale.gen&quot;_file_doesn&#39;t_have_template_like_in_the_handbook_base_steps"></span><span class="mw-headline" id="The_.22locale.gen.22_file_doesn.27t_have_template_like_in_the_handbook_base_steps">The "locale.gen" file doesn't have template like in the handbook base steps</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=24" title="Edit section: The &quot;locale.gen&quot; file doesn&#039;t have template like in the handbook base steps">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-clock-o fa-fw fa-2x"></span></span><span>This discussion is still ongoing.</span></div> </div> <p>Hi there. During installation of the fresh gentoo, I found that "locale.gen" file from the stage3-amd64-20200607T214504Z doesn't have template like in the handbook steps. </p><p>I think that it was good idea, if user can uncomment a language that he needs in the locale.gen file instead of to looking for this language param in the man page of locale! </p><p>What do you think about it? </p><p>Thanks in advance! </p><p>--<a href="/index.php?title=User:T0ha&amp;action=edit&amp;redlink=1" class="new" title="User:T0ha (page does not exist)">t0ha</a> (<a href="/index.php?title=User_talk:T0ha&amp;action=edit&amp;redlink=1" class="new" title="User talk:T0ha (page does not exist)">talk</a>) 21:15, 12 June 2020 (UTC) </p><p><br /> </p> <h2><span id="Use_&quot;--changed-use&quot;_instead_of_&quot;--newuse&quot;_while_updating_@world"></span><span class="mw-headline" id="Use_.22--changed-use.22_instead_of_.22--newuse.22_while_updating_.40world">Use "--changed-use" instead of "--newuse" while updating @world</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=25" title="Edit section: Use &quot;--changed-use&quot; instead of &quot;--newuse&quot; while updating @world">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-clock-o fa-fw fa-2x"></span></span><span>This discussion is still ongoing.</span></div> </div> <p>"--changed-use" is better for daily Gentoo user. "--newuse" leads to unnecessary rebuild of packages which didn't really change since last build. </p><p>Recently, the cleanup of ABI_RISCV and related use flags caused rebuild of hundreds of packages, due to the widely use of "--newuse". </p><p>Many Gentoo users don't realize the existence of "--changed-use". They just follow the Handbook and keep using "--newuse". </p><p>I heard that "--newuse" was put here to remind base system team not to forget revbmp. But since this Handbook is mostly used by new users, maybe we can add a note about the difference between "--changed-use" and "--newuse" at least. And let the user choose which one they want to use. </p><p><a href="/index.php?title=User:Imrebuild&amp;action=edit&amp;redlink=1" class="new" title="User:Imrebuild (page does not exist)">Imrebuild</a> (<a href="/index.php?title=User_talk:Imrebuild&amp;action=edit&amp;redlink=1" class="new" title="User talk:Imrebuild (page does not exist)">talk</a>) 08:54, 17 October 2020 (UTC) </p> <h2><span class="mw-headline" id="Gnome_no_longer_requires_systemd">Gnome no longer requires systemd</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=26" title="Edit section: Gnome no longer requires systemd">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 are gnome profiles without systemd that use elogind instead. Should the sentence about using &gt;= gnome 3.8 be removed? </p><p><a href="/index.php?title=User:Trainz-are-kul&amp;action=edit&amp;redlink=1" class="new" title="User:Trainz-are-kul (page does not exist)">Trainz-are-kul</a> (<a href="/index.php?title=User_talk:Trainz-are-kul&amp;action=edit&amp;redlink=1" class="new" title="User talk:Trainz-are-kul (page does not exist)">talk</a>) 20:17, 21 November 2020 (UTC) </p> <dl><dd>Done --<a href="/wiki/User:Grknight" title="User:Grknight">Grknight</a> (<a href="/wiki/User_talk:Grknight" title="User talk:Grknight">talk</a>) 13:15, 22 November 2020 (UTC)</dd></dl> <h2><span class="mw-headline" id="Mounting_of_btrfs">Mounting of btrfs</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=27" title="Edit section: Mounting of btrfs">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&#160;as of 2024-01-03.</span></div> </div> <p>I often failed with the handbook when it later comes to </p> <pre>grub-mkconfig -o /boot/grub/grub.cfg /usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?). </pre> <p>...because there is no / in the 'mount' list. I usually do a mount -a inside the chroot in order to mount all the btrfs subvolumes configured in the fstab there. But / wasn't mounted like that. The simple workaround is and please mention that in the handbook: mount / After that / is mounted again from the internal fstab and grub-mkconfig works. </p><p>--<a href="/index.php?title=User:Massimo_B.&amp;action=edit&amp;redlink=1" class="new" title="User:Massimo B. (page does not exist)">Massimo B.</a> (<a href="/index.php?title=User_talk:Massimo_B.&amp;action=edit&amp;redlink=1" class="new" title="User talk:Massimo B. (page does not exist)">talk</a>) 11:55, 15 December 2021 (UTC) </p> <dl><dd>Hello, <a href="/index.php?title=User:Massimo_B.&amp;action=edit&amp;redlink=1" class="new" title="User:Massimo B. (page does not exist)">Massimo B. <i class="fa fa-user"></i></a>, did you put your btrfs rootfs in a separate, non-default btrfs subvolume? Either that, or I'm wondering if you just didn't <code>--rbind</code> <span style="font-family: monospace; font-size: 95%; color: #3c763d; font-weight: 600;">/dev</span> into the chroot... what are the steps for someone to reproduce? If the Handbook is missing a step we'll try to change it, but creating subvolumes is outside Handbook scope... and recursively mounting /dev is already in the Handbook. Thank you, --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 23:13, 20 December 2021 (UTC)</dd></dl> <dl><dd>Hi, I have the rootfs on a non-default btrfs subvolume, yes. You mean setting it as default would solve the issue? However grub-mkconfig just parses 'mount' for / and doesn't find it. This is my fstab which I just apply by mount -a &amp;&amp; mount / after entering the chroot, mount -a alone does not seem to (re)mount /:</dd></dl> <pre>&#160;grep btrfs /etc/fstab LABEL=gentoo / btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes/root 0 1 LABEL=gentoo /mnt/btrfs-top-lvl btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=/ 0 1 #LABEL=gentoo /mnt/snapshots btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=snapshots 0 1 LABEL=gentoo /home btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes/home 0 1 LABEL=gentoo /mnt/data btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes/data 0 1 LABEL=gentoo /tmp btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/tmp 0 1 LABEL=gentoo /usr/portage btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/usr.portage 0 1 LABEL=gentoo /usr/src btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/usr.src 0 1 LABEL=gentoo /var/cache btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/var.cache 0 1 LABEL=gentoo /var/db/repos btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/var.db.repos 0 1 LABEL=gentoo /var/lib/layman btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/var.lib.layman 0 1 LABEL=gentoo /var/tmp btrfs defaults,compress-force=zstd:3,space_cache=v2,subvol=volumes.root.nosnap/var.tmp 0 1 </pre> <p>--<a href="/index.php?title=User:Massimo_B.&amp;action=edit&amp;redlink=1" class="new" title="User:Massimo B. (page does not exist)">Massimo B.</a> (<a href="/index.php?title=User_talk:Massimo_B.&amp;action=edit&amp;redlink=1" class="new" title="User talk:Massimo B. (page does not exist)">talk</a>) 10:52, 22 December 2021 (UTC) </p> <dl><dd>Unfortunately I am uncertain what is causing the issue. The handbook doesn't go into detail about btrfs sub-volumes and I don't plan on adding that level of detail in the future. If you figure out the cause of the issue please return here, re-open the discussion so that we notice it, and share the solution. Perhaps a small note could be added specific to btrfs installs which put rootfs on a non-default sub-volume... You could try asking on the mailing list or <span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="ircs://irc.libera.chat/#gentoo">#gentoo</a></span> (<span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="https://web.libera.chat/#gentoo">webchat</a></span>)? Thanks! --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 07:01, 4 January 2024 (UTC)</dd></dl> <h2><span class="mw-headline" id="Link_to_recovery_section_of_tips_and_tricks">Link to recovery section of tips and tricks</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=28" title="Edit section: Link to recovery section of tips and tricks">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-clock-o fa-fw fa-2x"></span></span><span>This discussion is still ongoing.</span></div> </div> <p>There is a section on <a href="/wiki/Gentoo_installation_tips_and_tricks#Recovering_from_a_malfunctioning_installation" title="Gentoo installation tips and tricks">recovering from a malfunctioning installation</a> on the tips and tricks article. Would it not be a good idea to link to that section from the <a href="/wiki/Handbook:AMD64/Installation/Base#Entering_the_new_environment" title="Handbook:AMD64/Installation/Base">tip that mentions the possibility of recovering an installation</a>? -- <a href="/wiki/User:Ris" title="User:Ris">Ris</a> (<a href="/wiki/User_talk:Ris" title="User talk:Ris">talk</a>) 10:25, 13 March 2023 (UTC) </p> <dl><dd>I want to be able to link out, but it generates a lot of maintenance when anchors within the main change...and they can change unexpectedly. I'd rather write up a new Handbook section that covers how to resume a partially complete installation instead which is inspired by the section you linked...</dd></dl> <h2><span class="mw-headline" id="Minor_spellchecking">Minor spellchecking</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=29" title="Edit section: Minor spellchecking">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&#160;as of 2024-01-03.</span></div> </div> <ul><li>In <i>Configuring USE Variables</i>: With Gentoo users can... --&gt; With Gentoo, users can...</li> <li>In <i>Ready, set go!</i>: "Then continue withInstalling [sic] the Gentoo base system." This link is unnecessarily redirecting to the next section of the same page.</li> <li>design principal --&gt; design principle</li> <li>uncertainty whether --&gt; uncertainty about whether</li> <li>Microsoft Windows based verification --&gt; Microsoft-Windows-based verification</li></ul> <p><a href="/index.php?title=User:Avidseeker&amp;action=edit&amp;redlink=1" class="new" title="User:Avidseeker (page does not exist)">Avidseeker</a> (<a href="/index.php?title=User_talk:Avidseeker&amp;action=edit&amp;redlink=1" class="new" title="User talk:Avidseeker (page does not exist)">talk</a>) 23:52, 28 May 2023 (UTC) </p> <dl><dd>In <i>Preparing for a bootloader</i>: it is necessary prepare the... --&gt; it is necessary to prepare the...--<a href="/index.php?title=User:Lknows&amp;action=edit&amp;redlink=1" class="new" title="User:Lknows (page does not exist)">Lknows</a> (<a href="/index.php?title=User_talk:Lknows&amp;action=edit&amp;redlink=1" class="new" title="User talk:Lknows (page does not exist)">talk</a>) 04:36, 26 December 2023 (UTC)</dd></dl> <dl><dd><dl><dd>Good hunting! There are probably more. At least these have been fixed now. Thank you! --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 06:55, 4 January 2024 (UTC)</dd></dl></dd></dl> <h2><span class="mw-headline" id="Add_info_about_the_new_binhost">Add info about the new binhost</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=30" title="Edit section: Add info about the new binhost">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&#160;as of 2024-01-03.</span></div> </div> <p>Recently it was <a rel="nofollow" class="external text" href="https://www.gentoo.org/news/2023/12/29/Gentoo-binary.html">announced</a> that Gentoo now has an official binary package host, perhaps there should be info added to <a href="/wiki/Handbook:AMD64/Installation/Base#Optional:_Selecting_mirrors" title="Handbook:AMD64/Installation/Base">selecting mirrors</a> telling users how to add this if they wish? </p><p>A POC can be (formatting intentionally removed): </p><p>==== {{Anchor|Binary package host}} Binary package host ==== </p><p>Adding a binary package mirror could greatly decrease the install time needed and could be useful for older hardware. The repository configuration for the "binhost" is found in the directory {{Path|/etc/portage/binhost.conf}}, much like how {{Path|{{Link|/etc/portage/repos.conf|repos.conf}}}} functions. </p><p>{{FileBox|filename=/mnt/gentoo/etc/portage/binhosts.conf/gentoobinhost.conf|title=UK mirror example|1= </p><p>[binhost] </p><p>priority = 9999 </p><p>sync-uri = https://mirror.bytemark.co.uk/gentoo/releases/amd64/binpackages/17.1/x86-64/ </p><p>}} </p><p><a href="/wiki/User:Xarvatium" title="User:Xarvatium">Xarvatium</a> (<a href="/index.php?title=User_talk:Xarvatium&amp;action=edit&amp;redlink=1" class="new" title="User talk:Xarvatium (page does not exist)">talk</a>) 21:26, 3 January 2024 (UTC)\ </p> <dl><dd>Good idea. I used your POC as inspiration and this request has been implemented. See <a href="/wiki/Special:Diff/1272283/1272285" title="Special:Diff/1272283/1272285">Special:Diff/1272283/1272285</a>. This section may need some tuning in the near future. Curious to know what happens with the system profile number (17.1) and binhost number in the <var>sync-uri</var> value do not line up... I hope there is a mechanism to notify the sysadmin in such a condition. Thanks! --<a href="/wiki/User:Maffblaster" title="User:Maffblaster">Maffblaster</a> (<a href="/wiki/User_talk:Maffblaster" title="User talk:Maffblaster">talk</a>) 06:36, 4 January 2024 (UTC)</dd></dl> <h2><span id="Make_it_clearer_that_the_base_&#39;desktop&#39;_profile_does_not_install_a_default_DE"></span><span class="mw-headline" id="Make_it_clearer_that_the_base_.27desktop.27_profile_does_not_install_a_default_DE">Make it clearer that the base 'desktop' profile does <i>not</i> install a default DE</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Handbook_Talk:AMD64/Installation/Base&amp;action=edit&amp;section=31" title="Edit section: Make it clearer that the base &#039;desktop&#039; profile does not install a default DE">edit source</a><span class="mw-editsection-bracket">]</span></span></h2> <p>In the "Choosing the right profile" section, there's currently a "Tip" box saying: </p><p>&gt; Desktop profiles are not exclusively for desktop environments. They are also suitable for minimal window managers like i3 or sway. </p><p>However, this doesn't make it clear that using a desktop profile doesn't <i>inherently</i> set up a default DE, and that the base 'desktop' profile in particular certainly doesn't do so. i've seen a couple of posts on the forums recently where people had assumed that they would get a DE installed, rather than the profile merely setting appropriate USE flags. </p><p>-- <a href="/wiki/User:Flexibeast" title="User:Flexibeast">Flexibeast</a> (<a href="/wiki/User_talk:Flexibeast" title="User talk:Flexibeast">talk</a>) 06:45, 11 January 2024 (UTC) </p> '
Unix timestamp of change (timestamp)
1705767282