From: Ralf Baechle <ralf@Julia.DE>
To: irish@akira.tampa.sgi.com (Liam Irish)
Cc: ralf@mailhost.uni-koblenz.de, linux@cthulhu.engr.sgi.com
Subject: Re: The Plan For Userland(tm)
Date: Wed, 4 Jun 1997 16:40:19 +0200 (MET DST) [thread overview]
Message-ID: <199706041440.QAA14054@kernel.panic.julia.de> (raw)
In-Reply-To: <9706041004.ZM2604@akira.tampa.sgi.com> from "Liam Irish" at Jun 4, 97 10:04:56 am
> > Yeah, and if there won't be xfs for linux I'd really like to see ext2
> > support for IRIX ...
>
> > Ralf
> >-- End of excerpt from Ralf Baechle
>
>
> I'd like to do that. I've already been talking to some engineers about it. I
> was trying to determine if it already been done. Guess not. I think it'd be
> easier to put ext2 on irix than xfs on linux, esp considering the other options
> involved with xfs. Would it be 32-bit xfs?
>
> Anyway. They both interface a VFS, so it should be _too_ bad. Unfortunately,
> I haven't seen to much documentation for VFS on irix. Well, see if the Mtn
> View engineers will help out in that regard.
The other fun thing is that right now David and some other people are
rewriting the Linux VFS which also has impact on the ext2 code.
Ralf
WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@Julia.DE>
To: Liam Irish <irish@akira.tampa.sgi.com>
Cc: ralf@mailhost.uni-koblenz.de, linux@cthulhu.engr.sgi.com
Subject: Re: The Plan For Userland(tm)
Date: Wed, 4 Jun 1997 16:40:19 +0200 (MET DST) [thread overview]
Message-ID: <199706041440.QAA14054@kernel.panic.julia.de> (raw)
Message-ID: <19970604144019.gKM2fMTaXxuqte1PRzeXKhSd3V8HEagQ2lc1ahJNQ-Y@z> (raw)
In-Reply-To: <9706041004.ZM2604@akira.tampa.sgi.com> from "Liam Irish" at Jun 4, 97 10:04:56 am
> > Yeah, and if there won't be xfs for linux I'd really like to see ext2
> > support for IRIX ...
>
> > Ralf
> >-- End of excerpt from Ralf Baechle
>
>
> I'd like to do that. I've already been talking to some engineers about it. I
> was trying to determine if it already been done. Guess not. I think it'd be
> easier to put ext2 on irix than xfs on linux, esp considering the other options
> involved with xfs. Would it be 32-bit xfs?
>
> Anyway. They both interface a VFS, so it should be _too_ bad. Unfortunately,
> I haven't seen to much documentation for VFS on irix. Well, see if the Mtn
> View engineers will help out in that regard.
The other fun thing is that right now David and some other people are
rewriting the Linux VFS which also has impact on the ext2 code.
Ralf
next prev parent reply other threads:[~1997-06-04 14:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-06-02 18:21 The Plan For Userland(tm) Mike Shaver
1997-06-03 18:23 ` Ralf Baechle
1997-06-03 18:23 ` Ralf Baechle
1997-06-03 22:13 ` Alex deVries
1997-06-03 22:24 ` Alex deVries
1997-06-04 0:41 ` Ralf Baechle
1997-06-04 0:41 ` Ralf Baechle
1997-06-04 14:04 ` Liam Irish
1997-06-04 14:40 ` Ralf Baechle [this message]
1997-06-04 14:40 ` Ralf Baechle
1997-06-04 17:28 ` Alex deVries
1997-06-03 18:34 ` Ralf Baechle
1997-06-03 18:34 ` Ralf Baechle
1997-06-03 18:48 ` Mike Shaver
1997-06-03 18:48 ` Mike Shaver
1997-06-03 19:00 ` Ralf Baechle
1997-06-03 19:00 ` Ralf Baechle
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=199706041440.QAA14054@kernel.panic.julia.de \
--to=ralf@julia.de \
--cc=irish@akira.tampa.sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=ralf@mailhost.uni-koblenz.de \
/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