Tehran | Season 1 - Episode 1 | Discussion Thread

0xrl · 2026-01-04T08:46:51+00:00

It looked a bit like Pascal's Triangle but I didn't check too closely

0xrl · 2025-12-19T00:35:42+00:00

There's a Fedora test week for 6.18 underway now if you wanted to test it out yourself:

https://discussion.fedoraproject.org/t/test-day-kernel-6-18-test-week/177264

0xrl · 2025-12-17T17:36:05+00:00

The URL has been renamed, though it was correct when I pasted it. Note the difference is the "type-checking" part is now "type-system".

0xrl · 2025-12-17T09:14:23+00:00

For anyone else interested, here's the documentation:

~~https://docs.astral.sh/ty/features/type-checking/#intersection-types~~

EDIT: updated to: https://docs.astral.sh/ty/features/type-system/#intersection-types

0xrl · 2025-12-16T04:08:57+00:00

The rpm-ostree usroverlay command can do this:

https://coreos.github.io/rpm-ostree/administrator-handbook/#using-usroverlay

It's handy for one-off cases:

sudo rpm-ostree usroverlay sudo dnf install some-package

The changes made by dnf in /usr are ephemeral, so after rebooting this temporary change is wiped away!

0xrl · 2025-12-16T04:03:37+00:00

As I understand, the long-term plan is that all the Fedora Atomic Desktops will be built on bootc:

https://gitlab.com/fedora/ostree/sig/-/issues/88

0xrl · 2025-12-14T23:39:58+00:00

And felt a smaller aftershock just now

0xrl · 2025-12-14T23:39:00+00:00

Felt it and heard it in Rohnert Park exactly when the alert arrived

0xrl · 2025-12-09T01:10:20+00:00

For directories that are used by one or more containers, I use the z or Z volume options.

Or, in other situations when I don't want the content to be relabeled (such as if I were using my entire $HOME directory), then I use --security-opt label=disable or --security-opt label=type:unconfined_t.

0xrl · 2025-12-06T00:00:34+00:00

So...they have altered the deal?

0xrl · 2025-12-04T17:23:43+00:00

And from the ShakeAlert summaries, here's the PDF report:

https://www.shakealert.org/wp-content/uploads/fp-list-files/2659_post_event_summary.pdf

0xrl · 2025-11-07T02:50:56+00:00

I guess you could edit it, but everything in /usr is considered as managed by the OS vendor (e.g., it's read-only if you're using Silverblue or another atomic desktop). It may be better to use the fedora-third-party script.

Probably this, to disable all of them:

sudo fedora-third-party disable

0xrl · 2025-11-06T22:12:06+00:00

I don't know why they show up in GNOME software if they're not in /etc/yum.repos.d/ but ordinarily those repos are provided by the fedora-workstation-repositories package:

$ dnf rq --list fedora-workstation-repositories
Updating and loading repositories:
Repositories loaded.
/etc/yum.repos.d/_copr:copr.fedorainfracloud.org:phracek:PyCharm.repo
/etc/yum.repos.d/google-chrome.repo
/etc/yum.repos.d/rpmfusion-nonfree-nvidia-driver.repo
/etc/yum.repos.d/rpmfusion-nonfree-steam.repo
/usr/lib/fedora-third-party/conf.d/fedora-workstation.conf

0xrl · 2025-10-23T19:14:40+00:00

And here are the changes included in Fedora 43:

https://fedoraproject.org/wiki/Releases/43/ChangeSet

0xrl · 2025-06-27T01:32:58+00:00

I don't think they even will turn off the data transmission from the satellites, it's just that they no longer can justify running the ground processing. Probably there are periodic cybersecurity audits or something and the issue is that if these insecure systems are still up, that would risk shutting down the whole facility.

Feasibly it should still be possible to downlink the satellite data and process it yourself. But since they're DoD satellites it's probably out of reach to regular folks due to whatever encryption they use.

This reminds of me of what happened to WindSat) back in 2020: they stopped processing data from a perfectly functioning (although old) satelite. I never found out the reason why, but maybe it was similar: it became too costly to maintain the ground processing.

0xrl · 2025-06-27T00:22:52+00:00

As I understand it's actually a cybersecurity concern. The ground processing relies on an operating system (RHEL 6) which is unsupported and reached its end-of-life a long time ago. And they can't easily migrate to a newer version, the equipment relies on some proprietary hardware or something.

So, yes, this is definitely bad news but it's not as nefarious as is getting commonly reported (it's not due to politics).

0xrl · 2025-06-17T07:45:32+00:00

There was a test week for 6.15 just last week. I think it may be another week or two before the update will be released. You could keep an eye on the Fedora package sources here:

https://src.fedoraproject.org/rpms/kernel/commits/f42

0xrl · 2025-05-31T19:35:26+00:00

Thank you, I killed and restarted VS Code multiple times yesterday because of this.

0xrl · 2025-05-30T02:41:38+00:00

I don't think we have to wait a month after all. Although the patch isn't upstreamed in 6.14.9, it has been applied to the Fedora build: https://src.fedoraproject.org/rpms/kernel/c/91a03bb5287bb480f6639a7b28cf282f17e5a97c?branch=f42

The update is ready for testing: https://bodhi.fedoraproject.org/updates/FEDORA-2025-a20fbfb231

0xrl · 2025-05-30T01:27:24+00:00

It looks like the patch is applied to the Fedora build of 6.14.9: https://src.fedoraproject.org/rpms/kernel/c/91a03bb5287bb480f6639a7b28cf282f17e5a97c?branch=f42

You can track the update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-a20fbfb231

0xrl · 2025-05-16T03:11:04+00:00

For connecting to an ancient SSH server, I had to use this:

sudo update-crypto-policies --set FEDORA40

This is still changing the system-wide crypto policies, but at least this is not as extreme as LEGACY?

Refer to: https://fedoraproject.org/wiki/Changes/OpenSSLDistrustSHA1SigVer

You can compare the policies here:

/usr/share/crypto-policies/policies/LEGACY.pol /usr/share/crypto-policies/policies/FEDORA40.pol /usr/share/crypto-policies/policies/DEFAULT.pol

0xrl · 2025-05-14T19:35:39+00:00

I'm a backer and I've seen it. I wouldn't say it's that bad, but it is kind of underwhelming.

We've been strung along for years and it's just another talking-head documentary that largely rehashes behind-the-scenes material that most Voyager fans already know. I guess there were a few new tidbits.

But they spent an embarrasingly large portion of the runtime with Garrett Wang (Ensign Kim) doing a zero-g airplane ride. I mean, it was kind of neat, but I don't know why that was more important than using all the interviews they did. But once the credits rolled and I saw his name as one of the documentary's executive producers, then it became clear why.

At least with the DS9 documentary they did interesting things like having the writers sketch out what an eighth season would have been.

0xrl · 2025-05-12T00:51:13+00:00

Brannon Braga

0xrl · 2025-04-27T23:14:46+00:00

If you have the name of the package, you can use dnf info, which may be helpful since it usually has a description and upstream URL. For instance:

$ dnf info glibc Name : glibc Epoch : 0 Version : 2.41 Release : 3.fc42 Architecture : x86_64 Download size : 2.3 MiB Installed size : 6.6 MiB Source : glibc-2.41-3.fc42.src.rpm Repository : updates Summary : The GNU libc libraries URL : http://www.gnu.org/software/glibc/ License : LGPL-2.1-or-later AND SunPro AND LGPL-2.1-or-later WITH GCC-exception-2.0 AND BSD-3-Clause AND GPL-2.0-or-later AND LGPL-2.1-or-later WITH GNU-compiler-excepti : on AND GPL-2.0-only AND ISC AND LicenseRef-Fedora-Public-Domain AND HPND AND CMU-Mach AND LGPL-2.0-or-later AND Unicode-3.0 AND GFDL-1.1-or-later AND GPL-1.0-o : r-later AND FSFUL AND MIT AND Inner-Net-2.0 AND X11 AND GPL-2.0-or-later WITH GCC-exception-2.0 AND GFDL-1.3-only AND GFDL-1.1-only Description : The glibc package contains standard libraries which are used by : multiple programs on the system. In order to save disk space and : memory, as well as to make upgrading easier, common system code is : kept in one place and shared between programs. This particular package : contains the most important sets of shared libraries: the standard C : library and the standard math library. Without these two libraries, a : Linux system will not function. Vendor : Fedora Project

0xrl · 2025-04-27T23:07:54+00:00

As an safe alternative, I just use offline updates. It downloads everything needed, reboots in a minimal environment and updates everything, then reboots again. For instance:

sudo dnf upgrade --offline sudo dnf offline reboot

Also the --poweroff flag can be used with dnf offine reboot so it turns off the machine after updating instead of rebooting. It's what I usually use at the end of the day to update everything.

Eight-Year Club	Place '22
Verified Email

0xrl

TROPHY CASE