Gentoo Quick Install Guide

[mingdao]

I wrote this Quick Guide to Installing Gentoo for installing Gentoo without having to read through all the steps of the Gentoo Handbook.

It assumes either some working knowledge of Gentoo, and/or a willingness to read if things don't go as stated.

You might just be able to copy and paste it and reboot and login as the normal user you create.

Try it out and give me your thoughts.

Thanks!

[pietinger]

[...] and give me your thoughts.

I see you install a systemd machine ... that is interesting ... ... All right, joking aside, I'm actually serious.

Why is it interesting? Because I've been looking for a systemd expert for a long time for ...

First, a question: Do you have a user account on our Gentoo Wiki? If not, would you like to register there ... because ... installation instructions are best kept on our Wiki!

Now to what I've been wanting for a long time:

Perhaps you're familiar with this (outdated) article (yes, I did add the warning): https://wiki.gentoo.org/wiki/Quick_Inst ... _Checklist

Now please follow the link ... yes, it is only for an OpenRC system ... and my remark #1 has never got a response ... ... I would be very happy if I could link to an article about systemd.

[pjp]

Try it out and give me your thoughts.

When I want information quickly, I don't really want a conversational style. I want: 1. Do this; 2. Then this, etc.

For example, the first instruction about bootable media and ssh I would have something like this:

Step 0: Boot with a suitable media running sshd.

For q Quick Install, I'd presume the reader able to figure out the details for most things.

After listing the commands to be used I'd include additional details as appropriate. For the file system setup, something like this:

Step 1: Disk setup: lsblk, gdisk, mkswap, mkfs.vfat, .xfs, etc.
mkdir /mnt/gentoo/{efi,home}

I may not remember all of the commands, so listing them helps as a reminder. I know how to use them. Without mkswap, I might forget it (and have) but I know how to use it. Similarly with creating the directory structure.

Step 2: Stage installation
wget ... stage3...tar.xz
sha256sum --check stage3....tar.xz.sha256
tar xpvf stage3-*.tar.xz --xattrs-include='*.*' --numeric-owner -C /mnt/gentoo/

That's more of what I think of for a Quick guide. There was once something like that.

As an aside, there's a possible "bug" in the post. In the "sha256sum --check" line, there's an "invisible" <arch> at the end:

Code: Select all

sha256sum --check stage3-amd64-<release>-<init>.tar.xz.sha256 <arch>

In an ideal world, the Handbook would be viewable like this in "collapsed" form, expandable if needed. But I have no idea how to set that up in a maintainable web format.

[haegar87]

Try it out and give me your thoughts.

Not bad. You lost many choices but that's normal in such a short guide. Not a big fan of removing the package.* directories but that's just my personal opinion.

Just my 2 cents:
1. Why install grub instead of using systemd-boot if you already use systemd?
2. No need to install dhcpcd. Systemd brings it's own DHCP client (and only uses it). Just change your network file to:

Code: Select all

[Match]
Name=eth0
[Network]
DHCP=yes

and systemd-networkd will handle the rest (without any DHCP package).

EDIT: Fixed typo.

[GDH-gentoo]

The problem with "quick install guides" like this one is that they are basically steps for replicating the writer's preferred setup, and therefore only useful for readers who might want that same setup. I think these kind of documents have their place, but still encourage users to read the Handbook.

[mingdao]

Not bad. You lost many choices but that's normal in such a short guide. Not a big fan of removing the package.* directories but that's just my personal opinion.

If you know enough to object, you can just write a file for each package whose USE flags you change, as per the present default. No worries. :wink:

Just my 2 cents:
1. Why install grub instead of using systemd-boot if you already use systemd?

I now have versions for 3 boot managers. One for systemd-boot per your request, one for EFI stub, and the original one for GRUB.

2. No need to install dhcpcd. Systemd brings it's own DHCP client (and only uses it). Just change your network file to:

Code: Select all

[Match]
Name=eth0
[Network]
DHCP=yes

and systemd-networkd will handle the rest (without any DHCP package).

There is now a section covering the choice of DHCP.

Check them out and let me know if you have any other suggestions.

[pietinger]

mingdao,

since I also write articles that try to help new users with Gentoo (old hands know what to do), I am familiar with the problem of too much and too little. When a new Gentoo user reads our Handbook, they are initially overwhelmed. If you write a "Quick Installation Guide" and leave out many options, you kill the diversity that Gentoo offers. That's why I'm in favor of having both: those who struggle with our Handbook can then look up what can be done by default in a quick guide. To do this, however, the quick guide must only contain the simplest steps. As you know, I used the outdated quick guide in our wiki and not only updated it, but also slimmed it down.

If you add new options to your descriptions, they can be very useful, but they can also confuse new Gentoo users. Only those who are familiar with Gentoo will immediately recognize the deviations from the standard. For example, you describe how to create a Gentoo installation from another machine via SSH. Some old hands here will certainly do that, but can newbies cope with it? I am a fan of options. In an old version of our Gentoo Handbook, parted was used for partitioning. Later, it was replaced by fdisk. However, I left it in the Quick Installation Guide that I edited so that users can choose what they want to use; you use gdisk - a third option.

I have looked at this thoroughly:
https://techfix.me/files/Gentoo-Quick-I ... -stub.html

... and am just noting a few differences that caught my eye - my comments are in parentheses:

- remote installation from another machine ... (Yes, this is also described as an option in the handbook)
- ... using tmux (using tmux is quite nice, but even if I only had one terminal (instead of many KDE “Konsole”s), I still have ALT-F3 and ALT-F4 ... is it really necessary?)
- gdisk (a 3rd alternative to fdisk an parted)
- creating 4 partitions; also one for /home (a user with at least intermediate Linux knowledge should be able to understand what this means... but what about a beginner?)
- 2 GB for an ESP (is really ... too big )
- using genfstab for creating /etc/fstab instead manually editing it
- immediately using an "emerge --sync" instaed of the default emerge-webrsync (does this really work?)
- using vim instead nano (easy for all beginners )
- using package.use as file and not as directory (which is expressly not recommended by our developers)
- creating an UKI kernel instead the default (yes, this is an option in our Handbook)
- the kernel command line parms: "net.ifnames=0 panic=30 loglevel=3 modprobe.blacklist=pcspkr" could confuse new users ...
- USE="X -wayland -device-mapper" (please do never disable wayland for a desktop profile)
- */* VIDEO_CARDS: intel should be:

Code: Select all

*/* VIDEO_CARDS: -* intel

Quite frankly - please take this as constructive criticism (I have learned through my work here in the forum how and where new users can make mistakes or have trouble with the description. I also know the problem of thinking like a newbie - because we're not newbies anymore. And then I'm always surprised how a newbie manages to skip this one step, so that the effects/problems only become apparent later on.):

If you disable the "wayland" Use-flag when using a desktop profile, a new user will log in here... because they will have problems ... if not immediately, then at least in the future.

[mingdao]

mingdao,

since I also write articles that try to help new users with Gentoo (old hands know what to do), I am familiar with the problem of too much and too little. When a new Gentoo user reads our Handbook, they are initially overwhelmed. If you write a "Quick Installation Guide" and leave out many options, you kill the diversity that Gentoo offers. That's why I'm in favor of having both: those who struggle with our Handbook can then look up what can be done by default in a quick guide. To do this, however, the quick guide must only contain the simplest steps. As you know, I used the outdated quick guide in our wiki and not only updated it, but also slimmed it down.

If you add new options to your descriptions, they can be very useful, but they can also confuse new Gentoo users. Only those who are familiar with Gentoo will immediately recognize the deviations from the standard. For example, you describe how to create a Gentoo installation from another machine via SSH. Some old hands here will certainly do that, but can newbies cope with it? I am a fan of options. In an old version of our Gentoo Handbook, parted was used for partitioning. Later, it was replaced by fdisk. However, I left it in the Quick Installation Guide that I edited so that users can choose what they want to use; you use gdisk - a third option.

I have looked at this thoroughly:
https://techfix.me/files/Gentoo-Quick-I ... -stub.html

... and am just noting a few differences that caught my eye - my comments are in parentheses:

- remote installation from another machine ... (Yes, this is also described as an option in the handbook)
- ... using tmux (using tmux is quite nice, but even if I only had one terminal (instead of many KDE “Konsole”s), I still have ALT-F3 and ALT-F4 ;-) ... is it really necessary?)
- gdisk (a 3rd alternative to fdisk an parted)
- creating 4 partitions; also one for /home (a user with at least intermediate Linux knowledge should be able to understand what this means... but what about a beginner?)
- 2 GB for an ESP (is really ... too big :P )
- using genfstab for creating /etc/fstab instead manually editing it
- immediately using an "emerge --sync" instaed of the default emerge-webrsync (does this really work?)
- using vim instead nano (easy for all beginners :lol: )
- using package.use as file and not as directory (which is expressly not recommended by our developers)
- creating an UKI kernel instead the default (yes, this is an option in our Handbook)
- the kernel command line parms: "net.ifnames=0 panic=30 loglevel=3 modprobe.blacklist=pcspkr" could confuse new users ... 8O
- USE="X -wayland -device-mapper" (please do never disable wayland for a desktop profile)
- */* VIDEO_CARDS: intel should be:

Code: Select all

*/* VIDEO_CARDS: -* intel

Quite frankly - please take this as constructive criticism (I have learned through my work here in the forum how and where new users can make mistakes or have trouble with the description. I also know the problem of thinking like a newbie - because we're not newbies anymore. And then I'm always surprised how a newbie manages to skip this one step, so that the effects/problems only become apparent later on.):

If you disable the "wayland" Use-flag when using a desktop profile, a new user will log in here... because they will have problems ... if not immediately, then at least in the future. :(

I've read your post, and to me, the introductory paragraphs in my guide(s) addresses everything you wrote. With all due respect, this really makes me think you didn't read my article top-down, or maybe this was confusing to you:

The Gentoo Handbook provides detailed documentation that guides you through the installation process. For me, after having installed Gentoo numerous times, there is considerably more than needed at this point. The purpose of this "Gentoo Quick Install Guide" is to cut out all the extra detail and just provide what is required to install a working headless Gentoo system for amd64 using systemd as the init system. It does have some explanation so that you can copy and paste, changing what might be specific for you, such as disk partitioning and networking. After you finish this install and reboot, it should be fairly easy to install your desktop system of choice. Mine has been Fluxbox for over 20 years. Contact me if you want any pointers.

If you've never installed Gentoo before, this guide is not for you. My recommendation would be to use the Gentoo Handbook and select the Quick links that matches your target machines.

They all three have that same text, and they're posted on my website.

Thanks for your comments. I have things about your guide with which I disagree, so I just don't use it - and won't edit it. It is YOURS - write and publish what you want.

Last, and certainly not least, did you install using one of my guides? Because I can copy and paste, and when I issue the last command (reboot) it boots up to:

Code: Select all

gentooligan login: mingdao
Password:
Welcome to your new account!

Therefore, I have accomplished my goal.

I do agree with you that 2GB for an ESP partition is more than necessary. The Gentoo Handbook had a recommendation that was too small forever. Use what you wish. My first versions had 1G.

[pietinger]

mingdao,

I feel that you have taken my criticism too personally. It was actually intended more as a classification. A classification that could lie exactly between Handbook and Quick Install. My only real criticism is the deactivation of the “wayland” use flag (also because we have already had frequent discussions/problems about this here in the forum).

I do NOT consider the version I edited to be mine, but am grateful for any comments and improvements (these have already been made; our wiki editor @immolo has added something and a note in the article's talk page has also corrected a faux pas).

Perhaps you will understand me better if you know my goal: We already have the Handbook – the “bible” for Gentoo. Are you familiar with the ArchLinux installation guide? It is very short. And as you know as an old hand, everything has its advantages and disadvantages. This guide would not be enough for me. But for many new users, it is ideal. That's why I want Gentoo to offer BOTH. I would be happy if we had a QuickInstall for an OpenRC AND a systemd system.

If I expressed myself unclearly in my previous post, I apologize - it was not my intention.

[mingdao]

mingdao,
Are you familiar with the ArchLinux installation guide? It is very short. And as you know as an old hand, everything has its advantages and disadvantages. This guide would not be enough for me. But for many new users, it is ideal.

The Arch Installation guide is background for why I wrote my Gentoo Quick Guide Install guides the way I did. To me the Arch Installation guide is perfect, and if one uses it as designed, going top-down, and clicking the parts such as Boot loader, follow the link it opens, complete that section, then go back to the main guide, Arch is much easier to install and makes more sense (to me) than the Gentoo Handbook.

And just like the Gentoo Handbook, after the Reboot (Section 4) you should continue to Section 5 Post-installation. Most people I've seen use the Gentoo Handbook over the years get to the section "Configuring the bootloader" and reboot, but don't continue to the Finalizing section. Where the last line in "Configuring the bootloader" states "Once rebooted in the fresh Gentoo environment, it is wise to finish with Finalizing the Gentoo installation."

The Gentoo Handbook has many errors and incomplete instructions as you go along. My guides can install using copy and paste. If someone wants to change something because their goal is different than the one I stated, then they will most likely know what to do. Let me reiterate what is in all 3 of my Gentoo Quick Guide Install guides:

If you've never installed Gentoo before, this guide is not for you.

You see my status in the Gentoo forum after 14 years? n00b - take that into consideration.

[Hu]

You see my status in the Gentoo forum after 14 years? n00b - take that into consideration.

This status can mean any of several things. I've seen users who have very old registration dates, very few posts, and who directly indicate that they tried to get into Gentoo back then, gave up, and spent many years not using or thinking about Gentoo. Such people are legitimately still "new" to Gentoo when they return, and their forum status is appropriate, despite their old registration date. I have seen people who are in the situation you seem to be implying about yourself: users who are proficient with Gentoo such that they rarely need to post, because they always solve their own problems. I have seen some users who have relatively old post dates, very high post counts, and they got that way because they always seek help, but rarely give it. I have also seen users who have very high post counts that they got by routinely giving help, and rarely seeking it. If, as you imply, you are a long-time highly proficient user, I encourage you to seek that last category: be more active helping users, and your post count will naturally rise, and with it, your status will change.

[mingdao]

You see my status in the Gentoo forum after 14 years? n00b - take that into consideration.

This status can mean any of several things. I've seen users who have very old registration dates, very few posts, and who directly indicate that they tried to get into Gentoo back then, gave up, and spent many years not using or thinking about Gentoo. Such people are legitimately still "new" to Gentoo when they return, and their forum status is appropriate, despite their old registration date. I have seen people who are in the situation you seem to be implying about yourself: users who are proficient with Gentoo such that they rarely need to post, because they always solve their own problems. I have seen some users who have relatively old post dates, very high post counts, and they got that way because they always seek help, but rarely give it. I have also seen users who have very high post counts that they got by routinely giving help, and rarely seeking it. If, as you imply, you are a long-time highly proficient user, I encourage you to seek that last category: be more active helping users, and your post count will naturally rise, and with it, your status will change.

I started using Linux on a daily basis in November 2003. We lived in a foreign country where almost no one spoke English, especially not proficiently, and in 9 years living there the only Linux computers I ever saw were servers in universities, or ones where I installed Slackware.

Also during that time I used LinuxQuestions.org and became the Hardware Compatibility List Maintainer. Since 2011 when I started using Gentoo, I've spent much more time on IRC than forums.

I will start looking at the forum more. It's just that today I have to work for a living, and don't have much time for posting - just grabbing a minute here or there on IRC is about it.

I do understand about post count raising status, and the n00b comment is a joke. Since 2011 Gentoo has been my distro for headless machines, and Arch for any that needed a GUI. I have no need or desire for a desktop environment, and use Fluxbox and Xorg (no desire for Wayland, either). I'm an old guy who's old school and not likely to change, but am converting a few computers from Arch to Gentoo.

[finoderi]

- immediately using an "emerge --sync" instead of the default emerge-webrsync (does this really work?)

I installed Gentoo several times in different circumstances, tried it every time - it never works. You must use emerge-webrsync for the very first repository synchronisation.

The Arch Installation guide is background for why I wrote my Gentoo Quick Guide Install guides the way I did. To me the Arch Installation guide is perfect, and if one uses it as designed, going top-down, and clicking the parts such as Boot loader, follow the link it opens, complete that section, then go back to the main guide, Arch is much easier to install and makes more sense (to me) than the Gentoo Handbook.

That guide is far from perfect and especially the article about the boot loader. It's a hot mess and has been for at least last 5 years. Overall the Handbook certainly does much better job listing and explaining what you need to do to successfully install the system.

Most people I've seen use the Gentoo Handbook over the years get to the section "Configuring the bootloader" and reboot, but don't continue to the Finalizing section. Where the last line in "Configuring the bootloader" states "Once rebooted in the fresh Gentoo environment, it is wise to finish with Finalizing the Gentoo installation."

It's not the guide's fault.

The Gentoo Handbook has many errors and incomplete instructions as you go along.

It doesn't have many errors and instructions are incomplete by design. Although imho it has some questionable recent edits like the advice to disable root password. This is really great suggestion for any beginner! Why kdesu doesn't work on a recently installed system? Ah yes, it's because I made it more 'secure'... Now you need to chroot into your system to reset the root password. Which is certainly a trivial thing to do for anybody trying to install Gentoo for the first time.

Let me reiterate what is in all 3 of my Gentoo Quick Guide Install guides:

If you've never installed Gentoo before, this guide is not for you.

And if you have done it before, this guide doesn't add anything useful to already existing ones.

[skellr]

I now have versions for 3 boot managers. One for systemd-boot per your request, one for EFI stub, and the original one for GRUB.

On your systemd-boot page you have the use flag for efistub enabled for installkernel.

Code: Select all

sys-kernel/installkernel -dracut systemd efistub -grub -refind systemd-boot ugrd uki ukify

That can bypass using another bootloader (systemd-boot) and configure UEFI to boot an image directly? sys-kernel/installkernel is actively developed so it's behavior is in a state of flux. I do remember at one point it would default to using efistub when multiple "bootloader" options were enabled.

I don't think you need efistub for UKI use.

[pietinger]

- immediately using an "emerge --sync" instead of the default emerge-webrsync (does this really work?)

I installed Gentoo several times in different circumstances, tried it every time - it never works. You must use emerge-webrsync for the very first repository synchronisation.

Yes, this was also my last information. I only asked because it's possible that this has changed. Thank you for confirming.

[mingdao]

- immediately using an "emerge --sync" instead of the default emerge-webrsync (does this really work?)

I installed Gentoo several times in different circumstances, tried it every time - it never works. You must use emerge-webrsync for the very first repository synchronisation.

Yes, this was also my last information. I only asked because it's possible that this has changed. Thank you for confirming. :)

You're believing someone who wrote something untrue without trying it yourself. Unbelievable.

Code: Select all

gentooligan ~ # cat .bash_history
export PS1="(chroot) ${PS1}"
time emerge --sync
eselect news read
getuto
emerge --getbinpkg -atv app-editors/vim
eselect editor set vim
. /etc/profile && export PS1="(chroot) ${PS1}"
eselect editor show
date ; ln -sf /usr/share/zoneinfo/America/Chicago /etc/localtime ; date
vim /etc/locale.gen
locale-gen
eselect locale list
eselect locale set 5
env-update && source /etc/profile && export PS1="(chroot) ${PS1}"

[Banana]

I installed Gentoo several times in different circumstances, tried it every time - it never works. You must use emerge-webrsync for the very first repository synchronisation.

Yes, this was also my last information. I only asked because it's possible that this has changed. Thank you for confirming.

You're believing someone who wrote something untrue without trying it yourself. Unbelievable.

I think you could have written this in a friendlier way.

emerge --sync or emerge-webrsync will sync your local stored information about the packages. One does it with rsync and the other does it over http based on a daily tar.gz.
There a multiple reasons why one or the other will not work for you.

[NeddySeagoon]

Moved from Installing Gentoo to Documentation, Tips & Tricks.

It's one of these.
Documentation lasts longer on the wiki in the users namespace.

[pietinger]

You're believing someone who wrote something untrue without trying it yourself. Unbelievable.

Many years ago, emerge-webrsync did not exist, and it was always possible to perform an “emerge --sync” immediately. I no longer recall when and why emerge-webrsync was developed. My last new installation was 2.5 years ago, and I found that an immediate emerge-sync did not work. It was also a frequent topic here in our forum. To be honest, I was never particularly interested in it. But since I don't know the current status, I asked the question (in parentheses).

I don't think @finoderi wrote anything untrue when he said that an immediate emerge-sync was not possible with multiple installations.

I believe all the users here in the forum. I also believe you that it was possible for you. And above all, I believe our developers that there is probably a reason why you should do an emerge-webrsync.

Whether something is untrue or a mistake usually only becomes clear afterwards. In my experience, it has almost always been a mistake. And yes, to err is human. That's why I would never accuse anyone of deliberately telling untruths (unless that person convinces me otherwise).

[NeddySeagoon]

pietinger,

I haven't tried emerge --sync with an empty repo for many years.
My memory of it is that it is was very slow ... hours.
websync is much faster, hence preferred to prime your copy of the ::gentoo repo.

[zen_desu]

pietinger,

I haven't tried emerge --sync with an empty repo for many years.
My memory of it is that it is was very slow ... hours.
websync is much faster, hence preferred to prime your copy of the ::gentoo repo.

I did tests a year or two ago and found that for the first sync, webrsync was faster, and tends to not speed up much on subsequent syncs, but --sync was about half to a third as fast the first time and ~2x as fast on later syncs.

[mingdao]

I don't think you need efistub for UKI use.

You are correct, thanks for that correction. I have updated the systemd-boot guide, and bootctl-status output from the test install is below.

Let me know your thoughts, skellr.

Code: Select all

mingdao@gentooligan ~ $ bootctl status
System:
      Firmware: UEFI 2.31 (American Megatrends 4.654)
 Firmware Arch: x64
   Secure Boot: disabled
  TPM2 Support: no
  Measured UKI: no
  Boot into FW: supported

Current Boot Loader:
      Product: systemd-boot 257.10
     Features: ✓ Boot counting
               ✓ Menu timeout control
               ✓ One-shot menu timeout control
               ✓ Default entry control
               ✓ One-shot entry control
               ✓ Support for XBOOTLDR partition
               ✓ Support for passing random seed to OS
               ✓ Load drop-in drivers
               ✓ Support Type #1 sort-key field
               ✓ Support @saved pseudo-entry
               ✓ Support Type #1 devicetree field
               ✓ Enroll SecureBoot keys
               ✓ Retain SHIM protocols
               ✓ Menu can be disabled
               ✓ Multi-Profile UKIs are supported
               ✓ Boot loader set partition information
    Partition: /dev/disk/by-partuuid/a31be31d-f488-43a8-baf8-e97be55d82b3
       Loader: └─/EFI/BOOT/BOOTX64.EFI
Current Entry: gentoo-6.12.58-gentoo-dist.efi

Current Stub:
      Product: systemd-stub 257.10
     Features: ✓ Stub sets loader partition information
               ✓ Picks up credentials from boot partition
               ✓ Picks up system extension images from boot partition
               ✓ Picks up configuration extension images from boot partition
               ✓ Measures kernel+command line+sysexts
               ✓ Support for passing random seed to OS
               ✓ Pick up .cmdline from addons
               ✓ Pick up .cmdline from SMBIOS Type 11
               ✓ Pick up .dtb from addons
              ✓ Stub understands profile selector
               ✓ Stub sets stub partition information
               ✓ Stub loader set partition information
    Partition: /dev/disk/by-partuuid/a31be31d-f488-43a8-baf8-e97be55d82b3
         Stub: └─/EFI/Linux/gentoo-6.12.58-gentoo-dist.efi

Random Seed:
 System Token: set
       Exists: yes

Available Boot Loaders on ESP:
          ESP: /efi (/dev/disk/by-partuuid/a31be31d-f488-43a8-baf8-e97be55d82b3)
         File: ├─/EFI/systemd/systemd-bootx64.efi (systemd-boot 257.10)
               └─/EFI/BOOT/BOOTX64.EFI (systemd-boot 257.10)

Boot Loaders Listed in EFI Variables:
        Title: UEFI OS
           ID: 0x0007
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/a31be31d-f488-43a8-baf8-e97be55d82b3
         File: └─/EFI/BOOT/BOOTX64.EFI

Boot Loader Entries:
        $BOOT: /efi (/dev/disk/by-partuuid/a31be31d-f488-43a8-baf8-e97be55d82b3)
        token: gentoo

Default Boot Loader Entry:
         type: Boot Loader Specification Type #2 (.efi)
        title: Gentoo Linux
           id: gentoo-6.12.58-gentoo-dist.efi
       source: /efi//EFI/Linux/gentoo-6.12.58-gentoo-dist.efi (on the EFI System Partition)
     sort-key: gentoo
      version: 2.18
        linux: /efi//EFI/Linux/gentoo-6.12.58-gentoo-dist.efi
      options: net.ifnames=0 panic=30 loglevel=3 modprobe.blacklist=pcspkr

[mingdao]

Running `emerge-webrsync` completes successfully for me.

Running `emerge --sync` completes successfully for me.

Below is the time and important output of [1] running `emerge-webrsync` then `emerge --sync`, which took a total of 2m23.987s for both emerges.

Then [2] is running only `emerge --sync` on a new, clean filesystem, which took 4m12.198s. I have various other timings, but much like zen_desu mentioned, these are averages for me.

Both succeed and contain the exact same data afterwards.

The fact is that booted with the install-amd64-minimal-20251130T164554Z.iso, the command `emerge --sync` should work for you. If either, or any other command, does not complete successfully for you, then post the entire output, and we are here to help.

Code: Select all

[1] RUNNING BOTH emerge-webrsync and emerge --sync:

(chroot) livecd / # time emerge-webrsync
<snip>
Number of files: 155,300 (reg: 127,743, dir: 27,557)
Number of created files: 155,299 (reg: 127,743, dir: 27,556)
Number of deleted files: 0
Number of regular files transferred: 127,743
Total file size: 234.54M bytes
Total transferred file size: 234.54M bytes
Literal data: 234.54M bytes
Matched data: 0 bytes
File list size: 3.43M
File list generation time: 0.001 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 119.49M
Total bytes received: 2.55M

sent 119.49M bytes  received 2.55M bytes  9.76M bytes/sec
total size is 234.54M  speedup is 1.92

Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)



 * IMPORTANT: 15 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.


real    0m30.000s
user    0m20.398s
sys     0m14.921s



(chroot) livecd / # time emerge --sync
<snip>
Number of files: 155,318 (reg: 127,761, dir: 27,557)
Number of created files: 54 (reg: 54)
Number of deleted files: 36 (reg: 36)
Number of regular files transferred: 129
Total file size: 234.62M bytes
Total transferred file size: 3.22M bytes
Literal data: 3.22M bytes
Matched data: 0 bytes
File list size: 1.83M
File list generation time: 0.001 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 32.22K
Total bytes received: 6.80M

sent 32.22K bytes  received 6.80M bytes  76.35K bytes/sec
total size is 234.62M  speedup is 34.33
 * Manifest timestamp: 2025-12-06 11:48:00 UTC
 * Valid OpenPGP signature found:
 * - primary key: DCD05B71EAB94199527F44ACDB6B8C1F96D8BF6D
 * - subkey: E1D6ABB63BFCFB4BA02FDF1CEC590EEAC9189250
 * - timestamp: 2025-12-06 11:48:00 UTC
 * Verifying /var/db/repos/gentoo/.tmp-unverified-download-quarantine ...                                                                                                                [ ok ]
=== Sync completed for gentoo

 * IMPORTANT: 15 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.


Action: sync for repo: gentoo, returned code = 0



real    1m53.987s
user    0m16.501s
sys     0m8.050s

(chroot) livecd / # du -sh /
du: cannot access '/proc/4156/task/4156/fd/4': No such file or directory
du: cannot access '/proc/4156/task/4156/fdinfo/4': No such file or directory
du: cannot access '/proc/4156/fd/3': No such file or directory
du: cannot access '/proc/4156/fdinfo/3': No such file or directory
5.3G    /

[2] ONLY RUNNING emerge --sync from the beginning:

(chroot) livecd / # time emerge --sync
<snip>
Number of files: 155,318 (reg: 127,761, dir: 27,557)
Number of created files: 155,317 (reg: 127,761, dir: 27,556)
Number of deleted files: 0
Number of regular files transferred: 127,761
Total file size: 234.62M bytes
Total transferred file size: 234.62M bytes
Literal data: 234.62M bytes
Matched data: 0 bytes
File list size: 4.20M
File list generation time: 0.003 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 2.56M
Total bytes received: 119.90M

sent 2.56M bytes  received 119.90M bytes  550.42K bytes/sec
total size is 234.62M  speedup is 1.92
 * Manifest timestamp: 2025-12-06 11:48:00 UTC
 * Valid OpenPGP signature found:
 * - primary key: DCD05B71EAB94199527F44ACDB6B8C1F96D8BF6D
 * - subkey: E1D6ABB63BFCFB4BA02FDF1CEC590EEAC9189250
 * - timestamp: 2025-12-06 11:48:00 UTC
 * Verifying /var/db/repos/gentoo/.tmp-unverified-download-quarantine ...                                                                                                                [ ok ]
=== Sync completed for gentoo

Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)
  .='update pass'  *='binary update'  #='/var/db update'  @='/var/db move'
  s='/var/db SLOT move'  %='binary move'  S='binary SLOT move'
  p='update /etc/portage/package.*'
/var/db/repos/gentoo/profiles/updates/1Q-2020..........
/var/db/repos/gentoo/profiles/updates/1Q-2021.......
/var/db/repos/gentoo/profiles/updates/1Q-2023.......................
/var/db/repos/gentoo/profiles/updates/1Q-2024...............................................................................................
/var/db/repos/gentoo/profiles/updates/1Q-2025...........................
/var/db/repos/gentoo/profiles/updates/2Q-2020.........
/var/db/repos/gentoo/profiles/updates/2Q-2021.......
/var/db/repos/gentoo/profiles/updates/2Q-2022............
/var/db/repos/gentoo/profiles/updates/2Q-2023...............................
/var/db/repos/gentoo/profiles/updates/2Q-2024.............
/var/db/repos/gentoo/profiles/updates/2Q-2025......
/var/db/repos/gentoo/profiles/updates/3Q-2020..............
/var/db/repos/gentoo/profiles/updates/3Q-2021...........
/var/db/repos/gentoo/profiles/updates/3Q-2022.....................
/var/db/repos/gentoo/profiles/updates/3Q-2023...................
/var/db/repos/gentoo/profiles/updates/3Q-2024.............
/var/db/repos/gentoo/profiles/updates/3Q-2025.......
/var/db/repos/gentoo/profiles/updates/4Q-2020.......
/var/db/repos/gentoo/profiles/updates/4Q-2021.......................................................................
/var/db/repos/gentoo/profiles/updates/4Q-2022.........
/var/db/repos/gentoo/profiles/updates/4Q-2023........................................
/var/db/repos/gentoo/profiles/updates/4Q-2024...................................................................................
/var/db/repos/gentoo/profiles/updates/4Q-2025.



 * IMPORTANT: 15 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.


Action: sync for repo: gentoo, returned code = 0



real    4m12.198s
user    0m34.154s
sys     0m39.374s

(chroot) livecd / # du -sh /
du: cannot access '/proc/5102/task/5102/fd/4': No such file or directory
du: cannot access '/proc/5102/task/5102/fdinfo/4': No such file or directory
du: cannot access '/proc/5102/fd/3': No such file or directory
du: cannot access '/proc/5102/fdinfo/3': No such file or directory
5.3G    /