Mark Knecht <[email protected]> posted
[email protected], excerpted
below, on Thu, 05 Feb 2009 11:31:11 -0800:
> Everyone's sort of quiet today...
>
> So, reading back through this thread I'm wondering what the risk level
> is in going to the newer baselayout stuff? If I keyword baselayout
> ~amd64 then it wants openrc. If I then keyword openrc ~amd64 it wants me
> to emerge -C stuff that, should the power go off during the process,
> might leave the system unbootable.
>
> Is udev *really* going away?
>
> - Mark
>
> lightning ~ # emerge -pvDuN system
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild U ] sys-apps/baselayout-2.0.0 [1.12.11.1] USE="-build
> (-bootstrap%) (-static%) (-unicode%*)" 23 kB
> [ebuild N ] sys-apps/openrc-0.4.2 USE="ncurses pam unicode -debug"
> 142 kB
> [blocks B ] <sys-fs/udev-133 ("<sys-fs/udev-133" is blocking
> sys-apps/openrc-0.4.2)
> [blocks B ] <sys-apps/sysvinit-2.86-r11
> ("<sys-apps/sysvinit-2.86-r11" is blocking sys-apps/openrc-0.4.2)
You need a newer udev and a newer sysvinit. Try keywording them too.
A word of caution. Newer baselayout with openrc is nice when you get it
going, but the transition isn't very smooth yet, that being one of the
reasons its not stable, the upgrade isn't something they're ready to
release on thousands of unprepared users just yet.
Expect a LOT of etc-updates when you first upgrade, and have a live-CD
handy (as you mentioned you already used so you do) as there may be
services that don't work right until you finish adjusting for the new
setup. In particular, if you run RAID, LVM, or DeviceMapper, the way
baselayout-2/openrc handles them has changed rather drastically. The
network configuration has changed substantially as well, and unlike the
above RAID, etc, the networking changes affect nearly everyone. However,
it's not quite so unsettling to boot and not have a net as it is to boot
and not have your partitions load!
What I'd suggest is that you upgrade sysvinit, run etc-update (or your
preferred alternative) for its files only, then upgrade udev and run etc-
update again, then baselayout and openrc. That way you won't have quite
as many config updates to deal with at once. Actually, I'd recommend
that you do sysvinit and udev one day, then read up on the issues (see
the tracker bug linked below), and save baselayout and openrc for a day
when you have a nice block of several hours (4-8) to resolve any issues
you find as you upgrade them. A lot of folks have already made the
transition so it's absolutely doable, but it's far from the fully
documented "easy" transition it should be before it goes stable. Take it
slow and work thru the issues one at a time, and there shouldn't be
anything too big to tackle. But try to do it all at once without knowing
what your in for, especially if you're planning on say making a
presentation with that machine in a couple hours or something (yes, I
/have/ seen people try serious system upgrades with a big presentation
that close!), and you're setting yourself up for a WORLD of hurt.
You'll also want to check out the documentation tracker bug, at least to
get an overview of where things are:
http://bugs.gentoo.org/show_bug.cgi?id=213988
Of course, keep in mind that some of that/those info and comments are
nearing a year old now, and may not represent current status. In
particular, the networking discussion thread I link is somewhat dated.
But there's documentation in the net.conf config file itself once you
merge baselayout-2/openrc, that should be relatively updated and accurate.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
