From owner-freebsd-current Sun Oct 10 15:36:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 7522E150E4 for ; Sun, 10 Oct 1999 15:35:42 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id AAA07769 for freebsd-current@freebsd.org; Mon, 11 Oct 1999 00:35:41 +0200 (CEST) (envelope-from olli) Date: Mon, 11 Oct 1999 00:35:41 +0200 (CEST) From: Oliver Fromme Message-Id: <199910102235.AAA07769@dorifer.heim3.tu-clausthal.de> To: freebsd-current@freebsd.org Subject: Re: The eventual fate of BLOCK devices. Organization: Administration Heim 3 Reply-To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams wrote in list.freebsd-current: > Interesting. It appears that somehow I got 'unsubscribed' from arch. > Not sure why, but in May I was subscribed, but I'm no longer subscribed. > > Did everyone get unsubscribed when it went idle? FWIW, I got unsubscribed, too. While I were at it, I sent a "which" command to the majordomo, and the result did not list me as a member of freebsd-announce and freebsd-security- notifications. When I tried to re-subscribe, it told me that I am already subscribed... Seems like majordomo is major buggy. ;-) Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message