Date: Wed, 01 Apr 2015 21:21:33 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-doc@FreeBSD.org Subject: [Bug 199103] 10.1 boot(8) docs loacking and/or inaccurate Message-ID: <bug-199103-9@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199103 Bug ID: 199103 Summary: 10.1 boot(8) docs loacking and/or inaccurate Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Documentation Assignee: freebsd-doc@FreeBSD.org Reporter: heas@shrubbery.net Speaking largely about 10.1-RELEASE: boot(8) & https://www.freebsd.org/cgi/man.cgi?query=boot%288%29 missing reference material for zfsloader and zfs device information, such as for currdev. zfsloader(8) missing; s.b. link to loader(8) documentation for boot.config appears to be wrong, at least for zfs bootblocks. For example, '# echo "-D -S 115200 " > /boot.config' from manpage or https://www.freebsd.org/doc/handbook/serialconsole-setup.html results in a host that stops after loading the bootblocks, as in: >> FreeBSD/i386 BOOT Default: 0:ad(0,a)/boot/loader boot: then you face the zfs-related documentation issues. /boot/zfsloader -D -S 115200 does not work either. rpool:/boot/zfsloader -D -S 115200 also not. zfs:rpool:/boot/zfsloader -D -S 115200 also not. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-199103-9>