Re: [gentoo-user] cannot boot using systemd and initrd

Mike Gilbert <floppym@g.o> wrote:

> On Mon, Jan 20, 2014 at 7:38 AM,  <covici@××××××××××.com> wrote:
> > Hi.  I am having a problem booting using systemd and an initrd generated
> > by genkernel.
> >
> > I get the message that says (may be slight paraphrase) that
> > /dev/mapper/linux--files-64--root does not appear to be a valid /, try
> > again.
> >
> > Now in the gentoo guide to systemd, I did what I think it wanted me to
> > do and wrote in my lilo append line real_init=/usr/lib/systemd/systemd
> > .  Now looking at the linuxsrc in the initrd, /usr is not even mounted
> > when it is looking for its init -- after all that fuss about /usr -- and
> > it only seems to look in /sbin for its init and dies.
> >
> > How can I solve this problem -- I suppose I could copy systemd over, but
> > that seems nasty to me and I would have to remember to update it every
> > time systemd was updated!
> >
> > Any assistance on this would be appreciated.
> >
>
> This is bug 479730. https://bugs.gentoo.org/show_bug.cgi?id=479730
>
> One solution would be to switch to genkernel-next. I recommend the
> latest ~arch version.
>
> Another solution would be to use dracut.

OK, thanks -- gentoo-next looks like a good solution -- I hope it will
still work with openrc since until I am sure systemd will do what I
need, I will use openrc and forget gnome exists.

Thanks again.


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@××××××××××.com