On Fri, Mar 19, 2004 at 10:44:05PM -0800, Paul Johnson wrote:
Phil Edwards [EMAIL PROTECTED] writes:
Because 'dpkg -S' can't find it.
Right, nothing in Debian provides it.
This turns out not to be the case. After some more grepping, I found
that locales.postinst can create it. Probably
Because 'dpkg -S' can't find it.
And more to the point, what's looking at that file? It isn't my login shell,
it isn't any of the setup files that it looks at (.bashrc and so forth).
But the variables in that file are getting set somehow, and I'd like to
know how, and what's going to someday
On Fri, Mar 19, 2004 at 12:12:57PM +, Robert Harris wrote:
Phil Edwards wrote:
Because 'dpkg -S' can't find it.
And more to the point, what's looking at that file? It isn't my login
shell,
it isn't any of the setup files that it looks at (.bashrc and so forth).
But the variables in
On Fri, Mar 19, 2004 at 06:05:36AM -0500, Phil Edwards wrote:
Because 'dpkg -S' can't find it.
It is created by the locales package installation scripts.
And more to the point, what's looking at that file? It isn't my login shell,
it isn't any of the setup files that it looks at (.bashrc
On Friday 19 March 2004 01:03 pm, Phil Edwards wrote:
On Fri, Mar 19, 2004 at 12:12:57PM +, Robert Harris wrote:
Phil Edwards wrote:
Because 'dpkg -S' can't find it.
And more to the point, what's looking at that file? It isn't my
From my /etc/pam.d/login:
# This module parses
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thus spake Phil Edwards:
# Because 'dpkg -S' can't find it.
A little Googling indicated that your shell may look at it after /etc/profile.
But from what I can see, no package actually creates it. It may have been
created by a script invoked by you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Phil Edwards [EMAIL PROTECTED] writes:
Because 'dpkg -S' can't find it.
Right, nothing in Debian provides it. I created mine by hand.
And more to the point, what's looking at that file? It isn't my login shell,
it isn't any of the setup files
7 matches
Mail list logo
