On Mon, Oct 26, 2009 at 11:18:26AM +0000, Matthew Booth wrote:
Problem is, if you don't put the magic in you're pushing the
problem on
to the library user.
This is not true. It's only used for the case where you are resolving
paths given to you by Windows -- eg. coming from a Windows
configuration file or from the Windows Registry. The case we use it
is precisely this: we read the Windows %systemroot% from NTLDR and
then have to resolve that against the filesystem. If Windows allowed
its root filesystem to be on ext3 it would work the same way.
In any other case, using case_sensitive_path is almost certainly
wrong, in fact not just slow but quite likely to be insecure too. You
don't want a Linux config file that specifies /etc/something to
randomly pick /etc/SOMETHING.
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://et.redhat.com/~rjones/virt-top