This commit is contained in:
gferg 2001-11-09 19:35:48 +00:00
parent eda8d61329
commit 0a38cfc3d8
7 changed files with 499 additions and 177 deletions

View File

@ -125,7 +125,7 @@ Kernel-HOWTO</ULink>,
The Linux Kernel HOWTO</CiteTitle>
</Para><Para>
<CiteTitle>
Updated: July 2001</CiteTitle>.
Updated: November 2001</CiteTitle>.
A detailed guide to kernel configuration, compilation, upgrades, and
troubleshooting for ix86-based systems.</Para>
</ListItem>

View File

@ -583,7 +583,7 @@ Shows some typical scenarios for easy start using Diald.
Diskless-HOWTO</ULink>,
<CiteTitle>Diskless Nodes HOWTO for Linux</CiteTitle>
</Para><Para>
<CiteTitle>Updated: October 2001</CiteTitle>.
<CiteTitle>Updated: November 2001</CiteTitle>.
How to set up a diskless Linux box. </Para>
</ListItem>
@ -1147,7 +1147,7 @@ under Linux. </Para>
Kernel-HOWTO</ULink>,
<CiteTitle>The Linux Kernel HOWTO</CiteTitle>
</Para><Para>
<CiteTitle>Updated: July 2001</CiteTitle>.
<CiteTitle>Updated: November 2001</CiteTitle>.
A detailed guide to kernel configuration, compilation, upgrades, and
troubleshooting for ix86-based systems. </Para>
</ListItem>

View File

@ -110,7 +110,7 @@ How to set up high-performance Linux computing clusters. </Para>
Diskless-HOWTO</ULink>,
<CiteTitle>Diskless Nodes HOWTO for Linux</CiteTitle>
</Para><Para>
<CiteTitle>Updated: October 2001</CiteTitle>.
<CiteTitle>Updated: November 2001</CiteTitle>.
How to set up a diskless Linux box. </Para>
</ListItem>

View File

@ -112,7 +112,7 @@ Another approach to
Diskless-HOWTO</ULink>,
<CiteTitle>Diskless Nodes HOWTO for Linux</CiteTitle>
</Para><Para>
<CiteTitle>Updated: October 2001</CiteTitle>.
<CiteTitle>Updated: November 2001</CiteTitle>.
How to set up a diskless Linux box. </Para>
</ListItem>

View File

@ -444,7 +444,7 @@ device parameters. </Para>
Kernel-HOWTO</ULink>,
<CiteTitle>The Linux Kernel HOWTO</CiteTitle>
</Para><Para>
<CiteTitle>Updated: July 2001</CiteTitle>.
<CiteTitle>Updated: November 2001</CiteTitle>.
A detailed guide to kernel configuration, compilation, upgrades, and
troubleshooting for ix86-based systems. </Para>
</ListItem>

View File

@ -52,7 +52,7 @@ DISKLESS NODES HOW-TO for Linux
<htmlurl url="mailto:gero@gkminix.han.de"
name="gero@gkminix.han.de">
<date>v22.2, 20 Oct 2001
<date>v22.3, 08 Nov 2001
<abstract>
This document describes how to set up a diskless Linux box.
As technology is advancing rapidly, network-cards are becoming cheaper and much
@ -63,14 +63,14 @@ local disk access which will make diskless nodes a viable
alternative to workstations in local LAN. Also diskless nodes eliminates the
cost of software upgrades and system administration costs like backup,
recovery which will be centralized on the server side.
Diskless nodes also enable "sharing/optimization" of centralised server CPU,
Diskless nodes also enable "sharing/optimization" of centralized server CPU,
memory, hard-disk, tape and cdrom resources. Diskless nodes
provides mobility for the users i.e., users
can log on from any one of diskless nodes and are not tied to one workstation.
Diskless Linux box completely eliminates the need for local floppy disk,
cdrom drive, tape drive and hard-disk. Diskless nodes JUST has a network card,
8MB RAM, a low-end cpu and a very simple mother-board which does not have
any interface sockets/slots for harddisks, modem, cdrom, floppy etc..
any interface sockets/slots for hard-disks, modem, cdrom, floppy etc..
With Diskless linux nodes you can run programs on remote Linux 64 CPU SMP box
or even on Linux super-computer!
Diskless nodes lowers the "Total Cost of Ownership" of the computer system.
@ -94,11 +94,425 @@ mini-howto) to English.
<chapt> What is this all about?
-->
<sect> What is this all about?
<p>
Diskless Linux Computers do not have any hard-disk, floppy drives and tape drives. They offer
significant savings in "Total Cost of Ownership" by eliminating the maintenance costs.
You can accomplish Diskless Linux Computer by one of the following two methods:
<enum>
<item> Boot directly a Live Linux CDROM. The Linux CDROM is live Linux system which
contains all the applications and programs and loads the software into RAM disks.
<p>
<item> Recent linux kernels offer the possibility to boot a linux box entirely from network, by
loading its kernel and root filesystem from a server. In that case, the client may use
several ways to get the first instructions it has to execute when booting: home made
eproms, special network cards implementing the RARP, BOOTP or DHCP protocols, cdroms, or
bootloaders loaded from a boot floppy or a local hard drive.
</enum>
The simplest and most easy method to build a diskless linux is by using Live Linux CDROM.
You simply download Live Linux CDROM and insert it into the CDROM drive and power-on and you are
done! For details see the "Live Linux CDROM" chapter in this document.
The other option is using a EPROM, but this will
take extra work to be done on the client and the server box.
If you want to go for EPROM method, I recommend you to
simply buy Diskless Linux computers from the manufacturers as given later.
<!--
*******************************************
************ End of Section ***************
*******************************************
<chapt> Advantages of Diskless Computer
-->
<sect> Advantages of Diskless Computer
<p>
Diskless linux computer will become <bf>immensely</bf> popular and will
be the product of this century and in the next century.
The diskless linux computers will be very successful because of the
availability of very high-speed network cards at
very low prices. Today 100 Megabit
per second (12.5 MB per sec transfer rate) network cards are
common and in about 1 to 2 years 1000 MBit (125 MB per sec transfer rate)
network cards will become very cheap and will be the standard.
In near future, Monitor manufacturers will place
the CPU, NIC, RAM <bf>right inside</bf> the monitor to form
a diskless computer!!
This eliminates the diskless computer box and saves space. The monitor will
have outlet for mouse, keyboard, network RJ45 and power supply.
The following are benefits of using diskless computers -
<itemize>
<item> Diskless Linux computers can run BOTH MS Windows 95/NT and linux programs.
<p>
<item> Total cost of ownership is very low in case of Diskless computers.
Total cost of ownership is cost of initial purchasing + cost of maintenance.
The cost of maintenance is usually <bf>3 to 5 times</bf> the cost of
initial computer purchase and this cost is recurring year after year.
In case of Diskless computers, the cost of maintenance
is <bf>completely eliminated</bf>!!
<p>
<item> All the backups are centralized at one single main server.
<p>
<item> More security of data as it is located at server.
<p>
<item> No need of UPS battery, air-conditioning, dust proof environment for
diskless clients, only server needs UPS battery, A/C and dust proof environment.
Only remote server inside the "Data Center" needs to have UPS, Redundant power supply,
Portable Diesel Electric generator, A/C, Fire protection,
Highly restricted access with locked and secure door to "Data Center".
<p>
<item> Noise is completely eliminated since diskless computer does not have
Fan motor, and local hard-disk. Only server makes lots of noise but it is enclosed
in a server room ("Data Center").
<p>
<item> Protection from Virus attack - Computer virus cannot attack diskless
computers as they do not have any hard disk. Virus cannot do any damage to
diskless computers. Only one single server box
need to be protected against virus attack. This saves millions of dollars for
the company by avoiding installation of vaccines and cleaning the hard disks!!
<p>
<item> Server can have large powerful/high performance hard disks, can optimize
the usage of disk space via sharing by many diskless computer users.
Fault tolerance of hard disk failure is possible by using RAID on main server.
<p>
<item> Server can have 64 bit CPU SMP box having many CPUs or even
linux super-computers. CPU power can be shared by many diskless computer users
<p>
<item> Sharing of central server RAM memory by many diskless computer users.
For example, if many users are using a web browser then in the server RAM there will
be only one copy of web browser in the RAM. In case Windows 95 PCs, many
users need to have individual copy of web browser
in local RAM and hence there is wastage of RAM space.
<p>
<item> Diskless computers are extremely fast because program loading time is
completely eliminated. For example, if the server loads the StarOffice suite
into memory due to request from one diskless user then if another diskless user wants to
use the StarOffice suite then loading time is avoided since StarOffice is
already loaded into memory.
<p>
<item> Diskless linux computers can run programs on multiple servers using the
"xhost" and DISPLAY environment.
<p>
<item> Very few system administrators required to maintain central server unlike
Windows 95 PC clients which need many administrators.
<p>
<item> Zero administration at diskless client side. Diskless computers
are absolutely maintenance free and troublefree.
<p>
<item> Long life of diskless clients - more than <bf>300 years</bf> without any
hardware or software upgrades.
<p>
<item> Eliminates install/upgrade of hardware, software on diskless client side.
<p>
<item> Eliminates cost of cdrom, floppy, tape drive, modem, UPS battery, Printer
parallel ports, serial ports etc..
<p>
<item> Prevents pilferage of hardware components as diskless node has very little
RAM and low-cost CPU. The server has lots of memory and many powerful CPUs.
<p>
<item> Can operate in places like factory floor where a hard disk might be too fragile.
</itemize>
<!--
*******************************************
************ End of Section ***************
*******************************************
<chapt> Diskless with "Live Linux CDROM" <label id="livecdrom">
-->
<sect> Diskless with "Live Linux CDROM" <label id="livecdrom">
<p>
The "Live Linux CDROM" is a CDROM which has the entire Linux Operating System filesystem
on the CDROM. It is made by copying the live Linux system on to CDROM. The "Live Linux CDROM"
directly boots the Linux operating system from the CDROM drive.
But you need to setup the BIOS to first boot from CDROM. Generally the boot order is :
Floppy Drive, Hard disk, CDROM. You can enter BIOS setup, by powering on the computer and
presssing the DEL key.
Get the "Live Linux CDROM" from
<itemize>
<item> <url url="http://www.demolinux.org">
<item> <url url="http://www.knopper.net/knoppix">
<item> <url url="http://www.ocslink.com/~blunier">
</itemize>
Diskless workstation with "Live Linux CDROM" is becoming a reality because
of the following reasons:
<enum>
<item> RAM prices are all time low and 512MB RAM costs only US$70.
<item> CDROM drives are becoming extremely fast and current read speed is topping at 72X.
<item> CDROM IDE drives are very cheap, CDROM with 52X read speed is costing only US$33.
<item> DVD-ROM is also getting very cheap and can carry 5 Gigabyte of Linux software and
is three times faster than CDROM drive.
</enum>
A big advantage of Live Linux CDROM over other methods of diskless operations like
EEPROM is that it is very easy to setup and you can very easily upgrade the Linux CDROM
with new versions of the Linux kernel every three months. Simply throw away the old Live
Linux CDROM and pop-in the new version Live Linux CDROM. Upgrade is just 20 seconds and
the cost of Linux CDROM is 30 cents (less than a US dollar!).
In near future, Live Linux CDROM + DVD-ROM will rule the computer desktops.
With Live Linux CDROM, you do not need a hard-disk, floppy drives and others. All you need to
build a diskless workstation is :
<enum>
<item> Live Linux CDROM
<item> CPU
<item> Mother board
<item> NIC (Network Interface Card)
<item> CDROM drive (IDE or SCSI)
<item> RAM (32 MB minimum for full graphics and 16 MB minimum for console mode)
</enum>
For best prices on RAM and CDROM IDE drives check
auctions in online stores like
Egghead <url url="http://www.egghead.com"> or local stores in your city like
<url name="UBM, Houston" url ="http://www.ubm.com">.
After you boot "Live Linux CDROM", you can mount the hard disk partitions from remote
Linux servers. And you can use
<url name="VNC" url="http://www.uk.research.att.com/vnc">
to access MS Windows 2000 and Linux servers.
To evaluate the CDROM/DVD drives use the following software from
<url url="http://www.cdspeed2000.com">. This site also gives the speed comparison of
drives from different vendors. The top speed CDROM drive is from Kenwood at
<url url="http://www.kenwoodtech.com"> at 72x speed.
<!--
*******************************************
************ End of Section ***************
*******************************************
-->
<sect1> Build a Live Linux CDROM
<p>
You can build your own Live Linux CDROM and customize the kernel, hardware support, loadable
module support etc.
This section was originally written by Hans de Goede
<htmlurl url="mailto:
j.w.r.degoede@et.tudelft.nl
" name="
j.w.r.degoede@et.tudelft.nl
">
for the Diskless-root-NFS-HOWTO. I modified it slightly in order to reflect some differences
between this document and the Diskless-root-NFS-HOWTO.
Much of the above also goes for booting from cdrom. Why would one want to boot a machine
from cdrom? Booting from cdrom is interesting everywhere one wants to run a very specific
application, like a kiosk, a library database program or an internet cafe, and one
doesn't have a network or a server to use a root over nfs setup.
Creating a test setup
Now that we know what we want to do and how, it's time to create a test setup:
<itemize>
<item> For starters just take one of the machines which you want to use and put in a big
disk and a cd burner.
<item> Install your linux of choice on this machine, and leave a 650 MB partition free for
the test setup. This install will be used to make the iso image and to burn the cd's
from, so install the necessary tools. It will also be used to restore any booboo's
which leave the test setup unbootable.
<item> On the 650 mb partition install your linux of choice with the setup you want to have
on the cd, this will be the test setup.
<item> Boot the test setup.
<item> Compile a kernel with isofs and cdrom support compiled in.
<item> Configure the test setup as described above with the root filesystem mounted read
only.
<item> Verify that the test setup automagically boots and everything works.
<item> Boot the main install and mount the 650 MB partition on /test of the main install.
<item> Put the following in a file called /test/etc/rc.d/rc.iso, this file will be sourced
at the beginning of rc.sysinit to create /var:
<code>
#/var
echo Creating /var ...
mke2fs -q -i 1024 /dev/ram1 16384
mount /dev/ram1 /var -o defaults,rw
cp -a /lib/var /
</code>
<item> Edit /test/etc/rc.sysinit, comment the lines where the root is remounted rw, and add
the following 2 lines directly after setting the PATH:
<code>
#to boot from cdrom
. /etc/rc.d/rc.iso
</code>
<item> Copy the following to a script and execute it to make a template for /var and create
/tmp and /etc/mtab links.
<code>
#!/bin/sh
echo tmp
rm -fR /test/tmp
ln -s var/tmp /test/tmp
###
echo mtab
touch /test/proc/mounts
rm /test/etc/mtab
ln -s /proc/mounts /test/etc/mtab
###
echo var
mv /test/var/lib /test/lib/var-lib
mv /test/var /test/lib
mkdir /test/var
ln -s /lib/var-lib /test/lib/var/lib
rm -fR /test/lib/var/catman
rm -fR /test/lib/var/log/httpd
rm -f /test/lib/var/log/samba/*
for i in `find /test/lib/var/log -type f`; do
cat /dev/null > $i;
done
rm `find /test/lib/var/lock -type f`
rm `find /test/lib/var/run -type f`
</code>
<item> Remove the creation of /etc/issue* from /test/etc/rc.local: it will only fail.
<item> Now boot the test partition again, it will be read only just like a cdrom. If
something doesn't work reboot to the working partition fix it, try again etc. Or you
could remount / rw, fix it, then reboot straight into to test partition again. To
remount / rw type:
<code>
# mount -o remount,rw /
</code>
</itemize>
Creating the CD
If you need more information than you can find below, please refer to the
CD-Writing-HOWTO.
Creating a boot image
First of all, boot into the working partition. To create a bootable cd we'll need an
image of a bootable floppy. Just dd-ing a zImage doesn't work since the loader at the
beginning of the zimage doesn't seem to like the fake floppydrive a bootable cd creates.
So we'll use syslinux instead.
<itemize>
<item> Get boot.img from a redhat cd.
<item> Mount boot.img somewhere through loopback by typing:
<code>
# mount boot.img somewhere -o loop -t vfat
</code>
<item> Remove everything from boot.img except for ldlinux.sys and syslinux.cfg.
<item> Cp the kernel-image from the test partition to boot.img.
<item> Edit syslinux.cfg so that it contains the following, of course replace zImage by the
appropriate image name:
<code>
default linux
label linux
kernel zImage
append root=/dev/<insert your cdrom device here>
</code>
<item> Umount boot.img:
<code>
# umount somewhere
</code>
<item> If your /etc/mtab is a link to /proc/mounts, umount won't automagically free
/dev/loop0 so free it by typing:
<code>
# losetup -d /dev/loop0
</code>
</itemize>
Creating the iso image
Now that we have the boot image and an install that can boot from a readonly mount it's
time to create an iso image of the cd:
<itemize>
<item> Copy boot.img to /test
<item> Cd to the directory where you want to store the image and make sure it's on a
partition with enough free space.
<item> Now generate the image by typing:
<code>
# mkisofs -R -b boot.img -c boot.catalog -o boot.iso /test
</code>
</itemize>
Verifying the iso image
<itemize>
<item> Mounting the image through the loopbackdevice by typing:
<code>
# mount boot.iso somewhere -o loop -t iso9660
</code>
<item> Umount boot.iso:
<code>
# umount somewhere
</code>
<item> If your /etc/mtab is a link to /proc/mounts umount won't automagically free
/dev/loop0 so free it by typing:
<code>
# losetup -d /dev/loop0
</code>
</itemize>
Writing the actual CD
Assuming that you've got cdrecord installed and configured for your cd-writer type:
<code>
# cdrecord -v speed=<desired writing speed> dev=<path to your writers generic scsi device> boot.iso
</code>
Boot the cd and test it
Well the title of this paragraph says it all;)
<!--
*******************************************
************ End of Section ***************
*******************************************
<chapt> Buying is cheaper than building!
-->
<sect> Buying is cheaper than building!
<sect> Buying is Cheaper Than Building!
<p>
Sometimes, buying a diskless linux computer will be cheaper than building!!
In modern days we focus our energy on economy and managing the time efficiently.
Gone are the days when you would build everything on your own! Man introduced the
concept of mass production (factory having production lines churning out millions
of pieces). In the industrialized nation like U.S.A, every product you see is made
in mass-production and diskless computers are no exception. There are many
companies in USA which manufacture diskless computers in very large quantities.
Checkout the following commercial sites, which are selling diskless
linux network-cards and diskless computers. These companies do <bf>mass
production</bf> of Linux Diskless computers selling millions of units and thereby
@ -114,7 +528,7 @@ linux diskless nodes. Get VNC from <url url="http://www.uk.research.att.com/vnc"
<itemize>
<item> Linux Systems Labs Inc., USA <url url="http://www.lsl.com"> Click
on "Shop On-line" and than click on "HardWare" where all the
on "Shop On-line" and then click on "HardWare" where all the
Diskless computers will be listed. Phone 1-888-LINUX-88.
<p>
<item> Diskless Workstations Corporation, USA <url url="http://www.disklessworkstations.com">
@ -154,7 +568,7 @@ Linux will be the "host" OS and Windows 95/NT will be the "guest" OS.
<url name="VMWare" url="http://www.vmware.com">
is NOT a
emulator but has BIOS which allows you to install Windows 95/98/NT as
the guest OS to linux. Install the VMWare on Linux server and than install
the guest OS to linux. Install the VMWare on Linux server and then install
Windows 95/NT on VMWare.
You can use the 'xhost' command and DISPLAY environment from <bf>any</bf>
@ -194,8 +608,8 @@ There are other tools similar to vmware:
-->
<sect1> VNC package from AT and T
<p>
You can also use the VNC (Virtual Network Computing) Technology from the telecom
giant AT &amp T. VNC is GPLed and is a free software. Using VNC you can run Windows 95/NT
You can also use the VNC (Virtual Network Computing) Technology from
AT &amp T. VNC is GPLed and is a free software. Using VNC you can run Windows 95/NT
programs on diskless linux computer but actually running on remote Windows95/NT server.
You can use the VNC to display remote machines on your local display.
@ -235,106 +649,6 @@ usleep((unsigned long) 10000)
<chapt> Advantages of Diskless Computer
-->
<sect> Advantages of Diskless Computer
<p>
Diskless linux computer will become <bf>immensely</bf> popular and will
be the product of this century and in the next century.
The diskless linux computers will be very successful because of the
availability of very high-speed network cards at
very low prices. Today 100 Megabit
per second (12.5 MB per sec transfer rate) network cards are
common and in about 1 to 2 years 1000 MBit (125 MB per sec transfer rate)
network cards will become very cheap and will be the standard.
In near future, Monitor manufacturers will place
the CPU, NIC, RAM <bf>right inside</bf> the monitor to form
a diskless computer!!
This eliminates the diskless computer box and saves space. The monitor will
have outlet for mouse, keyboard, network RJ45 and power supply.
The following are benefits of using diskless computers -
<itemize>
<item> Diskless Linux computers can run BOTH MS Windows 95/NT and linux programs.
<p>
<item> Total cost of ownership is very low in case of Diskless computers.
Total cost of ownership is cost of initial purchasing + cost of maintainence.
The cost of maintainence is usually <bf>3 to 5 times</bf> the cost of
initial computer purchase and this cost is recurring year after year.
In case of Diskless computers, the cost of maintainence
is <bf>completely eliminated</bf>!!
<p>
<item> All the backups are centralized at one single main server.
<p>
<item> More security of data as it is located at server.
<p>
<item> No need of UPS battery, air-conditioning, dust proof environment for
diskless clients, only server needs UPS battery, A/C and dust proof environment.
Only remote server inside the "Data Center" needs to have UPS, Redundant power supply,
Portable Diesel Electric generator, A/C, Fire protection,
Highly restricted access with locked and secure door to "Data Center".
<p>
<item> Noise is completely eliminated since diskless computer does not have
Fan motor, and local harddisk. Only server makes lots of noise but it is enclosed
in a server room ("Data Center").
<p>
<item> Protection from Virus attack - Computer virus cannot attack diskless
computers as they do not have any hard disk. Virus cannot do any damage to
diskless computers. Only one single server box
need to be protected against virus attack. This saves millions of dollars for
the company by avoiding installtion of vaccines and cleaning the hard disks!!
<p>
<item> Server can have large powerful/high performance hard disks, can optimize
the usage of disk space via sharing by many diskless computer users.
Fault tolerance of hard disk failure is possible by using RAID on main server.
<p>
<item> Server can have 64 bit CPU SMP box having many CPUs or even
linux super-computers. CPU power can be shared by many diskless computer users
<p>
<item> Sharing of central server RAM memory by many diskless computer users.
For example, if many users are using web browser than at server RAM there will
be only one copy of web browser in the RAM. In case Windows 95 PCs, many
users need to have individual copy of web browser
in local RAM and hence there is wastage of RAM space.
<p>
<item> Diskless computers are extremely fast because program loading time is
completely eliminated. For example, if the server loads the StarOffice suite
into memory due to request from one diskless user then if another diskless user wants to
use the StarOffice suite then loading time is avoided since StarOffice is
already loaded into memory.
<p>
<item> Diskless linux computers can run programs on multiple servers using the
"xhost" and DISPLAY environment.
<p>
<item> Very few system administrators required to maitain central server unlike
Windows 95 PC clients which need many administrators.
<p>
<item> Zero administration at diskless client side. Diskless computers
are absolutely maintainence free and troublefree.
<p>
<item> Long life of diskless clients - more than <bf>300 years</bf> without any
hardware or software upgrades.
<p>
<item> Eliminates install/upgrade of hardware, software on diskless client side.
<p>
<item> Eliminates cost of cdrom, floppy, tape drive, modem, UPS battery, Printer
parallel ports, serial ports etc..
<p>
<item> Prevents pilferage of hardware components as diskless node has very little
RAM and low-cost CPU. The server has lots of memory and many powerful CPUs.
<p>
<item> Can operate in places like factory floor where a hard disk might be too fragile.
</itemize>
<!--
*******************************************
************ End of Section ***************
*******************************************
<chapt> Quick Steps to implement Diskless Nodes
-->
<sect> Quick Steps to implement Diskless Nodes
@ -391,55 +705,6 @@ Related topics worth seeing -
<chapt> Diskless with "Live Linux CDROM" <label id="livecdrom">
-->
<sect> Diskless with "Live Linux CDROM" <label id="livecdrom">
<p>
The "Live Linux CDROM" is a CDROM which has the entire Linux Operating System filesystem
on the CDROM. It is made by copying the live Linux system on to CDROM. The "Live Linux CDROM"
directly boots the Linux operating system from the CDROM drive.
Get the "Live Linux CDROM" from
<itemize>
<item> <url url="http://www.demolinux.org">
<item> <url url="http://www.knopper.net/knoppix">
<item> <url url="http://www.ocslink.com/~blunier">
</itemize>
Diskless workstation with "Live Linux CDROM" is becoming a reality because
of the following reasons:
<enum>
<item> RAM prices are all time low and 512MB RAM costs only US$70.
<item> CDROM drives are becoming extremely fast about 52X read speeds.
<item> CDROM IDE drives are very cheap, CDROM with 52X read speed is costing only US$33.
</enum>
You do not need a harddisk, floppy drives and others. All you need to
build a diskless workstation is :
<enum>
<item> CPU
<item> Mother board
<item> NIC (Network Interface Card)
<item> CDROM drive (IDE or SCSI)
<item> RAM (64 MB minimum)
<item> Live Linux CDROM
</enum>
For best prices on RAM and CDROM IDE drives check
auctions in online stores like
Egghead <url url="http://www.egghead.com"> or local stores in your city like
<url name="UBM, Houston" url ="http://www.ubm.com">.
After you boot "Live Linux CDROM", you can mount the hard disk partitions from remote
Linux servers.
<!--
*******************************************
************ End of Section ***************
*******************************************
<chapt> EEPROMs or Flash ROMs? <label id="flashroms">
-->
<sect> EEPROMs or Flash ROMs? <label id="flashroms">
@ -1631,7 +1896,7 @@ Copyright policy is GNU/GPL as per LDP (Linux Documentation project).
LDP is a GNU/GPL project.
Additional restrictions are - you must retain the author's name, email address
and this copyright notice on all the copies. If you make any changes
or additions to this document than you should
or additions to this document then you should
intimate all the authors of this document.
<!--
*******************************************

View File

@ -37,7 +37,7 @@
" name="
bri@cs.uchicago.edu
">
<date>v3.0, 15 July 2001
<date>v3.1, 07 Nov 2001
<abstract>
This is a detailed guide to kernel configuration, compilation, upgrades,
@ -162,8 +162,8 @@ and your current kernel will be intact and will not be touched.
<code>
bash$ su - root
bash# cd /mnt/cdrom/RedHat/RPMS
bash# rpm -i kernel-headers*.rpm
bash# rpm -i kernel-source*.rpm
bash# rpm -i kernel-headers*.rpm
bash# rpm -i kernel-source*.rpm
bash# rpm -i dev86*.rpm
bash# rpm -i bin86*.rpm
</code>
@ -189,18 +189,24 @@ dev86*.rpm on cdrom or from
<code>
bash# export TERM=xterm
bash# make menuconfig
If you find scrambled display, then use different terminal emulators
like vt100, vt102, vt220 or ansi for example:
If you find scrambled display, then use different terminal emulators like vt100,
vt102, vt220 or ansi. The display will be scrambled and will have garbage
characters in cases where you use telnet to login to remote linux. In such
cases you should use the terminal emulators like vt100, vt220.
For example:
bash# export TERM=vt220
bash# export TERM=ansi
At a lower level, use:
bash# export TERM=vt100
bash# make menuconfig
If the above command fails then try -
If the menuconfig command fails then try -
bash# make config
</code>
</itemize>
The <bf>"make xconfig" or "make menuconfig"</bf> brings up a user friendly GUI interface.
The <bf>"make xconfig" or "make menuconfig"</bf> brings up a user friendly GUI interface.
And <bf>"make config"</bf> brings up command-line console mode interface.
You can load the
configuration file from <it>/usr/src/linux/.config</it> (dot config file. Note the dot
before config).
@ -211,7 +217,7 @@ If the above command fails then try -
<item> Select proper CPU type - Pentium 3, AMD K6, Cyrix, Pentium 4, Intel 386, DEC Alpha, PowerPC otherwise kernel will not boot!!
<item> Select SMP support - whether single CPU or multiple CPUs
<item> Filesystems - Select Windows95 Vfat, MSDOS, NTFS as part of kernel and
not as loadable modules.
not as loadable modules. (My personal preference but you are free to pick your own option).
<item> Enable the Loadable kernel modules support!
With this option you can load/unload the device drivers
dynamically on running linux system on the fly.
@ -254,9 +260,9 @@ Type 'h' for help and to navigate press i, j, k, l, h or arrow, page up/down key
bash# cd /usr/src/linux
bash# man nohup
bash# nohup make bzImage &
bash# man tail
bash# tail -f nohup.out (.... to monitor the progress)
This will put the kernel in /usr/src/linux/arch/i386/boot/bzImage
bash# man tail
</code>
<p>
@ -287,7 +293,7 @@ You can check device name for 'root=' with the command -
bash# lilo
bash# lilo -q
</code>
You must re-run lilo even if entry 'myker' exists, everytime you create a new bzImage.
You must re-run lilo even if the entry 'myker' exists, everytime you create a new bzImage.
<p>
<item> Reboot the machine and at lilo press tab key and
@ -301,6 +307,7 @@ boot disk. Insert a blank floppy into floppy drive and -
<code>
bash# cd /usr/src/linux
bash# make bzdisk
See also mkbootdisk -
bash# rpm -i mkbootdisk*.rpm
bash# man mkbootdisk
@ -344,6 +351,22 @@ You can set PATH the insmod searches in /etc/modules.conf
************ End of Section ***************
*******************************************
-->
<sect2> The System Hangs at LILO
<p>
<bf>Sympton: </bf> After you build the kernel and reboot, the system hangs just before LILO.
<bf>Reason: </bf> Probably you did not set the BIOS to pick up the proper Primary Master IDE and
Secondary Slave IDE hard disk partition.
<bf>Solution: </bf>Power on the machine and press DEL key to do setup of the BIOS (Basic Input Output system). Select the IDE settings and set proper primary hard disk partition and slave drives.
When the system boots it looks for the primary IDE hard disk and the Master Boot Record partition.
It reads the MBR and starts loading the Linux Kernel from the hard disk partition.
<!--
*******************************************
************ End of Section ***************
*******************************************
-->
<sect2> No init found
<p>
@ -371,7 +394,38 @@ bash# man init
*******************************************
-->
<sect2> Kernel does not load module - Unresolved symbol error messages
<sect2> The 'depmod' gives "Unresolved symbol error messages"
<p>
When you run <tt>depmod</tt> it gives "Unresolved symbols". A sample error message
is given here to demonstrate the case:
<code>
bash$ su - root
bash# man depmod
bash# depmod
depmod: *** Unresolved symbols in /lib/modules/version/kernel/drivers/md/linear.o
depmod: *** Unresolved symbols in /lib/modules/version/kernel/drivers/md/multipath.o
depmod: *** Unresolved symbols in /lib/modules/version/kernel/drivers/md/raid0.o
depmod: *** Unresolved symbols in /lib/modules/version/kernel/drivers/md/raid1.o
depmod: *** Unresolved symbols in /lib/modules/version/kernel/drivers/md/raid5.o
</code>
<bf>Reason: </bf> You did not make modules and install the modules after building
the new kernel with <tt>"make bzImage"</tt>.
<bf>Solution: </bf> After you build the new kernel, you must do:
<code>
bash$ su - root
bash# cd /usr/src/linux
bash# make modules
bash# make modules_install
</code>
<!--
*******************************************
************ End of Section ***************
*******************************************
-->
<sect2> Kernel Does Not Load Module - "Unresolved symbols" Error Messages
<p>
When you boot kernel and system tries to load any modules and
you get "Unresolved symbol : __some_function_name" then it means
@ -465,6 +519,10 @@ bash# man Xconfigurator
bash# /usr/bin/X11/Xconfigurator --help
bash# /usr/bin/X11/Xconfigurator
bash# /usr/bin/X11/Xconfigurator --expert
See also:
bash# man xf86config
bash# /usr/bin/X11/xf86config
</code>
If your card is not detected automatically, then you can use the --expert option
and select the "Unlisted card". If your monitor is not listed then select the generic
@ -560,8 +618,7 @@ image=/boot/bzImage.myker-firewall.16mar2001
root=/dev/hda9
read-only
</code>
<!--
<!--
*******************************************
************ End of Section ***************
*******************************************