From: KC <kcc1967@gmail.com>
To: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>
Cc: Erik Mouw <erik@harddisk-recovery.com>, linux-kernel@vger.kernel.org
Subject: Re: proc_mknod() replacement
Date: Tue, 10 May 2005 10:05:34 +0800 [thread overview]
Message-ID: <5eb4b065050509190549b1100d@mail.gmail.com> (raw)
In-Reply-To: <200505092107.j49L7J7C028882@turing-police.cc.vt.edu>
On 5/10/05, Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote:
> On Tue, 10 May 2005 01:06:08 +0800, KC said:
>
> > Why I want to use proc_mknod() in driver ? I write a small package, ovi-dev,
> > which can be downloaded from
> > http://www.sourceforge.net/projects/ovi
> > The ovi-dev will scan the PCI bus and if it found, eg, 3 PCI devices, it
> > will create 3 device entries (nodes) automatically at module load time.
> > So number of device entries (nodes) will match number of devices
> > of the system ... well, UNIX/Linux doesn't work that way ... there are a lot
> > of device entries ... but no corresponding hardware existed.
>
> Congrats. You've re-invented udev.
No, it's not ... dynamic entry is not my purpose, but a good
feature which I want to have in my package and I did it using
proc_mknod() for 2.4.x ...
Anyway, I'll check udev to see if it's enough for me.
Thanks
KC
>
>
>
next prev parent reply other threads:[~2005-05-10 2:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 11:17 proc_mknod() replacement KC
2005-05-09 15:41 ` Erik Mouw
2005-05-09 17:06 ` KC
2005-05-09 21:07 ` Valdis.Kletnieks
2005-05-10 2:05 ` KC [this message]
2005-05-09 22:04 ` Jim Crilly
2005-05-10 2:43 ` KC
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=5eb4b065050509190549b1100d@mail.gmail.com \
--to=kcc1967@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=erik@harddisk-recovery.com \
--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