Date: Mon, 1 Mar 2010 22:03:32 +0000 From: xorquewasp@googlemail.com To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= <des@des.no> Cc: Greg Larkin <glarkin@FreeBSD.org>, freebsd-hackers@FreeBSD.org Subject: Re: package building failure irritation Message-ID: <20100301220332.GB74816@logik.internal.network> In-Reply-To: <86635frhaa.fsf@ds4.des.no> References: <20100226163227.GA15162@logik.internal.network> <4B88074E.7050007@FreeBSD.org> <20100226222113.GA14592@logik.internal.network> <4B884D48.90509@FreeBSD.org> <20100227093409.GA40858@logik.internal.network> <864ol0w4g5.fsf@ds4.des.no> <20100301135829.GB2219@logik.internal.network> <86zl2suo8n.fsf@ds4.des.no> <20100301161901.GC2219@logik.internal.network> <86635frhaa.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
'Lo, Here's the current state of '/work': http://coreland.ath.cx/tmp/work.txt On 2010-03-01 20:08:45, Dag-Erling Smørgrav wrote: > That's begging the question... Clearly you're using nullfs because you > need something done that you think nullfs can do for you. I'd like to > know what that is, because I suspect that you don't actually need it, > and it might be the source of your problems. I agree, ZFS likely has something to replace my use of nullfs. I used it previously to do the following using only UFS filesystems: Basically, I have a ton of jails and each jail mounts a shared 'tmp', and possibly unshared 'pkg' 'work' 'distfiles' and 'ports' directories: /storage/jails/8.0/x86_64/mk4/pkg /jail/8.0-amd64-mk4/pkg nullfs rw /storage/jails/8.0/x86_64/mk4/work /jail/8.0-amd64-mk4/work nullfs rw /storage/distfiles /jail/8.0-amd64-mk4/distfiles nullfs rw /storage/ports /jail/8.0-amd64-mk4/ports nullfs ro /storage/shared_tmp /jail/8.0-amd64-mk4/shared_tmp nullfs rw xw
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100301220332.GB74816>