Talk:Lxrun

Lxrun is a layer sitting on top of SCO's Unix that allows it to run Linux binaries natively. It's debated about because of the SCO-IBM litegation for various reasons. Mostly because:


 * It was released by SCO and ported to other operating systems by non-SCO folk. Which means that contested methods and concepts like the ELF headers were released by SCO.
 * It's not unthinkable that it contains GPL'ed Linux code, which means that SCO would be violating the GPL. AFAIK Lxrun is closed source software, though it's source was used outside SCO presumably under NDA.

This page is currently linked from Groklaw. I hope someone from there will improve this lxrun article significantly. I suggest to postpone the speedy deletion by a few days. If no-one had improved it by them, get rid of it. -- Sander Marechal


 * It got speedied, but I recreated a new version that's written a bit more encyclopedically. And has the rather extensive Groklaw article as its reference. As far as I recall, it hasn't actually been mentioned in the SCO case, though there's been extensive conjecture and investigation on Groklaw - if I'm wrong, we need references. But for the moment, we have a decent stub here, we can let the article grow properly - David Gerard 22:57, 17 August 2006 (UTC)

lxrun in Windows 10
There is a (now deprecated) command in Windows 10 called lxrun for setting up the Windows Subsystem for Linux. In fact the article for WSL links to this one, but Windows' lxrun does not appear to be related in any way to the lxrun this article describes. Any ideas for how to address this discrepancy? ChrstphrChvz (talk • contribs) 11:57, 10 March 2018 (UTC)
 * Some choices would be:
 * Unlink the reference in WSL
 * Pipe the link to a redlink -- say, to lxrun (Windows)
 * Create an article for the command
 * Create a redirect for the command to an article where it's discussed
 * Since it's deprecated, my choice would be "unlink it" or "pipe to a redlink". In any event, it shouldn't link here, nor does this article need to mention it. Regards, NapoliRoma (talk) 23:36, 10 March 2018 (UTC)
 * Based on what Codename Lisa suggested on Talk:Windows Subsystem for Linux, I now see that the link ended up there probably because of mentioning Wine and similarly-purposed compatibility layers, so it's probably just a coincidence that Windows 10 has a command with the same name as one of them.
 * I'm inclined to follow your advice of removing the link to prevent confusion, rather than redlinking since it probably was not the intention to refer to the Windows 10 command. Thanks for the suggestions! ChrstphrChvz (talk • contribs) 00:26, 18 March 2018 (UTC)