On Tue, Jun 22, 2004 at 03:09:18PM +0200, Bjoern Koenig wrote:
> Hello,
>
> first of all:
>
> THIS FILESYSTEM TYPE IS NOT YET FULLY SUPPORTED
> (READ: IT DOESN'T WORK) AND USING IT MAY, IN FACT,
> DESTROY DATA ON YOUR SYSTEM. USE AT YOUR OWN RISK.
> BEWARE OF DOG. SLIPPERY WHEN WET.
Right, but t
On Tue, 22 Jun 2004, Bjoern Koenig wrote:
Hello,
first of all:
THIS FILESYSTEM TYPE IS NOT YET FULLY SUPPORTED
(READ: IT DOESN'T WORK) AND USING IT MAY, IN FACT,
DESTROY DATA ON YOUR SYSTEM. USE AT YOUR OWN RISK.
BEWARE OF DOG. SLIPPERY WHEN WET.
My experience:
I had much less problems with unionfs
Hello,
first of all:
THIS FILESYSTEM TYPE IS NOT YET FULLY SUPPORTED
(READ: IT DOESN'T WORK) AND USING IT MAY, IN FACT,
DESTROY DATA ON YOUR SYSTEM. USE AT YOUR OWN RISK.
BEWARE OF DOG. SLIPPERY WHEN WET.
My experience:
I had much less problems with unionfs -b, even with FreeBSD 4.10, to mount
On Mon, Jun 21, 2004 at 11:05:07PM +0200, Eirik Oeverby wrote:
> Hi,
>
> Since upgrading to 4.10-ish (cvsup), nullfs (mount_null) causes my
> jailing host to panic and reboot very frequently. I've been using nullfs
> for about a year now, up until and including 4.9 and beyond, and I have
> neve
On Mon, 21 Jun 2004, Eirik Oeverby wrote:
Hi,
Since upgrading to 4.10-ish (cvsup), nullfs (mount_null) causes my jailing
host to panic and reboot very frequently. I've been using nullfs for about a
year now, up until and including 4.9 and beyond, and I have never had
problems with it. It has bee