Boot prompt

Boot prompt

[jim grimsby]

Hi, was being a good little boy and was reading the red hat 9 manual
like the 
 the Speakup Modified Fedora Distribution  how to says to do. And I see
an inconsistency.  The red hat 9 manual says at the boot prompt to type
linux text for a text install the  the Speakup Modified Fedora
Distribution how to says to type text for a boot in to text
installation.  Witch one is correct. 
In other words would I type 
Linux text speakup_synth=acntsa 
Or 
Text speakup_synth=acntsa 
With sarge the command was speakup speakup_synth=acntsa  thanks!

Re: Boot prompt

[David Csercsics]

You'll want to type:
text speakup_synth=blah 
or whatever the Fedora HOWTO says because they've modified the boot
process for Speakup. That would be why it's not consistent  with  the
RH 9 install docs because the installer had to be hacked for Speakup.

RE: Boot prompt

[Steve Dawes]

your are right.

Steve



-----Original Message-----
From: speakup-bounces@braille.uwo.ca
[mailto:speakup-bounces@braille.uwo.ca]On Behalf Of David Csercsics
Sent: Tuesday, April 05, 2005 8:47 PM
To: Speakup is a screen review system for Linux.
Subject: Re: Boot prompt


You'll want to type:
text speakup_synth=blah 
or whatever the Fedora HOWTO says because they've modified the boot
process for Speakup. That would be why it's not consistent  with  the
RH 9 install docs because the installer had to be hacked for Speakup.

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

Re: Boot prompt

[Janina Sajka]

There is no inconsistency here.

The Red Hat 9 manual knows nothing about Speakup or installing the
Speakup Modified. So, it tells you how to start a text install on
screen. It will happily do that for you, but you're going to be
unsatisfied without Speakup, I should think.

Now, please tell me. Do I need to protect you from this kind of
confusion in the HOWTO? Can you suggest how, if your answer is "yes?"

jim grimsby writes:
> Hi, was being a good little boy and was reading the red hat 9 manual
> like the 
>  the Speakup Modified Fedora Distribution  how to says to do. And I see
> an inconsistency.  The red hat 9 manual says at the boot prompt to type
> linux text for a text install the  the Speakup Modified Fedora
> Distribution how to says to type text for a boot in to text
> installation.  Witch one is correct. 
> In other words would I type 
> Linux text speakup_synth=acntsa 
> Or 
> Text speakup_synth=acntsa 
> With sarge the command was speakup speakup_synth=acntsa  thanks!
> 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 

Janina Sajka				Phone: +1.202.494.7040
Partner, Capital Accessibility LLC	http://www.CapitalAccessibility.Com

Chair, Accessibility Workgroup		Free Standards Group (FSG)
janina@freestandards.org		http://a11y.org

If Linux can't solve your computing problem, you need a different problem.

RE: Boot prompt

[jim grimsby]

There is no inconsistency here.
Was not implying one on your part. 
The Red Hat 9 manual knows nothing about Speakup or installing the
Speakup Modified. So, it tells you how to start a text install on
screen. It will happily do that for you, but you're going to be
unsatisfied without Speakup, I should think.
Of course! The point here was not to debate how to start speakup.  The
point here was to insure that the word linux was not needed. I thought
the directions were wonderful in the howto and am going to follow them
to the letter trust me on that one. 
Now, please tell me. Do I need to protect you from this kind of
confusion in the HOWTO? 
No I would not think so.  I mean if you got a lot of users who were
asking this question then you might want to point it out but it sounds
like I am the only one at this point who has asked the question.
Another reason I asked is my pc has a broken pc speaker that I have been
to lazy to replace so when I first tried the commands the first few
times the boot timed out.  So nothing was happening when I was issuing
my boot command. 
Text speakup_synth=acnts 
So I remembered that the redhat guide witch was infroant of me said to
type linux before text.  Instead of trying it out like I guess I should
have done I asked just to verify that I was doing things the right way.
As I said when I said there was an inconsistency I ment that both
manuals said the inisal command to get a text install was slightly
different this was not a gritasisom of your howto  or anything.  This
was just a request for clarifications.  
Thanks 

Re: Boot prompt

[Sean McMahon]

Whether you type linux is kernel dependent on what kernels are available on the
iso.  In your case I'd follow what the howto for fedora says because it's a
modified iso and kernel.  Use the redhat as reference where the howto is unclear
or lacks.  And only then, use redhat 9 documentation where fedora docs are
unclear.  Well that wasn't verry clear, use first speakup fedora howto, then
fedora docs, then if those fail your need, redhat9.
----- Original Message ----- 
From: "jim grimsby" <jimgrims@pacbell.net>
To: "Speak Up Mailing List" <speakup@braille.uwo.ca>
Sent: Tuesday, April 05, 2005 7:20 PM
Subject: Boot prompt


> Hi, was being a good little boy and was reading the red hat 9 manual
> like the
>  the Speakup Modified Fedora Distribution  how to says to do. And I see
> an inconsistency.  The red hat 9 manual says at the boot prompt to type
> linux text for a text install the  the Speakup Modified Fedora
> Distribution how to says to type text for a boot in to text
> installation.  Witch one is correct.
> In other words would I type
> Linux text speakup_synth=acntsa
> Or
> Text speakup_synth=acntsa
> With sarge the command was speakup speakup_synth=acntsa  thanks!
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: Boot prompt

[Janina Sajka]

OK. I'm aware how much extra effort it is to get the boot params in at
the right time when you don't have a beep from your bios to signal you.
In fact, I generally prefer to edit my boot script to include my params,
even at the cost of creating a new iso image for booting.

I wish we could get some kind of sonicon along with the Boot> prompt,
but we caught a lot of hell when gdm included a beep with the login
prompt, so I don't expect we'll get anything with Boot>.

jim grimsby writes:
> 
> There is no inconsistency here.
> Was not implying one on your part. 
> The Red Hat 9 manual knows nothing about Speakup or installing the
> Speakup Modified. So, it tells you how to start a text install on
> screen. It will happily do that for you, but you're going to be
> unsatisfied without Speakup, I should think.
> Of course! The point here was not to debate how to start speakup.  The
> point here was to insure that the word linux was not needed. I thought
> the directions were wonderful in the howto and am going to follow them
> to the letter trust me on that one. 
> Now, please tell me. Do I need to protect you from this kind of
> confusion in the HOWTO? 
> No I would not think so.  I mean if you got a lot of users who were
> asking this question then you might want to point it out but it sounds
> like I am the only one at this point who has asked the question.
> Another reason I asked is my pc has a broken pc speaker that I have been
> to lazy to replace so when I first tried the commands the first few
> times the boot timed out.  So nothing was happening when I was issuing
> my boot command. 
> Text speakup_synth=acnts 
> So I remembered that the redhat guide witch was infroant of me said to
> type linux before text.  Instead of trying it out like I guess I should
> have done I asked just to verify that I was doing things the right way.
> As I said when I said there was an inconsistency I ment that both
> manuals said the inisal command to get a text install was slightly
> different this was not a gritasisom of your howto  or anything.  This
> was just a request for clarifications.  
> Thanks 
> 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 

Janina Sajka				Phone: +1.202.494.7040
Partner, Capital Accessibility LLC	http://www.CapitalAccessibility.Com

Chair, Accessibility Workgroup		Free Standards Group (FSG)
janina@freestandards.org		http://a11y.org

If Linux can't solve your computing problem, you need a different problem.

RE: Boot prompt

[jim grimsby]

OK. I'm aware how much extra effort it is to get the boot params in at
the right time when you don't have a beep from your bios to signal you.
In fact, I generally prefer to edit my boot script to include my params,
even at the cost of creating a new iso image for booting.
Hi, well here is an idea note it is only an idea I have no idea how to
go about implementing it at this point but maybe it is some thing for
kerk to think about. Now I have to go in to  some of my personal history
with another os. 
Once long long ago there was a company in ca called synthavoice.  The
install program for there slimware package would detect your synthesizer
by sending out index marks and then would wait tell the synthesizer sent
them back if it got the right mark back it then new to use this
synthesizer.  Each time a mark was sent out the computer speaker would
beep letting you know the marker had been sent.  If no synthesizer was
found it would then give a sharp beep tone.  
End of history.  
Now I am aware that the beeps would not help me in this situation but if
the boo iso file had such a system then all the user would have to do is
get the pc to boot. Note note note this is not criatsism of the currant
way things work thing work good as it is just an idea to make things
work a little smoother. Also this would help all speakup users who have
modified iso files.  Now if I could just get a good iso of the flodora
I would be good to go.  I think I will wait tell we have them in torrent
or I have the extra bucks to by the cd's because I have downloaded the
iso files about 6 times and every one but disk 4 and the boot iso is
bad.  Note note note I am not saying the isos have problems on the
server but the download keeps resuming so many times that by the time I
get it I have a problem with it.  
See I am learning to make sure I fraze things as to not jerk any ones
chain.  <smile> 
I wish we could get some kind of sonicon along with the Boot> prompt,
but we caught a lot of hell when gdm included a beep with the login
prompt, so I don't expect we'll get anything with Boot>.

jim grimsby writes:
> 
> There is no inconsistency here.
> Was not implying one on your part.
> The Red Hat 9 manual knows nothing about Speakup or installing the
> Speakup Modified. So, it tells you how to start a text install on
> screen. It will happily do that for you, but you're going to be
> unsatisfied without Speakup, I should think.
> Of course! The point here was not to debate how to start speakup.  The
> point here was to insure that the word linux was not needed. I thought
> the directions were wonderful in the howto and am going to follow them
> to the letter trust me on that one. 
> Now, please tell me. Do I need to protect you from this kind of
> confusion in the HOWTO? 
> No I would not think so.  I mean if you got a lot of users who were
> asking this question then you might want to point it out but it sounds
> like I am the only one at this point who has asked the question.
> Another reason I asked is my pc has a broken pc speaker that I have
been
> to lazy to replace so when I first tried the commands the first few
> times the boot timed out.  So nothing was happening when I was issuing
> my boot command. 
> Text speakup_synth=acnts 
> So I remembered that the redhat guide witch was infroant of me said to
> type linux before text.  Instead of trying it out like I guess I
should
> have done I asked just to verify that I was doing things the right
way.
> As I said when I said there was an inconsistency I ment that both
> manuals said the inisal command to get a text install was slightly
> different this was not a gritasisom of your howto  or anything.  This
> was just a request for clarifications.  
> Thanks 
> 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca 
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 

Janina Sajka				Phone: +1.202.494.7040
Partner, Capital Accessibility LLC
http://www.CapitalAccessibility.Com

Chair, Accessibility Workgroup		Free Standards Group (FSG)
janina@freestandards.org		http://a11y.org

If Linux can't solve your computing problem, you need a different
problem.


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

Re: Boot prompt

[Sean McMahon]

Maybe I'm not understanding something, probably not.  However When I wanted to
install the sarge iso, it simply waited there for me untill I typed a command.
It would wait for ever.  Now my bios is set to boot cd first before harddrive,
but what's going on with the fedora iso that it doesn't boot to the cd or just
wait there?  Does the Fedora iso have a way of booting even if the bios is set
to boot off harddrive first?
----- Original Message ----- 
From: "Janina Sajka" <janina@rednote.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Wednesday, April 06, 2005 1:56 PM
Subject: Re: Boot prompt


> OK. I'm aware how much extra effort it is to get the boot params in at
> the right time when you don't have a beep from your bios to signal you.
> In fact, I generally prefer to edit my boot script to include my params,
> even at the cost of creating a new iso image for booting.
>
> I wish we could get some kind of sonicon along with the Boot> prompt,
> but we caught a lot of hell when gdm included a beep with the login
> prompt, so I don't expect we'll get anything with Boot>.
>
> jim grimsby writes:
> >
> > There is no inconsistency here.
> > Was not implying one on your part.
> > The Red Hat 9 manual knows nothing about Speakup or installing the
> > Speakup Modified. So, it tells you how to start a text install on
> > screen. It will happily do that for you, but you're going to be
> > unsatisfied without Speakup, I should think.
> > Of course! The point here was not to debate how to start speakup.  The
> > point here was to insure that the word linux was not needed. I thought
> > the directions were wonderful in the howto and am going to follow them
> > to the letter trust me on that one.
> > Now, please tell me. Do I need to protect you from this kind of
> > confusion in the HOWTO?
> > No I would not think so.  I mean if you got a lot of users who were
> > asking this question then you might want to point it out but it sounds
> > like I am the only one at this point who has asked the question.
> > Another reason I asked is my pc has a broken pc speaker that I have been
> > to lazy to replace so when I first tried the commands the first few
> > times the boot timed out.  So nothing was happening when I was issuing
> > my boot command.
> > Text speakup_synth=acnts
> > So I remembered that the redhat guide witch was infroant of me said to
> > type linux before text.  Instead of trying it out like I guess I should
> > have done I asked just to verify that I was doing things the right way.
> > As I said when I said there was an inconsistency I ment that both
> > manuals said the inisal command to get a text install was slightly
> > different this was not a gritasisom of your howto  or anything.  This
> > was just a request for clarifications.
> > Thanks
> >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> -- 
>
> Janina Sajka Phone: +1.202.494.7040
> Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com
>
> Chair, Accessibility Workgroup Free Standards Group (FSG)
> janina@freestandards.org http://a11y.org
>
> If Linux can't solve your computing problem, you need a different problem.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

RE: Boot prompt

[jim grimsby]

Maybe I'm not understanding something, probably not.  However When I
wanted to install the sarge iso, it simply waited there for me untill I
typed a command.
Yes this is correct behavior for this distro. 
 It would wait for ever.  Now my bios is set to boot cd first before
harddrive, but what's going on with the fedora iso that it doesn't boot
to the cd or just wait there?  Does the Fedora iso have a way of booting
even if the bios is set to boot off harddrive first?
No what is going on here is that if you do nothing in about a moment
according to the redhat nine docs and 10 seconds according to the howto
it will do a default boot with a graphical install and no speech.  

Re: Boot prompt

[Janina Sajka]

Syntha Voice could do that because it had a fully loaded OS.

The installer's boot> prompt comes up even before the linux kernel.
There's next to nothing loaded at that point.

Which doesn't mean there couldn't be a beep, but we'd have to mangle the
boot loader code to do that. So far, our approach has been to do the
least that's necessary to get things working.

Also, there are numerous other options which can be provided and are
useful sometimes. So, there's more going on here than just finding the
hardware synth.

For example, you can specify network connections, or params to do nfs,
ftp, or http based installations. Or, you might be starting a kickstart
installation. Etc.



jim grimsby writes:
> 
> OK. I'm aware how much extra effort it is to get the boot params in at
> the right time when you don't have a beep from your bios to signal you.
> In fact, I generally prefer to edit my boot script to include my params,
> even at the cost of creating a new iso image for booting.
> Hi, well here is an idea note it is only an idea I have no idea how to
> go about implementing it at this point but maybe it is some thing for
> kerk to think about. Now I have to go in to  some of my personal history
> with another os. 
> Once long long ago there was a company in ca called synthavoice.  The
> install program for there slimware package would detect your synthesizer
> by sending out index marks and then would wait tell the synthesizer sent
> them back if it got the right mark back it then new to use this
> synthesizer.  Each time a mark was sent out the computer speaker would
> beep letting you know the marker had been sent.  If no synthesizer was
> found it would then give a sharp beep tone.  
> End of history.  
> Now I am aware that the beeps would not help me in this situation but if
> the boo iso file had such a system then all the user would have to do is
> get the pc to boot. Note note note this is not criatsism of the currant
> way things work thing work good as it is just an idea to make things
> work a little smoother. Also this would help all speakup users who have
> modified iso files.

Re: Boot prompt

[Janina Sajka]

The Fedora installer is set to pause at the boot prompt for just a few
seconds--I don't recall exactly, something like 10 seconds. Thereafter,
it executes a default.

However, all of this is specified via a syslinux.cfg file. As I said in
my earlier message, it's trivial to edit the syslinux.cfg for the boot
params you want to use. It's just that, if you do that, you have to
recreate the iso image, assuming you're booting from a cd rom. If,
instead, you're booting from a memory stick, this really does become
very trivial.

Sean McMahon writes:
> Maybe I'm not understanding something, probably not.  However When I wanted to
> install the sarge iso, it simply waited there for me untill I typed a command.
> It would wait for ever.  Now my bios is set to boot cd first before harddrive,
> but what's going on with the fedora iso that it doesn't boot to the cd or just
> wait there?  Does the Fedora iso have a way of booting even if the bios is set
> to boot off harddrive first?
> ----- Original Message ----- 
> From: "Janina Sajka" <janina@rednote.net>
> To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
> Sent: Wednesday, April 06, 2005 1:56 PM
> Subject: Re: Boot prompt
> 
> 
> > OK. I'm aware how much extra effort it is to get the boot params in at
> > the right time when you don't have a beep from your bios to signal you.
> > In fact, I generally prefer to edit my boot script to include my params,
> > even at the cost of creating a new iso image for booting.
> >
> > I wish we could get some kind of sonicon along with the Boot> prompt,
> > but we caught a lot of hell when gdm included a beep with the login
> > prompt, so I don't expect we'll get anything with Boot>.
> >
> > jim grimsby writes:
> > >
> > > There is no inconsistency here.
> > > Was not implying one on your part.
> > > The Red Hat 9 manual knows nothing about Speakup or installing the
> > > Speakup Modified. So, it tells you how to start a text install on
> > > screen. It will happily do that for you, but you're going to be
> > > unsatisfied without Speakup, I should think.
> > > Of course! The point here was not to debate how to start speakup.  The
> > > point here was to insure that the word linux was not needed. I thought
> > > the directions were wonderful in the howto and am going to follow them
> > > to the letter trust me on that one.
> > > Now, please tell me. Do I need to protect you from this kind of
> > > confusion in the HOWTO?
> > > No I would not think so.  I mean if you got a lot of users who were
> > > asking this question then you might want to point it out but it sounds
> > > like I am the only one at this point who has asked the question.
> > > Another reason I asked is my pc has a broken pc speaker that I have been
> > > to lazy to replace so when I first tried the commands the first few
> > > times the boot timed out.  So nothing was happening when I was issuing
> > > my boot command.
> > > Text speakup_synth=acnts
> > > So I remembered that the redhat guide witch was infroant of me said to
> > > type linux before text.  Instead of trying it out like I guess I should
> > > have done I asked just to verify that I was doing things the right way.
> > > As I said when I said there was an inconsistency I ment that both
> > > manuals said the inisal command to get a text install was slightly
> > > different this was not a gritasisom of your howto  or anything.  This
> > > was just a request for clarifications.
> > > Thanks
> > >
> > >
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> > -- 
> >
> > Janina Sajka Phone: +1.202.494.7040
> > Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com
> >
> > Chair, Accessibility Workgroup Free Standards Group (FSG)
> > janina@freestandards.org http://a11y.org
> >
> > If Linux can't solve your computing problem, you need a different problem.
> >
> >
> > _______________________________________________
> > 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				Phone: +1.202.494.7040
Partner, Capital Accessibility LLC	http://www.CapitalAccessibility.Com

Chair, Accessibility Workgroup		Free Standards Group (FSG)
janina@freestandards.org		http://a11y.org

If Linux can't solve your computing problem, you need a different problem.