From: Ron Marriage <marriage@seidata.com>
To: blinux-list@redhat.com
Subject: Re: Linux Mandrake 7.2 Accessibliity
Date: Thu, 16 Nov 2000 16:59:53 -0500 [thread overview]
Message-ID: <00111617222400.02085@tux.localhost.localdomain> (raw)
In-Reply-To: <000e01c05012$3b69d980$e075f59b@essex.ac.uk>
Hi
I run Mandrake 7.1 and like it very much. Mine is somewhat
a different situation as my wife and son want X and I work
in console. Mandrake does a super job at this.
As to your questions, no the harddrake utility is not
accessable from console, but then most of what it does use
are easily ran as seperate aps.
Linuxconf is and most of the other options can be run from
console without problem.
Kudzu automatically searches for new hardware at system
startup and had done a super job.
The difference between 7.1 and 7.2 is basically a new
kernal and many enhancements under X. You should expect to
be able to run and maintain your machine without problems.
Most of the sleak X utilities, I've found, are just pretty
interfaces for the console utilities. <grin>
Ron
On Thu, 16 Nov 2000, you wrote:
>
> Hi All,
>
> Are the configuration tools in Linux Mandrake 7.2, such as harddrake, the hardware detection tool, accessible from a console using speakup or brltty? i like the sound of mandrake, due to its intel optimisations, and advanced hardware support, but would like some information about the accessibility mentioned above.
>
> Regards, Saqib
>
--
Ron Marriage
Email marriage@seidata.com
Homepage http://www.seidata.com/~marriage/
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Saqib Shaikh
` Ron Marriage [this message]
` Brent Harding
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=00111617222400.02085@tux.localhost.localdomain \
--to=marriage@seidata.com \
--cc=blinux-list@redhat.com \
/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).