Your message dated Mon, 17 May 2004 19:59:07 -0700
with message-id <[EMAIL PROTECTED]>
and subject line fixed a while ago
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.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 26 Dec 2002 11:12:30 +0000
>From [EMAIL PROTECTED] Thu Dec 26 05:12:29 2002
Return-path: <[EMAIL PROTECTED]>
Received: from (bowl.fysh.org) [81.5.149.242] (mail)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 18RVwD-0005kJ-00; Thu, 26 Dec 2002 05:12:29 -0600
Received: from zefram by bowl.fysh.org with local (Exim 3.35 #1 (Debian))
id 18RVwC-00020x-00; Thu, 26 Dec 2002 11:12:28 +0000
Date: Thu, 26 Dec 2002 11:12:28 +0000
To: [EMAIL PROTECTED]
Subject: insufficient choice for boot loader location
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
From: Zefram <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-4.6 required=5.0
tests=SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_MUTT
version=2.41
X-Spam-Level:
Package: install
Version: woody
After the installer has put together a minimal system, there is a stage
where it wants to install a boot loader, in preparation to boot the new
system. The usual process is to install LILO's boot sector somewhere on
a hard drive. The installer gives a menu of possible locations for LILO,
but the menu isn't extensive enough.
The machine I've just been installing Debian on has three IDE hard drives,
/dev/hd{a,b,c}, of which only /dev/hdb was initially to be used for the
Debian install. Installing the base system worked, but the LILO install
menu looked something like:
/dev/hda Install LILO in the MBR (use this if unsure).
/dev/hdb1 Install LILO in the root partition's boot sector.
Apparently someone thinks that the computer has only one MBR, which
was news to me since I had been planning to install LILO in the MBR
on /dev/hdb. (The BIOS on this machine can be configured to boot from
*any* of the fixed disks, in addition to removable media.)
Now, the MBR of the first disk is a good default location for the boot
loader. I don't want to change that aspect of the menu. There are two
things that I think ought to change in the menu. Firstly, that option
ought to be labelled accurately, as "the MBR of the first disk" rather
than simply "the MBR".
Secondly, there *must* be some way to install LILO in a location other
than the two locations that are (quite reasonably) suggested. One way
to do this would be to extend the menu with other options, such as "the
MBR of the disk containing the boot partition" (which is what I wanted).
But that would get unwieldy if one tried to cover every possibility;
e.g., I could conceivably have wanted LILO in the MBR on /dev/hdc.
What I suggest instead is an option of "somewhere else (please specify)",
which would then ask for a device name to pass to LILO.
Style gurus may now debate whether the type-in location thing should
actually be the only way to specify where to install LILO. It could
default to the first disk, with explanatory text describing the reasonable
alternatives. This would be, I think, stylistically consistent with
most other configuration options in the installer.
A friend of mine suggested that I could have worked around the
excessively restrictive menu by switching to the shell on tty2 and
running LILO manually. I had indeed discovered the shell, and had a
look around the install environment. (Thanks, btw, for making the shell
available right at the beginning of installation. One of my gripes with
Red Hat's installer is that one has to get past a couple of troublesome
configuration screens before the shell is started.) I didn't consider
running LILO manually because, this being an install process, I had no
expectation that LILO would be run in the normal manner, with the config
file in the normal place, such that I could apply my knowledge of LILO
to modify the configuration. If this kind of workaround is intended
to be available, it would be nice if the install manual could mention
which parts of the install can sensibly be done manually.
-zefram
---------------------------------------
Received: (at 174348-done) by bugs.debian.org; 18 May 2004 02:59:08 +0000
>From [EMAIL PROTECTED] Mon May 17 19:59:08 2004
Return-path: <[EMAIL PROTECTED]>
Received: from smtp804.mail.sc5.yahoo.com [66.163.168.183]
by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
id 1BPuou-0007Ru-00; Mon, 17 May 2004 19:59:08 -0700
Received: from unknown (HELO triplehelix.org) ([EMAIL PROTECTED]@68.126.213.94 with
login)
by smtp804.mail.sc5.yahoo.com with SMTP; 18 May 2004 02:59:08 -0000
Received: from darjeeling.triplehelix.org (darjeeling.wifi.triplehelix.org
[192.168.0.7])
by triplehelix.org (Postfix) with ESMTP id B379E2DF23
for <[EMAIL PROTECTED]>; Mon, 17 May 2004 19:59:07 -0700 (PDT)
Received: from joshk by darjeeling.triplehelix.org with local (Exim 3.36 #1 (Debian))
id 1BPuot-000714-00
for <[EMAIL PROTECTED]>; Mon, 17 May 2004 19:59:07 -0700
Date: Mon, 17 May 2004 19:59:07 -0700
To: [EMAIL PROTECTED]
Subject: fixed a while ago
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="7AUc2qLy4jB3hD7Z"
Content-Disposition: inline
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report/>.
User-Agent: Mutt/1.5.6i
From: Joshua Kwan <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
--7AUc2qLy4jB3hD7Z
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Zefram,
I've more or less restored the lilo-installer selection stage to the way
it was in Woody. It offers a selection of MBR of first disk, partition
where you installed Debian, and an 'other' choice where you can type in
whatever you want. This was back in 0.40, i'm just triaging old bugs.
I hope this conclusion is satisfactory.
Thanks for reporting!
--=20
Joshua Kwan
--7AUc2qLy4jB3hD7Z
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: http://triplehelix.org/~joshk/pubkey_gpg.asc
iQIVAwUBQKl7+6OILr94RG8mAQKUjA//cHUf7yxKev+Q5XitVLCknJn2Ervm1pd2
HtRga0XrK/ZPjUW0O4GPcVDB48Db7wwwaV6vuPajk6zOjdlU1BtWsuS/mRxzSI05
BnRwCWepTnts4DyvnS/O5jcUDkYjPtLbQXJbsbR+un6gGqDbBpYC1C3YNBpiS4ZE
Xmlc7VPoNsN8aSbXiGlwPn9no3p1mdNWGcXtZmZQFJhF4rWS25DIJnrg4wqsVzhC
T2OyuqHHZdwcP3Woj8MrmNdyBWYpfGJBP+kJ5R04DSEyoDkgoNWcMRkTcknpZgw9
FtWJPJdPaRBrYgWSDOKZT1rJA/dUyEGfWMRIcXIND7tMqlLQ7aXwymZotStk83dk
oHH/9M1ofL33IkFKAFrRKy/l5JFhz+vDqiQZhHdsU8AMmQuJihjZgUvJbNUbdUqw
J4rDMKVnbrAWY3m16XavYisEXA8zJacLHr63Q/wZ29GRPRdW6S0uFReNYIhU5wus
k4aTlecvG/NRJJlivPghsWroNh/YhdUFW0SgMRJmwDyQRKLdB5lHEZGVS4GPiMan
kwDcTOx1AZOQabExgOzTA+fmIwXCf3VnKEPkYvcV+6bVTmuV0cFnmvgkZMTpEw8e
aR1EXIjUBMur8rXZsXA1IJGRINXfZNBBcE0OgBRsVK4LIl+I6909wbi9ZZKH3X2S
cV9/8eF+70E=
=lr25
-----END PGP SIGNATURE-----
--7AUc2qLy4jB3hD7Z--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
