Perhaps they've added it to the Windows kernel? One can dream.
________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of David Crayford <[email protected]> Sent: Wednesday, August 10, 2016 7:03 PM To: [email protected] Subject: Re: Enterprise COBOL API for dynamic capacity tables On 11/08/2016 8:44 AM, Frank Swarbrick wrote: > The video specifically noted that fork does work...! Yes, but I take that with a pinch of salt because there's no Windows API call that performs a real fork. There are similar functions to spawn() but nothing that does CoW like fork(). Microsoft had an experimental Windows port of Redis a year or so ago and that was the issue that made it not production ready. > > ________________________________ > From: IBM Mainframe Discussion List <[email protected]> on behalf of > David Crayford <[email protected]> > Sent: Wednesday, August 10, 2016 5:59 PM > To: [email protected] > Subject: Re: Enterprise COBOL API for dynamic capacity tables > > On 10/08/2016 11:35 PM, Frank Swarbrick wrote: >> That "Linux on Windows" thing (not a VM, they point out!) is certainly >> interesting. Hope it does better than Windows Services for UNIX et al! > Indeed, my mistake. They intercept syscalls and translate them to > Windows API calls. It's like a giant kernel shim. I wonder how to handle > fork()? Windows doesn't support forking which is significant if you want > to run popular open source software like redis. > >> When Richard Stallman learns of this I imagine he will have a bit to say >> about the terminology. >> (https://en.wikipedia.org/wiki/GNU/Linux_naming_controversy) It seems to me >> that this is really GNU user code running on Windows, not Linux on Windows, >> since they specifically say there is no Linux kernel code present, and Linux >> really is only the kernel. GNU/Linux naming controversy - Wikipedia, the free ...<https://en.wikipedia.org/wiki/GNU/Linux_naming_controversy> en.wikipedia.org The GNU/Linux naming controversy is a dispute among members of the free and open source software community over whether to refer to computer operating systems that ... > GNU/Linux naming controversy - Wikipedia, the free > ...<https://en.wikipedia.org/wiki/GNU/Linux_naming_controversy> > en.wikipedia.org > The GNU/Linux naming controversy is a dispute among members of the free and > open source software community over whether to refer to computer operating > systems that ... > > > > Microsoft are partnering with Canonical. The Linux subsystem is > effectively and Ubuntu distro without the kernel. Good on them. I've > been running headless linux VM guests under VirtualBox but this much > better as it's integrated. > >> GNU/Linux naming controversy - Wikipedia, the free >> ...<https://en.wikipedia.org/wiki/GNU/Linux_naming_controversy> >> en.wikipedia.org >> The GNU/Linux naming controversy is a dispute among members of the free and >> open source software community over whether to refer to computer operating >> systems that ... >> >> >> >> ________________________________ >> From: IBM Mainframe Discussion List <[email protected]> on behalf of >> David Crayford <[email protected]> >> Sent: Tuesday, August 9, 2016 7:29 PM >> To: [email protected] >> Subject: Re: Enterprise COBOL API for dynamic capacity tables >> >> I run Git for Windows on my work PC which is very good indeed. It has a >> bash shell emulator and a nice GUI. We use SMB on z/OS and map the >> network drives on windows, so it's easy to use git from the command line >> with the working directory mapping to the zFS file system. It's simple >> to push/pull stuff from/to github. We have a private github account and >> it's a great platform for development. We use the issue tracking system >> to create a backlog of work items. The tooling on github is superb. >> >> I've recently been using a beta version of Windows 10 that has an >> integrated Ubuntu Linux VM running so I can use bash natively >> https://msdn.microsoft.com/en-us/commandline/wsl/about. It's great, much >> [https://sec.ch9.ms/ch9/5db6/8ee786b7-9fc5-45bf-94d0-16ea91765db6/P488_960.jpg]<https://msdn.microsoft.com/en-us/commandline/wsl/about> >> >> Bash on Ubuntu on Windows | >> MSDN<https://msdn.microsoft.com/en-us/commandline/wsl/about> >> msdn.microsoft.com >> Announcements Blogs. Mike Harsh's Blog -- Run Bash on Ubuntu on Windows; >> Scott Hanselman's Blog -- Developers Can Run Bash And Usermode Ubuntu Linux >> ... >> >> >> better than VirtualBox running VMs or Cygwin. It's a smart move by >> Microsoft. All the young kids are working on open source these days and >> they all uses macs because of the toolset, bash, homebrew etc. By >> integrating a Linux subsystem into Windows they may attract hipster >> hackers back the platform. Desktop Linux is ok but it's nowhere near as >> polished as iOS or Windows. >> >> >> On 10/08/2016 1:27 AM, Frank Swarbrick wrote: >>> Can you clarify? Do you run 'git' on Windows (I assume) and specify SMB >>> folders that actually exist on USS as your local repository (or whatever >>> its called)? >>> >>> Sounds interesting. Of course we don't use z/OS SMB, so that's an, umm, >>> "opportunity". :-) >>> >>> Frank >>> ________________________________ >>> From: IBM Mainframe Discussion List <[email protected]> on behalf of >>> David Crayford <[email protected]> >>> Sent: Tuesday, August 9, 2016 9:56 AM >>> To: [email protected] >>> Subject: Re: Enterprise COBOL API for dynamic capacity tables >>> >>> On 9/08/2016 11:49 PM, John McKown wrote: >>>> On Tue, Aug 9, 2016 at 10:40 AM, Frank Swarbrick < >>>> [email protected]> wrote: >>>> >>>>> Since I developed it at work for work I'll have to ask my employer about >>>>> that. Of course perhaps I should have asked before posting it publicly, >>>>> but that's water under the bridge now! >>>>> >>>>> Sidetracking, has anyone used GitHub for z/OS production source >>>>> repository. Meaning interacting with it directly from the mainframe? All >>>>> of our distributed development groups use it, and it might be nice if we >>>>> could use it as well. >>>>> >>>> Just as a personal observation, I'd think that this would be difficult. >>>> Someone would need to port the "git" command to z/OS. And that would likely >>>> be a major undertaking since it uses the GNU tools to do a lot of it's >>>> setup. It may also depend on some gcc (GNU compiler) specific >>>> functionality. And, even if it is ported, there is the historic ASCII (UTF >>>> actually) vs EBCDIC dilemma. You wouldn't believe the number of problems >>>> I've read about due to the Windows CRLF vs UNIX LF-only line ending causing >>>> "problems". >>>> >>> I use git for z/OS UNIX stuff via SMB and it works well from a PC shell. >>> A script that mirrors PDS libraries should work. >>> >>>>> Frank >>>>> >>>>> >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to [email protected] with the message: INFO IBM-MAIN >>> >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to [email protected] with the message: INFO IBM-MAIN >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
