From: Helge Hafting <helge.hafting@aitel.hist.no>
To: "David S. Miller" <davem@davemloft.net>
Cc: jim@why.dont.jablowme.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] devfs: remove devfs from Kconfig preventing it from being built
Date: Thu, 23 Jun 2005 12:02:17 +0200 [thread overview]
Message-ID: <42BA88A9.6010701@aitel.hist.no> (raw)
In-Reply-To: <20050621.214527.71091057.davem@davemloft.net>
David S. Miller 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?
>>
>>
>
>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.
>
That works, but seems like "the long way".
You don't need to be given a tarball of a /dev tree - make your own!
tar up your existing devfs-based /dev tree (at a time when all
your devices are present) then umount devfs and untar it
all. Then you have a static /dev which works with the existing setup,
and a nondevfs kernel can boot right away.
The udev way may be necessary if you actually have lots of devices
that come and go, such as usb thingies. It shouldn't be necessary
just to boot the machine though.
Jim Crilly wrote:
>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.
Fortunately, one doesn't need to convert back. Just copy devfs-dev onto
ext3-dev and there you have the "good old" devfs-names in a static /dev.
Helge Hafting
next prev parent reply other threads:[~2005-06-23 10:14 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
2005-06-23 10:02 ` Helge Hafting [this message]
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=42BA88A9.6010701@aitel.hist.no \
--to=helge.hafting@aitel.hist.no \
--cc=davem@davemloft.net \
--cc=jim@why.dont.jablowme.net \
--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