nwlogo
NAVIGATION
About
News
Support

Downloads
- Search
- Mirrors
- Auto update

Documentation
- FAQ
- HOWTOs
- ARM info
- Crusoe info

Development
- Toolchain
- Autobuild
- Users

Sponsored by:

Open Source Lab at OSU

Total Domain Management by LaneChange.net

rh-9 Build Status

2003-Jul-22

  • Imaged all build nodes with image from pass 10. Node 7 needs a larger drive. Node 12 disk gone bad. Node 13 being used for dm-3.9 upgrade experiments.
  • Received new kernel patch, 2.4.21 packages built. Seemes to work on jay. New freeswan-2.01 included in kernels; userspace packaging is all busted again.

2003-Jul-21

  • Pass 10 completed with 94% success rate
  • Applied patch for glibc issue with libc.so and libpthread.so
  • Updated redhat-release with our distro name and codename
  • New image created from binaries.
  • Andrew built a base image and found problems with fdisk or the partition reading code.
  • Patch for kernel 2.4.21 received, unfortunately still crashing with "vector exception"...

2003-Jul-17

  • Problems booting 2.4.21 kernel, will take more investigating.
  • Nodes 2-11 are being re-imaged with the results from pass 9.
  • Setup web page to access modified SRPMS
  • Started Pass 10

2003-Jul-16

  • Pass 9 was completed yesterday.
  • New image created from the binaries
  • Updated openjade, docbook-style-* from rawhide
  • Edited a half-dozen packages that were failing due to "Architecture not included: armv4l". This means _nw1 versions for each.
  • Discarded all compat-* SRPMS, as well as other backwards-compat packages such as qt2 and postgres72.
  • Forgot to do kludges before tarring up the image, so re-doing it :-(
  • RMK released kernel 2.4.21-rmk1 patch, merging into CVS.

Todo

  1. Retry glibc upgrade on dm-3.9, update bugzilla bug
  2. Merge in security/errata updates for RH9
  3. Modify autobuild script to build larger packages on nodes with 10GB drives
  4. (DONE) Write a tool to extract spec changes & patches from modifed SRPMS
  5. Submit patches from modified SRPMS to Redhat
  6. For patches that work around gcc optimizer bugs, regenerate the ICE and submit bug reports to the gcc folks
  7. Setup yum repository (JeffJ recommended)
  8. Improve the webstats to better handle multiple versions of same package
  9. Add cumulative stats and node-totals to webstats
  10. Fix remaining packages
  11. Test, test, test...

Manual kludges

Note: the autobuild environment currently uses a chroot for the new image. In other words we are not booting into the new image yet. If you want to boot the image, make sure you have an /etc/fstab file, and be prepared for problems in the initscripts -- we haven't tested them yet.

The following kludges currently need to be done manually after installing all the packages.

  1. Fix kernel symlinks /usr/src/linux, /usr/include/linux, /usr/include/asm. The real problem is the kernel package needs to depend on /bin/ln, will be fixed in the next kernel package. If you're going to boot the image, make sure you create the /boot/vmlinux symlink as well.
  2. Edit /usr/lib/libc.so and /usr/lib/libpthread.so and remove the 4th line of each (containing the word "BUG") --- This has been FIXED for Pass 11
  3. In /usr/include/c++/3.3/backward copy/rename/symlink strstream to strstream.h
  4. Create /usr/X11 symbolic link to X11R6 directory
  5. To compile iproute, must update one file in kernel headers to 2.4.20+ (Next kernel will be 2.4.21, so should fix itself then).
  6. (Only for the autobuilder really) To set the name on RPMs you compile, create /etc/rpm/macros containing the lines
    %distribution NetWinder ARM Linux
    %packager NetWinder Autobuild <build@netwinder.org>
    %vendor NetWinder.org
    

Upgrade notes

Upgrading an existing dm-3.9 to the new build is currently a problematic process.

The dm-3.9 image uses RPM v3 database, while rh-9 uses RPM v4. To keep you database intact it is necessary to upgrade to rpm-4.0.4 and do a rpm --rebuildb. A suitable RPM binary is available at www.netwinder.org/autobuild/migration. You will then have a v4 database, and can upgrade to the current version of RPM, which is rpm-4.2.

Unfortunately, it seems there is a bug triggered during the update of glibc from 2.1.3 (dm-3.9) to 2.3.2 (rh-9), which corrupts the RPM database, regardless of having done the previous conversion to v4. See redhat bugzilla bug #97019

Freeing space

The current size (pass9) of the disk image is 3.1G installed. You can save over 300MB by deleting documentation

rpm -qad | xargs rm

This has already been done on the autobuild nodes. In additional you can remove the larger RPM pacakges, in particular tetex-doc (50MB), and glibc-debug (50MB). Next worsts offenders are xmeacs, xemacs-el, and emacs, delete if you don't use them.

rpm -qa --qf '%{SIZE}\t%{NAME}\n' | sort -n
[..snip..]
17775437        kernel-headers
18643525        gnome-games
19086182        ttfonts-zh_CN
19499706        gimp-print-cups
19819927        foomatic
20050692        fonts-ja
21106722        XFree86
23072808        ttfonts-zh_TW
23225353        tetex-fonts
23345851        aspell-fr
23494680        gimp
24455890        ghostscript
27888686        emacs-el
28023382        kdevelop
28072633        kdelibs
28275502        perl
30961647        qt-devel
31122634        emacs
35572280        kdebase
36637599        tetex
37536824        ttfonts-ko
40965504        glibc-common
42191205        kdeedu
44894253        xemacs-el
47323860        Omni
54545496        glibc-debug
54674111        tetex-doc
68971849        xemacs