From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] udev-191 bit me. Insufficient ptys
Date: Thu, 7 Feb 2013 15:25:08 -0600 [thread overview]
Message-ID: <CAEH5T2MkRVVTXTmrSfuUUCUD+Jx_WQn24cS8jYz3YqsZFP3EKA@mail.gmail.com> (raw)
In-Reply-To: <51141466.3030109@libertytrek.org>
On Thu, Feb 7, 2013 at 2:53 PM, Tanstaafl <tanstaafl@libertytrek.org> wrote:
> On 2013-02-07 12:53 PM, Peter Humphrey <peter@humphrey.ukfsn.org> wrote:
>>
>> On Thursday 07 February 2013 17:40:39 Tanstaafl wrote:
>>
>>> So, since I have:
>>>>
>>>> shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
>>>
>>>
>>> I change the type tmpfs to devtmpfs... ok...
>>
>>
>> I think that's a mistake (because I did it too!) - you only need to change
>> the tile type of a /dev line, not /dev/shm.
>
>
> Oh... well, glad I asked...
>
> Can anyone (a dev maybe) please confirm this?
>
> I think that a lot of people will misread that like I (we) did...
I believe he is correct and /dev/shm is irrelevant for this discussion.
The important thing to note is that entries for precisely /dev and
/proc don't need to be in fstab at all for most people if they are
using the standard gentoo openrc/udev combination. I have 3 gentoo
systems running latest ~amd64 openrc and udev and none have /dev or
/proc in fstab and all boot up just fine for me. Obviously if you are
experimenting with other init system or udev alternatives then YMMV
but those people are probably smart enough to figure it out for
themselves already. :)
next prev parent reply other threads:[~2013-02-07 21:25 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 3:35 [gentoo-user] udev-191 bit me. Insufficient ptys Michael Mol
2013-01-31 4:45 ` Canek Peláez Valdés
2013-01-31 4:48 ` Canek Peláez Valdés
2013-01-31 13:26 ` Michael Mol
2013-01-31 13:47 ` Michael Mol
2013-01-31 14:05 ` Michael Mol
2013-01-31 14:30 ` Peter Humphrey
2013-01-31 14:37 ` Michael Mol
2013-01-31 18:24 ` Mick
2013-01-31 18:29 ` Michael Mol
2013-01-31 14:31 ` Michael Mol
2013-01-31 14:45 ` Peter Humphrey
2013-01-31 15:23 ` Alan McKinnon
2013-01-31 15:26 ` Michael Mol
2013-02-02 15:21 ` Alex Schuster
2013-02-02 19:17 ` Alan McKinnon
2013-02-02 20:31 ` Neil Bothwick
2013-02-02 20:47 ` Alan McKinnon
2013-02-02 20:53 ` Bruce Hill
2013-02-03 11:24 ` Neil Bothwick
2013-02-03 12:02 ` Alan McKinnon
2013-02-03 14:54 ` Neil Bothwick
2013-02-03 17:24 ` Alan McKinnon
2013-02-03 19:08 ` Neil Bothwick
2013-02-03 19:23 ` Michael Orlitzky
2013-02-02 21:06 ` Michael Mol
2013-02-03 17:51 ` Alex Schuster
2013-02-03 19:08 ` [gentoo-user] " »Q«
2013-02-07 17:40 ` [gentoo-user] " Tanstaafl
2013-02-07 17:53 ` Peter Humphrey
2013-02-07 20:53 ` Tanstaafl
2013-02-07 21:25 ` Paul Hartman [this message]
2013-02-07 21:37 ` Tanstaafl
2013-02-07 22:00 ` Alecks Gates
2013-02-07 22:12 ` [gentoo-user] " »Q«
2013-02-08 7:29 ` [gentoo-user] " Alan McKinnon
2013-02-08 16:02 ` Paul Hartman
2013-02-08 20:17 ` Peter Humphrey
2013-02-11 1:40 ` Stroller
2013-02-07 21:38 ` Canek Peláez Valdés
2013-02-11 15:38 ` Stefan G. Weichinger
2013-02-11 16:14 ` Mick
2013-02-11 17:36 ` Dale
2013-02-11 19:41 ` Stefan G. Weichinger
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=CAEH5T2MkRVVTXTmrSfuUUCUD+Jx_WQn24cS8jYz3YqsZFP3EKA@mail.gmail.com \
--to=paul.hartman+gentoo@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