longer accept a "units" argument to the kernel configuration entry.
Devfs now does all the device management, eschew use of MAKEDEV.
Note: I haven't yet tested all the commands here, I suspect some
instances of "ccd0c" may need to become simply "ccd0".
doesn't work for audio CDs" at the end, with no explanation as to how to
duplicate audio CDs.
Since I needed to do this recently, document the process. Note that I
don't have an ATAPI CDRW drive, so the ATAPI examples are based on some
googling and IRC discussions.
While I'm here, remove some <option>s and <filenames> that had snuck
into some <userinput> elements.
* Conform section title
Automagic is a common English/computer term, but as Hiten points out,
this can be confusing to some.
PR: docs/34163
Submitted by: Hiten Pandya <hiten@uk.FreeBSD.org>
timeouts. Quotes around kernel options with numbers went out in the
Stone Age, and using whole seconds went out when CAM arrived.
Also add a very brief description of what this option does.
Handbook.
I believe that the answer given in the FAQ is incorrect, but am not
enough of a SCSI stud to confirm it. I'll be forwarding the info to
the -scsi list and asking for confirmation or denial before I make any
content changes.
mount a CDROM? You have *got* to be kidding...
Fixed, with content pulled from FAQ.
----------------------------------------------------------------------
* After reading this chapter you will know:
-> After reading this chapter, you will know:
* Before reading this chapter you should:
-> Before reading this chapter, you should:
* Move BIOS Drive Numbering and Mounting/Mounting and Unmounting
Filesystems to Basics chapter
* Update sypnosis to reflect changes
* Change title of "Disk Quotas" to "File System Quotas"
* Create new RAID section w/ sub-sections Soft & Hard
* Move ccd section into Soft RAID
* Create to-be completed vinum sub-section of Soft RAID
* Move Backup Programs, Backup Media, and Floppy Backup sections
from Backups chapter into Storage
Suggested by: murray and nik
An an aside, most of this part of the chapter is marked up
incorrectly--e.g., <quote> is used where something like <devicename>
is much more appropriate. This delta doesn't help, but keeps things
relatively consistent.
PR: 30062
Submitted by: Mike Meyer <mwm@mired.org>
* First and last word uppercase
* Prepositions, articles, and short conjunctions lowercase
* The word 'to' lowercase
* Preserved capitalization for program/command names
Reviewed by: murray
Placed sh, bash, csh, tcsh in <command>
Placed commands in <command>
Placed options in <option>
Placed several commands in man entities
Placed several applications in <application>
Placed make vars/targets into <makevar>/<maketarget>
Placed filenames in <filename>
<literal>chmod()</literal> -> <function>chmod()</function>
Standardize:
ATT -> AT&T
endeavour -> endeavor
tcl -> Tcl
Reviewed by: murray
at the end of the reference. Removed the '/'.
+ Marked up 'log' and 'spool' as filenames
in the discussion of the 'var' directory.
+ Changed fdisk to show up as command.
+ Marked up vn as device.
+ Marked up "sysinstall" using a man.systinstall.8; entity.
PR: docs/28989
Submitted by: Martin Heinen <mheinen0@wiesbaden-online.de>
<indexterm> tags outside of <para>s since this can add extra
whitespace characters to the output (for print stylesheets).
Pointed out by: Chris Costello
further step in, to allow for more topics in this chapter. Enwrap
it with <sect1 id="disks-adding"> and <title>Adding disks</title>.
Translators need just add the above, and indent, and then add the
closing tag where I did.
most of the other spurious comments.
Two comments relating to copyright have *not* been merged in from the
LinuxDoc version yet -- I've contacted the original authors to ask if
they would be willing to assign the copyright to the project. When I
get their response the copyright comments will either be merged in, or
left out, as necessary.
Rationale: All the changes to the DocBook handbook so far have been
careful to keep whitespace changes to a minimum. This is so the
translators have as easy a job as possible in identifying exactly what's
changed.
This has meant the English version has become more and more 'ugly'. Lines
indented by the wrong amount, some lines longer than 130 characters,
others shorter than 20, gaps of 3 or 4 lines between paragraphs (and
sometimes within paragraphs). This makes it difficult to follow the
structure of the document, and needlessly complicates fixing SGML
problems.
It also makes the source practically useless as a teaching aid; the
more baroque the source looks, the less likely people are to dive in and
contribute.
This commit fixes all that -- and boy was it tedious. The snag is, it's
touched almost every line in every file in the Handbook.
Technically, the changes were made by running (in Emacs)
sgml-indent-or-tab (bound to the TAB key) on almost each line (except
those in <programlisting>, <screen>, <literallayout>, and other
verbatim sections), and then running sgml-fill-element (bound to
C-c C-q) on most paragraphs.
FWIW, this is the first, only, and last change of this type contemplated.
<informalexample>
<screen>
...
</screen>
</informalexample>
need the <informalexample> element. So remove it. Simple search and
replace does the trick.
tags LINUXDOC_2_DOCBOOK_START and LINUXDOC_2_DOCBOOK from doc/handbook/.
Note that the LINUXDOC_2_DOCBOOK tag is not necessarily at the HEAD of
the file. So some files won't show changes because changes were applied
after I laid down the LINUXDOC_2_DOCBOOK tag.
Not everything was merged. In some cases, URLs had been shortened;
http://www.freebsd.org/docproj/
becomes
../docproj/
This is a mistake, since users browsing the Handbook on their own machine
can't be expected to have links like this work. Of course, for mirrors,
they'll end up pointing back to the main site. For the mean time, do
nothing -- this will need an entity defined to reference the base URL
of the FreeBSD site, individual mirrors can set this as necessary.
Notice how some files (on the left) are merged to the same file (on
the right). This is because the new Handbook file structure is organised
on DocBook chapter lines.
Files with no revision number in the "From" column didn't exist when I
started the conversion.
File From -> To Merged to files...
---------------------------------------------------------------
anoncvs.sgml -> 1.1 cutting-edge/chapter.sgml
authors.sgml 1.93 -> 1.118 authors.ent
backups.sgml -> 1.4 backups/chapter.sgml
bibliography.sgml 1.33 -> 1.37 bibliography/chapter.sgml
contrib.sgml 1.274 -> 1.312 staff/chapter.sgml
ctm.sgml 1.22 -> 1.23 cutting-edge/chapter.sgml
cvsup.sgml 1.36 -> 1.40 cutting-edge/chapter.sgml
disks.sgml -> 1.3 disks/chapter.sgml
eresources.sgml 1.39 -> 1.50 eresources/chapter.sgml
firewalls.sgml 1.19 -> 1.20 security/chapter.sgml
handbook.sgml 1.83 -> 1.91 handbook.sgml
history.sgml 1.24 -> 1.25 introduction/chapter.sgml
install.sgml 1.65 -> 1.67 install/chapter.sgml
isdn.sgml 1.12 -> 1.15 advanced-networking/chapter.sgml
kerberos.sgml 1.12 -> 1.13 security/chapter.sgml
kernelconfig.sgml 1.31 -> 1.32 kernelconfig/chapter.sgml
kerneldebug.sgml 1.17 -> 1.19 kerneldebug/chapter.sgml
linuxemu.sgml 1.22 -> 1.24 linuxemu/chapter.sgml
memoryuse.sgml 1.11 -> 1.12 internals/chapter.sgml
mirrors.sgml 1.80 -> 1.92 mirrors/chapter.sgml
nutshell.sgml 1.14 -> 1.15 introduction/chapter.sgml
pgpkeys.sgml 1.25 -> 1.28 pgpkeys/chapter.sgml
policies.sgml 1.16 -> 1.18 policies/chapter.sgml
porting.sgml 1.93 -> 1.112 contrib/chapter.sgml
ports.sgml 1.29 -> 1.31 ports/chapter.sgml
printing.sgml 1.21 -> 1.22 printing/chapter.sgml
relnotes.sgml 1.24 -> 1.28 introduction/chapter.sgml [1]
submitters.sgml 1.161 -> 1.246 contrib/chapter.sgml
synching.sgml 1.12 -> 1.13 cutting-edge/chapter.sgml
userppp.sgml 1.28 -> 1.30 ppp-and-slip/chapter.sgml
[1] A chunk of relnotes.sgml is in an IGNORED marked section. Why?
Submitted by: A bunch (~ 50%) of merging done by Charles A. Wimmer
(cawimm@FreeBSD.ORG), rest by Nik.
