From: "Doug Sutherland" <doug@proficio.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: can speakup be used in bsd?
Date: Sat, 9 Jun 2007 00:13:49 -0500 [thread overview]
Message-ID: <001101c7aa54$f6b154e0$ab00a8c0@tenstac> (raw)
In-Reply-To: <466a2507.5d8392a8.1750.ffffef08@mx.google.com>
What is Linux is actually only the kernel, the rest of what
makes a distro is all GNU tools, starting with the toolchain
that makes a kernel: compiler, assember, binutils, glibc, etc,
and the things make it a unix system: tcp/ip, dns, shells,
parsers, etc, and all of the other add-ons. What makes
one distro different from another is the choice of which
programs are included, how the file system hierarchy is
laid out, how the init scripts work, how the install and
and configuration works.
BSD is a similar situation but the design of the kernel is
exteremely different, how device drivers are included is
also very different, but its based on the same set of GNU
tools, similar toolchain, similar utilities etc. The difference
between the BSD variants is similar to the difference
between linux distros. People split off from the original
berkeley unix and started making different distros and
focusing on different areas, with somewhat different
philosophies as to how things should be done.
Regarding security, BSD is probably more secure only
because there is less of it around, therefore less reason
for hackers to attack it, same as mac.
Can speakup work with BSD, no. The source code
patches the kernel, and the kernels are completely
different. Something exactly like speakup could be
written for BSD but I think most of the code would
not be portable at all.
-- Doug
prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Jeremy
` Jacob Schmude
` Jeremy
` Doug Sutherland [this message]
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='001101c7aa54$f6b154e0$ab00a8c0@tenstac' \
--to=doug@proficio.ca \
--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).