22 replies to this topic

[Liraal]

will, hacking is not fun when it's being conducted by the way of client hacks that allow you to make a copy of a terminal and do with it whatever you want and the change will affect the original as well. There is NO protection against it, of which I am sure because my software got hacked, possibly without even physical access. THAT is what I am against, not in-game hacks (which i quite like), but adding a writable ROM is like giving a griefer a ton of TNT. It's not my call to make anyway, but I am just stating my point. And about the bootloader, you an easily ban items from your server, but you cannot ban a part of code of a mod.

[StrangeWill]

Liraal, on 19 March 2012 - 08:27 PM, said:

do with it whatever you want and the change will affect the original as well.

Oh yeah, you never should be able to edit any shared resources such as the ROM directory that is automatically shared. If machines were to get EEPROM it would have to be on a per-machine basis.

[PatriotBob]

It's not a far cry from the current setup.

Right now we have os code, term macros and other stuff shoved in BIOS.lua. what I suggest and have done for my setup. Is made BIOS do little more than look for potential boot devices. Disk the hdd them rom. Then boots the first available in that list. After that its the boot loader then to the os itself.

Sure it's 2-3 more files in the boot process but the added seperation means that if I don't like the standard included os I don't have to use any of it. No shell, no os.shutdown override in BIOS... etc...

New os installs just drop an image in /boot, background services are fired from /etc/init.d and then the shell.

It's a lot more steps but they're small and it makes it flexable.

Oh and most importantly everything is properly environmented off and in pcalls... so regardless of any failures in the system ALL coroutines are finished and cleaned up before shutdown.