From owner-freebsd-questions  Sat Sep  2  4:57:54 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from draenor.org (draenor.org [196.36.119.129])
	by hub.freebsd.org (Postfix) with ESMTP id 9A03137B423
	for <freebsd-questions@freebsd.org>; Sat,  2 Sep 2000 04:57:49 -0700 (PDT)
Received: from marcs by draenor.org with local (Exim 3.16 #1)
	id 13VBvN-000Jt8-00; Sat, 02 Sep 2000 13:57:29 +0200
Date: Sat, 2 Sep 2000 13:57:29 +0200
From: Marc Silver <marcs@draenor.org>
To: Network <redirect@mail.com>
Cc: freebsd-questions@FreeBSD.ORG
Subject: Re: mount_null Trouble, Please Help!!
Message-ID: <20000902135729.L48173@draenor.org>
References: <379538839.967889784957.JavaMail.root@web431-mc.mail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <379538839.967889784957.JavaMail.root@web431-mc.mail.com>; from redirect@mail.com on Sat, Sep 02, 2000 at 06:16:24AM -0400
X-Operating-System: FreeBSD 4.1-STABLE
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi there,

From the mount_null manpage:

BUGS:
     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.

Just something you might want to consider.  :)  I didn't have much luck
with mount_null either -- caused kernel panics galore.  

Cheers,
Marc

On Sat, Sep 02, 2000 at 06:16:24AM -0400, Network wrote:
> FreeBSD 4.0-STABLE / Pentium class server
> 
> First, I have reasons to use mount_null instead of a
> symlink because I am using anon FTP as well as secure
> FTP (ProFTP) which needs to be accessible via apache
> and a home dir.  Here is my problem, assume a scenario:
> 
> Original (web) directory: /somedir/www/
> Mount point: /usr/home/someuser/www/
> 
> As a generic example.  To mount I simply do the
> following:
> 
> mount_null /somedir/www/ /usr/home/someuser/www/
> 
> All works well, I can telnet in, list the directory
> etc.  Here is an example of what mount listing outputs:
> 
> /somedir/www on /usr/home/someuser/www (null, local)
> 
> However when I copy any reasonably sized binary file
> to the mount point, its completely screwed up on the
> original directory...  For example:
> 
> bash-2.03$ pwd
> /usr/home/someuser
> bash-2.03$ cp myapp.tar.gz ./www
> bash-2.03$
> 
> When I go to /somedir/www/, the file exists, and same
> size and everything, but when I copy it from /somedir
> or use download it via apache, or whatever, the file
> is invalid, its got junk in it.  Why is this?
> 
> The only way to fix the problem is for me to get on as
> root and copy it from their home to the web directory
> beforehand.. not using mount_null at all.
> 
> Please help!
> Thanks


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