Posts
4332Following
313Followers
444Entrepreneur at Siltakatu Solutions Oy
OpenPGP: 3AB05486C7752FE1
repeated
Gerry McGovern
gerrymcgovern@mastodon.green
Former out and out scumbag, depraved psychopath and and god-wannabe Google CEO tells US congress that 99% of all electricity will be used to power superintelligent AI. And he's serious, he's totally serious.
So, all the barbers and bakers, the hospitals and schools can survive on 1% electricity and water, while the tech bros devour 99% of everything. This is their plan. This is how they think. This is how they feel. Big Tech will burn everything to the ground.
https://futurism.com/google-ceo-congress-electricity-ai-superintelligence
0
2
0
repeated
darktable
darktable@photog.socialOur camera support is completely community driven! If you camera isn't supported, you can get it added by following the instructions at https://github.com/darktable-org/darktable/wiki/Camera-support
0
2
0
repeated
Jarkko Sakkinen
jarkkohttps://www.youtube.com/watch?v=16feIwUHB9w
#games #ultima #commodore #vic20
1
1
2
repeated
Jarkko Sakkinen
jarkkohttps://lwn.net/Articles/723477/
It's not discussed in the cover letter but obviously this would be much better tool for "full user space nesting" than namespace based containers.
I.e., kind of between Podman and Kata Containers as an infrastructure.
1
0
0
Jarkko Sakkinen
jarkkomy #build #container framework:
sudo unshare \
--fork \
--mount \
--uts \
sh -c "
mkdir -p $ROOTFS/proc
mkdir -p $ROOTFS/sys
mkdir -p $ROOTFS/dev
mount -t sysfs /sys $ROOTFS/sys
mount -t proc /proc $ROOTFS/proc
mount --rbind /dev $ROOTFS/dev
hostname $MACHINE
su $USER
export PUAVO_CACHE_PROXY=$PUAVO_CACHE_PROXY
sudo unshare --root $ROOTFS $CMDLINE
"
Jarkko Sakkinen
jarkkohttps://bsky.app/profile/jarkk0.bsky.social/post/3lmkaiqxdb22o
0
0
1
Jarkko Sakkinen
jarkko
0
0
1
Jarkko Sakkinen
jarkko🇪🇪 🇸🇪 🇫🇮
0
0
2
Jarkko Sakkinen
jarkkohttps://lore.kernel.org/keyrings/Z_e9CVsmiXD3QYkg@kernel.org/
It's a good timing, given that we are at -rc1. key_put() is exactly type of code where:
1. You need to be extremely conservative.
2. Still there's a chance for breakage.
3. struct key is widely accessed kernel object in various context's. Thus, it is practically impossible to consider every possible use case.
I'll put this to my v6.16 PR if it turns out to not cause too much devastation :-)
#linux #kernel #keyring
0
0
0