From: "Günter Kukkukk" <linux-KQewbsS9MvBBDgjK7y7TUQ@public.gmane.org>
To: Thomas Wolff <towo-JHPtuYzOr/0@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: mount error 79 = Can not access a needed shared library
Date: Fri, 28 Jun 2013 04:27:16 +0200 [thread overview]
Message-ID: <201306280427.16839.linux@kukkukk.com> (raw)
In-Reply-To: <51CCA586.1070105-JHPtuYzOr/0@public.gmane.org>
Am Donnerstag, 27. Juni 2013, 22:50:14 schrieb Thomas Wolff:
Hello Thomas,
> My attempt to mount with -o iocharset=utf8 fails with this message:
> mount error 79 = Can not access a needed shared library
>
> By google, I found one hint to "compile and install" nls_utf8.ko but
> without a mention of where to get that from or how to proceed anyway
> (very funny).
>
> The system is Debian on a ppc, uname -a:
> Linux MyBookLive 2.6.32.11-svn21605 #1 Fri Oct 15 17:13:23 PDT 2010 ppc
> GNU/Linux
>
> aptitude search does not show any useful results for nls
All those NLS related stuff is built into the kernel - usually as
modules. So you _cannot_ just install those kernel modules "on the fly".
Some linux .config file (used for the kernel build) might contain
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf8"
CONFIG_NLS_CODEPAGE_437=m
CONFIG_NLS_CODEPAGE_737=m
...
Which results to nls kernel modules in e.g.
lib/modules/2.6.32.11-svn21605/kernel/fs/nls/
Note - check for subpath "2.6.32.11-svn21605" above - it might be
different.
Strange is that utf8 seems to be not build-in in your kernel version.
(Should be the default for years)
Cheers, Günter
>
> ------
> Thomas
> --
> To unsubscribe from this list: send the line "unsubscribe linux-cifs" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-06-28 2:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 20:50 mount error 79 = Can not access a needed shared library Thomas Wolff
[not found] ` <51CCA586.1070105-JHPtuYzOr/0@public.gmane.org>
2013-06-27 21:15 ` Shirish Pargaonkar
2013-06-28 2:27 ` Günter Kukkukk [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201306280427.16839.linux@kukkukk.com \
--to=linux-kqewbss9mvbbdgjk7y7tuq@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=towo-JHPtuYzOr/0@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.