From: "hank smith" <hanksmith4@earthlink.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: installing Slackware or debian via telnet?
Date: Tue, 21 Feb 2006 21:49:26 -0800 [thread overview]
Message-ID: <01fb01c63773$bebe7f40$0818f304@home> (raw)
In-Reply-To: <20060221232548.GA29070@tomass.dyndns.org>
how do you start software speech with grml?
----- Original Message -----
From: "Thomas Stivers" <stivers_t@tomass.dyndns.org>
To: <speakup@braille.uwo.ca>
Sent: Tuesday, February 21, 2006 3:25 PM
Subject: Re: installing Slackware or debian via telnet?
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
> On Tue, Feb 21, 2006 at 12:33:51 PM -0700, Jacob Schmude wrote:
>> Hi all
>>
>> I need to install Linux on a computer to act as a server.
>> Unfortunately, the system is without serial ports and sighted
>> assistance is not, repeat not, available. I've tried installing
>> fedora core 4 via telnet, but the NIC on this system which has an
>> nVidia NForce chipset is not one of the drivers loaded when doing a
>> telnet install. Is there any way to install either slackware or
>> debian via telnet?
>
> You might try using the trml live cd. It supports both software speech
> from the live cd and starting up an ssh server with boot parameters.
> Once you have the live cd up and running you can then bootstrap a debian
> install on the hard drive. I'm not sure about installing grml to the hd
> though because then AFAICT its not a straight upgrade path to a debian
> system. If you absolutely need telnet rather than ssh I think you can
> start the telnet service from the boot prompt as well, but I don't know
> how off hand.
>
> - --
> "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.2 (GNU/Linux)
>
> iD8DBQFD+6F85JK61UXLur0RA5pAAJ9byGRPjkaLpuWEWS01IoRNJ1ZzMQCfTEDO
> HKipaOOE/bIikHnakfL0Mts=
> =Ienc
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> __________ NOD32 1.1410 (20060215) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
Jacob Schmude
` Tom Moore
` Jacob Schmude
` Thomas Stivers
` Kirk Reiser
[not found] ` <20060222222235.GB29581@cm.nu>
` Tyler Spivey
` Lorenzo Taylor
` hank smith [this message]
` Michael Prokop
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='01fb01c63773$bebe7f40$0818f304@home' \
--to=hanksmith4@earthlink.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).