Thanks Johnny and everyone here for a very exciting and educating 6-ish years. Coincidentally my bi-weekly crawler ran this morning and came up with 180 reachable and 818 dormant. Now I have to figure out why the total 1000 is elusive to it.
On Mar 8, 2023, at 8:14 PM, Paul Koning <paulkoning@comcast.net> wrote:
On Mar 8, 2023, at 8:03 PM, Johnny Billquist <bqt@softjar.se> wrote:
...
I think we should drop Cisco IOS and pyDECnet from the count - those
aren't really OSes for our purposes.
I struggled back and forth on those. At the moment I've come down on marking them that way.
For PyDECnet, I think it's pretty meaningless to say "Linux" or "Windows" or whatever. PyDECnet is like its own standalone DECnet environment that only exists inside that code Paul have written. Very different from someone actually running Linux/DECnet for instance.
The even more funny thing about PyDECnet is how I should call the CPU in this case. I've generally gone for saying the CPU is also PyDECnet, and architecture is unknown. But I've spotted a few times when I've been inconsistent.
Good point, "Linux" or the like are somewhat misleading. It might make sense to call the CPU "Python" since what's being executed is Python compiled bytecode. As for the architecture, either Python or the machine ISP below (like x86 or Arm).As for Cisco IOS, why would you not say that this is properly the OS?
Absolutely. It's an RTOS -- if you can show DECnet nodes running ELAN, it's equally valid to show DECnet nodes running IOS. aul_______________________________________________HECnet mailing list -- hecnet@lists.dfupdate.seTo unsubscribe send an email to hecnet-leave@lists.dfupdate.se