Because the driver is the glue code between the device, and the operating system. What happens when the kernel changes, or needs to change? Then the driver on your devices don't match up with the kernel anymore. A lot of Windows folks think Windows has some sort of stable interface and that's why Windows is backwards compatible. But it's untrue, Windows has inbox drivers, just like Linux has driver's that build with the Kernel. Any driver that reaches inbox status get brought into the Windows source. As the Windows kernel changes, Microsoft engineers update all the inbox drivers to match the new kernel changes. When companies don't get their driver inbox'd, they are responsible for keeping up with the kernel changes. Some devices eventually get left behind.
I believe you. I know I'm stretching it here. Only because it's just not like Microsoft to allow their OEMs off the leash. It's not unlike Microsoft to bring the full force and weight of the legal system down on their partners. And we definitely know Microsoft wouldn't hesitate to tie another company up in court just the for the sake of draining them of their operating cash. I'm just thinking, maybe there is a way that these handhelds fit into the free Microsoft licensing. I mean, knowing Microsoft is just going to crack the whip, why even spend the engineering dollars supporting Linux hardware in the first place. Maybe to give them leverage against Microsoft I guess.
Looks like /u/Luma got you sorted. Awesome feature right? It's been there for a long as I can remember. This is the best part about Linux. People who use Linux created features that helped them solve problems or made their daily work easier. And you can do the same if you are feeling motivated one day.
That's what the tty is for, or at worst a bootable thumbdrive, CD, or Floppy. If I can't switch to a tty, I boot a bootable drive, mount my harddrive, and chroot my install. No second machine required. It's rare that I fuck something up though. Rest assured it was some bullshit I was trying, zero to do with Linux itself. But I do remember Windows would just bork itself randomly for no reason at all. I'm sure Microsoft has all that resolved now, but man back in the day it was painfully often.
You are. You are supposed pretend, everything you know on Windows should immediately transfer to Linux. Try to do techie things on Linux the Windows way; borking your system. Finally claim Linux isn't ready for the average user, despite not using Linux like an average user would.
I had figured that would be the case this time as well. There is no way Microsoft will let their OEMs off their leash if they can help it. At first I thought there was no way any Windows OEM would be allowed, SteamOS on their handheld officially supported, or even sold that way. But I learned recently, at BUILD 2014, Microsoft made Windows free for devices with screens 8" or less, mostly IoT. I think that would count for these handhelds as well. So I think this time will be different.
The way I understand the contracts you are mentioning, the deal is, they have to sell a Windows license with every PC they sell. When a company like Dell or Lenovo sell machines with Linux, it's usually in the 10,000 range, (at least that I can tell) which is something Dell or Lenovo can eat the cost of. Plus, most of the machines go to companies that already have Volume Licensing deals already, so basically the Windows Tax is paid for in some way already.
But I think this time will be different because there will be a ramp up of devices and competition in the handheld space where there is no Windows Tax required. Valve will surely release a Steam Console and that will probably become the new PS2/DVD player that everybody buys. When people are buying consoles instead of PCs, OEMs are already spending engineering dollars on Linux for the handheld market, and 3rd party software and devices are suddenly competing in the Linux space. It's a stretch, but I really think SteamOS is breaking the grip of Microsoft's vendor lock'in strategy and we are just seeing the very beginning stages with Windows OEMs officially supporting SteamOS.
I think setting expectations appropriately is a reasonable expectation of new users. Microsoft expects it of Windows users. Apple expects it of MacOS users. For Linux, nope, we must have a different standard. If we don't, Linux isn't ready for the average user. Got news for you, average users don't install Windows, they don't install MacOS, and they don't install Linux or any other OS. They buy pre-built machines where everything is taken care of. Average users buying pre-built machines do not experience the woes of a tech nerd.
100% agree. That is coming soon though. Microsoft has had vendor lock'in for the last 30 years which guaranteed engineering dollars (drivers, software, testing) spent by OEMs to support Windows. SteamOS is breaking the grip of Microsoft though. If Microsoft is too slow to react, SteamOS will become entrenched for gaming and that will guarantee engineering dollars are spent on SteamOS support (again, drivers, software, testing), which will upstream to Linux. At that point, 3rd party hardware, peripherals, and software will be targeting SteamOS and Linux. OEMs will have already spent engineering dollars to support their hardware in SteamOS (and Linux), so they wouldn't hesitate to start shipping Linux machines to the big box stores. It's Microsoft's market to lose though.
Imagine the hardware compatibility issues you'd have trying to install MacOS on your machine. Probably a nightmare. Better to just buy hardware that is compatible with the OS you want to run.
Shouldn't be any problems. I'd suggest rclone. Great tool. I use it to reliably and safely copy files from my cloud server block storage to two different blob storage locations. rlcone will do anything. A simple cp will probably get it all done for you too, but I don't know how important the data is to you.
But, I think you are looking for a CMS site that does stuff like Wordpress.
I stole this from Wikipedia
Based on a survey, the most widely used content management system is WordPress, used by 43.6% of the top 10 million websites as of October 2021. Other commonly used content management systems include Squarespace, Joomla, Shopify, and Wix.
Something else you can do. Install oh-my-bash or oh-my-zsh, either, with zoxide jump around. Any of the directories you visit are tracked and weighted with a frecency weighted value. Then all you need to do is type in parts of the name to go there.
For instance, if I had directories
~/code/dev_repo/project-one
~/code/dev_repo/project-two
~/code/dev_repo/project-three
Then you just type z dev one or z co re pro two You know, the parts of the directories you remember. The more you visit various directories and the more recent, the weighting is higher and the more likely you get the correct directory you want with even less and less characters. Also check out atuin it adds a fuzzy finding to your bash history or zsh history.
I've played WoW on Linux for twenty years. Blizzard has always said they unofficially support Linux. Occasionally the Blizzard launcher will have an issue, but Blizzard fixes it right away. All that to say, you should 100% have high expectation for WoW on Linux.
I use bottles to run Blizzard games with the latest Soda runtime. But as others mentioned, it's probably the integrated gpu that's getting selected. If you didn't use the automatic installer, (Lutris, bottles, etc., all have auto installers) for the blizzard launcher I'd suggest going back to that. But likely it's just the gpu selection.
Honestly I thought the Steam Machine V2 would drop this summer. It would really be a great time for it. Definitely take some pressure off Valve to release a Steam Deck 2. I'm holding off not building my own console just in case.
Yep, same here. Back in the day, I was upgrading my computer to win2k. There was nothing wrong with my computer, Windows was just a hog. I installed Slackware and everything was smooth and snappy. One of the things I remember, playing EverQuest on Windows, I had to use the base texture modes in the game. With Slackware, I could enable the new game textures and everything played great. That's one of the great things about Linux, you can always find a lower footprint distro.
but with Linux it’s more like, “hm, I bet I can figure this out.”
Just to piggy back on this. When I would use Windows, back in the day, I would get really frustrated that I couldn't do something I wanted. With Linux, there is always something you can do. If anything there is always the code I can take a look at. I need the OS to do the things I need and get the hell out of the way. On Windows, it will do the things you need, as well as things other people need, as well as things Microsoft wants that will help them make money off you; even though you've already paid.
It's not in the kernel. It just comes a long with the kernel. You can compile any of the drivers as modules. Back in the day when you had to fit your kernel and boot loader on a 1.44MB floppy. We would save space by compiling most of the drivers as modules and then they would get loaded into kernel space on boot. Now a days, a 100MB kernel is not a big deal when systems have Gigs of ram and harddrives are in the Terabytes. They keep the driver code with the kernel code mostly for the reasons that @dafta gave. When I was a Windows kernel dev for Intel, Microsoft did the same thing. That's how you get inbox drivers. As a Windows kernel dev for Intel, it was our goal to get our drivers inbox'd with Microsoft so their developers would be responsible for maintaining the driver code, as well as testing, when ever there were changes to the Kernel that affected drivers.
short answer: There is generic support already in the kernel. It's up to the game controller MFG to use that standard. Also, the generic controller standard probably doesn't support a lot of the new features, so it makes sense to have a driver to support the extra features of the controller.
Because the driver is the glue code between the device, and the operating system. What happens when the kernel changes, or needs to change? Then the driver on your devices don't match up with the kernel anymore. A lot of Windows folks think Windows has some sort of stable interface and that's why Windows is backwards compatible. But it's untrue, Windows has inbox drivers, just like Linux has driver's that build with the Kernel. Any driver that reaches inbox status get brought into the Windows source. As the Windows kernel changes, Microsoft engineers update all the inbox drivers to match the new kernel changes. When companies don't get their driver inbox'd, they are responsible for keeping up with the kernel changes. Some devices eventually get left behind.