Live data from Hacker News

Linux as co-operative Windows process (2017)

colinux.org

51–60 of 97 posts

Re: Linux as co-operative Windows process (2017)

#51
post #47

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 .".

Pretty sure it was tongue in cheek.

Re: Linux as co-operative Windows process (2017)

#52
post #47

Earlier 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

Have you tried nushell (https://www.nushell.sh/)? It embeds GNU coreutils written in Rust, so it feels like Linux even on a Windows machine.

Re: Linux as co-operative Windows process (2017)

#53

I 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.

I use WSL1 on my work PC everyday, because I can't run HyperV. I don't have a GUI, but a coworker said he was able to get VNC running on WSL1 and was able to VNC into it from his Windows environment.

Re: Linux as co-operative Windows process (2017)

#54
post #23
post #12

Earlier 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.

Isn't WSL2 still slower than WSL1 for accessing Windows drives and networks? I use WSL1 because I don't have HyperV available on my work PC, but it's also convenient because I perform most of my work on Windows.

Re: Linux as co-operative Windows process (2017)

#55
post #47

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 .".

> "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)

#57
post #47

Earlier 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…

[deleted]

Re: Linux as co-operative Windows process (2017)

#58
post #46

Earlier 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...

Huh? What are you talking about? I can manipulate page tables just fine from userspace through the magic of MapViewOfFile.

Re: Linux as co-operative Windows process (2017)

#59

I 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.

If they are not willing to give complete power to the user, it will not happen, ever. Linux isn't designed for granular permission management like Windows is. A Linux desktop administrator has to choose between all or never. Moreover there is no equivalent of Active Directory or Group Policies.

Re: Linux as co-operative Windows process (2017)

#60
post #47

Earlier 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…

If the time comes to discuss operating systems, I always suggest an exercise of downloading a Windows 11 Home ISO and installing it into a virtual machine, look at how much of it is installing an OS versus upselling into services using every dark pattern in the book. (With such hits as "the No button is hidden under a link-button called Learn More and only appears if you choose an advanced installation")

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.

Post reply on HN