I don't don't know if this is, properly speaking, security-related... At 9:36 PM 12/4/04, Stefan Proels wrote:
On Saturday 04 December 2004 17:51, Günther J. Niederwimmer wrote:
Hello,
The working 9.0 machine is basically identically configured as the failing one but[...]
have you run lilo ??
No, I'm using grub.
I had a situation a month or two ago where two SuSE 9.0 Pro boxes, virtually identical hardware, far different configurations, had kernel updates applied and one of them failed to boot. The one which failed to boot had a manually selected and extremely minimal (minimal enough to get X running with some basic filesystem and network management apps running, but other than that, minimal) install. I found that either the (grub) menu.lst file had been edited, or else that the unneeded initrd file (present on the other system) had been deleted. I booted from an emergency CD ROM and deleted the reference to the now-missing file, and all is good. There was a message from grub which should have been more of a tipoff than it was in the heat of the moment; I don't recall what it was off the top of my head and I am nowhere near the particular machines in question at the moment. I sent feedback to SuSE about it, but never received a response. -- Fred Morris fredm3047@inwa.net (I-ACK on subject line to reply) ============================================================================== To my knowledge - nothing has been done. you will find that if you "roll your own" kernel, you can apply the source update - but if you have an Adaptec controller, you will get a kernel panic and failure to re-boot. It was a recommended SuSE security update - so I would think that it IS security related ... you won't be able to boot your box afterward...How's that for secure. Apparently Adaptec isn't considered mainstream by SuSE any longer.