Apparently, though unproven, at 01:09 on Monday 30 May 2011, Colleen Beamer
did opine thusly:
> > Colleen, you should follow the tip you found on Google to fix this. What
> > stage
> > 3 did you download and use?
> Actually, I used the most recent one - I think May 26th, However, my first
> install (that I screwed up on was the May 25th one, but I got the same
> message. Don't know if it makes a difference, but I used a tarball for
I'm not sure how the stages are built. it might be a hand-crafted list of
stuffs, or maybe it's a script that builds the (mostly) same thing for each
I reckon the latter, in which case x86 and amd64 will probably give similar
> Think I'll try the fix that I found on google first before attempting to
> find a stage 3 tarball that is not faulty.
The google fix will work. Really, trust me, I'm a sysadmin :-)
It's just a missing file that the install process should have made. You simply
need to make it manually.
> BTW, I can't recall from previous installs when I'm supposed to do this,
> but I thought that baselayout got emerged somewhere during the install
> prior to rebooting. There was no place in the handbook that mentioned
> installing baselayout ...... and yes, I did read the news item about
> baselayout2 and openrc migration.
The initial stage contains baselayout already, it's one of those things that
is absolutely needed for a gentoo system to even exist at all. All a stage
really is, is a large archive of an actual install with all it's various bits
- files, dirs, and the matching entries in portage's database of things
OK, it's not really built like that but the analogy will suffice. The end
result is the same and portage cannot tell the difference between baselayout
coming out of the stage and you installing it yourself.
The only time you install baselayout during an install is when you update
world and there's a newer baselayout available than the one in the stage.
That's true for almost every package in portage (except kernel sources, those
alan dot mckinnon at gmail dot com