> 1st off: Adam:- for some bizarre reason, my box booted
> into 2.4.18 this morning, even though 3 reboots still
> took it to 2.2.19 last night. I simply have no idea why.
>
> One question: why do people seem to dislike
> initrd.img's? I'm gonna have to compile a kernel
> anyway cos I got all sorts of unresolved symbols, and
> some of the modules I'd prefer to have compiled in
> anyway.
Not sure why initrd's are disliked other than maybe speed?
Aside: Only yesterday I had to compile and install the latest kernel to get NVIDIA's "non-GPL" kernel to load, but for the chance to run tuxracer faster than 1 frame a second it's worth it!
> For some reason, lilo won't let me boot to my second
> disk. I have a second HD, with a copy of lilo on it
> (from previous installation). I would like the lilo on
> hda1 to boot onto hdb1, but for some reason it won't
> let me do this this morning (it just ignores me-no errors!) my lilo.conf line for it is:
>
> other=/dev/hdb1
> label=Redhat
> alias=2
I just had this same problem yesterday, the trick was to switch the BIOS disk identifiers over(!) Try this
other=/dev/hdb1
label=RedHat
alias=2
map-drive=0x81
to=0x80
map-drive=0x80
to=0x81
> -General Weirdness Section-
>
> Last night, running on my old kernel, I copied the
> kernel source from a CD to my HD. While it did this my
> Xserver hung up until it had finished. The same
> happened when I un-bzipped it. grrr.
>
> Adam suggested it might be a h/w problem, so I booted
> into RH (which can't do *now*, grrr), and quite happily copied 4gigs from one directory to another,
> whilst mucking about with xmms, no lock up. Copied
> the kernel source from CD to ~/ and that was fine,
> unpacked it, fine.
>
> Anyone else experience this?
I had a few problems with a IDE Ultra-2 DMA drive which wouldn't boot after the debian install (halts before INIT), but booting a newer kernel (2.4.17) worked fine. Maybe there's a problem with 2.2.20 and newer ide controllers?
I agree myself that Debian rocks!
Cheers
David.