91–97 of 97 posts
Earlier quoted context omitted.
It's been years since I used Wine, but I think it just runs each Windows process in its own Linux process. There's no Wine "kernel" that needs to manage virtual memory or isolate multiple processes.
AIUI this is correct, yes.
Hi. I'm Dan Aloni, original author of this project. It still warms my heart to see this pops in HN every few years. The others who have worked on it and myself are keeping that site as the good relic that it obviously should be :) It still amazes me how breakthrough it was to have that working, given the lack of hardware virtualization for PCs in late 2003.
It seems that today we can achieve similar functionality in fundamentally different ways (WSL, WSL2/virtualisation, Cygwin, etc.) What in your opinion is today's closest solution to colinux? and why we don't see such clever solutions today?
[1] - State of WSL1 · microsoft/WSL · Discussion - https://github.com/microsoft/WSL/discussions/4022#discussion...
Hi. I'm Dan Aloni, original author of this project. It still warms my heart to see this pops in HN every few years. The others who have worked on it and myself are keeping that site as the good relic that it obviously should be :) It still amazes me how breakthrough it was to have that working, given the lack of hardware virtualization for PCs in late 2003.
I created the images for Fedora, CentOS and OpenSuse. it thought me a lot about the dependencies, Linux image builds, etc... it was creating 'container'-images before this was a general thing.
Around 2007 when Linux namespaces started getting better support, I had made a small executable to use these system calls and to spin up a squashfs image 'just for compiling stuff for another system'. Much later, this whole method was replaced with 'docker run'.
What a cool and novel concept! Bummed and a little surprised it's the first time I've heard of it. I wish there were a browsable directory index of cool projects such as CoLinux. Reading the description definitely set of bells in my head reminding me of the venerable Cygwin, though CoLinux could comparatively have potentially more capabilities and upsides since there is a fully resident kernel running. CoLinux hasn't…
> what happened? Probably the fact that it lacked 64-bit support: https://colinux.fandom.com/wiki/FAQ#Q27._Does_coLinux_work_u...
Hi. I'm Dan Aloni, original author of this project. It still warms my heart to see this pops in HN every few years. The others who have worked on it and myself are keeping that site as the good relic that it obviously should be :) It still amazes me how breakthrough it was to have that working, given the lack of hardware virtualization for PCs in late 2003.
I even published the app (ok code-signing was done on a Hackintosh), sadly it didn't make me rich...
This being historical pre-wsl aside: A lot of the foss tasklist is just aimless combinatorials. And they become obsolete to boot: -clone a program that just came out but make it open source -port everything to every platform -make x run on any dependency of category Y And then it gets exponential as every new project becomes a new target to port from and to as a dependency: e.g, port linux co-op to rust, or port it t…
What's the harm? Having multiple alternatives to any component of the software stack is a good thing, and it fosters understanding and improvement, doesn't it?
OTOH, it's quite aimless, this unfolds from the main weakness of foss that is without money there's little incentive. And all of the volunteer incentive is behind making new things, so there's a lot of horizontal exploration and almost no perfection.
Hi. I'm Dan Aloni, original author of this project. It still warms my heart to see this pops in HN every few years. The others who have worked on it and myself are keeping that site as the good relic that it obviously should be :) It still amazes me how breakthrough it was to have that working, given the lack of hardware virtualization for PCs in late 2003.
Any idea why Microsoft didn't use this in WSL1 or 2?
Is it more efficient than hyper-v with hardware acceleration?
Can you see it being useful again? Or does it make sense to have a hybrid where the code runs using hardware acceleration but the timers are cooperative?