public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [HEADS UP] udev-181
Date: Mon, 19 Mar 2012 11:15:25 -0400	[thread overview]
Message-ID: <CA+czFiBCKWd-0B3AoLHaL9v5qfdJAccNnnz4HJLHEHTOqrWtBg@mail.gmail.com> (raw)
In-Reply-To: <jk7hf8$8b7$1@dough.gmane.org>

On Mon, Mar 19, 2012 at 10:56 AM, walt <w41ter@gmail.com> wrote:
> I just had a bit of a scare after updating to udev-181, but
> all is well now, finally.  (I hope :)
>
> In addition to the separate /usr problem that has already
> been discussed at length here, there are other important
> changes in udev-181 to be aware of.
>
> First, I had to add two new items to my kernel config:
> CONFIG_DEV_TMPFS (which I thought I'd had for years but didn't)
> and CONFIG_TMPFS_POSIX_ACL.  I also elected to make the devfs
> automounting, but I don't think that was really necessary.
>
> Second, don't forget like I did to update the udev initscripts
> with etc-update or your machine won't be able to find the udev
> files in their new locations (just like mine didn't) and none
> of your kernel modules will auto-load, either.
>
> Oh, and of course you need to pre-mount /usr before udev starts
> if you have a separate /usr partition -- but you already knew
> that ;)

Is there an ENOTICE warning in the ebuild to hit people over the head
with these?

Also, how trivial would it be to have the ebuild check the running
kernel config (if available under /proc or wherever) for the necessary
config options?

-- 
:wq



  reply	other threads:[~2012-03-19 15:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 14:56 [gentoo-user] [HEADS UP] udev-181 walt
2012-03-19 15:15 ` Michael Mol [this message]
2012-03-19 15:55   ` [gentoo-user] " walt
2012-03-19 18:15   ` [gentoo-user] " Mark Knecht
2012-03-19 17:54 ` jason

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=CA+czFiBCKWd-0B3AoLHaL9v5qfdJAccNnnz4HJLHEHTOqrWtBg@mail.gmail.com \
    --to=mikemol@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