Lmst

EEHEEHEE lotta good work on this today, I'm trying to build it up to the point of execing an /etc/init that reads a file to a lil hello world!!

acourse't I'm still in the weeds on all the stack swapping multiprocessing low level muck, arghh hate this parta this kinda stuff -- but i've gotten SO FAR hehehe gonna head back to it tomorry

(I'm now on the init branch if y'all wanna check progress on the codeberg >:3)

#c #rust #unix #ancientUnix #compiler #popix #c6t

Yeah, that v4 tape find was kinda neat!

I can't help but think, older sources may still exist, somewhere?

I mean, not just because I helped restore some (e.g. https://code.google.com/archive/p/unix-jun72/ USENIX presentation on such findings here, PDF of Toomey's 2009 on "The Restoration of Ancient UNIX Artifacts": https://www.usenix.org/legacy/events/usenix09/tech/full_papers/toomey/toomey.pdf) and some of those collaborators went even deeper, e.g. https://ui.adsabs.harvard.edu/abs/2010IAHC...32c..74T/abstract "First Edition Unix: Its Creation and Restoration" (from 2010) and because well, for the 50th Anniversary of UNIX, they booted up a system with a version supposedly dating back to 1969 "The Earliest Unix Code: An Anniversary Source Code Release" (2019): https://computerhistory.org/blog/the-earliest-unix-code-an-anniversary-source-code-release/

But also, this: "1971 Bob Fabry buys UNIX license for $99 to share with students" (from https://www.berkeley.edu/about/history-discoveries/ though, you have to click "Contributions/Discoveries" then click on 1977 and I'll note: there's a typo within the associated image of "FreeBDS" when I am pretty sure they intended to write FreeBSD" so y'know, maybe not the most accurate source of earlier provenance outside of Bell Labs? Still, definitely older than the University of Utah UNIX v4 tape from 1974).

#AncientUNIX #UNIX #Artifacts #SoftwarePreservation #History #OurStory

trying to be on here more often (again lol)

Back on my BS with my project to make a portable version of Unix V6 (from 1975) with a self-hosted pre-K&R C compiler, that could be released on anything that can at least simulate the memory model

Gonna start on a custom VM written in #Rust, but then port to the #C64 and probably also #ALtair8800!!

You can check out the progress on the kernel branch here: https://codeberg.org/popeyeotaku/popix/src/branch/kernel

Right now the compiler's almost done, with a bootstrapper compiler written in Rust. I'm about to start booting and bugfixing the kernel as soon as I extend the VM a tad

Still gotta gut the kernel by another several K, and write self-hosted assembler/linker package, and port userland. Also gonna write a custom YACC that uses less RAM

but it's coming along swimmingly!!!

#ancientUnix #C #Popix #C6T

I'd beened stalling on my #AncientUnix #Popix project, but it just got a big shot in the arm

I jus realized my #AncientC compiler had a bug where any initialized array came out twice as big as it was susposed to, fixing it has cut all my programs compiled in it by several K 😅😅

I was so worried about how on Eart' I was gonna slim everthin down enuf, now I don't gotta worry about any of that

so as a side project to my "port #AncientUnix Sixth Edition to 8-bit platforms," I've been noodling off an on for "port #AncientUnix Seventh Edition to the #C64 with a RAM Expander cart" and I think I've finally noodled up how that will work successfully

acourse't now i'm having weird issues wit simh to get a Unix V7 running to work more on it 😅😅 (if I know any Unix7 folks interestid in helping hmu hehe)

I'm still hacking away on my #AncientUnix #Popix port, and it's wild how you really can just go look up the source of something to check its behavior or add something you need!

more importink #POPIX #ANCIENTUNIX NOW CLEARS THE BOOT PROCESS

(still not executing the user program but that hokey crap!!!)

NOTHER BUG HECKT IN #AncientUnix #Popix

hey, did you know if I want to drop the stack by `size` bytes, i shouldn't use the `sp=*pc*-size`, that might produce some memory bugs

PFFFFT it turns out me #AncientUnix #Popix bug was caused on accouna me #AncientC #C6T compiler didn't handle multi-dim arrays correck 🙃 thas all fix't now tho 💪💪

here's hopin for the next bug to be nicer as I recompile

boy i'd sure love it if this mysterious and otherworldly bug wud resolve isself thas wot #popix #ancientUnix

I'm getting a weird thin wit some pointer write going haywire that i gotta track down today, but I'm so excittid hehehe #popix #ancientUnix

I'll probably get thisk VM thin an mosta its userland together an releasked afore I make big headway on the 8bit ports, it shudint be TOO mucht work once't the kernel works

!!!!!!!!!!!!!!

(the TRAPk2's are clock ticks) THIS IS FAR ENOUGH IN THE BOOT PROCESS ITS STARTED SETTING UP THE ROOT DRIVE #popix #ancientunix

#ANCIENTUNIX UPDAKE!!!

it hangs affer thisk point but me #Popix port of Unix V6 is now gettink *pretty* far inter the boot process!! :D AAAA

im not saying it'll run very fast, an not all platforms will have proper multitasking --

but the big diffince between #Popix an nother #AncientUnix ports or 8bit unix clones, is the self-hostid compiler!

u get wanna these thins but theys not a lot to do on it, cuz it caint run modern unix sof'ware *an they's no internal dev environmink*

unix (esp afore it got so complicitatid) is a pretty smooth dev environmink, issa great bit to hav available

The #C6T #AncientC compiler has a dirt simple backend which't shud be pretty easy to port to a buncha CPU's, perfornanss aside

An' the #Popix #AncientUnix kernel has v lil in the way of system dependint routines -- the biggesk hurdle is figgerin up how yer gonna handle the stack whin getting into an out of the kernel. Once't thas finich't, they's jus' a baker's dozing small utiliky routines, an yer I/O drivers -- an yer set!!

well the last few days may have been hell, BUT i distracktid meself by working on me #AncientUnix #Popix #AncientC #C6T projecks!!!

For those who don't know, I'm porting Unix V6 from 1975 to 8-bit platforms like the C64 and Altair 8800.

To do thisk, I wrote a self-hosting 8-bit compiler for the pre-K&R version of C that Unix6 uses.

Thas actually finiched! An I puts together most of the kernel, and hav it testable on the Altair... but acourse't debugging it is a ***** and a half, so to heck wit it

The past couple days, I work't up a modern VM made espeshially for the C6T language, and just now got most of *its* kernel together.

Tomorry I'm gonner put together the last bits on the VM to interack wit the hosk environmink, get a tesk user program, an try bootin up the kernel!!

(the igea being the modern VM will be a *lot* easier to debug the kernel on hehe)

goddddd i dunno how y'all Z80 folks do it, i stg the bugs that've been hecking me on me #ancientUnix #popix port are THE DIVISION ROUTINE!! *never* had thisk trubble on 6502

i'm not actually on a Z80, the intel 8080 insted, but my garsh i dont like how me code looks on it, and right now it seems to be grabbink a return address insteda argymint sumwhere cuz its overwriting the code it returns to 🙃 (assuming ALL memory yaint partially borked)

Late night work on me #ancientUnix #popix port for #altair8800 , rewrote the interrupt system to work in #simh 😎sockem up 😎😎

Won't tesk it til tomorry, but lookout 😎

for those who yaint awares, I'm porting #ancientUnix Sixth Edition from '75, using a new pre-K&R #c6t #ancientC compiler I've written that's designed to be easy to port around to different platforms (especially 8 and 16bit ones)

It's *almost* running on the #altair8800 right now (it gets fairly far into the boot process before hanging), then I'm gonna work up a #commodore64 port

sighh i shud rewrit me #ancientUnix #Popix port to jus use the flat rst7 interrupt. it uses the #altair8800 vector interrupt board right now cuz I assumed simh wud susport it like the altairclone -- but nope.

I've beened back an fort' on wat to do, cuz bugfixing in simh is gonna be a *tad* easier than on a front panel

#AncientUNIX

Client Info