Howdy!
I encountered something minor to usual problems,
people have on this list, but it makes me nervous.
I bought brand new usb flash stick and used it to
solve the issue on handheld. After putting files
on it, I have them in format 8.3. The option to
mount -t was msdosfs. It should bring me long file
names, but it does not. Mu stupid question would
be: did I chose wrong file system? Or is this usb
drive preformatted in something strange like fat16?
This manner surprised me so much, that I did not
believed my eyes. 6.2 on amd64.
Best regards
Zoran
* Zoran Kolic <zkolic@sbb.co.yu> [2007-10-14 08:48]:> I encountered something minor to usual problems, > people have on this list, but it makes me nervous. > I bought brand new usb flash stick and used it to > solve the issue on handheld. After putting files > on it, I have them in format 8.3. The option to > mount -t was msdosfs. It should bring me long file > names, but it does not. Mu stupid question would > be: did I chose wrong file system? Or is this usb > drive preformatted in something strange like fat16?This sounds like the documented behavior if the drive was empty or had no long filenames when you mounted it. From mount_msdosfs(8): "If neither -s nor -l are given, mount_msdosfs searches the root directory of the file system to be mounted for any existing Win'95 long filenames. If no such entries are found, but short DOS filenames are found, -s is the default. Otherwise -l is assumed." -o longnames should do the trick. Alson
> From: Alson van der Meulen <alson+ml@alm.flutnet.org> > This sounds like the documented behavior if the drive was empty or had > no long filenames when you mounted it. From mount_msdosfs(8): > "If neither -s nor -l are given, mount_msdosfs searches the root > directory of the file system to be mounted for any existing > Win'95 long filenames. If no such entries are found, but short > DOS filenames are found, -s is the default. Otherwise -l is > assumed." > -o longnames should do the trick.Thank you, Alson! Works! I forgot how to handle ms things. Even worse, I contacted shop technician and got an information that it was intended to reformat as the very first. He said explicitely it was fat16 formatted. What would you do in this situation? Go as it is now or do something like (I've read manual finaly): newfs_msdos -F 32 /dev/da0 Best regards Zoran
> From: Alson van der Meulen <alson+ml@alm.flutnet.org> > This sounds like the documented behavior if the drive was empty or had > no long filenames when you mounted it. From mount_msdosfs(8): > "If neither -s nor -l are given, mount_msdosfs searches the root > directory of the file system to be mounted for any existing > Win'95 long filenames. If no such entries are found, but short > DOS filenames are found, -s is the default. Otherwise -l is > assumed." > -o longnames should do the trick.Thank you, Alson! Works! I forgot how to handle ms things. Even worse, I contacted shop technician and got an information that it was intended to reformat as the very first. He said explicitely it was fat16 formatted. What would you do in this situation? Go as it is now or do something like (I've read manual finaly): newfs_msdos -F 32 /dev/da0 Best regards Zoran