From: pete@dunnington.u-net.com (Pete Turnbull)
Subject: [TUHS] Re: Making boot disks
Date: Tue, 1 Oct 2002 06:29:56 GMT [thread overview]
Message-ID: <10210010729.ZM21799@mindy.dunnington.u-net.com> (raw)
In-Reply-To: Ian Molton <spyro@f2s.com> "Re: [TUHS] Re: Making boot disks" (Oct 1, 1:37)
On Oct 1, 1:37, Ian Molton wrote:
>
> On Tue, 1 Oct 2002 09:29:02 +0930
> "Greg 'groggy' Lehey" <grog at lemis.com> wrote:
>
> > Well, it would be nice to know what you're really trying to do.
> > What's the hardware? If the file system is UFS, it's unlikely to be a
> > good fit for Linux. I'd say "try FreeBSD", but without knowing more
> > about your software and hardware, it's not clear if that would be any
> > better. Google suggests that it runs on ARMs. Is that correct?
>
> The hardware is an obscure british platform from back when the ARM was
> young. - The Archimedes.
>
> The CPU is the ARM2 or 3 (either work) and the systems have SCSI,
> ethernet, and (up to) 16Mb of RAM.
>
> I dont actually know what the filesystem is, but my guess is UFS based
> on the newfs command in the mkkernel script, and a rumour it is BSD
> derived.
It is indeed a straight port of BSD 4.x, where x depends in whether is it's
RISC iX 1 or 1.2 (R440 used 4.2, I think; R260 used 4.3).
> I have everything from a machines filesystem in a tarball.
>
> I simply have no bootdisk, and cant create one without a suitable newfs
>
> > > any advice from the list would be appreciated :)
Take a look at James Carter's page at
http://www.jfc.org.uk/documents/riscix_clone.html
James and I worked this out when we rescued half-a-dozen R260's in various
states of disrepair and with various not-quite-complete copies of RISC iX.
> is it possible for someone else to make a filesystem image for me that I
> could dd onto a floppy? I suspect that this system uses an old variant
> of ufs.
It is a standard 4.3 filesystem (at least for the verison for an R260). It
even says so when it boots:
RISC iX Release 1.2
ARM3 processor, cache enabled
...
...
Root fstype 4.3, name /dev/sd0a
Swap fstype spec, name /dev/sd0S
...
One of us could copy some stuff for you. I'm not sure you'd be able to get
what you need onto a single floppy, though. That's not how Acorn did it.
We'd certainly be willing to help, especially if you have any RISC iX stuff
we're missing.
--
Pete Peter Turnbull
Network Manager
University of York
next prev parent reply other threads:[~2002-10-01 6:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-30 23:39 [TUHS] Re: Making boot disks (fwd) Warren Toomey
[not found] ` <20020930214211.5d53a9a0.spyro@f2s.com>
2002-09-30 21:37 ` [TUHS] Re: Making boot disks Warren Toomey
2002-09-30 23:59 ` Greg 'groggy' Lehey
2002-10-01 0:37 ` Ian Molton
[not found] ` <spyro@f2s.com>
2002-10-01 6:29 ` Pete Turnbull [this message]
2002-10-01 9:16 ` Ian Molton
2002-10-02 7:20 ` Pete Turnbull
2002-10-01 8:01 Christian Groessler
2002-10-01 9:04 ` Ian Molton
2002-10-01 9:55 ` Jochen Kunz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=10210010729.ZM21799@mindy.dunnington.u-net.com \
--to=pete@dunnington.u-net.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).