From: Adrian Bunk <bunk@fs.tum.de>
To: Mark Beyer - Contractor <mbeyer@unminc.com>
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.6: future of UMSDOS?
Date: Thu, 27 May 2004 22:28:38 +0200 [thread overview]
Message-ID: <20040527202837.GV16099@fs.tum.de> (raw)
In-Reply-To: <40B22E8D.6000901@unminc.com>
On Mon, May 24, 2004 at 10:19:09AM -0700, Mark Beyer - Contractor wrote:
> Jan-Benedict Glaw wrote:
>
> >On Wed, 2004-05-19 20:43:21 +0200, Adrian Bunk <bunk@fs.tum.de>
> >wrote in message <20040519184321.GB24287@fs.tum.de>:
> >
> >
> >>Looking at the state of the UMSDOS code in 2.6 I'm currently wondering
> >>about it's future.
> >>
> >>Are there still potential users and people willing to work on getting it
> >>working, or should it be removed from kernel 2.6?
> >>
> >>
> >
> >In my early Linux days, UMSDOS was quite a neat thing to have for
> >showing Linux to friends by placing a .zip'ed Linux installation on
> >their MS-DOS machines.
> >
> >So for historic reasons, I think it would be nice to have UMSDOS around.
> >
> >
> There are still embedded systems that boot from a DOS file system. Yes,
> there are better methods but for backward compatibility I wouldn't like
> to see it removed.
It's broken in 2.6.
Does anyone need it enough to fix it?
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2004-05-27 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 18:43 2.6: future of UMSDOS? Adrian Bunk
2004-05-24 14:51 ` Jan-Benedict Glaw
2004-05-24 17:19 ` Mark Beyer - Contractor
2004-05-27 20:28 ` Adrian Bunk [this message]
2004-05-28 9:03 ` aeriksson
2004-05-28 9:19 ` Jan-Benedict Glaw
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=20040527202837.GV16099@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=jbglaw@lug-owl.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mbeyer@unminc.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