From: ichi@ihug.co.nz
To: linux-newbie <linux-newbie@vger.kernel.org>
Subject: Re: Debian install issue
Date: Thu, 10 Oct 2002 07:56:35 +0000 [thread overview]
Message-ID: <3DA532B3.29A7FF20@ihug.co.nz> (raw)
In-Reply-To: Pine.LNX.4.44.0210091223130.6549-100000@localhost.localdomain
> On 9 Oct 2002, Ray Olszewski wrote:
>
> > As to Slackware (and btw, what does "survpc-friendly" mean?)
survpc = survivor PC = sub-Pentium PC
Slackware is survpc-friendly because even the latest version (8.1)
runs on a 386, provides a low-mem kernel for systems with less
than 8mb RAM and supports old non-IDE CDroms. And (incredibly)
it even supports pre-IDE (two cable) harddrives and MicroChannel
systems. I know of no other up-to-date, mainsteam distro that
provides that much upfront support for old hardware.
Cheers,
Steven
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2002-10-10 7:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0210091108330.6549-100000@localhost.localdom ain>
2002-10-09 17:03 ` Debian install issue Ray Olszewski
2002-10-09 17:49 ` James Miller
2002-10-09 18:01 ` Paul Kraus
2002-10-09 18:40 ` Jim Reimer
2002-10-09 19:23 ` Ray Olszewski
2002-10-10 7:56 ` ichi [this message]
2002-10-09 18:18 Little, Chris
-- strict thread matches above, loose matches on Subject: below --
2002-10-09 16:14 James Miller
2002-10-08 1:07 Identifying computers behind a NAT Lee Chin
2002-10-08 2:18 ` Debian install issue James Miller
[not found] ` <Pine.LNX.4.44.0210072054390.6549-100000@localhost.localdom ain>
2002-10-08 2:29 ` Ray Olszewski
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=3DA532B3.29A7FF20@ihug.co.nz \
--to=ichi@ihug.co.nz \
--cc=linux-newbie@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.