Hi Flemming
Which locale the system uses should not matter. as long as it is
installed. C is the default and basicly does no translation with gettext
(I think). Or at least it is that Language which always has Message
files in /usr/share/locale.
In any case the situation is pretty simple.
The Zo
Hello Till,
On 26/11/17 22:53, Till Wegmüller wrote:
Hmm
I am affraid several Unix Machanisms block you here.
First mount was designed so that a filesystem that is in access can not
be unmounted. This so that an admin can not accidentally kill the system
with an umount. I am not aware of a fil
Thanks for the response.
Yes this is a zone and I connect via ssh.
You are right zlogin behaves differently. In may case it set all LC's to
"C" and LANG=""
I don't get any complaints about locale but its not really correct is it ?
I would expect it to be en_US.UTF-8 as in the init file.
pkg list
Hey
I noticed a similar issue when logging into a zone via ssh. It works for
me via zlogin.
Are you inside a zone connecting via SSH?
What is the output of pkg list *locale* ?
Does en_US.UTF-8 exist in /usr/share/locale/ ?
How have you installed the system and when? With which medium?
Greeti
Hmm
I am affraid several Unix Machanisms block you here.
First mount was designed so that a filesystem that is in access can not
be unmounted. This so that an admin can not accidentally kill the system
with an umount. I am not aware of a filesystem based mechanism that
leaves the access once the
Hi.
I am stuck on a issue with locale not working.
It was discovered when pkg started issuing the following messages on
invocation:
# pkg search -rp rcs
pkg: Unable to set locale; locale package may be broken or
not installed. Reverting to C locale.
PACKAGE PUB
