From: mike <mike@kevino.org>
To: linux-newbie@vger.kernel.org
Subject: Re: devfs
Date: Wed, 04 Feb 2004 07:09:41 -0700 [thread overview]
Message-ID: <4020FD25.5060907@kevino.org> (raw)
In-Reply-To: <40208F5E.8020504@kevino.org>
mike wrote:
> Ken Moffat wrote:
>
>>
>>
>>
>> Based on past experience with mdk8.2, which used devfs and worked
>> extremely badly for me, I'd recommend doing without. However, that's a
>> lot easier said than done. You'll need to create static devices, and
>> you won't be able to do this while devfs is blocking access to the real
>> underlying /dev, which means booting from a recovery CD as well as
>> knowing which devices you need, and which groups should own them.
>>
>> I also take the view that most people don't change their underlying
>> hardware and peripherals very often, so for me manually adding a device
>> when I add a usb printer is par for the course. If you don't want that
>> level of involvement and you don't have any problems with it, keep it.
>
>
> I think I'll keep it, sounds like it does alot for me which I'm not
> knowledgeable enough to do for myself. At least at this point in my
> learning process :-)
>
>> Funnily enough, based on an email a little while ago on lkml about udev,
>> I thought Mandrake had already moved away from devfs. [ udev
>> reimplements some of what devfs does, with 2.6 kernels, but its still at
>> an early stage and certainly not intended as a drop-in replacement. ]
>>
>> Ken
>
>
> Thanks for reply Ken.
>
--
Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" 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.linux-learn.org/faqs
next prev parent reply other threads:[~2004-02-04 14:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 3:48 devfs mike
2004-02-03 15:26 ` devfs Ken Moffat
[not found] ` <40208F5E.8020504@kevino.org>
2004-02-04 14:09 ` mike [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-03 6:59 devfs beolach
[not found] ` <40208ADF.7010307@kevino.org>
2004-02-04 14:09 ` devfs mike
2004-02-03 3:53 devfs mike
2002-11-12 9:32 devfs Ian Molton
2002-11-12 9:43 ` devfs Xavier Bestel
2002-11-12 9:49 ` devfs john slee
2002-11-12 10:01 ` devfs Sean Neakums
2002-11-12 12:51 ` devfs Oliver Neukum
2002-11-12 10:05 ` devfs Xavier Bestel
2002-11-12 10:04 ` devfs Alexander Viro
2002-11-12 10:25 ` devfs Ian Molton
2002-11-12 10:46 ` devfs Dave Jones
2002-11-12 11:08 ` devfs Ian Molton
2002-11-12 11:24 ` devfs Rando Christensen
2002-11-12 13:30 ` devfs Alexander Viro
2002-11-12 14:53 ` devfs Alan Cox
2002-11-12 15:37 ` devfs Ian Molton
2002-11-12 11:29 ` devfs Helge Hafting
2002-11-12 15:40 ` devfs Greg KH
2002-08-18 9:10 cerberus errors on 2.4.19 (ide dma related) Alexander Viro
2002-08-18 9:16 ` Ed Sweetman
2002-08-18 18:10 ` Ed Sweetman
2002-08-18 18:20 ` Sean Neakums
2002-08-18 18:29 ` Ed Sweetman
2002-08-18 18:36 ` Sean Neakums
2002-08-18 21:53 ` Barry K. Nathan
2002-08-18 22:26 ` devfs Ed Sweetman
2002-08-18 22:47 ` devfs Sean Neakums
2002-08-18 23:03 ` devfs Alexander Viro
2002-08-18 23:15 ` devfs Ed Sweetman
2002-08-21 4:49 ` devfs Richard Gooch
2002-08-21 5:03 ` devfs Ed Sweetman
2002-08-19 1:06 ` devfs Olivier Galibert
2002-08-19 2:01 ` devfs Greg KH
2002-08-18 23:18 ` devfs Barry K. Nathan
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=4020FD25.5060907@kevino.org \
--to=mike@kevino.org \
--cc=linux-newbie@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 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.