Linux Netfilter development
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: "Jan Engelhardt" <jengelh@medozas.de>,
	"Pteris Kavi¹" <klavins@netspace.net.au>,
	"Netfilter Developer Mailing List"
	<netfilter-devel@vger.kernel.org>
Subject: Re: [RFC] netfilter: Rename ipt_ECN.h to ipt_ecn_target.h (and similar) to avoid file name clash
Date: Mon, 18 Aug 2008 13:17:10 +0200	[thread overview]
Message-ID: <48A95A36.7090505@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0808162057270.20963@blackhole.kfki.hu>

Jozsef Kadlecsik wrote:
> On Sat, 16 Aug 2008, Jan Engelhardt wrote:
> 
>> On Friday 2008-08-15 18:03, P˙˙teris K˙˙avi˙˙š wrote:
>>
>>> This is a request for comments on the proposal that the following
>>> filename changes (indicative at this point) be made in the
>>> netfilter source code tree, together with correcting the
>>> corresponding references to the files in both source code, the
>>> build system, and wherever else necessary.
>>>
>>> The changes are proposed in order to avoid file name clashes on
>>> filesystems that do not allow two files to have names that differ
>>> only in the case of their letters:
>>>
>>> include/linux/netfilter/xt_CONNMARK.h => xt_connmark_target.h
>> [...]
>>
>> As I see it, this will already be addressed by merging complementary
>> code into one source file (e.g. MARK, mark, CONNMARK, connmark
>> all into a big new xt_mark.c), to reduce (a) amount of files
>> and (b) build time.
> [...]
> 
> That is half of the story: we encode the functionality (match/target) in 
> the case of the (file)name and there are targets which have got no match 
> counterpart and thus no natural lowercase filename to merge into it. So 
> the directory tree still will be broken on case-insensitive filesystems. 
> 
> If as a side effect of some real internal changes netfilter becomes 
> compatible with case-insensitive filesystems, that's fine. However, I 
> object changes just for the sake to be compatible with such horrid 
> filesystems.

I agree. Without compat files this would also break compilation
of old userspace, so this is not an option anyways.

--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2008-08-18 11:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-15 22:03 [RFC] netfilter: Rename ipt_ECN.h to ipt_ecn_target.h (and similar) to avoid file name clash Pēteris Kļaviņš
2008-08-16 14:04 ` Jan Engelhardt
2008-08-16 15:32   ` Pēteris Kļaviņš
2008-08-16 19:14   ` Jozsef Kadlecsik
2008-08-16 19:22     ` Jan Engelhardt
2008-08-16 19:52       ` Jozsef Kadlecsik
2008-08-16 20:19         ` Pēteris Kļaviņš
2008-08-17 22:04           ` Jozsef Kadlecsik
2008-08-17 22:18             ` Jan Engelhardt
2008-08-18 11:17     ` Patrick McHardy [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=48A95A36.7090505@trash.net \
    --to=kaber@trash.net \
    --cc=jengelh@medozas.de \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=klavins@netspace.net.au \
    --cc=netfilter-devel@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