SteamOS has the root filesystem set to read only, this is because of the way the system gets updated, and also makes it sure that every deck is running the same system. So you can’t change system configs or install things on the system. You can get around these by installing things for your user and creating services for your user. It’s doable if you want a gaming device that you use for some other things, but it’s not very convenient for a day-to-day drive.
I’ve ran into it, and it’s very slightly off-putting. At the same time, I fully understand why they’ve done it that way, and actually agree with them. The use of flat packs as an alternative makes the problem irrelevant. They maximised openness, while also protecting it from being completely borked up by a newb running random commands.
Maybe it’s about the ‘mostly read only’? That’s the only thing I don’t get.
SteamOS has the root filesystem set to read only, this is because of the way the system gets updated, and also makes it sure that every deck is running the same system. So you can’t change system configs or install things on the system. You can get around these by installing things for your user and creating services for your user. It’s doable if you want a gaming device that you use for some other things, but it’s not very convenient for a day-to-day drive.
I’ve ran into it, and it’s very slightly off-putting. At the same time, I fully understand why they’ve done it that way, and actually agree with them. The use of flat packs as an alternative makes the problem irrelevant. They maximised openness, while also protecting it from being completely borked up by a newb running random commands.