Date: Sat, 16 Aug 1997 22:06:17 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= <ache@nagual.pp.ru> To: Paul Traina <pst@shockwave.com> Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-share@FreeBSD.ORG Subject: Re: cvs commit: src/share/skel dot.login dot.profile Message-ID: <Pine.BSF.3.96.970816214903.8342A-100000@lsd.relcom.eu.net> In-Reply-To: <199708161743.KAA29157@precipice.shockwave.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 16 Aug 1997, Paul Traina wrote: > Why must they be in login classes or .login.classes? LANG and MM_CHARSET can be in shell rc files still if users prefer it, but it is not a subject of _default_ dot.* files, it was the reason for removing. > This would seem to imply (unless people know about the file in ~, which is > quite non-standard) that the sysadmin of a machine needs to set the user's > home character type, which seems bogus to me...? They need to be set outside shell rc files in general case, consider following examples: 1) All programs you start in .login/.cshrc _before_ setenv becomes not localized. Enev shell itself is not localized before this setenv, it may affect startup messages or error diagnostics. 2) It is needed for shells with no startup files. 3) It is needed for shells which not support LANG changes on the fly. 4) In typical case of mass users setup, users not know anything about localization model but want to use their national language. It is more comfortable for sysadmin to have national login class for them which can be default for adduser. It is not sysadmin only priveledge since ~/.login_conf file can be maintained by user himself. -- Andrey A. Chernov <ache@null.net> http://www.nagual.pp.ru/~ache/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970816214903.8342A-100000>