public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Question kernel upgrades for dracut users
Date: Mon, 09 Jan 2012 05:08:10 -0600	[thread overview]
Message-ID: <4F0ACA9A.1030009@gmail.com> (raw)
In-Reply-To: <4F0AACF9.2090703@fu-berlin.de>

Hinnerk van Bruinehsen wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I would say it's between 8 and 9 - both versions are slotted, so you
> can install both at the same time. If you have trouble, you can reboot
> from a install cd/usb-drive and reinstall legacy grub. I never had any
> trouble with grub2 and I am using it since about 2 years, I think (at
> least no non-"handmade"-trouble ;) ).
> So I think it's easy.
>
> If you have a line for the init thingy in your grub.cfg it should use
> that or throw an error. If you use dracut according to a fedora-page
> you can add "rdshell rdinitdebug" to your kernel commandline and see
> dracut debugmessages and being dropped to a shell. maybe you could try
> that.
>
> Since I don't use dracut I'm not sure if it would mount a seperate
> usr. A quick google search seems to indicate that you have to do
> something manually: according to the last answer dracut tries to mount
> usr if init is a path in /usr - so you could create a symlink and add
> "init=/usr/bin/init" to your kernel commandline [1] - or use systemd
> (it should reside in usr, shouldn't it?).
>
>
>
>
> [1] http://unix.stackexchange.com/questions/18057/dracut-and-separate-usr
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.18 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEcBAEBAgAGBQJPCqz5AAoJEJwwOFaNFkYc3mMH/2J9bcI7z7weXZZaNe8naw3p
> uPb6mit6Q1xIuirfZhz7z4aQwxbmC/VAvbljWsCu+Ms7PTuJ7ys5UnSSQoZ0aJyV
> 2e73V82zS/m1m2EJ/TPOAHa4kbi7byTIFth4hTQbKfMIdXyZl7w1kvqv8WIdttnt
> n/LPSvXrYRKc/vJ/WavoLZ00tzx2ANvpy1h12zK2KeDwk9/mBEbKCRvMo1RkfiJg
> v3KGn/ZibCRRZc8Nd5xc6NyZlz7i6mW7QFcciteQNr83KOM8sEOnq8Z2ds6QZ/l2
> g1aGrGJl3NDGlAbV9c/VU5oadl1WSqcKCEHUWZPB34MSJgHBcNlWgM90IaeVu9s=
> =aMnj
> -----END PGP SIGNATURE-----
>
>
I was thinking it did mount /usr but wasn't sure.  Actually, I thought 
that was the point.  Thing is, I'm not sure either.  It seems when I 
built mine it read fstab.  Maybe it looks there to see if /usr is on a 
separate partition and if it is then it knows to mount /usr.  I dunno.  
I'll google some more tho.

I followed a couple howtos to get mine to work.  I'm not sure but I know 
one was on a Redhat or Fedora website.  I think the others came from a 
dracut site.

I just wanted to clear up some mud before I dived off into something.

I'll check you link too.

Thanks.

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"




  reply	other threads:[~2012-01-09 11:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-09  0:34 [gentoo-user] Question kernel upgrades for dracut users Dale
2012-01-09  1:08 ` Hinnerk van Bruinehsen
2012-01-09  1:47   ` Dale
2012-01-09  9:01     ` Hinnerk van Bruinehsen
2012-01-09 11:08       ` Dale [this message]
2012-01-09 13:38         ` Dale

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F0ACA9A.1030009@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox