[1498] in linux-announce channel archive

home help back first fref pref prev next nref lref last post

Re: when problems happen

daemon@ATHENA.MIT.EDU (David S. Miller)
Sat Jan 13 17:33:03 1996

Date: 	Fri, 12 Jan 1996 00:02:40 -0500
From: "David S. Miller" <davem@caip.rutgers.edu>
To: a_alonso@iastate.edu
CC: vger-helpers@vger.rutgers.edu, linux-announce@vger.rutgers.edu
In-reply-to: <9601080412.AA21530@pv0556.vincent.iastate.edu>
	(a_alonso@iastate.edu)

   Date: Sun, 07 Jan 1996 22:12:33 CST
   From: "Alberto Alonso (Albund)" <a_alonso@iastate.edu>

   For one I am one that appreciates the work you are doing. It is people
   like you that keep the Linux project alive, and that is something we
   must never forget.

Thanks.

   I don't know how feasable this is, but you could setup a name that
   people could finger to. This way they would know which problems have
   been reported and which ones you need more info on.

Requirement 1, must not be run on vger.  Anything that increases vgers
load I balk at as you can imagine, loads of 60 are not funny ;-)

   A diferent aproach would be a mailing list that reports problems, this
   way people could send mail to the list asking for which problems have
   been reported and see if theirs is in the list.

Again, would have to not be on vger.  I have gotten some good ideas
and people volunteering to run a web site with uptodate information.
Basically they would have a "vger status" homepage.  I'd send them a
formatted mail twice a day with whats up with vger information and
they'd transform it into html some how.  Things are in the works for
this.

Later,
David S. Miller
davem@caip.rutgers.edu


home help back first fref pref prev next nref lref last post