NSLU2-Linux
view · edit · print · history

Development.HomePage History

Hide minor edits - Show changes to markup

February 22, 2008, at 12:13 AM by rwhitby --
Changed lines 5-6 from:

See the make setup-host-debian or make setup-host-gentoo targets for a machine-executable description of the requirements for your build machine. I recommend Debian Etch (that's what I use - our official build machine uses that version). Most the of the core development team uses Debian or Gentoo.

to:

See the make setup-host-debian or make setup-host-gentoo targets for a machine-executable description of the requirements for your build machine. I recommend Ubuntu 7.10 (that's what I use - our official build machine uses that version). Most the of the core development team uses Debian, Ubuntu or Gentoo.

December 01, 2007, at 02:50 AM by Jon -- Comma to improve clarity
Changed lines 24-25 from:

If things stop working when they were working before removing the whole tmp directory is a very good place to start. Don't remove the downloads directory unless you start seeing weird failures in downloading. Even then just remove the downloads for the package which fails - if the package is obtained from cvs remove its directory from downloads/cvs too.

to:

If things stop working when they were working before, removing the whole tmp directory is a very good place to start. Don't remove the downloads directory unless you start seeing weird failures in downloading. Even then just remove the downloads for the package which fails - if the package is obtained from cvs remove its directory from downloads/cvs too.

November 19, 2007, at 01:46 AM by Alan H -- change openslug to slugosbe
Changed lines 9-11 from:

For OpenSlug firmware, use make openslug-image (recommended).
For all of OpenSlug (including lots of packages), use make openslug.

to:

For OpenSlug firmware, use make slugosbe-image (recommended).
For all of OpenSlug (including lots of packages), use make slugosbe.

June 16, 2006, at 10:57 PM by rwhitby --
Changed lines 18-19 from:

All commits, whether in Monotone (OE) or CVS (optware) need to use the commit guidelines.

to:

All commits, whether in Monotone (OE) or Subversion (optware) need to use the commit guidelines.

January 07, 2006, at 01:37 PM by jbowler -- Comments about removing tmp and downloads
Added lines 24-25:

If things stop working when they were working before removing the whole tmp directory is a very good place to start. Don't remove the downloads directory unless you start seeing weird failures in downloading. Even then just remove the downloads for the package which fails - if the package is obtained from cvs remove its directory from downloads/cvs too.

October 24, 2005, at 09:49 PM by jbowler --
Changed lines 16-17 from:

The Master Makefile will download and build everything that is required except the Intel code for the built in ethernet engines - you must download this yourself (see IntelSourceCode?). If there are sources missing from upstream sites, it *should* download them from the sources.nslu2-linux.org server - if not, then you can download them manually from there.

to:

The Master Makefile will download and build everything that is required except the Intel code for the built in ethernet engines - you must download this yourself (see DownloadingTheIntelSourceCode). If there are sources missing from upstream sites, it *should* download them from the sources.nslu2-linux.org server - if not, then you can download them manually from there.

October 24, 2005, at 09:48 PM by jbowler -- Intel Source Code link
Changed lines 16-17 from:

The Master Makefile will download and build everything that is required. If there are sources missing from upstream sites, it *should* download them from the sources.nslu2-linux.org server - if not, then you can download them manually from there.

to:

The Master Makefile will download and build everything that is required except the Intel code for the built in ethernet engines - you must download this yourself (see IntelSourceCode?). If there are sources missing from upstream sites, it *should* download them from the sources.nslu2-linux.org server - if not, then you can download them manually from there.

October 21, 2005, at 07:35 AM by rwhitby --
Changed lines 24-26 from:

When upgrading your kernel sources and rebuilding it is a good habit to remove tmp/{work,stamps}/{ixp,openslug*} (or unslung* if you are on unslung, or probably debianslug* if you are on debian).
Especially when going to a different kernel version it is possible that ixp has been changed. If you end up with a slug that seems to boot fine (led is green) it is possible that your ixp modules are not ok. This can a.o. happen when going from 2.6.14-rc2 to 2.6.14-rc3.

to:

When upgrading your kernel sources and rebuilding it is a good habit to remove tmp/{work,stamps}/{ixp,openslug*} (or unslung* if you are on unslung).
Especially when going to a different kernel version it is possible that ixp has not been recompiled to install in the new modules location. If you end up with a slug that seems to boot fine (led is green) it is possible that your ixp modules are not ok. This can a.o. happen when going from 2.6.14-rc2 to 2.6.14-rc3.

October 21, 2005, at 07:31 AM by eFfeM -- added caveats section
Added lines 19-27:

Caveats

There are some things to be aware of when starting to rebuild (especially when rebuilding from the head).

When upgrading your kernel sources and rebuilding it is a good habit to remove tmp/{work,stamps}/{ixp,openslug*} (or unslung* if you are on unslung, or probably debianslug* if you are on debian).
Especially when going to a different kernel version it is possible that ixp has been changed. If you end up with a slug that seems to boot fine (led is green) it is possible that your ixp modules are not ok. This can a.o. happen when going from 2.6.14-rc2 to 2.6.14-rc3.

When upgrading your image with reflash -i some settings (e.g. /linuxrc) are maintained. This is nice as you do not have to do a turnup. However, if you upgrade from one release of the kernel to another (e.g. from 2.6.12 to 2.6.14 or from 2.6.14-rc2 to 2.6.14-rc3) your boot will fail as there will normally not be a /lib/modules/`uname -r` directory on your hard disk. Solution is to unplug the disk, reboot, then connect the hard disk and either do a turnup -i, install the modules or be lazy and cp -R /lib/modules from the flash to your hard disk (of course after mounting it).

September 07, 2005, at 06:53 AM by kaste --
Changed lines 9-10 from:

For OpenSlug firmware (including packages), use make openslug.

to:

For OpenSlug firmware, use make openslug-image (recommended).
For all of OpenSlug (including lots of packages), use make openslug.

August 26, 2005, at 10:30 PM by ka6sox --
Added lines 16-17:

All commits, whether in Monotone (OE) or CVS (optware) need to use the commit guidelines.

August 16, 2005, at 10:00 PM by ka6sox --
Changed lines 5-6 from:

See the make setup-host-debian or make setup-host-gentoo targets for a machine-executable description of the requirements for your build machine. I recommend Debian Etch (that's what I use - our official build machine that version). Most the of the core development team uses Debian or Gentoo.

to:

See the make setup-host-debian or make setup-host-gentoo targets for a machine-executable description of the requirements for your build machine. I recommend Debian Etch (that's what I use - our official build machine uses that version). Most the of the core development team uses Debian or Gentoo.

August 16, 2005, at 10:00 PM by ka6sox --
Changed lines 5-6 from:

See the make setup-host-debian or make setup-host-gentoo targets for a machine-executable description of the requirements for your build machine. I recommend Debian Etch (that's what I use - our official build machine uses an earlier Debian version). Most the of the core development team uses Debian or Gentoo.

to:

See the make setup-host-debian or make setup-host-gentoo targets for a machine-executable description of the requirements for your build machine. I recommend Debian Etch (that's what I use - our official build machine that version). Most the of the core development team uses Debian or Gentoo.

August 11, 2005, at 11:30 AM by blaster8 -- cosmetics
Changed lines 5-15 from:

See the "make setup-host-debian" or "make setup-host-gentoo" for a machine-executable description of the requirements for your build machine. I recommend Debian Etch (that's what I use - our official build machine uses an earlier Debian version). Most the of the core development team uses Debian or Gentoo.

For Unslung firmware (including kernel modules), use "make unslung".

For OpenSlug firmware (including packages), use "make openslug".

For Unslung packages (which are now called Optware/NSLU2 packages), use "make optware-nslu2".

For Asus WL500g packages, use "make optware-wl500g".

The Master Makefile will download and build everything that is required. If there are sources missing from upstream sites, it *should* download them from source.nslu2-linux.org/sources - if not, then you can download them manually from there.

to:

See the make setup-host-debian or make setup-host-gentoo targets for a machine-executable description of the requirements for your build machine. I recommend Debian Etch (that's what I use - our official build machine uses an earlier Debian version). Most the of the core development team uses Debian or Gentoo.

For Unslung firmware (including kernel modules), use make unslung.

For OpenSlug firmware (including packages), use make openslug.

For Unslung packages (which are now called Optware/NSLU2 packages), use make optware-nslu2.

For Asus WL500g packages, use make optware-wl500g.

The Master Makefile will download and build everything that is required. If there are sources missing from upstream sites, it *should* download them from the sources.nslu2-linux.org server - if not, then you can download them manually from there.

August 11, 2005, at 12:46 AM by rwhitby --
Changed lines 11-14 from:

For Unslung packages (which are now called NSLU2? packages), use "make optware-nslu2".

For Asus WL500g? packages, use "make optware-wl500g".

to:

For Unslung packages (which are now called Optware/NSLU2 packages), use "make optware-nslu2".

For Asus WL500g packages, use "make optware-wl500g".

August 11, 2005, at 12:46 AM by rwhitby --
Added lines 5-15:

See the "make setup-host-debian" or "make setup-host-gentoo" for a machine-executable description of the requirements for your build machine. I recommend Debian Etch (that's what I use - our official build machine uses an earlier Debian version). Most the of the core development team uses Debian or Gentoo.

For Unslung firmware (including kernel modules), use "make unslung".

For OpenSlug firmware (including packages), use "make openslug".

For Unslung packages (which are now called NSLU2? packages), use "make optware-nslu2".

For Asus WL500g? packages, use "make optware-wl500g".

The Master Makefile will download and build everything that is required. If there are sources missing from upstream sites, it *should* download them from source.nslu2-linux.org/sources - if not, then you can download them manually from there.

August 08, 2005, at 12:01 PM by rwhitby --
Added lines 1-4:

NSLU2-Linux Development

NSLU2-Linux development revolves around the MasterMakefile.

view · edit · print · history · Last edited by rwhitby.
Based on work by Jon, Alan H, rwhitby, jbowler, eFfeM, kaste, ka6sox, and blaster8.
Originally by rwhitby.
Page last modified on February 22, 2008, at 12:13 AM