From: James Bottomley <James.Bottomley@SteelEye.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: viro@parcelfarce.linux.theplanet.co.uk, greg@kroah.com,
Rusty Russell <rusty@rustcorp.com.au>,
Linux Kernel <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [RFC] put symbolic links between drivers and modules in the sysfs tree
Date: 26 Sep 2004 09:09:03 -0400 [thread overview]
Message-ID: <1096204149.10924.2.camel@mulgrave> (raw)
In-Reply-To: <E1CBWOq-0007t6-00@gondolin.me.apana.org.au>
On Sun, 2004-09-26 at 06:37, Herbert Xu wrote:
> James Bottomley <James.Bottomley@steeleye.com> wrote:
> >
> >> So what will your userland code do when you run it on a system with
> >> non-modular kernel currently running?
> >
> > Not put a module in the initial ramdisk, since it would be unnecessary.
> > The only information the patch seeks to add is the linkage between
> > driver and module. So you can work back from sysfs to know which
> > devices have which modules
>
> You're assuming that the kernel before/after the reboot have the same
> configuration. This is false in general.
No I'm not. For an initrd/initramfs the only assumption would be that
the boot device's driver is compiled in or modular. If this isn't true,
the system won't boot anyway.
James
next prev parent reply other threads:[~2004-09-26 13:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 17:29 [RFC] put symbolic links between drivers and modules in the sysfs tree James Bottomley
2004-09-22 23:04 ` Greg KH
2004-09-22 23:06 ` Greg KH
2004-09-22 23:40 ` Greg KH
2004-09-25 7:38 ` viro
2004-09-25 8:05 ` Herbert Xu
2004-09-25 8:21 ` Arjan van de Ven
2004-09-25 13:16 ` James Bottomley
2004-09-25 13:14 ` James Bottomley
2004-09-26 10:37 ` Herbert Xu
2004-09-26 10:37 ` Herbert Xu
2004-09-26 13:09 ` James Bottomley [this message]
2004-09-25 16:46 ` Greg KH
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=1096204149.10924.2.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=greg@kroah.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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.