On Mon 11 Feb 2019 at 17:48:23 (-), Curt wrote:
> On 2019-02-11, Greg Wooledge wrote:
> > On Mon, Feb 11, 2019 at 05:26:34PM -, Curt wrote:
> >> I follow your logic. Give me everything in /etc/skel/ beginning with a dot.
> >> Which works. But apparently a dot is also something else. Like
On 2019-02-11, Greg Wooledge wrote:
> On Mon, Feb 11, 2019 at 05:26:34PM -, Curt wrote:
>> I follow your logic. Give me everything in /etc/skel/ beginning with a dot.
>> Which works. But apparently a dot is also something else. Like a directory.
>>
>> curty@einstein:~$ ls /etc/skel/.*
>>
On Mon, Feb 11, 2019 at 05:26:34PM -, Curt wrote:
> I follow your logic. Give me everything in /etc/skel/ beginning with a dot.
> Which works. But apparently a dot is also something else. Like a directory.
>
> curty@einstein:~$ ls /etc/skel/.*
> /etc/skel/.bash_logout /etc/skel/.bashrc
On 2019-02-11, rhkra...@gmail.com wrote:
> On Monday, February 11, 2019 08:07:24 AM Curt wrote:
>> On 2019-02-11, rhkra...@gmail.com wrote:
>> > There is a directory /etc/sket (with all hidden files thus you need
>> > something like ls /etc/skel/.* to get a listing).
>>
>> I believe you need
On Monday, February 11, 2019 08:07:24 AM Curt wrote:
> On 2019-02-11, rhkra...@gmail.com wrote:
> > There is a directory /etc/sket (with all hidden files thus you need
> > something like ls /etc/skel/.* to get a listing).
>
> I believe you need something like 'ls -a /etc/skel/', in fact, to see
On Sun, Feb 10, 2019 at 07:28:02PM -0500, Lee wrote:
> Which is semi-interesting I guess, but you're the one that wanted a
> single location to add $PATH elements for all current & future users -
> yes? The interesting answer would be if adding
> export PATH=$PATH:/foo
> to /etc/bash.bashrc is
On Mon 11 Feb 2019 at 09:53:39 (+0100), to...@tuxteam.de wrote:
> On Sun, Feb 10, 2019 at 04:22:44PM -0600, Richard Owlett wrote:
> > On 02/10/2019 03:42 PM, to...@tuxteam.de wrote:
> > >On Sun, Feb 10, 2019 at 02:57:22PM -0600, Richard Owlett wrote:
> > >
> > >[...]
> > >
> > >>Unless someone can
On 2019-02-11, rhkra...@gmail.com wrote:
> On Monday, February 11, 2019 03:57:14 AM to...@tuxteam.de wrote:
>> On Sun, Feb 10, 2019 at 09:07:13PM -0600, David Wright wrote:
>> > On Fri 08 Feb 2019 at 10:08:49 (-0500), Dan Ritter wrote:
>> > > Richard Owlett wrote:
>> > > > By my problem
On Monday, February 11, 2019 03:57:14 AM to...@tuxteam.de wrote:
> On Sun, Feb 10, 2019 at 09:07:13PM -0600, David Wright wrote:
> > On Fri 08 Feb 2019 at 10:08:49 (-0500), Dan Ritter wrote:
> > > Richard Owlett wrote:
> > > > By my problem definition, any thing in /home/user is not relevant as
>
On Sun, Feb 10, 2019 at 09:07:13PM -0600, David Wright wrote:
> On Fri 08 Feb 2019 at 10:08:49 (-0500), Dan Ritter wrote:
> > Richard Owlett wrote:
> > > By my problem definition, any thing in /home/user is not relevant as I
> > > explicitly want something that affects all current and future
On Sun, Feb 10, 2019 at 04:22:44PM -0600, Richard Owlett wrote:
> On 02/10/2019 03:42 PM, to...@tuxteam.de wrote:
> >On Sun, Feb 10, 2019 at 02:57:22PM -0600, Richard Owlett wrote:
> >
> >[...]
> >
> >>Unless someone can point to a single location to modify that:
> >> 1. modify existing user(s)
On Fri 08 Feb 2019 at 10:08:49 (-0500), Dan Ritter wrote:
> Richard Owlett wrote:
> > By my problem definition, any thing in /home/user is not relevant as I
> > explicitly want something that affects all current and future users.
>
> Everybody, no matter what?
>
> pam_env can do that.
>
> PAM
On Sun 10 Feb 2019 at 14:57:22 (-0600), Richard Owlett wrote:
> On 02/08/2019 12:55 PM, David Wright wrote:
> > On Fri 08 Feb 2019 at 07:18:39 (-0600), Richard Owlett wrote:
> > > I'm running Debian Stretch with MATE desktop.
> > > I want the current user and all future users to include all
> > >
On 2/10/19, Richard Owlett wrote:
> On 02/10/2019 05:00 PM, Lee wrote:
>> On 2/10/19, Andy Smith wrote:
>>> Hello,
>>>
>>> On Sun, Feb 10, 2019 at 02:57:22PM -0600, Richard Owlett wrote:
I used "grep -r /usr/local/games /etc" which yielded "/etc/login.defs"
and
"/etc/profile".
On Sun, Feb 10, 2019 at 03:49:00PM -0600, Richard Owlett wrote:
> On 02/10/2019 03:26 PM, Andy Smith wrote:
> >So what changes are you making and how are you checking for them?
I note you have neglected to explain what changes you are making, which
would be essential for us to help you with why
On 02/10/2019 05:00 PM, Lee wrote:
On 2/10/19, Andy Smith wrote:
Hello,
On Sun, Feb 10, 2019 at 02:57:22PM -0600, Richard Owlett wrote:
I used "grep -r /usr/local/games /etc" which yielded "/etc/login.defs"
and
"/etc/profile". Editing those two files had no effect.
How are you determining
On 2/10/19, Andy Smith wrote:
> Hello,
>
> On Sun, Feb 10, 2019 at 02:57:22PM -0600, Richard Owlett wrote:
>> I used "grep -r /usr/local/games /etc" which yielded "/etc/login.defs"
>> and
>> "/etc/profile". Editing those two files had no effect.
>
> How are you determining that changes to
On 02/10/2019 03:42 PM, to...@tuxteam.de wrote:
On Sun, Feb 10, 2019 at 02:57:22PM -0600, Richard Owlett wrote:
[...]
Unless someone can point to a single location to modify that:
1. modify existing user(s)
2. have effect for ALL future users
3. survive updating to future releases
On 02/10/2019 03:26 PM, Andy Smith wrote:
Hello,
On Sun, Feb 10, 2019 at 02:57:22PM -0600, Richard Owlett wrote:
I used "grep -r /usr/local/games /etc" which yielded "/etc/login.defs" and
"/etc/profile". Editing those two files had no effect.
How are you determining that changes to
On Sun, Feb 10, 2019 at 02:57:22PM -0600, Richard Owlett wrote:
[...]
> Unless someone can point to a single location to modify that:
> 1. modify existing user(s)
> 2. have effect for ALL future users
> 3. survive updating to future releases
> I'll drop the issue.
> Thanks all.
Did you
Hello,
On Sun, Feb 10, 2019 at 02:57:22PM -0600, Richard Owlett wrote:
> I used "grep -r /usr/local/games /etc" which yielded "/etc/login.defs" and
> "/etc/profile". Editing those two files had no effect.
How are you determining that changes to /etc/profile had no effect?
Because changes there
On 02/08/2019 12:55 PM, David Wright wrote:
On Fri 08 Feb 2019 at 07:18:39 (-0600), Richard Owlett wrote:
I'm running Debian Stretch with MATE desktop.
I want the current user and all future users to include all
directories in root's $PATH.
If you're talking about PATH, then you're talking
On Fri 08 Feb 2019 at 07:18:39 (-0600), Richard Owlett wrote:
> I'm running Debian Stretch with MATE desktop.
> I want the current user and all future users to include all
> directories in root's $PATH.
If you're talking about PATH, then you're talking about logging in.
So of equal importance to
On Fri, Feb 08, 2019 at 08:58:28AM -0600, Richard Owlett wrote:
> On 02/08/2019 07:37 AM, to...@tuxteam.de wrote:
> >More background: processes inherit their environment from their
> >parent process, and so on.
> >
> >[snip] there are "checkpoints" at which the (user) environment
> >can be set.
>
Richard Owlett wrote:
> By my problem definition, any thing in /home/user is not relevant as I
> explicitly want something that affects all current and future users.
Everybody, no matter what?
pam_env can do that.
PAM is the pluggable authentication module system, and controls
all sorts of
On 02/08/2019 07:37 AM, to...@tuxteam.de wrote:
On Fri, Feb 08, 2019 at 08:22:54AM -0500, Roberto C. Sánchez wrote:
On Fri, Feb 08, 2019 at 07:18:39AM -0600, Richard Owlett wrote:
I'm running Debian Stretch with MATE desktop.
I want the current user and all future users to include all
On Fri, Feb 08, 2019 at 08:22:54AM -0500, Roberto C. Sánchez wrote:
> On Fri, Feb 08, 2019 at 07:18:39AM -0600, Richard Owlett wrote:
> > I'm running Debian Stretch with MATE desktop.
> > I want the current user and all future users to include all directories in
> > root's $PATH.
> >
> > I
On Fri, Feb 08, 2019 at 07:18:39AM -0600, Richard Owlett wrote:
> I'm running Debian Stretch with MATE desktop.
> I want the current user and all future users to include all directories in
> root's $PATH.
>
> I haven't found a definitive answer in my web search. The answer's seem to
> depend on
I'm running Debian Stretch with MATE desktop.
I want the current user and all future users to include all directories
in root's $PATH.
I haven't found a definitive answer in my web search. The answer's seem
to depend on which Linux is used and multiple parameters.
TIA
29 matches
Mail list logo
