Who the hell put the idiots who can produce such ideas in charge of MeeGo compliance specs?
I'm starting to genuinely feel that I would be happier sinking years of my life into recoding closed-source components of Maemo 5 and porting that onto some more advanced hardware than switching to MeeGo, in the long run, with all that I've heard about MeeGo so far. Of course, I suspect it's that human nature thing of disliking things that are _different_ that what you're used to, but still... *Ughhh...*
Speaking of recodes, I've started working on recoding /sbin/preinit. Honestly, I'm not sure how legally defensible 'recoding' something is when the code is in plaintext already and you have little means of reverse engineering available to you (barring modifying the code you're reverse-engineering to pause-for-manual-interaction or display/record the state of the system at every step), but I've researched around and afaik many version of open source distros of linux-based firmware don't even bother with the legalities to this extent - i.e. lots of community router linux firmware packages will still redistribute 'non-redistributable' shell scripts from the original firmware maker. At least here I could say that I'm genuinely understanding what the boot process is doing, and then writing code accordingly, not just copying over code chunks.
I think I'm also going to recode this "key_pressed" utility that Nokia made - iirc it's closed source, but it's exceedingly simple and it bothers me to be using a closed source binary for what is effectively a "read -n 1 -t $2" command as a binary.
Who the hell put the idiots who can produce such ideas in charge of MeeGo compliance specs?
I'm starting to genuinely feel that I would be happier sinking years of my life into recoding closed-source components of Maemo 5 and porting that onto some more advanced hardware than switching to MeeGo, in the long run, with all that I've heard about MeeGo so far. Of course, I suspect it's that human nature thing of disliking things that are _different_ that what you're used to, but still... *Ughhh...*
Speaking of recodes, I've started working on recoding /sbin/preinit. Honestly, I'm not sure how legally defensible 'recoding' something is when the code is in plaintext already and you have little means of reverse engineering available to you (barring modifying the code you're reverse-engineering to pause-for-manual-interaction or display/record the state of the system at every step), but I've researched around and afaik many version of open source distros of linux-based firmware don't even bother with the legalities to this extent - i.e. lots of community router linux firmware packages will still redistribute 'non-redistributable' shell scripts from the original firmware maker. At least here I could say that I'm genuinely understanding what the boot process is doing, and then writing code accordingly, not just copying over code chunks.
I think I'm also going to recode this "key_pressed" utility that Nokia made - iirc it's closed source, but it's exceedingly simple and it bothers me to be using a closed source binary for what is effectively a "read -n 1 -t $2" command as a binary.
Do not be afraid of lawyers, just code!
Seriously, thanks to people like you the N900/Maemo community has a chance to survive post-Nokia.
