Hello.

I use gnupod to add tracks to my iPod. When I do it says this:

warning: /media/ELIOT_IPOD seems to be mounted *CASE SENSITIVE*
Mounting VFAT/HFS+ like this is a VERY BAD(tm) idea,
strange things may happen... GNUpod may not work correctly!
Please mount the Filesystem CASE *IN*SENSITIVE
(use 'mount ... -o check=r' for VFAT)
[Ignore this message if /media/ELIOT_IPOD isn't a
VFAT or HFS+ Filesystem ]

Thing is, I never use mount manually to mount my iPod. fstab-sync hears the HAL
event and mounts it for me. My question is, how do I tell fstab-sync to mount
the volume with the '-o check=r'?

man fstab-sync suggests I drop a file in /usr/share/hal/fdi/95userpolicy to do
this, and there are some examples of these files in /usr/share/doc, but I can't
see from the examples how to do this.

Any help would be much appreciated.

Cheers,

Eliot Stock.

Have you tried adding the "check=r" option to the comma separated options field (the fourth field, see "man fstab") of the ipod section in your /etc/fstab file?
Hope that helps.

No - I don't mount it by adding a line to fstab - that's what fstab-sync does for me when I plug the iPod in. When the iPod is unplugged, there is no line in fstab for it. When I plug it in there's a HAL event and fstab-sync adds the line to fstab for me.

I'm not sure if you've already solved the problem yourself, but since no one else has yet replied I thought I'd try again.
Perhaps one way to create the .fdi file you need might be to search google for an ipod.fdi file, to use a template for your own.
Such as HERE, for example.
To add the check=r option, you could for example try inserting the following line of XML which uses the volume.policy namespace:
See also the HAL Specification, the section on policy properties in particular.
Hope that helps.

Thanks for the help - we're getting somewhere.

Here's the complete fdi file I used:

[root@flyjack 95userpolicy]# more /usr/share/hal/fdi/95userpolicy/ipod.fdi
<?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- -->
<deviceinfo version="0.2">
<device>
<match key="block.is_volume" bool="true">
<match key="volume.fsusage" string="filesystem">
<match key="@block.storage_device:storage.vendor" string="Apple">
<match key="@block.storage_device:storage.model" string="iPod">
<merge key="volume.policy.mount_option.check=r" type="bool">true</merge>
</match>
</match>
</match>
</match>
</device>
</deviceinfo>

and this seems to work insofar as the line in fstab now has the check=r option I wanted:

[root@flyjack 95userpolicy]# tail -1 /etc/fstab
/dev/sda2 /media/ELIOT_IPOD vfat pamconsole,exec,noauto,check=r,iocharset=utf8,managed 0 0

but somehow gnupod is still complaining the drive is mounted case senstive:

[eliot@flyjack ~]$ gnupod_check.pl
gnupod_check.pl Version 0.98 (C) Adrian Ulrich
warning: /media/ELIOT_IPOD seems to be mounted *CASE SENSITIVE*
Mounting VFAT/HFS+ like this is a VERY BAD(tm) idea,
strange things may happen... GNUpod may not work correctly!
Please mount the Filesystem CASE *IN*SENSITIVE
(use 'mount ... -o check=r' for VFAT)
[Ignore this message if /media/ELIOT_IPOD isn't a
VFAT or HFS+ Filesystem ]
Pass 1: Checking Files in the GNUtunesDB.xml...
Pass 2: Checking Files on the iPod...
..finished

Total Playtime : 34 h
Space used : 2.52 GB
iPod files : 437
GNUpod files : 437
-> Everything is fine

And is the ipod also listed in /etc/mtab with the "check=r" option?

Yes:

/dev/sda2 /media/ELIOT_IPOD vfat rw,nosuid,nodev,check=r,iocharset=utf8,user=eliot 0 0

It would then appear that the ipod is indeed mounted with the "check=r" option. Thus I would suspect that this is probably a gnupod bug, especially if "strange things" are not happening and gnupod is working correctly.

ok, cheers. I'll make sure I'm running the latest gnupod and post a bug over there. thanks for the help.

This is apprently due to a broken kernel in Fedora. Got this from the gnupod guy. Since I only use my iPod with Linux it safe to just ignore the warning.


An important note about VFAT:

VFAT is ought to be 'case preserve' , *NOT* 'case sensitive'.

VFAT knows how you called the file, but it doesn't care about
the name (upper/lowercase) if you open/access the File!

GNUpod checks if this is true and does something like:

* create 'csTeSt'
* get the inode of 'csTeSt'
* get the inode of 'CStEsT'
* Compare it

Both inodes should be the same, because VFAT is *not* case sensitive,
only case preserve !

If the 2 inodes don't match (or one file does not exist), you'll get
this warning.. This means that someone broken VFAT for you.

But if you are not going to use your iPod with Windows/OSX, you can
ignore this warning.