The Future for TBOS, Part II

First, I'd like to say that if anyone wants to, feel free to link to us in your forum signature somewhere with this dynamic userbar: http://designer.userbars.com/dynubd1742.png

Second, to discuss the future. Recently, in the Elite Café, I said I was thinking of dropping support for TBOS (16) and rewriting TBOS32 in C. Well, I'm certainly doing the second, and I'm actually thinking about fulfilling the first. I find TBOS to be extremely insecure and basically a bad MikeOS clone. If someone wants to continue development of TBOS, speak now or forever hold your peace.

No, I swear, it will never ever ever ever ever ever ever ever ever happen again.

... ever ever ever ever ever ever ever ever ever ...

This will be the final note before the release of TBOS 1.1.0, I promise. I hope to have it out and ready by Sunday night (PST.)

Oh, hey, look! Another todo list!

• TBOS 1.1: FIREY ANVIL r0, hash 0.4
• TBOS 1.2: multiuserness fixed, FIREY ANVIL r1
• TBOS 1.3: hash 1.0 (oooh, colours)
  
• ........
  
• TBOS 2.0: some simple cross-compiler (probably BASIC)
  

I appear to have a new plan.

I've started re-implementing FIREY ANVIL (which was lost after a complete TBOS failure scare that turned out to be a bad segment register) and it should be done and in Python) to make FIREY ANVIL entries for TBOS files.

The kernel and loader must stay FAT files, as I don't think I could write FIREY ANVIL routines in the three or four bytes the boot sector has left :P

Ahh well, off to school.

An O RLY? Book...

http://www.oreillymaker.com/link/25072/tbos/

WHOA!

---

[TroyMartin] my plan is as follows: rewrite part of the FAT12 code for 1.2, then write a nice little FS in 1.3
<pc[work]> ah nice
[TroyMartin] I was also thinking of having the special FS be the main TBOS filesystem, just using FAT12 as a "container" of sorts
[TroyMartin] FAT12 doesn't really do much justice :D

---

A little snippet from a discussion in #pedigree on freenode. In all honesty, I don't like Microsloth's FATty file system, and I originally intended to use something completely different, but FAT stuck with the history of TBOS.

Whatever the TBOS filesystem will be called (the codename is Firey Anvil), I plan to use FAT12 as a container for either Firey Anvil files or the filesystem itself. I'll be uploading spec sheets as I write them.

I have seen the future...

...and it involves a rewrite!

I'm planning on releasing TBOS 1.1 this fine May weekend and then doing a bunch of rewrites to important/bloated/copied pieces of code (for example the entire k_fs.asm.) I'm also hoping to pump out a multi-user system for TBOS 1.x by the end of the month.