In truth the problematic patch for LILO may have been introduced
substantially earlier. Mainly I just ran into something that looks
suspiciously like this bug in 1:22.6.1-9.3
More interesting story in my case, I've got a disk that is acting up
(unsure whether it is merely acting up versus outright dead). The patched
LILO did its thing and was trying to read the MBR of the disk. Due to the
problem, the read fails. It provided an error message suggesting to do
"disk=/dev/sdb inaccessible".
What might actually justify the original grave severity is due to
whichever patch added this feature, LILO was still attempting to read the
MBR of the disk (which then fails and produces the aforementioned error
message).
This is severely problematic since I discovered the disk being
questionable when installing the kernel security update. Thus I was at a
point where I absolutely *MUST* be able to run LILO (otherwise my system
may suddenly be completely unbootable), and the suggested action had no
effect.
Since it seemed like the quickest fix, I tried renaming /dev/sdb so that
LILO wouldn't be able to access it. This also failed, stating that things
disagreed with /proc/partitions. I finally got through this by getting
back to the kernel documentation and making the device disappear via
`echo scsi remove-single-device 0 0 2 0 > /proc/scsi/scsi`, but this
would not have been an option for someone with an IDE disk and only
someone with major experience will know how to do things like this.
--
(\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/)
\BS ( | [EMAIL PROTECTED] PGP 8881EF59 | ) /
\_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/
\___\_|_/82 04 A1 3C C7 B1 37 2A*E3 6E 84 DA 97 4C 40 E6\_|_/___/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
