Slashdot Mirror
Windows 10 Spring Update Improves Linux On WSL With Unix Sockets and More (anandtech.com)
Billly Gates writes: Windows 10 build 1803 has come out this month, but with some problems. AnandTech has a deep-dive with the review examing many new features including the much better support for Linux. WSL (Windows Subsystem for Linux) now has native Curt and Tar from the command prompt as well as a utility to convert Unix to Windows pathnames called WSLpath.exe which is documented here. In addition it was mentioned on Slashdot in the past about OpenSSH being ported natively to Win32 in certain early builds. It now seems the reason was for Linux interoperability with this Spring Update 2. Unix sockets mean you can run Kali Linux on Windows 10 for penetration testing or run an Apache server in the background with full Linux networking support. Deemons now run in the background even with the command prompt closed. [...]
All this work to be compatible with Linux is only being done because Microsoft is desperately trying to get a ticket on the cloud moneytrain its ignored for nearly a decade. So far bootstrapping things like Kinect, office, and exchange to their cloud offering has boosted its presence in much the same way that paying hosting providers to switch their park-web sites to IIS static pages improved their netcraft numbers.
Curt and Tar from the command prompt
i presume we mean curl but this is moot. Anyone who needed curl or tar "from the command prompt" (as if it came anywhere else?) has their macbook, or their linux system...and they have it for free in the amazon cloud as well as the 40 some other openstack players that exist.
it was mentioned on Slashdot in the past about OpenSSH being ported natively to Win32 in certain early builds.
Embrace extend extinguish only works when theres a product with a bottom line people are willing to choose. "becoming linux" isnt doing anything to Redmond but wasting programmer hours trying to catch a lizard. Larry Ellison learned this fact with MySQL. GPL is an armored license that prohibits the type of early nineties chicanery Microsoft was absolutely legendary for pulling on small companies and startup projects.
Deemons now run in the background even with the command prompt closed.
Daemons,Welcome to 1991. You could also just pick a cloud provider with a competent ecosystem that will natively run any of five or more major linux distributions that your programmers are already familiar with.
Good people go to bed earlier.
Be patient. Eventually the Linux subsystem will be all that's left of Windows. Maybe a legacy support module on the side.
"First they came for the slanderers and i said nothing."
You may not but I do. My work requires that I use Windows. With WSL I can use all the classic Linux commands that I've been using for 15 years. The better they make it the happier I am.
Unix sockets mean you can run Kali Linux on Windows 10 for penetration testing or run an Apache server in the background with full Linux networking support.
You could just run Linux (and maybe Windows 10 in a VM).
It must have been something you assimilated. . . .
The differences are :
- On Windows, the use of .ini files has completely disappeared. Instead the registry hives being an opaque format that can be only access (in theory) with Windows' API of regedit. This would make it impossible to hand access them manually, say from a boot stick. (Well, in practice, there are 3rd party Linux tools able to access the hive format, so fixing from a boot stick is possible, but you got the idea).
- In gnome with gconfig the configuration is still stored in sets of plain XML files. Only they are now stored in an organized fashion in a specific set of subdirectories, and there's a centralized API and tool set to access them. But they are still human readable (you could still edit them with your favorite editor - emacs/vim/nano/ed) and easily machine readable (e.g. with your favorite Perl module such as XML::Twig).
The windows equivalent would have been if the .ini were kept, but now Microsoft defined a specific path to store them (e.g.: in a specifc subfolder tree within %USER_PROFILE% or whatever, instead of all over the place like in good old Win 3.x days) and mandated a specific API to manipulate them.
The closest thing to Windows' registry in Linux-land would be journald's internal database format, except that it has a very well documented format and journald forwards messages to any of your favorite system logger as soon as that deamon startsup - and it is configured to do so by default on virtually all the GNU/Linux distributions except for the most storage-starved ones in embed systems (e.g.: mercore/Sailfish OS doesn't have a syslog forwarding setup by default because it has to run on your smartphone limited internal flash. But Raspbian forwards to syslog by default).
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
Linux and all GPL software should move to GPL4, which should be identical to GPL2 with an added clause stating that Microsoft and Microsoft employees may not use any of it.
No need, and it would go against the GPL spirit.
The fundamental idea of GPL is that you should be able to do whatever you want with GPLed code, as long as you make sure that anyone you forward the code can still enjoy the same "whatever you want" freedom that your received. (that last part being the key difference with BSD-like persmissive license).
Restricting an imaginary GPLv4 against microsoft would go against the "to whatever you want" part. (And wouldn't be of any use, Microsoft would simply spin off a separate company to handle such GPLv4 code).
Also, by making mandatory to keep the same freedom to the next in line, GPL is pretty robust against EEE : you can't leverage extensions much if you have to publish them due to GPL, and you can't extinguish something that's freely available.
There's a reason why the older microsoft guard were shitting their pants and calling GPL "cancer" : RMS had designed something that incidentally happens to be completely EEE-proof.
The modifications of further GPL version were just about patching circumventions that some companies have found around the "keep the same freedom to the next in line" part.
GPLv1 made it mandatory to make source available together with the software.
Companies: "here's the code, but you can't legally do anything with it, because it's patent covered and you're violating our IP"
GPLv2 made it mandatory to grant access to the patents, without royalties.
Companies (e.g. TiVo): "here's the code, but in practice you can't really modify it because uploading your mods requires our secret cryptographic key"
GPLv3 made mandatory to provide a way (e.g.: key provided, unlockable bootloader, etc.) to actually be able to use modification in practice.
Currently there's no apparent need for a GPLv4 : no company has invented a way to give you the code, the patents license and the cryptographic keys, but still prevent you from actually modifying the code.
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
This means that I will be able to run Linux as a bag on the side of your wonderful Windows 10 product with two big advantages over a normal Linux installation: I will have the enormous overhead and slow boot time of Windows to deal with daily. And, Windows 10 will continue to spy on my every move and report it to you without telling me. I can hardly wait to get on the bandwagon with this one.
The problem you are facing is more that sysadmin as a career is fading away to be replaced by devops.
Linux is easy enough to admin that linux IT dept were always a fraction of the windows departments.
Now that most linux admin work is scripted/automated, Linux IT jobs are all but non-existent.
Windows IT jobs may last a bit longer, but as you can see, not much.