From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050719 Fedora/1.7.10-1.3.1
Description of problem:
When I name mountpoint in auto.misc with cyrillic letters (KOI8-R), automount fails with following in /var/log/messages
automount: handle_packet_missing: path to be mounted is to long
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Create mount point in /etc/auto.misc
ï¿½ï¿½ï¿½ï¿½ï¿½ -fstype=auto :/dev/cdrom
(ï¿½ï¿½ï¿½ï¿½ï¿½ - it's a cyrillic transliteration of latin cdrom :-) )
2. ls /misc/ï¿½ï¿½ï¿½ï¿½ï¿½
Actual Results: 1. ls: /mnt/ï¿½ï¿½ï¿½ï¿½ï¿½: No such file or directory
2. /var/log/messages :
Sep 8 09:29:00 SukholetSI automount: handle_packet_missing: path to be mounted is to long
Expected Results: mounted cd in my drive
bugzilla eats all my cyrillic letters, even the encoding of this page is UTF8
*** Bug 167777 has been marked as a duplicate of this bug. ***
*** Bug 167778 has been marked as a duplicate of this bug. ***
sorry for a duplicates, that whas something with my
It was unable to me to send a bug, may be due to cyrillic letters in messages?
I'll take a look at this. Thanks!
In theory, you should be able to use encodings other than ascii, so long as the
encoding of the shell matches the encoding of the automount map. It *may* work,
but no guarantees. (I'll note that I *can't* get it to work).
Is this really posing a problem in your environment? Do you have a workaround?
Since no one else has reported this problem, this is kind of low priority for
me. Let me know if it is a big problem for you, and I'll see what I can do.
Of course, I've change my mount points to latin names - that was a workaround.
But this is not very usefull.
I think, that it should be not really hard to fix - just change something like
'getstring' in C code to have any type of characters (i.e. not only [0-127] but
And possible, to have mountpoints with UTF8 (default locale for modern RH lunuxes)?
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Fedora Core 3 is not maintained anymore.
Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.