The weird Hewlett Packard FreeDOS option(blog.tmm.cx)
blog.tmm.cx
The weird Hewlett Packard FreeDOS option
https://blog.tmm.cx/2022/05/15/the-very-weird-hewlett-packard-freedos-option/
155 comments
Also, don't forget the Minix running inside a small embedded processor inside your processor or platform controller.
I occasionally wonder what an operating system running below ring 0 would be used for. I haven't thought of anything compelling, apart from being a backdoor.
The SIM card in your mobile telephone is doing that right now.
You are correct - it is basically used as a back door.
You are correct - it is basically used as a back door.
Usually when I hear people talk about backdooring it's usually on the network stack. On a phone that would be a modem.
Most devices, even in your computer (eg: laptop battery) run an OS. There's a good talk somewhere on how we've lost our way with OS design and now need to write an OS that looks at a single machine as a distributed system.
Most devices, even in your computer (eg: laptop battery) run an OS. There's a good talk somewhere on how we've lost our way with OS design and now need to write an OS that looks at a single machine as a distributed system.
Is it this one?
https://www.youtube.com/watch?v=36myc8wQhLo
USENIX ATC '21/OSDI '21 Joint Keynote Address-It's Time for Operating Systems to Rediscover Hardware
Edit or this one (not a talk but a paper)?
https://www.usenix.org/system/files/osdi18-shan.pdf
LegoOS: A Disseminated, Distributed OS for Hardware Resource Disaggregation ... We propose a new OS model called the splitkernel to manage disaggregated systems. Splitkernel disseminates traditional OS functionalities into loosely-coupled mon- itors, each of which runs on and manages a hardware component
https://www.youtube.com/watch?v=36myc8wQhLo
USENIX ATC '21/OSDI '21 Joint Keynote Address-It's Time for Operating Systems to Rediscover Hardware
Edit or this one (not a talk but a paper)?
https://www.usenix.org/system/files/osdi18-shan.pdf
LegoOS: A Disseminated, Distributed OS for Hardware Resource Disaggregation ... We propose a new OS model called the splitkernel to manage disaggregated systems. Splitkernel disseminates traditional OS functionalities into loosely-coupled mon- itors, each of which runs on and manages a hardware component
Similar enough! The one that I'm thinking of was the only actual non Linux talk (and really, OS development talk) at a OS Dev conference.
Some batteries have an entire stm32 series microcontroller in them, I've seen battery controllers that are actually the same "CPU" as on a discrete single motor quadcopter ESC.
Apple's laptop batteries in 2008 MacBook models have an independent microcontroller in them, which enables apple to manage it at a much more advanced level.
That generation of laptops can detect a problem with the battery much earlier (e.g. It can warn the user a year before the battery starts to swell. Been there, seen that). This knowledge is the basis of apple's battery technology that we see on their mobiles (iOS and macOS) today.
IIRC the password on these things were set to a default one and a PoC exploit was written for that platform.
That generation of laptops can detect a problem with the battery much earlier (e.g. It can warn the user a year before the battery starts to swell. Been there, seen that). This knowledge is the basis of apple's battery technology that we see on their mobiles (iOS and macOS) today.
IIRC the password on these things were set to a default one and a PoC exploit was written for that platform.
IBM PC keyboard from 1981 (and all later external PC & Mac keyboards) have an independent microcontroller.
https://en.wikipedia.org/wiki/Intel_MCS-48#Uses
https://en.wikipedia.org/wiki/Intel_MCS-48#Uses
MicroSD cards have a fully functional 32-bit microcontroller in them, it manages the write leveling and bad sector mitigation, but it's a fully fledged CPU otherwise.
And, there's a couple of great write-ups about them [0][1].
[0]: https://www.bunniestudios.com/blog/?p=3554
[1]: https://i.blackhat.com/us-18/Wed-August-8/us-18-Valadon-Reve...
[0]: https://www.bunniestudios.com/blog/?p=3554
[1]: https://i.blackhat.com/us-18/Wed-August-8/us-18-Valadon-Reve...
> and now need to write an OS that looks at a single machine as a distributed system
Exactly, currently they are too easily exploitable because they are not joined up.
You see it with gpu's being hacked and the OS not recognising this.
Exactly, currently they are too easily exploitable because they are not joined up.
You see it with gpu's being hacked and the OS not recognising this.
And the radio baseband firmware, what the hell is going on in there is likely known only to Qualcomm and the nsa.
Even when sending encrypted texts with Signal, I can't help but wonder if the keyboard software is sending everything to a government entity. Or, if a piece of hardware can silently grab screenshots.
Supposedly, it’s for low level system management functions. As in, stuff that could be done in hardware, but doing it in software is easier. Kindof like System Management Mode (SMM), but even lower.
ring -1 is canonically the hypervisor, so you could probably count hyper-v or xen or esxi as operating systems
I am sure they will soon find a way to add a hypervisor to Minix so they can add yet another layer to the mix.
That'd be fun. Intel would be providing services to customers for running their own spy platform on any supported Intel processor.
Not unlike "Other OS" on PS3. Same theory, different application.
Not unlike "Other OS" on PS3. Same theory, different application.
It's Minixes all the way down, man.
[deleted]
Possibly relevant: an NES emulator for UEFI: https://www.youtube.com/watch?v=-Juc1LT7Xls
[deleted]
I’m guessing they’re doing this because modern x86 processors can’t boot into BIOS mode anymore (edit: untrue, see reply by dmitrygr). This makes me wonder why they’re even offering FreeDOS as an option when they offer Linux for customers who don’t wish to purchase a Windows license. Maybe they have some sort of contractual obligation with a large customer?
> modern x86 processors can’t boot into BIOS mode anymore
This is false. They still can and happily will. Issue is more about vendor not shipping a CSM image. A modern x86 processor will happily run real DOS just fine.
This is false. They still can and happily will. Issue is more about vendor not shipping a CSM image. A modern x86 processor will happily run real DOS just fine.
Thank you for the correction! I saw multiple news articles several years ago saying that Intel would be dropping support for BIOS mode by the end of 2020, but it appears they've been dragging their feet. In the meantime, they seem to have been making moves in other ways, such as not supporting BIOS mode when booting with integrated graphics on 11th gen processors ( https://www.asus.com/us/support/FAQ/1045467 ).
You might get this all the time, but I saw your username and thought no way that's the old palm guy. But I clicked on your profile, and you are the old palm guy!
I used your apps back when I had a Tungsten T5, and Treo 680. :)
I used your apps back when I had a Tungsten T5, and Treo 680. :)
This is the most incredible thing I've ever read. I'm astounded at the level of work you've put into this.
Amazing read, thank you Dmitry. One typo for pedantry's sake? This:
> It as possible, but not documented.
Should probably be:
> It [is|was] possible, but not documented.
> It as possible, but not documented.
Should probably be:
> It [is|was] possible, but not documented.
Intel's been threatening to cut off everything non UEFI for a while... I think I read the iGPU in Alder Lake doesn't work unless you're running UEFI?
It might not have happened yet, but it seems inevitable.
It might not have happened yet, but it seems inevitable.
That's probably because it doesn't have a traditional VBIOS.
...which makes me wonder whether it's possible for the community to write one, given how much docs and source code Intel have released for their GPUs. Of course, how VGA-compatible it is is another thing to consider.
...which makes me wonder whether it's possible for the community to write one, given how much docs and source code Intel have released for their GPUs. Of course, how VGA-compatible it is is another thing to consider.
That depends on what one means by "booting into BIOS mode". CSM is a shim than makes UEFI firmware look like BIOS to the OS (or, well, bootloader) and to x86 code in various option ROMs, so you are always booting into UEFI.
Really booting without UEFI being involved in the process would require completely different firmware image.
Really booting without UEFI being involved in the process would require completely different firmware image.
The big market for this is K-12 schools.
Microsoft has a licensing program for .edu that doesn’t require an “embedded” hardware license. There are also many places using Neverware to provide Chrome desktops while using the some warranty services, etc that they have with PCs.
If you buy alot of computers, you can get desktops crazy cheap. Big enterprise buyers get low-spec desktops for ~$225 without windows or $300 with. If you don’t care about power/footprint, they are the best value thin client. Schools are huge PC buyers, some districts have >300k students, so you’re easily talking 40-70k PCs annually.
Microsoft has a licensing program for .edu that doesn’t require an “embedded” hardware license. There are also many places using Neverware to provide Chrome desktops while using the some warranty services, etc that they have with PCs.
If you buy alot of computers, you can get desktops crazy cheap. Big enterprise buyers get low-spec desktops for ~$225 without windows or $300 with. If you don’t care about power/footprint, they are the best value thin client. Schools are huge PC buyers, some districts have >300k students, so you’re easily talking 40-70k PCs annually.
Ok, but why the hell FreeDOS?
Why FreeDOS vs nothing or why FreeDOS vs Linux?
The former, because some OEMs have agreements with Microsoft that prohibit shipping systems without an OS. They found the loophole that they could ship a free OS as a placeholder.
Why not Linux? I guess it was easier at the time and they then just kept shipping what was already working. It was never intended to keep the original OS anyway (and in particular, Linux users tend to be opinionated and install their favorite distro anyway).
I suspect it's more bland than that, they need to be able to have a booting/working system otherwise the customer is going to call up support and say their computer isn't booting or that it's saying "no OS found" type messages. It's just to cover themselves, that's why they include enough Linux to be able to load a PDF reader. It should be easy enough to do d:\setup.exe with a USB that has a Windows installer on it, with this setup.
Windows installers are bootable these days (from DVD or USB; doesn’t matter); they haven’t been runnable from DOS for a couple decades now.
At any rate, even if you did find some OS you could install from DOS, you’d be installing it into the QEMU image if you installed from FreeDOS on a system with this arrangement. There’s no way to get back to the bare metal hardware from FreeDOS here.
At any rate, even if you did find some OS you could install from DOS, you’d be installing it into the QEMU image if you installed from FreeDOS on a system with this arrangement. There’s no way to get back to the bare metal hardware from FreeDOS here.
Yeah, but why not have something that just uefi boots into a barebones grub2 and then cli only debian-stable and bash shell?
Forget the DOS part.
Forget the DOS part.
It's probably more like they have DOS support contracted out to some vendor. And when the systems upgraded to the point of not being able to run DOS natively the vendor built this franken-OS to fulfill the contract.
Renegotiating the contract to something sensible like "don't run DOS anymore" was probably hopeless in the face of the bureaucracy, or risked losing to contact.
Renegotiating the contract to something sensible like "don't run DOS anymore" was probably hopeless in the face of the bureaucracy, or risked losing to contact.
Maybe it is for customers running weird old legacy hardware (e.g., lab devices, manufacturing, that only runs on DOS).
Weird old legacy hardware that only runs on DOS generally requires real-time access to stuff like ISA cards or parallel/serial ports, so this wouldn't work for that use case since the computer doesn't have any of those.
I have a weird old nylon cutting machine connected to a DOS machine over a serial port. It would not work with a USB/RS-232 adaptor?
USB-serial conversion would add a measurable amount of latency, and the access to USB hardware would occur under a non-real-time OS. Whether the setup "works" would be highly hardware-specific. There are modern industrial "PC" boards that are essentially a i586 implementation in a SoC and can run these workloads far more reliably, while consuming a lot less power compared to old x86 hardware. (They're also of interest to retrocomputing enthusiasts, for largely the same reasons.)
It probably won't if they do weird things with the flow control pins or if the timing really matters, but serial is far more likely than parallel to keep working.
Yeah this is why industrial PCs still have those physical ports.
Depends on the adaptor too. Cheap ones only have Rx and TX pins . The rest of the pins are not connected. If your device only used Rx and Tx it would work fine . If it uses functionality of other pins make sure you get the right adaptor
Spend no less than $20 on a USB to serial converter and you'd probably be fine. Anything with an FTDI chip in it are the best. Anything with a Prolific chip has a good possibility of being counterfeit will either not work well or the legit driver will try to brick it.
FTDI pushed driver updates that bricked counterfeits... https://www.theregister.com/2016/01/31/ftdi_accused_of_brick...
That's orecisely how we run our thread 3D printer. It even has a serial (UART) to USB chip on board and it's connected to a RPi3 boc running Linux and Octoprint.
[deleted]
No, the FreeDOS HP option has always been used by the customers who did not want to pay a Windows license, because they wanted to install a different operating system, usually some Linux variant (the option to install a pirated Windows variant was also popular in some parts of the world).
Dell has the Ubuntu option for many computers, but for those who do not want to use Ubuntu, like myself, there is no difference between the Dell Ubuntu option and the HP FreeDOS option, because such customers will always install their own preferred OS, immediately after the purchase of a new computer.
Dell has the Ubuntu option for many computers, but for those who do not want to use Ubuntu, like myself, there is no difference between the Dell Ubuntu option and the HP FreeDOS option, because such customers will always install their own preferred OS, immediately after the purchase of a new computer.
I'm the author of the article; It's not actually usable for that. The way the Qemu VM is setup there is no way to interface with the outside world at all. The only way to get any data in or out of that VM is through the keyboard and screen.
Would those apps work inside QEMU though? Is it configured to properly pass through the parallel port?
Maybe, but wouldn’t the customer have to know how to run QEMU? I am imagining a customer who wants to just replace an old machine while changing as little as possible.
Since this install is based on QEMU running in Linux, it would not meet that need.
The end user need not know it is QEMU atop Linux. They see and use DOS.
Yes, but inside a VM. What access to real hardware (e.g. to communicate with the outside world) does the user get?
Highly unlikely, without really messing around with it.
FreeDOS is known to not run well inside of virtualization. A proper host install would be far more capable.
That is not true.
In fact, if you just boot FreeDOS 1.3 in VirtualBox, you'll see it detect the virtual NIC, load a TCP/IP stack and acquire an IPv4 address, then report it.
It is mostly developed and run inside VMs these days, AFAICS.
In fact, if you just boot FreeDOS 1.3 in VirtualBox, you'll see it detect the virtual NIC, load a TCP/IP stack and acquire an IPv4 address, then report it.
It is mostly developed and run inside VMs these days, AFAICS.
But a proper host install is not possible on modern hardware.
Hypothetically if you wanted to use something like FreeBSD, Dragonfly BSD or maybe OpenSolaris? This is a big reach.
And I guess FreeDOS doesn't support booting by UEFI as well
(I mean, can it even?)
(I mean, can it even?)
It would involve essentially reinventing UEFI CSM as part of this hypotetical UEFI FreeDOS.
"FreeDOS assumes a BIOS, and does not work with UEFI."[0]
[0]http://wiki.freedos.org/wiki/index.php/UEFI
[0]http://wiki.freedos.org/wiki/index.php/UEFI
Knowing how big corporations usually work, dropping the FreeDOS option completely due to incompatibility would require approvals from 7 layers of corporate management, while shipping a half-assed version that is not usable for any practical purposes only took one nerd from engineering.
I can't find a source for it, but my recollection is that MS considers selling a PC with no operating system as encouraging piracy of Windows.
So I suspect this option is either due to an agreement with MS, or an overly cautious legal department.
So I suspect this option is either due to an agreement with MS, or an overly cautious legal department.
You're probably thinking about the agreement MS had with PC manufacturers that required them to pay for a copy of DOS regardless of whether the computer they sold had a copy of DOS or not. MS was barred from using that method in 1994.
https://www.justice.gov/atr/competitive-impact-statement-us-...
https://www.justice.gov/atr/competitive-impact-statement-us-...
But customers can also order this laptop with Ubuntu preinstalled. Why offer both Ubuntu and FreeDOS, especially if the latter is just running inside of a Linux VM anyway?
When I last ordered from HP, many laptops did not have Linux as an option (mine did not, so I bought the FreeDOS version)
Well that's also weird! Why are both options available on some computers, while others only have FreeDOS, even when they can't actually run FreeDOS.
My guess is that those computers are missing Linux drivers for modern devices like a camera or fingerprint scanner or something. Those wouldn't be expected to be supported in FreeDOS, but would be in Linux.
It ran FreeDOS just fine (and indeed runs Linux just fine for me), presumably they didn't want to QA that model with Linux.
Some countries have consumer protection laws that require that a factory-assembled computer must come with an OS. This whole FreeDOS thing feels like malicious compliance to me just to have something so it doesn't boot into a BIOS error.
Though I've assumed that FreeDOS runs on bare metal. This whole Linux-with-a-VM feels strange, to say the least.
Though I've assumed that FreeDOS runs on bare metal. This whole Linux-with-a-VM feels strange, to say the least.
It's not malicious compliance. It's for power-users who already own or don't want to own a copy of Windows. It's a good thing that we (where I live) fought hard for - fortunately here it wasn't about laws but only about available options, so lobbying the vendors and sellers was enough.
But they also offer Linux. In fact they already ship you Linux when you order the FreeDOS option. Why the extra effort?
Some countries also prohibit selling laptops without any OSs because they're unusable in that way, so this is a way to sell a technically "fully usable laptop" for people who'll install linux anyway.
which leaves the question of why going through the hassle of creating this mess instead of just Linux.
Because they they have to support that linux distro, with all the drivers, update etc.,...
And the FreeDOS just works. Doesn't do much, but what it does, it does well.
And the FreeDOS just works. Doesn't do much, but what it does, it does well.
No they don't. They could just start the debian distro without network configuration and gui and end up with a shell, with a MOTD saying this is just a base distro and a full reinstall to a supported OS is advised before connecting it to a network.
I guess they only do that because the FreeDOS name does not frighten the average tech guy who only used microsoft products as much as linux.
I guess they only do that because the FreeDOS name does not frighten the average tech guy who only used microsoft products as much as linux.
but the Linux they are shipping underneath that FreeDOS also works. And they also offer Linux preinstalled, so they need to "support" that to whatever amount anyways.
They probably only support the FreeDOS, not the underlying distribution. If you mess with the Linux and break the FreeDOS, that's on you. They might have 2 customers running some 40 year old legacy DOS app but 99% of people selecting the FreeDOS option are wiping it to install something else, so using it unsupported.
The pre-installed Linux works, but it doesn't have to work for all the driver and functionality edge cases that a real FreeDOS machine would definitely not support.
According to the article, they already do have a Linux option.
I’d wager the FreeDOS is a legacy option because they’ve supported it in the past an figures have shown it sells. Even if those figures don’t take into account how many of those legacy FreeDOS installs were for other alternative OS like Linux (though it could also be BSD, Haiku, Illumos, ReactOS or others).
Or there genuinely might still be FreeDOS users out there. Eg running industrial applications. Though I’d wager they’d be more likely to run DosBox and not on laptops either. But “industrial applications” covers such a wide spectrum of uses so never say never.
I’d wager the FreeDOS is a legacy option because they’ve supported it in the past an figures have shown it sells. Even if those figures don’t take into account how many of those legacy FreeDOS installs were for other alternative OS like Linux (though it could also be BSD, Haiku, Illumos, ReactOS or others).
Or there genuinely might still be FreeDOS users out there. Eg running industrial applications. Though I’d wager they’d be more likely to run DosBox and not on laptops either. But “industrial applications” covers such a wide spectrum of uses so never say never.
Many industrial users are not price sensitive. Having the keyboard, monitor, and computer in a single housing with a built-in UPS all in a compact device with a single power cord is a big selling point.
> Industrial users are not price sensitive
That's not a universal truth. I've worked with plenty who are.
> Having the keyboard, monitor, and computer in a single housing with a built-in UPS all in a compact device with a single power cord is a big selling point.
That's not a universal truth either. Sometimes the device will be a headless controller. In which case a laptop wouldn't always the right form factor. There might be additional hardware that needs supporting, which can be much more complicated with laptops. There might be other requirements (eg environmental constraints) too.
"Industrial" covers a pretty large spectrum of use cases.
That's not a universal truth. I've worked with plenty who are.
> Having the keyboard, monitor, and computer in a single housing with a built-in UPS all in a compact device with a single power cord is a big selling point.
That's not a universal truth either. Sometimes the device will be a headless controller. In which case a laptop wouldn't always the right form factor. There might be additional hardware that needs supporting, which can be much more complicated with laptops. There might be other requirements (eg environmental constraints) too.
"Industrial" covers a pretty large spectrum of use cases.
Thank you, I've clarified the comment by adding the word "many". It is a generalization, that holds in many but not all cases.
Indeed, but isn’t that literally what I said in my original comment?
I was emphasizing the utility of having the entire system packaged as a single unit (a laptop) for these clients.
But if you use DOS still for industrial stuff you usually do it because you need some old-fashioned interface (i.e. real serial or parallel ports are the usual example). Which is going to work great from inside a VM, not.
If you need real, physical RS-232, rs-422, rs-485, CANbus, 2wire, or parallel ports you're not buying a mass market modern laptop either.
Having worked in this world, I have sometimes patched DOSBox to communicate with all types of extravagant hardware, even ISA cards (look hard enough and you'll find even Core motherboards with ISA slots...).
Sure, but you presumably don't buy FreeDOS in a VM off-the-shelf for that, but setup the specific right thing for your use cases.
Recipients of Linux machines might expect them to perform all their functions well, whereas there is no such expectation with FreeDOS.
So while they offer Ubuntu on a limited set of machines, perhaps this emulated approach allows them to effortlessly ship neither-Windows-nor-Ubuntu option to everyone to guide their development/marketing effort (learn if people are happy with Ubuntu/Windows options).
So while they offer Ubuntu on a limited set of machines, perhaps this emulated approach allows them to effortlessly ship neither-Windows-nor-Ubuntu option to everyone to guide their development/marketing effort (learn if people are happy with Ubuntu/Windows options).
I dual-boot in my computers, because for some things live video games (and some software) I prefer Windows, while for coding or using a remote console I prefer Ubuntu. So I always try to split the hard disk in half and install Ubuntu in raw hardware.
My (relatively new) HP Spectre x360 only got sound working until Ubuntu 22.04 was launched. This is one year after the hardware was launched. I spent some months using Ubuntu without having sound, unless I plugged my USB headphones.
My previous laptop, Dell Inspiron 7375 with an AMD Ryzen 5 2500U CPU, did not even properly boot into Linux until Ubuntu 22.04 was launched. The best I could manage was make it boot it with some MMU kernel parameter, and it worked for half an hour until it froze. And it always froze with Ubuntu 18.04. It is a computer from 2018, so it was four years without me being able to natively run Linux in it. I had to use a virtual machine during these years =(
So, there's a lot of work either by the community or by the vendor to make Linux work in some hardware.
My (relatively new) HP Spectre x360 only got sound working until Ubuntu 22.04 was launched. This is one year after the hardware was launched. I spent some months using Ubuntu without having sound, unless I plugged my USB headphones.
My previous laptop, Dell Inspiron 7375 with an AMD Ryzen 5 2500U CPU, did not even properly boot into Linux until Ubuntu 22.04 was launched. The best I could manage was make it boot it with some MMU kernel parameter, and it worked for half an hour until it froze. And it always froze with Ubuntu 18.04. It is a computer from 2018, so it was four years without me being able to natively run Linux in it. I had to use a virtual machine during these years =(
So, there's a lot of work either by the community or by the vendor to make Linux work in some hardware.
They sell this laptop with Linux too already. And the equivalent of a FreeDOS setup doesn't even need anything complicated - I doubt FreeDOS ships with sound or graphics drivers after all.
Some line test might run on it. It could be that at that point it is simpler to sell it on with the software than wiping.
What gets me is... what's the point? If you don't want to fight MS about selling PCs with no OS, ship some Linux distro. DOS was a nice option when you needed to support bare-metal stuff like flashing the BIOS without a modern OS getting in the way, but I would be shocked if that worked here - basically, I can see reasons to ship DOS, but they're all mutually incompatible with a virtual machine. And if you're going to ship a Linux distro - heck even if you're going to include some weird DOS VM - why would you ever ship multiple different versions?
So yeah, I'm thinking horribly broken company process and/or outsourcing without actually making sure the requirements make sense.
So yeah, I'm thinking horribly broken company process and/or outsourcing without actually making sure the requirements make sense.
It seems pretty obvious to me. There were issues getting the old FreeDOS image to run on some of the new hardware. Someone was tasked by their manager with fixing it. They said fuck it and just did this because it was easier/faster than trying to troubleshoot DOS on modern hardware. They showed it to their manager and their manager saw FreeDOS boot and was happy. Until now no one ever noticed because FreeDOS is just the "I'm going to pirate windows option".
I'm the author of the article and that is my conclusion also.
Shipping your PC with "some linux distro" means you have to support that linux distro.
Selling it with freedos, you only have to support freedos, and people who buy that option will install something else anyway.
Selling it with freedos, you only have to support freedos, and people who buy that option will install something else anyway.
> Shipping your PC with "some linux distro" means you have to support that linux distro.
But they do offer to ship with a Linux distro, even apart from this strange frankensystem option. Did you miss where straight Ubuntu is a pre-install option?
But they do offer to ship with a Linux distro, even apart from this strange frankensystem option. Did you miss where straight Ubuntu is a pre-install option?
According to another commenter some laptops don't have Ubuntu as an option (likely due to some sort of driver issues).
Yes and they charge for that, so that's consistent with what the parent comment said.
Erm...no? Look at the screenshot in the article. There is no charge for Ubuntu in that shot, only for Windows.
Oops, you're right. I did look at the screenshot before but totally misread it (probably because Ubuntu is just blank in the price column rather than $0, and there's no horizontal lines (thanks Tufte)).
[deleted]
>>means you have to support that linux distro.
But why or how? I just don't see that at all. Dell won't "support" FreeDOS either. It could be just a basic Ubuntu install that's broken as hell, and I don't see why or how Dell would need to support that.
But why or how? I just don't see that at all. Dell won't "support" FreeDOS either. It could be just a basic Ubuntu install that's broken as hell, and I don't see why or how Dell would need to support that.
> If you don't want to fight MS about selling PCs with no OS, ship some Linux distro.
And that's exactly what they're doing. They just did the bare minimum work to be able to fit that Linux setup under their pre-existing "FreeDOS" SKU. And the real point of that SKU is for sophisticated users to wipe the whole thing clean and set up their own OS install. It still works perfectly for that.
And that's exactly what they're doing. They just did the bare minimum work to be able to fit that Linux setup under their pre-existing "FreeDOS" SKU. And the real point of that SKU is for sophisticated users to wipe the whole thing clean and set up their own OS install. It still works perfectly for that.
How does this "FreeDOS" option work better for that than selecting the straight Ubuntu option they offer, and wiping that clean?
It avoids HP paying Canonical and/or taking support calls on hundreds of Ubuntu feature packages.
The Ubuntu option appears to be free too.
Free to you, but HP is likely paying Ubuntu. They wouldn't be paying much, but they're probably paying something.
The Ubuntu license says that if they make any modification whatsoever, no matter how trivial, they can no longer call it Ubuntu. Just adding a driver is enough to trigger the clause, AFAICT.
The Ubuntu license says that if they make any modification whatsoever, no matter how trivial, they can no longer call it Ubuntu. Just adding a driver is enough to trigger the clause, AFAICT.
I doubt that.
Most likely it is an agreement that is seen as a win on both party. HP has no incentive to pay ubuntu for anything, and ubuntu can't get any new market if it starts asking companies to pay for it.
And they could use whatever distro they want that do not have those clauses instead of ubuntu.
Most likely it is an agreement that is seen as a win on both party. HP has no incentive to pay ubuntu for anything, and ubuntu can't get any new market if it starts asking companies to pay for it.
And they could use whatever distro they want that do not have those clauses instead of ubuntu.
The agreements would have been signed when Ubuntu had >50% Linux market share. Increasing share is not particularly helpful in that scenario compared to increasing revenue per seat.
Also, these agreements are Ubuntu's primary revenue source, AFAICT. And they have hundreds of millions in revenue per annum. Primarily from the cloud vendors.
All distros have these clauses. The software is free, but the name is a protected registered trade mark. Not all distros enforce it, but the HP lawyers will ensure HP is covered.
Finally corporate buyers will want a trusted distribution, not the flavor du jour.
Also, these agreements are Ubuntu's primary revenue source, AFAICT. And they have hundreds of millions in revenue per annum. Primarily from the cloud vendors.
All distros have these clauses. The software is free, but the name is a protected registered trade mark. Not all distros enforce it, but the HP lawyers will ensure HP is covered.
Finally corporate buyers will want a trusted distribution, not the flavor du jour.
As far as I heard from Canonical employees, Canonical was getting more per sold XPS13 (original Developer Edition) with Ubuntu than Microsoft did for every Windows being sold on the same laptop: when it was introduced, at the very least.
My guess is that it's offered for those who want to do their own Windows install but would be confused or scared away by seeing "Linux" in the name. "FreeDOS" is the codeword for no-OS, you install your own.
They’ve been doing it for 20 years, so I’d guess that there is some sort of contractural rationale between HP and Microsoft.
HP ships Ubuntu in thin clients by default. So the fact they are doing this implies some specific reason.
HP ships Ubuntu in thin clients by default. So the fact they are doing this implies some specific reason.
I'm surprised no one has guessed power and thermal management as a reason for running DOS on top of QEMU/Linux.
I have no idea.
If the laptop is running FreeDOS on "bare metal", what happens when you close the lid and put it in your backpack?
I have no idea.
If the laptop is running FreeDOS on "bare metal", what happens when you close the lid and put it in your backpack?
> If the laptop is running FreeDOS on "bare metal", what
> happens when you close the lid and put it in your backpack?
Discussed on HN here: https://news.ycombinator.com/item?id=28639952
[deleted]
That was far more amusing and interesting than I thought it would be...
I wonder if it can actually boot DOS on the physical hardware, and if it can't ( DOS itself is very minimal in what it requires of the hardware), is it really PC-compatible anymore?
I wonder if it can actually boot DOS on the physical hardware, and if it can't ( DOS itself is very minimal in what it requires of the hardware), is it really PC-compatible anymore?
I'm glad you were amused! I had fun dissecting these images and figuring out what lurked inside :)
Intel phased out the UEFI CSM from new platforms in 2020-2021.
I suppose you could use GRUB and whatever Coreboot has as its BIOS? Either way, sad times indeed when PCs aren't anymore.
seabios is the project you're looking for, and yes now I want to go see if it supports being booted from GRUB:)
EDIT: The answer is yes and it's been done: https://g00se.org/2016/11/seabios-on-libreboot.html (granted, that's booting directly from coreboot to GRUB, but it should be the same booting UEFI to GRUB AFAIK)
EDIT: The answer is yes and it's been done: https://g00se.org/2016/11/seabios-on-libreboot.html (granted, that's booting directly from coreboot to GRUB, but it should be the same booting UEFI to GRUB AFAIK)
Alternatively, we can be happy that some legacy systems actually die when they're no longer useful. My general attitude toward retro-computing is that the good old days weren't actually that good. I, for one, don't care if the original meaning of "PC" passes into irrelevance.
Hell no. We're being pushed into draconian closed systems, this is starting to infect the PC, and it's only because there's little opposition.
As if BIOS is any more open than UEFI is. At least UEFI had an open reference implementation since the beginning. BIOS had to be reverse engineered from IBM's implementation AFAIR.
Besides, two wrongs don't make one right. BIOS was a clutch from the beginning (it was probably appropriate for the time tho) and we should strive for better. We should keep functional systems working of course (e-waste is a real problem), but we shouldn't keep using it for the new stuff because we see the past with rose tinted glasses.
Rather than push for the past we should push for the future, for having all boards ship Coreboot and have that support upstream instead. That's how you achieve openness, not by sticking to _proprietary blobs_ of an outdated interface.
The Clover bootloader designed for Hackintosh is able to boot UEFI operating systems (including non-Apple ones) on computers that don't natively support UEFI. Is there any reason a different bootloader couldn't do the reverse?
It's like a Linux, qemu, DOS turducken
489K? That's terrible memory management! I wouldn't start a dos PC with less than 600k.
Wow.
But it's also quite surprising considering HP (and HPE which I understand is not very related) usually provides FreeDOS based firmware update and configurarion ISOs on their product download pages.
But it's also quite surprising considering HP (and HPE which I understand is not very related) usually provides FreeDOS based firmware update and configurarion ISOs on their product download pages.
Imagine being the engineer tasked with creating this bizarro system.
>HP computers sold with FreeDOS are intended for customers who have a license for an additional operating system, if so desired
From some HP documentation archived on some website called icecat
From some HP documentation archived on some website called icecat
Given that HP is also using obscure/outdated Linux images in their own Intelligent Provisioning / Smart Storage Administrator tools that are installed on the built-in flash of (at least) gen8 servers <https://op-co.de/blog/posts/microserver_gen8_fix_boot_order/>, I'm not at all surprised to see similar approaches in other situations.
I don't know if the law changed in the last years but here (Spain) it's illegal to sell a computer without a operative system.
Today the most easy option probably is to install Linux but I remember this law was there at year 2000 and at that time Linux was harder to install than FreeDOS.
Very interesting. I’m assuming there is no persistence in the referenced live squashfs ?
squashfs is supposed to be read-only, right?
First two things that come to my mind are limitations of OS when it comes to memory address space and need to easily display documentation.
So, has anyone bought one of these, then returned it for not being fit for purpose?
If not, can they just do the same thing with windows, and not bother with supporting it on bare metal?
If not, can they just do the same thing with windows, and not bother with supporting it on bare metal?
Ghastly.
Kind of random, but the article reminded me. I think every pdf should have it's own linux installation. They should role it into the pdf specification. You never know when that might be useful.
I know you're half-joking but there's actually been a few "bootable PDF" articles on HN before.
It this happened, would we need to say "gnu/ghostscript/linux", to be proper about it?
You are. (Weird that is).
I find OEMs that bundle operating systems to be weird. Dictating choice is something a dictatorship would do. I used to argue the reasoning until the obscurities hit.
I find OEMs that bundle operating systems to be weird. Dictating choice is something a dictatorship would do. I used to argue the reasoning until the obscurities hit.
Not weird but money-loving; sweet exclusive deals with Microsoft to have Windows preinstalled for less, as long as all machines have it preinstalled. (It was less sweet and more forcing their hand in 1990s.)
You may be able to buy a laptop with no OS and know what to do, but do the majority of people? It’s not evil; it’s just what’s required if you want to sell computers.
Something I recently joked about doing was porting SDL to the UEFI environment and then building DOSBOX for it. I’m sure someone has already done this in some fashion, but the idea was amusing enough for me to genuinely consider it one of these weekends. I guess in that case, though, you can’t really run FreeDOS.