RE: freebsd and utf-8 directory names
hi, as I said the evironment setting for the Hungarian local per the handb -Original Message- From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-curr...@freebsd.org] On Behalf Of Jamie Landeg-Jones Sent: Thursday, July 03, 2014 5:58 AM To: ke...@freebsd.org; d...@gmx.com Cc: freebsd-current@freebsd.org; thera...@freebsd.org Subject: Re: freebsd and utf-8 directory names Kevin Lo ke...@freebsd.org wrote: Well, I'm going to close that PR. :-) [ ... ] I basically replied with the same thing in a followup on the bug itself exactly 24 hours ago! :-) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191540 cheers, Jamie ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
RE: freebsd and utf-8 directory names
thanks, I will do that. I started to setup my locale again, and found that earlier I should have made a mistake because the new setup (almost) perfectly works: I set up login class for me following the handbook as hungarian (LANG=hu_HU.UTF-8, and charset=UTF-8; set keyboard layout to hungarian with setxkbmap hu, and used the hungarian locale in fstab to mount the fat32 partition.). there are two characters in the Hungarian alphabet which are not in the ISO-Latin1 code set (o with double accent and u with double accent, both lower and upper case) which are displayed as space in filenames, but now libreoffice is able to open the files. All other hungarian characters appeared as normal. I will do the test you suggested but it can take 1-2 days, I do not have time for it right now. rgds András Krasznai -Original Message- From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-curr...@freebsd.org] On Behalf Of Kevin Lo Sent: Thursday, July 03, 2014 5:33 AM To: d...@gmx.com Cc: freebsd-current@freebsd.org; David Chisnall Subject: Re: freebsd and utf-8 directory names On Wed, Jul 02, 2014 at 12:27:07AM +0200, d...@gmx.com wrote: David Chisnall wrote, On 07/01/2014 19:06: Please note that forums.freebsd.org is not a bug tracker. I tried searching the bug tracker for bugs with FAT and filename or FAT and utf-8/utf8/character in their names and could not find any reference to this issue. If you actually want to see bugs fixed, rather than just complain about them, please file them here: https://bugs.freebsd.org/bugzilla/enter_bug.cgi Make sure that you provide all of the steps required to reproduce them. I neglected to submit a bug report because: (1) there were already at least 3 bug reports related to (FAT32 and) character sets or encodings, some of them even had patches; (2) the reports were very old, indicating that the FreeBSD developers don't care about FAT32; (3) at least one report was seemingly related, and I didn't want to create a(nother) possible duplicate. But now, eat this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191540 Well, I'm going to close that PR. :-) First, set LANG environment variable to hu_HU.UTF-8 in your case: # setenv LANG hu_HU.UTF-8 Second, mount the FAT32 partition in Hungarian locale: # mount_msdosfs -L hu_HU.UTF-8 /dev/da0s1 /mnt Third, untar your attachement file: # tar xvf /mnt/files.zip x 1’.txt x 2–.txt # stat 1’.txt 128 244744 -rwxr-xr-x 1 root wheel 4294967295 0 Jan 1 08:00:00 1980 Aug 1 16:57:52 2011 Aug 1 16:57:52 2011 Jul 3 11:28:24 2014 16384 0 0x800 1’.txt # stat 2–.txt 128 244746 -rwxr-xr-x 1 root wheel 4294967295 0 Jan 1 08:00:00 1980 Aug 1 16:55:20 2011 Aug 1 16:55:20 2011 Jul 3 11:28:24 2014 16384 0 0x800 2–.txt Let me know if that works for you, thanks. Kevin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
RE: freebsd and utf-8 directory names
Hi, Kevin, I made the experiment and there was no fault, the result contains the stat outputs. I used login-class (according to the handbook) to set the environment, and added the -L hu_HU.UTF-8 option to the appropriate line in fstab rgds András From: owner-freebsd-curr...@freebsd.org [owner-freebsd-curr...@freebsd.org] On Behalf Of Kevin Lo [ke...@freebsd.org] Sent: Thursday, July 03, 2014 5:33 AM To: d...@gmx.com Cc: freebsd-current@freebsd.org; David Chisnall Subject: Re: freebsd and utf-8 directory names On Wed, Jul 02, 2014 at 12:27:07AM +0200, d...@gmx.com wrote: David Chisnall wrote, On 07/01/2014 19:06: Please note that forums.freebsd.org is not a bug tracker. I tried searching the bug tracker for bugs with FAT and filename or FAT and utf-8/utf8/character in their names and could not find any reference to this issue. If you actually want to see bugs fixed, rather than just complain about them, please file them here: https://bugs.freebsd.org/bugzilla/enter_bug.cgi Make sure that you provide all of the steps required to reproduce them. I neglected to submit a bug report because: (1) there were already at least 3 bug reports related to (FAT32 and) character sets or encodings, some of them even had patches; (2) the reports were very old, indicating that the FreeBSD developers don't care about FAT32; (3) at least one report was seemingly related, and I didn't want to create a(nother) possible duplicate. But now, eat this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191540 Well, I'm going to close that PR. :-) First, set LANG environment variable to hu_HU.UTF-8 in your case: # setenv LANG hu_HU.UTF-8 Second, mount the FAT32 partition in Hungarian locale: # mount_msdosfs -L hu_HU.UTF-8 /dev/da0s1 /mnt Third, untar your attachement file: # tar xvf /mnt/files.zip x 1’.txt x 2–.txt # stat 1’.txt 128 244744 -rwxr-xr-x 1 root wheel 4294967295 0 Jan 1 08:00:00 1980 Aug 1 16:57:52 2011 Aug 1 16:57:52 2011 Jul 3 11:28:24 2014 16384 0 0x800 1’.txt # stat 2–.txt 128 244746 -rwxr-xr-x 1 root wheel 4294967295 0 Jan 1 08:00:00 1980 Aug 1 16:55:20 2011 Aug 1 16:55:20 2011 Jul 3 11:28:24 2014 16384 0 0x800 2–.txt Let me know if that works for you, thanks. Kevin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org result Description: result ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
RE: freebsd and utf-8 directory names
Ok, I wrote yesterday that I will test it (again, I would say, because when I recognised the problem I did some testing. I picked up the FreeBSD Handbook and repeated the procedure listed in the localization section - with no success or at most half success). Naturally I may have made mistake, may have omitted some steps, but I will repeat. anyway, the whole thing started as working in a Windows environment I wanted to setup FreeBSD as a second operating system on my laptop, and I wanted to be able to do my work using freebsd only. The partitioning was done originally from Windows, Fat32 was formatted from Windows 7, and I use fat32 because when I started to use FreeBSD the NTFS support in FreeBSD was only for reading. The directory structure was created from windows, most of the files are various documents created either by me or my colleaugues and most of them are in some of Microsoft document format for compatibility reasons (I mean compatibility with my colleaugues). rgds András Krasznai -Original Message- From: Jamie Landeg-Jones [mailto:ja...@dyslexicfish.net] Sent: Tuesday, July 01, 2014 7:40 PM To: MS - Krasznai András; freebsd-current@freebsd.org; d...@gmx.com Subject: Re: freebsd and utf-8 directory names MS - Krasznai Andr??s krasznai.and...@mands.hu wrote: xfe display the file and directory names correctly together with creation date and time (simple 'ls' does not; it shows double question marks in the place of Hungarian characters. ls | od -c shows that such characters are represented in ls output as two characters e.g. 241 253 or such, I can test again but now I do not remember the exact numbers; the first of the two is the same for all Hungarian characters) That says to me that your locale is still not set correctly. The ls on it's own could be due to a non-compatible terminal emulator, but the fact that 'od' is showing two bytes rather than trying to display a character (however messed up the output may be) implies the characters are simply not valid in the locale you have set. It would be useful to have the exact numbers from the 'od' (a test filename with more than 2 Hungarian characters would be useful) and an approximate description (or screenshot) on how they should look. cheers, jamie ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
RE: freebsd and utf-8 directory names
Hi, I am not very satisfied with this situation. Today I was looking up the Hungarian FreeBSD site, but the Hungarian translation of the handbook deals only with settings for German, Russian and Japanese environment. A little additional info: I installed xfe (x11-fm/xfe) file manager in the same freebsd configuration. This application displays and handles those diretories and files perfectly, but as soon as I want to open such a file with double click on it (I set xfe to invoke libreoffice in this case) libreoffice still refuses to open the file. Even midnight commander fails to handle such files. What does xfe do differently? rgds András -Original Message- From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-curr...@freebsd.org] On Behalf Of d...@gmx.com Sent: Tuesday, July 01, 2014 4:42 PM To: freebsd-current@freebsd.org Subject: Re: freebsd and utf-8 directory names MS - Krasznai András wrote, On 06/30/2014 08:30: There is a partition formatted for FAT32 where I store documents which I would like to view (and edit) both in windows and freebsd. The problem is that if the path name contains certain Hungarian characters (e.g o with double accent), then libreoffice in FreeBSD refuses to open them complaining about illegal characters. The directory was created in windows, the document also, and I can handle them perfectly from windows (what is more, libreoffice under a linux can also open those documents). Some accented characters are shown as a question mark in FreeBSD, and some others are as a black rectangle; these latter are causing problems. If a file-nam contains such characters then the file is shown as 0- length in Midnight Commander. This is not limited to Hungarian characters. There are bugs in FreeBSD's FAT handling code. According to an IRC discussion with mux, FreeBSD has plenty of VOP_LOOKUP bugs, and this case hits such a bug. To allow FreeBSD to read files with fancy UTF-8 characters in their names, mount the FAT32 partition with ``-o shortnames''. Then, you won't be able to use proper file naming (so this is not even a workaround), but at least you'll be able to read the said files. Poke the FreeBSD developers to start fixing bugs, maybe (but not very likely) that will help. Also, you're at least the 3rd user (I'm at least the 2nd) that runs into this case; ie., here's a report: http://forums.freebsd.org/showthread.php?t=14612 (of course, this does not contain a solution). ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
RE: freebsd and utf-8 directory names
xfe display the file and directory names correctly together with creation date and time (simple 'ls' does not; it shows double question marks in the place of Hungarian characters. ls | od -c shows that such characters are represented in ls output as two characters e.g. 241 253 or such, I can test again but now I do not remember the exact numbers; the first of the two is the same for all Hungarian characters) rgds András -Original Message- From: d...@gmx.com [mailto:d...@gmx.com] Sent: Tuesday, July 01, 2014 5:20 PM To: MS - Krasznai András; freebsd-current@freebsd.org Subject: Re: freebsd and utf-8 directory names MS - Krasznai András wrote, On 07/01/2014 17:07: I installed xfe (x11-fm/xfe) file manager in the same freebsd configuration. This application displays and handles those diretories and files perfectly, but as soon as I want to open such a file with double click on it (I set xfe to invoke libreoffice in this case) libreoffice still refuses to open the file. [...] What does xfe do differently? What do you mean by handling and displaying properly? Listing (directory contents) is one thing, being able to stat or open the file is different. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
RE: freebsd and utf-8 directory names
hi I use the -L hu_HU.UTF-8 option in fstab, but I admit I forgot to set the LCxxx variables. I will test it soon. rgds András -Original Message- From: Gyrd Thane Lange [mailto:gyrd...@thanelange.no] Sent: Tuesday, July 01, 2014 5:30 PM To: Rainer Hurling; MS - Krasznai András; freebsd-current@freebsd.org Subject: Re: freebsd and utf-8 directory names Den 30. juni 2014 08:56, skrev Rainer Hurling: Am 30.06.2014 08:30 (UTC+1) schrieb MS - Krasznai András: Hi I have been using FreeBSD as desktop since 2003, and living in a mixed (windows-linux) environment I installed FreeBSd along with my usual (Windows 7) work environment, I have a dualboot configured laptop. I use FreeBSD-10 STABLE. There is a partition formatted for FAT32 where I store documents which I would like to view (and edit) both in windows and freebsd. The problem is that if the path name contains certain Hungarian characters (e.g o with double accent), then libreoffice in FreeBSD refuses to open them complaining about illegal characters. The directory was created in windows, the document also, and I can handle them perfectly from windows (what is more, libreoffice under a linux can also open those documents). Some accented characters are shown as a question mark in FreeBSD, and some others are as a black rectangle; these latter are causing problems. If a file-nam contains such characters then the file is shown as 0- length in Midnight Commander. I tried some steps described in the „Localization” part of the FreeBSD Handbook, but things did not improve. I installed PC-BSD with Hungarian language support, thinking that it would handle the localized directory names correctly but no, it gives the same error message. This problem is really annoying. How could I solve it? In my German environment I also use FAT32 formatted drives, mounted like: /dev/adaXsX /XXXmsdosfs rw,large,-Lde_DE.UTF-8 0 0 This should also work for Hungarian? I second this advice, it should work well for any language (It certainly is fine for my Norwegian). To expand on Rainer's suggestion: The -L parameter in the mount line is from the mount_msdosfs(8) utility. The man page says: -L locale Specify locale name used for file name conversions for DOS and Win'95 names. By default ISO 8859-1 assumed as local character set. The locale of your environment and mount command must match. In my case it is: LC_CTYPE=no_NO.UTF-8 mount_msdosfs -L no_NO.UTF-8 /dev/da3s1 /mnt/tmp (Regarding whether the default of ISO 8859-1 for mount_msdosfs should be changed to some UTF-8 locale to better match what people are using in this age is an entirely different matter. ;-) Best regards, Gyrd ^_^ HTH, Rainer Hurling Krasznai András rendszermérnök MS Informatikai Zrt. 1136 Budapest, Pannónia u. 17/A. Telefon: +36 1 703-2923 Mobil:+36 30 703-2923 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
freebsd and utf-8 directory names
Hi I have been using FreeBSD as desktop since 2003, and living in a mixed (windows-linux) environment I installed FreeBSd along with my usual (Windows 7) work environment, I have a dualboot configured laptop. I use FreeBSD-10 STABLE. There is a partition formatted for FAT32 where I store documents which I would like to view (and edit) both in windows and freebsd. The problem is that if the path name contains certain Hungarian characters (e.g o with double accent), then libreoffice in FreeBSD refuses to open them complaining about illegal characters. The directory was created in windows, the document also, and I can handle them perfectly from windows (what is more, libreoffice under a linux can also open those documents). Some accented characters are shown as a question mark in FreeBSD, and some others are as a black rectangle; these latter are causing problems. If a file-nam contains such characters then the file is shown as 0- length in Midnight Commander. I tried some steps described in the „Localization” part of the FreeBSD Handbook, but things did not improve. I installed PC-BSD with Hungarian language support, thinking that it would handle the localized directory names correctly but no, it gives the same error message. This problem is really annoying. How could I solve it? Krasznai András rendszermérnök MS Informatikai Zrt. 1136 Budapest, Pannónia u. 17/A. Telefon: +36 1 703-2923 Mobil:+36 30 703-2923 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
using single gcc compiler
Hi I use freebsd-10 as desktop . Compiling the system takes ages, and rather long time is spent in compiling different gcc compiler versions for various ports, e.g. - gcc-4.7.3- required by avidemux; - gcc-4.6.4_1,1: required by opera,operaplugins, gcc, gcc4.8 - gcc 4.8.4_xxx: required by rawtherapee Is there a way to specify that I want to use gcc 4.8.4 for all compilations which do not use clang? rgds Krasznai András rendszermérnök MS Informatikai Zrt. 1136 Budapest, Pannónia u. 17/A. Telefon: +36 1 703-2923 Mobil:+36 30 703-2923 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
RE: using single gcc compiler
Thanks. I will check which of my installed ports require any special gcc version, and which specify a minimal version. Then I will try to find replacement for those which require a fixed version. rgds Andras Krasznai -Original Message- From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-curr...@freebsd.org] On Behalf Of Allan Jude Sent: Monday, June 02, 2014 3:22 PM To: freebsd-current@freebsd.org Subject: Re: using single gcc compiler On 2014-06-02 08:52, Mark Felder wrote: On 2014-06-02 07:05, MS - Krasznai András wrote: Hi I use freebsd-10 as desktop . Compiling the system takes ages, and rather long time is spent in compiling different gcc compiler versions for various ports, e.g. - gcc-4.7.3- required by avidemux; - gcc-4.6.4_1,1: required by opera,operaplugins, gcc, gcc4.8 - gcc 4.8.4_xxx: required by rawtherapee Is there a way to specify that I want to use gcc 4.8.4 for all compilations which do not use clang? Some ports only work with specific versions of GCC. If you believe a specific port should be able to use GCC 4.8.4 I would recommend testing it and filing a PR so the port maintainer can confirm and update the port. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org GCC_DEFAULT_VERSION is set to 4.6 in ports/Mk/bsd.gcc.mk Unlike some other default versions, it isn't setup to be able to be overridden from make.conf As Mark mentioned, some applications have a requirement for a specific version of gcc, while others will specify a minimum version (USE_GCC=4.7+) This is why you end up needing all of those versions. You may be able to reduce some of the fragmentation by installing the highest version first, then any app that can use that will, and only those requiring a specific version will pull those in. The root issue is that some apps will just refuse to compile on newer versions of GCC -- Allan Jude ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
dual-booting windows 7 and freebsd 10 from gpt partition SSD
hi I have been using freebsd and windows 7 on mbr partitioned hdd (using easybcd on windows to manipulate boot menu and boot code). recently I bought an new machine with Intel I7 processor, uefi bios, ssd and installed windows 7 64-bit first. after that I installed freebsd 10 (amd64); I used guided partitioning, which created a 64-kB freebsd-boot partition, a 48GB / partition and a swap about 2.5 GB. Then I tried to set up booting by the same method: install easybcd in windows, then set up boot menu with easybcd, add an entry freebsd as BSD/FreeBSD type entry, but this time I am not able to get it work. Win 7 boots OK, but freebsd does not start, the windows boot manager complains about missing or corrupt boot block, which is definitely on the given full path. How can I get a working dual booting system in this case? Can anbody help me? Regards Krasznai András rendszermérnök MS Informatikai Zrt. 1136 Budapest, Pannónia u. 17/A. Telefon: +36 1 703-2923 Mobil:+36 30 703-2923 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
mounting ntfs partition from /etc/fstab
Hi I am using freebsd 10 64bit on an IBM T510. I can not mount ntfs partition from /etc/fstab with the normal method, thatis specifying /dev/ada0s2 /windows/C ntfs-3g ro 0 0 in /etc/fstab the mount -a command gives me an error message: /dev/ada0s2:Operation not supported by the device but I can mount the same partition from the command line: ntfs-3g -o ro /dev/ada0s2 /windows/C works. What is the cause of this problem? Krasznai András rendszermérnök MS Informatikai Zrt. 1136 Budapest, Pannónia u. 17/A. Telefon: +36 1 703-2923 Mobil:+36 30 703-2923 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
