From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] I guess it is time to update udev from 171-r10 to 197-r8...
Date: Mon, 18 Mar 2013 07:15:39 -0400 [thread overview]
Message-ID: <5146F75B.8030104@libertytrek.org> (raw)
In-Reply-To: <51460C8E.1090303@libertytrek.org>
Ok, spent a little time re-reading the old threads about this...
Just to confirm, changes I should make in my /etc/fstab...
<snip> normal fs lines
> # NOTE: The next line is critical for boot!
> none /proc proc defaults 0 0
I can/should simply delete the above two lines?
then
> # glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
> # POSIX shared memory (shm_open, shm_unlink).
> # (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
> # use almost no memory if not populated with files)
> shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
I should change the above line to:
> tmpfs /dev/shm tmpfs nodev,nosuid,noexec 0 0
Combined with the other recommended changes:
> - Remove udev-postmount from runlevels.
>
> - Enable CONFIG_DEVTMPFS=y in the kernel;
I've also seen recommendation to enable:
CONFIG_DEVTMPFS_MOUNT=y ?
> need to verify the fstype for possible /dev line in /etc/fstab is
> devtmpfs (and not, for example, tmpfs)
I have no /dev line, and only one network adapter, so nothing to do here
> - The case of separate /usr; if it worked for you with 171 it will
> continue to work for you with 197 (or newer). We still recommend
> initramfs with separate /usr mounting capabilities because you
> might need packages like sys-apps/kbd (keymaps in /usr) or
> net-wireless/bluez (possible keyboard) in early boot.
Ok, this one is unclear...
My system is currently indeed (and always has been) booting fine with a
separate /usr (on lvm)... but...
The above reference to 'might need packages like sys-apps/kbd', which is
now *required* by udev, suggests that now I again do need an initramsf?
Thanks for ya'lls patience. I have a feeling this is going to be another
non-event, but I'd much prefer a little pre-update pain than a lot of
post-update pain... ;)
next prev parent reply other threads:[~2013-03-18 11:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 17:46 [gentoo-user] I guess it is time to update udev from 171-r10 to 197-r8 Tanstaafl
2013-03-17 18:17 ` Neil Bothwick
2013-03-17 18:33 ` Tanstaafl
2013-03-17 20:12 ` Neil Bothwick
2013-03-18 8:18 ` [gentoo-user] " Nuno Silva
2013-03-18 10:14 ` Tanstaafl
2013-03-18 10:18 ` Alan McKinnon
2013-03-18 11:15 ` Tanstaafl [this message]
2013-03-18 13:39 ` [gentoo-user] " Neil Bothwick
2013-03-19 13:25 ` Tanstaafl
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=5146F75B.8030104@libertytrek.org \
--to=tanstaafl@libertytrek.org \
--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