incorrectly handles target paths with spaces

[Eugene V. Lyubimkin]

See http://bugs.debian.org/513948 for details.

[Geza Kovacs (gezakovacs)]

Fix committed as of rev 311

Also this issue seems to be due to an issue with /proc/mounts mangling the spaces, so it might occur with other uncommon labels as well, depending on how they're mangled in /proc/mounts:

/dev/sdc1 /media/has\040spaces vfat rw,nosuid,nodev,uid=500,fmask=0022,dmask=0022,codepage=cp437,iocharset=ascii,utf8 0 0

However the issue isn't consistent system-wide; the df output for the same drive was:

/dev/sdc1 245129 14 245115 1% /media/has spaces

[Geza Kovacs (gezakovacs)]

The space mangling issue seems to be present in vol_id as well, only it's using hexadecimal rather than octal - since it appears that backslashes aren't banned by certain disk labeling applications I'll just be sticking with a simple text find-replace solution.

[root@geza-laptop Desktop]# /lib/udev/vol_id /dev/sdc1
ID_FS_USAGE=filesystem
ID_FS_TYPE=vfat
ID_FS_VERSION=FAT32
ID_FS_UUID=0353-E120
ID_FS_UUID_ENC=0353-E120
ID_FS_LABEL=has spaces
ID_FS_LABEL_ENC=has\x20spaces
ID_FS_LABEL_SAFE=has_spaces