Bug#69617: marked as done (there should be some statically linked tar at installtime)
Your message dated 22 Aug 2000 22:03:08 -0400
with message-id <oabsyk20pv.fsf@arroz.fake>
and subject line there should be some statically linked tar at installtime
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Darren Benham
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 21 Aug 2000 21:09:37 +0000
>From tinne@kati.ping.de Mon Aug 21 16:09:37 2000
Return-path: <tinne@kati.ping.de>
Received: from lilly.ping.de [::ffff:195.37.120.2]
by master.debian.org with smtp (Exim 3.12 1 (Debian))
id 13Qyp7-0006dw-00; Mon, 21 Aug 2000 16:09:37 -0500
Received: (qmail 27077 invoked by uid 0); 21 Aug 2000 21:09:19 -0000
Received: (ofmipd 195.37.122.68); 21 Aug 2000 21:08:57 -0000
Received: from kati.ping.de (tinne@localhost [127.0.0.1])
by kati.ping.de (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id XAA08559
for <submit@bugs.debian.org>; Mon, 21 Aug 2000 23:08:49 +0200
Date: 21 Aug 2000 23:08:48 +0200
Message-Id: <200008212108.XAA08559@kati.ping.de>
From: "Karsten Tinnefeld" <tinne@kati.ping.de>
Sender: tinne@kati.ping.de
Reply-To: "Karsten Tinnefeld" <tinnefeld@noether.cs.uni-dortmund.de>,
"Karsten Tinnefeld" <tinne@kati.ping.de>
To: submit@bugs.debian.org
X-Mailer: exmh version 2.1.1 10/15/1999 (debian)
Subject: there should be some statically linked tar at installtime
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: submit@bugs.debian.org
Package: [debian cdroms]
Version: 2.2 r0 _Potato_ - Official i386 Binary
Package: [boot disks]
Version: 2.2.16-2000-07-14
Booting a broken system from cd and using the ram disk resident kernel is a
wonderful thing for repair work - e.g. when i tried to upgrade to 2.2 last
days but my 2.1 config was too broken so that the whole system dies of an ext2
fatal error.
However, i have been missing a working "tar" binary for moving my partitions
around and making space for a scratch installation. The small tar in the
distribution cannot "c"reate archive, but this is definitely useful for
tar cf - * | (cd /some/where; tar xvfpB -)
Since gtar is quite large when linked statically, I suggest building some
additional folder on the archive cds with some tools like this - all without
library dependencies, gettext support and such fancy things, but maybe with
preformatted manpages.
What I suggested to put there else? Hmm, I am not quite aware what there is
already in the basic system, maybe mostly the fileutils, diffutils+patch
packages, ldd, fsck.ext2, (u)mount.
Congratulations to an ever so stable distribution
Karsten
---------------------------------------
Received: (at 69617-done) by bugs.debian.org; 23 Aug 2000 02:02:36 +0000
>From adam@onshore.com Tue Aug 22 21:02:36 2000
Return-path: <adam@onshore.com>
Received: from relay03.netaddress.usa.net [::ffff:204.68.24.183]
by master.debian.org with smtp (Exim 3.12 1 (Debian))
id 13RPsC-0000Z0-00; Tue, 22 Aug 2000 21:02:36 -0500
Received: (qmail 10591 invoked from network); 23 Aug 2000 02:02:35 -0000
Received: from unknown (HELO arroz.fake) (postfix@64.22.101.122)
by relay03.netaddress.usa.net with SMTP; 23 Aug 2000 02:02:35 -0000
Received: by arroz.fake (Postfix, from userid 421)
id 66D2793802; Tue, 22 Aug 2000 22:03:08 -0400 (EDT)
Sender: apharris@arroz.fake
To: 69617-done@bugs.debian.org
Subject: there should be some statically linked tar at installtime
From: Adam Di Carlo <adam@onshore.com>
Date: 22 Aug 2000 22:03:08 -0400
Message-ID: <oabsyk20pv.fsf@arroz.fake>
Lines: 32
User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: 69617-done@bugs.debian.org
> Booting a broken system from cd and using the ram disk resident kernel is a
> wonderful thing for repair work - e.g. when i tried to upgrade to 2.2 last
> days but my 2.1 config was too broken so that the whole system dies of an ext2
> fatal error.
> However, i have been missing a working "tar" binary for moving my partitions
> around and making space for a scratch installation. The small tar in the
> distribution cannot "c"reate archive, but this is definitely useful for
> tar cf - * | (cd /some/where; tar xvfpB -)
> Since gtar is quite large when linked statically, I suggest building some
> additional folder on the archive cds with some tools like this - all without
> library dependencies, gettext support and such fancy things, but maybe with
> preformatted manpages.
> What I suggested to put there else? Hmm, I am not quite aware what there is
> already in the basic system, maybe mostly the fileutils, diffutils+patch
> packages, ldd, fsck.ext2, (u)mount.
cpio, afio, bash, and many others, in fact. However, none of this is
in the cards for the boot-floppies. It's primarily an install system
and only coincidentally a rescue system.
If you want a more full rescue system I suggest the infinitely better
Tom's Boot disk or other such single floppy "distributions".
It's a good idea, but it's just not in the cards for this package.
--
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>
Reply to: