Guide still says that I should do 'echo tux > /etc/hostname' and 'echo homenetwork > /etc/dnsdomainname' while the rc-scripts tells me to edit the proper files in /etc/conf.d. This also applies to keymaps. The affected chapter is section 8.b (in the SPARC installation-guide at least). Thanks!
Guide still says that I should do 'echo tux > /etc/hostname' and 'echo homenetwork > /etc/dnsdomainname' while the rc-scripts tells me to edit the proper files in /etc/conf.d. This also applies to keymaps. The affected chapter is section 8.b (in the SPARC installation-guide at least). Thanks! ©harlie Reproducible: Always Steps to Reproduce: 1. Following the SPARC Gentoo Installation-guide 2. 3. Actual Results: rc-scripts at startup complaining about /etc-files that should be configured through /etc/conf.d-files. Expected Results: Installation-guide to say that configuration goes in /etc/conf.d-files :)
Is this with "sparc" or "~sparc"? I.e. is the baselayout that triggers this marked stable?
No difference, I still use http://www.gentoo.org/doc/en/handbook/handbook-sparc.xml :) Just kiddin'. I have ~sparc, baselayout is 1.11.8 and is marked unstable. Latest stable baselayout is 1.9.4-r6, but I can't really tell if the bug applies to it, I don't do stable ;p Anyway, close bug with resolution LATER (when new baselayout becomes stable)? Sorry for buggin' you. Is there any other handbook for doing ~unstable installs? /
No difference, I still use http://www.gentoo.org/doc/en/handbook/handbook-sparc.xml :) Just kiddin'. I have ~sparc, baselayout is 1.11.8 and is marked unstable. Latest stable baselayout is 1.9.4-r6, but I can't really tell if the bug applies to it, I don't do stable ;p Anyway, close bug with resolution LATER (when new baselayout becomes stable)? Sorry for buggin' you. Is there any other handbook for doing ~unstable installs? /©harlie
this only applies to unstable baselayout
There's no handbook for ~ARCH as ~ARCH is unsupported (too many changes). We will update the handbooks when baselayout updates are stabilised. Until then, I'm marking this as INVALID (not LATER because this baselayout might never make it in stable, who knows).
