All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: mnalis@voyager.hr
Cc: Kazrak+kernel@cesmail.net, bunk@fs.tum.de,
	mnalis-umsdos@voyager.hr, linux-kernel@vger.kernel.org
Subject: Re: RFC: [2.6 patch] remove UMSDOS
Date: Thu, 29 Jul 2004 15:29:43 -0700	[thread overview]
Message-ID: <20040729152943.385f05e1.rddunlap@osdl.org> (raw)
In-Reply-To: <20040724182627.GA3767@eagle.earth.my>

On Sat, 24 Jul 2004 20:26:27 +0200 mnalis@voyager.hr wrote:

| On Sun, Jul 11, 2004 at 12:17:32PM -0600, Jeff Woods wrote:
| > At 7/11/2004 01:28 PM +0200, Adrian Bunk wrote:
| > >UMSDOS in 2.6 is broken, and it seems no one needs it enough to bother 
| > >fixing it.
| 
| Just to notify anybody interested that I have started working on fixing
| UMSDOS support for 2.6 kernels (as there still seems to be some people
| wanting it). 
| 
| Patch that enables UMSDOS to compile and insmod is available at 
| http://linux.voyager.hr/umsdos/
| It still doesn't work (triggers kernel BUG() after few write ops), 
| but I'll post another announcements when I get it in working condition.

I posted a umsdos patch (to build on 2.6.0-test) last October/2003.
See http://marc.theaimsgroup.com/?l=linux-fsdevel&m=106697862024272&w=2
and see Al Viro's reply to that.

Anyway, I just updated my patch to build on 2.6.8-rc2-bk8, so my patch
is quite similar to yours now.  Yours is a small bit ahead of mine.

  http://developer.osdl.org/rddunlap/patches/umsdos-build-268rc2bk8.patch

--
~Randy

      reply	other threads:[~2004-07-29 22:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-11 11:28 RFC: [2.6 patch] remove UMSDOS Adrian Bunk
2004-07-11 18:17 ` Jeff Woods
2004-07-11 20:17   ` H. Peter Anvin
2004-07-24 18:26   ` mnalis
2004-07-29 22:29     ` Randy.Dunlap [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=20040729152943.385f05e1.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=Kazrak+kernel@cesmail.net \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mnalis-umsdos@voyager.hr \
    --cc=mnalis@voyager.hr \
    /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.