From: Jay Miller <jnmiller@cryptofreak.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Porting to 2.4 info
Date: Thu, 22 Feb 2001 13:25:55 -0700 [thread overview]
Message-ID: <20010222132555.F23153@ethan.tricord.com> (raw)
In-Reply-To: <20010221143230.A8246@cryptofreak.org>
In-Reply-To: <20010221143230.A8246@cryptofreak.org>; from jnmiller@cryptofreak.org on Wed, Feb 21, 2001 at 02:32:30PM -0700
I hate to pollute your mailboxes with stuff that almost certainly
doesn't concern you, but my ISP went down for about 6-7 hours yesterday
after I posted this.. <sigh> So, um, if you couldn't get in - please try
again!
(Sorry to the rest of ya'..)
- Words by Jay Miller <jnmiller@cryptofreak.org> [010221 16:48]:
> Since I had some trouble finding any porting info from 2.2 to 2.4, I
> wrote up a small amount of research I did on porting FSDs in hope that
> someone else might find it useful.. it can be found here:
>
> http://www.cryptofreak.org/projects/port/port-fs-2.4.html
>
> I'd also be grateful for any help, re: errors or improvements. Thanks!
--
Jay Miller
prev parent reply other threads:[~2001-02-22 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 21:32 Porting to 2.4 info Jay Miller
2001-02-22 20:25 ` Jay Miller [this message]
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=20010222132555.F23153@ethan.tricord.com \
--to=jnmiller@cryptofreak.org \
--cc=linux-kernel@vger.kernel.org \
/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