Quoting Gijs Nijholt <[EMAIL PROTECTED]>:

> What's particularly strange, it's that the command (/sbin/mount_null)
> exists, but on executing the following command:
> [EMAIL PROTECTED]> sudo mount_null /extended/ /home/gijs/fileserver/
> ...I get the following error:
> mount_null: /home/gijs/fileserver/: Filesystem not supported by kernel
>
> Both filesystems are FFS, and it worked really well in 3.6.
> Can anyone tell me how to fix this problem?
>
> On 9/4/05, Gijs Nijholt <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
> > After some digging through mailinglist archives, it seems that
> > mount_null is no longer in the GENERIC since OpenBSD 3.7 (and
> > mount_union as well)
> > This is not mentioned in the release notes as far as I can verify.
> >
> > Why is it gone and what is the alternative?
> > (I need a way to mount my /extended partition into /home/users and
> > /var/www/users/user, which are both chrooted in respectively ftp and
> > apache)
> >
> > Or how can I get mount_null back without reinstalling the system?
> >
> > Thanks in advance.
> > Gijs Nijholt
>
>

This was planned imho, a few months after reporting this:
http://www.monkey.org/openbsd/archive/bugs/0404/msg00119.html
I got response from Otto that nullfs isn't supported anymore.

I think the code is to old and hasn't a maintainer to support
it any further (I could be wrong).

Take a look at mount_nullfs(8) from freebsd for example:

BUGS
     THIS FILE SYSTEM 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.

     This code also needs an owner in order to be less dangerous - serious
     hackers can apply by sending mail to <[EMAIL PROTECTED]> and announcing
     their intent to take it over.


Kind Regards,
Jimmy Scott

----------------------------------------------------------------
This message has been sent through ihosting.be
To report spamming or other unaccepted behavior
by a iHosting customer, please send a message 
to [EMAIL PROTECTED]
----------------------------------------------------------------

Reply via email to