headers
Jeremy C. Reed | 2 Dec 2008 03:43

missing licenses in man pages (man8)

Slowly working on printed book based on man8. ...

I noticed several files missing licenses.

(I blind carbon copied this same email to a few developers who were the 
ones who committed the initial manual pages. I mention your NetBSD 
username below. Please point me to the copyright/license, or public domain 
statement.)

Please share your comments on any of these.

atrun.8 -- switched to GPL'd copy via OpenBSD? (do they know?) revert? ask 
cgd (original commit) and christos (removed license and switched to GPL'd 
version)

bootparamd.8 -- .c is public domain, assume same

bootpef.8 -- license in .c file, assume same

bootptest.8 -- assume same as usr.sbin/bootp/bootptest/print-bootp.c -- if 
so must include this in the file itself

dbsym.8 -- maybe license is same as dbsym.c

fdisk.8 -- don't know if was written by Julian Elischer or Robert Baron or 
other

hpcmips/boot.8	-- ask takemura

hpcmips/pbsdboot.8 -- ask jun
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jeremy C. Reed | 20 Dec 2008 18:21

End-of-Life documented? merge releases pages?

Where is the NetBSD release end-of-life policy documented?

And any suggestions or thoughts onm merging the /releases/ webpages? For 
example, maybe the formal.html, index.html, and parts of release-map.html 
should be merged? Some redundant information. And some information about 
same topics are disjointed (but should be together). Have a look.

  Jeremy C. Reed
Permalink | Reply | 0 comments |
headers
Jeremy C. Reed | 20 Dec 2008 18:47

docs for upgrading?

http://www.netbsd.org/releases/formal.html says "There is also typically 
an upgrade procedure to bring a system from the previous formal release to 
the current one."

I think this should link to the documentation for this. Where is it? If it 
is several documents, then maybe at least tell the reader where to look 
for this "upgrade procedure".

http://www.netbsd.org/releases/release-map.html#maintenance says "The 
maintenance branch(es) can be considered an easy way to get the most up to 
date fixes for a given release."

What is this easy way? What should this webpage link to or say?

I have a remote NetBSD/i386 3.1 (GENERIC kernel) system to consider 
upgrading. And I don't want to upgrade using src. The steps chould be:

- download desired sets
- move old kernel and install new kernel
- install new boot loader files??
- reboot using new kernel (if upgrading to new major/formal release only?)
- extract sets, preserving modes
- run postinstall
- run etcupdate
- reboot again

- or use sysinst to upgrade? (what about reboot between kernel steps if 
new major/formal release upgrade?)

By the way, one NetBSD developer told me that for his remote automated
(Continue reading)

Permalink | Reply | 0 comments |

Gmane