On Thu, May 17, 2007 at 03:30:43PM -0600, Matthew Wilcox wrote:
> On Thu, May 17, 2007 at 03:43:26PM -0400, Benjamin LaHaise wrote:
> > On Thu, May 17, 2007 at 01:39:54PM -0600, Matthew Wilcox wrote:
> > > On Fri, May 18, 2007 at 12:34:40AM +0530, Satyam Sharma wrote:
> > > > Hmmm, actually those other users could easily write and maintain
> > > > a 20-line patch that does the wait for async scans thing for them
> > > > using /proc/scsi/scsi in any case.
> > >
> > > How about the three users who're bothered by this extra module being
> > > built maintain a one-line patch to Kconfig and leave well enough alone?
> >
> > The module has an added bonus that it doesn't require any new tools to
> > make work. Doing it via sysfs/procfs means a new rev of whatever tool
> > generates the boot initrd, plus fixing up boot scripts. Loading a module
> > can be done via a simple option to the existing boot tools.
>
> That was what James and I thought. However, the distros seem unhappy
> with it. Of course, they won't actually *comment* on it, they just
> disable the async scan and won't talk about why.
FWIW, Fedora 7 has it enabled, and afaik, Peter (mkinitrd maintainer) is happy
with the current situation. It's my understanding that the latest ubuntu
release has it enabled too, though obviously I can't speak for whether
or not they're happy with the status quo.
Dave
--
http://www.codemonkey.org.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
