public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: hirofumi@mail.parknet.co.jp, g.liakhovetski@gmx.de,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] NLS as module
Date: Sat, 25 Oct 2003 16:18:47 -0700	[thread overview]
Message-ID: <20031025161847.4b13a986.rddunlap@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0310260049030.1490-100000@poirot.grange>

On Sun, 26 Oct 2003 00:55:18 +0200 (CEST) Guennadi Liakhovetski <g.liakhovetski@gmx.de> wrote:

| On Sat, 25 Oct 2003, OGAWA Hirofumi wrote:
| 
| > Guennadi Liakhovetski <g.liakhovetski@gmx.de> writes:
| >
| > > Problem: NLS support can only be compiled in the kernel - and not as a
| > > module. And if you don't configure one of Joliet / FAT and some other
| > > filesystems at kernel compile-time, you can't compile these filesystems
| > > later as modules(*). However, I see nothing that would prevent one from
| > > compiling nls_base as a module. I tried - it worked, but I didn't actually
| > > use any of the codepages. Just tried insmod nls_base, insmod <fs>, mount.
| > > So, is it desired / really this trivial or are there some real reasons why
| > > nls_base cannot be properly done as a module? I am attaching a naive
| > > patch - but not really understanding NLS internals and not being able to
| > > extensively test it, it might be not quite correct.
| >
| > Sound good to me. And I like this, but it may be more test needed
| > (i.e. module autoload etc.). So I suggest it start on development
| > tree. And backport after it.
| 
| Sure. Attached is a patch against 2.6.0-test7. Looks like it's not going
| to make it into 2.6.0, but, maybe later. And I reversed the dependencies -
| looks more logical, that FAT, SMB, etc. depend on NLS, and not vise versa.
| I tested it briefly, seems to work.

I would prefer to see the opposite:  selecting an FS that requires NLS
should force NLS to be enabled, via "select NLS".
For example:


| diff -ur linux-2.6.0-test7/fs/Kconfig linux-2.6.0-test7.new/fs/Kconfig
| --- linux-2.6.0-test7/fs/Kconfig	Thu Oct  9 22:11:31 2003
| +++ linux-2.6.0-test7.new/fs/Kconfig	Sat Oct 25 21:24:13 2003
| @@ -246,6 +246,7 @@
| 
|  config JFS_FS
|  	tristate "JFS filesystem support"
| -	depends on NLS
	select NLS
|  	help
|  	  This is a port of IBM's Journaled Filesystem .  More information is
|  	  available in the file Documentation/filesystems/jfs.txt.
| @@ -464,6 +465,8 @@
|  	  local network, you probably do not need an automounter, and can say
|  	  N here.


--
~Randy

  reply	other threads:[~2003-10-25 23:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-23 21:36 [PATCH] NLS as module Guennadi Liakhovetski
2003-10-25 10:53 ` OGAWA Hirofumi
2003-10-25 22:55   ` Guennadi Liakhovetski
2003-10-25 23:18     ` Randy.Dunlap [this message]
2003-10-26 15:58       ` OGAWA Hirofumi
2003-10-26 19:27         ` Guennadi Liakhovetski

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=20031025161847.4b13a986.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=hirofumi@mail.parknet.co.jp \
    --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