From: Patrick Schaaf <bof@bof.de>
To: James Stevenson <mistral@stev.org>
Cc: linux-kernel@vger.kernel.org, netfilter-devel@lists.samba.org
Subject: Re: file names ?
Date: Wed, 26 Dec 2001 06:48:22 +0100 [thread overview]
Message-ID: <20011226064822.Q14419@oknodo.bof.de> (raw)
In-Reply-To: <000701c18d82$57158ea0$0801a8c0@Stev.org>
In-Reply-To: <000701c18d82$57158ea0$0801a8c0@Stev.org>; from mistral@stev.org on Tue, Dec 25, 2001 at 08:25:48PM -0000
> i could not help but notice in the kernel source
> in both the ipv4/netfilter and ipv6/netfilter
> dirs there are files the same name which can cause problems
> under certin conditions like non-case sensitive file systems.
>[...]
> this does not cause a problem for me but i do
> know people who it does cause a problem for
>[...]
> anyone got any suggestions ?
Yes: don't worry. That's Unix.
> a small example is a smallish ext2 / filesystem
> and the rest being a fat filesystem to that
> it can be accessed from both windows and linux.
> and there is not enough space on the ext2 to compile a kernel anymore.
There's a very simple means to "solve" that scenario, if you are the
one in a million people who happens to have such a setup, _and_ want
to recompile your kernel from scratch: create a loop mount file on the
FAT partition, create an ext2fs there, mount that, and compile on it.
Problem solved.
best regards
Patrick
next prev parent reply other threads:[~2001-12-26 5:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-25 20:25 file names ? James Stevenson
2001-12-25 20:41 ` Ryan Cumming
2001-12-25 23:36 ` Nicholas Knight
2001-12-26 3:59 ` Ryan Cumming
2001-12-26 5:48 ` Patrick Schaaf [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-28 14:36 Jacques Gelinas
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=20011226064822.Q14419@oknodo.bof.de \
--to=bof@bof.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mistral@stev.org \
--cc=netfilter-devel@lists.samba.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