Linux-kernel mailing list archive 1998-31,: Re: DEVFSv50 and /dev/fb? (or /dev/fb/? ???)

# Re: DEVFSv50 and /dev/fb? (or /dev/fb/? ???)

Kragen (kragen@pobox.com)
Fri, 7 Aug 1998 21:17:52 -0400 (EDT)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Richard Gooch: "Re: DEVFSv50 and /dev/fb? (or /dev/fb/? ???)"
- Previous message: David Burrows: "Re: DEVFS and permissions/group/owner"
- In reply to: Richard Gooch: "Re: DEVFSv50 and /dev/fb? (or /dev/fb/? ???)"
- Next in thread: Nathan Hand: "Re: DEVFSv50 and /dev/fb? (or /dev/fb/? ???)"

On Sat, 8 Aug 1998, Richard Gooch wrote:
> When you attempt to access a device node which isn't there (say
> "ide/cd/c0b0t0u0") then for each path component that doesn't exist,
> devfs sends that to kmod. Thus, potentially, you have have the
> following sequence of strings sent to kmod: "ide", "ide/cd",
> "ide/cd/c0b0t0u0".

Oh, OK.

Is this something that I should already know from reading the FAQ?
(It's been a few weeks.)

> then the ide-cd module will be loaded as required. Then the module
> will detect your CD-ROM and will also register the "c0b0t0u0"
> entry. So in general only one request is made to kmod: "ide/cd".
>
> Something to keep in mind here is that while device entries don't
> appear/exist at first, an explicit lookup of the inode (any syscall
> that provides a pathname) will trigger kmod. So it all just magically
> works.

Good!

Kragen

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html

- Next message: Richard Gooch: "Re: DEVFSv50 and /dev/fb? (or /dev/fb/? ???)"
- Previous message: David Burrows: "Re: DEVFS and permissions/group/owner"
- In reply to: Richard Gooch: "Re: DEVFSv50 and /dev/fb? (or /dev/fb/? ???)"
- Next in thread: Nathan Hand: "Re: DEVFSv50 and /dev/fb? (or /dev/fb/? ???)"