public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: more thoughts on kernel config organization
Date: Sun, 12 Jan 2003 09:04:06 +0100	[thread overview]
Message-ID: <20030112080406.GA1006@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0301112300570.20815-100000@dell>

On Sat, Jan 11, 2003 at 11:17:46PM -0500, Robert P. J. Day wrote:
>   how about something like
> 
>   ext2
>   ext3
>   reiser
>   XFS
>   JFS
>   quotas
>   MS/DOS related filesystems
>     MD-DOS
>     VFAT
>     NTFS
>   other OS-related filessytems
>     Apple
>     ADFS
>     BeOS
>     BFS
>     QNX
>     System V/XENIX/...
>   Pseudo(?) filessytems
>     /proc
>     /dev/pts
>     /dev

I like the structure proposed above. I for myself has often wondered why
ext2 was not named ext2, and hidden between lots of less used stuff.
If you sort in alphabetic order, then be consistent.

If you are going to reorganise fs/Kconfig I would suggest moving
ext3, reiserfs etc. specific stuff down in their respective directories,
and then source as appropriate.
There is no reason to keep that in a centralised placed, when it can
be distributed.
For simple (Kconfig wise) stuff like CODA or Intermezzo keep them
in fs/KConfig.

	Sam

  reply	other threads:[~2003-01-12  7:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-12  4:17 more thoughts on kernel config organization Robert P. J. Day
2003-01-12  8:04 ` Sam Ravnborg [this message]
2003-01-12  9:22   ` Robert P. J. Day
2003-01-12 10:03     ` Tomas Szepe
2003-01-12 17:12 ` Roman Zippel
2003-01-13 12:32 ` Dave Jones

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=20030112080406.GA1006@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.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