Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@codesourcery.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter@lists.netfilter.org, Philip Craig <philipc@snapgear.com>
Subject: Re: netfilter files in a case-insensitive filesystem
Date: Mon, 5 Jun 2006 09:40:48 -0400	[thread overview]
Message-ID: <20060605134047.GL4977@lios> (raw)
In-Reply-To: <Pine.LNX.4.58.0606021714480.12607@blackhole.kfki.hu>

On Fri, Jun 02, 2006 at 05:24:45PM +0200, Jozsef Kadlecsik wrote:
> > The current goal is to be able to ship the headers for use in an
> > environment which resides on a case-insenstive filesystem.
> 
> But why would it be useful? If someone develops netfilter kernel
> modules/iptables extension in a Windows environment, he is unable to test
> it. What is the point?

Target embedded devices attached via serial or usb?
 
> > If we did the work, would the community accept such patches?
> 
> You should not only have to merge the header files, but the source files
> as well.  And develop another method to autoload kernel modules and
> iptables extensions when required - matches and targets. And even when all
> is done, I personally would be extremely reluctant to accept such patches
> until I'm not convinced why it's absolutely required.

Thank you for your an initial evaluation of the required work.

Cheers,
Carlos.
-- 
Carlos O'Donell
CodeSourcery
carlos@codesourcery.com
(650) 331-3385 x716


      reply	other threads:[~2006-06-05 13:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-23 20:27 netfilter files in a case-insensitive filesystem Carlos O'Donell
2006-06-01  5:40 ` Philip Craig
2006-06-01 15:45   ` Carlos O'Donell
2006-06-02  0:14     ` Philip Craig
2006-06-02 15:24     ` Jozsef Kadlecsik
2006-06-05 13:40       ` Carlos O'Donell [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=20060605134047.GL4977@lios \
    --to=carlos@codesourcery.com \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=netfilter@lists.netfilter.org \
    --cc=philipc@snapgear.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