On Fr, 01.09.23 02:02, Christian Pernegger (perneg...@gmail.com) wrote:
> Am Do., 31. Aug. 2023 um 21:55 Uhr schrieb Andrei Borzenkov
> :
> >
> > On 31.08.2023 19:22, Christian Pernegger wrote:
> > There is no ID_SEAT, so this device [/dev/rfkill] ]belongs to seat0 by
> > default.
>
> It makes no
Am Fr., 1. Sept. 2023 um 11:48 Uhr schrieb Lennart Poettering
:
> > It makes no sense for /dev/rfkill to belong to a specific seat,
> > though.
>
> Typically any RF kill buttons are attached to the main seat of a
> laptop only, hence this assignment.
If there's some form of physical RF kill button
On Fr, 01.09.23 13:13, Christian Pernegger (perneg...@gmail.com) wrote:
> Of course, if you want to take the position that it's a bit weird for
> GNOME to use /dev/rfkill to detect the presence of BT devices, I can't
> argue against that. :)
Doesn't NM/bluez manage these things from privileged co
I may just be over-thinking this but I have a scenario that I can configure
manually but have not been able to figure out how to amend the networkd
configuration to match!
# echo "2 starlink" >> /etc/iproute2/rt-tables
# ip -6 rule add from 2001:0DB8:1:1::/64 table starlink priority 100
# ip -6
On Fri, 1 Sep 2023 13:13:12 +0200
Christian Pernegger wrote:
> Alright. I only played around with it in the hopes that it would help
> me get some VTs (and VT switching) on seat1. So far, no luck on that
> front.
The funny thing there is that the kernel, where the VT is implemented,
has no idea
On Fri, 1 Sep 2023 13:37:46 +0200
Lennart Poettering wrote:
> On Fr, 01.09.23 13:13, Christian Pernegger (perneg...@gmail.com) wrote:
>
> > I don't know about this. Yes, seat1 could hog the GPU that seat0's
> > outputs are attached to, or vice versa, but seat1 could just as well
> > hog all the
On Fri, Sep 1, 2023 at 2:55 PM TJ wrote:
> I may just be over-thinking this but I have a scenario that I can
> configure manually but have not been able to figure out how to amend the
> networkd configuration to match!
>
> # echo "2 starlink" >> /etc/iproute2/rt-tables
> # ip -6 rule add from 200
On 01/09/2023 14:15, Mantas Mikulėnas wrote:
No; `default` has nothing to do with the gateway field. It's an alias for
the route *destination network* field, specifically ::/0 for IPv6 or
0.0.0.0/0 for IPv6.
What you have is a completely standard IPv6 default route, regardless of
which table it
Okay
Hi,
i am running a bunch of partly very different systems with Debian
Bookworm. On this machines, i am using systemd 252 (252.12-1~deb12u1).
If i am configuring journald, i am facing the problem, that /var/log is
having a very different size on all my machines. From 100M to 8G or
something.
Hi community,
I am experiencing an issue while using journald, and I would like to inquire
whether this is a known issue within the community.
The problem is I see duplicate log lines appearing in journald sometimes. It
seems that certain log entries are being duplicated, which can make log
an
On 02.09.2023 00:29, PureLinux Betriebsführung wrote:
Hi,
i am running a bunch of partly very different systems with Debian
Bookworm. On this machines, i am using systemd 252 (252.12-1~deb12u1).
If i am configuring journald, i am facing the problem, that /var/log is
having a very different size
12 matches
Mail list logo
