Brooklyn Linux Solutions CEO wrote: ....
Maybe 1000 times I've compiled kernels on RH, Slackware, Strorm, Debian and SuSe.
This compile DOES NOT WORK because the sysv init system and the kernel module is SCREWED....(as hinted at in the docs).
??? Nothing is screwed, works beautifully. When 7.0 was made LSB did NOT have anything to say about the init system, so we continued to use what we always used. Which by the way I still find much nicer than the new one. When it was time for 7.1 LSB had indeed defined how sysV should look like - and look, we immediately took it! And the "old" system was never "screwed".
modules.conf was invisible to the 7.0 system with a hand compile
What are you talking about??? This file is a standard.
and the initiation system was screwed with the RPM's...problbly secondary to PAM or the location of the files?
??? can't decipher that... what "initiation"??? what rpm's???
AND BTW - mod-ulits? Where waas that under the 7.0 tree in yast? ....... Hmm - not there.....
Where it is supposed to be: ftp://ftp.suse.com/pub/suse/i386/update/7.0/a1/ Please read: the directory you were looking it is called "kernel", which means you will find - kernel rpm's! There are also some links to yast, etc. in that directory, and ALSO for modutils. Just looked in 7.0 and 7.1 update directory. So I don't know what you are talking about...??? Arguably, the update stuff is the least documented at SuSE. This will be better once all files are avaiable via YOU (online update), which of course also means a much better yast2 YOU module than now. Right now esp. the kernel update directory is very, very poorly documented - that's true. Basically, in the current state we should really add an "experts only" sticker to that directory... so no, I do not want to ignore your complaints completely, as you can see.
Aside which YAST is also largely broken.....
Of course, this sentence goes to /dev/null. How about providing _arguments_ rather than rethoric... you'd have no chance if you talk to Bill O'Reilly (Fox News) this way. Facts, please!
BTW - I don't think 7.1 installed the new Firewall or Forwarding tools to deal with iptables..... I'm still investigating.
Of course not. 2.4 is backwards compatible to ipchains, plus default is still 2.2, so why on earth would we update _security_ to a new, untested system?! By the way, the new SuSE Press book on Firewalls is based solely on 2.4 and iptables. Just FYI, it's German only right now, just to show you we know it very well.
And you are free to compile your kernel anytime -- you just loose the ability to get installation support.
Screw that - that is flat out no right of SUSE and is PART of the problem....Changing the oil shouldn't invalidate the agreement... especially when there is a SECURITY HOLE in the 7.0 Kernel
Then get the update from ftp.suse.com (binary kernel). It's fixed there.
And you _don't_ have to compile your own kernels. How about getting the security updates instead?