- Comment out the description of the unimplemented replace command
- Explain in even stronger language that resetconfig is not for
everyday use
Motivated by: Marko Schütz <marko@ki.informatik.uni-frankfurt.de>
- Correct the description of the start command (no longer used to
start vinum, just specific objects)
Motivated by: dg
- Remove .TH N commands, which conflict badly with the doc macros,
causing strange headings in nroff output and endless loops in troff.
The current version produces warning messages with some screen
sizes, and will be fixed when I have time.
Bug-report: docs/9328 (nroff)
Reported-by: joerg (troff)
- Add gotcha info for the setupstate keyword and the use of label and
resetconfig.
- Add bug entry for the warning messages introduced by fixing
docs/9328.
- Add references to web pages on Vinum
In the words of the submitter:
"The patch below allows to ping from any address on the multihomed host.
The man page is also updated, the text was cutted from traceroute(8)."
Submitted by: Ruslan Ermilov
PR: 6832
It just replace u_long with u_int32_t and shouldn't affect on i386.
Without this patch,
- unaligned accesses occur
- permission denied randomly
Submitted by: Hidetoshi Shimokawa <simokawa@sat.t.u-tokyo.ac.jp>
- Describe subdisk attachment in more detail
- Describe new 'makedev' command
- Correct use of 'partition' and 'slice'
- Describe 'setupstate' keyword
- Include performance guidelines for striped plexes
- Correct numerical values in examples
- Add examples for disklabel(8)
- Clarify problems creating Vinum drives on inappropriate partitions
Prodded by: NAGANUMA Yasuhiro <y_naga@carat.rim.or.jp> (slices and
partitions)
Submitted by: Kirk McKusick <mckusick@McKusick.COM>
Obtained from: Mckusick, BSDI and a host of others
This exactly matches Kirks sources imported under the
Tag MCKUSICK2. These are as supplied by kirk with one small
change needed to compile under freeBSD.
Some FreeBSD patches will be added back, though many have been
added to Kirk's sources already.
This allows for more flexible ipfw configuration files using
`variables' to describe frequently used items in the file, like the
local IP address(es), interface names etc. Both m4 and cpp are useful
and supported; with m4 being a little more unusual to the common C
programmer, things like automatic rule numbering can be achieved
fairly easy.
While i was at it, i've also untangled some of the ugly style inside
main(), and fixed a bug or two (like not being able to use blank lines
when running with -q).
A typical call with preprocessor invocation looks like
ipfw -p m4 -Dhostname=$(hostname) /etc/fwrules
Someone should probably add support for this feature to /etc/rc.firewall.
