Code Listing 48 shows to run 'modules-update'. This will result in an error message "couldn't write to /etc/modules.conf" (or something similar) when in a session booted from the LiveCD kernel. Reproducible: Always Steps to Reproduce: Follow the install instructions in the handbook for an AMD64 system with the gentoo-dev-2.6.3-r2 kernel. Actual Results: Code Listing 48 shows to run 'modules-update'. This will result in an error message "couldn't write to /etc/modules.conf" (or something similar) when in a session booted from the LiveCD kernel. This makes sense, but the handbook mentions nothing of this. Expected Results: Before updating the modules, the user should be made to reboot, run modules-update (and maybe other things), and reboot again. Things should then work properly. Being a new user to gentoo (but a linux user on and off since 1996), this really threw me. People on the IRC channel were confused as well, so it would be great to fix this so other new users don't get frustrated.
Could someone of the amd-team check why modules-update wouldn't allow writing to /etc/modules.conf? The only reason I can give here is that someone forgot to chroot (and even then would writing to /etc/modules.conf work as its a ramdisk, not a readonly filesystem).
I just performed a stage1 install last week and didn't experience this issue...
Can't duplicate this issue.
