All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Martin Schaffner <schaffner@gmx.li>,
	Kevin Hilman <kjh@hilman.org>,
	bertrand marquis <bertrand.marquis@sysgo.com>
Subject: Re: Building on case-insensitive systems and systems where -shared doesn't work well
Date: Sat, 16 Oct 2004 12:04:30 -0700	[thread overview]
Message-ID: <417170BE.9030906@kegel.com> (raw)
In-Reply-To: <20041016204001.B20488@flint.arm.linux.org.uk>

Russell King wrote:
>>Btw. this is not about "case-challenged" filesystems in general. This is
>>about making the kernel usefull out-of-the-box for the increasing
>>embedded market.
>>Less work-around patces needed the better. And these people are often
>>bound to Windoze boxes - for different reasons. And the individual
>>developer may not be able to change this.

Hear, hear!

> You still need a case-sensitive filesystem to be able to create a root
> filesystem for their embedded device. 

A case-preserving filesystem should be enough.  Or do you have a counterexample?

In any case, when I was building embedded filesystems,
I used an ext2 image file with genext2fs regardless of which operating
system I was running; made it a heck of a lot easier to
do things like create device files.
- Dan


-- 
Trying to get a job as a c++ developer?  See http://kegel.com/academy/getting-hired.html

  reply	other threads:[~2004-10-16 20:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-21  6:03 2.6.8 link failure for sparc32 (vmlinux.lds.s: No such file or directory)? Dan Kegel
2004-09-21 10:50 ` Sam Ravnborg
2004-09-21 10:57   ` William Lee Irwin III
2004-09-22  5:40     ` Dan Kegel
2004-09-24 20:19       ` Sam Ravnborg
2004-10-07  5:57   ` Building on case-insensitive systems and systems where -shared doesn't work well (was: Re: 2.6.8 link failure for sparc32 (vmlinux.lds.s: No such file or directory)?) Dan Kegel
2004-10-16 21:00     ` Sam Ravnborg
2004-10-16 19:06       ` Russell King
2004-10-16 21:24         ` Sam Ravnborg
2004-10-16 19:40           ` Russell King
2004-10-16 19:04             ` Dan Kegel [this message]
2004-10-16 22:04             ` Sam Ravnborg
2004-10-17 16:57               ` Herbert Poetzl
2004-10-17 16:42                 ` Building on case-insensitive systems and systems where -shared doesn't work well Dan Kegel
2004-10-17 18:29                   ` Herbert Poetzl
2004-10-17 17:47                     ` Dan Kegel
2004-10-17 19:06                       ` Herbert Poetzl
2004-10-17 19:32                         ` Dan Kegel
2004-10-31 21:10       ` Building on case-insensitive systems and systems where -shared doesn't work well (was: Re: 2.6.8 link failure for sparc32 (vmlinux.lds.s: No such file or directory)?) Sam Ravnborg

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=417170BE.9030906@kegel.com \
    --to=dank@kegel.com \
    --cc=bertrand.marquis@sysgo.com \
    --cc=kjh@hilman.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    --cc=sam@ravnborg.org \
    --cc=schaffner@gmx.li \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.