Hi!
On Sat, Jan 08, 2022 at 07:54:33PM +0100, Andreas Schwab wrote:
> On Jan 08 2022, Segher Boessenkool wrote:
>
> > For example, that en_US.UTF-8 (as it is on Mac OS) will not work on most
> > Linux systems, which use en_US.utf8 instead.
>
> en_US.UTF-8 works perfectly well on glibc. In fact,
On Jan 08 2022, Segher Boessenkool wrote:
> For example, that en_US.UTF-8 (as it is on Mac OS) will not work on most
> Linux systems, which use en_US.utf8 instead.
en_US.UTF-8 works perfectly well on glibc. In fact, that's the
preferred spelling.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Ke
On Sat, Jan 08, 2022 at 11:51:54AM +0100, Andreas Schwab via cfarm-users wrote:
> On Jan 07 2022, Christian Jullien via cfarm-users wrote:
> > Also, the following variables are set
> >
> > LANG=zh_CN
> > LC_ALL=zh_CN
> > LC_CTYPE=zh_CN
> > LC_NUMERIC=zh_CN
> > LC_TYPE=zh_CN
> >
> > I set them in my
The machines should be running an NTP daemon to keep the clock
up-to-date.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
___
cfarm-users ma
On Jan 07 2022, Christian Jullien via cfarm-users wrote:
> Also, the following variables are set
>
> LANG=zh_CN
> LC_ALL=zh_CN
> LC_CTYPE=zh_CN
> LC_NUMERIC=zh_CN
> LC_TYPE=zh_CN
>
> I set them in my .bash_profile to more common en_US.UTF-8
>
> You probably want to set them globally for all users.
