…is suing the state of California for the First Amendment.
I wonder if this will end up in the Supreme Court?
Category Archives: Technology and Society
We Are So Screwed
Make Your Flight-Test Predictions
[Late-afternoon update]
Go for Monday. SpaceX has gotten their launch license.
That means I have to get up at an ungodly hour to see the launch (window opens at 0500 PDT).
California’s “Clean Energy” Policy
It’s been a disaster, and it would be even worse if Biden imposes it on the rest of the country.
biden’s EV Edict
…is fascistic.
What’s Been Happening AT Starbase
A deep dive.
“Excitement Guaranteed”
Expecting the launch license this week, but no guarantees of that.
Chaos Versus Maskirovka
Thoughts on the classified leaks and the coming offensive in Ukraine.
Starship to Mars
Amazing CGI.
[Update a while later]
And then there’s this:
Read the thread. Most people think (correctly) that this is nuts.
I’m willing to agree that it’s a religion, but rocks don’t have rights. The moon is just a very large rock.
Fedora Upgrade Issue
When doing an upgrade with dnf (going from 34 to 35), I’m getting a slew of transaction test errors like these:
file /usr/bin/qemu-alpha-static from install of qemu-user-static-2:6.1.0-16.fc35.x86_64 conflicts with file from package qemu-user-static-alpha-2:6.2.0-17.fc36.x86_64
file /usr/share/systemtap/tapset/qemu-alpha-static.stp from install of qemu-user-static-2:6.1.0-16.fc35.x86_64 conflicts with file from package qemu-user-static-alpha-2:6.2.0-17.fc36.x86_64
file /usr/lib64/python3.10/site-packages/pycrypto-2.6.1-py3.10.egg-info from install of python3-crypto-2.6.1-36.fc35.x86_64 conflicts with file from package python3-crypto-2.6.1-39.fc36.x86_64
file /usr/lib/udev/rename_device from install of initscripts-10.15-1.fc35.x86_64 conflicts with file from package initscripts-rename-device-10.16-3.fc36.x86_64
Anyone know what’s going on, and how to fix it?
[Update Monday morning]
OK, the problem is that I’m trying to upgrade to 35 when in fact I’m running 36. And the weird thing is that ‘uname -r’ says it’s 34, while /etc/fedora-release says it’s 36. And when I boot it, it’s using a 34 kernel. So, I decided to upgrade to 37 instead, since in actuality, other than the kernel, all my packages are 36. That upgrade went well, but I don’t know what will happen if I actually do a reboot into the new version. I’m asking people on the Fedora forum. The mystery is why it’s running on a 34 kernel.
[Bumped]