On Wed, Jan 26, 2022 at 10:59:28PM -0600, David Wright wrote:
> On Mon 12 Apr 2021 at 11:26:49 (-0400), Greg Wooledge wrote:
> > On Mon, Apr 12, 2021 at 10:18:19AM -0500, David Wright wrote:
> > > I'm not using PS1 to test whether stdout is a terminal, but whether
> > > the file is running interact
On Mon 12 Apr 2021 at 11:26:49 (-0400), Greg Wooledge wrote:
> On Mon, Apr 12, 2021 at 10:18:19AM -0500, David Wright wrote:
> > I'm not using PS1 to test whether stdout is a terminal, but whether
> > the file is running interactively. From man bash:
> >
> > "PS1 is set and $- includes i if bash
On Sat, 2022-01-22 at 23:53 +0100, Andrei POPESCU wrote:
> On Sb, 22 ian 22, 10:00:34, to...@tuxteam.de wrote:
> >
> > *Poof*, your Ethernet device name changes, since, by default [1] it's
> > named after the path in the USB device tree leading to your device.
> > Don't forget to stick your Ethern
On Sb, 22 ian 22, 10:00:34, to...@tuxteam.de wrote:
>
> *Poof*, your Ethernet device name changes, since, by default [1] it's
> named after the path in the USB device tree leading to your device.
> Don't forget to stick your Ethernet dongle into the same port
> afterwards. Else... *poof*.
I thoug
On Sb, 22 ian 22, 09:52:45, David Wright wrote:
> On Sat 22 Jan 2022 at 11:32:17 (+), piorunz wrote:
> > On 22/01/2022 07:28, Andrei POPESCU wrote:
> > > On Lu, 17 ian 22, 22:43:49, piorunz wrote:
> > > >
> > > > Problem is, every now and then, Ethernet adapter name changes, from
> > > > enp5s
On Sat, Jan 22, 2022 at 10:00:34AM +0100, to...@tuxteam.de wrote:
> On Sat, Jan 22, 2022 at 08:28:34AM +0100, Andrei POPESCU wrote:
> > On Lu, 17 ian 22, 22:43:49, piorunz wrote:
> > >
> > > Problem is, every now and then, Ethernet adapter name changes, from
> > > enp5s0 to enp6s0 for example.
>
On Sat, Jan 22, 2022 at 09:53:00AM -0600, David Wright wrote:
[...]
> That doesn't tally with my experience. Two paragraphs before Table 2 is:
>
>ID_NET_NAME_MAC=prefixxAABBCCDDEEFF
[...]
> which describes what I observe here.
MAC is definitely a better choice in this (USB) context. A
On Sat 22 Jan 2022 at 10:00:34 (+0100), to...@tuxteam.de wrote:
> On Sat, Jan 22, 2022 at 08:28:34AM +0100, Andrei POPESCU wrote:
> > On Lu, 17 ian 22, 22:43:49, piorunz wrote:
> > >
> > > Problem is, every now and then, Ethernet adapter name changes, from
> > > enp5s0 to enp6s0 for example.
> >
On Sat 22 Jan 2022 at 11:32:17 (+), piorunz wrote:
> On 22/01/2022 07:28, Andrei POPESCU wrote:
> > On Lu, 17 ian 22, 22:43:49, piorunz wrote:
> > >
> > > Problem is, every now and then, Ethernet adapter name changes, from
> > > enp5s0 to enp6s0 for example.
> >
> > Those names are supposed t
On 22/01/2022 09:00, to...@tuxteam.de wrote:
Hahaha:)
Actually, they're supposed to be/predictable/.
Now assume the following situation: you've got just one USB port (Apple,
I'm looking at you). Your Ethernet adapter is a dongle hanging off it.
You now realize you need some USB storage to do yo
On 22/01/2022 07:28, Andrei POPESCU wrote:
On Lu, 17 ian 22, 22:43:49, piorunz wrote:
Problem is, every now and then, Ethernet adapter name changes, from
enp5s0 to enp6s0 for example.
Those names are supposed to be stable.
Are you doing any changes to the hardware when that happens?
Kind r
On Sat, Jan 22, 2022 at 08:28:34AM +0100, Andrei POPESCU wrote:
> On Lu, 17 ian 22, 22:43:49, piorunz wrote:
> >
> > Problem is, every now and then, Ethernet adapter name changes, from
> > enp5s0 to enp6s0 for example.
>
> Those names are supposed to be stable.
Hahaha :)
Actually, they're supp
On Lu, 17 ian 22, 22:43:49, piorunz wrote:
>
> Problem is, every now and then, Ethernet adapter name changes, from
> enp5s0 to enp6s0 for example.
Those names are supposed to be stable.
Are you doing any changes to the hardware when that happens?
Kind regards,
Andrei
--
http://wiki.debian.or
On 17/01/2022 22:50, Darac Marjal wrote:
If you have multiple Network Adapters, connected to different networks,
why not give them more sensible names?
Using
https://wiki.debian.org/NetworkInterfaceNames#CUSTOM_SCHEMES_USING_.LINK_FILES
you can assign names such as "lan", "wan", "internal", "wi
On 17/01/2022 22:43, piorunz wrote:
Hello,
I run Firefox via firejail. I let Firefox use only one network adapter,
because that cuts off Firefox from my LAN. I run several profiles of
Firefox on my machine. Only one of them has access to LAN for security
reasons.
This is my example shortcut in
Hello,
I run Firefox via firejail. I let Firefox use only one network adapter,
because that cuts off Firefox from my LAN. I run several profiles of
Firefox on my machine. Only one of them has access to LAN for security
reasons.
This is my example shortcut in KDE menu:
firejail --net=enp5s0 --net
On Saturday 23 October 2021 22:00:42 piorunz wrote:
> On 17/10/2021 17:18, Gene Heskett wrote:
> > The local electrical system, while better than Haiti's is getting to
> > be a nuisance with 5 second power failures about weekly, or is that
> > weakly? (...)
> > I made some mods to a 3d printer pro
On 17/10/2021 17:18, Gene Heskett wrote:
The local electrical system, while better than Haiti's is getting to be a
nuisance with 5 second power failures about weekly, or is that weakly?
(...)
I made some mods to a 3d printer project in openscad last week, printed
it, but forgot to save it. So I l
On 2021-10-17 19:09, Greg Wooledge wrote:
On Sun, Oct 17, 2021 at 06:35:01PM +0200, deloptes wrote:
> 2. and another pesky thing is starting a konsole to do work, needs a
> $PATH modification that we used to put in ~.profile. But opening a
> terminal hasn't called a ". .p
could do all this as me because the
> > > > mount point for the card is in my home directory, I own it all. And
> > > > didn't have to be root to do any of it. This was not fixed by a 2nd
> > > > reboot.
> > >
> > > I guess this problem is not
onday 18 October 2021 01:12:42 Will Mengarini wrote:
> > > > > * Gene Heskett [21-10/17=Su 12:18 -0400]:
> > > > > > [...] opening a terminal hasn't called
> > > > > > a ". .profile" since about jessie [...]
> > > > >
Gene Heskett [21-10/17=Su 12:18 -0400]:
> > > > > [...] opening a terminal hasn't called
> > > > > a ". .profile" since about jessie [...]
> > > >
> > > > Check whether you *also* have either .bash_profile or
> >
rminal hasn't called
> > > > a ". .profile" since about jessie [...]
> > >
> > > Check whether you *also* have either .bash_profile or
> > > .bash_login, because either of those supersedes .profile:
> > >
> > > ls -lA ~/.bash_{prof
On Mon, Oct 18, 2021 at 01:42:43AM -0400, Gene Heskett wrote:
> On Monday 18 October 2021 01:12:42 Will Mengarini wrote:
>
> > * Gene Heskett [21-10/17=Su 12:18 -0400]:
> > > [...] opening a terminal hasn't called
> > > a ". .profile" since about
On Monday 18 October 2021 01:12:42 Will Mengarini wrote:
> * Gene Heskett [21-10/17=Su 12:18 -0400]:
> > [...] opening a terminal hasn't called
> > a ". .profile" since about jessie [...]
>
> Check whether you *also* have either .bash_profile or
> .bash_lo
* Gene Heskett [21-10/17=Su 12:18 -0400]:
> [...] opening a terminal hasn't called
> a ". .profile" since about jessie [...]
Check whether you *also* have either .bash_profile or
.bash_login, because either of those supersedes .profile:
ls -lA ~/.bash_{profile,login}
On Sunday 17 October 2021 21:15:21 Douglas McGarrett wrote:
> On 10/17/21 8:38 PM, David Christensen wrote:
> > On 10/17/21 2:12 PM, Stefan Monnier wrote:
> >>> normally when a storm comes through i turn off the PC anyways
> >>> because I really don't want to have things fried (even if i do
> >>>
Stefan Monnier wrote:
>> normally when a storm comes through i turn off the PC anyways because
>> I really don't want to have things fried (even if i do have the UPS
>> and surge protection).
>
> Hmmm does turning them off make any difference w.r.t a surge large
> enough to pass through the surge s
On 10/17/21 8:38 PM, David Christensen wrote:
On 10/17/21 2:12 PM, Stefan Monnier wrote:
normally when a storm comes through i turn off the PC anyways because
I really don't want to have things fried (even if i do have the UPS
and surge protection).
Hmmm does turning them off make any diffe
> normally when a storm comes through i turn off the PC anyways because
> I really don't want to have things fried (even if i do have the UPS
> and surge protection).
Hmmm does turning them off make any difference w.r.t a surge large
enough to pass through the surge suppression?
I thought the onl
On 10/17/21 2:12 PM, Stefan Monnier wrote:
normally when a storm comes through i turn off the PC anyways because
I really don't want to have things fried (even if i do have the UPS
and surge protection).
Hmmm does turning them off make any difference w.r.t a surge large
enough to pass through t
On Sunday 17 October 2021 15:45:36 songbird wrote:
> Gene Heskett wrote:
> > On Sunday 17 October 2021 12:39:50 Dan Ritter wrote:
> >> Gene Heskett wrote:
> >> > The local electrical system, while better than Haiti's is getting
> >> > to be a nuisance with 5 second power failures about weekly, or
Gene Heskett wrote:
> On Sunday 17 October 2021 12:39:50 Dan Ritter wrote:
>
>> Gene Heskett wrote:
>> > The local electrical system, while better than Haiti's is getting to
>> > be a nuisance with 5 second power failures about weekly, or is that
>> > weakly?
>>
>> That's a great case for a UPS...
On Sunday 17 October 2021 14:09:23 Greg Wooledge wrote:
> On Sun, Oct 17, 2021 at 06:35:01PM +0200, deloptes wrote:
> > > 2. and another pesky thing is starting a konsole to do work, needs
> > > a $PATH modification that we used to put in ~.profile. But opening
> > &
fixed by a 2nd
> > reboot.
>
> Are you mounting via /etc/fstab? If so, show us the line.
nope, command line, as me, until this reboot.
> > 2. and another pesky thing is starting a konsole to do work, needs a
> > $PATH modification that we used to put in ~.profile
On Sun, Oct 17, 2021 at 06:35:01PM +0200, deloptes wrote:
> > 2. and another pesky thing is starting a konsole to do work, needs a
> > $PATH modification that we used to put in ~.profile. But opening a
> > terminal hasn't called a ". .profile" since about j
e directory, I own it all. And
> > > didn't have to be root to do any of it. This was not fixed by a 2nd
> > > reboot.
> >
> > I guess this problem is not related to the .profile issue you are
> > having below.
>
> Agreed.
>
> > Check the permissi
his was not fixed by a 2nd
> > reboot.
>
> I guess this problem is not related to the .profile issue you are
> having below.
Agreed.
> Check the permissions on the mount point
done, I still own it.
> and the fstab
its not in fstab, never was. I touched a file in
home/gene/Download
> $PATH modification that we used to put in ~.profile. But opening a
> terminal hasn't called a ". .profile" since about jessie. So thats
> another PITA.
>
> So, what has replaced .profile as the function for such as that in recent
> releases?
I'm guessing
Gene Heskett wrote:
> 1. Before the latest failure I could do all this as me because the mount
> point for the card is in my home directory, I own it all. And didn't
> have to be root to do any of it. This was not fixed by a 2nd reboot.
>
I guess this problem is not relate
thing is starting a konsole to do work, needs a
$PATH modification that we used to put in ~.profile. But opening a
terminal hasn't called a ". .profile" since about jessie. So thats
another PITA.
So, what has replaced .profile as the function for such as that in recent
releases
I found a solution:
Open terminal and type dconf-editor (if you don't have it installed it will
automatically ask you if you want to install it)
when it opens you should go /org/gnome/control-center , open last-panel scroll
down and the custom value should be 'power' now you need to change it ,
I found a solution:
Open terminal and type dconf-editor (if you don't have it installed it will
automatically ask you if you want to install it)
when it opens you should go /org/gnome/control-center , open last-panel scroll
down and the custom value should be 'power' now you need to change it ,
back or fix this error? Thanks
(gnome-control-center:19500): GLib-GIO-ERROR **: 01:23:11.959: Settings schema
'org.gnome.settings-daemon.plugins.power' does not contain a key named
'power-saver-profile-on-low-battery'Trace/breakpoint trap
al/learn/nix/p1/default.nix:1:17
--8<---cut here---end--->8---
I have added myself to ‘nix-users’ group as specified in the
‘/usr/share/doc/nix-bin/README.Debian’.
Do I need to manually create profile directory? What is the proper
debian-way of creating per-user profile?
Le lundi 2 août 2021 à 06:00:05 UTC+2, Ratan Gupta a écrit :
[...]
> In my case it is not at all complaining as it is because the process is
> unconfined.
[...]
If I am not mistaken, the purpose of the complain mode is precisely to inform
about policy violations without forbidding them (forbiddi
Hi Didier,
I was not able to reply on your mail as I am not part of the above mailing
list, I have subscribed myself now.
Regarding your suggestion.
> From what I understand, unless you specify a deny rule, when you switch
an AppArmor profile to complain mode, it complains but does not conf
Hello,
Disclaimer: I never wrote an AppArmor profile
>From what I understand, unless you specify a deny rule, when you switch an
>AppArmor profile to complain mode, it complains but does not confine, so you
>would probably switch your AppArmor profile to enforce mode instead.
And
Hi Team,
Looking for your help.
I have gone through the following link where the similar issue was asked.
https://lists.debian.org/debian-user/2018/07/msg00542.html
Issue: I made a profile for the application, and it is not getting confined
by the apparmor.
What I did:
1) I wrote
On Mon 12 Apr 2021 at 11:26:49 (-0400), Greg Wooledge wrote:
> On Mon, Apr 12, 2021 at 10:18:19AM -0500, David Wright wrote:
> > I'm not using PS1 to test whether stdout is a terminal, but whether
> > the file is running interactively. From man bash:
> >
> > "PS1 is set and $- includes i if bash
On Mon, Apr 12, 2021 at 10:18:19AM -0500, David Wright wrote:
> I'm not using PS1 to test whether stdout is a terminal, but whether
> the file is running interactively. From man bash:
>
> "PS1 is set and $- includes i if bash is interactive, allowing a
> shell script or a startup file to test
On Sun 11 Apr 2021 at 10:45:22 (-0400), Greg Wooledge wrote:
> On Sun, Apr 11, 2021 at 09:10:24AM -0500, David Wright wrote:
> > For stdout, the problem is more serious. Every time you press TAB
> > expecting remote filename completion, you receive the profile output
> > from
> than setting it in .bashrc every time. I may be in the minority there.
> >
> > Exported from .[bash_]profile? I don't do that because the terminal
> > type might be different (login on VC, but prompt in an xterm).
>
> >From .profile, typically. Althoug
On Sun, Apr 11, 2021 at 05:00:23PM +, Lee wrote:
>
> really?!! What do you have in PS1?
>
PS1='\h:\w\$ '
> IMO, the if test needs an else and the directory name shouldn't be
> typed out multiple times -- it belongs in an e-var:
>
> dir="$HOME/AppImages"
> if [ -d "$dir" ] ; then
> PATH=
hrc every time. I may be in the minority there.
>>
>> Exported from .[bash_]profile? I don't do that because the terminal
>> type might be different (login on VC, but prompt in an xterm).
>
> >From .profile, typically. Although I'm actually not doing it right n
On Sun, Apr 11, 2021 at 09:10:24AM -0500, David Wright wrote:
> For stdout, the problem is more serious. Every time you press TAB
> expecting remote filename completion, you receive the profile output
> from the other end, double-escaped (so a forest of backslashes).
...? What the *hell
> Exported from .[bash_]profile? I don't do that because the terminal
> type might be different (login on VC, but prompt in an xterm).
>From .profile, typically. Although I'm actually not doing it right now.
The terminal type is irrelevant. I don't put terminal escape
iles, not scripts in general. Using PS1 as a condition
> > in the latter is unlikely to make much sense at all.
>
> I'm not a fan of it, because I actually like to export PS1, rather
> than setting it in .bashrc every time. I may be in the minority there.
Exported from .[bash_]p
> >> [ -n "$PS1" ] && printf …
> >> >
> >> > Maybe consider:
> >> >
> >> > [[ -t 1 ]] && printf ...
> >>
> >> Until your script that was started via crontab silently fails. I
> >> *lik
On Sat, Apr 10, 2021 at 01:21:21PM -0500, David Wright wrote:
> My start-up files, .bash_profile, .bashrc, and other files that
> they source, contain permanent printf commands. When they finish
> printing their output, the next thing that's going to happen is
> that the shell will emit a prompt. S
gt; Maybe consider:
>> >
>> >[[ -t 1 ]] && printf ...
>>
>> Until your script that was started via crontab silently fails. I
>> *like* always having error messages enabled.
>
> Here's the context, from Greg, again:
>
>> Writing e
mp;& printf ...
>
> Until your script that was started via crontab silently fails. I
> *like* always having error messages enabled.
Here's the context, from Greg, again:
> Writing error messages to stdout from a .profile isn't generally the
> best idea. Writing to stder
> >> Where I want output, I protect it with:
> >>
> >> [ -n "$PS1" ] && printf …
> >
> > Maybe consider:
> >
> > [[ -t 1 ]] && printf ...
>
> Until your script that was started via crontab silently fails. I
> *like* always having error messages enabled.
I like logs too but -t was in the
On Thu, Apr 08, 2021 at 07:50:23AM +, Curt wrote:
> What about addressing his primary point rather than what in my
> benefit-of-the-doubt humor I construe as a typographical oversight?
I don't remember what the "primary point" was. Was it the same as
the Subject: header
On Thu, Apr 08, 2021 at 11:14:48AM +0100, Tixy wrote:
> I believe ">/dev/stderr" is not Posix standard and knowing the correct
> standard way of doing this could be beneficial.
That's correct -- it's not portable.
On systems where /dev/stderr actually exists (such as Debian GNU/Linux),
according
On Thu, 2021-04-08 at 07:50 +, Curt wrote:
> On 2021-04-07, Greg Wooledge wrote:
> > On Wed, Apr 07, 2021 at 09:41:51PM +, Lee wrote:
> > > Interesting.. "echo foo" in .bashrc does break scp, but not "echo foo >2"
> >
> > That redirects to a file named "2".
> >
> > > .. but that doesn't
On 2021-04-07, Greg Wooledge wrote:
> On Wed, Apr 07, 2021 at 09:41:51PM +, Lee wrote:
>> Interesting.. "echo foo" in .bashrc does break scp, but not "echo foo >2"
>
> That redirects to a file named "2".
>
>> .. but that doesn't work for bash, so hhrmm.. > /dev/stderr seems to
>> work in all
On Wed, Apr 07, 2021 at 09:41:51PM +, Lee wrote:
> Interesting.. "echo foo" in .bashrc does break scp, but not "echo foo >2"
That redirects to a file named "2".
> .. but that doesn't work for bash, so hhrmm.. > /dev/stderr seems to
> work in all cases:
You wanted >&2 .
On 4/7/21, Marco Ippolito wrote:
>> Where I want output, I protect it with:
>>
>> [ -n "$PS1" ] && printf …
>
> Maybe consider:
>
> [[ -t 1 ]] && printf ...
Until your script that was started via crontab silently fails. I
*like* always having error messages enabled.
Lee
will probably show you what's wrong -- eg
>>
>> dir="$HOME/AppImages"
>> if [ -d "$dir" ] ; then
>> PATH="$dir:$PATH"
>> else
>> echo "OnNoes!! The directory \"$dir\" does not exist!"
>> fi
>
>
> Where I want output, I protect it with:
>
> [ -n "$PS1" ] && printf …
Maybe consider:
[[ -t 1 ]] && printf ...
ppImages"
> > if [ -d "$dir" ] ; then
> > PATH="$dir:$PATH"
> > else
> > echo "OnNoes!! The directory \"$dir\" does not exist!"
> > fi
>
> Writing error messages to stdout from a .profile isn't generally the
On Wednesday 07 April 2021 08:28:49 IL Ka wrote:
> > The first of them will be added but not the other if I
> > . .profile
>
> Try to debug it. First of all, run this from the command line:
>
> [ -d "$HOME/AppImages" ] ; echo $?
>
> result should be &quo
On Wed, Apr 07, 2021 at 03:16:41PM +, Lee wrote:
> On 4/7/21, Gene Heskett wrote:
> > Greetings all;
> >
> > I just installed buster on a Dell 7010 and I have added two stanza's to
> > my .profile, to find a logout and back in does not establish a new
> &g
On Wednesday 07 April 2021 08:28:49 IL Ka wrote:
> > The first of them will be added but not the other if I
> > . .profile
>
> Try to debug it. First of all, run this from the command line:
>
> [ -d "$HOME/AppImages" ] ; echo $?
>
> result should be &quo
On 4/7/21, Gene Heskett wrote:
> Greetings all;
>
> I just installed buster on a Dell 7010 and I have added two stanza's to
> my .profile, to find a logout and back in does not establish a new
> $PATH.
Probably because you've got a window manager that does the login stu
On Wed 07 Apr 2021 at 08:16:43 (-0400), Gene Heskett wrote:
>
> I just installed buster on a Dell 7010 and I have added two stanza's to
> my .profile, to find a logout and back in does not establish a new
> $PATH.
>
> The first of them will be added but not the other if
On Wed, Apr 07, 2021 at 08:16:43AM -0400, Gene Heskett wrote:
> I just installed buster on a Dell 7010 and I have added two stanza's to
> my .profile, to find a logout and back in does not establish a new
> $PATH.
> Any idea why its not working?
How do you log in? Probabl
>
>
> The first of them will be added but not the other if I
> . .profile
>
Try to debug it. First of all, run this from the command line:
[ -d "$HOME/AppImages" ] ; echo $?
result should be "0". If not, then there must be some problem with this
directory
Greetings all;
I just installed buster on a Dell 7010 and I have added two stanza's to
my .profile, to find a logout and back in does not establish a new
$PATH.
The first of them will be added but not the other if I
. .profile
The additions to .profile are:
=
# set PATH so it inc
ive-build/(<=/1:20170213)'
> > +++ sed 's#^/*##; s#[[/(<].*##'
> > ++ CURRENTREALPKGNAME=live-build
> > ++ echo 'live-build/(<=/1:20170213)'
> > ++ grep -q '\['
> > ++ echo 'live-build/(<=/1:20170213)'
> > ++
gt; +++ get_pkg_name 'live-build/(<=/1:20170213)'
> +++ echo 'live-build/(<=/1:20170213)'
> +++ sed 's#^/*##; s#[[/(<].*##'
> ++ CURRENTREALPKGNAME=live-build
> ++ echo 'live-build/(<=/1:20170213)'
> ++ grep -q '\['
> ++
Hello, Mattia, folks,
I'm running pbuilder-0.230.4~bpo9+1/pbuilder-satisfydepends-classic
for the debian/control which contains
Build-Depends: live-build (<= 1:20170213), ...
I get the following log
+++ output='live-build (<= 1:20170213), sed, gawk, rsync, wget, patch,
coreutils, findutils, '
+
Le 21/03/2020 à 08:56, Reco a écrit :
On Sat, Mar 21, 2020 at 10:52:53AM +0300, Reco wrote:
What I figure out is the problem is that somehow, apparmor denies to
network-manager the ability to provide a valid resolv.conf file.
So ipsec can't add a DNS server to my VPN connection.
For that parti
On Sat, Mar 21, 2020 at 10:52:53AM +0300, Reco wrote:
> > What I figure out is the problem is that somehow, apparmor denies to
> > network-manager the ability to provide a valid resolv.conf file.
> > So ipsec can't add a DNS server to my VPN connection.
>
> For that particular file it's:
Forgot
Hi.
On Sat, Mar 21, 2020 at 01:44:21AM +0100, rudu wrote:
> I searched the web with as many keywords as I could think of, to no avail ...
> for me.
You should've searched for aa-logprof.
> What I figure out is the problem is that somehow, apparmor denies to
> network-manager the abili
Greetings,
I'm trying to setup a vpn connection to my local desktop.
I've successfully achieved it with my local laptop using this tutorial :
https://protonvpn.com/support/linux-ikev2-protonvpn/
I figured that I would as well achieve it on my desktop.
But I fail to have a working connection thou
ank you.
In my understanding there is no inherent harm in always starting a login
shell, you are only loosing the option to separate stuff that you want
to run always (.bashrc) or just at login (.profile[1])
Performance is also typically not a concern unless you run some heavy
and/or netwo
On Fri, Aug 23, 2019 at 12:01:09AM +0300, Andrei POPESCU wrote:
> On Ma, 20 aug 19, 16:39:50, Greg Wooledge wrote:
> >
> > And now people will think that running login shells in every terminal
> > session is the RIGHT way.
>
> Please do feel free to educate me on when/why it's wrong to run login
On Ma, 20 aug 19, 16:39:50, Greg Wooledge wrote:
>
> And now people will think that running login shells in every terminal
> session is the RIGHT way.
Please do feel free to educate me on when/why it's wrong to run login
shells instead of a plain interactive shell (or just point me to the
relev
On Thu, Aug 22, 2019 at 07:07:08PM +, Vipul wrote:
> To know who actually reads ~/.profile I've set an environment variable
> "SHELL_PRO" by adding `export SHELL_PRO=$(echo $0)` line in ~/.profile
> file then re-login and typed following command in gnome-terminal
tx1 -An
> wooledg:~$
>
> Your test is also reasonable, as long as you understand that <<< adds
> a newline (0a) which has to be accounted for.
>
>> which is kind of expected behavior because is presence of
>> ~/.bash_profile file login shell (bash) will not read ~/.
On Wed, Aug 21, 2019 at 10:43:18AM -0400, Greg Wooledge wrote:
> wooledg:~$ ls -l /etc/environment.d
> total 8
> -rw-r--r-- 1 root root 20 Aug 21 10:18 11-foo.conf
> -rw-r--r-- 1 root root 19 Feb 9 2019 90qt-a11y.conf
> wooledg:~$ cat /etc/environment.d/90qt-a11y.conf
> QT_ACCESSIBILITY=1
> woole
0 years, someone will kill systemd and replace
it with something that doesn't suck, and then the next time a Desktop
Environment user asks for help configuring their environment, we'll be
able to say "Oh, you just edit ~/.config/qqz-profile and put commands
in there, and they'll run
lt;< adds
a newline (0a) which has to be accounted for.
> which is kind of expected behavior because is presence of
> ~/.bash_profile file login shell (bash) will not read ~/.profile but,
> not clear who reads ~/.profile when login from GNOME interface.
An excellent question, which onl
Andrei POPESCU wrote:
> On Ma, 20 aug 19, 10:36:19, Greg Wooledge wrote:
>> On Tue, Aug 20, 2019 at 02:27:40PM +, Vipul wrote:
>>> Hi there,
>>>
>>> From few days, I'm trying find answer of a question "which program does
>>> read ~/.p
Greg Wooledge wrote:
> On Tue, Aug 20, 2019 at 02:27:40PM +, Vipul wrote:
>> Hi there,
>>
>> From few days, I'm trying find answer of a question "which program does
>> read ~/.profile if I login from graphical user interface (for ex: GNOME)?".
>
On Tue, Aug 20, 2019 at 11:24:55PM +0300, Andrei POPESCU wrote:
> On Ma, 20 aug 19, 10:36:19, Greg Wooledge wrote:
> > On Tue, Aug 20, 2019 at 02:27:40PM +, Vipul wrote:
> > > Hi there,
> > >
> > > From few days, I'm trying find answer of a question
On Ma, 20 aug 19, 10:36:19, Greg Wooledge wrote:
> On Tue, Aug 20, 2019 at 02:27:40PM +, Vipul wrote:
> > Hi there,
> >
> > From few days, I'm trying find answer of a question "which program does
> > read ~/.profile if I login from graphical user in
On Tue, Aug 20, 2019 at 10:36:19AM -0400, Greg Wooledge wrote:
> And there is no known way to configure the environment of dbus in a way
> that is useful to end users.
dbus-update-activation-environment(1) says otherwise.
Reco
1 - 100 of 530 matches
Mail list logo