You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I set the hostname during the Aurora installation (on the network settings screen) it is still set to "fedora" when I reboot into the installed OS.
What did you expect to happen?
Hostname set during install keeps being set after I reboot.
Output of rpm-ostree status
No response
Output of groups
No response
Extra information or context
No response
The text was updated successfully, but these errors were encountered:
I've had a similar experience twice now (once without and once with LUKS encryption). I set a hostname during install both times but found hostnamectl reported no static hostname set, instead using my local IP address in kebab-case as an automatic name. That bit's easy to fix with sudo hostnamectl hostname <name> but it still leaves the aurora-dx "device" in Dolphin named with the IP address. Is there any way to correct that? I'm new to Aurora/Bluefin, coming from a primarily Arch and NixOS background, so still finding my feet here... It's otherwise great so far though, so kudos everyone!
...it still leaves the aurora-dx "device" in Dolphin named with the IP address. Is there any way to correct that?
Probably should've done some digging first... I was seeing the BTRFS volume label in Dolphin (duh), and AFAIK the "right" way to change that is by running sudo btrfs filesystem label / aurora-dx_$(hostname). It reflected in Dolphin immediately for me, and didn't affect my LUKS encryption (which I'm quite new to) or the related TPM unlock. I figured I'd share in case it was bothering anyone else! 😄
Describe the bug
When I set the hostname during the Aurora installation (on the network settings screen) it is still set to "fedora" when I reboot into the installed OS.
What did you expect to happen?
Hostname set during install keeps being set after I reboot.
Output of
rpm-ostree status
No response
Output of
groups
No response
Extra information or context
No response
The text was updated successfully, but these errors were encountered: