[dba-Tech] Microsoft is bringing the Bash shell to Windows 10

[Salakhetdinov Shamil]

 Hi Jim --

Thank you for your detailed comment. Let's wait to see what the Bash Shell will be in this summer Win10 upgrade.
I suppose it should be a default feature to run as many Bash Shells instances as needed as you can currently run many win cmd shells...

Multi-processing, background and parallel processing, isolation layers - all that processing modes are available in Win10.

--- Shamil

>Tuesday, April  5, 2016 8:40 AM +03:00 from Jim Lawrence <accessd at shaw.ca>:
>
>Shamil:
>
>I saw the video and it looked interesting...and finally had a chance to play with it. 
>
>As far as I can see it is just an emulator and not full featured yet. The other thing worthy of noting that there is only one Bash shell allowed per session. On real Linux you could open a dozen or more shells and run processes on each and only if you actually locked a file would another shell no have complete access. You can also use one shell to release another if process became locked.
>
>I am not really sure what the advantage to having a Bash shell on a Windows box is, as any real system commands are currently blocked and I am not sure whether they will be supported in the final version. The real properties of Linux are that a person can run many environment with many separate users and each user/process is completely isolated. All Linux computers are basically full servers.
>
>Running a Bash shell on a single user Windows box is nice and fun but the question is why? As soon as multiple simultaneous processes are spawned or more accurately attempted to be spawned...like a fork for example...it of course bails. Then the are virtual file systems, direct calls to hardware like checking the condition of wireless "iwconfig"...even ifconfig is limited. Try to set or add additional ip addresses and well... Then try running virtual processes across the network... I have not tried this yet, because I am sure I know what the result would be; if I downloaded a tar-ball, expanded it and attempted to recompile the source with all it dependencies would it unceremonious crash?
>
>Linux is a multi-user, multi-processing system with multiple levels of isolation and background and parallel processing capabilities. I can not imagine how that could be shoe-horned into a rather simplistic single user Windows 10 OS, that I have previously been able to crash with impunity. 
>
>I think the effort is great but at the end why would anyone bother? OTOH, dropping Windows 10 into a Linux box is a great idea. A remote user could call in pick their session, any of a dozen GUIS, and in some cases this could be Windows 10, and a host of other users could remote in and do the same...of course this would break the Windows licensing agreement, with say a half dozen instances running simultaneously on the same computer. Just like you can have five copies of MS Access running on your computer...through five different logins...or if you used a bare bone VFS, like KVM, hundreds of copies could be spawned. (I have heard this can be done I have not done this myself...) 
>
>In conclusion, its real nice but why? Maybe it is so that Windows users can get up to speed on Linux basics?
>
>Jim 
<<< skipped >>>
>