Re: bash history

2024-07-27 Thread mick.crane
On 2024-07-27 23:58, Greg Wooledge wrote: You need to specify *exactly* what you're doing. "exactly" is at mickiwiki.com I can take the ridicule of my coding understanding. Whenever I need to reboot my computer (kernel update or the like), I decide which shells I want to retain history from,

Re: bash history

2024-07-27 Thread Jeffrey Walton
On Sun, Jul 28, 2024 at 12:25 AM Mike Castle wrote: > > On Sat, Jul 27, 2024 at 2:50 PM mick.crane wrote: > > Is this something that can be changed so history is shared between > > virtual terminals? > > [...] > For me, I see up bash with the following features: > * Unbounded history > * History

Re: bash history

2024-07-27 Thread mick.crane
On 2024-07-28 02:12, Greg Wooledge wrote: On Sun, Jul 28, 2024 at 02:01:04 +0100, mick.crane wrote: On 2024-07-27 23:58, Greg Wooledge wrote: > You need to specify *exactly* what you're doing. Sometimes I forget where I was after closing a virtual terminal and it would be handy to see the h

Re: systemd may silently break your system!

2024-07-27 Thread David Wright
On Sun 28 Jul 2024 at 04:25:32 (+0200), Vincent Lefevre wrote: > On 2024-07-27 20:25:54 -0400, Greg Wooledge wrote: > > On Sun, Jul 28, 2024 at 01:17:19 +0200, Vincent Lefevre wrote: > > > The configuration got broken by a *systemd* upgrade: > > > > > > * Drop /etc/sysctl.d/99-sysctl.conf symli

Re: info is not dead

2024-07-27 Thread David Wright
On Sun 28 Jul 2024 at 02:06:38 (+0200), Vincent Lefevre wrote: > On 2024-07-23 11:13:47 -0500, Nate Bargmann wrote: > > The GNU info documentation is really intended to be read in Emacs where > > some nice formatting is done in the GUI Emacs version. The stand alone > > GNU info browser is rather

Re: systemd may silently break your system!

2024-07-27 Thread Geoff
Vincent Lefevre wrote: The /etc/sysctl.d/99-sysctl.conf symlink has been removed (currently in unstable) *without any announcement*, so that the /etc/sysctl.conf file (which is still documented, BTW) is no longer read. So, be careful if you have important settings there (security...). Thanks

Re: bash history

2024-07-27 Thread Mike Castle
On Sat, Jul 27, 2024 at 2:50 PM mick.crane wrote: > Is this something that can be changed so history is shared between > virtual terminals? Yes. There are all sorts of settings that can control how shells save history. Most shells are capable of doing whatever you want, but the default configur

Re: systemd may silently break your system!

2024-07-27 Thread Vincent Lefevre
On 2024-07-27 20:25:54 -0400, Greg Wooledge wrote: > On Sun, Jul 28, 2024 at 01:04:14 +0200, Vincent Lefevre wrote: > > On 2024-07-27 10:23:01 +0200, Michel Verdier wrote: > > > /etc/sysctl.d/README.sysctl recommends to use a separate file such as > > > /etc/sysctl.d/local.conf > > > > No, it does

Re: bash history

2024-07-27 Thread Max Nikulin
On 28/07/2024 08:01, mick.crane wrote: Sometimes I forget where I was after closing a virtual terminal  and it would be handy to see the history in a new terminal, where I "cd'd" to for example. help history less ~/.bash_history

Re: info is not dead

2024-07-27 Thread Max Nikulin
On 27/07/2024 20:00, Nate Bargmann wrote: Texinfo is from a time when GNU documentation was only man pages or flat text files and something "better" was desired for moving through a manual in what is now known as a hypertext format. It also includes a lot of semantic markup rather than the basi

Re: switch users and still use display

2024-07-27 Thread Max Nikulin
On 27/07/2024 23:06, Greg Wooledge wrote: Yes, but the other ways are *far* more complicated, especially when neither user1 nor user2 is root. The issue is that in order to authenticate yourself to the X server, you present a token, known as a "magic cookie". in some cases xhost +si:local

Re: bash history

2024-07-27 Thread Greg Wooledge
On Sun, Jul 28, 2024 at 02:01:04 +0100, mick.crane wrote: > On 2024-07-27 23:58, Greg Wooledge wrote: > > You need to specify *exactly* what you're doing. > Sometimes I forget where I was after closing a virtual terminal and it > would be handy to see the history > in a new terminal, where I "cd'

Re: bash history

2024-07-27 Thread mick.crane
On 2024-07-27 23:58, Greg Wooledge wrote: You need to specify *exactly* what you're doing. My project management skills are non-existent. If I have a script that is working I'll copy to eg. script2 and make changes to that. Sometimes, depending, I'll have similar things in other directories t

Re: systemd may silently break your system!

2024-07-27 Thread Greg Wooledge
On Sun, Jul 28, 2024 at 01:04:14 +0200, Vincent Lefevre wrote: > On 2024-07-27 10:23:01 +0200, Michel Verdier wrote: > > /etc/sysctl.d/README.sysctl recommends to use a separate file such as > > /etc/sysctl.d/local.conf > > No, it does *not* recommend anything: > > ---

Re: bash history

2024-07-27 Thread Vincent Lefevre
On 2024-07-27 22:50:17 +0100, mick.crane wrote: > In debian bookworm, xfce desktop, different virtual terminals have a > different history if same user presses "up key" in different virtual > terminals ? > Is this something that can be changed so history is shared between virtual > terminals? This

Re: info is not dead

2024-07-27 Thread Vincent Lefevre
On 2024-07-23 11:13:47 -0500, Nate Bargmann wrote: > The GNU info documentation is really intended to be read in Emacs where > some nice formatting is done in the GUI Emacs version. The stand alone > GNU info browser is rather obtuse. I found a much better option to be > the independent pinfo (De

Re: systemd may silently break your system!

2024-07-27 Thread Vincent Lefevre
On 2024-07-27 09:26:49 -0400, Greg Wooledge wrote: > > On 2024-07-26, Vincent Lefevre wrote: > > > > > The /etc/sysctl.d/99-sysctl.conf symlink has been removed > > > (currently in unstable) *without any announcement*, so that > > > the /etc/sysctl.conf file (which is still documented, BTW) > > >

Re: SeLinux

2024-07-27 Thread jeremy ardley
On 28/7/24 06:45, Greg Wooledge wrote: On Sat, Jul 27, 2024 at 22:40:10 +, Andy Smith wrote: Hi, On Sun, Jul 28, 2024 at 06:30:50AM +0800, cor...@free.fr wrote: Is selinux necessary in a production environment? "Will my door still function as a door if it has no lock on it?" More li

Re: systemd may silently break your system!

2024-07-27 Thread Vincent Lefevre
On 2024-07-27 10:23:01 +0200, Michel Verdier wrote: > On 2024-07-26, Vincent Lefevre wrote: > > > The /etc/sysctl.d/99-sysctl.conf symlink has been removed > > (currently in unstable) *without any announcement*, so that > > the /etc/sysctl.conf file (which is still documented, BTW) > > is no longe

Re: bash history

2024-07-27 Thread The Wanderer
On 2024-07-27 at 18:44, mick.crane wrote: > On 2024-07-27 23:08, Greg Wooledge wrote: > >> On Sat, Jul 27, 2024 at 22:50:17 +0100, mick.crane wrote: >> >>> In debian bookworm, xfce desktop, different virtual terminals >>> have a different history if same user presses "up key" in >>> different vi

Re: bash history

2024-07-27 Thread Greg Wooledge
On Sat, Jul 27, 2024 at 23:44:08 +0100, mick.crane wrote: > On 2024-07-27 23:08, Greg Wooledge wrote: > > On Sat, Jul 27, 2024 at 22:50:17 +0100, mick.crane wrote: > > > In debian bookworm, xfce desktop, different virtual terminals have a > > > different history if same user presses "up key" in dif

Re: SeLinux

2024-07-27 Thread Greg Wooledge
On Sat, Jul 27, 2024 at 22:40:10 +, Andy Smith wrote: > Hi, > > On Sun, Jul 28, 2024 at 06:30:50AM +0800, cor...@free.fr wrote: > > Is selinux necessary in a production environment? > > "Will my door still function as a door if it has no lock on it?" More like "Will my door still function as

Re: bash history

2024-07-27 Thread mick.crane
On 2024-07-27 23:08, Greg Wooledge wrote: On Sat, Jul 27, 2024 at 22:50:17 +0100, mick.crane wrote: In debian bookworm, xfce desktop, different virtual terminals have a different history if same user presses "up key" in different virtual terminals ? As your subject says, this is "bash history"

Re: SeLinux

2024-07-27 Thread jeremy ardley
On 28/7/24 06:30, cor...@free.fr wrote: Hello I have checked this doc, https://wiki.debian.org/SELinux/Setup Is selinux necessary in a production environment? Will it affect running services such as web, database, mail, etc., causing potential problems? Thanks. I have set it up multip

Re: SeLinux

2024-07-27 Thread Andy Smith
Hi, On Sun, Jul 28, 2024 at 06:30:50AM +0800, cor...@free.fr wrote: > Is selinux necessary in a production environment? "Will my door still function as a door if it has no lock on it?" > Will it affect running services such as web, database, mail, etc., > causing potential problems? "Has any co

Re: switch users and still use display

2024-07-27 Thread David Wright
On Sat 27 Jul 2024 at 23:21:06 (+0200), Hans wrote: > I never found an official documentation about "su -p", just found it myself, > but I read, "su -" shall do the same. It does not. When you write something like this, can you accompany it with a reference? The essential package util-linux's man

Re: bash history

2024-07-27 Thread Andy Smith
Hi, On Sat, Jul 27, 2024 at 10:50:17PM +0100, mick.crane wrote: > Is this something that can be changed so history is shared between virtual > terminals? You may be interested in "atuin" to aggregate shell history from multiple logins and machines in a searchable interface. It can be self-hosted.

SeLinux

2024-07-27 Thread coreyh
Hello I have checked this doc, https://wiki.debian.org/SELinux/Setup Is selinux necessary in a production environment? Will it affect running services such as web, database, mail, etc., causing potential problems? Thanks. -- corey hickman

Re: bash history

2024-07-27 Thread Greg Wooledge
On Sat, Jul 27, 2024 at 22:50:17 +0100, mick.crane wrote: > In debian bookworm, xfce desktop, different virtual terminals have a > different history if same user presses "up key" in different virtual > terminals ? As your subject says, this is "bash history". And yes, each instance of bash has it

bash history

2024-07-27 Thread mick.crane
In debian bookworm, xfce desktop, different virtual terminals have a different history if same user presses "up key" in different virtual terminals ? Is this something that can be changed so history is shared between virtual terminals? mick

Re: switch users and still use display

2024-07-27 Thread Hans
Some window managers are offering an option, to change the user (plasma = KDE does it, for example.). It is also possible, to start a new X-session and login with another user. Doing so, you have 2 X-session open. The option is also, to change the user, or, add another user with a new session.

Re: info is not dead

2024-07-27 Thread David
On Sat, 2024-07-27 at 19:04 +, Jaap van Wingerde wrote: > > > Nate Bargmann schreef op 27 juli 2024 13:00:17 UTC: > > > I typically will search for an HTML version of a GNU manual.  The > > only > > problem is that what is found online are the latest versions and > > Debian > > Stable packa

Re: info is not dead

2024-07-27 Thread Jaap van Wingerde
Nate Bargmann schreef op 27 juli 2024 13:00:17 UTC: >I typically will search for an HTML version of a GNU manual. The only >problem is that what is found online are the latest versions and Debian >Stable packages may be a version or two behind. It's a pity that besides 'manpages.debian.org',

Re: switch users and still use display

2024-07-27 Thread eben
On 7/27/24 12:43, fxkl4...@protonmail.com wrote: > does ssh destinguish between "ssh host1" and "ssh localhost" Probably the interface it uses. host1 -> eth0 and localhost -> lo. Unless you've done something funny with hostnames or routing. Anyhow that's my guess, and if not, someone will b

Re: switch users and still use display

2024-07-27 Thread Greg Wooledge
On Sat, Jul 27, 2024 at 16:43:50 +, fxkl4...@protonmail.com wrote: > simple is better > thanks > > does ssh destinguish between "ssh host1" and "ssh localhost" Depends on how everything is configured. It can. If you prefer 'ssh -X user2@host1' and if that works for you, then you can use tha

Re: switch users and still use display

2024-07-27 Thread fxkl47BF
simple is better thanks does ssh destinguish between "ssh host1" and "ssh localhost" On Sat, 27 Jul 2024, Greg Wooledge wrote: > On Sat, Jul 27, 2024 at 15:44:51 +, fxkl4...@protonmail.com wrote: >> i log in to x session as user1 on host1 >> from within a xterm i want to change to user2 on h

Re: switch users and still use display

2024-07-27 Thread Richmond
fxkl4...@protonmail.com writes: > i log in to x session as user1 on host1 > from within a xterm i want to change to user2 on host1 and run x programs > the current way i do this is ssh user2@host1 > does using ssh on the same host use encryption > is there another way to do this > i feel like this

Re: switch users and still use display

2024-07-27 Thread Greg Wooledge
On Sat, Jul 27, 2024 at 15:44:51 +, fxkl4...@protonmail.com wrote: > i log in to x session as user1 on host1 > from within a xterm i want to change to user2 on host1 and run x programs > the current way i do this is ssh user2@host1 I'm assuming you mean "ssh -X", or that you've configured the

switch users and still use display

2024-07-27 Thread fxkl47BF
i log in to x session as user1 on host1 from within a xterm i want to change to user2 on host1 and run x programs the current way i do this is ssh user2@host1 does using ssh on the same host use encryption is there another way to do this i feel like this has been hashed over here previously i just

Re: systemd may silently break your system!

2024-07-27 Thread David Wright
On Sat 27 Jul 2024 at 09:26:49 (-0400), Greg Wooledge wrote: > > On 2024-07-26, Vincent Lefevre wrote: > > > > > The /etc/sysctl.d/99-sysctl.conf symlink has been removed > > > (currently in unstable) *without any announcement*, so that > > > the /etc/sysctl.conf file (which is still documented, B

Re: systemd may silently break your system!

2024-07-27 Thread Greg Wooledge
> On 2024-07-26, Vincent Lefevre wrote: > > > The /etc/sysctl.d/99-sysctl.conf symlink has been removed > > (currently in unstable) *without any announcement*, so that > > the /etc/sysctl.conf file (which is still documented, BTW) > > is no longer read. > > > > So, be careful if you have important

Re: info is not dead

2024-07-27 Thread Nate Bargmann
* On 2024 25 Jul 07:48 -0500, Oliver Schode wrote: > To be honest I'm not happy with the info format still being around, > precisely because sometimes man pages don't cut it, and we should have > something better by now. On the other hand, and I'll make no bones > about it, so called chatbots turne

Re: [SOLVED] potential bug? - was Re: Problem with cryptsetup-initramfs

2024-07-27 Thread Jonathan Dowland
On Fri Jul 26, 2024 at 10:47 AM BST, Nicolas George wrote: > Now maybe you fix your MUA configuration to not omit “Re: ”. What would that achieve? -- Please do not CC me for listmail. 👱🏻 Jonathan Dowland ✎j...@debian.org 🔗 https://jmtd.net

Re: [SOLVED] potential bug? - was Re: Problem with cryptsetup-initramfs

2024-07-27 Thread Jonathan Dowland
I'm glad you've solved your issue. I read your original (very detailed) mail and I had nothing to contribute with respect to a fix; but I was interested to follow it, as I rely upon remote decryption of the root filesystem myself. >From what you write, I think you are correct that some component (

Re: Alternative to Authy

2024-07-27 Thread jeremy ardley
On 27/7/24 09:43, Max Nikulin wrote: On 23/07/2024 09:16, jeremy ardley wrote: I use Google Authenticator as an option in pam to secure ssh connections. [...] NB. Google Authenticator does not use any Google cloud services. It is purely a local application on your machine. Do you mean rfc

Re: Strange behavior of ifupdown package

2024-07-27 Thread Michel Verdier
On 2024-07-26, Ian Molton wrote: > Michael, that was not a personal attack. I am in no doubt that you personally > try to help. And *was helped*. So I am not alone :) > The statistics for this list, however, are public record. And they are indeed > of concern. Can you give the statistics which

Re: systemd may silently break your system!

2024-07-27 Thread Michel Verdier
On 2024-07-26, Vincent Lefevre wrote: > The /etc/sysctl.d/99-sysctl.conf symlink has been removed > (currently in unstable) *without any announcement*, so that > the /etc/sysctl.conf file (which is still documented, BTW) > is no longer read. > > So, be careful if you have important settings there

Re: [SOLVED] potential bug? - was Re: Problem with cryptsetup-initramfs

2024-07-27 Thread Andy Smith
Hi, On Fri, Jul 26, 2024 at 10:35:03AM +0100, Ian Molton wrote: > Should this be reported somewhere else? Any devs reading this? Yes, if you think there is a bug it should be reported in bugs.debian.org. The "reportbug" program may help. This mailing list is mostly for user support by other user

Re: Never receive an unsubscription confirmation e-mail

2024-07-27 Thread Andy Smith
Hi, On Fri, Jul 26, 2024 at 05:39:30PM +0200, rudu wrote: > I wrote an e-mail to debian-user-requ...@lists.debian.org with the > subject "unsubscribe" and sent it, expecting to receive a confirmation > e-mail ... which never comes ... > I also tried https://www.debian.org/MailingLists/unsubscribe,