From owner-freebsd-questions Mon Jun 22 00:54:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA11840 for freebsd-questions-outgoing; Mon, 22 Jun 1998 00:54:28 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from post.mail.demon.net (post-11.mail.demon.net [194.217.242.40]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA11763 for ; Mon, 22 Jun 1998 00:54:01 -0700 (PDT) (envelope-from freebsd-root@i-zone.demon.co.uk) Received: from (i-zone.demon.co.uk) [158.152.227.78] by post.mail.demon.net with smtp (Exim 1.82 #2) id 0yo1QN-0006Tq-00; Mon, 22 Jun 1998 07:54:00 +0000 Message-ID: Date: Mon, 22 Jun 1998 08:16:01 +0100 To: freebsd-questions@FreeBSD.ORG From: John Subject: Re: Emptying the "bit bucket" References: <199806220459.OAA17010@mail.wr.com.au> In-Reply-To: <199806220459.OAA17010@mail.wr.com.au> MIME-Version: 1.0 X-Mailer: Turnpike (32) Version 4.00 beta 5 <5jmCrxUbpyYdwGXid1yqlWD9$N> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199806220459.OAA17010@mail.wr.com.au>, Gary Harris writes > > > What exactly does "emptying the bit bucket" entail? I received >a message on >start-up asking me to do this. > Bizarre. Can you post the error message? The 'bit bucket' as it is sometimes called, is /dev/null. It always returns 0 to a write. Consequently, it is always 'empty'. John "Tough on causes and tough on the causes of causes" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message