In all honesty, being a newbie, I can't really debate the technical merits on the install with any authority at all. However, modules conf, modprobe, and depmod wouldn't work for me after in rpm'ed the 2.4.2 and modutils-2.4.2-14 and followed the instructed for install/post-install. I only got the new kernel to properly display and work with the modules after a copied the fc.config.old to the rc.config. After reboot everything appeared ok. Although the video drivers and the new kernel don't get along at all. Why this worked I couldn't say. -----Original Message----- From: Brooklyn Linux Solutions CEO [mailto:ruben@dsl254-112-136-sea1.dsl-isp.net] Sent: Monday, April 23, 2001 1919 To: Rafael E. Herrera Cc: suse-linux-e@suse.com Subject: Re: [SLE] Support vs Support (Was: [SLE] util-linux and Kernel 2.4.3)
wrong, modules.conf is part of the modutils packages and is integral part of suse. /etc/rc.d files are part of the sys V init mechanism and has nothing to do with modules.conf.
Of course they are related. What does mk_intird do but create boot scripts for the kernel dameon. Are you saying that I use any init scripts and module.conf will look the same? The original /rc.d/boot - or some other script in that directory had a case in the shell script looking for kerneld and conf.modules or modules.conf or both or either ;) If the loader is not initiallized correctly on boot, modules.conf, modprobe and depmod fails to work correctly. I really didn't want to rewrite half the system. Someone will acuse me of just not being smart enough and blaming my deficiencies on SuSe ;)
There is no mkinitrd script in SuSE. To create initrd files under suse you use mk_initrd.
Which is the best peice of information to come out of this thread ! Ruben -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com