>> On Sunday 16 March 2003 10:55 am, CM Miller wrote:

>> If I cat the backup copy of modules.conf, it pukes
>>out
>> as garbage.

>And hence the file probably couldn't be read at boot
>time.

Sorry, I didn't write back right away, very busy with
school/work.  


So to understand you correctly, during bootup all of
these conf files you see at start up are being read by
cat?  Correct?  


> >> alias sound-slot-0 trident
> >> post-install sound-slot-0 /bin/aumix-minimal -f
> >> /etc/.aumixrc -L >/dev/null 2>&1 || :

> >> What the hell are the post-install and pre-remove
> >> mean?
>
> Those lines are normal, they save and restore mixer
> settings.

I've never seen them before in modules.conf.

>
> What lines?  I'm talking about the pre-remove and
> post-install...those can't be normal...cause once I
> removed them, then all modules loaded back ok.

>The pre remove and post install lines are correct.
The >do nothing 
>more 
>than load and save mixer settings for your sound
card. >Recreating the 
>file is probably what allowed it to work.

> >> alias /proc/scsi/imm
> >> alias /proc/scsi/parport
> >> alias /lib/modules/2.4.18-26.8.0/kernel/fs/ntfs

> >The 3 lines above are invalid, I believe.
> >alias takes the form of "alias alias_name result"

But I want those modules to be loaded each time I
start up my box, so I manually don't have to do it
each time.  

> THey work fine now and load these modules, unless
you
> can give a better example.

>Load what modules?
>The parport module is loaded by: alias
>parport_lowlevel parport_pc
>The ntfs module should be loaded on demand when you
>try to mount an 
>ntfs 
>filesystem (with mount /foo /bar -t ntfs ..., or an
>entry in 
>/etc/fstab), 
>and I've no idea what /proc/scsi/imm is supposed to
>do.
>If you are trying to load an scsi_hostadapter
>something like:
>'alias scsi_hostadapter imm'
>would be the syntax, but I've no idea if that is
>correct for your 
>system. 
>I take it this is for a zip drive? 

You are correct, a zip 250 w/parallel connection.  

>You might try a google search for 
>imm 
>and modules.conf to get the correct entries.


>My best guess at this point is that /etc/modules.conf
>got corrupted. 
>You 
>moved it out of the way, and replaced it with a good
>copy.

But how?  How did it become corrupted?  I still am
trying to understand that? 

thanks

-Chris 



=====
Winning an argument on the internet is like getting 1st place at the Special Olympics

*****************************************
GAIM ID:  cmmiller1973
*****************************************

__________________________________________________
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com



-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to