Very Computer

by **Darren Daviso** » Mon, 12 Feb 2001 00:56:04

Hi,

*newbie alert*

I d/loaded and untarred the 2.4.1 kernel to my hdd and ran make config,
make dep, make clean, make bzImage, make modules and make
modules_install. First time I've ever done this so was quite pleased to
see it work.

Backed up my existing /boot/vmlinuz and copied the new bzImage to that
location. Rebooted - all fine, using the 2.4 kernel.

I then realised I had misconfigured something I needed and followed
exactly the same procedure as before, changing my config along the way.
Now, bzImage never gets created - it runs through the procedure, but the
file never appears in arch/i386/boot (or anywhere for that matter).
What have I suddenly done wrong? Will there be a log of errors
somewhere (couldn't find it)?

On a separate note, I tried removing the whole /usr/src/linux directory
so I could start again from the tarball but all I get is 'Cannot unlink
linux: Is a directory' (I am using rm -df ...) has something major gone
wrong?

Regards,
DD

by **Eric P. McC** » Mon, 12 Feb 2001 03:12:44

> I then realised I had misconfigured something I needed and followed
> exactly the same procedure as before, changing my config along the way.
> Now, bzImage never gets created - it runs through the procedure, but the
> file never appears in arch/i386/boot (or anywhere for that matter).
> What have I suddenly done wrong? Will there be a log of errors
> somewhere (couldn't find it)?

Hmm. Did you remember to do `make bzImage' (and not just `make')?

Any errors would be sent to the screen. Since make often has to
unwind through several directories, this can move the actual error
off-screen, so try: `make 2>&1 > log'. Then you can use your favorite
text editor to peruse the file `log'.

Quote:> On a separate note, I tried removing the whole /usr/src/linux directory
> so I could start again from the tarball but all I get is 'Cannot unlink
> linux: Is a directory' (I am using rm -df ...) has something major gone
> wrong?

Use `rm -fr' instead. From the manpage for rm:

-d, --directory
attempt to unlink directory, even if non-empty
(super-user only)

I don't even know how this works, but I'd guess that it may orphan
inodes in the directory (which would be why it's for root only).

--

"Knowing that a lot of people across the world with Geocities sites
absolutely despise me is about the only thing that can add a positive
spin to this situation." - Something Awful, 1/11/2001

by **Darren Daviso** » Mon, 12 Feb 2001 19:03:16

> Hmm. Did you remember to do `make bzImage' (and not just `make')?

yes.

Quote:> Any errors would be sent to the screen. Since make often has to
> unwind through several directories, this can move the actual error
> off-screen, so try: `make 2>&1 > log'. Then you can use your favorite
> text editor to peruse the file `log'.

in some frustration, I gave up and started again from the tarball -
everything worked fine (apart from the fact that there was a problem
with bzImage which means it won't uncompress on boot now, but that's a
different story!)

Thanks for the input,
DD

Very Computer

Kernel recompilation.. wher is bzImage ???

Kernel recompilation.. wher is bzImage ???

Kernel recompilation.. wher is bzImage ???

Kernel recompilation.. wher is bzImage ???