What do you mean the chair is haunted?

After a Fedora kernel update WiFi works differently :-)

I have not dared to try out suspend (it's completely disabled) but now WiFi connection seldomly and randomly plain dies and I need to reconnect.

#fedora #linux

@mairacanal yeah, i agree! I like it because it is the only theme where both light and dark versions work for me :-) while hacking i like to use dark and while in meetings and in presentation slides the light version is great

@pid_eins s/Models/Modules/ ;-)

Sorry could not help myself, otherwise cool stuff...

I think I wait buying a new computer up until 3950X3D is out and then make a pre-order. I want a mATX form factor machine. I sold my PC when I started at Parity Technologies so for now have to survive with a shitty Thinkpad ;-)

The only other part I know for sure is https://www.fractal-design.com/products/cases/meshify/meshify-2-mini/black-tg-dark-tint/

This is because I only ever buy Fractal Design cases :-)

Can't wait for the smell of a fresh computer...

@oleksandr more i've used 6.11 in fedora more i feel like that kernel release was a mistake ;-) random crashes, wifi not working etc. no time to write bug reports all the time...

x.x.x.x - - [10/Nov/2024:00:02:37 +0000] "GET / HTTP/1.1" 301 162 "-" "okhttp/4.9.0"

You know what’s interesting about this log line? It repeats 56,686,963 times in www.kernel.org logs for yesterday, across 4 nodes. That’s about 700 times a second, and this has been going on for months.

These requests aren’t intentionally malicious – they issue a simple GET /, receive their 301 redirect, and terminate the connection. From what I can tell, this is some kind of appliance or software installed on mobile clients that uses “can I reach www.kernel.org” as a network test.

This wouldn’t be that big of a deal – a single plaintext “GET /“ that triggers an immediate 301 is very cheap for us to generate, but the number of these requests has been steadily growing.

If you have any idea what this is and how to make it stop, please reach out?

@mairacanal After knowingly realizing the different order of vim and helix I don't find too complicated to use both either. Vim is "do-select" and helix is "select-do" :-) That's the main philosophical difference.

@mairacanal Yes.

You just have to generate the compile_commands.json manually as shown by my example in this toot. That is the file that will be recognized by clangd (the LSP server for C). You have to build the kernel first so thus I have that separate "LSP build" stored under ".clangd".

For anyone who cares my helix config is available at: https://codeberg.org/jarkko/skeleton/src/branch/main/.config/helix

https://beincrypto.com/truth-terminal-becomes-crypto-millionaire/

@mpdesouza I gave a test run for a (trivial) kernel patch: https://lore.kernel.org/linux-integrity/20241113002414.609168-1-jarkko@kernel.org/T/#u

Was not a bad experience and finding files with <space> + f was convenient. Will try another time.

I have to agree with Boris. It's a force majeure situation. What else could we do. I'd guess that UK would get support from Nordic and Baltic states if this action was taken and there would be a coalition.

And DRPK troops terrorizing Europe is unacceptable. Any country who brings them here in this region should pay the consequences. It's even orthogonal to the war situation. North Korea is an enemy state and any aggressive action from such should receive a clear and brutal response.

https://www.independent.co.uk/news/uk/politics/boris-johnson-ukraine-uk-troops-putin-b2645681.html

one aerc feature i always keep forgetting:

1. s: toggle the message view in a horizontal split.
2. S: toggle the message view in a vertical split.

#aerc #email

It's not mentally hard to switch betwen vim and helix because vim is "do-select" and helix is "select-do". They play opposites.

#helix #vim #editor

@mpdesouza So I did a kernel workaround in .config/helix/languages.toml:

[[language]]
name = "c"
indent = { tab-width = 8, unit = "\t" }

:-) I mean I rarely use anything else than kernel convention for any C code not a big deal… Still would be nice to have editorconfig eventually for some contribution or something.

For using compile_commands.json with kernel this the workflow I’ve ended up with:

make ARCH=x86_64 O=./.clangd x86_64_defconfig                                       
make ARCH=x86_64 O=./.clangd menuconfig
make ARCH=x86_64 O=./.clangd -j`nproc`
scripts/clang-tools/gen_compile_commands.py -d ./.clangd

This way it does not confuse e.g. BuildRoot when I point out my BuildRoot with LINUX_OVERRIDER_SRCDIR to my local kernel tree. Not sure if there is better way to do this but feels like a working workflow in my case.

Nice to see some real innovation with Rust in text editors instead pwning the GPU or similar features. If you editor will not work in terminal, it will end up sucking in the end, as far as I’m consdered :-) Not minding of having also GUI but first things first…

@rolle propsit muuten jäbän irssi-teemasta, tuli tämmöinen ihan vahingon kautta vastaan: https://github.com/ronilaukkarinen/weed !

@rolle.wtf@bsky.brid.gy @rolle tää taas on vähän niin kuin usenet tai sitä ennen fidonet (muinaisina BBS-aikoina). semmoista kirjavampaa keskustelua ja näkemystä, ei niin poliittisten suuntausten dominoimaa.

@rolle.wtf@bsky.brid.gy @rolle jos jonkun somen poistasin vielä niin bsky olis ekana tappolistalla ;-) se on vähän niin kuin vasemmiston twitter ja X on oikeiston twitter. siirrytty kahteen hiekkalaatikkoon.

@wren3n also vim already had too many features, so for it never made sense to break the old ones and pile bunch of new ones on top... it is called inconsistency in my books :-) making something completely new from clean slate is something i get much better. and for terminal.