-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 16 March 2003 11:01 pm, CM Miller wrote: > 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. > >> 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. > > 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" > 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 might try a google search for imm and modules.conf to get the correct entries. I'd love to give an example, but since those 3 lines do _nothing_ (as near as I can tell) I'd be hard pressed to find a replacement. ;) Prove it to yourself, remove those 3 lines, reboot and see if it makes a difference. alias takes 2 arguments, in the lines above you've assigned the names given to NULL. > >Which, the mixer lines? They shouldn't have caused > > any >problem. > > I believe that they did, I removed them and things > were then ok. Again, no. You recreated modules.conf, most likely replacing a corrupt version. You said yourself that you can't cat the backup file. > I still do not understand what happened here which > caused it to screw up. 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. - -- - -Michael pgp key: http://www.tuxfan.homeip.net:8080/gpgkey.txt Red Hat Linux 7.{2,3}|8.0 in 8M of RAM: http://www.rule-project.org/ - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+dVwNn/07WoAb/SsRAvElAJ4nPJBFNZkdTiHi5uYRK1vsLw6vqgCff8sE cTljIP1ZwO18ToXJFCJT4kI= =aUPQ -----END PGP SIGNATURE----- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
