mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "William Knop" <w_knop@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Modules and DevFS
Date: Thu, 01 Feb 2001 03:44:38 -0500	[thread overview]
Message-ID: <F204tAEHLB8TrBHxvZ900001de6@hotmail.com> (raw)

>One thing that I've noticed with devfs is that all the old-style names are
>symlinks.

Hmm... I have no symlinks until the module loads. Therefore X sees no 
/dev/input/mouse, doesn't ask the kernel for it, the kernel doesn't load the 
module, and DevFS doesn't add the /dev entry. There's got to be an easy way 
around this. Perhaps it has already been implimented, but I haven't been 
able to get anything to work well (manual loading for me).

>Everything is modularized here, including ppp and such, and modprobe is
>loading everything quite nicely for me.  I don't like to run one big
>kernel, it wastes too much memory, and so I use pretty much *everything*
>that I can in modules (IDE I can't, because I boot from IDE, but I leave
>SCSI in a module, becuase I use ide-scsi to burn my CDs and it's not
>*reqired*).

Really? How can DevFS know which devices to add to /dev/scsi/... without 
loading the module and scanning the bus first? Or do you manually insert the 
scsi module when you need it?

Do you think if I add symlinks manually perhaps it will force DevFS to look 
for a module to add the needed entry? Or maybe module aliases? I think I am 
going to spend some time checking out the DevFS code and experimenting with 
module entries.

-Will
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com

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

             reply	other threads:[~2001-02-01  8:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-01  8:44 William Knop [this message]
2001-01-31 22:56 ` Michael B. Trausch
2001-02-02 10:35   ` Helge Hafting
2001-02-02 20:00     ` Michael B. Trausch
2001-02-05 10:36       ` Helge Hafting
2001-02-02 20:33     ` Georg Nikodym
2001-02-01 10:23 ` Peter Samuelson
2001-02-01 15:22 ` John Jasen
2001-02-01 16:13 ` Georg Nikodym
  -- strict thread matches above, loose matches on Subject: below --
2001-01-31 21:34 William Knop
2001-01-30 22:20 ` Michael B. Trausch
2001-01-31 22:05 ` Brian May
2001-02-01 10:31 ` Helge Hafting

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=F204tAEHLB8TrBHxvZ900001de6@hotmail.com \
    --to=w_knop@hotmail.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

all inboxes | Powered by JetHome®