From: mutazilah@gmail.com   
      
   On 18/02/24 11:19, Paul Edwards wrote:   
      
   >>> you can use the getpid() syscall to get the process ID, then open and   
   >>> read /proc//cmdline   
   >>>   
   >>> Apparently this method exists in Unix too.   
   >>   
   > Anyway, I have Ubuntu Kylin installed again on   
   > this Chicom computer, this time running under   
   > Virtualbox, and this time from an American site   
   > (I think) instead of direct from the PLA   
   > (People's Suppression Army), so I will try out   
   > this /proc theory now.   
      
   And ... it works!   
      
   So that's a very solid basis for PDOS/386.   
      
   With no msvcrt.dll or doscalls.dll present on   
   the PDOS/386 disk I am expecting to support   
   32-bit MSDOS (my definition), PDOS-generic,   
   Win32, OS/2 2.0 and Linux ELF executables.   
      
   All with a footprint that fits on a 360k floppy.   
      
   Or very close, anyway. ie it shouldn't be much   
   more than this:   
      
   C:\vbox>7z l pdos.vhd | grep -i pdos.sys   
   2024-02-14 12:10:02 ....A       241664       241664  PDOS.SYS   
      
   C:\vbox>7z l pdos.vhd | grep -i command.exe   
   2024-02-14 12:10:02 ....A        45568        49152  COMMAND.EXE   
      
   C:\vbox>7z l pdos.vhd | grep -i io.sys   
   2024-02-14 12:10:02 ....A        34103        36864  IO.SYS   
      
   C:\vbox>zcalc 241664+45568+34103   
   Calculated Value is 321335.000000   
      
      
   ... in theory.   
      
   It would be cool if I could have a "hello world"   
   executable for each of those (OS/2, Linux etc)   
   on the same floppy. And even cooler if I could   
   run in 640k instead of the current requirement   
   for 2.5 MiB or something.   
      
   There were 80386 machines shipped with 1 MiB   
   of memory.   
      
   BFN. Paul.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)