The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: spyro@f2s.com (Ian Molton)
Subject: [TUHS] Re: Making boot disks
Date: Tue, 1 Oct 2002 01:37:54 +0100	[thread overview]
Message-ID: <20021001013754.4d51c7ef.spyro@f2s.com> (raw)
In-Reply-To: <20020930235902.GP22839@wantadilla.lemis.com>

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.

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 :)
> 
> In that case you should copy us.

Done. whats the subscribe address, btw?

Well, heres the mkkernel and other scripts (attached).

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.

the system is little-endian, if that helps?

I just had an evil thought...

one way to get this system up would be to finish my port of ARMlinux to
the Archimedes (naerly done but lots to do still). then write a RISCiX
personality and run RISCiX newfs on armlinux ;-)

No. too evil. I think best to try easier methods first ;-)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mkkernel
Type: application/octet-stream
Size: 1491 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20021001/32100959/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mkfloppies
Type: application/octet-stream
Size: 1762 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20021001/32100959/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mksystem
Type: application/octet-stream
Size: 8996 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20021001/32100959/attachment-0002.obj>


  reply	other threads:[~2002-10-01  0:37 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 [this message]
     [not found]         ` <spyro@f2s.com>
2002-10-01  6:29           ` Pete Turnbull
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=20021001013754.4d51c7ef.spyro@f2s.com \
    --to=spyro@f2s.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).