trn

23 ms·

1.
by trn 1mo ago
While I'm not necessarily 100% anti-AI, it would completely eliminate all the potential for learning and any "fun" from this project.
2.
by trn 1mo ago
Yes, DR-DOS/Novell DOS 7 has a full 386 preemptive multitasking kernel and a decent API, which was essentially unused, with a few exceptions. See https://web.archive.org/web/20160809210402/http://www
3.
by trn 1mo ago
Actually, while the TPA is "flat", the OS model is using only segmentation for protection and not paging currently. Just the segment is quite large:)
4.
by trn 1mo ago
Thank you, as this is my project. As I said in the README, it's as much of a learning experience as it is a "practical" project. Using AI would eliminate the fun.
5.
by trn 1mo ago
Yes, currently the system boots from a floppy disk (stage1 -> stage2 loader), which then loads the OS (CBIOS/BDOS/CCP) and an (384K) initial ramdisk, and currently runs out of memory, so once the OS is booted the disk can actua
6.
by trn 1mo ago
Hi there, this is my project. And yes, you are essentially correct. It can actually work in a little less than 2MB, but this was done this way for simplicity, and to avoid, for now, what would be a more complicated memory map and paging r
7.
by trn 4mo ago
We also have a new CP/M-86 emulator at https://github.com/johnsonjh/emu2-cpm86
8.
DPS8M Performance(dps8m.gitlab.io)
2 points by trn 1y ago|0 comments
9.
by trn 2y ago
Multics MR12.9 is under active development. The current release is MR12.8, released August 8, 2023: https://multics-wiki.swenson.org/ . While Multics no longer commercially supported, many of the current developers were pr
10.
by trn 2y ago
While we do want to support GCOS, it'll be GCOS-3, and that is if we can find system tapes. We are actually planning another blog post soon that will touch on this. Now, Multics does have GTSS (GCOS Time Sharing Simulator), which
11.
Hardware FPGA DPS-8M Mainframe and FNP Project(dps8m.gitlab.io)
2 points by trn 2y ago|0 comments
12.
by trn 3y ago
> you're not allowed to add additional usage restrictions to GPL software SIMH is not GPL'd software.
13.
by trn 3y ago
I'll give an unpaid plug to https://www.softintegration.com/ for their Ch product, which is beyond excellent (and has existed for a very long time.) Clang-Repl/Cling is, however, nice to see, especially as it is
14.
by trn 3y ago
We should also mention that the PDF documentation has some graphics showing how these components are (physically) connected together at https://dps8m.gitlab.io/dps8m-r3.0.1-archive/R3.0.1/omnibus/... (pages 4
15.
by trn 3y ago
Yes, I was simplifying a bit :) Those who are interested should take a peek at https://dps8m.gitlab.io/dps8m/Overview/#supported-components to see all the various components that make up the DPS mainframe system.
16.
by trn 3y ago
Perhaps, however, SIMH ( http://simh.trailing-edge.com/ , https://opensimh.org/ ) also calls itself a simulator rather than an emulator. Six of one, half dozen of the other, I guess!
17.
by trn 3y ago
Yes, this interpretation is correct. It should be noted that not all of the hardware is strictly "emulated" (or simulated, if you prefer that term) in the traditional sense of interpreting each hardware instruction. The DPS in
18.
by trn 3y ago
See the homepage at https://dps8m.gitlab.io/ as well for more details.
19.
by trn 5y ago
I will confirm that Vile is an excellent editor. I don't know if I'd consider it a vi-clone, because the vi-ness is kind of skin-deep, but it's performant and works well. (In school, early 90's, there was a large vile f
20.
by trn 5y ago
Do you have a summary of those changes or a repo up anywhere? If they are general-purpose you might consider sending a PR upstream to n-t-roff
21.
by trn 5y ago
It should be simple, mostly fixes and no major features or refactoring.
22.
by trn 5y ago
pEmacs is "even better" for minimalists. https://github.com/hughbarney/pEmacs Stripped -Os build using link-time GC on Linux x86_64 glibc: 30 KB pe* Compare to portable mg: 132 KB mg* Ope
23.
by trn 5y ago
OpenVi uses only secure functions (snprintf, strlcpy, etc.) as a matter of policy. This may lead to a more secure editor for untrusted files, but it depends on how careful the other editors are. (I haven't examined them at that level.)
24.
by trn 5y ago
I dogfood OpenVi and use it for OpenVi development, however, 99% of my normal programming workflow is (terminal-based) NeoVim. The other 1% is Eclipse or VSCode ... and I have VSCode setup to use the embedding functionality of NeoVim.
25.
by trn 5y ago
Of particular note, the lack of `expandtab` in Nvi and Traditional vi may be more of a showstopper than lack of multibyte glyph rendering for many.
26.
by trn 5y ago
Cleanly doing UTF-8 support (the "right" way) is planned but is certainly non-trivial ... for example, see: https://www.openbsd.org/papers/eurobsdcon2016-utf8.pdf and http://www.usenix.org/eve
27.
by trn 5y ago
To give a quick overview of ':set'-able options (`:set all` output) of the various editors that derive from 'nvi' ... [no Nvi2 here ... yet] ... Nv1 [nvi-1.81.6-45-g864873d3 (2022-02-21)]: noaltwerase nocomment
28.
by trn 5y ago
Don't confuse OpenVi/OpenBSD-vi, nvi1, and nvi2. These are all different programs that share the same heritage. OpenVi is derived from OpenBSD vi, which derives from nvi version 1.79, released in 1996. There has been 25+ years o
29.
by trn 5y ago
https://copyfree.org/standard/licenses is worth a look
30.
by trn 5y ago
Using Carsten Kunze's actively maintained continuation of Gunnar Ritter's (outstanding) traditional ex/vi project is highly recommended. See https://github.com/n-t-roff/heirloom-ex-vi/ . The parent p

More ›