Bug#62311: marked as done (silo should be installed on first harddisk, not on installation harddisk)
Your message dated Thu, 13 Apr 2000 10:33:02 -0400
with message-id <20000413103302.A15564@visi.net>
and subject line Bug#62311: silo should be installed on first harddisk, not on installation harddisk
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; 13 Apr 2000 13:58:34 +0000
Received: (qmail 4160 invoked from network); 13 Apr 2000 13:58:33 -0000
Received: from dame.isr.uni-stuttgart.de (129.69.33.86)
by master.debian.org with SMTP; 13 Apr 2000 13:58:33 -0000
Received: from schelle ([129.69.33.90] ident=mail)
by dame.isr.uni-stuttgart.de with esmtp (Exim 2.02 #1)
id 12fk8d-0002xu-00; Thu, 13 Apr 2000 15:58:31 +0200
Received: from flynn by schelle with local (Exim 3.12 #1 (Debian))
id 12fk8c-0007Jn-00; Thu, 13 Apr 2000 15:58:30 +0200
From: Flynn Marquardt <flynn@isr.uni-stuttgart.de>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: silo should be installed on first harddisk, not on installation harddisk
X-Reportbug-Version: 0.54
X-Mailer: reportbug 0.54
Date: Thu, 13 Apr 2000 15:58:30 +0200
Message-Id: <[🔎] E12fk8c-0007Jn-00@schelle>
Sender: Flynn Marquardt <flynn@isr.uni-stuttgart.de>
Package: boot-floppies
Version: N/A; reported 2000-04-13
Severity: normal
I installed potato for sparc on the second harddisk (/dev/sdb1) and
silo was installed on /dev/sdb. IMHO silo should be installed on the
first harddisk, in my case on /dev/sda. Otherwise special openprom
commands are needed, e.g
boot disk3
or
setenv boot-device disk3
Flynn
-- System Information
Debian Release: 2.2
Architecture: sparc
Kernel: Linux schelle 2.2.13 #13 Mon Dec 6 15:20:24 CET 1999 sparc64
---------------------------------------
Received: (at 62311-done) by bugs.debian.org; 13 Apr 2000 14:33:29 +0000
Received: (qmail 17860 invoked from network); 13 Apr 2000 14:33:28 -0000
Received: from ppp14.ts2.gloucester.visi.net (HELO blimpo.visi.net) (@209.96.247.78)
by master.debian.org with SMTP; 13 Apr 2000 14:33:28 -0000
Received: from bmc by blimpo.visi.net with local (Exim 3.12 #1 (Debian))
id 12fkg2-00044C-00; Thu, 13 Apr 2000 10:33:02 -0400
Date: Thu, 13 Apr 2000 10:33:02 -0400
From: Ben Collins <bcollins@debian.org>
To: Flynn Marquardt <flynn@isr.uni-stuttgart.de>,
62311-done@bugs.debian.org
Subject: Re: Bug#62311: silo should be installed on first harddisk, not on installation harddisk
Message-ID: <20000413103302.A15564@visi.net>
References: <[🔎] E12fk8c-0007Jn-00@schelle>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0.1i
In-Reply-To: <[🔎] E12fk8c-0007Jn-00@schelle>; from flynn@isr.uni-stuttgart.de on Thu, Apr 13, 2000 at 03:58:30PM +0200
Sender: Ben Collins <bmc@visi.net>
On Thu, Apr 13, 2000 at 03:58:30PM +0200, Flynn Marquardt wrote:
> Package: boot-floppies
> Version: N/A;
> Severity: normal
>
> I installed potato for sparc on the second harddisk (/dev/sdb1) and
> silo was installed on /dev/sdb. IMHO silo should be installed on the
> first harddisk, in my case on /dev/sda. Otherwise special openprom
> commands are needed, e.g
>
> boot disk3
>
> or
> setenv boot-device disk3
>
IMO, that is a bad idea, and not really possible to determine properly.
What if someone has OpenPROM to boot from the second disk.
For example, someone has a disk at SCSI ID 1, and ID 3. By default, the
PROM boots from ID 3, but in Linux, that is sdb. If we then setup silo on
sda (ID 1), the system will not boot. Also, what if the first disk is a
Solaris install. If we then install silo on sda (even if sda is the
default boot drive, and sdb is the linux install), then we overwrite the
Solaris boot loader.
I think it needs to remain the same. Too many unknowns when dealing with
that kind of assumption. Users who read the install docs, or just know
their machines, will know how to boot from the correct drive. Also, you
can change the default boot device in the PROM so that you wont have to do
that anymore.
I'm closing this bug, since it really isn't an issue.
--
-----------=======-=-======-=========-----------=====------------=-=------
/ Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \
` bcollins@debian.org -- bcollins@openldap.org -- bmc@visi.net '
`---=========------=======-------------=-=-----=-===-======-------=--=---'
Reply to: