On Sun, Jul 17, 2022 at 10:38:53AM +0200, Matthieu Herrb wrote:
> Hi,
>
> twm(1) is the original X11R5 window manager. It has not been update to
> support any of the extended window manager hints and still only knows
> how to handle the legacy bitmapped fonts rendered by the X server.
>
> In port
I use it, have used it, and will continue to use it full time.
It is simple, low resource use and works on any system I have.
I don't need any more functionality in a window manager.
Anything else can be added on.
The argument presented is something like "why would anyone want to do that".
geoff
Bump.
sure you do! otherwise I figure you'd have removed it already :)
dropping the diff.
On 17:08 Mon 18 Jul , Florian Obser wrote:
> yes, I use it daily.
>
> $ dig @k.root-servers.net +norec +noall +answer hostname.bind ch txt
> hostname.bind.0 CH TXT "ns1.ch-gva.k
On 2022-07-18 14:52 +01, Ricardo Mestre wrote:
> Hi,
>
> I'm too young to ever know there were other types of networks still supported
> by
> dig(1), but it seems it's a thing. Found while reading [0].
>
> Realistically speaking do we want to keep supporting these kind of ancient
> networks on ou
Hi,
I'm too young to ever know there were other types of networks still supported by
dig(1), but it seems it's a thing. Found while reading [0].
Realistically speaking do we want to keep supporting these kind of ancient
networks on our version? Is there still someone out there using them?
[0] ht
On Mon, Jul 18, 2022 at 03:46:05PM +0200, Claudio Jeker wrote:
> Noticed the other day, when the RDE dies the session engine may log the
> "Can't send message %u to RDE, ctl pipe closed" multiple times because
> the queue is still processed.
>
> Since this error only happens after a "SE: Lost conn
Noticed the other day, when the RDE dies the session engine may log the
"Can't send message %u to RDE, ctl pipe closed" multiple times because
the queue is still processed.
Since this error only happens after a "SE: Lost connection to RDE" error
it does not anything to the crash log. This is why t
pipex(4) doesn't rely on netlock anymore.
Index: sys/net/if_pppx.c
===
RCS file: /cvs/src/sys/net/if_pppx.c,v
retrieving revision 1.119
diff -u -p -r1.119 if_pppx.c
--- sys/net/if_pppx.c 15 Jul 2022 22:56:13 - 1.119
+++ sys
On Fri, Jul 15, 2022 at 06:58:33PM +0200, Mark Kettenis wrote:
> > Date: Mon, 11 Jul 2022 16:21:39 +0200
> > From: Anton Lindqvist
> >
> > On Mon, Jul 11, 2022 at 09:02:20AM +0200, Mark Kettenis wrote:
> > > > Date: Mon, 11 Jul 2022 08:35:44 +0200
> > > > From: Anton Lindqvist
> > > >
> > > > H
We don't use "static" keyword for functions declaration to allow ddb(4)
debug. Also, many "Static" functions are called by pppx(4) layer outside
pipex(4) layer.
This is the mostly mechanic diff, except the `pipex_pppoe_padding' which
should be "static const".
Index: sys/net/pipex.c
==
I think cwm works fine for that and it is still there.
Den mån 18 juli 2022 08:39Alessandro De Laurenzis
skrev:
> This is just the perspective of a user (even less: my _personal_
> perspective).
>
> Removing twm would be a mistake in my opinion. It is still pretty
> functional and, when correctl
12 matches
Mail list logo
