Izaya

As the MultICE networking stack just gained support, I'd like to reserve protocol 0x1000 (4096). I'll note it uses broadcasts for its stuff though.

So uh, I've ended up running a server. It's hosted in Hell (Australia) on a residential line.

It's designed to be a wasteland server, with customised world generation and a custom modpack. There are resource drops at random in order to allow plants to exist. Fun stuff.

The server specs are:

Lenovo ThinkPad T400

Core 2 Duo P8700 2.53Ghz

4GB DDR2 RAM

8GB flash drive as /

8GB flash drive as /mnt/mcsrv

More info can be found here

So I added an init file for Titan to amie - untested, but it should work.

It loads the kernel into RAM and downloads the useful init files to the tmpfs - not that you can do anything with amie yet, but such will happen eventually

I tend to lose my timetable for school. This is not good. So, I wrote something to keep a digital copy of it.

I present to you: TimeTable Manager.

It uses my syscall API, so it will run on both micrOS v2 (when it is released) and OpenOS.

You can get it at http://shadowkat.tk/files/ttman.lua - you'll want to have syscall.lua in /usr/lib, or if it's in /boot/, remove the require line.

Mmmkay, I'm done here.

As I'm working on some stuff for MicrOS, I decided I wanted to get some stuff going, even it it was very limited. So I implimented the very basic syscalls from MicrOS into a library for standard Lua, and by extension, OpenOS.

Basically, it has 4 syscalls: writeln, write, read, fs_open, and they're all pretty self-explanatory, though you can read the docs at http://shadowkat.tk/projects/os/syscalls.php

Now, the actual program? http://shadowkat.tk/files/syscall.lua Ideally, dump it in /boot/ to be loaded later, then use the syscall function. Failing that, require it and use the syscall function.

Yep, I'm done here.

I noticed v 1.1. I really like the event functions you implemented. I've come upon a bug in skex.

1.insert code into buffer from client

2.execute the buffer

3.clear the buffer

4.re-enter insert mode and enter a line into buffer.

5.crash- dont know why...

 

Thanks for skex. I'm learning a lot from your stuff

Well, v0.1.2 is out.

The bug you mentioned is probably accidentally fixed.

I changed the buffer and line number to be global rather than local, in order to support read and write to/from the EEPROM and to/from the buffer. There's snippets for abusing this feature on the project page.

I'm really happy I could help you, not often someone tells you thanks for something.

Oh yeah, I incorporated your changes to the client program, too. There will be improvements to it soon, but I'd like to make the EEPROM-resident capible of supporting identification of some kind. Anyway, enjoy.

As drones have recently been released (ie latest dev build), it became apparent that there needed to be an OS that is even more embedded than MiniOS. Even more embedded than MicrOS. This has been done.

I present to you:

skex-BIOS

skex-BIOS is a port of my not-very-popular line editor skex (ShadowKat Editor eXpanded, the sequel to sked) to fit into an EEPROM and be accessible over a network. skex-BIOS uses some code Sangar posted for controlling robots, mainly the I/O and client program for OpenOS, but with far more functionality: on the remote end, you have a full line editor that can execute code from the buffer, the ability to re-flash the EEPROM for updates or permenant deployment of a program, and on the client-side, you have a non-blocking remote terminal that allows you to have multiple lines of text coming across your link.

Note: In this state there is no security at all on the link, so someone could easily hijack your drone or microcontroller. Plan accordingly, especially change the port used.

Anyway, you can find skex-BIOS at my site: https://git.shadowkat.net/izaya/skex-BIOS

Old link: http://web.archive.org/web/20150317135050/http://shadowkat.tk/projects/skex-BIOS/

Unfortunately, yes, the forums aren't very active, but most of the stuff goes on in IRC anyway, so yeah. I haven't posted some of my stuff because I cba, and that if people want it, they can ask me on IRC.

Don't get me started on AfterLifeLochie though... Totally not thinking of stabbing that guy.

That's the only thing I know that can do that in CC anyways. I don't know much about the OC networking API.

Ah, you see, in OC, the networking cards can do raw TCP, so no external 'peripherals' needed.

Why Kilobyte's peripherals?

Any chance we could get an API or something for rendering images outside of the program? I have uses for such things.

Up to 3.4 now, oh yeah, I re-arranged the chapters. 1 - 7 are now 1.1 - 1.7, chapter 8 is now chapter 2 and chapter 9 is now chapter 3. \o/

Also, back to the original site.

Some data recovery thing can do too.

Also, make SSDs that are smaller (512k,1m,2m), but don't fail

Nonononono, In my opionion, SSDs should be cheaper but more likley to fail. I have a computer running off a hard drive, and I've had said computer and drive since 2004. I had a school laptop with a SSD, and it failed within 6 months. Perhaps, HDDs could fail randomly, but it would be unlikley, but SSDs would fail after a certain amount of write cycles, so if you used them for archiving and/or running the read-only parts of a system off, it wouldn't kill the drive.

Due to the lack of an editor (that I could find), I adapted my sub-1k line editor for miniOS.

I'd like to note my dislike of drive lettering, but there are those that like it, and I'd suggest sticking with it. If directories worked on drives, it would be significantly more usable.

Aaanyway, here's my MiniOS version of sked: http://pastebin.com/622z9agf

I've decided to post the logs from third person hour on the forums.

This is #oc's grand tradition, and it might have even been going on for a full month by now!

[02:01]	<PsychokenesisKat>	Such a grand tradition we have created.
[02:01]	<DeanIsaCat>	^
[02:01]  *	Vexatos	likes Traditions
[02:02]	<DeanIsaCat>	No other channel has this
[02:02]	<DeanIsaCat>	we are legion
[02:02]	<DeanIsaCat>	we do not forget

Am I the only one that doesn't see why you can't just have your programs handshake with the other computer and then communicate as you please, over whatever port you wish? Your programs should be able to ignore other transmissions over the network that aren't intended for your program, anyway.

Of course, but even with real TCP programs, you need to start talking on a port, then it can tell you which port to use.

Before implimenting higher-level protocols, you'll want a lower-level way to make your messages appear as a stream, just like TCP sockets, right?

That's where this comes in.

ocsocket makes modems behave like TCP sockets.

Functions:

ocsocket.socket(port,address)

That will return a socket object.

Socket object functions:

obj.init()

Must be called to make a socket work.

octcp.isData()

Returns true if there is data to be read, false otherwise.

obj.read(i)

i is a number or character, if it's a number, it will read that many characters. If it's a string, it will read until that character appears.

obj.write(string)

Sends string to the target computer

obj.close()

Closes the socket and stops listening.

And the download?

http://pastebin.com/vyW5k820

Alternatively:

pastebin get vyW5k820 ocsocket

I reccomend you place it in /usr/lib

That is all.

Bai o/

Oooh yeah, that's right... User ports... Derp. Uh... 60, 61 and 63?

If ports are to be claimed, please reserve port 20 and 21 for FTP, and port 23 for telnet. I would also like to reserve port 101 for myself.

EDIT: 25 for SMTP

EDIT: 109 and 110 for POP.

EDIT: 115 for Simple File Transfer Protocol

How recent is your program that uses port 42?

On the 25 of March, I published a program that used port 42 for mesh networking and message forwarding. Therefore, one assumes I would have the right to use that port, not you. Though really...

None of us really have the right to write programs using ports below 1024 unless they use the relevant protocol. 1024 and above are allocated-on-request ports.

For example:

42: ARPA Host Name Server Protocol

9001: ETL Service Manager

Port 1-32 are commonly used protocols that have mostly been around for ages.

User ports should be 49152–65535, not 1-32. In fact, I may modify my programs to use different ports to comply with said standards._{What we really need though is something that works like a socket, not like what it currently does.}

Okay, I'm done. Bye

^{Failure to comply will result in a competing port list that complies with real-world standards.}

Just realised this page still had the old link. Fixed that.

Also, up to 9.2 now.

 

No computers from 2015 onwards? What kind of horrible future is this?!D:

That means my education will only leave me a defunct psychologist! I don't have the skill sot build cognition without a machine to build it on :/

 

Don't worry, remember, there is a form of time travel in here.

If anyone cares, I'm up to 8.7 now.

Okay, after 2 days of on-and-off testing, it seems to at the very least run. Enjoy

Chapter 7 is out! Also, I decided to have some fun and make this: https://dl.dropbox.com/u/79548926/derp.dfpwm It contains hints for the next chapter