Difference between revisions of "Recreate the Openlink distribution using buildroot"

From NAS-Central Buffalo - The Linkstation Wiki
Jump to: navigation, search
(added "why do we need this?")
m
 
(9 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 +
{{Template:Articles}}
 
<table align="right"><tr><td>
 
<table align="right"><tr><td>
 
http://buildroot.uclibc.org/images/busybox1.png
 
http://buildroot.uclibc.org/images/busybox1.png
Line 10: Line 11:
 
== Why do we need this? ==
 
== Why do we need this? ==
 
=== Problems of the current situation ===
 
=== Problems of the current situation ===
* You might noticed that there are several different models of Linkstations out there. There are ppc-based Linkstations (LS1, HG, HS) and there is the mips-based LS2. We have different hardware that needs slightly different drivers and different cross-toolchains.
+
* You might noticed that there are several different models of Linkstations out there. There are PPC-based Linkstations (LS1, HG, HS),the LS2 is MIPS-based and the Linkstation Pro will be based on ARM. We have different hardware that needs different drivers and different cross-toolchains.
* The LS1, the HG and the HS are quite similar regarding the directory-structure. All shares are at /mnt/ and the usbdisks are mounted to /mnt2/usbdisk* . The LS2 is different, shares are at /mnt/hda/ and usbdisks are mounted to /mnt/usbdisk* (-> '''correct this if it is wrong!''' [[User:Mindbender|Mindbender]]). So we even have slightly different linux-distributions that make it hard for us to answer support questions if you do not know what model the other one has.
+
* The LS1, the HG and the HS are quite similar regarding the directory-structure. All shares are at /mnt/ and the usbdisks are mounted to /mnt2/usbdisk* . The LS2, and some HG models, are different. Shares are at located /mnt/hda/ and usbdisks are mounted to /mnt/usbdisk*. So we even have slightly different linux-distributions that make it hard for us to answer support questions if you do not know what model the other one has.
 
* If someone currently wants to modify OpenLink for all LS models, he would have to redo the same modification for all OpenLink-Images and has to upload and release this images. This means everything would have to be done 4 times....As not many of us have more than one model this frightens many of us and thats why there is so little development. It is possible that the same version of OpenLink can have different bugs as redoing the changes is a manual process...not every solutions is documented.
 
* If someone currently wants to modify OpenLink for all LS models, he would have to redo the same modification for all OpenLink-Images and has to upload and release this images. This means everything would have to be done 4 times....As not many of us have more than one model this frightens many of us and thats why there is so little development. It is possible that the same version of OpenLink can have different bugs as redoing the changes is a manual process...not every solutions is documented.
 
* OpenLink was only developed by one person, frontalot. Currently OpenLink is only developed by mindbender who has only a LS1. Commiting modifications is not really possible.
 
* OpenLink was only developed by one person, frontalot. Currently OpenLink is only developed by mindbender who has only a LS1. Commiting modifications is not really possible.
 +
 
=== What would the buildroot-project change? ===
 
=== What would the buildroot-project change? ===
 
* Only model-specific-stuff regarding the hardware has to be done to make OpenLink work on a new model (currently the HS).
 
* Only model-specific-stuff regarding the hardware has to be done to make OpenLink work on a new model (currently the HS).
Line 30: Line 32:
 
To get the project install [http://subversion.tigris.org/ subversion] and type:  
 
To get the project install [http://subversion.tigris.org/ subversion] and type:  
  
: ''svn co http://svn.artage.com/svn/linkstation/trunk/''
+
: ''svn co http://svn.artage.com/svn/linkstation/trunk/openlink''
  
== Information ==
+
== Packages Required ==
: [http://forum.linkstationwiki.net/index.php?action=vthread&forum=7&topic=959  Forum Discussion: Buildroot!]
+
: [http://www.kegel.com/crosstool/ Crosstool]
+
: [http://buildroot.uclibc.org/ Buildroot]
+
  
 +
The additional packages which are required to build the environment are:
  
[[category:Projects]]
+
*libncurses-dev
 +
*bison
 +
*flex
 +
*texinfo
 +
*zlib1g-dev
 +
 
 +
== Information ==
 +
: [http://forum.nas-central.org/index.php?action=vthread

Latest revision as of 02:42, 11 September 2007

busybox1.png

Contents

Information

This project aims to recreate most of the Openlink distribution using buildroot so that it is possible to easily cross compile the whole of Openlink on a Linux workstation. This will provide a clear cut way of maintaining Openlink and be useful to those who want to customise a Linux distribution for their own projects.

Buildroot has been patched to use toolchains produced by crosstool so that it is possible to use glibc instead of the usual uclibc support provided by buildroot. Note that this is intended as a way of maintaining Openlink, not as a package management system.

Why do we need this?

Problems of the current situation

  • You might noticed that there are several different models of Linkstations out there. There are PPC-based Linkstations (LS1, HG, HS),the LS2 is MIPS-based and the Linkstation Pro will be based on ARM. We have different hardware that needs different drivers and different cross-toolchains.
  • The LS1, the HG and the HS are quite similar regarding the directory-structure. All shares are at /mnt/ and the usbdisks are mounted to /mnt2/usbdisk* . The LS2, and some HG models, are different. Shares are at located /mnt/hda/ and usbdisks are mounted to /mnt/usbdisk*. So we even have slightly different linux-distributions that make it hard for us to answer support questions if you do not know what model the other one has.
  • If someone currently wants to modify OpenLink for all LS models, he would have to redo the same modification for all OpenLink-Images and has to upload and release this images. This means everything would have to be done 4 times....As not many of us have more than one model this frightens many of us and thats why there is so little development. It is possible that the same version of OpenLink can have different bugs as redoing the changes is a manual process...not every solutions is documented.
  • OpenLink was only developed by one person, frontalot. Currently OpenLink is only developed by mindbender who has only a LS1. Commiting modifications is not really possible.

What would the buildroot-project change?

  • Only model-specific-stuff regarding the hardware has to be done to make OpenLink work on a new model (currently the HS).
  • Providing support gets much easier as all images would have the same directory structure and wwould look the same.
  • Changes only need to be done one time to the svn-repository. All images for all models compiled via buildroot after the change would have this modifications automatically. Bug fixing gets easy.
  • Several developers could maintain and develope the OpenLink-Distribution.

Buildroot is definitely the future of OpenLink. We need to get it working. Buildroot will accelerate development significantely. It will change everything much more to community-work instead of the current one-man-show.

Project Status

The buildroot project is still in the initial stages of construction. Currently it will not create a bootable image. If you want to contribute or try it out read the howto then checkout the subversion trunk.

Subversion Access

To get the project install subversion and type:

svn co http://svn.artage.com/svn/linkstation/trunk/openlink

Packages Required

The additional packages which are required to build the environment are:

  • libncurses-dev
  • bison
  • flex
  • texinfo
  • zlib1g-dev

Information

[http://forum.nas-central.org/index.php?action=vthread