To view parent comment, click here.
To read all comments associated with this story, please click here.
I'm planning to give it a try. My attempt this morning failed, but that's apparently because VirtualBox and Syllable isn't a great match.
With regards to reinventing the wheel, there is a wheel and if too much stuff is just ported you end up with another wheel and then I wonder why bother if there already was a fine wheel. In this case the first wheel is called Linux.
Maybe I should try Syllable first, because now I see all these open source projects that are also on Linux, giving me the impression it's all the usual suspects running on a different kernel.
There have been and are a number of "operating systems" that are just the Linux kernel, GNU stuff and then some small twist. If Syllable presents me with a bash shell and vi I will get a Linux feeling.
But okay, maybe I should try it first.
Again, Syllable Desktop is built on its own kernel, not the Linux kernel.
VirtualBox works, but needs to be configured right. Syllable doesn't support SATA, so you need to set VB to an IDE disk.
Here's an image in standardised OVF format, generated by VMware, if that helps:
https://docs.google.com/open?id=0B-dRFgFxR1iJOEtySWJ5NWFBMXc





Member since:
2010-06-09
You only have to start Syllable once to experience that it's not Linux. Why don't you give it a try?
Syllable's concept has always been to be an excellent base to port existing open source software on. Syllable is a complete stack of its own: kernel, driver framework, application server, multi-media server, user-space toolkit, and a collection of native apps. Around that skeleton, by now more than 99% of the code is ported. How do you suggest we arrive at end-user functionality if we would reinvent the wheel for everything?