Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: alan@lxorguk.ukuu.org.uk (Alan Cox)
To: ralf@mailhost.uni-koblenz.de (Ralf Baechle)
Cc: vincent@waw.com, miguel@nuclecu.unam.mx, linux@cthulhu.engr.sgi.com
Subject: Re: boot linux - wish
Date: Sun, 17 Aug 1997 13:33:22 +0100 (BST)	[thread overview]
Message-ID: <m0x04WI-0005FiC@lightning.swansea.linux.org.uk> (raw)
In-Reply-To: <199708162207.AAA01148@informatik.uni-koblenz.de> from "Ralf Baechle" at Aug 17, 97 00:07:45 am

> As far as the complexity of writing an XFS-like fs is concerned - SGI has
> invested a significant fraction of the R&D of XFS into the realtime stuff.
> So ignoring that part for the beginning makes the task of writing a XFS
> like filesystem much easier.

An XFS reader doesn't look too difficult, we can even take the btree
code from the Mac HFS driver. It should be possible to put the writing
algorithm back together by working back from the actual allocation patterns
for blocks the system makes

WARNING: multiple messages have this Message-ID (diff)
From: alan@lxorguk.ukuu.org.uk (Alan Cox)
To: Ralf Baechle <ralf@mailhost.uni-koblenz.de>
Cc: vincent@waw.com, miguel@nuclecu.unam.mx, linux@cthulhu.engr.sgi.com
Subject: Re: boot linux - wish
Date: Sun, 17 Aug 1997 13:33:22 +0100 (BST)	[thread overview]
Message-ID: <m0x04WI-0005FiC@lightning.swansea.linux.org.uk> (raw)
Message-ID: <19970817123322.yZGcwoSEth9SP4VYfs-7gMYq9BGFHVA3oLviulzY6Tw@z> (raw)
In-Reply-To: <199708162207.AAA01148@informatik.uni-koblenz.de> from "Ralf Baechle" at Aug 17, 97 00:07:45 am

> As far as the complexity of writing an XFS-like fs is concerned - SGI has
> invested a significant fraction of the R&D of XFS into the realtime stuff.
> So ignoring that part for the beginning makes the task of writing a XFS
> like filesystem much easier.

An XFS reader doesn't look too difficult, we can even take the btree
code from the Mac HFS driver. It should be possible to put the writing
algorithm back together by working back from the actual allocation patterns
for blocks the system makes

  parent reply	other threads:[~1997-08-17 11:24 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-08-15 20:17 boot linux - wish Ariel Faigon
1997-08-15 20:17 ` Ariel Faigon
1997-08-15 20:23 ` Mike Shaver
1997-08-15 21:47   ` Miguel de Icaza
1997-08-15 22:03     ` Alex deVries
1997-08-16  1:05     ` Mike Shaver
1997-08-16  1:05       ` Mike Shaver
1997-08-16 12:08       ` Alan Cox
1997-08-16 12:08         ` Alan Cox
1997-08-16 14:15         ` Mike Shaver
1997-08-16 14:15           ` Mike Shaver
1997-08-16 20:33         ` Ralf Baechle
1997-08-16 20:33           ` Ralf Baechle
1997-08-15 20:38 ` Alex deVries
1997-08-15 20:53   ` Mike Shaver
1997-08-15 20:53     ` Mike Shaver
1997-08-15 20:59     ` Alex deVries
1997-08-19 10:38     ` Oliver Frommel
1997-08-15 21:46   ` Miguel de Icaza
1997-08-16  5:08     ` Eric Kimminau
1997-08-16  6:18       ` Ralf Baechle
1997-08-16  6:18         ` Ralf Baechle
1997-08-16 20:25       ` Miguel de Icaza
1997-08-16 21:54         ` Vincent Renardias
1997-08-16 22:07           ` Ralf Baechle
1997-08-16 22:07             ` Ralf Baechle
1997-08-17 12:33             ` Alan Cox [this message]
1997-08-17 12:33               ` Alan Cox
1997-08-18  4:25     ` Kernel with working initrd? Alex deVries
1997-08-19  1:37     ` Current problems Alex deVries

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=m0x04WI-0005FiC@lightning.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=miguel@nuclecu.unam.mx \
    --cc=ralf@mailhost.uni-koblenz.de \
    --cc=vincent@waw.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