On Tue, 10 Apr 2001, [EMAIL PROTECTED] wrote:
> I change the stock kernel in my SuSE 6.4 this morning, and all went all right.
> 
>   Ok, Edgar, you must do the following:
>   - Put the kernel sources in /usr/src.
>   - tar xvfz linux-2.2.18.tar.gz. this create a "linux" folder.

What happens if one already has a linux "folder" as you say.????
Dont forget the "directory" linux is almost certainly a symblolic link to the
kernel version number.
Simply doing what you say overwrites the old sources.

>   - From /usr/src/linux do make menuconfig. don't disable anything, only
> change your proccesor type, enable parallel port support and PC-Style in 
> "General Setup" menu, enable PPP in "Network device support", enable parallel
> printer support in "Character devices" menu, give support like modules or
> "built in" (like you prefer) in "FileSystem" menu and choose your sound car in
> "sound".   - do make dep, make clean, make bzImage, make bzlilo, make
> modules and make modules_install.   - Delete the old files "System.map" and
> "vmlinuz" from /boot directory, put the new files (you must have it in /) in
> /boot, Don't forget do "lilo" from command line, and reboot.

There is no need to delete the old System.map and vmlinuz as 'make bzlilo'
copys then to file.old.
Why "lilo" you already told him to use "make bzlilo" is that not the same
thing.??

>     Please, tell me the result.

I can tell you the result right now, if he makes a mistake in his configuration
and does things like you say, then he will quite possably not be able to boot.

Say for instance he "forgets" to define the needed ext2 filesystem, or
defines it as a module, doing things your way, "bzlilo" does not allow booting
of the "old" kernel.
In other words if one does not have a set of boot/resuce disks handy one is up
the jolly old creek without a paddle, how many times has this been discussed
here on this group.......

Make a new entry in /etc/lilo.conf for the new kernel and leave the old one
bootable as well, that way one can "always" boot the old kernel and have his
system back on line ASAP if the new one fails.

NEVER delete the old kernel BEFORE you KNOW the new one works, period.

> 
>                                                                                      
>            José Luis.


-- 
Regards Richard
[EMAIL PROTECTED]
http://people.zeelandnet.nl/pa3gcu/

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs

Reply via email to