Bug#37873: marked as done (Installation interruptable?)
Your message dated 23 Apr 2000 22:38:50 -0400
with message-id <oan1mk5ikl.fsf@arroz.fake>
and subject line Installation interruptable?
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; 17 May 1999 21:01:19 +0000
Received: (qmail 31963 invoked from network); 17 May 1999 21:01:19 -0000
Received: from elch.de.uu.net (192.76.144.55)
by master.debian.org with SMTP; 17 May 1999 21:01:18 -0000
Received: from allinux (pec-143.au2.d.uunet.de [149.228.251.143]:1259)
by elch.de.uu.net with SMTP (5.65+:003/3.0.2)
for <submit@bugs.debian.org>
id XAA01477; Mon, 17 May 1999 23:00:10 +0200 (MET DST)
X-zyzzy: 90%
From: Andre Langemeyer <alangemeyer@knuut.de>
To: submit@bugs.debian.org
Subject: Installation interruptable?
Date: Mon, 17 May 1999 21:29:10 +0200
X-Mailer: KMail [version 1.0.17]
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <99051722432102.00922@allinux>
Content-Transfer-Encoding: 8bit
package: bootdisk
Hello
Having installed debian on a compaq several times I discovered that the keybord
wasn't accessable after reboots.
Passing basic-installation I couldn't go on setting up root and user-accounts
because the keyboard didn't work. After rebooting again, I was left with a login
promt, having a root account with an empty password.
Though anything could handily be done by using command-line instructions
instead of following the "normal installation process", I think the
installation routine might be improved by setting up checkpoints.
Thus allowing to save and regain installation progress at any time.
Not being a programmer myself, I asked several guys on the german debian user
list, being told that the installation process is interruptable in great parts
up to first rebooting.
So I'ld like to propose it would be a good idea to make it interruptable up to
the point where dselect comes in improving it's robustness.
Since this is not really a bug, it might help to make debian a little better
than it already is.
Thanks and bye
Andre
---------------------------------------
Received: (at 37873-done) by bugs.debian.org; 24 Apr 2000 02:39:00 +0000
Received: (qmail 9399 invoked from network); 24 Apr 2000 02:38:54 -0000
Received: from amsterdam.interport.net (199.184.165.19)
by master.debian.org with SMTP; 24 Apr 2000 02:38:54 -0000
Received: from arroz.fake (postfix@209-122-225-35.s35.tnt1.nyw.ny.dialup.rcn.com [209.122.225.35])
by amsterdam.interport.net (8.8.5/8.8.5) with ESMTP id WAA02397
for <37873-done@bugs.debian.org>; Sun, 23 Apr 2000 22:38:51 -0400 (EDT)
Received: by arroz.fake (Postfix, from userid 421)
id 2C95793802; Sun, 23 Apr 2000 22:38:51 -0400 (EDT)
Sender: apharris@arroz.fake
To: 37873-done@bugs.debian.org
Subject: Installation interruptable?
From: Adam Di Carlo <adam@onshore.com>
Date: 23 Apr 2000 22:38:50 -0400
Message-ID: <oan1mk5ikl.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
> Having installed debian on a compaq several times I discovered that the keybord
> wasn't accessable after reboots.
>
> Passing basic-installation I couldn't go on setting up root and user-accounts
> because the keyboard didn't work. After rebooting again, I was left with a login
> promt, having a root account with an empty password.
>
> Though anything could handily be done by using command-line instructions
> instead of following the "normal installation process", I think the
> installation routine might be improved by setting up checkpoints.
> Thus allowing to save and regain installation progress at any time.
We believe these issues have been fixed in the potato boot-floppies,
thus, we are closing these bugs. Now there are specific sub-areas
which could use improvement. If you identify these which are still
not addressed in potato, we would appreciate it if you would file
another bug for that.
--
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>
Reply to: