Katze
@IanSeyler here, have some [inline assembly](http://doc.rust-lang.org/nightly/book/inline-assembly.html).
So, you want a syscall (?) to send a memory range directly onto the network?
It is a buffer, it will be hard to impossible to remove that, unless you let the application specify its own.
Is the buffer used for more than one packet?
I think it would be an overall good solution if the application could specify it's own handlers for all interrupts (without overwriting the system ones). That would solve many problems....
Sorry, but I haven't had time yet to have a deeper look into BareMetalOS. Isn't there a Zero-Copy network "stack" then?
I think the shell should be "outsourced" in it's own repo where it can be developed as a general purpose app. This has been discussed at #40 and @primoz made...
_My_ intent was to have a shell, which is a shell, and a loader, which is a loader, both completely indepentently developed. So we would have the kernel being minimalistic....
@scherrey Sorry for making that ambiguous. I edited that comment.
We can already load an executable. Only a binary, but an executable one. So if someone make a program called "loader" that reads some e.g. elf file, parses and loads...