I remember using this decades ago. The user friendliness of Linux combined with the stability of windows. It did beat dual booting though. Worked like a charm.
>>The user friendliness of Linux combined with the stability of windows. I think you meant: "The user friendliness of Windows combined with the stability of Linux .".
Linux as co-operative Windows process (2017)
51–60 of 97 posts
Re: Linux as co-operative Windows process (2017)
#52Earlier quoted context omitted.
>>The user friendliness of Linux combined with the stability of windows. I think you meant: "The user friendliness of Windows combined with the stability of Linux .".
My use case for WSL is really what original comment says: I need stability of windows so my graphics drivers won't stop working randomly and user friendliness of linux command line as a developer
Re: Linux as co-operative Windows process (2017)
#53I wonder if something like this might make a comeback for workers that are blocked from using wsl/hyperv on their corporate laptops. For me I've been using msys2 as an "alternative" since I'm unable to use wsl. It's not the same but it's all I got.
Re: Linux as co-operative Windows process (2017)
#54Earlier quoted context omitted.
WSL1 is actually quite similar afaik. Unfortunately also development stalled here in favour of WSL2. I remember Co-Linux to be a a thing around 2005, but it never stuck with me as I was mostly happy with Cygwin until all the libuv and go (now rust) stuff popped up.
I don't think WSL1 development stalled in as much as Microsoft made the determination that it wasn't a viable path forward. I/O was piss slow and chasing syscalls NT API calls probably wasn't very fun. Microsoft already knew Hyper-V quite well so a VM made sense, they just had to put some automagic management around it.
Re: Linux as co-operative Windows process (2017)
#55I remember using this decades ago. The user friendliness of Linux combined with the stability of windows. It did beat dual booting though. Worked like a charm.
>>The user friendliness of Linux combined with the stability of windows. I think you meant: "The user friendliness of Windows combined with the stability of Linux .".
I think you meant: "The user friendliness of Linux combined with the stability of Linux."
You know, like when you're not forced to link your system to a Microsoft account. Or when you cannot reboot because a 30 minute update is pushed down your throat. Or when you cannot start working because an other 30 minute update is pushed down your throat at startup. Or when you have a 2 minute warning before a forced 1h update is pushed down your.. ..you get the picture. And the long, long list goes on.
Re: Linux as co-operative Windows process (2017)
#56Re: Linux as co-operative Windows process (2017)
#57Earlier quoted context omitted.
>>The user friendliness of Linux combined with the stability of windows. I think you meant: "The user friendliness of Windows combined with the stability of Linux .".
> "The user friendliness of Windows combined with the stability of Linux." I think you meant: "The user friendliness of Linux combined with the stability of Linux ." You know, like when you're not forced to link your system to a Microsoft account. Or when you cannot reboot because a 30 minute update is pushed down your throat. Or when you cannot start working because an other 30 minute update is pushed down your thro…
Re: Linux as co-operative Windows process (2017)
#58Earlier quoted context omitted.
The site is down, so I can't see what they're doing with the MMU: that said, most virtual memory management works just fine from normal boring userspace. If wine can do it for running win32 on Linux, this thing can do it for running Linux stuff on win32, which isn't less powerful when it comes to virtual memory management.
The VMM is part of the kernel (or executive), not userspace. App requests memory, VMM assigns pages from RAM, page file, or backing store. If you wanted to segment yourself and take over anything 'below' the kernel like the MMU, you'd need elevated rights. But that'd be some interesting programming. https://en.wikipedia.org/wiki/Architecture_of_Windows_NT#/me...
Re: Linux as co-operative Windows process (2017)
#59I think it's great that tools like colinux exist but when if ever will IT departments (System Administrators) figure out how to support Linux Desktop users on our machines instead of forcing Windows or Mac on us. Mac is a terrible OS for Java software development.
Re: Linux as co-operative Windows process (2017)
#60Earlier quoted context omitted.
>>The user friendliness of Linux combined with the stability of windows. I think you meant: "The user friendliness of Windows combined with the stability of Linux .".
> "The user friendliness of Windows combined with the stability of Linux." I think you meant: "The user friendliness of Linux combined with the stability of Linux ." You know, like when you're not forced to link your system to a Microsoft account. Or when you cannot reboot because a 30 minute update is pushed down your throat. Or when you cannot start working because an other 30 minute update is pushed down your thro…
Once you're using it for >month, it's easy to see the BS as just an occasional inconvenience because saying yes is so much easier.