From: muta...@gmail.com   
      
   On Friday, July 2, 2021 at 7:05:55 PM UTC+10, Rod Pemberton wrote:   
      
   > > I want to run Linux executables from PDOS/386, running   
   > > as an unprivileged program running under Windows 10.   
   > > I don't have access to INT 80H so the executable will   
   > > fail (unless I was to somehow scan the executable and   
   > > zap them all into callbacks).   
      
   Note that that "desire" was for illustration purposes only.   
   I couldn't give a shit about crap like Linux.   
      
   What interests me is Win32-like S/370 executables   
   running under PDOS-generic (using FAT) running   
   under the current PDOS/3X0 (using CKD).   
      
   With all executables running at native speed on real   
   S/3X0 hardware.   
      
   That's largely embryonic. I'm not 100% sure what a   
   Win32-like S/370 executable is, and I don't have a   
   linker to produce the theoretical executable.   
      
   There is a S/370 assembler and linker written in   
   Python, about 30,000 lines, and I've made an attempt   
   at turning Python 3.3 into a C90-compliant executable,   
   a pre-requisite to working on either PDOS/386 or   
   PDOS/3X0. I have an executable built, but it produces   
   an internal error, likely due to one of the shortcuts I   
   took to get a build at all.   
      
   Someone else on the mainframe interested in Python   
   said he would take a look, and then went quiet.   
      
   I have a lot of paths open at any one time. But some   
   of them do indeed close. I have a Windows C compiler   
   with source (gccwin, 3.2.3) not dependent on Cygwin   
   crap, buildable from source. And in fact, the only   
   compiler that has been ported to PDOS/386. It only   
   became available in a form that passed my integrity   
   checks about 23 hours and 15 minutes ago, with a   
   lot of updates to pdos.org during the process.   
      
   There is method to the madness. Or there is madness.   
   Take your pick.   
      
   > You may wish to look at this old project. It directly runs Linux   
   > executables under Windows. An old post of mine says it has an "int   
   > 0x80 syscall interface, DLL loader, and no POSIX layer".   
   >   
   > LINE is not an emulator   
   > https://sourceforge.net/projects/line/   
      
   I checked out the link and stopped here:   
      
   LINE Is Not an Emulator. LINE executes unmodified Linux applications on   
   Windows by intercepting Linux system calls.   
      
      
   Intercepting Linux system calls, presumably by inserting   
   something into the INT 80H vector, requires privilege, the   
   thing I was illustrating I wanted to avoid.   
      
   BFN. Paul.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)