RE: New Kernel Survival Strategies

["Tim Burgess" <tim.burgess@blazie.co.uk>]

Hi,

This sounds like an excellent strategy to me.  Would you be willing to
provide your lilo.conf as a reference for us newbies who have just fallen
foul of getting lilo.conf wrong?

Thanks.

Tim


-----Original Message-----
From: speakup-admin@braille.uwo.ca
[mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
Sent: 02 October 2001 14:53
To: speakup@braille.uwo.ca
Subject: New Kernel Survival Strategies



Well, since we're on the subject of new kernel strategies, I've changed
the subject line.

Now, I'd like to modestly offer my strategy.

Here's what I do:

I have three entries in my lilo.conf, previous, current, and new. These
are the image labels. In my /boot directory, I symlink the appropriate
vmlinuz to previous and current. New is actually symlinked to
/usr/src/linux/arch/i386/boot/bzImage, which does work with my lilo and
bios.

Now, when I gen a new kernel, I have to actively select it during
boot--and I have to specify the speakup synth parm.

Previous is there mainly in case I make a mistake copying a new kernel
into current.

PS: I use several synths on my laptop--including none. Each of these is a
separate entry in lilo.conf pointing to current and differes only on the
append= line, of course.

This has worked very well for me.


On Tue, 2 Oct 2001, Kirk Wood wrote:

> On Tue, 2 Oct 2001, Martin G. McCormick wrote:
> > 	I second the advice to not fear configuring kernels.  The
> > main thing is to first do no harm.  If you have a working kernel,
> > by all means, save it.  .....
>
> Better yet, just leave it just as it is. After you compile your new kernel
> copy/move it to the /boot directory (or partition) and then make another
> entry in lilo.conf for the new kernel. You can copy everything from your
> current (hopefully working) entry changing the label and the name of the
> kernel itself. If this is the only modification, then you can boot back by
> simply doing nothing. If you want to try the new kernel hit the tab key
> right as the computer starts to boot. Then type the label for hte new
> kernel and hit enter.
>
> Things to avoid are believing you need to name your kernel just like the
> one that is there (probably vmlinuz). This is great for making it so that
> anyone can find it. But you can always refer to lilo as well. I name mine
> with a combo of version info and other stuff (such as 2.2.17-music for
> when I configured to use the also drivers). This makes it easy for me to
> tell what was for what. I like to keep multiple kernels arround. If
> something goes goofy in hardware one may be able to get by the problem.
>
> =======
> Kirk Wood
> Cpt.Kirk@1tree.net
>
> "When I take action, I'm not going to fire a $2 million missle at
> a $10 empty tent and hit a camel in the butt. It's going to be decisive."
> 	- President George Bush
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

--

				Janina Sajka, Director
				Technology Research and Development
				Governmental Relations Group
				American Foundation for the Blind (AFB)

Email: janina@afb.net		Phone: (202) 408-8175

Chair, Accessibility SIG
Open Electronic Book Forum (OEBF)
http://www.openebook.org

Will electronic books surpass print books? Read our white paper,
Surpassing Gutenberg, at http://www.afb.org/ebook.asp

Download a free sample Digital Talking Book edition of Martin Luther
King Jr's inspiring "I Have A Dream" speech at
http://www.afb.org/mlkweb.asp

Learn how to make accessible software at
http://www.afb.org/accessapp.asp


_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup