Could be you need to set boot partition EFI in BIOS, or could be a recovery partition messing things up for you
- 0 Posts
- 18 Comments
I had no issue with HP, even with secure boot. Just had to pick boot order in BIOS
Gnome has touchscreen in mind, but you can totally use its hotkey system and navigate much quicker than point and click functions in Windows. Its a simple DE that gets out of your way to focus on your task, whenever I go back to Windows for work I’m frustrated by all the nonsense
Gnome is different and at first I was lost, but after figuring out the basics is amazingly well integrated and just works as expected. KDE is super configurable but always feels a little off in a hard to describe way, like little quirks or lags or other papercuts.
The repos have a lot of stuff, but if you ever get stuck for q package you can install debs with alien command, or find community repoes here https://software.opensuse.org/ They typically offer 1 click installs, or direct rpm downloads
OpenSUSE TUMBLEWEED, always updating, but they have an OpenQA tool that checks the builds for success, and if for some reason something did go bad you just reboot and pick the previous (automatic) snapshot. Lots of GUI tools to manage the system and packages via the various Yast2-GUI apps.
Well that’s part of Hollywood schlockbusters, just cater to the masses. Anything slower than continuous action and majority of movie goers can’t stay focused. So the film becomes a garbage Coles notes version. You don’t need full on time frame to capture the essence, and if it really does then it should have been a series not a film.
Often its not about what you had in your head (like how you pictured the character, etc) but the premise and obviously depth of the book is lost.
Was it a movie first then the book adapted from the screenplay? I read one like that before, it was just the movie written down
Yes, its really good, and every time somebody say “Linux needs ____ to make its use easy for new comers”. My answer is typically uhm, openSUSE already has it.
That can be:
- OneClick installs
- GUI package management
- GUI service and system settings
- auto cleaning of btrfs
OpenSUSE, you can rollback your OS if an update, or your own mistake, borks it. GUI interface for a lot of stuff. It defaults to enforcing Secure Linux these days. This is a good thing but means extra steps if you want to access certain things remotely, so you can set it to complain or off, instead of the enforcing setting.
BCsven@lemmy.cato Lemmy Shitpost@lemmy.world•What sort of grill needs a firmware update lol0·9 days agoIf you are into that: then tplink kasa switches and plugs can be reconfigured via hs100 app on git hub, so that they only look local and don’t try to reach out to a remote server. You can use the app to connect them to your local WiFi. Then you can control them via home assistant locally (or remotely) and not rely on a corporate server and android app for use
BCsven@lemmy.cato Lemmy Shitpost@lemmy.world•What sort of grill needs a firmware update lol0·9 days agoWhen you want to intergrate your smoker into homeassitant so you can adjust it from the office.
OpenSUSE has OneClick install for RPMs. https://en.opensuse.org/openSUSE:One_Click_Install
Edit: and if you happen to download an rpm, you just double click it in the filemanager (or single click if that is your setting) and it launces the install GUI.
Its similar to how MSI file install looks…just next next finish kind of thing
BCsven@lemmy.cato Linux@lemmy.ml•According to Pornhub data (yes seriously!) Linux market share in 2024 increased more than 40% relative to 5.1% of all users.2·16 days agoNot what the distro meant by release
BCsven@lemmy.cato Linux@lemmy.ml•Killing an application in a terminal has a different effect than killing it in the UI. Help?0·1 year agoClosing from the X icon on the app window lets the program write out any info it needs to before shutdown. Killing the process from the terminal just ends the process totally
Do you know if you installed in legacy BIOS or EFI mode? If its EFI then most BIOS screens have a method to then pick the actual EFI entry (if the bootup discovers more than one) and you can then set it to boot Linux (and hopefully your Linux install did a probe OS and chainloaded to your Windows Boot). I had this issue before.
I also had an HP recovery partition getting invoked every time windows booted and detected change. The remedy wiping the drive to her ride of that stupid partition