From: Hans Zoebelein <hzo@gmx.de>
To: blinux-list@redhat.com
Subject: Re: General linux list for newbies
Date: Wed, 29 Nov 2000 22:53:52 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.21.0011292251360.2753-100000@goldfish> (raw)
In-Reply-To: <200011290038.QAA16506@sugarbeet.ultimanet.com>
Thx for the correction.
The error was corrected yesterday.
--Hans
On Tue, 28 Nov 100, Gary Wynn wrote:
> Hans---It looks like this should be changed in the FAQ. Thanks, Gary
>
> >
> > Use vger.kernel.org that machine had a failure and it moved to kernel.org,
> > had a post on linux-tape about that awhile back.
> > At 05:53 PM 11/27/00 -0800, you wrote:
> > >Hi,
> > >
> > >In the Blinux.faq, it says:
> > >
> > > 2.2 Q: Where can I find answers for general Linux problems?
> > >
> > > A: Linux-l@mana.landofhaze.com (mail listserv@mana.landofhaze.com and
> > > type subscribe linux-l to subscribe) and linux-newbie@vger.rutgers.edu
> > > (mail majordomo@vger.rutgers.edu and type subscribe linux-newbie to
> > > join) are two general-purpose mailing lists.
> > >
prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Gary Wynn
` Brent Harding
` Gary Wynn
` Hans Zoebelein [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0011292251360.2753-100000@goldfish \
--to=hzo@gmx.de \
--cc=blinux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).