Linux FAQ's & Manuals

• Linux Scripts
• Debian Install
• Bash For Beginners
• Bugzilla
• Consultants Guide
• GCC Manual
• Linux Command Line Tools
• Gnu Pascal Coding Standards
• Linux Installation Disk
• Labolatorium Linux(PL)
• Budowa systemu Linux(PL)
• Linux Dictionary
• Network Administrators
• Rescue Disk for Linux
• Red Hat Installation
• Red Hat Customization
• Red Hat Getting Started
• Red Hat Security
• Secure & Optimize
• Slackware Manual
• Suse Support
• Suse FAQ

LinuxElectrons: The Free Standards Group Unites Linux Printing Initiatives
Free Standards Group (FSG) has announced Linuxprinting.org... is merging with the FSG's OpenPrinting workgroup and will be integrated and supported in the Linux Standard Base...

Reg Developer: Eclipse: We Don't Have a Relationship with Sun
Prospects of a thaw between Sun and the Eclipse Foundation seem as slim as ever, judging by remarks made to The Register by Eclipse executive director Mike Milinkovich...

The Inquirer: Croatian Government Adopts Free Software Policy
The Croatian government has decided to adopt a free software policy and move entirely to Open Source...

Ars Technica: OpenOffice.org Less Secure than Microsoft Office?
However, a report just released by the French Ministry of Defense says that it still falls short of Microsoft's office suite in one important area: security...

Groklaw: A Word to SCO from the Open Group's Website
Now that we have read SCO's incredible Objections to Judge Brooke Wells' Order (which I call their 'How are we supposed to know what IBM did?' appeal)...

next: making a bootable diskette up: making linux installation disks previous: populating the root file   contents

building a kernel

now it is time to build a kernel. for the target system we will build a kernel that is different from the host system kernel. we build it under the myboot directory. first cd to the myboot/linux-2.4.21 subdirectory.

the most important job is configuring the kernel. run the following command:

 make menuconfig 

instead of menuconfig you can use config (not recommended!) or xconfig. this will give a usable kernel for the target system.

• processor type menu: processor family must be 486, switch off smp support, leave the rest at defaults.
• general setup menu: switch off hot-pluggable devices, system v ipc and sysctl support. support elf binaries, other formats can be disabled.
• parallel port support can be switched off, unless you want to enable it for plip networking or parallel port storage devices (zip disk, cd-rom).
• scsi: enable scsi cd-rom support, enable a large selection of low level drivers as modules.
• network device support: enable a large selection of ethernet cards as modules.
• code maturity, module support, memory technology, parallel port, plug and play, multi-device, telephony, i2o, amateur radio, isdn, old cdrom, input core, multimedia, sound, and kernel hacking submenus: disable everything, if it was not already disabled.
• block device submenu: support floppy, loop device, ram disk and initial ram disk.
• ata/ide/mfm/rll submenu: support, keep everything under the ata/ide... block devices submenu the default.
• character devices submenu: support virtual terminal, console on virtual terminal, unix 98 pty, disable everything else.
• file systems. keep second extended, proc and dev pts enabled. if you want to mount dos diskettes, enable fat, msdos and vfat. enable iso9660, nfs (client only) and ext3. if you want to experiment with other file systems such as reiserfs, you must enable support for them.
• console drivers. keep vga text console enabled.
• exit and say yes to save changes.

of course you must adapt the configuration to the target system you are using are you are anticipating your target audience to use. this kernel tries to be useful for a large number of systems, from 486dx onward. the strategy is to keep things in if they enable a user to get started with an installation, so it must be possible to access scsi harddisks and cd-roms and also the local area network in case the machine does not have a cd-rom. this kernel will be different from the one that is going to be used after installation. support for soundcards and printers is probably unnecessary on this installation disk.

now we only need to build the kernel:

 make clean make dep make bzimage 

the kernel described here should be around 900kb.

next create the modules:

 make modules make install_mod_path=$myboot modules_install cd $myboot tar zcvf modules.tar.gz lib 

the modules will end up in a compressed tar archive, not normally stored on the main ram disk.

---

next: making a bootable diskette up: making linux installation disks previous: populating the root file   contents

lennart benschop 2003-07-16