Bug#60291: marked as done (boot-floppies: stderr is unvisible)
Your message dated 15 Mar 2000 00:49:38 -0500
with message-id <oad7owhjf1.fsf@arroz.fake>
and subject line Bug#60291: boot-floppies: stderr is unvisible
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; 13 Mar 2000 13:22:03 +0000
Received: (qmail 7485 invoked from network); 13 Mar 2000 13:22:01 -0000
Received: from smtp1.plusnet.ch (HELO smtp.plusnet.ch) (root@194.158.230.8)
by master.debian.org with SMTP; 13 Mar 2000 13:22:01 -0000
Received: from localhost.. (root@pop-ls-9-4-1-dialup-218.freesurf.ch [194.230.243.218])
by smtp.plusnet.ch (8.9.1/8.9.1) with ESMTP id OAA00619;
Mon, 13 Mar 2000 14:21:48 +0100
From: tpo@spin.ch
Received: (from tpo@localhost)
by localhost.. (8.9.3/8.9.3/Debian 8.9.3-6) id OAA00563;
Mon, 13 Mar 2000 14:18:39 +0100
Date: Mon, 13 Mar 2000 14:18:39 +0100
Message-Id: <200003131318.OAA00563@localhost..>
Subject: boot-floppies: stderr is unvisible
To: submit@bugs.debian.org
X-Mailer: bug 3.3.2
Package: boot-floppies
Version: N/A
Severity: important
I'm trying to install Debian over an allready existing RH. There are errors now
and then, but the real problem is that they flush by in a split second and
that's it. I have just found out that I can do a Shift-Page-Up to scroll up
beyond the currently shown install page or error message (generic: "A problem
was encountered..." without further explanation), but this method fails also, if
I have to switch ttys to correct the problem (since then the screen history is
lost). So there seems not to be any way to find out why something failed when
something failed. No stderr redirected to some file or terminal - nothing.
So often there's no way to find out what went wrong and it seems also not th be documented, where error logs can be found.
*t
-- System Information
Debian Release: woody
Kernel Version: Linux localhost 2.2.14 #2 Fri Mar 10 15:53:42 CET 2000 i686 unknown
---------------------------------------
Received: (at 60291-done) by bugs.debian.org; 15 Mar 2000 05:07:44 +0000
Received: (qmail 16985 invoked from network); 15 Mar 2000 05:07:43 -0000
Received: from 216-164-253-50.s50.tnt6.nyw.ny.dialup.rcn.com (HELO arroz.fake) (@216.164.253.50)
by master.debian.org with SMTP; 15 Mar 2000 05:07:43 -0000
Received: by arroz.fake (Postfix, from userid 421)
id B70FB93857; Wed, 15 Mar 2000 00:49:38 -0500 (EST)
Sender: apharris@arroz.fake
To: tpo@spin.ch
Cc: 60291-done@bugs.debian.org
Subject: Re: Bug#60291: boot-floppies: stderr is unvisible
References: <200003131318.OAA00563@localhost..>
From: Adam Di Carlo <adam@onshore.com>
Date: 15 Mar 2000 00:49:38 -0500
In-Reply-To: tpo@spin.ch's message of "Mon, 13 Mar 2000 14:18:39 +0100"
Message-ID: <oad7owhjf1.fsf@arroz.fake>
Lines: 21
User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.5
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
tpo@spin.ch writes:
> I'm trying to install Debian over an allready existing RH. There are errors now
> and then, but the real problem is that they flush by in a split second and
> that's it. I have just found out that I can do a Shift-Page-Up to scroll up
> beyond the currently shown install page or error message (generic: "A problem
> was encountered..." without further explanation), but this method fails also, if
> I have to switch ttys to correct the problem (since then the screen history is
> lost). So there seems not to be any way to find out why something failed when
> something failed. No stderr redirected to some file or terminal - nothing.
>
> So often there's no way to find out what went wrong and it seems
> also not th be documented, where error logs can be found.
I'm not sure at what phase you are getting the error, but if it's
while dbootstrap is running, then the bug has already been fixed in
potato. I'm pretty sure this is what you mean so I'm closing the bug.
Thanks.
--
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>
Reply to: