a very challenging question?
klewellen at shellworld.net
Tue Dec 23 22:41:02 UTC 2014
On Tue, 23 Dec 2014, Tim Chase wrote:
>> From a user perspective, the experience of using Linux and FreeBSD
> aren't all that distinct. I can't think of any user-land utilities
> for the command-line that run on FreeBSD but not on Linux (the
> administrative tools vary, but that would be expected). There are
> some I've encountered that will run on Linux but not the BSDs.
Since this box is supposed to serve a specific focus, media /composition
etc., I am less concerned with user utilities, save t hose associated with
browsers, perhaps some that I know exist in both like antiword and unrtf.
Linux does support more high end sound cards, those that can capture as
well as perform playback.
I would never want to use my sound card for speech, even if I cared for it
which I firmly do not.
> > I can't blame you on the software speech thing as I find it tiring in
> long doses. At least with the freely available synths (the voices on
> my old Macbook were much easier to tolerate). Do you prefer hardware
> synths, braille output, or some other method of access?
Firmly hardware, and dectalk hardware to be specific.
I have two reading edges, I always keep a spare. My main DOS speech is
business vision, and I do not believe Linux has a direct browser for reading
edge speech regardless.
I have three dectalk express units which would have been the synthesizer for the
debian box had the rest come together.
However since I can ssh TELNET into shellworld using Dos and access all
the command line tools here with that speech, I cannot imagine why the ssh
TELNET process will not
work the other way into whatever this box becomes.
> Also, if you like the SSH shell access like you
but > want to move to a platform that you control and can install software
> that you want to, you might want to check out something like a
> Raspberry Pi. It sips power, is $35 (plus costs for a case, SD card,
> and power adaptor, but still totals under $50 in my experience), and
> can give you headless access like you currently have to shellworld
> in addition to the ability to install whatever software you like.
Nothing personal, but I have zero reason to buy a box for a platform that
has yet to prove worth investing in otherwise.
Perhaps in time, but first things first, being able to do something with
the Linux box presently holding up the speakers for my DOS one.
I am fortunate to have a fine computer tech who can build units from
scratch...he works for the motherboard people, aMD? As an electrical
I am told the things I would install in part already exist in debian, a
program for music work, with the others existing in both Linux and
freebsd. aS they are 100% command line, I should be fine once I can access
the box...something I have been working on for almost three years at least
> On December 23, 2014, Karen Lewellen wrote:
>> Hi there,
>> Thanks for all the rich and varied answers.
>> My goal if I did this would indeed be running the freebsd box
>> remotely and using ssh telnet to access it. In a way I would be
>> mirroring what I do daily <hourly? lol, here at shellworld which is
>> based on freebsd. I had intended doing the same with a debian box,
>> but am still unable to find anyone local to Toronto who can correct
>> adjust and confirm he network configuration on the unit.
>> I find programs often that are command line and coded for freebsd
>> that I would welcome trying.
>> Their may be comparative ones for debian too, but the support
>> leaves a grand deal to be desired.
>> I strongly dislike software speech, and speakup is not my idea of a
>> screen reader.
>> I would rather experiment with creating a comparative structure to
>> what I already know works then branching out as I got more
>> practice. The computer tech who builds & maintains my DOS machines
>> knows nothing much about Linux, but a clean freebsd install might
>> be fun for him. beats staying stuck without being able to try the
>> items I desire. thanks for your answer,
>> On Tue, 23 Dec 2014, Kyle wrote:
>>> I've wanted to play with FreeBSD or another sort of *real* BSD
>>> that hasn't been tainted by Apple for quite a few years. However,
>>> I am stopped thus far by a lack of a fully functional screen
>>> reader. GhostBSD is really nice, as it is said to run the MATE
>>> desktop now, but the problem is that Orca doesn't speak because
>>> of a Python conflict that causes it to fail to talk to
>>> speech-dispatcher. This would limit me to the command line, where
>>> the only full-featured screen readers run on Linux only as far as
>>> I am aware. Speakup is a set of modules that are specific to the
>>> Linux kernel, and SBL as far as I know only runs on Linux. The
>>> only other choice then would be YASR, which is rather old and is
>>> probably unmaintained now, and runs as a subshell rather than as
>>> a system daemon, so one must login without speech and run the YSR
>>> subshell manually in order to get a somewhat decent screen reader
>>> for only a single virtual console. This isn't really a problem if
>>> you intend to run your FreeBSD machine remotely over ssh or
>>> telnet, but it makes running it directly on your machine next to
>>> impossible. Please do correct me if I happen to be wrong, as I
>>> would immediately try to set it up here, at least on a virtual
>>> machine, and I could then support BSD as well as Linux in the
>>> computer business that I run. -- "Don't judge my disability until
>>> you are able to see my ability." ~ Kyle: https://kyle.tk/ My
>>> chunk of the internet: https://chunkhost.com/r/Kyle
>>> Blinux-list mailing list
>>> Blinux-list at redhat.com
>> Blinux-list mailing list
>> Blinux-list at redhat.com
> Blinux-list mailing list
> Blinux-list at redhat.com
More information about the Blinux-list