After doing a fresh install of Silverblue and running “rpm-ostree upgrade”
the installed kernel is named archlinux maybe it should be named something else it’s a bit missleading as in the terminal I now see username@archlinux instead of username@fedora which is what the system originally had when installed.
output of uname -a cmd:
“Linux archlinux 6.1.9-200.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Feb 2 00:21:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux”
Hi,
I just completed rpm-ostree update
from
rpm-ostree status
State: idle
Deployments:
● fedora:fedora/37/x86_64/silverblue
Version: 37.20230205.0 (2023-02-05T00:43:31Z)
BaseCommit: 0c6c7982a70b6fec67b9d51c1676f13f86605570f8333ff2f48fa2d0d56a8f47
GPGSignature: Valid signature by ACB5EE4E831C74BB7C168D27F55AD3FB5323552A
LayeredPackages: langpacks-en
fedora:fedora/37/x86_64/silverblue
Version: 37.20230115.0 (2023-01-15T00:45:42Z)
BaseCommit: a5f26673e144d96f00a38f1a36eb7cfd20e46fdb7ecc33ad6183923a8cf37483
GPGSignature: Valid signature by ACB5EE4E831C74BB7C168D27F55AD3FB5323552A
LayeredPackages: langpacks-en
[fcc@fedora ~]$ uname -a
Linux fedora 6.1.9-200.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Feb 2 00:21:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
You can notice my uname -a
is “Linux fedora”, which “fedora” is actually my hostname - which yours is “archlinux” .
Please try change your hostname and run uname -a
again.
Do you have a host name assigned in a dhcp server (on your home router, for example)?
(Note that this isn’t the kernel name.)
1 Like
Ah, I did have archlinux installed before I installed this and yes the router would have kept the hostname, thanks this is likely the case.
3 Likes
hostnamectl set-hostname "ohyeah"
hostnamectl
ohyeah
uname -a
Linux ohyeah 6.1.8-200.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Tue Jan 24 20:32:16 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
1 Like