All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: Non-hardware devices like loop: another idea
Date: Thu, 18 Mar 2004 09:58:06 +0000	[thread overview]
Message-ID: <405972AE.9000008@ums.usu.ru> (raw)
In-Reply-To: <200403122003.00557.patrakov@ums.usu.ru>

Mike Snitzer wrote:

>Ok, so at system boot udevstart walks sysfs and populates /dev 
>accordingly;
>loop devices work great.  GregKH says tun/tap devices now work in 2.6.4;
>so ultimately its just a matter of adding sysfs support to the various
>device drivers.
>
>But your desire for loading modules when a device node is accessed isn't
>doable.

This is not my desire. My wish is that all devices supported by kernel
(even by means of modules) should be present in /dev, before (not when!)
a program tries to access them, as it is the case now e.g. for PCI
soundcards where the hotplug initscript probes the needed modules when
the system boots.

-- 
Alexander E. Patrakov












-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2004-03-18  9:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-12 15:03 Non-hardware devices like loop: another idea Alexander E. Patrakov
2004-03-17  1:47 ` Mike Snitzer
2004-03-17  4:13 ` Alexander E. Patrakov
2004-03-17  4:26 ` Mike Snitzer
2004-03-17  6:39 ` Alexander E. Patrakov
2004-03-17 17:01 ` Mike Snitzer
2004-03-18  3:56 ` Alexander E. Patrakov
2004-03-18  4:24 ` Greg KH
2004-03-18  4:55 ` Mike Snitzer
2004-03-18  9:55 ` Alexander E. Patrakov
2004-03-18  9:58 ` Alexander E. Patrakov [this message]
2004-03-18 10:23 ` Marco d'Itri

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=405972AE.9000008@ums.usu.ru \
    --to=patrakov@ums.usu.ru \
    --cc=linux-hotplug@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.