If you type: and not you don't have to type because make does that, too.

edit the Makefile and uncomment (i.e. remove the #):
Then when you hit make install the kernel image and system.map will be installed in /boot with the previous kernel image and system.map moved to vmlinuz.old System.old.

Or you can change the destination directory to /test (maybe) and use this until you get the perfect kernel set-up, that way keeping the original working kernel safe.

And about cereal83's 2.6x kernel compile guide.
Well, I wouldn't like to see anyone who is a server maintainer to compile the kernel like that, because it's stupid to remove the previous kernel that worked fine on the last boot.
I would rather listen to cathectic and his method. That way nothing could go wrong.

And if cereal83 again says: What if your new kernel didn't boot?????????????????????????

well....i also use the method outlined by cathectic.
and cereal83 just had a lot of luck, being able to boot every time.

btw.....why did those servers get new kernels ?

egag

You have no backup kernel to boot from should the new kernel not load correctly. Very bad business practice. Mind telling us who this friend works for so we can all avoid the company like the plague?

make bzlilo renames automatically /boot/vmlinuz and /boot/System.map
to /boot/vmlinuz.old and /boot/System.map.old (if they exist)

That requires uncomment the #export INSTALL_PATH=/boot line
in Makefile though

Man, some of you peple are just ignorant! I don't think you people have ever heard of boot disks. Every server has a boot disk incase of a screw up. We never had to use one due to recompling a kernel.

We upgraded the kernel due to it being all new servers. All new servers have 2.6.10 kernel and 2.4.* on older servers and evem 2.2.* kernel on really old servers.

You want to know the name of the guy and the company name? lol lets just say that if your in Canada, you use their service.

It's just luck we have booted after every single recompile? umm no ... there is over 100 servers and none of them have failed. It's not luck, it just works and thats what IT people go with!WITH WHAT WORKS.

I am not telling you fools to compile it this way. I am just saying on how I do it and how this dude do it. I am his assistant to over 100 servers that are mostly all Quad Xeon's or higher and never had a problem yet you people are telling me it's luck and we are doing it wrong. Ever seen a Xeon MP server with 16 cpu's on Slack? I have seen many times and they all work with the way I mentioned.

The only differace from bzimage and bzlilo is bzlilo moves it to / and bzimage doesn't move it.

Yes I know about the makefile thing but that isn't on like 450 like all the guides on this forum tell me it is!

Good day!

I took a moment and searched the OP's posts. Now I understand

He has seen everything but the wind
He has done everything but die
He does it all better, stronger and faster than other mere mortals
We are like the buzzing of flies to him

Tell us more stories about how them "IT people do it" with the quad xeons and magic boot floppies

cereal83 I don't want to offend you, but you should take a rest or drink a beer (you can make that guy who owns so many server to pay it). Most people here are because they needed/need help sometime and want to help others, with questions or answers. I guess most told you about that because it's not common to see make bzlilo, but make or make bzimage are, just don't freak out and answer the difference (the / thingy).
What I really didn't like is calling ignorant a lot of people here because they don't know something. You didn't know how to compile a kernel, they didn't know that bootdisk existed (by the way, a bootdisk is a very generic term... my Windows 98 installation cd is a boot disk, my V2OS floopy is a bootdisk).

thanks a lot.
i'm looking forward to your review on bootdisks.
( as soon people are going to use your kernel-update guide, they will kill for a bootdisk )

in general it's not smart to throw away old shoes before the new ones are proven to be ok.
when you fill in " kernel of productionserver " for shoes, then " not smart " should be changed to stupid.
why take a risk, if there's a simple way to avoid it ?
people told you how to change to a new kernel the safe way, keeping the old kernel as a backup.
if you don't want to use it, that's ok.
but don't tell here that " that's the way that IT people go ".
( btw.: how would you know..... )

" fools" ???
could you give some arguments for that ?
" just saying how you change a kernel " on this forum is asking for comments. ( why else did you post it ? )
and, as with your bad practice of kernel changing , you're lucky again.
there's a lot of good advice for you.

btw.: i'm not very impressed of Slack on a 16 cpu server.
Slack on a i486 with 32 MB ram as a firewall/router demands the same kernel-change procedure.

i hope you'll at least remember this thread when you're fiddling with your bootdisk.

egag

In the tutorial, you forget two points :
- as make bzlilo run /sbin/lilo in its final step, you need to
edit your lilo.conf before make bzlilo

- from my investigation I don't see where it makes modules, so
you may need to make modules after make bzlilo and
make modules_install of course

bzlilo is defined in :
arch/i386/Makefile

and zlilo:
arch/i386/boot/Makefile

I am not a bad person. I just get upset when you people tell me that what my and my boss are doing is wrong when it's obvously works for us. I just thought I would mention this way because it seems easier for me. If the kernel did screw up and it wasn't bootable, we would put a bootdisk in and then recomiple the kernel again and fix what is wrong with it. We can also resort to the old kernel by moving images from the 2.4.* kernel back to the /boot folder.

to run bzlilo you don't have to edit your lilo.conf unless you want a backup of your kernel to be listed. We don't need a backup kernel to be listed so we don't edit it.

I dunno. I guess I shouldn't try to offer new ways of doing things anymore I should just be quiet. I am no linux guru but I can make my way around linux just like I can with windows now.

Well basically just forget what I said in this whole thread because obviously it's wrong even though if your in Canada and use a bank your using our services.

I also never said I had all this money. The company does. I can find something much better to buy then a $250k IBM @server 445s.