6 ms·
PDOS: Public Domain Operating System
- rkta 4y agoI wonder in what language this was written in. ;)
- anta40 4y agoIt's stated in the FAQ: Was PDOS written in C90? As a matter of fact, yes. PDOS was in fact written in C90.
- aa-jv 4y agoEnglish.
- rep_lodsb 4y agoUnrelated (it's written C90, God's own programming language as far as the author believes), but this comment reminds me of "The Osmosian Order of Plain English Programmers", a project which may be on the same level of usefulness as PDOS. http://osmosian.com http://osmosian.com To say something positive, it's refreshingly different. I tried it out once, it seems to compile itself, but when I attempted to make literally any change it didn't work anymore. Whether trying to improve code generation, or just inserting a "Hello world" message somewhere.
- aa-jv 4y agoMy flippant response aside, this is an awesome thing to learn about on a Sunday morning .. thanks for that! I might have to give it a whirl. Although ChatGPT seems to be making it easier and easier to program in English and get code in any language to run anywhere needed ..
- lproven 4y agoI remember talking to this chap on the hercules-os380 mailing list. It used to be on Yahoo Groups but now it's here: https://groups.io/g/Hercules-OS380 https://groups.io/g/Hercules-OS380 The list was once for people extending the FOSS Hercules emulator and the early IBM OS/360 source code (available, but not technically FOSS) to make an emulator for an updated mainframe that never existed but could have more memory than the real things. Sounds crazy but it has some practical uses: IBM did do this later, but its OSes from that era are not FOSS or free: they are very expensive. The author of PDOS seemed to feel that PCs ought to have descended from miniaturised mainframes, not from a scaled-up Intel 8080. He wanted to write a Unix-like OS but for mainframes, and port it to the PC. It was very strange and confusing, and he did not explain it well at all. He seemed not to know (or care) about a lot of the history of computers, OS development or anything else: he seemed to feel he knew better and didn't need to know. In the end, the group was almost all his posts, and I left it, unable to cope with the torrent.
- LBJsPNS 4y agoIt would seem this individual is a bit unbalanced...
- lproven 4y agoCould well be, yes. Our exchanges on the Hercules list were very unproductive and in fact frustrating to very unpleasant for me. Just remembering where I'd seen this before was slightly upsetting.
- turtleyacht 4y agoThank-you for the link. Messages continue here: https://groups.io/g/hercules-380/messages https://groups.io/g/hercules-380/messages
- kerravon86 4y agoI am the main author of PDOS. I am not claiming to "know better" (or even know what that means). And I don't recognize your description of "PCs ought" as an accurate description of my views. Or even understand what that means either. If you ask a specific question I'll try to give an answer, based on my current understanding, but note that all my beliefs are tentative.
- InCityDreams 4y agoI can't help but think this is a somewhat terrible name choice.
- lproven 4y agoFWIW, the original name of FreeDOS was "PD-DOS". https://www.freedos.org/about/ https://www.freedos.org/about/ A lot of non-techies, or techies with not much exposure to the Linux/xBSD world, consider "PD" -- public domain -- to be more or less the same as FOSS. PD, BTW, is a USA concept and doesn't really exist in the rest of the Anglosphere.
- kerravon86 4y agoWhat does the UK and Australia consider Shakespeare's "Macbeth" to be? That's the concept, regardless of whether they (we) chose to name it differently.
- skissane 4y ago> A lot of non-techies, or techies with not much exposure to the Linux/xBSD world, consider "PD" -- public domain -- to be more or less the same as FOSS. I find a lot of old "public domain software" – especially from the 1970s and (early) 1980s, it seems unclear what exactly the authors mean by "public domain". A few even assert it is both "public domain" and "copyright" simultaneously, suggesting they actually think "public domain" means "freely redistributable" or something like that. But, nowadays understanding of the difference seems much more common. Most FOSS licenses come with conditions – MIT/BSD are often presented as "liberal", but even they have attribution requirements. PD has no conditions, including no legal requirement for attribution. If you can't legally pass it off as your own work, it isn't PD. A zero-condition copyright license, like so-called "0BSD", is practically equivalent to PD though, even if the work technically remains copyrighted. I agree that it is unethical to pass someone else's work off on your own. But legal attribution requirements cause a lot of bureaucratic pain if you worry about technical compliance with them. I don't like that pain and feel bad about imposing it on others, which is why for personal projects I prefer PD or PD-equivalent like 0BSD. I think attribution is best left as a matter of legally-unenforceable ethics. > PD, BTW, is a USA concept and doesn't really exist in the rest of the Anglosphere. Public Domain absolutely does exist in English law, and the rest of the Anglosphere. Copyright exists for a limited time (usually 70 years after death of author, but details vary); when it expires, the work enters the public domain. I think what you are alluding to though, is there is a legal dispute about whether you can voluntarily put a work into the public domain by relinquishing the copyright before it expires. It is pretty clear under US law you can; it is very debated under non-US law. In some countries, the consensus answer seems to be "No" (for example, Germany). From what I understand, in the UK/Australia/etc, the question is totally unsettled, different lawyers have different opinions and no court has ever ruled on it. However, in practice, it doesn't make a huge difference. Most people nowadays who try to put things in the public domain use something like Unlicense or CC0 – which basically contain a super-liberal fallback copyright license. So, if any court rules that the attempt to explicitly put the work in the public domain is void, the fallback copyright license means "it is still technically copyrighted but you can treat it as if you were public domain"
- rasengan 4y ago> For the benefit of blind and deafblind users, the above pictures, which are in fact just text, as everything in PDOS is, can be found in text format here. I like this and thought it was admirable. Good reason to be building something - to make the world a better place for someone.
- natas 4y agoHow "compatible" is it with MS-DOS? Can it run 16-bits DOS applications?
- rep_lodsb 4y agoOnly the 16 bit version, and probably not very well, you're better off running literally any other DOS instead. PDOS is all written in C with little or no assembly code (like FreeDOS, but unlike MS-/DR-/PTS-DOS), and worse than that the 16 bit version is compiled in the "huge" memory model which sort of simulates a flat address space. That means basically any pointer operation generates several extra instructions. Because the author feels that segmented memory should not exist and is something that can be ignored, even on 16 bit x86. The author is - IMO - a kook¹, who among other things is obsessed with UNIX and C90 (no other version!). His only problem with Linux/BSD is that they use communist free software licenses instead of being public domain, which supports TRUE capitalist freedom. His OS will be the one to restart technological civilization after a nuclear war. ¹ I might be one too, and I haven't even seriously started on writing my own OS, which will use segmented memory in the 80286's protected mode, be written exclusively in assembly for the kernel and Pascal for userland, and do it's utmost to not accomodate UNIXisms and the horrible C programming language, while still being compatible with DOS.
- lproven 4y ago> The author is - IMO - a kook¹, From many long threads on the Hercules/OS380 list, I would have to agree with you. I suggested many profitable, interesting, relevant lines of research he should read about. Not use, even, just investigate, as they were highly relevant to his plans. Nope. They were all dismissed as evil possible communist mind-poison. :shrug: In the end, I just left the list, which I almost never do.
- kerravon86 4y agoThe huge memory model supposedly has a 4% overhead in practice, cited by someone who did such programming under OS/2. Personally I wasn't able to detect any slowdown at all, which is not surprising, because you are normally expected to be bottlenecked on some application doing some calculation, not the OS. I am not aware that I have any obsession with Unix. For PDOS/386, PDOS/86 and PDOS-generic I use an API inspired by MSDOS. For z/PDOS I use the MVS API. I specifically don't want anything to do with Posix which mandated fork() but didn't provide for simple memory allocation.
- DeathArrow 4y agoLooks insane.
- peter_d_sherman 4y ago>"PDOS/386 is good enough to run BBS software. But instead of using modems to exchange mail packets, data can be transferred using bluetooth, USB stick, or potentially the internet (email, Discord, Facebook)." What an interesting idea! Using a social network to store and forward data packets for a BBS -- which is in effect, another miniature social network...
- stuaxo 4y agoDoes this run windows apps, I seen to get the idea it does from that text ? If so, how ? - via Wine, HX DOS extender or it's ow. implemention?
- kerravon86 4y agoOwn implementation of MSVCRT.DLL (C library - just C90) and KERNEL32.DLL (subset) too, that do 32-bit MSDOS-like calls.