Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 14 Feb 2004 11:09:00 +0000
From:      Matthew Seaman <m.seaman@infracaninophile.co.uk>
To:        Gary Kline <kline@thought.org>
Cc:        FreeBSD Mailing List <freebsd-questions@freebsd.org>
Subject:   Re: MFS on new server.
Message-ID:  <20040214110900.GA64281@happy-idiot-talk.infracaninophile.co.uk>
In-Reply-To: <20040214104818.GA59107@tao.thought.org>
References:  <20040214104818.GA59107@tao.thought.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--CE+1k2dSO48ffgeK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Feb 14, 2004 at 02:48:18AM -0800, Gary Kline wrote:

> 	When my new DNS server is finished I'm planning to create
> 	around a 512MB memory file system.  An Onlamp article gives
> 	some basics.  But how would I cp (say), gcc, sendmail, and
> 	bind to this new fs?  Or am I looking at this the wrong way?

Unless you're talking about a vnode backed MFS (as generated by
vnconfig(8) on 4.x or 'mdconfig -t vnode' with 5.x's generic
mdconfig(8) command) you're going to have to rebuild everything you
put onto the MFS every time you recreate it.  That's not the usual way
of doing things -- generally a MFS is used for ephemeral data created
as the application runs.

On the other hand, if you're running on a vnode backed setup, then
=66rom the point of view of populating it with files, it's just like any
other filesystem.
=20
> 	Any advice, tips, or sharing will be greatly appreciated.

Hmmm... Well, the copying can be done by all manner of means.
rsync(1), tar(1), find(1)/cpio(1) spring to mind.  pkg_add(1) works
well -- maybe with a modified $PREFIX.  Building a custom package
containing everything you want to install in your MFS so that you can
just re-install it at will would be quite a nifty idea.  Even cp(1).
If you're using a vnode backed area for a thick jail(8), then you can
install a base system on it by:

    # make installworld DESTDIR=3D/jail/192.168.0.2

(assuming that's where you mount your jail...)  If you then either do
a loopback nfs mount or a null mount of /usr/ports onto the jail (see
mount_nfs(8), mount_null(8)), or even just install a separate copy of
/usr/ports, you can compile and install ports from within the jail as
just if you were in the base system.

	Cheers,

	Matthew

--=20
Dr Matthew J Seaman MA, D.Phil.                       26 The Paddocks
                                                      Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey         Marlow
Tel: +44 1628 476614                                  Bucks., SL7 1TH UK

--CE+1k2dSO48ffgeK
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFALgHMdtESqEQa7a0RAu27AKCRuT0YSXrvmtfk5jgAFLvR15SpDgCaAqGM
tNzyoR6XA6wpPhvQBXI/Uzo=
=j5F+
-----END PGP SIGNATURE-----

--CE+1k2dSO48ffgeK--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040214110900.GA64281>