Re: [gentoo-dev] openrc portage news item

[Brian Harring <ferringb@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2173 bytes --]

On Fri, Apr 22, 2011 at 12:39:04PM +0200, Lars Wendler wrote:
> Am Donnerstag 21 April 2011, 03:12:21 schrieb Donnie Berkholz:
> > It seems like nobody's really clear on what exactly happens though,
> > since I've seen people talking about this *maybe* resulting in an
> > unbootable system. Has anyone tested it?
> 
> I didn't test it intentionally. The last time I accidently rebooted a system 
> freshly moved to bl-2/openrc without updating the config files the boot process 
> threw a couple of strange errors. I cannot exactly remember what kind of 
> errors that were but the result was a system hanging in the middle of the boot 
> process with a message similar to "nothing left to do in this runlevel" and I 
> wasn't able to log into the system.
> Another problem I've once encountered after updating a system to use openrc 
> was no running udev daemon after boot. I first didn't notice this but X didn't 
> start and funny part was that X won't tell you it cannot start because the 
> devicenodes in /dev for the graphics card were missing. So took me nearly a 
> day of frustrating research until I found that the udev init script wasn't 
> added to the sysinit runlevel. Of course this is mentioned in the migration 
> guide but it should be explicitly pointed out how fatal this can be to not 
> have udev getting started.
> 
> I can offer to "abuse" my two stable VMs (amd64 / x86) for this to test if 
> there's interest in getting "exact results".  :)

Exact results please; the pkg_pretend crap proposed elsewhere (which 
is yet another way to crap up stage builds) frankly sucks.

Mind you I'm just looking in, but this whole upgrade process really 
reads fairly suboptimal to me.  It's definitely possible that this is 
the best that can be done, but I'd like to see exactly which issues we 
can't resolve in some fashion via pkg_postinst tricks w/in openrc.

I'd much rather have an ebuild that violates a few rules than forced 
"you must accept this beyond normal mechanisms" and potential "can't 
boot" upgrade processes.

So... details please, and why we can't script our way past chunks of 
this. :)
~brian

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]