Re: guide.diff

Hi & sorry for the late reply!

> Because chap-net-misc already exist:). we have to alternatives here I can 
> create 4 small chapters from chap-net-misc (nfs,bridge,ntp,ipv6to4) or we 
> create one bigger with misc. stuff there. I preffer bigger chapter but I can 
> do it also with other way :).

I would suggest a new chapter: "Network file transfer": for nfs and 
similar things. Maybe a new chapter "Network Time Protocol" for ntpd, if 
there is no fitting place.

Bridge could be moved to "24. Introduction to 
TCP/IP Networking" or "25. Setting up TCP/IP on NetBSD in practice".

ipv6to4 could be moved to "24.7. Next generation Internet protocol - IPv6"

About the separate chapters:

"13. File systems" and "14. Disk Device". The separation is okay for 
me, it's systematic and clear. But would it possibly make sense to put 
them into one chapter? Maybe something like "Storage devices and file 
systems"?

In "13. File systems" it's not always obvious to users what the 
different file system are useful for. The "fields of application" should 
be made clearer.

"14.2.1. Configuring booting process": I think "booting process" is 
misleading here as it's about Master Boot Records and boot 

RFC: Proposed mtree.5 man page

I'm experimenting with mtree support for bsdtar, which
led me to look for a definitive statement of "the
mtree format."  Not finding one, I cobbled together
the attached draft by pulling details from the mtree.8 pages for
FreeBSD and NetBSD and adding a few choice tidbits from
the source code.

I've also included my proposal for a "#mtree" signature
at the beginning of any mtree file.

My goal is for this to become the defining document
for the mtree format across all current implementations.
In particular, I'm looking for comments from people
knowledgable about the existing mtree tools.

Feedback/comments appreciated,

Tim Kientzle

.\" Copyright (c) 1989, 1990, 1993
.\"     The Regents of the University of California.  All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\"    notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\"    notice, this list of conditions and the following disclaimer in the

(non-NetBSD) proofreading wanted

[this is not NetBSD-related; sending this to a list of people that I
  expect are able to write and proofread, still 

I'm looking for someone to proofread some 100-150 pages of english, 
preferably a native (english) speaker. Focus should be expression, grammar 
and some (minor) contents. If you're interested, please contact me 
off-list.

The text will be my PhD thesis, see http://www.feyrer.de/vulab/ for more 
information.

Thanks!

  - Hubert