Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269530AbUIZNKO (ORCPT ); Sun, 26 Sep 2004 09:10:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269527AbUIZNKO (ORCPT ); Sun, 26 Sep 2004 09:10:14 -0400 Received: from stat16.steeleye.com ([209.192.50.48]:18371 "EHLO hancock.sc.steeleye.com") by vger.kernel.org with ESMTP id S269530AbUIZNKH (ORCPT ); Sun, 26 Sep 2004 09:10:07 -0400 Subject: Re: [RFC] put symbolic links between drivers and modules in the sysfs tree From: James Bottomley To: Herbert Xu Cc: viro@parcelfarce.linux.theplanet.co.uk, greg@kroah.com, Rusty Russell , Linux Kernel , SCSI Mailing List In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-9) Date: 26 Sep 2004 09:09:03 -0400 Message-Id: <1096204149.10924.2.camel@mulgrave> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1024 Lines: 26 On Sun, 2004-09-26 at 06:37, Herbert Xu wrote: > James Bottomley 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/