All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <dm@neteng.engr.sgi.com>
To: alambie@wellington.sgi.com
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Is this a silly idea?
Date: Tue, 11 Jun 1996 10:38:50 -0700	[thread overview]
Message-ID: <199606111738.KAA05955@neteng.engr.sgi.com> (raw)
In-Reply-To: <199606110013.MAA03444@soyuz.wellington.sgi.com> (alambie@wellington.sgi.com)

   From: alambie@wellington.sgi.com (Alistair Lambie)
   Date: Tue, 11 Jun 1996 12:13:36 +1200 (NZT)

   I'm not sure what the best way to attack this would be, but my
   guess is that we need to put the common filesystem in Irix, as I
   would pick that it would be difficult to get the buyin to port one
   of our filesystems to Linux.

I planned on hacking xfs _and_ efs implementations into Linux.

   Several questions:

   1. Is this sensible (or is there already a way of doing this)?

   2. If it is sensible, what should we do (type of fs etc)?

   3. Does anyone know how easy this is (I'm not sure whether I'm
   brave enough!)?

Also, I wouldn't mind seeing an ext2 implementation in IRIX, I could
probably hack up an initial read-only kernel module implementation in
a very short amount of time.

This is all only a matter of someone sitting behind the screen and
whacking away at the code for 2 or 3 days, nothing more.  I'd rather
concentrate on getting bootstrapped at this point, but after that I'll
probably hack on something like xfs/efs or whatever.

Later,
David S. Miller
dm@sgi.com

  reply	other threads:[~1996-06-11 17:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-06-11  0:13 Is this a silly idea? Alistair Lambie
1996-06-11 17:38 ` David S. Miller [this message]
1996-06-11 17:47 Larry McVoy
1996-06-11 18:44 ` Donna Yobs
1996-06-11 22:34   ` Ariel Faigon
1996-06-11 22:34     ` Ariel Faigon
1996-06-11 19:48 Larry McVoy

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=199606111738.KAA05955@neteng.engr.sgi.com \
    --to=dm@neteng.engr.sgi.com \
    --cc=alambie@wellington.sgi.com \
    --cc=linux@cthulhu.engr.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.