Difference between revisions of "Little-Fe PPC"
(→Creating a new Little-Fe PPC) |
|||
| Line 13: | Line 13: | ||
==Creating a new Little-Fe PPC== | ==Creating a new Little-Fe PPC== | ||
| − | + | ===Choose an operating system=== | |
| − | + | ||
| − | + | ===Setup the diskless netboot environment=== | |
| + | |||
| + | ====TFTPD==== | ||
| + | |||
| + | ====DHCPD==== | ||
| + | |||
| + | ====NFSD==== | ||
| + | If you're using Debian, use the nfs-kernel-server package (not the nfs-user-server package). (Knowledge about how this translates to other platforms would be helpful here.) | ||
| + | |||
| + | ====Unified Root==== | ||
| + | [[Unified Root Setup]] | ||
| + | |||
| + | ====Configure Client Firmware==== | ||
==Related pages== | ==Related pages== | ||
*[[Pegasos|Pegasos PPC (ODW) notes]] | *[[Pegasos|Pegasos PPC (ODW) notes]] | ||
Revision as of 14:39, 12 May 2006
This is page contains information about the 4 node PPC (Pegasos) version of Little-Fe.
This version of Little-Fe PPC is based on a Debian GNU/Linux installation. It employs UnionFS to facilitate consolidation of system and cluster software on a single hard drive (attached to lf0). All other nodes netboot from the master image by masking the server-specific files with a lightweight overlay.
lf0can be found atlf-ppc.cluster.earlham.edu
Contents
Documentation and bug reporting
- To report a bug, please use Bugzilla
We are documenting the production of Little-Fe in two ways: First, bugs are filed in bugzilla (and hopefully fixed). Second, we're putting flesh on a set of instructions to build a replica of the original Little-Fe PPC. The latter is probably (but not necessarily) based on the former. The distinction is mainly that Bugzilla will show how things were done wrong, while the wiki-based instructions will show how to do things right the first time.
Creating a new Little-Fe PPC
Choose an operating system
Setup the diskless netboot environment
TFTPD
DHCPD
NFSD
If you're using Debian, use the nfs-kernel-server package (not the nfs-user-server package). (Knowledge about how this translates to other platforms would be helpful here.)
