From: Jim Crilly <jim@why.dont.jablowme.net>
To: "Martin J. Bligh" <mbligh@mbligh.org>
Cc: "David S. Miller" <davem@davemloft.net>,
gregkh@suse.de, torvalds@osdl.org, akpm@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] devfs: remove devfs from Kconfig preventing it from being built
Date: Wed, 22 Jun 2005 23:45:04 -0400 [thread overview]
Message-ID: <20050623034504.GL21897@mail> (raw)
In-Reply-To: <258190000.1119422406@[10.10.2.4]>
On 06/21/05 11:40:06PM -0700, Martin J. Bligh wrote:
> >> > 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?
> >
> > 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.
>
> ??? I use debian sarge all the time with kernel.org kernels that don't
> have devfs compiled in, and I don't use udev either. Works across ia32,
> x86_64, and PPC64 (32 bit userspace) at least, with no trouble at all,
> out of the box. I did the same with Woody as well before that ...
I think he's just saying that since he did the install with devfs enabled
and has been using devfs device names, a conversion back to 'standard'
names would be a major PITA. It's definately possible to convert, but if
there's not much on the boxes a reinstall might be quicker.
>
> M.
Jim.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2005-06-23 3:48 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
2005-06-22 6:40 ` Martin J. Bligh
2005-06-23 3:45 ` Jim Crilly [this message]
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=20050623034504.GL21897@mail \
--to=jim@why.dont.jablowme.net \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.