Brooklyn Linux Solutions CEO wrote:
I think you're trying to blame your faults on us here, because you apparantly consider yourself some kind of expert.
You know what - maybe your right. But I just finished doing this with Slackware with no trouble.
And I was working with some VA system engineers when I was doing the SuSe upgrade. They didn't know exactly why module.conf seemed to be completely ignored when the upgrade happened by the kernel dameom. I tried to force kerneld into use though the system setup files, that failed. kmod was failing, kerneld was failing.. so maybe you can tell me why the kernel refused to load the aic7xxx drivers and the 3c90x drivers. The RH solution was tied to mkinitrd which wasn't on the system ANYWHERE. The docs from the source code at
/sbin/mk_initrd creates initrd's for all kernel for which there's an initrd entry in lilo.conf using /etc/rc.config variable INITRD_MODULES to determine which modules to insert.
kernel.org lead to a hand compile of module-utils etc, and the kernel which caused an infinite LOOP in the login process. And in single user mode, nothign showed in the logs as any error. So the system failed without logging any messages!
So your probibly right. It's my fault. Sorry for mentioning it.
The I would like you to send to this list *exactly* what you wanted to do, and where the problem arose. Let's stick to technical facts.
The list can read the archival history.
No here is the deal, untill I did an automated update from the 7.1 disk which rewrote the init system, and loaded a bunch of stuff I didn't ask for...nothing from either YAST available RPM's or hand compiling worked to get the system working.
I had reached a point wheren I was consulting face to face with others, but tracking the problem down through the entire sysV system just didn't make sense over upgrading through the 7.1 CD's
You know, the other extreme _does_ exist as well - insert 7.1 cd, select "upgrade", and all works. I know that doesn't help those stuck with the problems. In addition, 7.0->7.1 was a major step. 7,0 was really a 6.5... oh well. No it's not the marketing guys fault, we had a product split into two products, plus when we did the planning for 7.0 we expected both kde 2 and kernel 2.4 to become available. Neither did, but it's harder to change a printing press than to just go through with this too-early version number change.