Tom Rhodes <trhodes@FreeBSD.org> writes:
> I've included a patch. It causes a few "empty line" warnings,
> but still gives you the general idea. Comments and suggestions
> are very welcome.
I got no change to my file after these messages:
Patching file rc.conf.5 using Plan A...
Hunk #1 succeeded at 49.
Hunk #2 succeeded at 73.
patch: **** malformed patch at line 261: script files -into individual filenames.
> ===================================================================
> RCS file: /home/ncvs/src/share/man/man5/rc.conf.5,v
> Instead, it is included by the
> various generic startup scripts in
rm "generic".
> -.Pa /etc
> +.Pa /etc/rc.d
> which conditionalize their
rm "alize". Please.
> internal actions according to the settings found there.
Found where? "settings found there" -> "variables set in rc.conf".
> .Nm
> -file:
> +file, classified by section.
If you think it's worth your time. IMO, it won't help users
much, but it WILL make it look more organized -- a good thing.
> +When an configuration variable exists which may fit into
"an" > "a"
> +two or more catagories, it will be listed with those which
spelling
> +contain the most likeness.
That sounds like some will be listed in muliple categories.
I hope that's not true.
> +.Ss DEBUG
> +Configuration variables which enable or disable debugging
> +messages or controls are defined below:
I don't like "are defined below:". Redundant or something.
Maybe "are defined below." or "are:"
Whoops; maybe that's not yours. Oh well.
_______________________________________________
freebsd-doc@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-doc
To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org"