Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Tuesday July 11 2017, @12:50PM   Printer-friendly
from the open-sesame dept.

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.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by stormreaver on Wednesday July 12 2017, @02:25PM (2 children)

    by stormreaver (5101) on Wednesday July 12 2017, @02:25PM (#538101)

    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.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 2) by ledow on Wednesday July 12 2017, @02:42PM (1 child)

    by ledow (5567) on Wednesday July 12 2017, @02:42PM (#538112) Homepage

    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

      by stormreaver (5101) on Wednesday July 12 2017, @07:00PM (#538242)

      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.

      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.