6 ms·

Now we need to have a linux driver that lets run Windows after kernel panic and we can switch between them without reboot, just like we wanted 20 years ago...

bdhcuidbebe 3y ago
its called kvm and is just 2 years shy of turning 20
- weinzierl 3y ago
  Nah, it's call loadlin and so old that no one seems to remember its birth.
  - meepmorp 3y ago
    I remember loadlin. Netware used to boot that way, too - load DOS, then replace everything.
    - wannacboatmovie 3y ago
      I vaguely remember you could exit NetWare and it would drop you back at the DOS prompt. Do I remember this correctly?
      - meepmorp 3y ago
        It's been a while but I don't remember that, under 3.x at least. However, according to Wikipedia: > NetWare 286 2.x normally requires a dedicated PC to act as the server, where the server uses DOS only as a to execute the operating system file NET$OS.EXE. All memory is allocated to NetWare; no DOS ran on the server. However, a "non-dedicated" version was also available for price-conscious customers. In this, DOS 3.3 or higher remains in memory, and the processor time-slices between the DOS and NetWare programs, allowing the server computer to be used simultaneously as a network file server and as a user workstation. Because all (RAM above 1 MiB) is allocated to NetWare, DOS is limited to only 640 KiB; managers that used the MMU of 80386 and higher processors, such as EMM386, do not work; 8086-style expanded memory on dedicated plug-in cards is possible however. Time slicing is accomplished using the keyboard interrupt, which requires strict compliance with the IBM PC design model, otherwise performance is affected. So, maybe that's what you're thinking of? Also, time slicing via keyboard interrupt is something.
  - mikecoles 3y ago
    You are an old head. Thankfully, your memory is better than mine.
  - pjmlp 3y ago
    Naturally using umsdos.
  - deleted 3y ago
    [deleted]
bhdlr 3y ago
Been using Linux as my daily driver for 5 years and have never seen a Kernel panic, so there's probably no drive to do it :P
- fps_doug 3y ago
  I've worked and developed on Linux, for Linux, for 10+ years, I've seen my fair share of panics, especially using the bleeding edge releases. Most (not all!) of them were my own making though. :>
  - logicprog 3y ago
    Yeah I've been using Linux exclusively for maybe 9 years and the only time I've ever seen a kernel panic was when I was messing around with Gentoo on a cheap machine I have just for that sort of screwing around, and I accidentally told it to literally overwrite the kernel. It got pretty far giving itself a lobotomy before it died, too. Meanwhile, the last time I used Windows (in order to install Linux on a new laptop, lol), it blue screened four times just trying to mount a simple USB flash drive.
    - 13of40 3y ago
      > it blue screened four times just trying to mount a simple USB flash drive With Linux these problems can typically be solved by googling it on your phone then appending a text file with some nonsense string you found on a 10 year old forum post. I'm still holding my breath for Windows to catch up with that level of UX.
      - onetimeuse92304 3y ago
        The basic difference and reason for me to have stuck with Linux for so long is that when there is a problem with Linux it is all about how much I can persevere trying to fix it. All code is there and I have the skills to fix it. With Windows, if it doesn't work, there is a chance there simply is nothing you can do about it. There is no source code. The support people are completely useless. If you can't fiddle with it until it somehow works or find a person on the Internet that fiddled with it until it worked and they were gracious to share the solution, your only option tends to be to reinstall the entire thing and hope for the best.
Deforest7551 3y ago
I think this already existed. https://youtu.be/q5M0TwnkWUM?si=X6WdLHNfXNZ-FSrD https://youtu.be/q5M0TwnkWUM?si=X6WdLHNfXNZ-FSrD
RulerOf 3y ago
I had that working very briefly for a short period of time circa 2010. Linux -> kexec grub -> NTLDR Windows -> Winkexec[1] grub -> linux kernel It was extremely fiddly, and the majority of hardware I threw it at really didn't like complying with what I was trying to do, in spite of the fact that it ought to work, at least on paper. 1: https://github.com/stump/winkexec https://github.com/stump/winkexec

bdhcuidbebe 3y ago

its called kvm and is just 2 years shy of turning 20

weinzierl 3y ago
Nah, it's call loadlin and so old that no one seems to remember its birth.
- meepmorp 3y ago
  I remember loadlin. Netware used to boot that way, too - load DOS, then replace everything.
  - wannacboatmovie 3y ago
    I vaguely remember you could exit NetWare and it would drop you back at the DOS prompt. Do I remember this correctly?
    - meepmorp 3y ago
      It's been a while but I don't remember that, under 3.x at least. However, according to Wikipedia: > NetWare 286 2.x normally requires a dedicated PC to act as the server, where the server uses DOS only as a to execute the operating system file NET$OS.EXE. All memory is allocated to NetWare; no DOS ran on the server. However, a "non-dedicated" version was also available for price-conscious customers. In this, DOS 3.3 or higher remains in memory, and the processor time-slices between the DOS and NetWare programs, allowing the server computer to be used simultaneously as a network file server and as a user workstation. Because all (RAM above 1 MiB) is allocated to NetWare, DOS is limited to only 640 KiB; managers that used the MMU of 80386 and higher processors, such as EMM386, do not work; 8086-style expanded memory on dedicated plug-in cards is possible however. Time slicing is accomplished using the keyboard interrupt, which requires strict compliance with the IBM PC design model, otherwise performance is affected. So, maybe that's what you're thinking of? Also, time slicing via keyboard interrupt is something.
- mikecoles 3y ago
  You are an old head. Thankfully, your memory is better than mine.
- pjmlp 3y ago
  Naturally using umsdos.
- deleted 3y ago
  [deleted]

bhdlr 3y ago

Been using Linux as my daily driver for 5 years and have never seen a Kernel panic, so there's probably no drive to do it :P

fps_doug 3y ago
I've worked and developed on Linux, for Linux, for 10+ years, I've seen my fair share of panics, especially using the bleeding edge releases. Most (not all!) of them were my own making though. :>
- logicprog 3y ago
  Yeah I've been using Linux exclusively for maybe 9 years and the only time I've ever seen a kernel panic was when I was messing around with Gentoo on a cheap machine I have just for that sort of screwing around, and I accidentally told it to literally overwrite the kernel. It got pretty far giving itself a lobotomy before it died, too. Meanwhile, the last time I used Windows (in order to install Linux on a new laptop, lol), it blue screened four times just trying to mount a simple USB flash drive.
  - 13of40 3y ago
    > it blue screened four times just trying to mount a simple USB flash drive With Linux these problems can typically be solved by googling it on your phone then appending a text file with some nonsense string you found on a 10 year old forum post. I'm still holding my breath for Windows to catch up with that level of UX.
    - onetimeuse92304 3y ago
      The basic difference and reason for me to have stuck with Linux for so long is that when there is a problem with Linux it is all about how much I can persevere trying to fix it. All code is there and I have the skills to fix it. With Windows, if it doesn't work, there is a chance there simply is nothing you can do about it. There is no source code. The support people are completely useless. If you can't fiddle with it until it somehow works or find a person on the Internet that fiddled with it until it worked and they were gracious to share the solution, your only option tends to be to reinstall the entire thing and hope for the best.

Deforest7551 3y ago

I think this already existed. https://youtu.be/q5M0TwnkWUM?si=X6WdLHNfXNZ-FSrD https://youtu.be/q5M0TwnkWUM?si=X6WdLHNfXNZ-FSrD

RulerOf 3y ago

I had that working very briefly for a short period of time circa 2010. Linux -> kexec grub -> NTLDR Windows -> Winkexec[1] grub -> linux kernel It was extremely fiddly, and the majority of hardware I threw it at really didn't like complying with what I was trying to do, in spite of the fact that it ought to work, at least on paper. 1: https://github.com/stump/winkexec https://github.com/stump/winkexec