From owner-freebsd-current Sat Apr 21 11:28:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from mr200.netcologne.de (mr200.netcologne.de [194.8.194.109]) by hub.freebsd.org (Postfix) with ESMTP id A174337B422 for ; Sat, 21 Apr 2001 11:28:22 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from husten.security.at12.de (dial-213-168-88-15.netcologne.de [213.168.88.15]) by mr200.netcologne.de (Mirapoint) with ESMTP id AEC61181; Sat, 21 Apr 2001 20:27:57 +0200 (CEST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by husten.security.at12.de (8.11.3/8.11.3) with ESMTP id f3LIRpj97450 for ; Sat, 21 Apr 2001 20:27:51 +0200 (CEST) (envelope-from pherman@frenchfries.net) Date: Sat, 21 Apr 2001 20:27:51 +0200 (CEST) From: Paul Herman To: Subject: Re: /bin/df set-gid operator In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry to follow up on my own mail... On Sat, 21 Apr 2001, Paul Herman wrote: > This brings up a slightly related question: Now that block > devices have been abolished, wouldn't it be a good idea to get rid > of the quick mount(2)/umount(2) of /tmp/df.XXXXXX to stat the file > system? I see now that block type devices still pop up everywhere in the VFS system, so I'll just forget this and leave it up to the team that may someday totaly remove block device support from the kernel -- if that ever will happen. :-) -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message