Incoming from Ritesh Raj Sarraf: > Lee Braiden wrote: > > > On Monday 16 May 2005 11:02, Carl Fink wrote: > >> Why is it a "problem" and why do you want to stop it? It isn't hurting > >> anything. > > > > I consider this to be "broken" too. It slows down the boot process, and > > the messages are misleading, giving the impression that something is going > > wrong. I haven't got around to removing it from my laptop yet, but on > > another machine I just installed, I'm just skipping the whole hotplug > > thing and loading what I need manually. > > > > No, its not broken. There are a certain modules which get loaded by default > from /etc/modules. Then later when hotplug starts up its hardware probe it .....................^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > tries to load the corresponding module, but finds that its already loaded ..^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
You don't consider that an error? Shouldn't hotplug see if there's anything to do before bulling ahead and doing it? A simple grep of /etc/modules would create an exclude list. > and print that message. If you don't want that message, don't allow the > kernel to load that particular module. > > Its working as designed. Sure. Is the design correct? :-) Better yet, this should be classed as an implementation, not design, issue. The design isn't changed by adding that sanity check to hotplug. -- Any technology distinguishable from magic is insufficiently advanced. (*) http://www.spots.ab.ca/~keeling Please don't Cc: me. - - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
