Quote:
Originally Posted by Nyoxi
I think having good experience with Linux and shell scripting is essential at this point. What you (or somebody) could do to help is: - Look for the buildroot that we could use. Something that would be easy to set up and which would provide good support for writing package build scripts. I was thinking about Openembeded. Taking the framework from the OpenWrt and strip it down to things that are necessary or useful to us is also an option. Or if someone has any other tips feel free to entertain me.
- Maybe write an init script that would load the necessary modules and mount the loop file. It might do some sanity checks to make sure it's safe to mount the loop file or check for some file in /mnt/us that would allow user to skip the mounting. (Or maybe even something else ... thoughts/suggestions?)
|
I'll have a look at those links. I don't have much experience with C++ GUI programming (I've started as Delphi programmer as a hobby, and now I'm Python guy on my work).
I can also write basic init.d scripts (and most of them are really basic
), however I think we should refer to them as "upstart" scripts (KT uses upstart, right?).
What I propose is having some kind of site/wiki that describes what needs to be done and advertise this somehow so people could go there and help.
BTW, as for "stripping the framework" from OpenWrt (I didn't read the links yet) - is it really needed to be stripped? I think if it would have some more MBs it's okay - we can afford this at least at the start because we'll save developers' time (and seeing we don't have many developers out there I think it's really critical to spend as little time as possible to get this working safe & reliable).