From: <jaffar@jeffstudio.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Debian netinst CD with speakup
Date: Mon, 20 Jun 2005 23:31:28 +0800 [thread overview]
Message-ID: <000f01c575ad$28bbde80$f342d4da@jaffar57b5aa42> (raw)
In-Reply-To: <20050620114741.GE19441@tomass.dyndns.org>
Hi I don't know if this is an appropriate thread on which to discuss this
on, but the netinst Cd would not boot and I seem to get no response either
from the CD or when i typed in the speakup command at the boot prompt. I
have set the bios on my pc to boot up with my Cd drive, so I can't exactly
be sure what is really happening here. Fedora and slackware, for example
did spin during the boot up and after the text commands for each was typed
in, but i got no response from the debian netinst CD at all, no spinning to
speak off. Don't know what to do next. Cheers!
----- Original Message -----
From: "Thomas Stivers" <stivers_t@tomass.dyndns.org>
To: <speakup@braille.uwo.ca>; "Speakup Distribution List"
<speakup@speech.braille.uwo.ca>
Sent: Monday, June 20, 2005 7:47 PM
Subject: Re: Debian netinst CD with speakup
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
> On Mon, Jun 20, 2005 at 07:05:03 AM -0400, Charles Hallenbeck wrote:
>> The disk installs Sarge/testing, but Sarge is no longer testing, since
>> it was promoted to stable on June 6. Testing is now called something
>> else. So what do I get if I now do an install with that CD? Do I get
>> Sarge/stable? or the new testing? Will there be an opportunity to
>> specify which I want during the install? perhaps by dropping to a shell
>> prompt and editing something? I will be doing two more installations
>> later this week and hope to avoid surprises.
>
> Short answer: If you have the 3.1r0a CD just install it and it'll work.
>
> Long answer: I think the answer depends on exactly which revision of the
> netinst-speakup cd you have. If you downloaded it a while back you might
> have a copy that was for the testing ditribution, but if you have the
> 3.1r0a version then what you have is for stable. You can of course edit
> /etc/apt/sources.list after you install and specify
> stable/testing/unstable or sarge/etch/sid whichever you prefer. As an
> interesting note, according to the debian top brass who are supposed to
> know about these things, changing entries in /etc/apt/sources.list is
> not the canonical way to choose which version you are running. I am not
> completely clear on the details, but it looks like you can have all
> three of stable, testing, and unstable listed in sources.list and then
> choose the default release you want by putting the line
> APT::Default-Release "stable"; in /etc/apt/apt.conf. This file will not
> exist by default. I think this might be a good idea because it allows
> you to run selected packages from testing or unstable while keeping the
> bulk of your system running stable. It is rather an advanced option, so
> as the saying goes "if you break it you get to keep all the pieces."
>
> - --
> "Debugging is twice as hard as writing the code in the first place.
> Therefore, if you write the code as cleverly as possible, you are,
> by definition, not smart enough to debug it." - Brian W. Kernighan
>
> Thomas Stivers e-mail: stivers_t@tomass.dyndns.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
>
> iD8DBQFCtqzd5JK61UXLur0RA4WJAJ4h7DE6zPXsoRIXs0ZQd2hZURrzngCbBx9W
> tv/kn+eJlDdcEThdSo2cHk4=
> =ism0
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
Charles Hallenbeck
` Thomas Stivers
` jaffar [this message]
` Jim Grimsby
` Thomas Stivers
` Jim Grimsby
` Jim Grimsby
` Thomas Stivers
` Sean McMahon
` Sean McMahon
` Sean McMahon
` Thomas Stivers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000f01c575ad$28bbde80$f342d4da@jaffar57b5aa42' \
--to=jaffar@jeffstudio.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).