From owner-freebsd-hackers Thu Sep 28 0:49:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id CE5F637B422; Thu, 28 Sep 2000 00:49:14 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e8S7n1817835; Thu, 28 Sep 2000 00:49:01 -0700 (PDT) Date: Thu, 28 Sep 2000 00:49:01 -0700 From: Alfred Perlstein To: Danny Braniss Cc: Paul Saab , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: nfs v2 Message-ID: <20000928004901.J7553@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from danny@cs.huji.ac.il on Thu, Sep 28, 2000 at 09:35:56AM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Danny Braniss [000927 23:36] wrote: > hi, > with 4.1: there seems to be a problem with nfs2 mounts to > non freebsd hosts: > mainly, the special files - eg /dev/null - show up as something like > 0 crw-r--r-- 1 root wheel 0, 0x00200002 Sep 28 09:29 /mnt/tmp/null > > it's ok if the exporting os is freebsd, but so far: netapp, procom, bsdi > all show up to freebsd as 0, 0x00200002! btw, the problem is not with ls, > > loo> date > /mnt/tmp/null > /mnt/tmp/null: Device not configured. > loo> > > > needless to say, this is screwing up my diskless project. I'm pretty sure that device major/minor are not same across different systems. I would use an MFS or a vn device created from a FreeBSD UFS over NFS. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message