From: Matt Taggart <taggart@carmen.fc.hp.com>
To: Albert Strasheim <fullung@ilink.nis.za>
Cc: "Carlos O'Donell Jr." <carlos@megatonmonkey.net>,
parisc-linux@lists.parisc-linux.org
Subject: Don't Use base tarballs (was Re: [parisc-linux] nfsroot login problems on 720/50)
Date: Mon, 24 Sep 2001 14:37:57 -0600 [thread overview]
Message-ID: <20010924203757.BCCE337DDD@carmen.fc.hp.com> (raw)
In-Reply-To: Message from Albert Strasheim <fullung@ilink.nis.za> of "Sat, 22 Sep 2001 01:56:10 +0200." <20010922015609.A14166@dogbert.localdomain>
Albert Strasheim writes...
> Should I try the base tarball (same date... :-( ) or is that known to be
> bad too?
Neither are "bad" just out of date. As soon as we had a real installer
everyone switched over to using that. They were left there for historical
reasons.
I have moved them to an old directory to prevent confusion. No one should be
using these any more. If, for some good reason, you can't use the normal
installer process then I think the proper way to generate base tarballs now is
to use the debootstrap tool. If there's enough demand then we could generate
them and put them on the ftp site again.
--
Matt Taggart Linux Development Lab
taggart@fc.hp.com HP Linux Systems Operation
next prev parent reply other threads:[~2001-09-24 20:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-21 17:35 [parisc-linux] nfsroot login problems on 720/50 Albert Strasheim
2001-09-21 22:05 ` Carlos O'Donell Jr.
2001-09-21 23:56 ` Albert Strasheim
[not found] ` <20010922125826.C6488@megatonmonkey.net>
2001-09-23 14:00 ` Albert Strasheim
2001-09-23 17:55 ` Carlos O'Donell Jr.
2001-09-23 21:15 ` Albert Strasheim
2001-09-23 22:33 ` [parisc-linux] 720/50 - Out of options Carlos O'Donell Jr.
2001-09-24 20:37 ` Matt Taggart [this message]
2001-09-24 22:47 ` Don't Use base tarballs (was Re: [parisc-linux] nfsroot login problems on 720/50) Albert Strasheim
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=20010924203757.BCCE337DDD@carmen.fc.hp.com \
--to=taggart@carmen.fc.hp.com \
--cc=carlos@megatonmonkey.net \
--cc=fullung@ilink.nis.za \
--cc=parisc-linux@lists.parisc-linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox