Posts by Bitcrazed 12 publicly visible posts • joined 29 Apr 2016
FWIW, Qualcomm's 8cx Gen 3 SoC is a pretty good desktop/laptop class SoC, and powers Surface Pro 9 and the Windows Dev Kit, along with devices from other OEMs including Lenovo's ThinkPad X13S
Ampere's Altra is a great choice for a more powerful SoC option.
As Arm based SoCs mature in desktop/laptop scenarios, and as Arm native OS, dev tools runtimes and libs, and Arm native apps, etc. arrive, expect more Arm silicon options to emerge,
Hi. (former) PM for WSL here.
Firstly, the sideswipe at Fedora Remix for WSL was completely unnecessary: When will the software world get over the fact that paying people who build, support, and maintain useful tools, apps, etc. is not only acceptable, but also necessary if we want to enjoy those tools, apps, etc. long into the future?
It's worth remembering that "Blowing out someone else’s flame doesn’t make yours shine brighter".
Secondly, WSL is not an NT kernel "personality" and is in no way related to NT's POSIX subsystem. Not even slightly. They are entirely different implementations of different things and share zero architecture and implementation details.
Slight correction: Unlike SFU, for which you had to rebuild your source code, Bash/WSL runs native ELF64 binaries so that everything in apt-get should work*.
* Note: There are gaps in this first version - some things will break. But as we continue to improve our syscall implementation coverage and depth, you should see more and more sceanrios "just work"
Actually, we run many things rather well. We have several things that are having issues right now (including MySQL, node/npm), but we're actively working on fixes to solve these and many other scenarios.
Our intent is that you should absolutely be able to run Linux-native Redis, MySQL, Postgres, Mongo, etc., locally for dev/test.
Microsoft has not clearly and intelligently explained what are the technical advantages of porting Ubuntu Linux into Windows VM infrastructure.
Did you watch our overview video. Or read & watch our architectural overview?
In both, we articulate that we're building this to make it easier for developers to build code for all platforms and all devices, on Windows. The WSL underlying Bash on Ubuntu on Windows allows unmodified Linux ELF64 binaries to run directly on Windows, within a new, secure, lightweight process PicoProcess infrastructure.
The net result being that Linux tools and tech that would normally fail to run on Windows will run well (once we've ironed out some initial kinks) and enable you to build, test and run your *NIX tools & code locally.
it certainly isn't Linux (no kernel; Linux is the kernel)
Which is precisely why we don't call it Winux - there is not Linux code in WSL.
and it certainly doesn't map the Linux system interface to Windows; it would be implementing it in the NT Kernel, just as Windows is implemented by the NT kernel.
Actually, yes, we DO implement the POSIX+Linux compatible syscalls layer running within a new PicoProcess infrastructure which calls into the syscalls implementation within the Windows kernel, calling into Windows kernel internals. You can read this to learn more!
And, no, this is not the old POSIX/Interix/SFU subsystem - this is brand new code which allows Windows to run unmodified native Linux ELF64 binaries directly on Windows.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
