ahhh so i have a dual boot system and have a question about the lilo.conf. If i make both the old kernel and the new kernel at teh same partition it wont mess anything up will it? ( i think i already know the answer i just wanna be sure) and how exactly could i edit the lilo in sbin (i get encrypted junk when i try to pico it)
thnx for putting up with my newb questions

Hold on a sec,
Your not editing the sbin lilo are you?
Just edit the /etc/lilo.conf.
Then run /sbin/lilo
You should be golden.
And no. you can have both kernels boot from the same partition with no problem, I do it.

# Linux bootable partition config begins
image = /boot/vmlinuz.old
root = /dev/hda1
label = slack.old
read-only

image = /boot/vmlinuz
root = /dev/hda3
label = Linux
read-only
# Linux bootable partition config ends
^ lilo.conf edited



root@linux:/home/wLancer# exec /sbin/lilo
Added Windows *
Fatal: open /boot/vmlinuz.old: No such file or directory
wLancer@linux:~$
^ what i get when i try to run the /sbin/lilo

ack i dont understand what I'm doing wrong

wLancer,
Check my post #293 on this thread to see what my lilo.conf looks like.
Seperate your kernels & map files specifically by name like I have done.
Do not use the default [vmlinuz].
Also as [root] run sbin/lilo like this,
as root: /sbin/lilo
NO preceding comments are necessary.

ahh i see now

thnx for puttin up with me

Ok i feel like the biggest n00b in here. I feel I'm close but just out of reach.
I followed your advice Wolfy on post 293 and it worked. I then proceeded to change the file names and such and lilo is configured properly. only thing is when i click on the new one it still boots to the old kernel. I was perplexed so i fished around and discovered the wrong makefile was in my /usr/src/linux so I changed it and edited it so that it would export the install boot path yadda yadda yadda. but that was no good. posted below is what my new lilo looks like

# Linux bootable partition config begins
image = /boot/vmlinuz-ide-2.4.26
root = /dev/hda3
label = OldSlack
read-only

image = /boot/vmlinuz-2.6.8
root = /dev/hda3
label = Slack
read-only

# Linux bootable partition config ends
Like I said I've renamed all the corresponding files to match the lilo and it still boots to the old kernel. I even reinstalled the new one just to make sure and still nothing.

I know I'm a pain in the rear but I am baffled

wLancer,
When the make file exports the kernel to the boot directory,"for me" it does noes not name it correctly, it calls it just "vmlinuz" I had to change it myself along with the System.map file.
Then I ran [/sbin/lilo] as root.
Whenever you make any kind of change no matter how small, always, I mean always....
update lilo........
You won't break anything if you keep using [/sbin/lilo].
If all else fails rename the problem kernel to .old and recompile and try again following my examples.
The procedure I outline works for me and a few other people I have helped before with this same problem.
Don't lose hope, just be patient, and cross all your T's and dot all your I's.
I'll be here if you still need help.
Wolfy

just a quick question i noticed in the ./ file there is a System.old i was wondering what that was
and in the /boot file when i rename the vmlinuz-2.4.26 to vmlinuz.old it locks the new one. Same with the system.map file

wLancer,
Check to see if those files have sym links to the other files your having problems with.
You may have to do some adjusting so that they only refer to the files you want them too.
Wolfy

odd the vmlinuz.old is a backup file as is the System.old. and vmlinuz-2.6.8 and System.map-2.6.8 are just copies.

wLancer,
Have you tried my examples for naming scheme for your kernels/System.maps?
I'm not 100% sure, but that might help.
Another option is to do some research and ask some other people, as I am no Linux Genius.
I'm trying to help but some things may be beyond me.
Wolfy

A benefit of compiling from scratch is the ability to select your specific architecture to create a kernel specifically tuned for it. I'm confused on how this is done. Does it just default to a i386 kernel on an Intel architecture or does it somehow detect that I have a P4 and would want to do i686

My guess would be that it's selected in the make file with this variable assignment.

This is the line that specifies which architecture the kernel will be compiled for correct? The command uname -m gives me this output "i686" so I'm thinking thats it. However I don't understand the rest of the bit after |. The man page for sed made no sense to me.

This will be my first compile from source and I'm just a little paranoid and trying to make sure I get it all correct.

Also for someone that's already done this am I going to be able to select and install only the parts of the kernel that are necessary to run my hardware specifically, or is that done all automatically?

Here's my 2 cents:
It's a lot easier to create separate directories in /boot so that you never have to deal with the confusion of what files are what. A simple:
mkdir /boot/268
followed by editing the line in the 2.6.8 Makefile that reads:
#export INSTALL_PATH=/boot
to read:
export INSTALL_PATH=/boot/268
solves just about all of your problems, in my experiences at least. When my compile is finished I have three files in /boot/268 and I know exactly what they're for. I then edit /etc/lilo.conf like this for the new kernel:
image = /boot/268/vmlinuz
root = /dev/hdx (x depending on your system)
label = linux-268 (or whatever you like)
read-only

That's really simple and really effective. Just my thoughts.

you kinda missed out 'make bzImage', that kinda caused lots of problems, it needs to acctually make the kernel, and the bootup files, correct me if i'm wrong...still a

I was just referring to the issue of new kernel and associated file placement. Of course you also have to configure and build a new kernel. That's what this thread is about.