Bug#53113: marked as done (hard to install to secondary disk)
Your message dated 15 Mar 2000 03:04:14 -0500
with message-id <oa3dpsfym9.fsf@arroz.fake>
and subject line bugs fixed in previous upload
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; 20 Dec 1999 03:45:34 +0000
Received: (qmail 360 invoked from network); 20 Dec 1999 03:45:32 -0000
Received: from sense-sea-pm2-5.oz.net (HELO frantica.lly.org) (mail@216.39.133.37)
by master.debian.org with SMTP; 20 Dec 1999 03:45:32 -0000
Received: from rcw by frantica.lly.org with local (Exim 3.11 #1 (Debian))
for submit@bugs.debian.org
id 11ztlK-0001sv-00; Sun, 19 Dec 1999 19:45:30 -0800
Date: Sun, 19 Dec 1999 19:45:30 -0800
From: Robert Woodcock <rcw@debian.org>
To: submit@bugs.debian.org
Subject: hard to install to secondary disk
Message-ID: <19991219194530.A7213@frantica.lly.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0i
Sender: Robert Woodcock <rcw@frantica.lly.org>
Package: boot-floppies
Version: 2.2.1
I ran into this today while installing potato to a system where the user
wanted to keep Win98 installed on /dev/hda.
If a root fs is placed on /dev/hdb2, boot-floppies will want to install an
MBR on /dev/hdb. This is wrong, because the BIOS will only look at the MBR
on /dev/hda.
In order to complete the installation I had to switch to VC #2 and do:
cd /target
export LD_LIBRARY_PATH=/target/lib:/target/usr/lib
ae etc/lilo.conf
[where I changed 'boot=/dev/hdb2' to 'boot=/dev/hda', saved, and exited]
lilo -r . -C etc/lilo.conf
sync
reboot
Things worked just peachy after that, but I can't imagine a normal user
knowing that they would need to do that :)
I suppose this theoretical normal user could have used boot-floppies to
make a boot disk and then used far more normal incantations to edit
lilo.conf and run lilo, but ideally it should just pick the right place to
install bootloader code automatically.
Is the Debian MBR even capable of reaching LILO on a secondary drive?
--
Robert Woodcock - rcw@debian.org
"This Linux thing is unbelievable!" -- CNBC Market Wrapup
---------------------------------------
Received: (at 53113-done) by bugs.debian.org; 15 Mar 2000 07:22:15 +0000
Received: (qmail 4963 invoked from network); 15 Mar 2000 07:22:14 -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 07:22:14 -0000
Received: by arroz.fake (Postfix, from userid 421)
id E39DF93858; Wed, 15 Mar 2000 03:04:14 -0500 (EST)
Sender: apharris@arroz.fake
To: 36412-done@bugs.debian.org, 38144-done@bugs.debian.org,
48637-done@bugs.debian.org, 50014-done@bugs.debian.org,
53113-done@bugs.debian.org, 54130-done@bugs.debian.org,
56600-done@bugs.debian.org, 56960-done@bugs.debian.org,
57094-done@bugs.debian.org, 57110-done@bugs.debian.org,
57114-done@bugs.debian.org, 57119-done@bugs.debian.org,
57344-done@bugs.debian.org, 57364-done@bugs.debian.org,
57366-done@bugs.debian.org, 57372-done@bugs.debian.org,
57672-done@bugs.debian.org, 57736-done@bugs.debian.org,
57738-done@bugs.debian.org, 57783-done@bugs.debian.org,
58006-done@bugs.debian.org, 58009-done@bugs.debian.org,
58387-done@bugs.debian.org, 59156-done@bugs.debian.org,
59187-done@bugs.debian.org
Subject: bugs fixed in previous upload
From: Adam Di Carlo <adam@onshore.com>
Date: 15 Mar 2000 03:04:14 -0500
Message-ID: <oa3dpsfym9.fsf@arroz.fake>
Lines: 11
User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.5
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
We believe the bug you reported has been fixed as of the Potato boot flopppies,
version 2.2.8. Please let us know if not.
Remember that often bugs are filed against boot-floppies, when the should
be filed against modconf, base-config, kernel-image-2.2.14, or other
related packages. Please do you best to track down which package is the
culprit when creating bugs.
--
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>
Reply to: