Dokumentacja

ODF: The Inevitable Format
Red Hat Magazine: 'The scientist thought he would find what he needed on a NASA website somewhere, but it wasn't that easy. The original data had been misplaced, and when the huge magnetic tapes that stored the data were found, they were 'in a format so old that the programmers who knew it had died...'"

Report: Seagate Plans to Stop Manufacturing IDE Drives by Year End
Ars Technica:: "Seagate plans to cease manufacturing IDE hard drives by the end of the year and will focus exclusively on SATA-based products..."

How To Manage An iPod From A Linux Desktop With Amarok
HowtoForge: "This article shows how you can use an iPod on a Linux desktop with Amarok..."

Ingimp's Tools May Improve FOSS Usability
Linux.com: "Since May, ingimp, a modified version of the GIMP, has collected daily logs on what users do with the program in the hope of improving its usability..."

HowTo Configure Hidden Compiz/XGL Effects
Linux In Novell's East Region: "One of the coolest things about Novell's SUSE Linux Enterprise Desktop (SLED) are its new 'Desktop Effects.' Desktop Effects are really a combination of two opensource components written by Novell's David Reveman, Compiz and Xgl..'""

next: populating the root file up: making linux installation disks previous: building curses and dialog contents

other essential binaries

while busybox offers us many essential unix utilities, we still miss a few essential programs for our mission. we cannot partition a hard disk, we cannot select an appropriate keyboard layout and we cannot create or repair ext2 file systems. busybox can be made to include mkfs and fsck for minix file systems, but not for the much more common ext2 file system. both util-linx and e2fsprogs complain if you had not built uclibc with large file support.

first start another shell and type the following command:

 export path=$myboot/uclibc-dev/usr/bin:$path

from now on, the uclibc version of gcc will be used instead of the normal version.

for now we need util-linux only for the fdisk and cfdisk utilities. the build procedure is as follows:

cd into the util-linux source directory.
run configure and make.
make stops with an error while trying to build swapon. we already have a swapon in busybox, so we leave it that way.
cd into the fdisk directory.
run the following commands.
```
 cp $myboot/uclibc-dev/include/ncurses/curses.h \    $myboot/uclibc-dev/include make have_ncurses=yes libcurses=-lncurses 
```
all the trouble is to get cfdisk compiled, so we can use it in addition to or instead of the stone age fdisk program.
copy the binaries fdisk and cfdisk to the $myboot/rootfs/sbin directory.

now we will build e2fsprogs as follows:

create a directory named build under the e2fsprogs source directory and cd to it.

configure and build the programs: ¹

 ./configure make build_cc=/usr/bin/gcc

strip and move e2fsck and mke2fs to the rootfs directory.

 strip e2fsck/e2fsck.shared mv e2fsck/e2fsck.shared $myboot/rootfs/sbin/e2fsck strip misc/mke2fs mv misc/mke2fs $myboot/rootfs/sbin

now we still need to be able to load keyboard definitions for foreign keyboards. now enter the kbd subdirectory. run the local configure command and then create the file defines.h with the following contents:

 #define lc_all 0

now you can make the program without errors, but apparently it is a bit buggy. move the loadkeys binary and key maps to the rootfs directory.

 strip src/loadkeys mv src/loadkeys $myboot/rootfs/usr/bin mkdir $myboot/rootfs/usr/share/kbd cp -a data/keymaps $myboot/usr/share/kbd

now you can weed out a lot of those keymap files that we do not need. start with removing the amiga, atari, mac and sun directories. in the i386 directories there are probably only a few maps you want to keep, one for each country that your product may need to be used. all files that are left can be compressed with gzip. i kept the keymaps for belgium, france, germany, uk and us (used almost exclusively in the netherlands) and all include directories (and these are probably not even needed). if you want to test loadkeys using the familiar chroot trick, this only works on a text console and you may need some of the device nodes already in place (see next chapter).

this is the time to build any other programs you will need. link them with uclibc and move them to the one of the binary subdirectories in the
$myboot/rootfs directory. if linking with uclibc does not work, try to link statically using the ordinary gcc.

next: populating the root file up: making linux installation disks previous: building curses and dialog contents

lennart benschop 2003-07-16

Linux FAQ's & Manuals

other essential binaries