From: Jody Bruchon <jody@jodybruchon.com>
To: linux-8086@vger.kernel.org
Subject: Re: Removed MSDOS/FAT/VFAT support; keeping CONFIG_MODULES
Date: Fri, 17 Feb 2012 12:02:32 -0500 [thread overview]
Message-ID: <4F3E8828.1070306@jodybruchon.com> (raw)
In-Reply-To: <A206356A1CB74CA1A2B7CA43B48DC9E2@p4>
On 02/17/12 11:58, Petr Koval wrote:
> is it possible to have (V)FAT support later?
>
> Petr Koval
Yes, if a driver is written for it (something which I eventually intend
to do), then it will be implemented. At this time, I am focusing my
efforts on cleaning the cruft out. Since one of the less emphasized
goals of ELKS is to be an easy-to-understand kernel for educational
purposes, removing these junky items cluttering the menus and code will
help with that process in many ways. For me personally, I find the
existence of options to compile in features that literally DO NOT EXIST
to be very annoying. When a FAT filesystem driver is being written, the
menu option for compiling it in will be added back as well.
From what I understand, everyone now working on ELKS is fairly new to
the project, or has not worked with it actively for quite some time. We
need to be able to see where we are so we know where to go, without
having to sift through false positives like "elksfs" and "VFAT" that are
in reality non-existent or might as well be rendered the same.
In summary: let me clean the code up first, then we'll worry about a FAT
filesystem implementation. :-)
Jody Bruchon
prev parent reply other threads:[~2012-02-17 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 16:53 Removed MSDOS/FAT/VFAT support; keeping CONFIG_MODULES Jody Bruchon
2012-02-17 16:58 ` Petr Koval
2012-02-17 17:02 ` Jody Bruchon [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=4F3E8828.1070306@jodybruchon.com \
--to=jody@jodybruchon.com \
--cc=linux-8086@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).