From owner-freebsd-questions  Tue Aug 25 18:19:14 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA14626
          for freebsd-questions-outgoing; Tue, 25 Aug 1998 18:19:14 -0700 (PDT)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from gatekeeper.peerlogic.com (gatekeeper.peerlogic.com [204.31.26.2])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA14620
          for <freebsd-questions@FreeBSD.ORG>; Tue, 25 Aug 1998 18:19:13 -0700 (PDT)
          (envelope-from jolp@peerlogic.com)
Received: by gatekeeper.peerlogic.com; id SAA11683; Tue, 25 Aug 1998 18:16:00 +0800
Received: from unknown(204.31.26.175) by gatekeeper.peerlogic.com via smap (3.2)
	id xma011680; Tue, 25 Aug 98 18:15:49 +0800
Received: from legacy (legacy.peerlogic.com [204.31.26.190])
	by pop.peerlogic.com (8.8.5/8.8.5) with ESMTP id RAA31074
	for <freebsd-questions@FreeBSD.ORG>; Tue, 25 Aug 1998 17:46:54 -0700
Message-ID: <35E35F8A.AB3A713F@peerlogic.com>
Date: Tue, 25 Aug 1998 18:06:18 -0700
From: jolp <jolp@peerlogic.com>
Reply-To: jolp@peerlogic.com
Organization: PeerLogic, Inc.
X-Mailer: Mozilla 4.01 [en] (WinNT; U)
MIME-Version: 1.0
To: freebsd-questions@FreeBSD.ORG
Subject: null fs problem (mount_null)
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I'm running FreeBSD 2.1.0.  I know it's old, but it still works great. 
I've searched the archives and cant find a solution, so before I
possibly waste time on an upgrade just to find the fix isn't there, I
thought I'd ask first.

After spending hours trying to find lofs, I finally discovered that my
only option for mounting an lofs is to mount a null fs instead.  But
apparently that doesn't even work right.

The mount (8) man page says following:

"rdonly  The same as -r; mount the file system read-only (even the
super-user may not write it).

However, mounting with "-t null" seems to defeat the read-only option. 
If I "mount -t null -r /target /mount-point" or "mount -t null -o rdonly
/target /mount-point" I can write to the mounted file system whether I'm
root or not.

Any clues?

Regards,

-John

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message