is 595-3067, not 441 (which is the type of external enclosure it is in!).
And throughput is roughly 1.5 MBytes/sec.
Submitted by: Robert E. Seastrom <rs@seastrom.com>
"Work through the PR database".
Prompted by Doug <Doug@gorean.org>, who in an e-mail to an interested
contributor in -hackers wrote;
On Sun, Jul 18, 1999 at 12:01:43PM -0700, Doug wrote:
[...]
> Step three, (and I can't believe this isn't mentioned in the handbook) if
> there isn't anything on that page that looks interesting to you, take a
> look at http://www.freebsd.org/cgi/query-pr-summary.cgi and see if
> anything there strikes your fancy. Look first at unsassigned PR's, but
> if one of them that is assigned to someone looks like something you can
> handle and have time to work on, mail the person it's assigned to and
> ask them about it.
[...]
So now it is mentioned in the Handbook :-)
by the recently committed "Serial Console" section. I had these in my
local tree, and they slipped off my "list of things to commit" somehow.
Prompted by: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
o st0 -> sa0
o Document when and where you should quote numbers in the config file.
I've modified Chris' patch slightly, any errors are mine.
PR: docs/12181
Submitted by: Chris Costello <chris@calldei.com>
it slightly from the submission just to clean up some of the English,
but Kazutaka YOKOTA should get all the kudos for this.
Submitted by: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
the 435 is no longer made, the 450 supercedes it. Keep the references to
the 435 around though, so that potential users who have one aren't put off.
Submitted by: Kevin Eliuk <kevin_eliuk@sunshine.net>
chapter 27.
These sections look pretty silly with only one entry, so please
(anyone) add more entries if you know of anything suitable.
Reviewed & adjusted by: nik
to other languages. Well, not exactly, this is more of a
FAQ than a proper tutorial. But (1) it gets it out of the
plain text format I've been sending out over the past 4
months, (2) it gets it better publicised than it has been,
and (3) it shows anyone that wants to see how to markup a
FAQ than a proper tutorial. But (1) it gets it out of the
plain text format I've been sending out over the past 4
months, (2) it gets it better publicised than it has been,
and (3) it shows anyone that wants to see how to markup a
FAQ in DocBook exactly how to do it.
