Difference between revisions of "Configuration"
Line 12: | Line 12: | ||
=== Configuring the Build === | === Configuring the Build === | ||
− | Unlike ZeptoOS V1.5 on [[Bluegene/L]] where it was required to run a configure script, in ZeptoOS V2.0 for [[Bluegene/P]] we have an [http://en.wikipedia.org/wiki/Ncurses ncurses] based make menuconfig option. | + | Download the bzipped file on the [[Bluegene/P]] login node. Extract the sources by using: |
+ | <code>$ tar xjf zeptoos-20.tar.bz2 </code> | ||
+ | |||
+ | Change to the BGP top directory using: | ||
+ | <code>$ cd BGP/</code> | ||
+ | |||
+ | {{asfsadfasd}} | ||
+ | |||
+ | Unlike ZeptoOS V1.5 on [[Bluegene/L]] where it was required to run a configure script, in ZeptoOS V2.0 for [[Bluegene/P]] we have an [http://en.wikipedia.org/wiki/Ncurses ncurses] based <code>make menuconfig</code> option. The required paths can be configured issuing: | ||
+ | <code>$ make menuconfig</code> | ||
=== Building ZeptoOS V2.0 === | === Building ZeptoOS V2.0 === |
Revision as of 17:30, 20 January 2009
Checklist
- Login Node
Security Notes
ZeptoOS is completely configurable. You may choose to allow user login access, or restrict it. However you configure ZeptoOS, it is important to note that the default configuration from IBM is for the I/O Nodes to NFS mount the /bgl file system with full root privileges. This means that anyone who has root access on the I/O nodes can modify everything on the NFS server. On our machine, we have modified the service node to export /bgl read-only, without observing any adverse effects on the I/O nodes.
Configuring the Build
Download the bzipped file on the Bluegene/P login node. Extract the sources by using:
$ tar xjf zeptoos-20.tar.bz2
Change to the BGP top directory using:
$ cd BGP/
sdfsadfsadfsadf
Unlike ZeptoOS V1.5 on Bluegene/L where it was required to run a configure script, in ZeptoOS V2.0 for Bluegene/P we have an ncurses based make menuconfig
option. The required paths can be configured issuing:
$ make menuconfig