The x86 install guide now only describes how to configure /etc/conf.d/{hostname,domainname} while 2005.0(the most recent stable) livecd and its stage3 still use the old baselayout. The guide needs a note either on how to upgrade to the new baselayout, or how to configure the old style as well as the new style. Reproducible: Always Steps to Reproduce: 1. Follow a 2005.0 stage3 install. 2. Get to 'Configuring your system' in the install guide. Actual Results: /etc/conf.d/{hostname,domainname} are not present as documented. Expected Results: /etc/conf.d/{hostname,domainname} should be present, or there should be a note on upgrading baselayout manually or documentation on the old style baselayout. not sure how this applies, but what the heck: Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5, glibc-2.3.4.20040808-r1, 2.6.11-gentoo-r8 i686) ================================================================= System uname: 2.6.11-gentoo-r8 i686 Unknown CPU Type Gentoo Base System version 1.6.12 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Mar 10 2005, 20:47:05)] dev-lang/python: 2.3.4-r1 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-Os -march=i586 -fomit-frame-pointer -pipe" CHOST="i386-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-Os -march=i586 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp.ussg.iu.edu/pub/linux/gentoo http://gentoo.mirrors.pair.com/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X aac acpi alsa apm avi berkdb bitmap-fonts bzip2 crypt emboss encode flac foomaticdb fortran gdbm gif gpm imlib ipv6 jpeg libg++ libwww mad mikmod minimal mmx motif mp3 mpeg nls ogg oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl spell sse ssl tcpd truetype truetype-fonts type1-fonts usb xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
http://www.gentoo.org/doc/en/handbook/2005.0/handbook-x86.xml?part=1&chap=8 Which is the 2005.0 Handbook, is correct for 2005.0
imho, this is desired behaviour... i vote WONT FIX
Yeah. The absolute latest is put under /doc/en/handbook/ but if the livecd asks people to look into the latest on the web (as it usualy does) and points them to the generic /doc/en/handbook/, then we'd have to prolly add a note on the differing baselayout versions till 2005.1 comes out?
Michael is right. Stages 1/2 pull new baselayout in. If you do a stage3 install, you need to `emerge -u baselayout`. At the moment, HB covers new baselayout, users have old one, and they are not told what to do. Would telling users to update baselayout at http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=6#doc_chap2 (link to a small section 6.e before jumping to the next chapter) break anything?
-u brings in gcc/glibc/binutils and a few more. IMO, it's not acceptable for a stage3 that is supposed to quickly deliver a working install. # emerge baselayout brings in [ebuild U ] sys-libs/readline-5.0-r2 [4.3-r5] [ebuild N ] sys-apps/sysvinit-2.86 [ebuild U ] app-shells/bash-3.0-r11 [2.05b-r9] [ebuild U ] sys-apps/baselayout-1.11.12-r4 [1.9.4-r6] Seems reasonable to me. Unsetting CFG_PROTECT and emerge baselayout would do it, I suppose. Needs to be properly tested though. I'll do it as soon as I get the chance. Not assigning to myself (a funeral has become very likely). Feel free to take this one.
rm /etc/conf.d/net CONFIG_PROTECT="-*" emerge baselayout seems to work. Following part about net config needs a few changes. I should be able to do that tomorrow, but I shall unassign if I can't make it before Wednesday.
Created attachment 62117 [details, diff] /doc/en/handbook/96715.patch Suggested patch. Please review.
Looks much better. Asking the user to upgrade baselayout is acceptable, and if they cannot upgrade, having that note there at least explains why some files are missing. Reporter Approved(tm)
Remove the <c>...</c> inside the <uri>...</uri>, but other than that it looks fine. I couldn't find a hvc line in my /etc/inittab but perhaps that's because I don't have it auto-update by dispatch-conf...
(In reply to comment #9) > Remove the <c>...</c> inside the <uri>...</uri> Done > I couldn't find a hvc line in my /etc/inittab but perhaps that's because I > don't have it auto-update by dispatch-conf... Irrelevant. You should read the note at the beginning of that section. I only added a <path> tag around /etc/inittab
