[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[patch] Booting and the MULTIBOOT_CMDLINE

From: Neal H Walfield
Subject: [patch] Booting and the MULTIBOOT_CMDLINE
Date: Tue, 14 Aug 2001 16:58:35 +0200
User-agent: Mutt/1.3.18i

When booting a sub Hurd, and unlike booting a Hurd via serverboot, the
environment variable MULTIBOOT_CMDLINE is not set.  This brings out a
latent bug in /libexec/runsystem.sh:  if MULTIBOOT_CMDLINE is unset, it
assumes that something is wrong and goes into single user mode.  As far
as I can tell, this is wrong;  runsystem should continue as if the
MULTIBOOT_CMDLINE was empty.  This patch corrects this.


2001-08-08  Neal H Walfield  <neal@cs.uml.edu>

        * runsystem.sh: Do not fail if MULTIBOOT_CMDLINE is unset.

Index: daemons/runsystem.sh
RCS file: /cvs/hurd/daemons/runsystem.sh,v
retrieving revision 1.1
diff -u -p -r1.1 runsystem.sh
--- daemons/runsystem.sh        1999/06/18 22:04:58     1.1
+++ daemons/runsystem.sh        2001/08/14 10:30:42
@@ -63,8 +63,6 @@ if [ "${FALLBACK_CONSOLE+set}" = set ]; 
   singleuser "Running on fallback console ${FALLBACK_CONSOLE}"
 elif [ $# -ne 0 ]; then
   singleuser "Unexpected arguments: $*"
-elif [ "${MULTIBOOT_CMDLINE+set}" != set ]; then
-  singleuser "No multiboot command line!"

Attachment: pgpWRWQCJllz1.pgp
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]