public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Coywolf Qi Hunt <coywolf@gmail.com>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] devfs: remove devfs from Kconfig preventing it from being built
Date: Wed, 22 Jun 2005 17:23:58 +0800	[thread overview]
Message-ID: <2cd57c9005062202237cd4ece9@mail.gmail.com> (raw)
In-Reply-To: <1119429466l.8047l.1l@werewolf.able.es>

On 6/22/05, J.A. Magallon <jamagallon@able.es> wrote:
> 
> On 06.22, Coywolf Qi Hunt wrote:
> > On 6/22/05, David S. Miller <davem@davemloft.net> wrote:
> > > From: Greg KH <gregkh@suse.de>
> > > Date: Tue, 21 Jun 2005 21:13:30 -0700
> > >
> > > > On Tue, Jun 21, 2005 at 03:59:19PM -0700, David S. Miller wrote:
> > > > > From: Greg KH <gregkh@suse.de>
> > > > > Date: Tue, 21 Jun 2005 15:24:19 -0700
> > > > >
> > > > > However, this does mean I do need to reinstall a couple
> > > > > debian boxes here to something newer before I can continue
> > > > > doing kernel work in 2.6.x on them.
> > > >
> > > > Those boxes rely on devfs?
> > >
> > > Yeah, when I forget to turn on DEVFS_FS and DEVFS_MOUNT in the
> > > kernel config the machine won't boot. :-)
> > >
> > > > Can't you just grab the "static dev" debian package and continue on?
> > > > I'm sure there is one in there somewhere (don't really know for sure,
> > > > not running debian anywhere here, sorry.)
> > > >
> > > > Or how about a tarball of a /dev tree?  Would that help you out?
> >
> > There's /sbin/MAKEDEV on debian.
> >
> > >
> > > I don't know if Debian has such a package.
> > >
> > > Don't worry, I'll take care of this by simply reinstalling
> > > and thus moving to udev.
> >
> > Moving to udev is right. Still you need a "static dev" in case your
> > udev not working.
> >
> > Use /sbin/MAKEDEV from makedev package.
> >
> 
> A nice addition to udev package would be an standard minimal /dev tree
> to allow booting till init and running udev as the first thing...
> A tar.gz you could just unpack on a new box or on an initrd.
> 
> ;)


I guess we've already got one in initramfs.
The "static" /dev is still necessary. I once killed my udevd, and the
static /dev revealed.

-- 
Coywolf Qi Hunt
http://ahbl.org/~coywolf/

  reply	other threads:[~2005-06-22  9:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-21 22:24 [PATCH] devfs: remove devfs from Kconfig preventing it from being built Greg KH
2005-06-21 22:59 ` David S. Miller
2005-06-22  4:13   ` Greg KH
2005-06-22  4:45     ` David S. Miller
2005-06-22  6:23       ` Coywolf Qi Hunt
2005-06-22  8:37         ` J.A. Magallon
2005-06-22  9:23           ` Coywolf Qi Hunt [this message]
2005-06-22  6:40       ` Martin J. Bligh
2005-06-23  3:45         ` Jim Crilly
2005-06-23 10:02       ` Helge Hafting
2005-06-22  8:22   ` Christoph Hellwig
2005-06-22 15:34     ` Nix

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=2cd57c9005062202237cd4ece9@mail.gmail.com \
    --to=coywolf@gmail.com \
    --cc=coywolf@lovecn.org \
    --cc=jamagallon@able.es \
    --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