Date: Wed, 20 May 2015 22:16:12 +0300 From: Slawa Olhovchenkov <slw@zxy.spb.ru> To: Allan Jude <allanjude@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD Boot Environments Message-ID: <20150520191612.GC21070@zxy.spb.ru> In-Reply-To: <555CD1DB.6010807@freebsd.org> References: <20150520181006.GB21070@zxy.spb.ru> <555CD1DB.6010807@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 20, 2015 at 02:26:35PM -0400, Allan Jude wrote:
> On 2015-05-20 14:10, Slawa Olhovchenkov wrote:
> > I am try to use Boot Environments and have some misundertanding.
> > As I see beadm manage only zroot/ROOT. But base upgrade touch not only
> > /{boot,etc,bin,lib,libexec,rescue,sbin} but also /usr and from time to
> > time /var. And don't touch (at most) /root.
> >
> > What correct way to use Boot Environments?
> > Rename zfs datasets as:
> >
> > From To
> > zroot/usr zroot/ROOT/default/usr
> > zroot/usr/home zroot/home
> >
> > create
> >
> > zroot/root
> >
> > leave (rename after moving zroot/usr)
> >
> > zroot/usr/ports
> > zroot/usr/src
> > zroot/usr/local
> >
> > Or somehow else?
> >
> > How prepare upgrades for such install?
> >
> > Create model setup, witch similar enviroment
> > zfs snap modelroot@N
> > do install{world,kernel} DESTDIR=/modelroot
> > do mergemaster -I -U -D /modelroot
> > zfs send -i N-1 modelroot@N | ssh host zfs recv zroot/ROOT/new
> >
> > Or somehow else?
> > _______________________________________________
> > freebsd-hackers@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
> >
>
> The typical way (done by bsdinstall) is that your zroot/usr dataset, is
> set 'canmount=off', and only exists for you to create child datasets.
>
> Any files written to /usr/bin etc, actually end up going to the
> ROOT/default dataset
>
> you can tell by looking at 'zfs list' and your zroot/usr is only like
> 200kb, instead of 100s of megabytes. It also won't be listed in the
> output of 'mount'.
Yes, I see. Thanks.
What about creating zroot/root?
What about send/recv? And how I can have localy changed
/boot/loader.conf, /etc/rc.conf and other /etc/ files?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150520191612.GC21070>