From: mike <mike@kevino.org>
To: linux-newbie@vger.kernel.org
Subject: Re: devfs
Date: Wed, 04 Feb 2004 07:09:14 -0700 [thread overview]
Message-ID: <4020FD0A.8020009@kevino.org> (raw)
In-Reply-To: <40208ADF.7010307@kevino.org>
mike wrote:
> beolach@comcast.net wrote:
>
>> Sorry for the length of this reply, I was bored and felt like writing
>> a novel.
>
>
> Thats quite alright, I need to have things spelled out to me.
> And your explanation helped me understand quite abit more of whats going
> on.
>
>> Well, no you don't *need* to have devfs, and it would be really easy
>> to remove,
>> but I wouldn't recommend it, for a couple reasons. First of all,
>> devfs really
>> is the best way to do what's being done (see below), and secondly (and
>> more
>> importantly) I don't subscribe to the engineering maxim, "If it's not
>> broken,
>> fix it."
>
>
> I agree with you on that, theres much more to it than I thought, and
> from your explanation way out of my league. Sounds like it could get
> complicated. My system runs well for me I would hate to 'jinks'
> that :-)
>
>
>> And because enough people do dislike the new naming scheme, it
>> can be changed in /etc/devfsd.conf (if you can figure out how - my
>> very brief
>> glance at it looked complicated). While the new names are longer,
>> they also
>> give more information with less ambiguity than the old names. And
>> IIRC devfs
>> by default does make symlinks to to all the old names.
>
>
> I was used to the /dev/hda naming scheme and understood it, is why the
> new naming kinda through me when I used the "df" command.
> But your explanation of how it works makes sense to me, and I believe I
> can used to it.
>
>>
>> Well, that's my novel for today. Hope you enjoy,
>> Conway S. Smith
>
>
> I appreciate your responce thanks, Conway
>
--
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 6:59 devfs beolach
[not found] ` <40208ADF.7010307@kevino.org>
2004-02-04 14:09 ` mike [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-03 3:53 devfs mike
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 ` 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=4020FD0A.8020009@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.