Booting back and forth between Bazzite and Windows

Bazzite
1

On my system I have to enter BIOS and select the boot device priority (SSD/HDD) and then select a secondary priority (can’t remember the name) that tells it which SSD/HDD I want to boot from. I don’t want to do that every time I want to switch between Windows and Bazzite, so I’m looking into using bootnext to make a non-steam game I can select that will switch me back and forth.

Anyway, I’m looking at the install instructions for bootnext - and it says I need to place it in the PATH directory of my choosing. With Bazzite being immutable (still wrapping my head around what all that means) - do I need to have any worries about where I place it? I want to make sure it doesn’t get erased.

Thanks!

2

Also, is there a default password for the bazzite user? I’m starting by trying it out in /home/Bazzite since I see that is in the $PATH variable, but when I try to run sudo ./bootnext-linux-amd64 --list from there it is asking me for a password. I don’t think a password was ever set/prompted for during install - so I’m assuming there is a default password for the bazzite user?

Using the Nvidia HTPC beta image BTW

EDIT: It’s bazzite/bazzite

3

OMG, lol - What am I doing wrong here?

image
image1567×413 92 KB

EDIT: Seems that unlike on Windows, you don’t need to use the full name of the “exe” to run bootnext on linux. On linux, just use “bootnext”

Example:

bootnext --list
4

No. In Linux an executable has to be flagged as executable to be executable :grinning:. For example:

$ chmod a+x bootnext-linux-amd64
$ sudo ./bootnext-linux-amd64
1 Like
5

Huh, that’s interesting - just using bootnext does work, for whatever reason :thinking:. I didn’t have to chmod it. I assume that however bootnext works must have flagged that shot name somehow? I will try doing that to the full name though, but I ended up using bootnext in the sh script I added to Steam. I also didn’t realize before that /home is part of $path so I’m assuming that keeping it in /home/Bazzite is a safe location.

6

It just means there is another copy of bootnext installed in your PATH.

7

Ah ok. Is it preinstalled with Bazzite or something?

8

I don’t believe it is. You must have installed it yourself but are not aware. Try to remember :slightly_smiling_face:. You can check where it was installed by running:

$ which bootnext