headers
Jean-Yves Migeon | 13 Jul 2008 23:01
Picon

boot(8), kprintf(9), boothowto and code comments

Hi list,

While browsing through boot code (for Xen), I did not find any man page 
talking about the boothowto variable and boot flags which control the 
aprint_*() functions' verbosity. After looking for them for maybe 10 
min, I did not see anything.

Just to fix it, anyone would be so kind to comment the attached diff, 
and see if we could find some way to commit this info?

Please cc me on reply.

Cheers,

--

-- 
Jean-Yves Migeon
jean-yves.migeon <at> espci.fr
Attachment (boot.8.diff): text/x-patch, 1557 bytes
Attachment (kprintf.9.diff): text/x-patch, 774 bytes
Permalink | Reply | 1 comment |
headers
James K. Lowden | 14 Jul 2008 00:50
Gravatar

Re: boot(8), kprintf(9), boothowto and code comments

Jean-Yves Migeon wrote:
> the boothowto variable

Oh, dear me.  Why wasn't it called the "howtoboot" variable?  

Backwards ran the sentence until reeled the mind.  

--jkl
Permalink | Reply | 0 comments |
headers
Petar Bogdanovic | 31 Jul 2008 13:57

16.3.8. Migrating System to RAID

Hi,

from time to time I have to migrate a system to RAIDframe and since this
is not a daily task I often forget every step and have to reread chapter
16 of the NetBSD guide.

Every time I do this, the following pax(1) example confuses me:

	16.3.8. Migrating System to RAID

	The new RAID filesystems are now ready for use. We mount them under /mnt
	and copy all files from the old system. This can be done using dump(8)
	or pax(1).

	# mount /dev/raid0a /mnt
	# df -h /mnt
	Filesystem    Size     Used     Avail Capacity  Mounted on
	/dev/raid0a   9.0G     2.0K      8.6G     0%    /mnt
	# cd /; pax -v -X -rw -pe / /mnt
	[...snip...]

Since the rw-synopsis of pax goes something like:

	pax -r -w (...) [file ...] directory

users will use pax with a `cd'-prefix and a `.' as file in the common
case when one wants to copy the content of a directory into another
directory.

So I'm pretty sure that the following two versions would be a better
(Continue reading)

Permalink | Reply | 0 comments |

Gmane