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:[EMAIL PROTECTED])
"In jedem St�ck Kohle wartet ein Diamant auf seine Geburt"
(Terry Pratchett)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
- People getting automatically unsub'ed from -arch Brian Somers
- Re: The eventual fate of BLOCK devices. Matthew Dillon
- Re: The eventual fate of BLOCK devices. Kirk McKusick
- Re: The eventual fate of BLOCK devices. David Scheidt
- Re: The eventual fate of BLOCK devices. Warner Losh
- Re: The eventual fate of BLOCK device... Peter Wemm
- Re: The eventual fate of BLOCK device... Chuck Robey
- Re: The eventual fate of BLOCK devices. Jonathan M. Bresler
- Re: The eventual fate of BLOCK devices. Chuck Robey
- Re: The eventual fate of BLOCK devices. Julian Elischer
- Re: The eventual fate of BLOCK devices. Oliver Fromme
- Re: The eventual fate of BLOCK devices. Jonathan M. Bresler
- Majordomo problems (Re: The eventual fate of BLOC... Peter Jeremy
- Re: Majordomo problems (Re: The eventual fate... Jonathan M. Bresler
- Re: The eventual fate of BLOCK devices. Oliver Fromme
- Re: The eventual fate of BLOCK devices. Jonathan M. Bresler
- Re: The eventual fate of BLOCK devices. Archie Cobbs
