Your message dated Fri, 10 May 2019 22:42:40 +0200
with message-id <[email protected]>
and subject line arch:sparc has been removed from Debian
has caused the Debian Bug report #293867,
regarding should offer to install silo to partition instead of MBR with silo -t
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
293867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=293867
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: installation-reports
Version: Debian 3.0r2
Severity: important
Processor: UltraSPARC-IIi 440 MHz
Root Device: IDE
I have installed Debian Linux 3.0r2 on my ultra5
(There are two large IDE disks (60 GB and 120GB) with several versions
of solaris on there and now of course Debian Linux ;)
My main problem was that during my installation I had only
the possibility to let silo install on the master boot sectors.
(The possibility of making a boot floppy failed)
Afterwards neither solaris nor linux started but silo was installed.
I had to remove silo by starting the solaris boot cd and restore the
solaris boot blocks.
(On a root shell you can type
installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c0t0d
0s0
)
Afterwards I booted the Debian cd mounted my
linux partition and run silo -r /mnt -t to install silo on the linux
partition. Afterwards everything worked fine.
I can now boot silo or solaris from the OpenBoot and from silo I can
boot linux)
It would be great if the new debian has a possibility to let the
master boot blocks untouched. There should be one option e.g.
4. save silo installation (Master Boot Sector will not be changed)
Installing silo with the -t option seems to be a save method and does
not harm. It's really a nasty thing to remove silo (if something
goes wrong like in my example (perhaps too large disks) or you
want/have to remove linux/silo) and restore the old boot blocks.
Kind regards
Roland
--- End Message ---
--- Begin Message ---
Version: 1.30+rm
The (32-bit) sparc architecture was last released with Debian 7.0
(wheezy) in May 2013 and was removed from the Debian archive afterwards.
Since support for wheezy has now ended and the suites have been
archived, I'm closing all the remaining bugs reported against
sparc specific packages.
While the silo-installer package may still be used by the
sparc64 architecture in debian-ports, the Debian BTS cannot be used for
tracking bugs in ports-only packages.
Andreas
--- End Message ---
