Maybe I can ask @jorge ?
Can I rebase to a different kernel or is this going to break things and cause me to get slow updates and cry ? #factcheckingAI #atomic
Someone needs to tell Hegseth that the Enola Gay was a delivery system for one of the most horrific war crimes committed by the US, the Atomic bombing of Hiroshima, NOT some sort of queer DEI pentagon grooming propaganda.
"Atoms for peace" on your Christmas tree? I found these (presumably vintage mercury glass) ornaments at the local Goodwill outlet and did a double-take. They were all in this box, along with detritus and bits of broken glass; no idea if they were sold as a set or someone stored them together like this.
Shot (August 2024) from the rim of the subsidence crated, Project Faultless unclear detonation site. The top of the rusted shaft to the left was flush with the surface prior to the detonation of a 1 MT device at 3200 feet in 1968 #faultless #nuclear #nucleartestsite #subsidence #crater #projectcrosstie #atomic #AEC #nuke
This default wallpaper in #Aurora 41 is absolutely stunning.
Discover how #Atomic and #Transactional systems are redefining development, and how tools like #Distrobox make containerized environments feel just like home, from this #openSUSE Conference #Keynote. https://youtu.be/ExnlVwXcBkk?si=FQYMNF7Ai__VX7tu
anyone who uses #bazzite or #fedora #silverblue #atomic know what i should know if i want to switch from ubuntu? W/r/t software differences, drivers, etc.? the 22.04-24.04 upgrade borked, and i've been thinking of switching over to it for a while
Hello from Ultramarine on bootc!
(Ultramarine Atomic GNOME 41, development build) #tech #fedora #bootc #atomic #immutable #immutablelinux #ultramarine #ultramarinelinux #foss #linux
Project Faultless Nuclear Detonation Test Site Exploration Part 1. January 19, 1968 at 10:15am. a 1 megaton warhead was detonated in a remote section of Nye County, Nevada to test the suitability of the area for larger explosions. #nuclear #test #faultless #atomic #abandoned
Hey. A different post for today.
After using #Aurora from the #uBlue team for almost 24h now, I realized that although it's hassle free for most users, when it comes to tweaking, it's not all sunshine n roses. A lot of work & knowledge will be needed. Heck just making #Fastfetch use my own custom config had me go to their forums to figure out I had to edit the script they ship by default in a weird location. Fun for me not so much for everyone. 1/2
#FOSS #Linux #Atomic #OpenSource
How has people's experience been rebasing to #universalblue #aurora from #kinoite and potentially back again? I may have a need of the convenience of the image on one of my machines. I know that early on the official instructions were to rebase from #fedora #atomic spin to #ublue, but it now seems their site only offers isos?
#BlendOS is #ArchLinux made #Declarative, #Immutable and #Atomic. With #Android app support and #Fedora, #Debian, #CentOS Stream and #Ubuntu containers available, as well as system packages/DEs/kernels from Arch Linux and the #AUR.
On the fediverse at @blendOS
0n the web at https://blendos.co/
Unlike #NixOS, YAML is the primary config language.
More discussion on Lemmy: https://infosec.pub/post/13393420
One thing that would certainly make the initial experience of running #Atomic #Fedora better for seasoned #Linux users is having the `dnf` command exist and grok rpm-ostree out of box. I understand *why* this is the current experience, but there's definitely room for improvement here:
dnf: command not found
Using Python 3.11 or higher, I want to create an output file *and* add a line describing it to a log file as an atomic operation: either the output file is created and the log entry is added, or neither happens. fcntl.flock() is only advisory - will something else give me stronger guarantees, preferably on all three major OSes? #python #file-lock #atomic-operation #question
Today in Labor History May 18, 1979: An Oklahoma jury ruled in favor of the estate of atomic worker Karen Silkwood. Kerr-McGee Nuclear Company was ordered to pay $505,000 in actual damages and $10 million in punitive damages for negligence leading to Silkwood’s plutonium contamination. On appeal, the court reduced the settlement to a pitiful $5,000, the estimated value of her property losses. In 1984, the Supreme Court restored the original verdict, but Kerr-McGee again threatened to appeal. Ultimately, Silkwood’s family settled out of court for $1.38 million and the company never had to admit any wrongdoing.
Silkwood first started working at Kerr-McGee in 1972. She joined the Oil, Chemical & Atomic Workers union and participated in a strike. After the strike, her comrades elected her to the union’s bargaining committee. She was the first woman to attain that status at Kerr-McGee. In this role, one of her duties was to investigate health and safety issues. Not surprisingly, she discovered numerous violations, including exposure of workers to contamination. The union accused Kerr-McGee of falsifying inspection records, manufacturing faulty fuel rods and other safety violations. After testifying to the Atomic Energy Commission, Silkwood discovered that her own body and home were contaminated with radiation. Her body contained 400 times the legal limit for plutonium contamination and she was expelling contaminated air from her lungs. Her house was so contaminated they had to destroy much of her personal property.
Later, she decided to go public with documentation proving the company’s negligence. She left a meeting with union officials in order to meet a New York Times journalist. She brought a binder and packet of documents supporting her allegations with her. However, she never made it, dying in a suspicious car crash. The documents were never found. Some journalist believe she was rammed from behind by another vehicle. Investigators noted damage to the read of her car that would be consistent with this hypothesis. She had also received death threats shortly before her death. However, no one has yet substantiated the claims of foul play.
Retrotechtacular: The Other Kind of Fallout Show - Thanks to the newly released Amazon Prime series, not to mention nearly 30 years a... - https://hackaday.com/2024/04/16/retrotechtacular-the-other-kind-of-fallout-show/ #retrotechtacular #foodsafety #dosimetry #radiation #survival #coldwar #fallout #nuclear #atomic #polish #water
Question for users of #Fedora #Kinoite &/or #openSUSE #Kalpa
I use
#ArchLinux #KDEPlasma #Wayland
as my Host, but enjoy playing with & learning about numerous alternatives in VMs. In the #immutable / #atomic space, two of these VMs are Kinoite & Kalpa. Whilst not yet convinced that they would adequately suit my use-case as potential future Host Arch replacements [coz i'm an inveterate tinkerer], i nonetheless find them fascinating.
In my Host i actively shy away from #Flatpaks, but have come to accept their necessary role in immutables. However IMO the single project that transforms the potential viability of immutables for me is the magnificent #Distrobox. Using DB in both VMs then allows me to create an #Arch container in which i can avail myself of the large range of Arch repo apps, & also once setup in it, all the cornucopia of the #AUR goodies. It's a brilliant combo.
That said, my mind now turns to another essential requirement for me. My default browser is #FirefoxNightly. Though it's available in the AUR, i much prefer downloading it direct from the Firefox site, extracting it from the tar, then moving it to
/opt/firefoxnightly/
. This is elementary in Arch, but checking now in my VMs, i'm somewhat surprised to find that both Kinoite & Kalpa seem to have made their respective /opt
directories immutable along with the rest of the root directory. I'd certainly have hoped that considering the usual uses of /opt
it would have been exempted.
What then do experienced Kinoiters & Kalpans do here? Do you "fight the system" to force Nightly into opt, or do you merely decide to run it from your Home directory?