* Re: strange question
@ Martin G. McCormick
` Shaun Oliver
` Kirk Wood
0 siblings, 2 replies; 19+ messages in thread
From: Martin G. McCormick @ UTC (permalink / raw)
To: speakup
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. I am sure we have all had new kernels
that just sat there doing nothing on boot because it either
turned out that that kernel wasn't suitable for our system or
that we made a terrible mistake in configuring it.
I once configured a new kernel for a Dell system that
uses a SCSI bus for the hard drive. I forgot about that because
I also use a Dell system which is very similar to this one only
with an IDE drive. The result was a paper weight of a computer
until I could boot an old kernel and get the system back to life
again.
The biggest problem you will have in setting up kernels,
at times, is finding out enough about your hardware to answer the
questions properly. If you do that, you've taken care of the
worst part of the whole thing.
Right now, I have one kernel that boots perfectly on a
Dell system, but which doesn't work quite right with sound, and
another kernel which works better with sound, but which is
obsolete.
That kind of thing is what you will often-times run in to
in the kernel game.
Martin McCormick WB5AGZ Stillwater, OK
OSU Center for Computing and Information Services Network Operations Group
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: strange question
strange question Martin G. McCormick
@ ` Shaun Oliver
` Kirk Wood
1 sibling, 0 replies; 19+ messages in thread
From: Shaun Oliver @ UTC (permalink / raw)
To: speakup
haveing said that however, it's still daunting for those who've never
configured and compiled a kernel before.
thing is though, you're right. once you've done it and you know enough
about your own system and what to configure for, it gets much easier as
you go on.
remember this though, it's all tryal and error.
more often than not you'll get more errors than you'd like but it's worth
the time u spend swearing and thinking about things. <grin>
--
Shaun
I never made a mistake in my life.
I thought I did once, but I was wrong.
-- Lucy Van Pelt
email: shauno@goanna.net.au
icq: 76958435
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. I am sure we have all had new kernels
> that just sat there doing nothing on boot because it either
> turned out that that kernel wasn't suitable for our system or
> that we made a terrible mistake in configuring it.
>
> I once configured a new kernel for a Dell system that
> uses a SCSI bus for the hard drive. I forgot about that because
> I also use a Dell system which is very similar to this one only
> with an IDE drive. The result was a paper weight of a computer
> until I could boot an old kernel and get the system back to life
> again.
>
> The biggest problem you will have in setting up kernels,
> at times, is finding out enough about your hardware to answer the
> questions properly. If you do that, you've taken care of the
> worst part of the whole thing.
>
> Right now, I have one kernel that boots perfectly on a
> Dell system, but which doesn't work quite right with sound, and
> another kernel which works better with sound, but which is
> obsolete.
>
> That kind of thing is what you will often-times run in to
> in the kernel game.
>
> Martin McCormick WB5AGZ Stillwater, OK
> OSU Center for Computing and Information Services Network Operations Group
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: strange question
strange question Martin G. McCormick
` Shaun Oliver
@ ` Kirk Wood
` New Kernel Survival Strategies Janina Sajka
1 sibling, 1 reply; 19+ messages in thread
From: Kirk Wood @ UTC (permalink / raw)
To: speakup
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
^ permalink raw reply [flat|nested] 19+ messages in thread
* New Kernel Survival Strategies
` Kirk Wood
@ ` Janina Sajka
` Tim Burgess
0 siblings, 1 reply; 19+ messages in thread
From: Janina Sajka @ UTC (permalink / raw)
To: speakup
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
^ permalink raw reply [flat|nested] 19+ messages in thread
* RE: New Kernel Survival Strategies
` New Kernel Survival Strategies Janina Sajka
@ ` Tim Burgess
` Janina Sajka
0 siblings, 1 reply; 19+ messages in thread
From: Tim Burgess @ UTC (permalink / raw)
To: speakup
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
^ permalink raw reply [flat|nested] 19+ messages in thread
* RE: New Kernel Survival Strategies
` Tim Burgess
@ ` Janina Sajka
` Tim Burgess
0 siblings, 1 reply; 19+ messages in thread
From: Janina Sajka @ UTC (permalink / raw)
To: speakup
On Tue, 2 Oct 2001, Tim Burgess wrote:
> 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?
>
No problem. Here it is. Beware, though, that your circumstances may be
different, i.e. lba32, vga=, initrd's, and such things.
The other important survival tool is a bootable floppy disk. Here's my
/etc/lilo.conf:
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
compact
prompt
timeout=500
message=/boot/message
lba32
default=current
serial=0,9600N8
image=/boot/new
label = new
alias = n
vga=0X317
initrd=/boot/initrd.img-new
read-only
root=/dev/hda1
append = "hdc=ide-scsi hde=ide-scsi"
image = /boot/current
label=current
alias = c
vga=0X317
initrd=/boot/initrd.img
read-only
root=/dev/hda1
append = "hdc=ide-scsi hde=ide-scsi"
image = /boot/current
label=express
alias = x
vga=0X317
initrd=/boot/initrd.img
read-only
root=/dev/hda1
append = "speakup_synth=dectlk hdc=ide-scsi hde=ide-scsi"
image = /boot/current
label=litetalk
alias = l
vga=0X317
initrd=/boot/initrd.img
read-only
root=/dev/hda1
append = "speakup_synth=ltlk hdc=ide-scsi hde=ide-scsi"
image = /boot/current
label=bns
alias = b
vga=0X317
initrd=/boot/initrd.img
read-only
root=/dev/hda1
append = "speakup_synth=bns hdc=ide-scsi hde=ide-scsi"
image = /boot/previous
label=previous
alias = p
vga=0X317
initrd=/boot/initrd.img-previous
read-only
root=/dev/hda1
append = "hdc=ide-scsi hde=ide-scsi"
other=/dev/hda3
optional
label=dos
table = /dev/hda
> 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
>
>
> _______________________________________________
> 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
^ permalink raw reply [flat|nested] 19+ messages in thread
* RE: New Kernel Survival Strategies
` Janina Sajka
@ ` Tim Burgess
` Janina Sajka
0 siblings, 1 reply; 19+ messages in thread
From: Tim Burgess @ UTC (permalink / raw)
To: speakup
Hi and thanks.
I'll give it a study and try again - this time I got as far as a successful
compile based on 2.2.18 with SpeakUp 0.10a. However I got a kernel panic
that's killed me and I don't know how to boot back to my /boot/vmlinuz.old
as I messed up lilo.conf. Looks like another rebuild. If it's true that we
learn by our mistakes then I'm going to wind up a real guru at this rate.
Best wishes.
Tim
-----Original Message-----
From: speakup-admin@braille.uwo.ca
[mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
Sent: 02 October 2001 16:49
To: speakup@braille.uwo.ca
Subject: RE: New Kernel Survival Strategies
On Tue, 2 Oct 2001, Tim Burgess wrote:
> 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?
>
No problem. Here it is. Beware, though, that your circumstances may be
different, i.e. lba32, vga=, initrd's, and such things.
The other important survival tool is a bootable floppy disk. Here's my
/etc/lilo.conf:
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
compact
prompt
timeout=500
message=/boot/message
lba32
default=current
serial=0,9600N8
image=/boot/new
label = new
alias = n
vga=0X317
initrd=/boot/initrd.img-new
read-only
root=/dev/hda1
append = "hdc=ide-scsi hde=ide-scsi"
image = /boot/current
label=current
alias = c
vga=0X317
initrd=/boot/initrd.img
read-only
root=/dev/hda1
append = "hdc=ide-scsi hde=ide-scsi"
image = /boot/current
label=express
alias = x
vga=0X317
initrd=/boot/initrd.img
read-only
root=/dev/hda1
append = "speakup_synth=dectlk hdc=ide-scsi hde=ide-scsi"
image = /boot/current
label=litetalk
alias = l
vga=0X317
initrd=/boot/initrd.img
read-only
root=/dev/hda1
append = "speakup_synth=ltlk hdc=ide-scsi hde=ide-scsi"
image = /boot/current
label=bns
alias = b
vga=0X317
initrd=/boot/initrd.img
read-only
root=/dev/hda1
append = "speakup_synth=bns hdc=ide-scsi hde=ide-scsi"
image = /boot/previous
label=previous
alias = p
vga=0X317
initrd=/boot/initrd.img-previous
read-only
root=/dev/hda1
append = "hdc=ide-scsi hde=ide-scsi"
other=/dev/hda3
optional
label=dos
table = /dev/hda
> 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
>
>
> _______________________________________________
> 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
^ permalink raw reply [flat|nested] 19+ messages in thread
* RE: New Kernel Survival Strategies
` Tim Burgess
@ ` Janina Sajka
` Tim Burgess
0 siblings, 1 reply; 19+ messages in thread
From: Janina Sajka @ UTC (permalink / raw)
To: speakup
Hi, Tim:
Best avenue back to your broken linux system may well be a speakup enabled
floppy that can take you into rescue mode. You could do this with the
Redhat installation boot floppies on Bill's site, for example:
vmlinuz -s speakup_synth=ltlk
or perhaps:
vmlinuz rescue speakup_synth=dectlk
Obviously, you would specify the correct synth you have.
If you can get the machine up this way, your lilo.conf can be fixed.
On Tue, 2
Oct 2001, Tim Burgess wrote:
> Hi and thanks.
>
> I'll give it a study and try again - this time I got as far as a successful
> compile based on 2.2.18 with SpeakUp 0.10a. However I got a kernel panic
> that's killed me and I don't know how to boot back to my /boot/vmlinuz.old
> as I messed up lilo.conf. Looks like another rebuild. If it's true that we
> learn by our mistakes then I'm going to wind up a real guru at this rate.
>
> Best wishes.
>
> Tim
>
>
> -----Original Message-----
> From: speakup-admin@braille.uwo.ca
> [mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
> Sent: 02 October 2001 16:49
> To: speakup@braille.uwo.ca
> Subject: RE: New Kernel Survival Strategies
>
>
> On Tue, 2 Oct 2001, Tim Burgess wrote:
>
> > 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?
> >
> No problem. Here it is. Beware, though, that your circumstances may be
> different, i.e. lba32, vga=, initrd's, and such things.
>
> The other important survival tool is a bootable floppy disk. Here's my
> /etc/lilo.conf:
>
> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
> compact
> prompt
> timeout=500
> message=/boot/message
> lba32
> default=current
> serial=0,9600N8
>
> image=/boot/new
> label = new
> alias = n
> vga=0X317
> initrd=/boot/initrd.img-new
> read-only
> root=/dev/hda1
> append = "hdc=ide-scsi hde=ide-scsi"
>
> image = /boot/current
> label=current
> alias = c
> vga=0X317
> initrd=/boot/initrd.img
> read-only
> root=/dev/hda1
> append = "hdc=ide-scsi hde=ide-scsi"
>
> image = /boot/current
> label=express
> alias = x
> vga=0X317
> initrd=/boot/initrd.img
> read-only
> root=/dev/hda1
> append = "speakup_synth=dectlk hdc=ide-scsi hde=ide-scsi"
>
> image = /boot/current
> label=litetalk
> alias = l
> vga=0X317
> initrd=/boot/initrd.img
> read-only
> root=/dev/hda1
> append = "speakup_synth=ltlk hdc=ide-scsi hde=ide-scsi"
>
> image = /boot/current
> label=bns
> alias = b
> vga=0X317
> initrd=/boot/initrd.img
> read-only
> root=/dev/hda1
> append = "speakup_synth=bns hdc=ide-scsi hde=ide-scsi"
>
> image = /boot/previous
> label=previous
> alias = p
> vga=0X317
> initrd=/boot/initrd.img-previous
> read-only
> root=/dev/hda1
> append = "hdc=ide-scsi hde=ide-scsi"
>
> other=/dev/hda3
> optional
> label=dos
>
> table = /dev/hda
>
> > 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
> >
> >
> > _______________________________________________
> > 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
>
>
> _______________________________________________
> 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
^ permalink raw reply [flat|nested] 19+ messages in thread
* RE: New Kernel Survival Strategies
` Janina Sajka
@ ` Tim Burgess
` Janina Sajka
` Frank Carmickle
0 siblings, 2 replies; 19+ messages in thread
From: Tim Burgess @ UTC (permalink / raw)
To: speakup
Hi again,
Do you have the URL for Bill's site and does he have such disks for
Slackware (7.1 in my case)?
Thanks yet again.
Tim
-----Original Message-----
From: speakup-admin@braille.uwo.ca
[mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
Sent: 02 October 2001 18:18
To: speakup@braille.uwo.ca
Subject: RE: New Kernel Survival Strategies
Hi, Tim:
Best avenue back to your broken linux system may well be a speakup enabled
floppy that can take you into rescue mode. You could do this with the
Redhat installation boot floppies on Bill's site, for example:
vmlinuz -s speakup_synth=ltlk
or perhaps:
vmlinuz rescue speakup_synth=dectlk
Obviously, you would specify the correct synth you have.
If you can get the machine up this way, your lilo.conf can be fixed.
On Tue, 2
Oct 2001, Tim Burgess wrote:
> Hi and thanks.
>
> I'll give it a study and try again - this time I got as far as a
successful
> compile based on 2.2.18 with SpeakUp 0.10a. However I got a kernel panic
> that's killed me and I don't know how to boot back to my /boot/vmlinuz.old
> as I messed up lilo.conf. Looks like another rebuild. If it's true that
we
> learn by our mistakes then I'm going to wind up a real guru at this rate.
>
> Best wishes.
>
> Tim
>
>
> -----Original Message-----
> From: speakup-admin@braille.uwo.ca
> [mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
> Sent: 02 October 2001 16:49
> To: speakup@braille.uwo.ca
> Subject: RE: New Kernel Survival Strategies
>
>
> On Tue, 2 Oct 2001, Tim Burgess wrote:
>
> > 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?
> >
> No problem. Here it is. Beware, though, that your circumstances may be
> different, i.e. lba32, vga=, initrd's, and such things.
>
> The other important survival tool is a bootable floppy disk. Here's my
> /etc/lilo.conf:
>
> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
> compact
> prompt
> timeout=500
> message=/boot/message
> lba32
> default=current
> serial=0,9600N8
>
> image=/boot/new
> label = new
> alias = n
> vga=0X317
> initrd=/boot/initrd.img-new
> read-only
> root=/dev/hda1
> append = "hdc=ide-scsi hde=ide-scsi"
>
> image = /boot/current
> label=current
> alias = c
> vga=0X317
> initrd=/boot/initrd.img
> read-only
> root=/dev/hda1
> append = "hdc=ide-scsi hde=ide-scsi"
>
> image = /boot/current
> label=express
> alias = x
> vga=0X317
> initrd=/boot/initrd.img
> read-only
> root=/dev/hda1
> append = "speakup_synth=dectlk hdc=ide-scsi hde=ide-scsi"
>
> image = /boot/current
> label=litetalk
> alias = l
> vga=0X317
> initrd=/boot/initrd.img
> read-only
> root=/dev/hda1
> append = "speakup_synth=ltlk hdc=ide-scsi hde=ide-scsi"
>
> image = /boot/current
> label=bns
> alias = b
> vga=0X317
> initrd=/boot/initrd.img
> read-only
> root=/dev/hda1
> append = "speakup_synth=bns hdc=ide-scsi hde=ide-scsi"
>
> image = /boot/previous
> label=previous
> alias = p
> vga=0X317
> initrd=/boot/initrd.img-previous
> read-only
> root=/dev/hda1
> append = "hdc=ide-scsi hde=ide-scsi"
>
> other=/dev/hda3
> optional
> label=dos
>
> table = /dev/hda
>
> > 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
> >
> >
> > _______________________________________________
> > 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
>
>
> _______________________________________________
> 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
^ permalink raw reply [flat|nested] 19+ messages in thread
* RE: New Kernel Survival Strategies
` Tim Burgess
@ ` Janina Sajka
` Tim Burgess
` Gregory Nowak
` Frank Carmickle
1 sibling, 2 replies; 19+ messages in thread
From: Janina Sajka @ UTC (permalink / raw)
To: speakup
Absolutely, all the way around.
Bill's is an ftp site that you can access via anonymous ftp at
speakup.octothorp.org.
Once there, cd /pub/redhat and further as appropriate. There is indeed a
full Redhat 7.1 installation set. The file you want, and it's path is:
/pub/redhat-7.1/d1/images/boot.img
This is the image for the floppy. If you don't already have it, you will
also need rawrite which is at:
/pub/redhat-7.1/d1/dosimages/rawrite.exe
This is a DOS executable for creating floppies from floppy image files.
NOTE: You may need to kill your screen reader while running rawrite in
order to avoid data corruption on the floppy. It may also be advisable to
run from an actual DOS boot, or a shutdown to MS-DOS as opposed to running
in a DOS window in Windows.
You can safely run your screen reader while answering questions from
rawrite. It will ask you what file you want to use for the image, what
drive to write to, and a third question probably like "press enter when
ready." I don't recall the exact sequence, but it's OK to wait until the
third question to kill speech. That way, you need only press enter and
wait for the floppy to stop spinning.
Good luck, and stay in touch about this. We'll get you up in linux yet!
<grin>
On Tue, 2 Oct 2001, Tim Burgess
wrote:
> Hi again,
>
> Do you have the URL for Bill's site and does he have such disks for
> Slackware (7.1 in my case)?
>
> Thanks yet again.
>
> Tim
>
>
> -----Original Message-----
> From: speakup-admin@braille.uwo.ca
> [mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
> Sent: 02 October 2001 18:18
> To: speakup@braille.uwo.ca
> Subject: RE: New Kernel Survival Strategies
>
>
> Hi, Tim:
>
> Best avenue back to your broken linux system may well be a speakup enabled
> floppy that can take you into rescue mode. You could do this with the
> Redhat installation boot floppies on Bill's site, for example:
>
> vmlinuz -s speakup_synth=ltlk
>
> or perhaps:
>
> vmlinuz rescue speakup_synth=dectlk
>
> Obviously, you would specify the correct synth you have.
>
> If you can get the machine up this way, your lilo.conf can be fixed.
>
> On Tue, 2
> Oct 2001, Tim Burgess wrote:
>
> > Hi and thanks.
> >
> > I'll give it a study and try again - this time I got as far as a
> successful
> > compile based on 2.2.18 with SpeakUp 0.10a. However I got a kernel panic
> > that's killed me and I don't know how to boot back to my /boot/vmlinuz.old
> > as I messed up lilo.conf. Looks like another rebuild. If it's true that
> we
> > learn by our mistakes then I'm going to wind up a real guru at this rate.
> >
> > Best wishes.
> >
> > Tim
> >
> >
> > -----Original Message-----
> > From: speakup-admin@braille.uwo.ca
> > [mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
> > Sent: 02 October 2001 16:49
> > To: speakup@braille.uwo.ca
> > Subject: RE: New Kernel Survival Strategies
> >
> >
> > On Tue, 2 Oct 2001, Tim Burgess wrote:
> >
> > > 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?
> > >
> > No problem. Here it is. Beware, though, that your circumstances may be
> > different, i.e. lba32, vga=, initrd's, and such things.
> >
> > The other important survival tool is a bootable floppy disk. Here's my
> > /etc/lilo.conf:
> >
> > boot=/dev/hda
> > map=/boot/map
> > install=/boot/boot.b
> > compact
> > prompt
> > timeout=500
> > message=/boot/message
> > lba32
> > default=current
> > serial=0,9600N8
> >
> > image=/boot/new
> > label = new
> > alias = n
> > vga=0X317
> > initrd=/boot/initrd.img-new
> > read-only
> > root=/dev/hda1
> > append = "hdc=ide-scsi hde=ide-scsi"
> >
> > image = /boot/current
> > label=current
> > alias = c
> > vga=0X317
> > initrd=/boot/initrd.img
> > read-only
> > root=/dev/hda1
> > append = "hdc=ide-scsi hde=ide-scsi"
> >
> > image = /boot/current
> > label=express
> > alias = x
> > vga=0X317
> > initrd=/boot/initrd.img
> > read-only
> > root=/dev/hda1
> > append = "speakup_synth=dectlk hdc=ide-scsi hde=ide-scsi"
> >
> > image = /boot/current
> > label=litetalk
> > alias = l
> > vga=0X317
> > initrd=/boot/initrd.img
> > read-only
> > root=/dev/hda1
> > append = "speakup_synth=ltlk hdc=ide-scsi hde=ide-scsi"
> >
> > image = /boot/current
> > label=bns
> > alias = b
> > vga=0X317
> > initrd=/boot/initrd.img
> > read-only
> > root=/dev/hda1
> > append = "speakup_synth=bns hdc=ide-scsi hde=ide-scsi"
> >
> > image = /boot/previous
> > label=previous
> > alias = p
> > vga=0X317
> > initrd=/boot/initrd.img-previous
> > read-only
> > root=/dev/hda1
> > append = "hdc=ide-scsi hde=ide-scsi"
> >
> > other=/dev/hda3
> > optional
> > label=dos
> >
> > table = /dev/hda
> >
> > > 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
> > >
> > >
> > > _______________________________________________
> > > 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
> >
> >
> > _______________________________________________
> > 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
>
>
> _______________________________________________
> 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
^ permalink raw reply [flat|nested] 19+ messages in thread
* RE: New Kernel Survival Strategies
` Tim Burgess
` Janina Sajka
@ ` Frank Carmickle
` Janina Sajka
1 sibling, 1 reply; 19+ messages in thread
From: Frank Carmickle @ UTC (permalink / raw)
To: speakup
Hi Tim
slackware7.1 images can be found at
ftp://linux-speakup.org/pub/speakup/disks/slackware/slackware-7.1/
These will have speakup0.09a in them I believe. Just build a new kernel
with the latest cvs speakup when you get the machine back up and running.
On Tue, 2 Oct 2001, Tim Burgess wrote:
> Hi again,
>
> Do you have the URL for Bill's site and does he have such disks for
> Slackware (7.1 in my case)?
--
Frank Carmickle
phone: 412 761-9568
email: frankiec@dryrose.com
^ permalink raw reply [flat|nested] 19+ messages in thread
* RE: New Kernel Survival Strategies
` Frank Carmickle
@ ` Janina Sajka
` Tim Burgess
0 siblings, 1 reply; 19+ messages in thread
From: Janina Sajka @ UTC (permalink / raw)
To: speakup
Ooopps. Missed that Tim has Slack and not Redhat. Though the Redhat floppy
should still get him into rescue mode!
On Tue, 2 Oct 2001, Frank Carmickle wrote:
> Hi Tim
>
> slackware7.1 images can be found at
> ftp://linux-speakup.org/pub/speakup/disks/slackware/slackware-7.1/
> These will have speakup0.09a in them I believe. Just build a new kernel
> with the latest cvs speakup when you get the machine back up and running.
>
> On Tue, 2 Oct 2001, Tim Burgess wrote:
>
> > Hi again,
> >
> > Do you have the URL for Bill's site and does he have such disks for
> > Slackware (7.1 in my case)?
>
>
--
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
^ permalink raw reply [flat|nested] 19+ messages in thread
* RE: New Kernel Survival Strategies
` Janina Sajka
@ ` Tim Burgess
0 siblings, 0 replies; 19+ messages in thread
From: Tim Burgess @ UTC (permalink / raw)
To: speakup
Hi,
No problem - I'm game for trying it with a RedHat image. I've just created
the disk and I'll get back to you when I've tried it out.
Cheers.
Tim
-----Original Message-----
From: speakup-admin@braille.uwo.ca
[mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
Sent: 02 October 2001 19:55
To: speakup@braille.uwo.ca
Subject: RE: New Kernel Survival Strategies
Ooopps. Missed that Tim has Slack and not Redhat. Though the Redhat floppy
should still get him into rescue mode!
On Tue, 2 Oct 2001, Frank Carmickle wrote:
> Hi Tim
>
> slackware7.1 images can be found at
> ftp://linux-speakup.org/pub/speakup/disks/slackware/slackware-7.1/
> These will have speakup0.09a in them I believe. Just build a new kernel
> with the latest cvs speakup when you get the machine back up and running.
>
> On Tue, 2 Oct 2001, Tim Burgess wrote:
>
> > Hi again,
> >
> > Do you have the URL for Bill's site and does he have such disks for
> > Slackware (7.1 in my case)?
>
>
--
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
^ permalink raw reply [flat|nested] 19+ messages in thread
* RE: New Kernel Survival Strategies
` Janina Sajka
@ ` Tim Burgess
` Janina Sajka
` Gregory Nowak
` Gregory Nowak
1 sibling, 2 replies; 19+ messages in thread
From: Tim Burgess @ UTC (permalink / raw)
To: speakup
Hi,
I booted from the boot disk generated at the end of the Slackware
installation procedure and got access back right away. I've restored my
original 2.2.16 vmlinuz and System.map, so all I need to do now is generate
a working 2.2.18 kernel. Since my last attempt compiled and then gave a
kernel panic the following questions spring to mind:
1 - When I'm booting a new kernel, can I redirect the screen output to a
file so that I can review the messages generated (including any panics) to
aid my trouble-shooting?
2 - Once I've got a good (booting) 2.2.18, how do I update my wonderful boot
disk (or create a new one)?
Sorry to be a pain, but I promise I'll keep plugging at it until I
understand this stuff and then I'll take my turn at helping others who are
starting out. I'm saving all of the messages and I'll be using them to
create a guide for new blinux-types on my up-coming web site.
Tim
-----Original Message-----
From: speakup-admin@braille.uwo.ca
[mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
Sent: 02 October 2001 19:17
To: speakup@braille.uwo.ca
Subject: RE: New Kernel Survival Strategies
Absolutely, all the way around.
Bill's is an ftp site that you can access via anonymous
ftp at
ftp://speakup.octothorp.org.
Once there, cd /pub/redhat and further as appropriate. There is indeed a
full Redhat 7.1 installation set. The file you want, and it's path is:
/pub/redhat-7.1/d1/images/boot.img
This is the image for the floppy. If you don't already have it, you will
also need rawrite which is at:
/pub/redhat-7.1/d1/dosimages/rawrite.exe
This is a DOS executable for creating floppies from floppy image files.
NOTE: You may need to kill your screen reader while running rawrite in
order to avoid data corruption on the floppy. It may also be advisable to
run from an actual DOS boot, or a shutdown to MS-DOS as opposed to running
in a DOS window in Windows.
You can safely run your screen reader while answering questions from
rawrite. It will ask you what file you want to use for the image, what
drive to write to, and a third question probably like "press enter when
ready." I don't recall the exact sequence, but it's OK to wait until the
third question to kill speech. That way, you need only press enter and
wait for the floppy to stop spinning.
Good luck, and stay in touch about this. We'll get you up in linux yet!
<grin>
On Tue, 2 Oct 2001, Tim Burgess
wrote:
> Hi again,
>
> Do you have the URL for Bill's site and does he have such disks for
> Slackware (7.1 in my case)?
>
> Thanks yet again.
>
> Tim
>
>
> -----Original Message-----
> From: speakup-admin@braille.uwo.ca
> [mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
> Sent: 02 October 2001 18:18
> To: speakup@braille.uwo.ca
> Subject: RE: New Kernel Survival Strategies
>
>
> Hi, Tim:
>
> Best avenue back to your broken linux system may well be a speakup enabled
> floppy that can take you into rescue mode. You could do this with the
> Redhat installation boot floppies on Bill's site, for example:
>
> vmlinuz -s speakup_synth=ltlk
>
> or perhaps:
>
> vmlinuz rescue speakup_synth=dectlk
>
> Obviously, you would specify the correct synth you have.
>
> If you can get the machine up this way, your lilo.conf can be fixed.
>
> On Tue, 2
> Oct 2001, Tim Burgess wrote:
>
> > Hi and thanks.
> >
> > I'll give it a study and try again - this time I got as far as a
> successful
> > compile based on 2.2.18 with SpeakUp 0.10a. However I got a kernel
panic
> > that's killed me and I don't know how to boot back to my
/boot/vmlinuz.old
> > as I messed up lilo.conf. Looks like another rebuild. If it's true
that
> we
> > learn by our mistakes then I'm going to wind up a real guru at this
rate.
> >
> > Best wishes.
> >
> > Tim
> >
> >
> > -----Original Message-----
> > From: speakup-admin@braille.uwo.ca
> > [mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
> > Sent: 02 October 2001 16:49
> > To: speakup@braille.uwo.ca
> > Subject: RE: New Kernel Survival Strategies
> >
> >
> > On Tue, 2 Oct 2001, Tim Burgess wrote:
> >
> > > 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?
> > >
> > No problem. Here it is. Beware, though, that your circumstances may be
> > different, i.e. lba32, vga=, initrd's, and such things.
> >
> > The other important survival tool is a bootable floppy disk. Here's my
> > /etc/lilo.conf:
> >
> > boot=/dev/hda
> > map=/boot/map
> > install=/boot/boot.b
> > compact
> > prompt
> > timeout=500
> > message=/boot/message
> > lba32
> > default=current
> > serial=0,9600N8
> >
> > image=/boot/new
> > label = new
> > alias = n
> > vga=0X317
> > initrd=/boot/initrd.img-new
> > read-only
> > root=/dev/hda1
> > append = "hdc=ide-scsi hde=ide-scsi"
> >
> > image = /boot/current
> > label=current
> > alias = c
> > vga=0X317
> > initrd=/boot/initrd.img
> > read-only
> > root=/dev/hda1
> > append = "hdc=ide-scsi hde=ide-scsi"
> >
> > image = /boot/current
> > label=express
> > alias = x
> > vga=0X317
> > initrd=/boot/initrd.img
> > read-only
> > root=/dev/hda1
> > append = "speakup_synth=dectlk hdc=ide-scsi hde=ide-scsi"
> >
> > image = /boot/current
> > label=litetalk
> > alias = l
> > vga=0X317
> > initrd=/boot/initrd.img
> > read-only
> > root=/dev/hda1
> > append = "speakup_synth=ltlk hdc=ide-scsi hde=ide-scsi"
> >
> > image = /boot/current
> > label=bns
> > alias = b
> > vga=0X317
> > initrd=/boot/initrd.img
> > read-only
> > root=/dev/hda1
> > append = "speakup_synth=bns hdc=ide-scsi hde=ide-scsi"
> >
> > image = /boot/previous
> > label=previous
> > alias = p
> > vga=0X317
> > initrd=/boot/initrd.img-previous
> > read-only
> > root=/dev/hda1
> > append = "hdc=ide-scsi hde=ide-scsi"
> >
> > other=/dev/hda3
> > optional
> > label=dos
> >
> > table = /dev/hda
> >
> > > 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
> > >
> > >
> > > _______________________________________________
> > > 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
> >
> >
> > _______________________________________________
> > 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
>
>
> _______________________________________________
> 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
^ permalink raw reply [flat|nested] 19+ messages in thread
* RE: New Kernel Survival Strategies
` Tim Burgess
@ ` Janina Sajka
` Tim Burgess
` Gregory Nowak
1 sibling, 1 reply; 19+ messages in thread
From: Janina Sajka @ UTC (permalink / raw)
To: speakup
Hi, Tim:
Congrats on getting the linux box back!
On Tue, 2 Oct 2001, Tim Burgess wrote:
> I booted from the boot disk generated at the end of the Slackware
> installation procedure and got access back right away.
Right on. That's exactly what it's for. I like to call it the "get out of
jail free disk."
<<<snip snip>>>
> 1 - When I'm booting a new kernel, can I redirect the screen output to a
> file so that I can review the messages generated (including any panics) to
> aid my trouble-shooting?
We have a spaghetti sauce here in the States that has a commercial which
uses the phrase:
"It's already in there."
So, Tim, take a look at /var/log and have at all the logs you need.
They're already in there.
> 2 - Once I've got a good (booting) 2.2.18, how do I update my wonderful boot
> disk (or create a new one)?
>
Well, don't know about slackware, but on Redhat there's a script:
mkbootdisk
PS: I don't think you're a pain at all.
Janina
> Sorry to be a pain, but I promise I'll keep plugging at it until I
> understand this stuff and then I'll take my turn at helping others who are
> starting out. I'm saving all of the messages and I'll be using them to
> create a guide for new blinux-types on my up-coming web site.
>
> Tim
>
>
> -----Original Message-----
> From: speakup-admin@braille.uwo.ca
> [mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
> Sent: 02 October 2001 19:17
> To: speakup@braille.uwo.ca
> Subject: RE: New Kernel Survival Strategies
>
>
> Absolutely, all the way around.
>
> Bill's is an ftp site that you can access via anonymous
> ftp at
> ftp://speakup.octothorp.org.
>
> Once there, cd /pub/redhat and further as appropriate. There is indeed a
> full Redhat 7.1 installation set. The file you want, and it's path is:
>
> /pub/redhat-7.1/d1/images/boot.img
>
> This is the image for the floppy. If you don't already have it, you will
> also need rawrite which is at:
>
> /pub/redhat-7.1/d1/dosimages/rawrite.exe
>
> This is a DOS executable for creating floppies from floppy image files.
>
> NOTE: You may need to kill your screen reader while running rawrite in
> order to avoid data corruption on the floppy. It may also be advisable to
> run from an actual DOS boot, or a shutdown to MS-DOS as opposed to running
> in a DOS window in Windows.
>
> You can safely run your screen reader while answering questions from
> rawrite. It will ask you what file you want to use for the image, what
> drive to write to, and a third question probably like "press enter when
> ready." I don't recall the exact sequence, but it's OK to wait until the
> third question to kill speech. That way, you need only press enter and
> wait for the floppy to stop spinning.
>
> Good luck, and stay in touch about this. We'll get you up in linux yet!
> <grin>
> On Tue, 2 Oct 2001, Tim Burgess
> wrote:
>
> > Hi again,
> >
> > Do you have the URL for Bill's site and does he have such disks for
> > Slackware (7.1 in my case)?
> >
> > Thanks yet again.
> >
> > Tim
> >
> >
> > -----Original Message-----
> > From: speakup-admin@braille.uwo.ca
> > [mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
> > Sent: 02 October 2001 18:18
> > To: speakup@braille.uwo.ca
> > Subject: RE: New Kernel Survival Strategies
> >
> >
> > Hi, Tim:
> >
> > Best avenue back to your broken linux system may well be a speakup enabled
> > floppy that can take you into rescue mode. You could do this with the
> > Redhat installation boot floppies on Bill's site, for example:
> >
> > vmlinuz -s speakup_synth=ltlk
> >
> > or perhaps:
> >
> > vmlinuz rescue speakup_synth=dectlk
> >
> > Obviously, you would specify the correct synth you have.
> >
> > If you can get the machine up this way, your lilo.conf can be fixed.
> >
> > On Tue, 2
> > Oct 2001, Tim Burgess wrote:
> >
> > > Hi and thanks.
> > >
> > > I'll give it a study and try again - this time I got as far as a
> > successful
> > > compile based on 2.2.18 with SpeakUp 0.10a. However I got a kernel
> panic
> > > that's killed me and I don't know how to boot back to my
> /boot/vmlinuz.old
> > > as I messed up lilo.conf. Looks like another rebuild. If it's true
> that
> > we
> > > learn by our mistakes then I'm going to wind up a real guru at this
> rate.
> > >
> > > Best wishes.
> > >
> > > Tim
> > >
> > >
> > > -----Original Message-----
> > > From: speakup-admin@braille.uwo.ca
> > > [mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
> > > Sent: 02 October 2001 16:49
> > > To: speakup@braille.uwo.ca
> > > Subject: RE: New Kernel Survival Strategies
> > >
> > >
> > > On Tue, 2 Oct 2001, Tim Burgess wrote:
> > >
> > > > 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?
> > > >
> > > No problem. Here it is. Beware, though, that your circumstances may be
> > > different, i.e. lba32, vga=, initrd's, and such things.
> > >
> > > The other important survival tool is a bootable floppy disk. Here's my
> > > /etc/lilo.conf:
> > >
> > > boot=/dev/hda
> > > map=/boot/map
> > > install=/boot/boot.b
> > > compact
> > > prompt
> > > timeout=500
> > > message=/boot/message
> > > lba32
> > > default=current
> > > serial=0,9600N8
> > >
> > > image=/boot/new
> > > label = new
> > > alias = n
> > > vga=0X317
> > > initrd=/boot/initrd.img-new
> > > read-only
> > > root=/dev/hda1
> > > append = "hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/current
> > > label=current
> > > alias = c
> > > vga=0X317
> > > initrd=/boot/initrd.img
> > > read-only
> > > root=/dev/hda1
> > > append = "hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/current
> > > label=express
> > > alias = x
> > > vga=0X317
> > > initrd=/boot/initrd.img
> > > read-only
> > > root=/dev/hda1
> > > append = "speakup_synth=dectlk hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/current
> > > label=litetalk
> > > alias = l
> > > vga=0X317
> > > initrd=/boot/initrd.img
> > > read-only
> > > root=/dev/hda1
> > > append = "speakup_synth=ltlk hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/current
> > > label=bns
> > > alias = b
> > > vga=0X317
> > > initrd=/boot/initrd.img
> > > read-only
> > > root=/dev/hda1
> > > append = "speakup_synth=bns hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/previous
> > > label=previous
> > > alias = p
> > > vga=0X317
> > > initrd=/boot/initrd.img-previous
> > > read-only
> > > root=/dev/hda1
> > > append = "hdc=ide-scsi hde=ide-scsi"
> > >
> > > other=/dev/hda3
> > > optional
> > > label=dos
> > >
> > > table = /dev/hda
> > >
> > > > 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
> > > >
> > > >
> > > > _______________________________________________
> > > > 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
> > >
> > >
> > > _______________________________________________
> > > 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
> >
> >
> > _______________________________________________
> > 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
>
>
> _______________________________________________
> 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
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: New Kernel Survival Strategies
` Janina Sajka
` Tim Burgess
@ ` Gregory Nowak
1 sibling, 0 replies; 19+ messages in thread
From: Gregory Nowak @ UTC (permalink / raw)
To: speakup
I believe Tim asked for Slackware, not Redhat.
Greg
On Tue, Oct 02, 2001 at 02:17:27PM -0400, Janina Sajka wrote:
> Absolutely, all the way around.
>
> Bill's is an ftp site that you can access via anonymous ftp at
> speakup.octothorp.org.
>
> Once there, cd /pub/redhat and further as appropriate. There is indeed a
> full Redhat 7.1 installation set. The file you want, and it's path is:
>
> /pub/redhat-7.1/d1/images/boot.img
>
> This is the image for the floppy. If you don't already have it, you will
> also need rawrite which is at:
>
> /pub/redhat-7.1/d1/dosimages/rawrite.exe
>
> This is a DOS executable for creating floppies from floppy image files.
>
> NOTE: You may need to kill your screen reader while running rawrite in
> order to avoid data corruption on the floppy. It may also be advisable to
> run from an actual DOS boot, or a shutdown to MS-DOS as opposed to running
> in a DOS window in Windows.
>
> You can safely run your screen reader while answering questions from
> rawrite. It will ask you what file you want to use for the image, what
> drive to write to, and a third question probably like "press enter when
> ready." I don't recall the exact sequence, but it's OK to wait until the
> third question to kill speech. That way, you need only press enter and
> wait for the floppy to stop spinning.
>
> Good luck, and stay in touch about this. We'll get you up in linux yet!
> <grin>
> On Tue, 2 Oct 2001, Tim Burgess
> wrote:
>
> > Hi again,
> >
> > Do you have the URL for Bill's site and does he have such disks for
> > Slackware (7.1 in my case)?
> >
> > Thanks yet again.
> >
> > Tim
> >
> >
> > -----Original Message-----
> > From: speakup-admin@braille.uwo.ca
> > [mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
> > Sent: 02 October 2001 18:18
> > To: speakup@braille.uwo.ca
> > Subject: RE: New Kernel Survival Strategies
> >
> >
> > Hi, Tim:
> >
> > Best avenue back to your broken linux system may well be a speakup enabled
> > floppy that can take you into rescue mode. You could do this with the
> > Redhat installation boot floppies on Bill's site, for example:
> >
> > vmlinuz -s speakup_synth=ltlk
> >
> > or perhaps:
> >
> > vmlinuz rescue speakup_synth=dectlk
> >
> > Obviously, you would specify the correct synth you have.
> >
> > If you can get the machine up this way, your lilo.conf can be fixed.
> >
> > On Tue, 2
> > Oct 2001, Tim Burgess wrote:
> >
> > > Hi and thanks.
> > >
> > > I'll give it a study and try again - this time I got as far as a
> > successful
> > > compile based on 2.2.18 with SpeakUp 0.10a. However I got a kernel panic
> > > that's killed me and I don't know how to boot back to my /boot/vmlinuz.old
> > > as I messed up lilo.conf. Looks like another rebuild. If it's true that
> > we
> > > learn by our mistakes then I'm going to wind up a real guru at this rate.
> > >
> > > Best wishes.
> > >
> > > Tim
> > >
> > >
> > > -----Original Message-----
> > > From: speakup-admin@braille.uwo.ca
> > > [mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
> > > Sent: 02 October 2001 16:49
> > > To: speakup@braille.uwo.ca
> > > Subject: RE: New Kernel Survival Strategies
> > >
> > >
> > > On Tue, 2 Oct 2001, Tim Burgess wrote:
> > >
> > > > 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?
> > > >
> > > No problem. Here it is. Beware, though, that your circumstances may be
> > > different, i.e. lba32, vga=, initrd's, and such things.
> > >
> > > The other important survival tool is a bootable floppy disk. Here's my
> > > /etc/lilo.conf:
> > >
> > > boot=/dev/hda
> > > map=/boot/map
> > > install=/boot/boot.b
> > > compact
> > > prompt
> > > timeout=500
> > > message=/boot/message
> > > lba32
> > > default=current
> > > serial=0,9600N8
> > >
> > > image=/boot/new
> > > label = new
> > > alias = n
> > > vga=0X317
> > > initrd=/boot/initrd.img-new
> > > read-only
> > > root=/dev/hda1
> > > append = "hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/current
> > > label=current
> > > alias = c
> > > vga=0X317
> > > initrd=/boot/initrd.img
> > > read-only
> > > root=/dev/hda1
> > > append = "hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/current
> > > label=express
> > > alias = x
> > > vga=0X317
> > > initrd=/boot/initrd.img
> > > read-only
> > > root=/dev/hda1
> > > append = "speakup_synth=dectlk hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/current
> > > label=litetalk
> > > alias = l
> > > vga=0X317
> > > initrd=/boot/initrd.img
> > > read-only
> > > root=/dev/hda1
> > > append = "speakup_synth=ltlk hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/current
> > > label=bns
> > > alias = b
> > > vga=0X317
> > > initrd=/boot/initrd.img
> > > read-only
> > > root=/dev/hda1
> > > append = "speakup_synth=bns hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/previous
> > > label=previous
> > > alias = p
> > > vga=0X317
> > > initrd=/boot/initrd.img-previous
> > > read-only
> > > root=/dev/hda1
> > > append = "hdc=ide-scsi hde=ide-scsi"
> > >
> > > other=/dev/hda3
> > > optional
> > > label=dos
> > >
> > > table = /dev/hda
> > >
> > > > 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
> > > >
> > > >
> > > > _______________________________________________
> > > > 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
> > >
> > >
> > > _______________________________________________
> > > 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
> >
> >
> > _______________________________________________
> > 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
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: New Kernel Survival Strategies
` Tim Burgess
` Janina Sajka
@ ` Gregory Nowak
` Tim Burgess
1 sibling, 1 reply; 19+ messages in thread
From: Gregory Nowak @ UTC (permalink / raw)
To: speakup
Updating/creating a boot disk with slackware is done
with the makebootdisk utility.
Greg
On Tue, Oct 02, 2001 at 10:10:39PM +0100, Tim Burgess wrote:
> Hi,
>
> I booted from the boot disk generated at the end of the Slackware
> installation procedure and got access back right away. I've restored my
> original 2.2.16 vmlinuz and System.map, so all I need to do now is generate
> a working 2.2.18 kernel. Since my last attempt compiled and then gave a
> kernel panic the following questions spring to mind:
>
> 1 - When I'm booting a new kernel, can I redirect the screen output to a
> file so that I can review the messages generated (including any panics) to
> aid my trouble-shooting?
>
> 2 - Once I've got a good (booting) 2.2.18, how do I update my wonderful boot
> disk (or create a new one)?
>
> Sorry to be a pain, but I promise I'll keep plugging at it until I
> understand this stuff and then I'll take my turn at helping others who are
> starting out. I'm saving all of the messages and I'll be using them to
> create a guide for new blinux-types on my up-coming web site.
>
> Tim
>
>
> -----Original Message-----
> From: speakup-admin@braille.uwo.ca
> [mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
> Sent: 02 October 2001 19:17
> To: speakup@braille.uwo.ca
> Subject: RE: New Kernel Survival Strategies
>
>
> Absolutely, all the way around.
>
> Bill's is an ftp site that you can access via anonymous
> ftp at
> ftp://speakup.octothorp.org.
>
> Once there, cd /pub/redhat and further as appropriate. There is indeed a
> full Redhat 7.1 installation set. The file you want, and it's path is:
>
> /pub/redhat-7.1/d1/images/boot.img
>
> This is the image for the floppy. If you don't already have it, you will
> also need rawrite which is at:
>
> /pub/redhat-7.1/d1/dosimages/rawrite.exe
>
> This is a DOS executable for creating floppies from floppy image files.
>
> NOTE: You may need to kill your screen reader while running rawrite in
> order to avoid data corruption on the floppy. It may also be advisable to
> run from an actual DOS boot, or a shutdown to MS-DOS as opposed to running
> in a DOS window in Windows.
>
> You can safely run your screen reader while answering questions from
> rawrite. It will ask you what file you want to use for the image, what
> drive to write to, and a third question probably like "press enter when
> ready." I don't recall the exact sequence, but it's OK to wait until the
> third question to kill speech. That way, you need only press enter and
> wait for the floppy to stop spinning.
>
> Good luck, and stay in touch about this. We'll get you up in linux yet!
> <grin>
> On Tue, 2 Oct 2001, Tim Burgess
> wrote:
>
> > Hi again,
> >
> > Do you have the URL for Bill's site and does he have such disks for
> > Slackware (7.1 in my case)?
> >
> > Thanks yet again.
> >
> > Tim
> >
> >
> > -----Original Message-----
> > From: speakup-admin@braille.uwo.ca
> > [mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
> > Sent: 02 October 2001 18:18
> > To: speakup@braille.uwo.ca
> > Subject: RE: New Kernel Survival Strategies
> >
> >
> > Hi, Tim:
> >
> > Best avenue back to your broken linux system may well be a speakup enabled
> > floppy that can take you into rescue mode. You could do this with the
> > Redhat installation boot floppies on Bill's site, for example:
> >
> > vmlinuz -s speakup_synth=ltlk
> >
> > or perhaps:
> >
> > vmlinuz rescue speakup_synth=dectlk
> >
> > Obviously, you would specify the correct synth you have.
> >
> > If you can get the machine up this way, your lilo.conf can be fixed.
> >
> > On Tue, 2
> > Oct 2001, Tim Burgess wrote:
> >
> > > Hi and thanks.
> > >
> > > I'll give it a study and try again - this time I got as far as a
> > successful
> > > compile based on 2.2.18 with SpeakUp 0.10a. However I got a kernel
> panic
> > > that's killed me and I don't know how to boot back to my
> /boot/vmlinuz.old
> > > as I messed up lilo.conf. Looks like another rebuild. If it's true
> that
> > we
> > > learn by our mistakes then I'm going to wind up a real guru at this
> rate.
> > >
> > > Best wishes.
> > >
> > > Tim
> > >
> > >
> > > -----Original Message-----
> > > From: speakup-admin@braille.uwo.ca
> > > [mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
> > > Sent: 02 October 2001 16:49
> > > To: speakup@braille.uwo.ca
> > > Subject: RE: New Kernel Survival Strategies
> > >
> > >
> > > On Tue, 2 Oct 2001, Tim Burgess wrote:
> > >
> > > > 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?
> > > >
> > > No problem. Here it is. Beware, though, that your circumstances may be
> > > different, i.e. lba32, vga=, initrd's, and such things.
> > >
> > > The other important survival tool is a bootable floppy disk. Here's my
> > > /etc/lilo.conf:
> > >
> > > boot=/dev/hda
> > > map=/boot/map
> > > install=/boot/boot.b
> > > compact
> > > prompt
> > > timeout=500
> > > message=/boot/message
> > > lba32
> > > default=current
> > > serial=0,9600N8
> > >
> > > image=/boot/new
> > > label = new
> > > alias = n
> > > vga=0X317
> > > initrd=/boot/initrd.img-new
> > > read-only
> > > root=/dev/hda1
> > > append = "hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/current
> > > label=current
> > > alias = c
> > > vga=0X317
> > > initrd=/boot/initrd.img
> > > read-only
> > > root=/dev/hda1
> > > append = "hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/current
> > > label=express
> > > alias = x
> > > vga=0X317
> > > initrd=/boot/initrd.img
> > > read-only
> > > root=/dev/hda1
> > > append = "speakup_synth=dectlk hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/current
> > > label=litetalk
> > > alias = l
> > > vga=0X317
> > > initrd=/boot/initrd.img
> > > read-only
> > > root=/dev/hda1
> > > append = "speakup_synth=ltlk hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/current
> > > label=bns
> > > alias = b
> > > vga=0X317
> > > initrd=/boot/initrd.img
> > > read-only
> > > root=/dev/hda1
> > > append = "speakup_synth=bns hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/previous
> > > label=previous
> > > alias = p
> > > vga=0X317
> > > initrd=/boot/initrd.img-previous
> > > read-only
> > > root=/dev/hda1
> > > append = "hdc=ide-scsi hde=ide-scsi"
> > >
> > > other=/dev/hda3
> > > optional
> > > label=dos
> > >
> > > table = /dev/hda
> > >
> > > > 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
> > > >
> > > >
> > > > _______________________________________________
> > > > 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
> > >
> > >
> > > _______________________________________________
> > > 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
> >
> >
> > _______________________________________________
> > 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
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
^ permalink raw reply [flat|nested] 19+ messages in thread
* RE: New Kernel Survival Strategies
` Gregory Nowak
@ ` Tim Burgess
0 siblings, 0 replies; 19+ messages in thread
From: Tim Burgess @ UTC (permalink / raw)
To: speakup
Thanks Greg,
When I get a kernel worth the processing, I'll use the command!
Cheers.
Tim
-----Original Message-----
From: speakup-admin@braille.uwo.ca
[mailto:speakup-admin@braille.uwo.ca]On Behalf Of Gregory Nowak
Sent: 03 October 2001 01:33
To: speakup@braille.uwo.ca
Subject: Re: New Kernel Survival Strategies
Updating/creating a boot disk with slackware is done
with the makebootdisk utility.
Greg
On Tue, Oct 02, 2001 at 10:10:39PM +0100, Tim Burgess wrote:
> Hi,
>
> I booted from the boot disk generated at the end of the Slackware
> installation procedure and got access back right away. I've restored my
> original 2.2.16 vmlinuz and System.map, so all I need to do now is
generate
> a working 2.2.18 kernel. Since my last attempt compiled and then gave a
> kernel panic the following questions spring to mind:
>
> 1 - When I'm booting a new kernel, can I redirect the screen output to a
> file so that I can review the messages generated (including any panics) to
> aid my trouble-shooting?
>
> 2 - Once I've got a good (booting) 2.2.18, how do I update my wonderful
boot
> disk (or create a new one)?
>
> Sorry to be a pain, but I promise I'll keep plugging at it until I
> understand this stuff and then I'll take my turn at helping others who are
> starting out. I'm saving all of the messages and I'll be using them to
> create a guide for new blinux-types on my up-coming web site.
>
> Tim
>
>
> -----Original Message-----
> From: speakup-admin@braille.uwo.ca
> [mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
> Sent: 02 October 2001 19:17
> To: speakup@braille.uwo.ca
> Subject: RE: New Kernel Survival Strategies
>
>
> Absolutely, all the way around.
>
> Bill's is an ftp site that you can access via anonymous
> ftp at
> ftp://speakup.octothorp.org.
>
> Once there, cd /pub/redhat and further as appropriate. There is indeed a
> full Redhat 7.1 installation set. The file you want, and it's path is:
>
> /pub/redhat-7.1/d1/images/boot.img
>
> This is the image for the floppy. If you don't already have it, you will
> also need rawrite which is at:
>
> /pub/redhat-7.1/d1/dosimages/rawrite.exe
>
> This is a DOS executable for creating floppies from floppy image files.
>
> NOTE: You may need to kill your screen reader while running rawrite in
> order to avoid data corruption on the floppy. It may also be advisable to
> run from an actual DOS boot, or a shutdown to MS-DOS as opposed to running
> in a DOS window in Windows.
>
> You can safely run your screen reader while answering questions from
> rawrite. It will ask you what file you want to use for the image, what
> drive to write to, and a third question probably like "press enter when
> ready." I don't recall the exact sequence, but it's OK to wait until the
> third question to kill speech. That way, you need only press enter and
> wait for the floppy to stop spinning.
>
> Good luck, and stay in touch about this. We'll get you up in linux yet!
> <grin>
> On Tue, 2 Oct 2001, Tim Burgess
> wrote:
>
> > Hi again,
> >
> > Do you have the URL for Bill's site and does he have such disks for
> > Slackware (7.1 in my case)?
> >
> > Thanks yet again.
> >
> > Tim
> >
> >
> > -----Original Message-----
> > From: speakup-admin@braille.uwo.ca
> > [mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
> > Sent: 02 October 2001 18:18
> > To: speakup@braille.uwo.ca
> > Subject: RE: New Kernel Survival Strategies
> >
> >
> > Hi, Tim:
> >
> > Best avenue back to your broken linux system may well be a speakup
enabled
> > floppy that can take you into rescue mode. You could do this with the
> > Redhat installation boot floppies on Bill's site, for example:
> >
> > vmlinuz -s speakup_synth=ltlk
> >
> > or perhaps:
> >
> > vmlinuz rescue speakup_synth=dectlk
> >
> > Obviously, you would specify the correct synth you have.
> >
> > If you can get the machine up this way, your lilo.conf can be fixed.
> >
> > On Tue, 2
> > Oct 2001, Tim Burgess wrote:
> >
> > > Hi and thanks.
> > >
> > > I'll give it a study and try again - this time I got as far as a
> > successful
> > > compile based on 2.2.18 with SpeakUp 0.10a. However I got a kernel
> panic
> > > that's killed me and I don't know how to boot back to my
> /boot/vmlinuz.old
> > > as I messed up lilo.conf. Looks like another rebuild. If it's true
> that
> > we
> > > learn by our mistakes then I'm going to wind up a real guru at this
> rate.
> > >
> > > Best wishes.
> > >
> > > Tim
> > >
> > >
> > > -----Original Message-----
> > > From: speakup-admin@braille.uwo.ca
> > > [mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
> > > Sent: 02 October 2001 16:49
> > > To: speakup@braille.uwo.ca
> > > Subject: RE: New Kernel Survival Strategies
> > >
> > >
> > > On Tue, 2 Oct 2001, Tim Burgess wrote:
> > >
> > > > 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?
> > > >
> > > No problem. Here it is. Beware, though, that your circumstances may be
> > > different, i.e. lba32, vga=, initrd's, and such things.
> > >
> > > The other important survival tool is a bootable floppy disk. Here's my
> > > /etc/lilo.conf:
> > >
> > > boot=/dev/hda
> > > map=/boot/map
> > > install=/boot/boot.b
> > > compact
> > > prompt
> > > timeout=500
> > > message=/boot/message
> > > lba32
> > > default=current
> > > serial=0,9600N8
> > >
> > > image=/boot/new
> > > label = new
> > > alias = n
> > > vga=0X317
> > > initrd=/boot/initrd.img-new
> > > read-only
> > > root=/dev/hda1
> > > append = "hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/current
> > > label=current
> > > alias = c
> > > vga=0X317
> > > initrd=/boot/initrd.img
> > > read-only
> > > root=/dev/hda1
> > > append = "hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/current
> > > label=express
> > > alias = x
> > > vga=0X317
> > > initrd=/boot/initrd.img
> > > read-only
> > > root=/dev/hda1
> > > append = "speakup_synth=dectlk hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/current
> > > label=litetalk
> > > alias = l
> > > vga=0X317
> > > initrd=/boot/initrd.img
> > > read-only
> > > root=/dev/hda1
> > > append = "speakup_synth=ltlk hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/current
> > > label=bns
> > > alias = b
> > > vga=0X317
> > > initrd=/boot/initrd.img
> > > read-only
> > > root=/dev/hda1
> > > append = "speakup_synth=bns hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/previous
> > > label=previous
> > > alias = p
> > > vga=0X317
> > > initrd=/boot/initrd.img-previous
> > > read-only
> > > root=/dev/hda1
> > > append = "hdc=ide-scsi hde=ide-scsi"
> > >
> > > other=/dev/hda3
> > > optional
> > > label=dos
> > >
> > > table = /dev/hda
> > >
> > > > 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
> > > >
> > > >
> > > > _______________________________________________
> > > > 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
> > >
> > >
> > > _______________________________________________
> > > 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
> >
> >
> > _______________________________________________
> > 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
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
^ permalink raw reply [flat|nested] 19+ messages in thread
* RE: New Kernel Survival Strategies
` Janina Sajka
@ ` Tim Burgess
0 siblings, 0 replies; 19+ messages in thread
From: Tim Burgess @ UTC (permalink / raw)
To: speakup
Thanks Gina,
I'm going for another attempt this morning - fingers crossed!
Thanks again.
Tim
-----Original Message-----
From: speakup-admin@braille.uwo.ca
[mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
Sent: 02 October 2001 22:28
To: speakup@braille.uwo.ca
Subject: RE: New Kernel Survival Strategies
Hi, Tim:
Congrats on getting the linux box back!
On Tue, 2 Oct 2001, Tim Burgess wrote:
> I booted from the boot disk generated at the end of the Slackware
> installation procedure and got access back right away.
Right on. That's exactly what it's for. I like to call it the "get out of
jail free disk."
<<<snip snip>>>
> 1 - When I'm booting a new kernel, can I redirect the screen output to a
> file so that I can review the messages generated (including any panics) to
> aid my trouble-shooting?
We have a spaghetti sauce here in the States that has a commercial which
uses the phrase:
"It's already in there."
So, Tim, take a look at /var/log and have at all the logs you need.
They're already in there.
> 2 - Once I've got a good (booting) 2.2.18, how do I update my wonderful
boot
> disk (or create a new one)?
>
Well, don't know about slackware, but on Redhat there's a script:
mkbootdisk
PS: I don't think you're a pain at all.
Janina
> Sorry to be a pain, but I promise I'll keep plugging at it until I
> understand this stuff and then I'll take my turn at helping others who are
> starting out. I'm saving all of the messages and I'll be using them to
> create a guide for new blinux-types on my up-coming web site.
>
> Tim
>
>
> -----Original Message-----
> From: speakup-admin@braille.uwo.ca
> [mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
> Sent: 02 October 2001 19:17
> To: speakup@braille.uwo.ca
> Subject: RE: New Kernel Survival Strategies
>
>
> Absolutely, all the way around.
>
> Bill's is an ftp site that you can access via anonymous
> ftp at
> ftp://speakup.octothorp.org.
>
> Once there, cd /pub/redhat and further as appropriate. There is indeed a
> full Redhat 7.1 installation set. The file you want, and it's path is:
>
> /pub/redhat-7.1/d1/images/boot.img
>
> This is the image for the floppy. If you don't already have it, you will
> also need rawrite which is at:
>
> /pub/redhat-7.1/d1/dosimages/rawrite.exe
>
> This is a DOS executable for creating floppies from floppy image files.
>
> NOTE: You may need to kill your screen reader while running rawrite in
> order to avoid data corruption on the floppy. It may also be advisable to
> run from an actual DOS boot, or a shutdown to MS-DOS as opposed to running
> in a DOS window in Windows.
>
> You can safely run your screen reader while answering questions from
> rawrite. It will ask you what file you want to use for the image, what
> drive to write to, and a third question probably like "press enter when
> ready." I don't recall the exact sequence, but it's OK to wait until the
> third question to kill speech. That way, you need only press enter and
> wait for the floppy to stop spinning.
>
> Good luck, and stay in touch about this. We'll get you up in linux yet!
> <grin>
> On Tue, 2 Oct 2001, Tim Burgess
> wrote:
>
> > Hi again,
> >
> > Do you have the URL for Bill's site and does he have such disks for
> > Slackware (7.1 in my case)?
> >
> > Thanks yet again.
> >
> > Tim
> >
> >
> > -----Original Message-----
> > From: speakup-admin@braille.uwo.ca
> > [mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
> > Sent: 02 October 2001 18:18
> > To: speakup@braille.uwo.ca
> > Subject: RE: New Kernel Survival Strategies
> >
> >
> > Hi, Tim:
> >
> > Best avenue back to your broken linux system may well be a speakup
enabled
> > floppy that can take you into rescue mode. You could do this with the
> > Redhat installation boot floppies on Bill's site, for example:
> >
> > vmlinuz -s speakup_synth=ltlk
> >
> > or perhaps:
> >
> > vmlinuz rescue speakup_synth=dectlk
> >
> > Obviously, you would specify the correct synth you have.
> >
> > If you can get the machine up this way, your lilo.conf can be fixed.
> >
> > On Tue, 2
> > Oct 2001, Tim Burgess wrote:
> >
> > > Hi and thanks.
> > >
> > > I'll give it a study and try again - this time I got as far as a
> > successful
> > > compile based on 2.2.18 with SpeakUp 0.10a. However I got a kernel
> panic
> > > that's killed me and I don't know how to boot back to my
> /boot/vmlinuz.old
> > > as I messed up lilo.conf. Looks like another rebuild. If it's true
> that
> > we
> > > learn by our mistakes then I'm going to wind up a real guru at this
> rate.
> > >
> > > Best wishes.
> > >
> > > Tim
> > >
> > >
> > > -----Original Message-----
> > > From: speakup-admin@braille.uwo.ca
> > > [mailto:speakup-admin@braille.uwo.ca]On Behalf Of Janina Sajka
> > > Sent: 02 October 2001 16:49
> > > To: speakup@braille.uwo.ca
> > > Subject: RE: New Kernel Survival Strategies
> > >
> > >
> > > On Tue, 2 Oct 2001, Tim Burgess wrote:
> > >
> > > > 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?
> > > >
> > > No problem. Here it is. Beware, though, that your circumstances may be
> > > different, i.e. lba32, vga=, initrd's, and such things.
> > >
> > > The other important survival tool is a bootable floppy disk. Here's my
> > > /etc/lilo.conf:
> > >
> > > boot=/dev/hda
> > > map=/boot/map
> > > install=/boot/boot.b
> > > compact
> > > prompt
> > > timeout=500
> > > message=/boot/message
> > > lba32
> > > default=current
> > > serial=0,9600N8
> > >
> > > image=/boot/new
> > > label = new
> > > alias = n
> > > vga=0X317
> > > initrd=/boot/initrd.img-new
> > > read-only
> > > root=/dev/hda1
> > > append = "hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/current
> > > label=current
> > > alias = c
> > > vga=0X317
> > > initrd=/boot/initrd.img
> > > read-only
> > > root=/dev/hda1
> > > append = "hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/current
> > > label=express
> > > alias = x
> > > vga=0X317
> > > initrd=/boot/initrd.img
> > > read-only
> > > root=/dev/hda1
> > > append = "speakup_synth=dectlk hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/current
> > > label=litetalk
> > > alias = l
> > > vga=0X317
> > > initrd=/boot/initrd.img
> > > read-only
> > > root=/dev/hda1
> > > append = "speakup_synth=ltlk hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/current
> > > label=bns
> > > alias = b
> > > vga=0X317
> > > initrd=/boot/initrd.img
> > > read-only
> > > root=/dev/hda1
> > > append = "speakup_synth=bns hdc=ide-scsi hde=ide-scsi"
> > >
> > > image = /boot/previous
> > > label=previous
> > > alias = p
> > > vga=0X317
> > > initrd=/boot/initrd.img-previous
> > > read-only
> > > root=/dev/hda1
> > > append = "hdc=ide-scsi hde=ide-scsi"
> > >
> > > other=/dev/hda3
> > > optional
> > > label=dos
> > >
> > > table = /dev/hda
> > >
> > > > 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
> > > >
> > > >
> > > > _______________________________________________
> > > > 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
> > >
> > >
> > > _______________________________________________
> > > 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
> >
> >
> > _______________________________________________
> > 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
>
>
> _______________________________________________
> 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
^ permalink raw reply [flat|nested] 19+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 19+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
strange question Martin G. McCormick
` Shaun Oliver
` Kirk Wood
` New Kernel Survival Strategies Janina Sajka
` Tim Burgess
` Janina Sajka
` Tim Burgess
` Janina Sajka
` Tim Burgess
` Janina Sajka
` Tim Burgess
` Janina Sajka
` Tim Burgess
` Gregory Nowak
` Tim Burgess
` Gregory Nowak
` Frank Carmickle
` Janina Sajka
` Tim Burgess
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).