🚀 go-pugleaf

In article <46gu4v$53j@fido.asd.sgi.com>, mdf@bluedini.asd.sgi.com (Martin
Frankel) wrote:


> Comp.sys.be will exist by the time the machine is released; I think
> that's good enough.  IMHO, the Be traffic on comp.sys.powerpc has
> degenerated greatly; there will not be much more useful information
> anywhere on Usenet until more people get their hands on the machine.

I aggree, I don't want to create an alt. group when it really looks 
like a comp.sys group will be possible in the lull between the storms of
the anouncement and when more developers start to see the machine.

I'm sorry for the mistake, and I have asked for assistance from the 
folks at group-advice@uunet.uu.net, they have pointed out a possible
issue with an employee of Be as the proponent of the group, and the
traditional non-comercial nature of newsgroups. Its possible that
if I were to have continued, many sites might have decided not to
carry the comp.sys.be group.

I have passed the torch to an independant party who will be doing the
honors. I have been told that the error does reset the clock, but
does not incur any other delays. (Phew!)

I'm not sure that it's cricket to try to regain the time, I'd rather
have Be, Inc. concidered a law abiding citizen of the net.

I was _VERY_ confused by the missive I got about the second posting
of the RFC, it took me an hour to discover the error. Jeez.

________________________________
Joseph Palmer
Director of Hardware Engineering
Be, Incorporated.