On Thu, 2005-04-07 at 19:14 -0700, Pete Zaitcev wrote:
> On Wed, 06 Apr 2005 15:08:14 -0400 Peter Jones <pjones@xxxxxxxxxx> wrote:
> > But at the same time, once somebody actually starts using this
> > rc.modules.d idea, they're going to quickly discover that they want
> > ordering there, as well, to make sure e.g. the various usb hcd modules
> > are loaded in the order they want.
>
> I don't think so. First, USB is processed in a special way, and I asked not
> to bring it up in the very first message (after which someone immediately
> replied with a discussion about USB). But second, HCD modules are not
> ordered, even in case of EHCI and its companion controllers. If you see
> different results depending on the loading order, file a bug.
Ok, that one example isn't completely perfect, so here's a better one.
If I load usb_storage before sd_mod, the iRiver plugged into my usb port
is going to be sda, and the drive plugged into my scsi bus will be sdb,
right?
And if I load them in the opposite order?
I'm sure you can find *many* more examples of module load order
mattering to sysadmins and users, but where there's no strict dependency
in the code. If people use rc.modules.d, they're going to hit them.
> Just what is your definition of "awfully cluttered"? I noticed that all
> my directories get much bigger and filesystem trees way branchier when
> I use Nautilus, because with ls I try to keep them smaller than one
> screenful subconsciously. Or do you have any other criteria?
When there are enough files in rc5.d that I often have to choose between
using the service name as part of the sort or renumbering other
services, I call that cluttered. And we're already at that point.
--
Peter
