Bug#26510: marked as done (rootdisk: unconfigured.sh uses a heredoc, which fails badly if / is ro)
Your message dated 27 Jan 1999 17:36:15 -0500
with message-id <oaiuds5oo0.fsf@burrito.fake>
and subject line bugs closed in boot-floppies ver 2.1.5
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'm
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Ian Jackson
(administrator, Debian bugs database)
Received: (at submit) by bugs.debian.org; 7 Sep 1998 21:24:15 +0000
Received: (qmail 1649 invoked from network); 7 Sep 1998 21:24:14 -0000
Received: from bigbang.generation.net (205.205.118.5)
by debian.novare.net with SMTP; 7 Sep 1998 21:24:14 -0000
Received: from localhost (portX43.lanzen.net [205.205.70.62])
by bigbang.Generation.NET (8.8.7/8.8.7) with SMTP id RAA23645;
Mon, 7 Sep 1998 17:24:11 -0400 (EDT)
Message-Id: <199809072124.RAA23645@bigbang.Generation.NET>
Received: by localhost (sSMTP sendmail emulation); Mon, 7 Sep 1998 17:24:08 -0400
Date: Mon, 7 Sep 1998 17:24:08 -0400
From: "Gregory S. Stark" <gsstark@mit.edu>
Subject: rootdisk: unconfigured.sh uses a heredoc, which fails badly if / is ro
To: submit@bugs.debian.org
X-Mailer: bug 3.1.5
Package: rootdisk
Version: N/A
I'm not completely sure whether this has to do with rootdisk, or some package
that generates the install disks. If this is the wrong place to report it
please move it.
I installed a friend's machine the other day, and ran into a terrible
situation. The machine was still not configured, so there was a script called
unconfigured.sh which was supposed to print some instructions about what went
wrong. However it used a heredoc (the <<EOF sh construct) which doesn't work
when / is mounted read-only. Instead it caused the boot process to fail and the
machine to reboot; I couldn't even get a root shell to investigate the problem.
I did solve the problem eventually, but this is a very bad situation for
someone not comfortable with linux and boot disks to face.
greg
-- System Information
Debian Release: 2.0
Kernel Version: Linux portX43.lanzen.net 2.0.36-pre7 #2 Sun Sep 6 17:20:30 EDT 1998 i586 unknown
Reply to: