28 Aug
2014
28 Aug
'14
5:39 a.m.
On 28 August 2014 09:36, David Griffith <dgriffi at cs.csubak.edu> wrote:
On Wed, 27 Aug 2014, jwsmobile wrote:
Sun boxes boot a different filesystem image based on their
architecture, which will include an appropriate kernel, after which
the root filesystem and similar can be shared within reason - (sun4,
sun4c & sun4m) & (sun3, sun3x) etc.
mksunbootcd can add in the filesystem images into a standard ISO
image, generating a new iso with the data & boot images -
http://pkgsrc.se/sysutils/mksunbootcd
This means you (theoretically) can make a single ISO image bootable on
sun4, sun4c, sun4m, sun4u, sun3, sun3x & sun2... Presumably "Because
its there".
IIRC earlier versions of NetBSD had multiboot ISO images, but now just
tends to have ultrasparc, sparc, & sun3
http://www.netbsd.org/docs/bootcd.html#sparcimage
Has anyone successfully duplicated or archived
the Sun 4.1 era Sunos CDs?
That is my benchmark of a real archive tool.
If you ever had one of those with an SS1, SS5 and an IPX and IPC all
running, when you booted the CD or inserted it after install and browsed it
between the boot code and drivers, each system would see different
executables and data for all the CD partitions. Each sun system had s
different architecture, and this CD would present a different set of data to
each system.
Duplicating that (and explaining it better than I have here) is what I'd
love to see in a CD tool.
It took me a few days of discussion in #classiccmp to get a SunOS 4.1.4 CD
image that would work. The first one I acquired had a corrupted tar file on
it, perhaps from a complication of the sort you seem to be alluding to.
Anyhow, I managed to get it booted, installed, and running under QEMU.
Poking through the innards of the CD image, I decided that the different
executables presented part came about from clever scripting -- no esoteric
CD diddling. That being said, I have never installed SunOS on real
hardware.