Hello,
On 14-01-2007, Jeremy C. Reed <[EMAIL PROTECTED]> wrote:
> As it is now, I am confused because I never heard of null(4) for /dev/null
> being a kernel module.
>
> Anyone have a nullfs(4) manual page?
Those are different beasts: see mount_null(8).
Regards,
Francis
Jeremy C. Reed wrote:
It's a typo in the default loader.conf, I guess. I'll fix it along with some
other stuff.
I may misunderstand still...
I think the loader.conf is probably correct, but the kernel object should
be called nullfs.ko?
As it is now, I am confused because I never heard of nu
On Sun, 14 Jan 2007, Sascha Wildner wrote:
> Jeremy C. Reed wrote:
> > Is "nullfs" same as "null"? If so, how is loader configuration called
> > nullfs_load while file is null.ko?
>
> nullfs == null.ko
>
> It's a typo in the default loader.conf, I guess. I'll fix it along with some
> other stuff
Jeremy C. Reed wrote:
Is "nullfs" same as "null"? If so, how is loader configuration called
nullfs_load while file is null.ko?
nullfs == null.ko
It's a typo in the default loader.conf, I guess. I'll fix it along with
some other stuff.
Sascha
--
http://yoyodyne.ath.cx
Why would someone use "null" kernel module?
Is "nullfs" same as "null"? If so, how is loader configuration called
nullfs_load while file is null.ko?
I see a system that has "null" listed by kldstat but nullfs_load is NO (by
default).
Why is kernel also listed in kldstat output?
Jeremy C.
