Date: Sun, 14 Jun 2009 17:44:27 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> To: freebsd-hackers@freebsd.org, FreeBSD current <freebsd-current@freebsd.org> Subject: Re: sysinstall, GJOURNAL and ZFS Message-ID: <20090614172116.C55547@ramstind.fig.ol.no> In-Reply-To: <cf9b1ee00906121507n24ec1f7dt89687ce2b85803b1@mail.gmail.com> References: <cf9b1ee00906090242h6dea1182h8e743b7ceec36c2c@mail.gmail.com> <alpine.BSF.2.00.0906091632430.6551@wojtek.tensor.gdynia.pl> <cf9b1ee00906090757v7d589dfch978076a97be724a9@mail.gmail.com> <4A2E84DC.1010900@unsane.co.uk> <d5992baf0906090958r250ae0afibd2c4320630778ba@mail.gmail.com> <cf9b1ee00906121507n24ec1f7dt89687ce2b85803b1@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--0-1121150211-1244993917=:55547
Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Content-ID: <20090614173858.M55547@ramstind.fig.ol.no>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, 13 Jun 2009 01:07+0300, Dan Naumov wrote:
> <Begin Installation> screen: The screen states that in order to do a
> manual installation "<SNIP> login as root, and follow the instructions
> given in the file /README". There is no indication regarding how the
> user is supposed to open the README file, at least ONE sane option
> should be suggested (for example: login as root and type "vi README"
> at the command prompt to read the instructions regarding installing
> FreeBSD manually.
Although longer to type, "less /README" would be a better alternative
than using vi to view the contents of the file. You could otherwise
risk the user destroying the README file due to unfamiliarity with
this particular editor.
OTOH, why not adopt OpenBSD's afterboot(8) man page?
===
Almost completely off-topic:
An /altroot mechanism would be nice to have in FreeBSD. ;-)
There are at least two schools of thought regarding /altroot.
One school of thought would be to simply dd the contents of the root
partition on to the altroot partition and run fsck on /altroot,
assuming /root and /altroot have the same size. I believe this is how
OpenBSD handles /altroot when configured to do so.
My school of thought, given a system with more than one hard drive,
physical or virtual (as in RAID volumes), is to have /altroot appear
as a regular root file system (partition a) on the other drive and
thus being able to (manually) boot from the available root file
system. Both hard drives should be made bootable with the EasyBoot
loader placed in the MBRs and with regular boot blocks in the FreeBSD
slices. Of course, /altroot should normally remain unmounted.
There is also the possible need of having /etc/fstab files with
specific contents for each root file system. For instance, /'s
/altroot should be mounted as /altroot's /. I'm not sure how to handle
this scenario with either installers as you probably need to perform
the installation twice, that's how I did it on a couple of recently
installed systems, not to mention how to handle make
install{kernel,world} for both of the two root file systems.
Just some random thoughts,
Trond.
- --
- ----------------------------------------------------------------------
Trond Endrestøl | Trond.Endrestol@fagskolen.gjovik.no
ACM, NAS, NUUG, SAGE, USENIX | FreeBSD 6.2-STABLE & Pine 4.64
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (FreeBSD)
iD8DBQFKNRrfbYWZalUoElsRAnzTAJ0StVu1t2FY1rr9JjI2MVQ0jexsAgCfZICv
kbpbqm4Vzv/vGYVTZEPwmfw=
=dPhW
-----END PGP SIGNATURE-----
--0-1121150211-1244993917=:55547--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090614172116.C55547>