Re: [Sheflug] kernel compile woes....

[Barrie Bremner <nospam [at] barriebremner.com>]

>>>>> "ross" == ross h <ross> writes:

    ross> On Sunday 20 May 2001 17:48, you wrote:
    >> >>>>> "ross" == ross h <ross> writes: Do you still have your
    >> old kernel installed?
    >> 

    ross> yes works fine :-)

That's good.

    >> When you editted /etc/lilo.conf and ran lilo (please tell me
    >> you did) were there any errors?
    >> 

    ross> yes, i did.........no errors

    >> Ah. You didn't remove support for ext2 (or ReiserFS if you're
    >> using that) did you?
    >> 

    ross> ext2..... no. reiserFS was a module with the old kernel so i
    ross> left it as a module even though my main partition is
    ross> reiserfs! thought it was a bit odd but it must be ok like
    ross> this as it gets through a consideralble amount of the boot
    ross> process.

Are all of your partitions ReiserFS?

Check /etc/fstab - it'll give you info.

I'm always inclined to include ext2 since it's the default filesystem
for Linux.
Build filesystems in to the kernel - it's hard to access a filesystem
to get the modules if the kernel knows nothing about the FS it's
trying to get at :-)

    >> Removing PCMCIA and IrDA is fine - as you said - you don't use
    >> them.
    >> 
    >> It might be worth while running through a fresh kernel compile,
    >> so you get the hang of which options are selected by default.
    >> 
    >> Try:
    >> 
    >> cp arch/i386/boot/bzImage /boot/vmlinuz-2.4.4 [or whatever
    >> version it is]

    ross> ahh are you supposed to rename the bzImage vmlinuz then?
    ross> doesn't mention this in the docs (as far as i can see)

    >> cp System.map /boot/System.map-2.4.4
    >> 

    ross> oh... didn't do that (again... the docs with the kernel
    ross> don't mention this)

You call the bzImage whatever you like, as long as you fill the right
details in to lilo.conf, System.map on the other hand, I'm not sure
about.
These are the defaults on mosts system, so I stick with them - saves
me getting creative :-)

    >> edit /etc/lilo.conf
    >> 

    ross> i've got a bit of an odd entry in lilo.conf

    ross> image=/boot/vmlinuz label=linux root=/dev/hdb6
    ross> initrd=/boot/initrd.img read-only

    ross> it's this initrd bit.... i've got no idea what this is? do i
    ross> need it (i guess i do) do i have to make a new file for the
    ross> new kernel?

InitRD - Initial RamDisk - this is used to pre-load modules for
filesystems and/or controllers (RAID controllers, SCSI etc) before
anything else is done.

You don't really need it unless you've got out of the ordinary
hardware, or have a sadistic need to mess about with it :-)

You'll find the default install of some Distros (Redhat certainly)
uses an initrd, but all the systems I've got don't need them.

Cheers.

Baz.

-- 
Barrie J. Bremner 		OpenPGP public key ID: 5164F553
baz [at] barriebremner.com	http://barriebremner.com/

baz /baz/ n.
 1. [common] The third metasyntactic variable.
 2. interj. A term of mild annoyance.
 3. Occasionally appended to foo to produce `foobaz'

	-- Jargon File v4.3.0, www.tuxedo.org/jargon

 4. Me.

---------------------------------------------------------------------
Sheffield Linux User's Group - http://www.sheflug.co.uk
To unsubscribe from this list send mail to
- <sheflug-request [at] vuw.ac.nz> - with the word 
 "unsubscribe" in the body of the message. 

  GNU the choice of a complete generation.