Today is the anniversary of the launch of the #Linux #Kernel Self-Protection Project (2015), and the invention of the Flux Capacitor (1955):
https://lore.kernel.org/kernel-hardening/CAGXu5jJ3FgxXK9WuOLRwnEq=y4dS+CTm+WQBxWe3sYZ7e9p6Gg@mail.gmail.com/

Every argument about undefined behavior in a nutshell

having worked with many #infosec #researcher's over the years sometimes (definitely not always) they have a misconception that being able to build and/or detonate a bomb gives you capability to be a great #programmer.

if this was the case, safe thieves should build safes, and police department should be recruited from organized crime groups.

an infosec researcher can also definitely be a great programmer but they are different crafts.

"Toinen yllätys oli se, että poliisi sai avattua vahvasti salattujen palvelimien tiedot auki. Niitä suojannut salasana oli 64-merkkinen, ja sen poliisi onnistui selvittämään."

Tämä jäi itselläkin kytemään, että millä tempulla salasana saatiin selville.

https://www.is.fi/digitoday/tietoturva/art-2000009983201.html

#vastaamo

En käytä ruokalähettipalveluja, koska bisnesmalli on moraaliton. Omistajien verojen maksu on taas tämän tosiasian valkopesua.Toisten selkänahasta revitty fyffe on väärin, vaikka siitä maksaisi kuinka paljon veroja.

https://www.iltalehti.fi/kotimaa/a/b1cd31b2-5992-4302-ad4c-9d88e38f7fb2

#foodora #wolt

One thing where I would use #rustlang rewrite: vim/neovim clone. Helix/Amp etc. have the problem that they try to do something new.

Actually the best would be if @neovim would join the club of Firefox, Linux etc. and provide shenanigans for rewriting parts of it in Rust. I promise to contribute in this effort, if that ever happens (no time for working on the shenanigans unfortunately).

totally missed this https://git-scm.com/docs/git-worktree

printing hex in the #python shell:

>>> val = bin(0x1119e)[2:]
>>> ' '.join(list(map(lambda i: val[i:i + 4], range(0, len(val), 4))))
'1000 1000 1100 1111 0'

#note

I like the #BeagleBone layout in #BeagleV:

https://www.beagleboard.org/boards/beaglev-ahead

Very nice indeed, should get one.

#riscv #beagleboard

.@beagleboardorg launched the BeagleV®-Fire, a new SBC that opens up new horizons for developers, tinkerers and more to explore the vast potential of #RISCV architecture and FPGA technology: https://riscv.org/news/2023/11/beagleboard-org-makes-fpga-and-risc-v-accessible-with-new-beaglev-fire-single-board-computer-at-150/?hss_channel=tw-2694452875 #RISCVeverywhere

Original tweet: https://twitter.com/risc_v/status/1723024225127076007

Did you know you could control brightness of the red dot on the i of the "ThinkPad" on the top-side of your thinkpad? I sure didn't:

this turns it off:

echo 0 | sudo tee /sys/class/leds/tpacpi\:\:lid_logo_dot/brightness

and this turns it on:

echo 255 | sudo tee /sys/class/leds/tpacpi\:\:lid_logo_dot/brightness

I don't really know what this information is good for, but hey, isn't it awesome to have a 1px display on the outside of your laptop?

Kaljantaikevennys!

watched this embarrassingly many times https://www.youtube.com/watch?v=M8bt2SJnuX4

making new tracks over the weekend, here's one released last june https://nullzone2007.bandcamp.com/track/lumo-ava-2

macro(import_binary_as_elf Path Symbol Target)
    set(objcopy_flags -I binary -O default -B riscv)
    string(MAKE_C_IDENTIFIER ${Path} unstripped)
    add_custom_command(
        OUTPUT ${Path}.elf
        DEPENDS ${Target}
        COMMAND 
             ${CMAKE_OBJCOPY} ${objcopy_flags}
             ${Path} ${Path}.elf
        COMMAND
              ${CMAKE_OBJCOPY} -N
              _binary_${unstripped}_end ${Path}.elf
        COMMAND
              ${CMAKE_OBJCOPY} --redefine-sym
              _binary_${unstripped}_start=${Symbol}_start
              ${Path}.elf
        COMMAND
              ${CMAKE_OBJCOPY} --redefine-sym
              _binary_${unstripped}_size=${Symbol}_size
              ${Path}.elf
    )
    add_custom_target(${Symbol}_elf DEPENDS ${Path}.elf)
endmacro()

#cmake #riscv #embed #binary #elf #note

quick #m8tracker #synthwave jam during kid's naptime

Are you someone who has a simple fix for something in the Linux kernel, but haven't bothered submitting a patch because you find the email workflow daunting? Can be a bugfix, spelling correction, anything at all.

If so, I want to talk to you! I have tools that simplify this process quite a bit, but I need more feedback from people who aren't long-term Linux maintainers.

Please reach out, either via here or by emailing mricon@kernel.org.

Some learnings of RISC-V, at least from CVA6 perspective:

1. If there is any SATP or PTE sync issue, sprinkle first sfence.vma together with fence.i. It is not optimal but usually ensures stability. Once things are functionally together sync points can be reduced.
2. Might be CVA6 specific issue but I’ve sometimes had issues with W PTE’s created without having also D, causing odd crashes. So again, I’ve taken the habit of first binding these together and later on reduce.

I’ve yet use ASIC boards, have only used FPGA so far and development versions of CPU’s. I guess these sort of fail-safe practices are more important in early development

#riscv #fpga #note

I like Rust in kernel, and more generally in the backend but Rust command-line replicas mostly are just software bloat tbh.

#rustlang