Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[main] Improve modules/ROOT/pages/update-streams.adoc (how to check current stream ?) #704

Open
udf2457 opened this issue Feb 9, 2025 · 4 comments

Comments

@udf2457
Copy link

udf2457 commented Feb 9, 2025

At present the docs cover:

  • What streams are available
  • Switching between streams.

However the docs do not cover how to check what stream you are currently on.

As a CoreOS noob, this sort of thing could be quite useful. Otherwise I have to resort to $search_engine to find out how.

@udf2457 udf2457 changed the title [main] Improve modules/ROOT/pages/update-streams.adoc [main] Improve modules/ROOT/pages/update-streams.adoc (how to check current stream ?) Feb 9, 2025
@hrismarin
Copy link
Contributor

The os-release file in the /etc directory is a text file that contains information about the Linux-based operating system (OS). It provides essential details such as the OS name, version, and other system-related identifiers. Reading this file, e.g. cat /etc/os-release will display the Fedora CoreOS stream in the RELEASE_TYPE identification parameter.

Since this is not specific to Fedora CoreOS, I'm not sure if such an instruction would be relevant to include on this particular page.

@udf2457
Copy link
Author

udf2457 commented Feb 12, 2025

Fair enough, for some reason it did not occur to me to check /etc/os-release I just assumed the stream detail was hidden elsewhere.

@dustymabe
Copy link
Member

However the docs do not cover how to check what stream you are currently on.

Right now I would just tell someone to run rpm-ostree status:

core@localhost:~$ rpm-ostree status 
State: idle
AutomaticUpdatesDriver: Zincati
  DriverState: active; periodically polling for updates (last checked Wed 2025-02-12 14:20:42 UTC)
Deployments:
● fedora:fedora/aarch64/coreos/testing
                  Version: 41.20250130.2.0 (2025-01-31T22:06:10Z)
                   Commit: dd57816f8920bec00095f3f867a56a06f1af1f803736bc95f3a0ecdbfa386a68
             GPGSignature: Valid signature by 466CF2D8B60BC3057AA9453ED0622462E99D6AD1

  fedora:fedora/aarch64/coreos/testing
                  Version: 41.20250117.2.0 (2025-01-21T02:05:34Z)
                   Commit: 28f861b1b540f004b4892bb69563bb4fceebd7405d50ab9d5754bc6aa0f526bc
             GPGSignature: Valid signature by 466CF2D8B60BC3057AA9453ED0622462E99D6AD1

which shows (in this example): fedora/aarch64/coreos/testing

I guess we could add something like that to the docs?

@hrismarin
Copy link
Contributor

I guess we could add something like that to the docs?

I can open a PR to include both commands with a brief explanation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants