Spelling police.
This commit is contained in:
Mike Pritchard
parent
0788e8780d
commit
04564716a7
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=911
5 changed files with 25 additions and 25 deletions
|
|
@ -6,7 +6,7 @@
|
|||
++
|
||||
++ Copyright Eric L. Hernes - Wednesday, August 2, 1995
|
||||
++
|
||||
++ $Id: ddwg.sgml,v 1.2 1996-10-06 20:17:08 jfieber Exp $
|
||||
++ $Id: ddwg.sgml,v 1.3 1996-12-28 23:36:51 mpp Exp $
|
||||
++
|
||||
++ Sgml doc for something
|
||||
-->
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<abstract>
|
||||
|
||||
This document describes how to add a device driver to FreeBSD. It is
|
||||
<it/not/ intended to be a tutorial on unix device drivers in general.
|
||||
It is intended for device driver authors, familiar with the unix
|
||||
<it/not/ intended to be a tutorial on UNIX device drivers in general.
|
||||
It is intended for device driver authors, familiar with the UNIX
|
||||
device driver model, to work on FreeBSD.
|
||||
|
||||
</abstract>
|
||||
|
|
@ -464,7 +464,7 @@ The steps required to add your driver to the standard FreeBSD kernel are
|
|||
<p>
|
||||
The standard model for adding a device driver to the Berkeley kernel
|
||||
is to add your driver to the list of known devices. This list is
|
||||
dependant on the cpu architecture. If the device is not i386 specific
|
||||
dependent on the CPU architecture. If the device is not i386 specific
|
||||
(PCCARD, PCI, SCSI), the file is in ``/usr/src/sys/conf/files''.
|
||||
If the device is i386 specific, use ``/usr/src/sys/i386/conf/files.i386''.
|
||||
A typical line looks like:
|
||||
|
|
@ -793,9 +793,9 @@ Lines 132 - 139
|
|||
driver, as opposed to an LKM filesystem, or an LKM system call.
|
||||
<code>
|
||||
132 /*
|
||||
133 * this macro maps to a funtion which
|
||||
133 * this macro maps to a function which
|
||||
134 * sets the LKM up for a driver
|
||||
135 * as opposed to a filesystem, systemcall, or misc
|
||||
135 * as opposed to a filesystem, system call, or misc
|
||||
136 * LKM.
|
||||
137 */
|
||||
138 MOD_DEV("pcaudio_mod", LM_DT_CHAR, 24, &pcacdevsw);
|
||||
|
|
@ -833,7 +833,7 @@ and just refer to the shared memory segment via pointers.
|
|||
151 /*
|
||||
152 * this maps the shared memory address
|
||||
153 * from physical to virtual, to be
|
||||
154 * consistant with the way
|
||||
154 * consistent with the way
|
||||
155 * /usr/src/sys/i386/isa.c handles it.
|
||||
156 */
|
||||
157 pcadev[i].id_maddr -=0xa0000;
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
|
||||
<!ENTITY base CDATA "../..">
|
||||
<!ENTITY date "$Date: 1996-10-06 20:17:12 $">
|
||||
<!ENTITY date "$Date: 1996-12-28 23:36:52 $">
|
||||
<!ENTITY title "Diskless X Server: a how to guide">
|
||||
<!ENTITY copyright " ">
|
||||
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
|
||||
]>
|
||||
<!-- $Id: disklessx.sgml,v 1.2 1996-10-06 20:17:12 jfieber Exp $ -->
|
||||
<!-- $Id: disklessx.sgml,v 1.3 1996-12-28 23:36:52 mpp Exp $ -->
|
||||
|
||||
<html>
|
||||
&header;
|
||||
|
|
@ -19,7 +19,7 @@ required first creating a diskless system with minimal utilities mounted
|
|||
via NFS. These same steps were used to create 2 separate diskless systems.
|
||||
The first is 'altair.kcis.com'. A diskless X terminal that I run on my
|
||||
old 386DX-40. It has a 340Meg hard disk but, I did not want to change it.
|
||||
So, it boots from 'antares.kcis.com' across a ethernet. The second system
|
||||
So, it boots from 'antares.kcis.com' across a Ethernet. The second system
|
||||
is a 486DX2-66. I setup a diskless FreeBSD (complete) that uses no local
|
||||
disk. The server in that case is a Sun 670MP running
|
||||
SunOS 4.1.3. The same setup configuration was needed for both.</p>
|
||||
|
|
@ -79,7 +79,7 @@ boot floppy created earlier.
|
|||
|
||||
<h2>Determine which program to run (On the diskless system)</h2>
|
||||
|
||||
<p>If you know the chipset that your ethernet adapter uses, this is
|
||||
<p>If you know the chipset that your Ethernet adapter uses, this is
|
||||
easy. If you have the NS8390 chipset, or a NS8390 based chipset,
|
||||
use NB8390.COM. If you have a 3Com 509 based chipset, use the
|
||||
NB3C509.COM boot program. If you are not sure which you have,
|
||||
|
|
@ -89,9 +89,9 @@ Beyond that, you are pretty much on your own.
|
|||
<h2>Booting across the network</h2>
|
||||
|
||||
<p>Boot the diskless system with out any config.sys/autoexec.bat
|
||||
files. try running the boot program for your ethernet adapter.</p>
|
||||
files. try running the boot program for your Ethernet adapter.</p>
|
||||
<pre>
|
||||
My ethernet adapter is running in WD8013 16bit mode so
|
||||
My Ethernet adapter is running in WD8013 16bit mode so
|
||||
I run NB8390.COM
|
||||
|
||||
C:> cd \netboot
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: mh.sgml,v 1.2 1996-10-06 20:17:14 jfieber Exp $ -->
|
||||
<!-- $Id: mh.sgml,v 1.3 1996-12-28 23:36:53 mpp Exp $ -->
|
||||
<!--
|
||||
From matt@garply.com Wed May 22 08:25:18 1996
|
||||
Date: Tue, 23 Jan 1996 11:02:50 -0600
|
||||
|
|
@ -279,7 +279,7 @@ created underneath your MH Mail directory, and messages in that folder
|
|||
are going to be stored in that directory. When new email comes in that
|
||||
new email is thrown into your inbox directory with a file name that is
|
||||
equivalent to the message number. So even if you didn't have any of
|
||||
the MH tools to read your email you could still use standard unix
|
||||
the MH tools to read your email you could still use standard UNIX
|
||||
commands to munge around in those directories and just more your
|
||||
files. It's this simplicity that really gives you a lot of power with
|
||||
what you can do with your email.
|
||||
|
|
@ -351,7 +351,7 @@ This allows you to do things like
|
|||
pick -to freebsd-hackers@freebsd.org -seq hackers
|
||||
</verb></tscreen>
|
||||
to get a list of all the email send to the FreeBSD hackers mailing
|
||||
list. <em/pick/ also allows you to group these criteria in differents
|
||||
list. <em/pick/ also allows you to group these criteria in different
|
||||
ways using the following options:
|
||||
<itemize>
|
||||
<item>... <tt/-and/ ...
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
<!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN">
|
||||
<!-- $Id: newuser.sgml,v 1.3 1996-11-17 15:09:08 jfieber Exp $ -->
|
||||
<!-- $Id: newuser.sgml,v 1.4 1996-12-28 23:36:54 mpp Exp $ -->
|
||||
|
||||
<article>
|
||||
<title>For People New to Both FreeBSD and Unix</title>
|
||||
|
|
@ -74,7 +74,7 @@ root, and as root you'll have the same environment as jack
|
|||
|
||||
You can quit <tt>adduser</tt> any time by typing <tt>Ctrl-C</tt>, and at the end
|
||||
you'll have a chance to approve your new user or simply type <tt>n</tt> for no.
|
||||
You might want to create a second newuser (jill?) so that when you edit
|
||||
You might want to create a second new user (jill?) so that when you edit
|
||||
jack's login files, you'll have a hot spare in case something goes wrong.
|
||||
|
||||
Once you've done this, use <tt>exit</tt> to get back to a login prompt and log
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue