Posts by ptesarik@infosec.exchange
(DIR) Post #AybEBjE0iVeJeuqVvM by ptesarik@infosec.exchange
2025-09-26T13:25:23Z
0 likes, 0 repeats
@piggo nopefound it nowyes, it looks like a gamebut it isn't playable
(DIR) Post #AybEBl8laydvbEPM1o by ptesarik@infosec.exchange
2025-09-26T13:29:54Z
0 likes, 0 repeats
@piggo uh-oh, I quit playing games a few decades ago, but has gaming really changed so much?is it essentially pure brainrot now?
(DIR) Post #AyjBLw4b3bjxnxIWLg by ptesarik@infosec.exchange
2025-09-30T09:15:38Z
0 likes, 0 repeats
@lkundrak And now I'm seriously searching a church.
(DIR) Post #Az4BOXeEPFmBEuMnMO by ptesarik@infosec.exchange
2025-10-10T11:31:11Z
0 likes, 0 repeats
Guys, so what is the current consensus on line length in the kernel? Coding style still says:The preferred limit on the length of a single line is 80 columns.This is not a hard limit and it may (or even must) be exceeded if there are good reasons. That's also mentioned in the document. But then I get a nitpick like this:It is still under the 100 character limit.Where does it come from? Should the coding style be updated?@corbet ?
(DIR) Post #B06AcoCqQeAbguxjyS by ptesarik@infosec.exchange
2025-11-09T12:41:44Z
1 likes, 0 repeats
@ljs @vbabka @lkundrak smoke it
(DIR) Post #B06P4vMQov1ZLbkOwK by ptesarik@infosec.exchange
2025-11-10T10:56:23Z
0 likes, 0 repeats
@vadim @lkundrak Sorry for being too dumb, but would sir mind clarifying it for me?Is it because old people don't torrent porn, or because they no longer wank in the morning?
(DIR) Post #B0MgMAQb1EWQzXq2i0 by ptesarik@infosec.exchange
2025-11-18T08:45:31Z
1 likes, 0 repeats
@vadim @vbabka @pony keyboard for lunch?
(DIR) Post #B0ZDFQqYlIKp2AxQDg by ptesarik@infosec.exchange
2025-11-24T09:43:18Z
0 likes, 0 repeats
@wagi @ljs @vbabka @lkundrak Take this as my humble contribution to the general trend of enshittification.
(DIR) Post #B0hYnMcEeSRQ3kxS3k by ptesarik@infosec.exchange
2025-11-28T10:23:32Z
0 likes, 0 repeats
@ljs @bonkers Exactly! We need the feature so we can test the feature. I'm glad you got me right.Hail whom?
(DIR) Post #B0nWa5ryZGuJOjcmn2 by ptesarik@infosec.exchange
2025-12-01T05:42:25Z
0 likes, 0 repeats
@hny @vbabka @pony When I was young, boozing was a social activity. We socialized in front of a večerka or nápojka, and it was beautiful.
(DIR) Post #B0nxnBVHd6FFOlTdXU by ptesarik@infosec.exchange
2025-12-01T08:38:51Z
0 likes, 0 repeats
@vbabka @hny @pony Sounds like great time.Happy Hack Week BTW!Večerka with chairs and/or bench in Prague when?
(DIR) Post #B0q8WaIXg8hrBbiyFU by ptesarik@infosec.exchange
2025-12-02T13:52:54Z
0 likes, 0 repeats
@pony @vbabka @lkundrak does it run Doom, or what?
(DIR) Post #B12B2nwH1s4OZ3Jpvk by ptesarik@infosec.exchange
2025-12-08T08:02:40Z
0 likes, 0 repeats
Oh, great! This morning (after a #Slowroll update), @kde has finally reached feature parity between #Wayland and #X11 for me: When I try to log in, I get only black screen in both cases.EDIT: My apologies to #KDE. This was a hanging ssh-add process waiting for a password on an apparently random terminal (definitely not visible on screen). It was started by keychain, which I added to my bash profile to work around missing ssh-daemon support in Wayland sessions. After I killed it using SSH from another computer, my desktop environment is now back to #SNAFU (freezing and crashing) behaviour.
(DIR) Post #B14nD07InAUlnsgcBE by ptesarik@infosec.exchange
2025-12-03T17:11:32Z
0 likes, 1 repeats
And now #konsole even crashed on me. This never happened to me with KDE and #x11, but it's the third (and most serious) issue I have with KDE and #Wayland. Let me repeat, @kde, I have no objections against #Wayland as such. It's fighting with the most basic functionality that puts me off.
(DIR) Post #B1MmnDleufZ9SPY5Xk by ptesarik@infosec.exchange
2025-12-18T07:39:36Z
1 likes, 0 repeats
@woozleYou want to see the socket?I want to see the fanout!@NanoRaptor
(DIR) Post #B3TCQiRuukSLt0CYlM by ptesarik@infosec.exchange
2026-02-18T15:54:58Z
0 likes, 1 repeats
Hit another #KDE #Wayland bug: Importing an mbox file in Claws crashes the entire desktop. 100% reproducible. Of course, I'll write a proper bug report. As soon as I don't need my desktop for actual work.Yes, people have other things to do than writing bug reports. And that's why many desktop bugs are not reported, or the bug reporter “disappears” without testing a fix…EDIT: Oh, actually, the entire desktop does not crash. There is a lonely survivor: Konsole. No idea why.
(DIR) Post #B4csyTaHlV2JeFC7RA by ptesarik@infosec.exchange
2026-03-25T19:52:57Z
0 likes, 0 repeats
@vbabka @lkundrak @poni @katka Sounds like a plan. Is there an upper limit on intoxicated software engineers?
(DIR) Post #B56whm5hvsYkgKytto by ptesarik@infosec.exchange
2026-04-09T07:31:42Z
0 likes, 0 repeats
@poni @lkundrak @vadim No, this is the wrong direction.Somebody should get rid of the remaining ugly C code in Emacs by rewriting them in pure lisp, so it can run natively on a Symbolics 3640.
(DIR) Post #B5JqUMDClWDtz7BaqW by ptesarik@infosec.exchange
2026-04-15T09:19:50Z
1 likes, 0 repeats
@adingbatponder Since the problem statement is not very clear, my answer is a bit generic.First, I hope you know the kernel can reboot itself automatically using a hardware and/or software watchdog.Second, you can tell the kernel to pin all memory of a process in physical RAM, and under some circumstances, it may prevent memory allocations. This is good to implement a watchdog keepalive process, but not a usable SSH session.Third, assuming your kernel is built with memory cgroups, you can run your critical services in a separate cgroup that is properly sized to handle the required workload.
(DIR) Post #B6HdyOaIFk5LzVJriC by ptesarik@infosec.exchange
2026-05-14T09:12:19Z
1 likes, 0 repeats
@algebraicterror @lkundrak Fuj.Leda tohle PIKO:https://www.piko.de/