SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hi all, i'm using slackware 12.2 and i have 2 NTFS partitions mounted. Both were added to fstab in the setup process, and I modified fstab to add iocharset=utf8. Then i re-mounted the partitions and i could see all my files and directories.
However, the next time i turned on my box, i found out the partitions weren't showing those files and directories with special characters, so each time i reboot i have to
umount /ntfspartition && mount /ntfspartition
after this, i can see those files again. My question is, why they don't get mounted from the beginning with the utf8 charset? it seems at boot time, fstab setting "iocharset=utf8" is completely ignored.
Thanks niels.horn, i-ll try that... i solved it on my laptop without setting the locale param, instead i commented LANG=en_US and added LANG=es_MX.UTF-8 in /etc/profiles.d/lang.sh and that did the trick, besides i upgraded to ntfs-3g-2009-4-4, since full utf8 support for ntfs-3g was released since version 2009-1-1, and slack 12.2 ships with 1.15, and that did the trick.
However, i have the same issue in my desktop pc... i'll try just setting the locale param and see what happens. I'll post back the results.
P.S. If anyone would like to upgrade to the new version of ntfs-3g, just remember to backup your /usr/share/hal/fdi/policy/10osvendor/10-ntfs-3g-policy.fdi before removing ntfs-3g package, because it gets deleted after that, and you'll need to copy it back if you install from source.
what i get is the missing directories showing up this time, however accents are displayed as a 2 letter code like
ImÃ¡genes instead of Imágenes (as you may guess, or know, that's "images" in spanish), but i guess this is due to the system locale, which is still en_US and thunar displays those names that way, so i guess this is a solved matter. Thanks!!
Maybe I don't understand, my first dialect being Redneck.
Have you set this file up:
root@silas64:~# cat /etc/profile.d/lang.sh
# Set the system locale. (no, we don't have a menu for this ;-)
# For a list of locales which are supported by this machine, type:
# locale -a
# en_US is the Slackware default locale:
# 'C' is the old Slackware (and UNIX) default, which is 127-bit
# ASCII with a charmap setting of ANSI_X3.4-1968. These days,
# it's better to use en_US or another modern $LANG setting to
# support extended character sets.
# There is also support for UTF-8 locales, but be aware that
# some programs are not yet able to handle UTF-8 and will fail to
# run properly. In those cases, you can set LANG=C before
# starting them. Still, I'd avoid UTF unless you actually need it.
# Another option for en_US:
# One side effect of the newer locales is that the sort order
# is no longer according to ASCII values, so the sort order will
# change in many places. Since this isn't usually expected and
# can break scripts, we'll stick with traditional ASCII sorting.
# If you'd prefer the sort algorithm that goes with your $LANG
# setting, comment this out.
# End of /etc/profile.d/lang.sh
You can also use one for normal users in your ~/ directory: