SoylentNews is people
SoylentNews
Peter N. M. Hansteen walks through use of OpenBSD on a modern laptop in his latest blog post. While OpenBSD has a good reputation for servers and routers, many do not realize how well it works on laptops with supported hardware. He's been running it as the only OS on his laptops for well over a decade at this point and shares his experience with recent hardware. OpenBSD is clean, organized, and predictable. It does what you configure it to do, and only that, with no backtalk or second-guessing — like from other systems. Its documentation is second to none.
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Grelb's Reminder:
Eighty percent of all people consider themselves to be above
average drivers.
(Score: 2) by ledow on Tuesday July 11 2017, @07:42PM (3 children)
I deploy hundreds of machines a year. Would you like to know how many modern Windows installs / images I have? One. It was created from a standard install CD, hotfixes slipstreamed for convenience, and then a bunch of software installed (office, etc.). The image gets updated every year for convenience but otherwise it's the same image throughout the network, on every machine.
You push it to a machine over PXE, it boots, finds all drivers, works. I'm not suggesting we need a Linux Update site, but it works, because Windows Update just does that for you. I don't claim it'll pick up the latest nVidia drivers, but it works enough to get the computer going. The same is true of the same install CD but the reason I use PXE as an example is that it literally takes seconds to redeploy HUNDREDS of different machines, to a working config, with fully working drivers, no matter the underlying hardware. And I do that all day long. Literally, 1 image, 15 revisions over 3 years (mainly to update software, or put in some more Windows updates). There is precisely ONE device that needs an extraneous driver - an all-in-one PC that needs a decent driver to complete Windows setup from a network (i.e. NDIS2 driver) - on the entire network.
Sure, there's a device or two it doesn't like, or aren't optimal. But driver disks? Really? Not unless you're booting some server from a RAID that is unsupported in Windows Setup which is incredibly rare nowadays.
UEFI is a major complication - I understand that, and why that is, and I'm not saying it's anyone's fault on the open-source end. It's a tricky problem. But Windows setup hasn't had the problem you describe since Windows 7/8 either.
A regular user doesn't NEED to install Windows. It's done for them.
But a regular Linux / BSD user *does* need to install Windows. In fact, almost all of them. So it can't be done for them. So they need more help.
It's about raising the standard of experience, not "we can theoretically do what Windows does, that's good enough".
That said, I rolled out a bunch of VM's to a school full of pupils. To show them what real OS are like, how they are installed and deployed. Literally just put Windows 10 education ISO image into the HyperV VM and then let them access it on a locked-out network. They worked it out in seconds. These are kids that have NEVER installed an OS in their life. It's not that difficult. But even partitioning properly would be beyond them (fortunately Windows setup rarely cares!).
Try the same with Linux distros, it does NOT go as smoothly. I know. We did it. With the kids. The success rate wasn't high and they had all kinds of images available to them. That was without exotic hardware, dual-boot, or anything else.
To be honest, with the kids we tried it on, they ALL went to grab the mouse to select the initial (text mode) boot menu. That's a sign of the times.
Almost as bad as when we have a new intake being shown the computers for the first time, who are young enough to expect to just be able to prod the screen directly.
(Score: 2) by stormreaver on Wednesday July 12 2017, @02:25PM (2 children)
You completely ignored and mischaracterized the discussion. We're not talking about corporate installs or pre-installs, where there is an IT department to hold your hand. We're talking about consumer-level users who want to use a BSD or Linux desktop or laptop that isn't pre-installed with the same. We are also talking about the same level of user who needs to reinstall Windows because it did what Windows is want to do: puke all over itself.
1) BSD is usually a non-starter, because its consumer-level hardware support is abysmal. Even if its installer is on par with Kubuntu, there is a high degree of probability that the system just won't work for lack of device drivers.
2) Installing Windows is also a non-starter, because it's a scattered mess. Install device driver, reboot. Install the next device driver, reboot; ad. infinitum. The last Windows 7 install I did required five or six reboots for device drivers that Windows couldn't find.
3) A Kubuntu install asks a few simple questions, and then does everything else automatically. There is one reboot, after the install is finished, to get into the new system. Its built-in device driver support is excellent, and there is a high probability that everything will work right out of the box. The only exception to this I have had in the last five or six years has been with USB wireless adapters. There are several excellently supported ones, but it's not as care-free as the rest of the system.
4) You apparently misunderstood what I said about UEFI on a Kubuntu install. The installer handles UEFI just fine. When the installer detects that there is already a Kubuntu installed in BIOS mode, it pops up a too-verbose message which tells the user that a UEFI install over a BIOS install may render the BIOS install unbootable. That's the end of the UEFI complication, which is only such because the average user won't have a clue what that means. If it's a tricky problem, then the Kubuntu installer hides it wonderfully.
(Score: 2) by ledow on Wednesday July 12 2017, @02:42PM (1 child)
No I didn't.
1) Correct.
2) NOT CORRECT. If your PC boots into a Windows boot environment (bog-standard boot disk, OEM setup pre-installed on the machine, whatever), it will connect to Windows Update and get everything else it needs. HUNDREDS of different models / manufacturer of machines, each with all kinds of weird devices, standard Windows install (just the boot-disk drivers, and whatever it can get from the net) and it all just works, to the extent that the average home user would get things working enough to use the machine. The worst culprit is wifi drivers, but almost every device I've seen can load Ethernet drivers without a hitch to do this, and then work from there. Windows has this to the point where I don't EVER install a driver for a machine, whether brand-new out of the box, 2017 model, or re-imaged junk that's been in place for nearly a decade.
3) Somewhere in-between. Networking is generally good, wifi is generally much worse off (firmware etc. mainly), and other things are highly specific on models (e.g. some graphics cards take a LOT of messing to make work right, e.g. Intel/nVidia Optimus for many early models)
4) Such things are not in the realm of things that Kubuntu should be tinkering with, not in an environment where dual-boot is a possibility. Damn right it should be asking. A problem that you can't get around, I agree, but it's not something that should be hidden anyway.
(Score: 3, Interesting) by stormreaver on Wednesday July 12 2017, @07:00PM
In the decades in which I have had to install Windows, I have never, ever experienced this. It's how Microsoft would like the world to believe Windows installs work, but it's a lot like Bigfoot sightings: people claim to have seen it, but the pictures are always fake. In every single Windows install I have ever done (or even seen done), I have seen nothing but Windows failing to find drivers through Windows Update. I have always had to either hunt down the driver disk, or go to the manufacturer's Web site.
It's entirely possible that there is some obscure magical incancation that allows Windows to find drivers on Windows Update, but I have no idea what that might be. But having fought with the sadism of Windows for too many years, I stopped caring. Kubuntu installs have been so trivially simple for so long that I leave the Windows mess to the more masochistic crowd.