Sorry for the so long delay in answering.. Andrey Borzenkov <[EMAIL PROTECTED]> writes:
> On Friday 16 May 2003 18:26, Guillaume Cottenceau wrote: > > > > why not deciding on $kernel like you do for deciding if > > bootsplash need be disabled? > > It is needed anyway. It is impossible to just parse modprobe output because > you may create 2.5 under 2.4 and vice versa and modules are different across > versions. So this adds check for kernel version. 2.4 and below or 2.5 and > above. Yes but $kernel contains the target kernel so that's just the information you need, no? You already do so for bootsplash. Or excuse my extreme stupidity? I'm maybe not getting something. > > Ok. Me too I far prefer perl, but for mkinitrd it's a no-no. > > this one is using awk. Frankly speaking I think it is much easier to just add Ouch it's long and extreme.. is this really needed? > probeall (and possible probe) to modprobe from module-init-tools than add > highly unreliable parsing to every package that has to check modules conf. Ah, so in that case the above mentioned code would be unneeded, right? Frankly I'd prefer not having to maintain the frightening awk code you've submitted to me :). > I am still fighting with initscripts; at some point during boot it apparetly > calls modprobe -C /etc/modules.devfs and I cannot find out where. It results > in a flood of errors from modprobe. > > -andrey > -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
