Hello
On Debian 6.1.129-1, I have a static network interface conf (no Netplan)
with both IPv4 & IPv6 addressing and Name-servers set.
>
root@debian:/home/user# more /etc/network/interfaces
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
allow
Thank you. I don't understand about the linux-image from backports. Would that
be the same kernel that is in Trixie? I already tried that.
If the problem is with the kernel configuration, is there any way to find the
problem working on a single computer?
On Thu, 27 Mar 2025 at 01:43, Timothy M Butterworth
wrote:
> Does anyone know if/when openMW will become available in Trixie? OpenMW is
> available in both Bookworm and Sid. I actually added the Sid repos to Trixie
> and installed openMW. It is running fine for me.
>
> I checked https://package
On 27/03/2025 03:26, George at Clug wrote:
I tried "$ journalctl | grep -i error"
First of all, likely it should be "#", not "$" (run it as root: either
sudo or su). Next
journalctl --priority=err
or
journalctl --priority=warning
instead of grep.
However in the case of obscure is
Hello,
Does anyone know if/when openMW will become available in Trixie? OpenMW is
available in both Bookworm and Sid. I actually added the Sid repos to
Trixie and installed openMW. It is running fine for me.
I checked https://packages.debian.org/search?keywords=openmw and Trixie is
currently miss
On 3/26/25 6:55 AM, Greg Wooledge wrote:
[SNIP]
I normally use "sudo -s", which is the closest sudo approximation to
the traditional behvior of "su" (before it was broken in buster).
I don't understand the reference to some "brokenness" of "su".
I've not closely followed this thread so I may
W. Pepperdine,
Here are outputs of a few queries on log entries from one of my XFCE
installations. How do they compare with your logs? Can you see any reports on
your computer that could point to what is causing your issue?
# lightdm --show-config
[Seat:*]
B greeter-session=lightdm-greeter
Hi,
Is anyone using similar hardware to Pepperdine ? If you are, do you have
issues?
Can anyone give useful suggestions where Pepperdine could start looking for
issues?
I tried "$ journalctl | grep -i error" and the output was not in a useful
format on my computer for searching for issues.
On Wed 26 Mar 2025 at 16:37:41 (-), Greg wrote:
> On 2025-03-26, Richard Owlett wrote:
> >
> > I assumed it was effectively the same as power down and then logging in
> > as root on power-up.
>
> It is. But it's unnecessary and dangerous to run your entire DE as root.
> Or maybe you log in t
Thanks Andrew, also for your translation effort.
Regards
Julio
El dom, 23 mar 2025 a las 18:36, Andrew M.A. Cater ()
escribió:
> On Sun, Mar 23, 2025 at 04:14:15PM +0100, Julio Gil Garcia wrote:
> > Buenas tardes, me llamo Julio:
>
> Como Tomas te has escrito - suele hablar en ingles por aqui <3
Greg Wooledge (HE12025-03-26):
> This caused ALL KINDS of problems. People would do things like:
>
> $ su
> # apt update
> # apt install somepkg
>
> And the postinstall script for somepkg would fail because it couldn't
> find commands that are in /sbin or /usr/sbin, because those dir
So, in most cases* sudo -s* is better? Any downsides?
ср, 26 мар. 2025 г. в 16:10, Greg Wooledge :
> On Wed, Mar 26, 2025 at 07:48:16 -0500, Richard Owlett wrote:
> > On 3/26/25 6:55 AM, Greg Wooledge wrote:
> > > I normally use "sudo -s", which is the closest sudo approximation to
> > > the trad
On Wed, Mar 26, 2025 at 07:55:33AM -0400, Greg Wooledge wrote:
[...]
> I normally use "sudo -s", which is the closest sudo approximation to
> the traditional behvior of "su" (before it was broken in buster).
>
> "sudo -i" is meant to approximate the behavior of "su -". Before buster,
> nobody w
On 2025-03-26, Richard Owlett wrote:
>
> I assumed it was effectively the same as power down and then logging in
> as root on power-up.
It is. But it's unnecessary and dangerous to run your entire DE as root.
Or maybe you log in to the console and use startx to run Mate?
At any rate, I do follo
> I was once sitting at a $(DAYJOB) where they blocked everything but
> 443 (and 80). I tunneled ssh over socat (with TLS, so that the handshake
> didn't look suspect, in case their firewall sniffed that).
Reminds me: I have an OpenVPN running on port 443, specifically to
minimize the chances that
On 3/20/25 17:11, Kleene, Steven (kleenesj) wrote:
The software setup for my Brother DCP-L2640DW driverless laser printer is
confusing the hell out of me. I'm running bookworm.
remove cups-browsed. Then the brother drivers which fully support their
printers will work.
The printer is connected
On 2025-03-26, Greg Wooledge wrote:
>>
>> Does this "brokenness" of "su" have any potential effect on my usage?
>
> Maybe. If you haven't created an /etc/default/su file, then something
> like this:
If he hasn't noticed yet, I doubt it.
I noticed when I finally erased Stretch and installed Boo
On 2025-03-26, Richard Owlett wrote:
>> If he hasn't noticed yet, I doubt it.
>
> I agree.
> If I understand what people want to accomplish by using command-line
> options, I would likely have gone to System->Log Out ... and then logged
> in as root.
Not recommended.
On 2025-03-26, Max Nikulin wrote:
> [...]
>> Who the hell the mentioned copying tables, but you?
>
> My intention was to clarify confusion of Cindy and to lower down
> expectations of Mick.
Yes, sorry about that.
I'm all for lowing expectations after all.
On Wed 26 Mar 2025 at 10:03:59 (-0500), Richard Owlett wrote:
> On 3/26/25 9:55 AM, Greg wrote:
> > On 2025-03-26, Richard Owlett wrote:
> >
> > > > If he hasn't noticed yet, I doubt it.
> > >
> > > I agree.
> > > If I understand what people want to accomplish by using command-line
> > > options
On Wed 26 Mar 2025 at 16:24:21 (+0300), J wrote:
> ср, 26 мар. 2025 г. в 16:10, Greg Wooledge :
> > On Wed, Mar 26, 2025 at 07:48:16 -0500, Richard Owlett wrote:
> > > On 3/26/25 6:55 AM, Greg Wooledge wrote:
> > > > I normally use "sudo -s", which is the closest sudo approximation to
> > > > the t
On 3/26/25 9:55 AM, Greg wrote:
On 2025-03-26, Richard Owlett wrote:
If he hasn't noticed yet, I doubt it.
I agree.
If I understand what people want to accomplish by using command-line
options, I would likely have gone to System->Log Out ... and then logged
in as root.
Not recommended.
On 2025-03-25, wrote:
>
> I enjoyed it. Max is always very knowledgeable.
You're right. Sorry.
>> Who the hell the mentioned copying tables, but you?=20
>
> Grumpy today?
Mildly irascible, let's say.
On 3/26/25 9:04 AM, Greg wrote:
On 2025-03-26, Greg Wooledge wrote:
Does this "brokenness" of "su" have any potential effect on my usage?
Maybe. If you haven't created an /etc/default/su file, then something
like this:
If he hasn't noticed yet, I doubt it.
I agree.
If I understand what
On Wed, Mar 26, 2025 at 01:38:55PM -, Greg wrote:
> On 2025-03-25, wrote:
[...]
> > Grumpy today?
>
> Mildly irascible, let's say.
Happens to me sometimes, too.
Cheers
--
t
signature.asc
Description: PGP signature
On Wed, Mar 26, 2025 at 10:16:19AM -0400, Stefan Monnier wrote:
> > I was once sitting at a $(DAYJOB) where they blocked everything but
> > 443 (and 80). I tunneled ssh over socat (with TLS, so that the handshake
> > didn't look suspect, in case their firewall sniffed that).
>
> Reminds me: I have
On Sun, 23 Mar 2025 15:25:31 -0400
Felix Miata wrote:
> 0 upgraded, 48 newly installed, 0 to remove and 1 not upgraded.
> Need to get 6,874 kB of archives.
> After this operation, 23.0 MB of additional disk space will be used.
> Do you want to continue? [Y/n] n
> Abort.
> #
> :~(
Yes, I'm gettin
On Wed, Mar 26, 2025 at 04:19:37PM +0300, J wrote:
> >
> > > work with* root?* I will try to test.
> >
> > I fully expect it to, yes.
> >
>
> Oh, yes, it works. I just had to use *sudo su* and not not
I think you never need "sudo su". "sudo -i" and "sudo -s" will do your
bidding, depending on you
On 2025-03-25, Dave Howorth wrote:
> On Tue, 25 Mar 2025 17:17:24 - (UTC)
> Greg wrote:
>
>> On 2025-03-23, Julio Gil Garcia wrote:
>> >
>> > Thanks Andrew, also for your translation effort.
>>
>> Hoy en día, realmente no supone ningún esfuerzo.
>>
>
> Que?
>
De nos jours, cela ne demand
>
> > work with* root?* I will try to test.
>
> I fully expect it to, yes.
>
Oh, yes, it works. I just had to use *sudo su* and not not
*su - *
Also it's bad that Wiki doesn't clarify* how to* 'boot the rescue system
including the kernel option "efi=runtime" and mount the EFI variables
before pro
On Wed, Mar 26, 2025 at 07:48:16 -0500, Richard Owlett wrote:
> On 3/26/25 6:55 AM, Greg Wooledge wrote:
> > I normally use "sudo -s", which is the closest sudo approximation to
> > the traditional behvior of "su" (before it was broken in buster).
>
> I don't understand the reference to some "brok
On Wed, Mar 26, 2025 at 12:23:38 +0100, to...@tuxteam.de wrote:
> On Wed, Mar 26, 2025 at 02:15:03PM +0300, J wrote:
> > And i thought *sudo -i*, you speaking about, is something like
> > *--interactive*, which is not, how i see now...
>
> The long form is "--login", not interactive. But the "-i"
On Wed, Mar 26, 2025 at 02:15:03PM +0300, J wrote:
> > In my opinion, "sudo -i" might be added to the wiki articles. I would
> > prefer to see a warning concerning compound shell commands in *sudo* docs.
> >
> > J, my impressions is that you read some docs strongly suggesting to
> > prefix every co
> In my opinion, "sudo -i" might be added to the wiki articles. I would
> prefer to see a warning concerning compound shell commands in *sudo* docs.
>
> J, my impressions is that you read some docs strongly suggesting to
> prefix every command instead of just becoming root.
Actually it is easier
On Wed, Mar 26, 2025 at 11:28:40AM +0100, Erwan David wrote:
[...]
> > My bet was that 443 is always open because otherwise mid- and hi-
> > level mgmt would be on top of the poor admins because they couldn't
> > go to their share trading casinos: I won :)
>
> Admins would also have problems to
On 3/26/25 05:04, to...@tuxteam.de wrote:
On Wed, Mar 26, 2025 at 09:41:55AM +0100, Nicolas George wrote:
to...@tuxteam.de (HE12025-03-26):
I was once sitting at a $(DAYJOB) where they blocked everything but
443 (and 80). I tunneled ssh over socat (with TLS, so that the handshake
didn't look
to...@tuxteam.de (HE12025-03-26):
> I was once sitting at a $(DAYJOB) where they blocked everything but
> 443 (and 80). I tunneled ssh over socat (with TLS, so that the handshake
> didn't look suspect, in case their firewall sniffed that). Bonus: I
> got to see whether they did MITM, since I made m
jeremy ardley (HE12025-03-26):
> One reason to choose VPN over ssh is that many ISPs block incoming ports
> including ssh, telnet, RDP, smtp, and smb ports.
And they do not block ports used for VPNs. How convenient.
--
Nicolas George
38 matches
Mail list logo
