3 ms·
You can't say something interesting like that without a link to a Go example for the rest of us to see the similarities too. :)
by dbaupp 13y ago
You can't say something interesting like that without a link to a Go example for the rest of us to see the similarities too. :)
- _mhr_ 13y agoWell, there's this: http://code.google.com/p/gofy/ http://code.google.com/p/gofy/
- adsche 13y agoI was interested in this as well and found this commit[1] by Russ Cox. README has details on running it inside bochs. [1] http://code.google.com/p/go/source/detail?r=ffbf0900a2 http://code.google.com/p/go/source/detail?r=ffbf0900a2
- aray 13y agoOther commenters beat me to the first two examples, though there's more. GoFY (which hilariously I'm a contributor on) was probably the closest analogy; it booted on x86. Russ Cox's did as well, but it was removed from the go tree years ago when it bitrotted. Really it boils down to 1) custom linker scripts/targets and 2) a custom "OS" target that emulates syscalls/etc I've done it a couple times (on ARM-based embedded devices), I end up throwing it out every time. Should get a proper writeup I suppose.
- dbaupp 13y agoHm, those two seem vastly more complicated, with extra C and ASM rather than just plain Go.