Talk:FSG-3 Community Release

From OpenFSG

Jump to: navigation, search

Working title

Suggestions:

neXtNAS - no acronym but the X for Xperimental, next as in the next development stage

openNAS - credit to the open source community

C.R.O.S.S. - acronym for Community Release(d) Open Source Software

Nift-e NAS - acronym for New & Improved Firmware Thingy(?) - Enhanced (nifty meaning something like clever, -e as in electronic -e mail etc.) --Admin2 23:54, 13 July 2009 (CEST)

I think the name should have 'FSG' included, because of Freecom Firmware is very special. --Jo-master 18:50, 15 July 2009 (CEST)

OpenFSG ? --Admin2 00:20, 16 July 2009 (CEST)

why not. openfsg is very easy. --Jo-master 10:07, 16 July 2009 (CEST)

OpenFSG gets my vote. Says it all, really. And the name is already established right here. Kenpem 10:29, 17 July 2009 (CEST)


ToDO

We should force to get the newest sourcecodes from freecom. It is really impossible to don't publish the code under GPL license. If freecom don't publish all actual code (should be 4.5.3 ) we should call the FSF cause of license-violations!!! --Jo-master 09:03, 7 August 2009 (CEST)

Good News: Freecom publish Sources of 4.4.5 Now i hope they will publish 4.5.0.8 soon. I will start to compare it.

  • overwork whole build-system (begin at basics): currently at work - 80% done
  • add all required software (all software of freecom firmware, but new versions and building directly from upstream packages like optware do)
  • add a new configuration system and web-interface (until this, try to use the old one)

developer-todo: http://openfsg.svn.sourceforge.net/viewvc/openfsg/trunk/TODO?view=markup

Current Status

  • i created a sourceforge-project: https://sourceforge.net/projects/openfsg/
  • i start to overwork the firmware build-process (make it more generic)
    • include kernel into firmware
    • include toolchain into firmware
    • change hard code paths to make it possible to compile wherever you want
    • disable all additional software (at ./user/ folder), because of required reconfiguration. 
freecom had preconfigure all software with hard-coded paths, which is very bad. we should only preconfigure required basic-software but also here with dynamically paths and all other additionally software should be build generically.
  • overwork whole build system (also all basics)
    • done only application-config system should be rebuild. but not necessary now


developer-changelog: http://openfsg.svn.sourceforge.net/viewvc/openfsg/trunk/changelog?view=markup

Retrieved from "http://www.openfsg.com/index.php/Talk:FSG-3_Community_Release"
Personal tools