public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: devfs and udev
Date: 9 Oct 2003 22:09:33 GMT	[thread overview]
Message-ID: <bm4mat$6ld$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 20031007213758.GB3095@kroah.com

In article <20031007213758.GB3095@kroah.com>,
Greg KH  <linux-kernel@vger.kernel.org> wrote:

| mount -t ramfs none /dev
| 
| That is what udev will run off of :)
| 
| Again, can you point me to any documentation that states that udev will
| do this on a persistant filesystem?

I'm going back to look again, but I don't recall that it won't, either.
If it wants a ramfs on /dev, why doesn't it just create one? That's a
question, not an argument! I had assumed it would run on a persistent
f/s if present.
-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.

  parent reply	other threads:[~2003-10-09 22:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-07 13:17 devfs and udev Bradley Chapman
2003-10-07 13:32 ` Måns Rullgård
2003-10-07 18:28   ` insecure
2003-10-07 18:44     ` viro
2003-10-07 19:41     ` Greg KH
2003-10-07 20:47       ` insecure
2003-10-07 20:52         ` Greg KH
2003-10-07 21:17           ` Chris Meadors
2003-10-07 21:48             ` Greg KH
2003-10-08  7:30               ` Andreas Jellinghaus
2003-10-08 12:07                 ` [2.6 patch] document that udev isn't yet ready Adrian Bunk
2003-10-07 21:27           ` devfs and udev Måns Rullgård
2003-10-07 21:37             ` Greg KH
2003-10-07 22:01               ` Måns Rullgård
2003-10-07 22:12                 ` Bryan O'Sullivan
2003-10-07 22:49                   ` Måns Rullgård
2003-10-07 23:27                     ` Greg KH
2003-10-08  0:03                       ` Måns Rullgård
2003-10-09 22:09               ` bill davidsen [this message]
2003-10-13 20:15                 ` Tom Rini
2003-10-07 20:57 ` David Lang
2003-10-08 22:34   ` H. Peter Anvin

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='bm4mat$6ld$1@gatekeeper.tmr.com' \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.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