Difference between revisions of "Pegasos"
Jump to navigation
Jump to search
(→Netbooting: add 0.0.0.0 magic) |
(→Netbooting: add boot command info) |
||
| Line 4: | Line 4: | ||
setenv boot-device eth:dhcp,0.0.0.0,,0.0.0.0 | setenv boot-device eth:dhcp,0.0.0.0,,0.0.0.0 | ||
</pre> | </pre> | ||
| − | (The double comma indicates an empty boot file name--it is supplised by the DHCP server.) | + | (The double comma indicates an empty boot file name--it is supplised by the DHCP server.) Now to boot, simply type <code>boot</code> and hit return. |
This can be saved in the firmware by editing the nvramrc script. To begin editing, type <code>nvedit</code> and add the above command to the end of the list (change 'eth' to the devalias of whatever ethernet device you wish to use). When finished, hit control-C to exit the editor. Then, type <code>nvstore</code> to save your changes. | This can be saved in the firmware by editing the nvramrc script. To begin editing, type <code>nvedit</code> and add the above command to the end of the list (change 'eth' to the devalias of whatever ethernet device you wish to use). When finished, hit control-C to exit the editor. Then, type <code>nvstore</code> to save your changes. | ||
Revision as of 00:46, 9 February 2006
Netbooting
The Open Desktop Workstations (ODWs) use SmartFirmware. The SmartFirmware user manual has a good netbooting tutorial. The DHCP support in the firmware is slightly buggy and requires inserting a client and server IP of 0.0.0.0 in the boot-device string, like so:
setenv boot-device eth:dhcp,0.0.0.0,,0.0.0.0
(The double comma indicates an empty boot file name--it is supplised by the DHCP server.) Now to boot, simply type boot and hit return.
This can be saved in the firmware by editing the nvramrc script. To begin editing, type nvedit and add the above command to the end of the list (change 'eth' to the devalias of whatever ethernet device you wish to use). When finished, hit control-C to exit the editor. Then, type nvstore to save your changes.
