https://clonwiki0.jlab.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=129.57.167.199 2026-05-07T12:35:56Z User contributions MediaWiki 1.42.1 https://clonwiki0.jlab.org/wiki/index.php?title=Clasxt&diff=5814 2012-05-03T16:05:55Z

<p>129.57.167.199: </p> <hr /> <div>'''Clasxt's''' are mac mini's running MAC OS X.<br /> <br /> '''Initial installation'''<br /> <br /> * connect monitor, ethernet, keyboard and mouse and power up; sometimes it will not recognize keyboard or/and mouse, in that case just unplug mouse/keyboard and plug them back; follow instructions to identify keyboard; when asked to 'Create Your Account', enter 'admin' with usual root pass<br /> <br /> * in '''System preferences/Network''': turn off '''AirPort'''; configure '''Ethernet''' as Manually and type IP address (ex. 129.56.167.xxx), mask (ex. 255.255.255.0), router (ex. 129.57.167.99), DNS server (ex. 129.57.167.5, 129.57.167.14) and search domain (ex. jlab.org); goto '''Advanced/Proxies''', check '''Automatic Proxy Configuration''' and type in file name '''http://jprox.jlab.org/wpad.dat'''<br /> <br /> * in '''System preferences/Accounts''' change Admin's user password to the our clon root password (if not done yet, should be done on first step); create new user '''clasrun''' with usual clasrun's pass, keep '''Automatic login''' is '''ON'''; click on '''Login Options''' and choose '''Automatic Login''' as '''clasrun'''<br /> <br /> * in '''System preferences/Sharing''' set correct computer name (ex. clasxt35); enable '''Remote Login''' for user '''admin''' only<br /> <br /> * in '''System preferences/Energy Saver''' move '''Computer Sleep''' to '''Never''' to prevent user's forced logging off, and click on '''Start up automatically after a power failure'''<br /> <br /> * type ''sudo emacs /etc/ssh_config'' and set '''Host *''' and '''ForwardX11 yes'''<br /> <br /> * insert '''Mac OS X Install DVD''' and install '''Xcode''' and '''Optional Installs''' (last one contains X11)<br /> <br /> * insert '''Applications Install DVD''' and click on '''Install Bundled Software''', then follow instructions<br /> <br /> * run '''Software Update'''<br /> <br /> <br /> '''NOTE:''' to patch machine remotely ssh as ''admin'' with usual root pass; to check for updates, use ''softwareupdate --list''; for actual update, use ''sudo softwareupdate --install --all'' and then ''sudo reboot'' commands.<br /> <br /> <br /> <br /> '''OBSOLETE: OLD DISKLESS CLIENTS '''<br /> <br /> '''Clasxt''' machines are diskless 'thin clients' from neoware, running newlinux. We have 5 those machines still in use:<br /> <br /> * clasxt23 (425563, Counting room)<br /> <br /> * clasxt33 <br /> <br /> * clasxt34 (F425591, EEL room 121)<br /> <br /> * clasxt35 (F425584, counting room)<br /> <br /> * clasxt37<br /> <br /> * clasxt39<br /> <br /> * clasxt40 (F425589, counting room)<br /> <br /> To reboot in single user mode do following:<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt should display 'Software'<br /> * Enter ''Software -s ramdisk=12000'' and press enter<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt<br /> <br /> <br /> <br /> '''IMPORTANT:'''<br /> <br /> On clon machines where clasxt's suppose to login, XDM server must be running. On Solaris 10 XDM server is running as part of ''dtlogin''. By default it has following options:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 7799 1 0 17:25:38 ? 0:00 /usr/dt/bin/dtlogin -daemon -udpPort 0<br /> <br /> which means upd connection is not allowed. Looking into options will see following:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> dtlogin/args astring \ -udpPort\ 0<br /> <br /> To change that use following command:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot;\&quot;<br /> <br /> Now that option is gone:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> clon00:/etc&gt;<br /> <br /> To place that option back type following:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot; -udpPort 0\&quot;<br /> <br /> Restart dtlogin server:<br /> <br /> /etc/init.d/dtlogin stop<br /> /etc/init.d/dtlogin start<br /> <br /> Now it is running without upd restriction:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 11503 1 0 17:30:46 ? 0:00 /usr/dt/bin/dtlogin -daemon<br /> <br /> <br /> In addition to that, to make fonts loading process work enable xfs service. Normally it will be enabled on the machines with monitors, but on servers like clon00 and clon10 it will be disabled by default:<br /> <br /> clon00:/etc&gt; svcs -a | grep xfs<br /> disabled Jan_04 svc:/application/x11/xfs:default<br /> clon00:/etc&gt;<br /> <br /> so enable it:<br /> <br /> clon00:/etc&gt; svcadm enable svc:/application/x11/xfs<br /> clon00:/etc&gt; svcs | grep xfs<br /> online 12:55:53 svc:/application/x11/xfs:default<br /> clon00:/etc&gt; <br /> <br /> <br /> <br /> <br /> <br /> Some useful information can be found in following paper:<br /> <br /> Some reports indicate that 3.x builds do not work. The error that is reported is<br /> FATAL ERROR<br /> The device that contains the configuration file (config.xml) could not be found. m0n0wall cannot continue booting.<br /> I do not yet know of a solution. This tutorial should be construed to apply only to the 2.x builds in the meantime. Please email me if you get 3.x working on an EON.<br /> <br /> Here's how to install the latest build of the excellent m0n0wall firewall on a Neoware EON 4000 thin client. These machines make excellent firewalls for home users and small businesses because they are cheap, compact, sturdy, and powerful enough to run a several megabit connection. The hardware is available in a variety of configurations, with CPUs roughly equivalent to a 150-200Mhz Pentium. Before embarking on this little journey, you should be aware of a few caveats:<br /> <br /> * Some Neoware boxes come with a 32-pin Disk-on-Chip module in a socket on the motherboard. m0n0wall does not ship with the required driver to run this module. Therefore, on these systems you will need a hard drive, compact flash to IDE adapter, or similar device to boot from. You may also be able to netboot your firewall (this is supported on the built-in network device), though I do not cover that in this tutorial.<br /> * The motherboard accepts both PC133 DIMMs or SO-DIMMs. It will use both at the same time. However, when using a DIMM, be sure it is less than 1.1&quot; (28mm) tall, or you will not be able to install a second network card.<br /> * There are many different revisions of the NeoLinux operating system and not all include the necessary software to complete this tutorial.<br /> * You may need to purchase several EON 4000s to get suitable software and hardware.<br /> * These instructions were based on NeoLinux 2.4-100802, with kernel 2.2.20. Your particular configuration may vary slightly.<br /> <br /> With those potential issues in mind, follow along!<br /> <br /> There are three main steps to be completed to get m0n0wall running on your EON. First, you will need to get single-user access to the NeoLinux installation. Next, you need to enable networking and fetch and install m0n0wall. Third, you need to configure it to fit your requirements. I will address the first two of these, as adequate resources exist to help with the latter.<br /> <br /> To begin, you will need:<br /> <br /> * One or more Neoware EONs with disk-on-chip modules that plug into the IDE header<br /> * Access to the internet from your EON (or to a web server on a LAN)<br /> * A supported PCI network card. Common Intel or 3Com cards work fine.<br /> * At least 64MB of suitable memory. Some EONs ship with SO-DIMMs, others with DIMMs. These should be short enough to accomodate a PCI network card.<br /> * See the m0n0wall supported hardware page for more information.<br /> <br /> Step ONE: Get single-user access to the NeoLinux distribution.<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt may vary, but pressing tab should display either 'Software' or 'Eon_Software'.<br /> * Enter, as appropriate, either<br /> Software -s ramdisk=12000<br /> or<br /> Eon_Software -s ramdisk=12000<br /> and press enter.<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt.<br /> <br /> Step TWO: Fetch and install m0n0wall.<br /> <br /> * Check that your installation has the necessary software:<br /> bash# ls /usr/bin/wget<br /> . If NeoLinux reports that it is not found, you will have to try a different EON. Keep this hardware however: a single working EON can program m0n0wall onto several disk-on-chip modules, even those without the proper software. More on this later.<br /> * Plug the EON into a network which provides DHCP information and enable the ethernet connection:<br /> bash# cp /etc/sysconfig/network-scripts/ifcfg-eth0.default /etc/sysconfig/network-scripts/ifcfg-eth0<br /> bash# ifup eth0<br /> * Create a ramdisk on which to place temporary files during the installation:<br /> bash# mkfs.ext2 /dev/ram0<br /> bash# mount /dev/ram0 /mnt/usbcdrom<br /> bash# cd /mnt/usbcdrom<br /> bash# /usr/bin/wget http://hostname/path/to/m0n0wall<br /> bash# cp /bin/gunzip .<br /> bash# cp /bin/dd .<br /> * Now you're ready. You have created a ramdisk with the two utilities you will need to rewrite IDE disk-on-chip modules with m0n0wall. At this point, if you have modules containing copies of NeoLinux without wget, you should try using them first. That way if something goes wrong you can repeat these steps later. With the machine running, remove the IDE DOC that you booted from and replace it with the one you want to reprogram.<br /> * Then,<br /> gunzip -c m0n0wall-file-name.img | dd of=/dev/hda bs=16k<br /> Ignore the warning about trailing garbage.<br /> <br /> That's it! At this point you can remove the DOC and replace it with another one and repeat the reprogramming step, as many times as needed.<br /> <br /> When you next boot the machine, it should load m0n0wall exactly as it would on any other x86-compatible system. Jump right in with the m0n0wall quick-start guide for PC platforms. Chapter 3: Initial Configuration is probably where you will want to start. Good luck!<br /> <br /> Version 0.3 | Content date: 05 July 2008 | Page last generated: 2009-01-18 13:11 CST</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=Scratch&diff=5430 2011-08-31T16:08:44Z

<p>129.57.167.199: </p> <hr /> <div>test setup error aug 31, 2011:<br /> ...<br /> 0x9478760 (ROLS_LOOP): INFO: User Go ... <br /> proc_thread: waiting= 31106 processing= 234 microsec per event (nev=59)<br /> net_thread: waiting= 21361 sending= 2 microsec per event (nev=108)<br /> proc_thread: waiting= 12613 processing= 106 microsec per event (nev=66)<br /> proc_thread: waiting= 13237 processing= 137 microsec per event (nev=66)<br /> net_thread: waiting= 13001 sending= 1 microsec per event (nev=129)<br /> proc_thread: waiting= 12753 processing= 110 microsec per event (nev=65)<br /> proc_thread: waiting= 13227 processing= 106 microsec per event (nev=66)<br /> 0x9478760 (ROLS_LOOP): tdc1190ReadBoardDmaDone: WRONG: nbytes_save[4]=176, res=0 =&gt; mbytes=176<br /> 0x9478760 (ROLS_LOOP): [ 4] ERROR: tdc1190ReadEvent[Dma] returns -2<br /> 0x9478760 (ROLS_LOOP): [ 5] ERROR: tdc1190ReadEvent[Dma] returns 0<br /> 0x9478760 (ROLS_LOOP): [ 6] ERROR: tdc1190ReadEvent[Dma] returns 0<br /> 0x9478760 (ROLS_LOOP): [ 7] ERROR: tdc1190ReadEvent[Dma] returns 0<br /> 0x9478760 (ROLS_LOOP): [ 8] ERROR: tdc1190ReadEvent[Dma] returns 0<br /> 0x9478760 (ROLS_LOOP): tdc1190ReadStart: [ 0] not ready ! (nev=0)<br /> 0x9478760 (ROLS_LOOP): tdc1190ReadStart: [ 1] not ready ! (nev=0)<br /> 0x9478760 (ROLS_LOOP): tdc1190ReadStart: [ 2] not ready ! (nev=0)<br /> 0x9478760 (ROLS_LOOP): tdc1190ReadStart: [ 3] not ready ! (nev=0)<br /> 0x9478760 (ROLS_LOOP): tdc1190ReadStart: [ 4] not ready ! (nev=0)<br /> 0x9478760 (ROLS_LOOP): tdc1190ReadStart: [ 5] not ready ! (nev=0)<br /> 0x9478760 (ROLS_LOOP): tdc1190ReadStart: [ 6] not ready ! (nev=0)<br /> 0x9478760 (ROLS_LOOP): tdc1190ReadStart: [ 7] not ready ! (nev=0)<br /> 0x9478760 (ROLS_LOOP): tdc1190ReadStart: [ 8] not ready ! (nev=0)<br /> 0x9478760 (ROLS_LOOP): [ 0] ERROR: tdc1190ReadEvent[Dma] returns 0<br /> 0x9478760 (ROLS_LOOP): [ 1] ERROR: tdc1190ReadEvent[Dma] returns 0<br /> 0x9478760 (ROLS_LOOP): [ 2] ERROR: tdc1190ReadEvent[Dma] returns 0<br /> ...............<br /> <br /> Sergey Kuleshov Aug 15 2011: send Ben's schematic for DC TDC, and mentioned young engineers from Chile for CLAS disassemble/CLAS12 assemble <br /> <br /> timeout 2: 9599514 + 64 = 9599578<br /> timeout: 9599579 9599578<br /> SEND_BUFFER_ROC 4<br /> timeout 2: 9599579 + 64 = 9599643<br /> timeout: 9599644 9599643<br /> SEND_BUFFER_ROC 4<br /> interrupt: SEND_BUFFER_ROL1<br /> timeout 2: 9599644 + 64 = 9599708<br /> timeout: 9599709 9599708<br /> SEND_BUFFER_ROC 4<br /> interrupt: SEND_BUFFER_ROL1<br /> attempt to send short buffer failed !!!<br /> timeout 2: 9599709 + 64 = 9599773<br /> timeout: 9599774 9599773<br /> SEND_BUFFER_ROC 4<br /> timeout 2: 9599774 + 64 = 9599838<br /> ERROR1: LINK_sized_write() returns errno=851971 (cc=-1, sizeof(nbytes)=4(104040), netlong=104040)<br /> ERROR: net_thread failed (in LINK_sized_write).<br /> timeout: 9599839 9599838<br /> SEND_BUFFER_ROC 4<br /> ERROR: big0.failure=0, big1.failure=1<br /> interrupt: SEND_BUFFER_ROL1<br /> 0x9247630 (coda_proc): timer: 2 microsec (min=0 max=601 rms**2=1)<br /> 0x9247630 (coda_proc): timer: 2 microsec (min=0 max=601 rms**2=6)<br /> interrupt: SEND_BUFFER_ROL1<br /> <br /> <br /> -------------------------<br /> <br /> Quota check:<br /> <br /> http://cc.jlab.org/cgi-bin/quotacheck.cgi<br /> <br /> Nerses:<br /> <br /> Home number is +374 10 425049<br /> <br /> Cell phone +374 91 206 217 <br /> <br /> -----------<br /> <br /> clon02:/etc&gt; ifconfig -a<br /> lo0: flags=2001000849&lt;UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL&gt; mtu 8232 index 1<br /> inet 131.225.70.20 netmask ff000000 <br /> age0: flags=1000842&lt;BROADCAST,RUNNING,MULTICAST,IPv4&gt; mtu 1500 index 2<br /> inet 131.225.70.20 netmask fffffc00 broadcast 131.225.255.255<br /> ether 0:a0:80:0:52:e5 <br /> eri0: flags=1000843&lt;UP,BROADCAST,RUNNING,MULTICAST,IPv4&gt; mtu 1500 index 3<br /> inet 129.57.167.2 netmask ffffff00 broadcast 129.57.167.255<br /> ether 0:3:ba:1d:9b:c0 <br /> clon02:/etc&gt; <br /> <br /> <br /> -------<br /> <br /> SUNW-MSG-ID: ZFS-8000-HC, TYPE: Error, VER: 1, SEVERITY: Major<br /> EVENT-TIME: Thu Mar 5 17:41:00 EST 2009<br /> PLATFORM: SUNW,Netra-240, CSN: -, HOSTNAME: clon10<br /> SOURCE: zfs-diagnosis, REV: 1.0<br /> EVENT-ID: 2f3d5430-2bbb-c8aa-87d5-f79b44f89edf<br /> DESC: The ZFS pool has experienced currently unrecoverable I/O failures. Refer to http://sun.com/msg/ZFS-8000-HC for more information.<br /> AUTO-RESPONSE: No automated response will be taken.<br /> IMPACT: Read and write I/Os cannot be serviced.<br /> REC-ACTION: <br /> <br /> The pool has experienced I/O failures. Since the ZFS pool property 'failmode'<br /> is set to 'wait', all I/Os (reads and writes) are blocked. See the zpool(1M)<br /> manpage for more information on the 'failmode' property. Manual intervention<br /> is required for I/Os to be serviced. You can see which devices are<br /> affected by running 'zpool status -x':<br /> <br /> <br /> <br /> # zpool status -x<br /> pool: test<br /> state: FAULTED<br /> status: There are I/O failures.<br /> action: Make sure the affected devices are connected, then run 'zpool clear'.<br /> see: http://www.sun.com/msg/ZFS-8000-HC<br /> scrub: none requested<br /> config:<br /> <br /> NAME STATE READ WRITE CKSUM<br /> test FAULTED 0 13 0 insufficient replicas<br /> c0t0d0 FAULTED 0 7 0 experienced I/O failures<br /> c0t1d0 ONLINE 0 0 0<br /> <br /> errors: 1 data errors, use '-v' for a list<br /> <br /> <br /> <br /> After you have made sure the affected devices are connected, run 'zpool clear'<br /> to allow I/O to the pool again:<br /> <br /> <br /> <br /> # zpool clear test<br /> <br /> <br /> <br /> If I/O failures continue to happen, then applications and commands for the<br /> pool may hang. At this point, a reboot may be necessary to allow I/O to the<br /> pool again.<br /> <br /> <br /> ----<br /> <br /> mgetty<br /> <br /> Sergey --- does this help you ? Today marked the 3rd week since this <br /> case was opened....<br /> <br /> Paul<br /> <br /> <br /> <br /> -------- Original Message --------<br /> Subject: CASE 66172087<br /> Date: Wed, 28 Jan 2009 12:39:51 -0500<br /> From: Roland 'butch' Morrissette - Sun Microsystems <br /> &lt;Roland.Morrissette@sun.com&gt;<br /> To: letta@jlab.org<br /> <br /> <br /> <br /> Paul<br /> <br /> Received this from engineering. Hopefully this is of some helpfull.<br /> <br /> xdm is creating $HOME/.Xauthority file, xauth only reads it. In <br /> $HOME/.Xdefaults file try adding the following entry as an alternate <br /> location to see if it works.<br /> *<br /> <br /> DisplayManager.DISPLAY.userAuthDir<br /> <br /> */DISPLAY should be the actual display, like<br /> <br /> /DisplayManager.host1:0.0.userAuthDir: /path/to/alternate/file<br /> <br /> *<br /> *(If this does not work and still $HOME/.Xauthority file gets written <br /> try changing the permissions on $HOME/.Xauthority file to readonly)<br /> <br /> Regards,<br /> <br /> -- <br /> <br /> Roland 'Butch' Morrissette<br /> Sun Service OS Support<br /> Sun Microsystems, Inc.<br /> <br /> phone: (781) 442-7112<br /> email: roland.morrissette@sun.com<br /> (800)USA-4SUN (Reference your Case Id #)<br /> <br /> My Working Hours : 8am-4pm ET, Monday thru Friday <br /> My Manager's Email: dawn.ball@sun.com <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> 5126<br /> 303-6644<br /> <br /> CLAS12 DC (Mac 14-nov-2007): 2 stereo, +-6 degrees, good resolution (1% dp/p, 1 mrad angle), six 6-layer superlayers, 112 wires per layer; reconstruction improvements: use double hits, use segment angle in road dictionary, early l-r ambig. resolution (now it resolved locally and then corrected after track reconstructed ?), find tracks with no TOF hit and cut off accidental tracks (using residials ?), derive off-diagonal terms in error matrix<br /> <br /> <br /> SVT readout:<br /> <br /> SVX4 - old chip<br /> 132ns clock, 40pipeline cells -&gt;5.2us trigger latency; can select readout window like pipeline TDCs (position defined +-132us, window size 132ns fixed)<br /> initial part stored upto 4 events, they are rotating internally<br /> 32 bits per hit, 128 channels per chip, ... -&gt; 3.2us per chip to get data from the chip to the buffer of 512 full events<br /> L2 pipeline 16us<br /> L1 latency from Amrit is 3us, Amrit will try to make it 4us<br /> Use the same clock as entire CLAS12 trigger system (256MHz)<br /> <br /> FSSR 125ns instead of 132ns (built for BTev, never used)<br /> self-triggering, do not need L1ACCEPT, L2 pipe 16us can be implemented<br /> <br /> SVX4 goes to review !!!<br /> <br /> Generic DAQ drawing will be sent to Amrit in April</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=Clasxt&diff=5321 2011-05-17T19:42:27Z

<p>129.57.167.199: </p> <hr /> <div>'''Clasxt's''' are mac mini's running MAC OS X.<br /> <br /> '''Initial installation'''<br /> <br /> * connect monitor, ethernet, keyboard and mouse and power up; sometimes it will not recognize keyboard or/and mouse, in that case just unplug mouse/keyboard and plug them back; follow instructions to identify keyboard<br /> <br /> * in '''System preferences/Network''': turn off '''AirPort'''; configure '''Ethernet''' as Manually and type IP address (ex. 129.56.167.xxx), mask (ex. 255.255.255.0), router (ex. 129.57.167.99), DNS server (ex. 129.57.167.5, 129.57.167.14) and search domain (ex. jlab.org)<br /> <br /> * in '''System preferences/Accounts''' change Admin's user password to the our clon root password; create new user '''clasrun''' with usual clasrun's pass, keep '''Automatic login''' is '''ON'''; click on '''Login Options''' and choose '''Automatic Login''' as '''clasrun'''<br /> <br /> * in '''System preferences/Sharing''' set correct computer name (ex. clasxt35); enable '''Remote Login''' for user '''admin''' only<br /> <br /> * in '''System preferences/Energy Saver''' move '''Computer Sleep''' to '''Never''' to prevent user's forced logging off, and click on '''Start up automatically after a power failure'''<br /> <br /> * type ''sudo emacs /etc/ssh_config'' and set '''Host *''' and '''ForwardX11 yes'''<br /> <br /> * insert '''Mac OS X Install DVD''' and install '''Xcode''' and '''Optional Installs''' (last one contains X11)<br /> <br /> * insert '''Applications Install DVD''' and click on '''Install Bundled Software''', then follow instructions<br /> <br /> * run '''Software Update'''<br /> <br /> <br /> <br /> '''OBSOLETE: OLD DISKLESS CLIENTS '''<br /> <br /> '''Clasxt''' machines are diskless 'thin clients' from neoware, running newlinux. We have 5 those machines still in use:<br /> <br /> * clasxt23<br /> <br /> * clasxt33<br /> <br /> * clasxt35<br /> <br /> * clasxt37<br /> <br /> * clasxt39<br /> <br /> * clasxt40<br /> <br /> To reboot in single user mode do following:<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt should display 'Software'<br /> * Enter ''Software -s ramdisk=12000'' and press enter<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt<br /> <br /> <br /> <br /> '''IMPORTANT:'''<br /> <br /> On clon machines where clasxt's suppose to login, XDM server must be running. On Solaris 10 XDM server is running as part of ''dtlogin''. By default it has following options:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 7799 1 0 17:25:38 ? 0:00 /usr/dt/bin/dtlogin -daemon -udpPort 0<br /> <br /> which means upd connection is not allowed. Looking into options will see following:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> dtlogin/args astring \ -udpPort\ 0<br /> <br /> To change that use following command:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot;\&quot;<br /> <br /> Now that option is gone:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> clon00:/etc&gt;<br /> <br /> To place that option back type following:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot; -udpPort 0\&quot;<br /> <br /> Restart dtlogin server:<br /> <br /> /etc/init.d/dtlogin stop<br /> /etc/init.d/dtlogin start<br /> <br /> Now it is running without upd restriction:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 11503 1 0 17:30:46 ? 0:00 /usr/dt/bin/dtlogin -daemon<br /> <br /> <br /> In addition to that, to make fonts loading process work enable xfs service. Normally it will be enabled on the machines with monitors, but on servers like clon00 and clon10 it will be disabled by default:<br /> <br /> clon00:/etc&gt; svcs -a | grep xfs<br /> disabled Jan_04 svc:/application/x11/xfs:default<br /> clon00:/etc&gt;<br /> <br /> so enable it:<br /> <br /> clon00:/etc&gt; svcadm enable svc:/application/x11/xfs<br /> clon00:/etc&gt; svcs | grep xfs<br /> online 12:55:53 svc:/application/x11/xfs:default<br /> clon00:/etc&gt; <br /> <br /> <br /> <br /> <br /> <br /> Some useful information can be found in following paper:<br /> <br /> Some reports indicate that 3.x builds do not work. The error that is reported is<br /> FATAL ERROR<br /> The device that contains the configuration file (config.xml) could not be found. m0n0wall cannot continue booting.<br /> I do not yet know of a solution. This tutorial should be construed to apply only to the 2.x builds in the meantime. Please email me if you get 3.x working on an EON.<br /> <br /> Here's how to install the latest build of the excellent m0n0wall firewall on a Neoware EON 4000 thin client. These machines make excellent firewalls for home users and small businesses because they are cheap, compact, sturdy, and powerful enough to run a several megabit connection. The hardware is available in a variety of configurations, with CPUs roughly equivalent to a 150-200Mhz Pentium. Before embarking on this little journey, you should be aware of a few caveats:<br /> <br /> * Some Neoware boxes come with a 32-pin Disk-on-Chip module in a socket on the motherboard. m0n0wall does not ship with the required driver to run this module. Therefore, on these systems you will need a hard drive, compact flash to IDE adapter, or similar device to boot from. You may also be able to netboot your firewall (this is supported on the built-in network device), though I do not cover that in this tutorial.<br /> * The motherboard accepts both PC133 DIMMs or SO-DIMMs. It will use both at the same time. However, when using a DIMM, be sure it is less than 1.1&quot; (28mm) tall, or you will not be able to install a second network card.<br /> * There are many different revisions of the NeoLinux operating system and not all include the necessary software to complete this tutorial.<br /> * You may need to purchase several EON 4000s to get suitable software and hardware.<br /> * These instructions were based on NeoLinux 2.4-100802, with kernel 2.2.20. Your particular configuration may vary slightly.<br /> <br /> With those potential issues in mind, follow along!<br /> <br /> There are three main steps to be completed to get m0n0wall running on your EON. First, you will need to get single-user access to the NeoLinux installation. Next, you need to enable networking and fetch and install m0n0wall. Third, you need to configure it to fit your requirements. I will address the first two of these, as adequate resources exist to help with the latter.<br /> <br /> To begin, you will need:<br /> <br /> * One or more Neoware EONs with disk-on-chip modules that plug into the IDE header<br /> * Access to the internet from your EON (or to a web server on a LAN)<br /> * A supported PCI network card. Common Intel or 3Com cards work fine.<br /> * At least 64MB of suitable memory. Some EONs ship with SO-DIMMs, others with DIMMs. These should be short enough to accomodate a PCI network card.<br /> * See the m0n0wall supported hardware page for more information.<br /> <br /> Step ONE: Get single-user access to the NeoLinux distribution.<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt may vary, but pressing tab should display either 'Software' or 'Eon_Software'.<br /> * Enter, as appropriate, either<br /> Software -s ramdisk=12000<br /> or<br /> Eon_Software -s ramdisk=12000<br /> and press enter.<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt.<br /> <br /> Step TWO: Fetch and install m0n0wall.<br /> <br /> * Check that your installation has the necessary software:<br /> bash# ls /usr/bin/wget<br /> . If NeoLinux reports that it is not found, you will have to try a different EON. Keep this hardware however: a single working EON can program m0n0wall onto several disk-on-chip modules, even those without the proper software. More on this later.<br /> * Plug the EON into a network which provides DHCP information and enable the ethernet connection:<br /> bash# cp /etc/sysconfig/network-scripts/ifcfg-eth0.default /etc/sysconfig/network-scripts/ifcfg-eth0<br /> bash# ifup eth0<br /> * Create a ramdisk on which to place temporary files during the installation:<br /> bash# mkfs.ext2 /dev/ram0<br /> bash# mount /dev/ram0 /mnt/usbcdrom<br /> bash# cd /mnt/usbcdrom<br /> bash# /usr/bin/wget http://hostname/path/to/m0n0wall<br /> bash# cp /bin/gunzip .<br /> bash# cp /bin/dd .<br /> * Now you're ready. You have created a ramdisk with the two utilities you will need to rewrite IDE disk-on-chip modules with m0n0wall. At this point, if you have modules containing copies of NeoLinux without wget, you should try using them first. That way if something goes wrong you can repeat these steps later. With the machine running, remove the IDE DOC that you booted from and replace it with the one you want to reprogram.<br /> * Then,<br /> gunzip -c m0n0wall-file-name.img | dd of=/dev/hda bs=16k<br /> Ignore the warning about trailing garbage.<br /> <br /> That's it! At this point you can remove the DOC and replace it with another one and repeat the reprogramming step, as many times as needed.<br /> <br /> When you next boot the machine, it should load m0n0wall exactly as it would on any other x86-compatible system. Jump right in with the m0n0wall quick-start guide for PC platforms. Chapter 3: Initial Configuration is probably where you will want to start. Good luck!<br /> <br /> Version 0.3 | Content date: 05 July 2008 | Page last generated: 2009-01-18 13:11 CST</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=Clasxt&diff=5320 2011-05-17T19:39:38Z

<p>129.57.167.199: </p> <hr /> <div>'''Clasxt's''' are mac mini's running MAC OS X.<br /> <br /> '''Initial installation'''<br /> <br /> * connect monitor, ethernet, keyboard and mouse and power up; sometimes it will not recognize keyboard or/and mouse, in that case just unplug mouse/keyboard and plug them back; follow instructions to identify keyboard<br /> <br /> * in '''System preferences/Network''': turn off '''AirPort'''; configure '''Ethernet''' as Manually and type IP address (ex. 129.56.167.xxx), mask (ex. 255.255.255.0), router (ex. 129.57.167.99), DNS server (ex. 129.57.167.5, 129.57.167.14) and search domain (ex. jlab.org)<br /> <br /> * in '''System preferences/Accounts''' change Admin's user password to the our clon root password; create new user '''clasrun''' with usual clasrun's pass, keep '''Automatic login''' is '''ON'''; click on '''Login Options''' and choose '''Automatic Login''' as '''clasrun'''<br /> <br /> * in '''System preferences/Sharing''' set correct computer name (ex. clasxt35); enable '''Remote Login''' for user '''admin''' only<br /> <br /> * in '''System preferences/Energy Saver''' move '''Computer Sleep''' to '''Never''' to prevent user's forced logging off, and click on '''Start up automatically after a power failure'''<br /> <br /> * insert '''Mac OS X Install DVD''' and install '''Xcode''' and '''Optional Installs''' (last one contains X11)<br /> <br /> * insert '''Applications Install DVD''' and click on '''Install Bundled Software''', then follow instructions<br /> <br /> * run '''Software Update'''<br /> <br /> <br /> <br /> '''OBSOLETE: OLD DISKLESS CLIENTS '''<br /> <br /> '''Clasxt''' machines are diskless 'thin clients' from neoware, running newlinux. We have 5 those machines still in use:<br /> <br /> * clasxt23<br /> <br /> * clasxt33<br /> <br /> * clasxt35<br /> <br /> * clasxt37<br /> <br /> * clasxt39<br /> <br /> * clasxt40<br /> <br /> To reboot in single user mode do following:<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt should display 'Software'<br /> * Enter ''Software -s ramdisk=12000'' and press enter<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt<br /> <br /> <br /> <br /> '''IMPORTANT:'''<br /> <br /> On clon machines where clasxt's suppose to login, XDM server must be running. On Solaris 10 XDM server is running as part of ''dtlogin''. By default it has following options:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 7799 1 0 17:25:38 ? 0:00 /usr/dt/bin/dtlogin -daemon -udpPort 0<br /> <br /> which means upd connection is not allowed. Looking into options will see following:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> dtlogin/args astring \ -udpPort\ 0<br /> <br /> To change that use following command:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot;\&quot;<br /> <br /> Now that option is gone:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> clon00:/etc&gt;<br /> <br /> To place that option back type following:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot; -udpPort 0\&quot;<br /> <br /> Restart dtlogin server:<br /> <br /> /etc/init.d/dtlogin stop<br /> /etc/init.d/dtlogin start<br /> <br /> Now it is running without upd restriction:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 11503 1 0 17:30:46 ? 0:00 /usr/dt/bin/dtlogin -daemon<br /> <br /> <br /> In addition to that, to make fonts loading process work enable xfs service. Normally it will be enabled on the machines with monitors, but on servers like clon00 and clon10 it will be disabled by default:<br /> <br /> clon00:/etc&gt; svcs -a | grep xfs<br /> disabled Jan_04 svc:/application/x11/xfs:default<br /> clon00:/etc&gt;<br /> <br /> so enable it:<br /> <br /> clon00:/etc&gt; svcadm enable svc:/application/x11/xfs<br /> clon00:/etc&gt; svcs | grep xfs<br /> online 12:55:53 svc:/application/x11/xfs:default<br /> clon00:/etc&gt; <br /> <br /> <br /> <br /> <br /> <br /> Some useful information can be found in following paper:<br /> <br /> Some reports indicate that 3.x builds do not work. The error that is reported is<br /> FATAL ERROR<br /> The device that contains the configuration file (config.xml) could not be found. m0n0wall cannot continue booting.<br /> I do not yet know of a solution. This tutorial should be construed to apply only to the 2.x builds in the meantime. Please email me if you get 3.x working on an EON.<br /> <br /> Here's how to install the latest build of the excellent m0n0wall firewall on a Neoware EON 4000 thin client. These machines make excellent firewalls for home users and small businesses because they are cheap, compact, sturdy, and powerful enough to run a several megabit connection. The hardware is available in a variety of configurations, with CPUs roughly equivalent to a 150-200Mhz Pentium. Before embarking on this little journey, you should be aware of a few caveats:<br /> <br /> * Some Neoware boxes come with a 32-pin Disk-on-Chip module in a socket on the motherboard. m0n0wall does not ship with the required driver to run this module. Therefore, on these systems you will need a hard drive, compact flash to IDE adapter, or similar device to boot from. You may also be able to netboot your firewall (this is supported on the built-in network device), though I do not cover that in this tutorial.<br /> * The motherboard accepts both PC133 DIMMs or SO-DIMMs. It will use both at the same time. However, when using a DIMM, be sure it is less than 1.1&quot; (28mm) tall, or you will not be able to install a second network card.<br /> * There are many different revisions of the NeoLinux operating system and not all include the necessary software to complete this tutorial.<br /> * You may need to purchase several EON 4000s to get suitable software and hardware.<br /> * These instructions were based on NeoLinux 2.4-100802, with kernel 2.2.20. Your particular configuration may vary slightly.<br /> <br /> With those potential issues in mind, follow along!<br /> <br /> There are three main steps to be completed to get m0n0wall running on your EON. First, you will need to get single-user access to the NeoLinux installation. Next, you need to enable networking and fetch and install m0n0wall. Third, you need to configure it to fit your requirements. I will address the first two of these, as adequate resources exist to help with the latter.<br /> <br /> To begin, you will need:<br /> <br /> * One or more Neoware EONs with disk-on-chip modules that plug into the IDE header<br /> * Access to the internet from your EON (or to a web server on a LAN)<br /> * A supported PCI network card. Common Intel or 3Com cards work fine.<br /> * At least 64MB of suitable memory. Some EONs ship with SO-DIMMs, others with DIMMs. These should be short enough to accomodate a PCI network card.<br /> * See the m0n0wall supported hardware page for more information.<br /> <br /> Step ONE: Get single-user access to the NeoLinux distribution.<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt may vary, but pressing tab should display either 'Software' or 'Eon_Software'.<br /> * Enter, as appropriate, either<br /> Software -s ramdisk=12000<br /> or<br /> Eon_Software -s ramdisk=12000<br /> and press enter.<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt.<br /> <br /> Step TWO: Fetch and install m0n0wall.<br /> <br /> * Check that your installation has the necessary software:<br /> bash# ls /usr/bin/wget<br /> . If NeoLinux reports that it is not found, you will have to try a different EON. Keep this hardware however: a single working EON can program m0n0wall onto several disk-on-chip modules, even those without the proper software. More on this later.<br /> * Plug the EON into a network which provides DHCP information and enable the ethernet connection:<br /> bash# cp /etc/sysconfig/network-scripts/ifcfg-eth0.default /etc/sysconfig/network-scripts/ifcfg-eth0<br /> bash# ifup eth0<br /> * Create a ramdisk on which to place temporary files during the installation:<br /> bash# mkfs.ext2 /dev/ram0<br /> bash# mount /dev/ram0 /mnt/usbcdrom<br /> bash# cd /mnt/usbcdrom<br /> bash# /usr/bin/wget http://hostname/path/to/m0n0wall<br /> bash# cp /bin/gunzip .<br /> bash# cp /bin/dd .<br /> * Now you're ready. You have created a ramdisk with the two utilities you will need to rewrite IDE disk-on-chip modules with m0n0wall. At this point, if you have modules containing copies of NeoLinux without wget, you should try using them first. That way if something goes wrong you can repeat these steps later. With the machine running, remove the IDE DOC that you booted from and replace it with the one you want to reprogram.<br /> * Then,<br /> gunzip -c m0n0wall-file-name.img | dd of=/dev/hda bs=16k<br /> Ignore the warning about trailing garbage.<br /> <br /> That's it! At this point you can remove the DOC and replace it with another one and repeat the reprogramming step, as many times as needed.<br /> <br /> When you next boot the machine, it should load m0n0wall exactly as it would on any other x86-compatible system. Jump right in with the m0n0wall quick-start guide for PC platforms. Chapter 3: Initial Configuration is probably where you will want to start. Good luck!<br /> <br /> Version 0.3 | Content date: 05 July 2008 | Page last generated: 2009-01-18 13:11 CST</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=Clasxt&diff=5319 2011-05-17T19:23:52Z

<p>129.57.167.199: </p> <hr /> <div>'''Clasxt's''' are mac mini's running MAC OS X.<br /> <br /> '''Initial installation'''<br /> <br /> * connect monitor, ethernet, keyboard and mouse and power up; sometimes it will not recognize keyboard or/and mouse, in that case just unplug mouse/keyboard and plug them back; follow instructions to identify keyboard<br /> <br /> * in '''System preferences/Network''': turn off '''AirPort'''; configure '''Ethernet''' as Manually and type IP address (ex. 129.56.167.xxx), mask (ex. 255.255.255.0), router (ex. 129.57.167.99), DNS server (ex. 129.57.167.5, 129.57.167.14) and search domain (ex. jlab.org)<br /> <br /> * in '''System preferences/Accounts''' change Admin's user password to the our clon root password; create new user '''clasrun''' with usual clasrun's pass, keep '''Automatic login''' is '''ON'''; click on '''Login Options''' and choose '''Automatic Login''' as '''clasrun'''<br /> <br /> * in '''System preferences/Energy Saver''' move '''Computer Sleep''' to '''Never''' to prevent user's forced logging off, and click on '''Start up automatically after a power failure'''<br /> <br /> * insert '''Mac OS X Install DVD''' and install '''Xcode''' and '''Optional Installs''' (last one contains X11)<br /> <br /> * insert '''Applications Install DVD''' and click on '''Install Bundled Software''', then follow instructions<br /> <br /> * run '''Software Update'''<br /> <br /> <br /> <br /> '''OBSOLETE: OLD DISKLESS CLIENTS '''<br /> <br /> '''Clasxt''' machines are diskless 'thin clients' from neoware, running newlinux. We have 5 those machines still in use:<br /> <br /> * clasxt23<br /> <br /> * clasxt33<br /> <br /> * clasxt35<br /> <br /> * clasxt37<br /> <br /> * clasxt39<br /> <br /> * clasxt40<br /> <br /> To reboot in single user mode do following:<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt should display 'Software'<br /> * Enter ''Software -s ramdisk=12000'' and press enter<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt<br /> <br /> <br /> <br /> '''IMPORTANT:'''<br /> <br /> On clon machines where clasxt's suppose to login, XDM server must be running. On Solaris 10 XDM server is running as part of ''dtlogin''. By default it has following options:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 7799 1 0 17:25:38 ? 0:00 /usr/dt/bin/dtlogin -daemon -udpPort 0<br /> <br /> which means upd connection is not allowed. Looking into options will see following:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> dtlogin/args astring \ -udpPort\ 0<br /> <br /> To change that use following command:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot;\&quot;<br /> <br /> Now that option is gone:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> clon00:/etc&gt;<br /> <br /> To place that option back type following:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot; -udpPort 0\&quot;<br /> <br /> Restart dtlogin server:<br /> <br /> /etc/init.d/dtlogin stop<br /> /etc/init.d/dtlogin start<br /> <br /> Now it is running without upd restriction:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 11503 1 0 17:30:46 ? 0:00 /usr/dt/bin/dtlogin -daemon<br /> <br /> <br /> In addition to that, to make fonts loading process work enable xfs service. Normally it will be enabled on the machines with monitors, but on servers like clon00 and clon10 it will be disabled by default:<br /> <br /> clon00:/etc&gt; svcs -a | grep xfs<br /> disabled Jan_04 svc:/application/x11/xfs:default<br /> clon00:/etc&gt;<br /> <br /> so enable it:<br /> <br /> clon00:/etc&gt; svcadm enable svc:/application/x11/xfs<br /> clon00:/etc&gt; svcs | grep xfs<br /> online 12:55:53 svc:/application/x11/xfs:default<br /> clon00:/etc&gt; <br /> <br /> <br /> <br /> <br /> <br /> Some useful information can be found in following paper:<br /> <br /> Some reports indicate that 3.x builds do not work. The error that is reported is<br /> FATAL ERROR<br /> The device that contains the configuration file (config.xml) could not be found. m0n0wall cannot continue booting.<br /> I do not yet know of a solution. This tutorial should be construed to apply only to the 2.x builds in the meantime. Please email me if you get 3.x working on an EON.<br /> <br /> Here's how to install the latest build of the excellent m0n0wall firewall on a Neoware EON 4000 thin client. These machines make excellent firewalls for home users and small businesses because they are cheap, compact, sturdy, and powerful enough to run a several megabit connection. The hardware is available in a variety of configurations, with CPUs roughly equivalent to a 150-200Mhz Pentium. Before embarking on this little journey, you should be aware of a few caveats:<br /> <br /> * Some Neoware boxes come with a 32-pin Disk-on-Chip module in a socket on the motherboard. m0n0wall does not ship with the required driver to run this module. Therefore, on these systems you will need a hard drive, compact flash to IDE adapter, or similar device to boot from. You may also be able to netboot your firewall (this is supported on the built-in network device), though I do not cover that in this tutorial.<br /> * The motherboard accepts both PC133 DIMMs or SO-DIMMs. It will use both at the same time. However, when using a DIMM, be sure it is less than 1.1&quot; (28mm) tall, or you will not be able to install a second network card.<br /> * There are many different revisions of the NeoLinux operating system and not all include the necessary software to complete this tutorial.<br /> * You may need to purchase several EON 4000s to get suitable software and hardware.<br /> * These instructions were based on NeoLinux 2.4-100802, with kernel 2.2.20. Your particular configuration may vary slightly.<br /> <br /> With those potential issues in mind, follow along!<br /> <br /> There are three main steps to be completed to get m0n0wall running on your EON. First, you will need to get single-user access to the NeoLinux installation. Next, you need to enable networking and fetch and install m0n0wall. Third, you need to configure it to fit your requirements. I will address the first two of these, as adequate resources exist to help with the latter.<br /> <br /> To begin, you will need:<br /> <br /> * One or more Neoware EONs with disk-on-chip modules that plug into the IDE header<br /> * Access to the internet from your EON (or to a web server on a LAN)<br /> * A supported PCI network card. Common Intel or 3Com cards work fine.<br /> * At least 64MB of suitable memory. Some EONs ship with SO-DIMMs, others with DIMMs. These should be short enough to accomodate a PCI network card.<br /> * See the m0n0wall supported hardware page for more information.<br /> <br /> Step ONE: Get single-user access to the NeoLinux distribution.<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt may vary, but pressing tab should display either 'Software' or 'Eon_Software'.<br /> * Enter, as appropriate, either<br /> Software -s ramdisk=12000<br /> or<br /> Eon_Software -s ramdisk=12000<br /> and press enter.<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt.<br /> <br /> Step TWO: Fetch and install m0n0wall.<br /> <br /> * Check that your installation has the necessary software:<br /> bash# ls /usr/bin/wget<br /> . If NeoLinux reports that it is not found, you will have to try a different EON. Keep this hardware however: a single working EON can program m0n0wall onto several disk-on-chip modules, even those without the proper software. More on this later.<br /> * Plug the EON into a network which provides DHCP information and enable the ethernet connection:<br /> bash# cp /etc/sysconfig/network-scripts/ifcfg-eth0.default /etc/sysconfig/network-scripts/ifcfg-eth0<br /> bash# ifup eth0<br /> * Create a ramdisk on which to place temporary files during the installation:<br /> bash# mkfs.ext2 /dev/ram0<br /> bash# mount /dev/ram0 /mnt/usbcdrom<br /> bash# cd /mnt/usbcdrom<br /> bash# /usr/bin/wget http://hostname/path/to/m0n0wall<br /> bash# cp /bin/gunzip .<br /> bash# cp /bin/dd .<br /> * Now you're ready. You have created a ramdisk with the two utilities you will need to rewrite IDE disk-on-chip modules with m0n0wall. At this point, if you have modules containing copies of NeoLinux without wget, you should try using them first. That way if something goes wrong you can repeat these steps later. With the machine running, remove the IDE DOC that you booted from and replace it with the one you want to reprogram.<br /> * Then,<br /> gunzip -c m0n0wall-file-name.img | dd of=/dev/hda bs=16k<br /> Ignore the warning about trailing garbage.<br /> <br /> That's it! At this point you can remove the DOC and replace it with another one and repeat the reprogramming step, as many times as needed.<br /> <br /> When you next boot the machine, it should load m0n0wall exactly as it would on any other x86-compatible system. Jump right in with the m0n0wall quick-start guide for PC platforms. Chapter 3: Initial Configuration is probably where you will want to start. Good luck!<br /> <br /> Version 0.3 | Content date: 05 July 2008 | Page last generated: 2009-01-18 13:11 CST</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=Clasxt&diff=5318 2011-05-16T15:46:11Z

<p>129.57.167.199: </p> <hr /> <div>'''Clasxt's''' are mac mini's running MAC OS X.<br /> <br /> '''Initial installation'''<br /> <br /> * connect monitor, ethernet, keyboard and mouse and power up; sometimes it will not recognize keyboard or/and mouse, in that case just unplug mouse/keyboard and plug them back; follow instructions to identify keyboard<br /> <br /> * in '''System preferences/Network''': turn off '''AirPort'''; configure '''Ethernet''' as Manually and type IP address (ex. 129.56.167.xxx), mask (ex. 255.255.255.0), router (ex. 129.57.167.99), DNS server (ex. 129.57.167.5, 129.57.167.14) and search domain (ex. jlab.org)<br /> <br /> * in '''System preferences/Accounts''' change Admin's user password to the our clon root password; create new user '''clasrun''' with usual clasrun's pass, keep '''Automatic login''' is '''ON'''; click on '''Login Options''' and choose '''Automatic Login''' as '''clasrun'''<br /> <br /> * in '''System preferences/Energy Saver''' move '''Computer Sleep''' to '''Never''' to prevent user's forced logging off, and click on '''Start up automatically after a power failure'''<br /> <br /> * insert '''Mac OS X Install DVD''' and install '''Xcode''' and '''Optional Installs''' (last one contains X11)<br /> <br /> * insert '''Applications Install DVD''' and click on '''Install Bundled Software''', then follow instructions<br /> <br /> * run '''Software Update'''<br /> <br /> <br /> <br /> '''OBSOLETE'''<br /> <br /> '''Clasxt''' machines are diskless 'thin clients' from neoware, running newlinux. We have 5 those machines still in use:<br /> <br /> * clasxt23<br /> <br /> * clasxt33<br /> <br /> * clasxt35<br /> <br /> * clasxt37<br /> <br /> * clasxt39<br /> <br /> * clasxt40<br /> <br /> To reboot in single user mode do following:<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt should display 'Software'<br /> * Enter ''Software -s ramdisk=12000'' and press enter<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt<br /> <br /> <br /> <br /> '''IMPORTANT:'''<br /> <br /> On clon machines where clasxt's suppose to login, XDM server must be running. On Solaris 10 XDM server is running as part of ''dtlogin''. By default it has following options:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 7799 1 0 17:25:38 ? 0:00 /usr/dt/bin/dtlogin -daemon -udpPort 0<br /> <br /> which means upd connection is not allowed. Looking into options will see following:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> dtlogin/args astring \ -udpPort\ 0<br /> <br /> To change that use following command:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot;\&quot;<br /> <br /> Now that option is gone:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> clon00:/etc&gt;<br /> <br /> To place that option back type following:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot; -udpPort 0\&quot;<br /> <br /> Restart dtlogin server:<br /> <br /> /etc/init.d/dtlogin stop<br /> /etc/init.d/dtlogin start<br /> <br /> Now it is running without upd restriction:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 11503 1 0 17:30:46 ? 0:00 /usr/dt/bin/dtlogin -daemon<br /> <br /> <br /> In addition to that, to make fonts loading process work enable xfs service. Normally it will be enabled on the machines with monitors, but on servers like clon00 and clon10 it will be disabled by default:<br /> <br /> clon00:/etc&gt; svcs -a | grep xfs<br /> disabled Jan_04 svc:/application/x11/xfs:default<br /> clon00:/etc&gt;<br /> <br /> so enable it:<br /> <br /> clon00:/etc&gt; svcadm enable svc:/application/x11/xfs<br /> clon00:/etc&gt; svcs | grep xfs<br /> online 12:55:53 svc:/application/x11/xfs:default<br /> clon00:/etc&gt; <br /> <br /> <br /> <br /> <br /> <br /> Some useful information can be found in following paper:<br /> <br /> Some reports indicate that 3.x builds do not work. The error that is reported is<br /> FATAL ERROR<br /> The device that contains the configuration file (config.xml) could not be found. m0n0wall cannot continue booting.<br /> I do not yet know of a solution. This tutorial should be construed to apply only to the 2.x builds in the meantime. Please email me if you get 3.x working on an EON.<br /> <br /> Here's how to install the latest build of the excellent m0n0wall firewall on a Neoware EON 4000 thin client. These machines make excellent firewalls for home users and small businesses because they are cheap, compact, sturdy, and powerful enough to run a several megabit connection. The hardware is available in a variety of configurations, with CPUs roughly equivalent to a 150-200Mhz Pentium. Before embarking on this little journey, you should be aware of a few caveats:<br /> <br /> * Some Neoware boxes come with a 32-pin Disk-on-Chip module in a socket on the motherboard. m0n0wall does not ship with the required driver to run this module. Therefore, on these systems you will need a hard drive, compact flash to IDE adapter, or similar device to boot from. You may also be able to netboot your firewall (this is supported on the built-in network device), though I do not cover that in this tutorial.<br /> * The motherboard accepts both PC133 DIMMs or SO-DIMMs. It will use both at the same time. However, when using a DIMM, be sure it is less than 1.1&quot; (28mm) tall, or you will not be able to install a second network card.<br /> * There are many different revisions of the NeoLinux operating system and not all include the necessary software to complete this tutorial.<br /> * You may need to purchase several EON 4000s to get suitable software and hardware.<br /> * These instructions were based on NeoLinux 2.4-100802, with kernel 2.2.20. Your particular configuration may vary slightly.<br /> <br /> With those potential issues in mind, follow along!<br /> <br /> There are three main steps to be completed to get m0n0wall running on your EON. First, you will need to get single-user access to the NeoLinux installation. Next, you need to enable networking and fetch and install m0n0wall. Third, you need to configure it to fit your requirements. I will address the first two of these, as adequate resources exist to help with the latter.<br /> <br /> To begin, you will need:<br /> <br /> * One or more Neoware EONs with disk-on-chip modules that plug into the IDE header<br /> * Access to the internet from your EON (or to a web server on a LAN)<br /> * A supported PCI network card. Common Intel or 3Com cards work fine.<br /> * At least 64MB of suitable memory. Some EONs ship with SO-DIMMs, others with DIMMs. These should be short enough to accomodate a PCI network card.<br /> * See the m0n0wall supported hardware page for more information.<br /> <br /> Step ONE: Get single-user access to the NeoLinux distribution.<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt may vary, but pressing tab should display either 'Software' or 'Eon_Software'.<br /> * Enter, as appropriate, either<br /> Software -s ramdisk=12000<br /> or<br /> Eon_Software -s ramdisk=12000<br /> and press enter.<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt.<br /> <br /> Step TWO: Fetch and install m0n0wall.<br /> <br /> * Check that your installation has the necessary software:<br /> bash# ls /usr/bin/wget<br /> . If NeoLinux reports that it is not found, you will have to try a different EON. Keep this hardware however: a single working EON can program m0n0wall onto several disk-on-chip modules, even those without the proper software. More on this later.<br /> * Plug the EON into a network which provides DHCP information and enable the ethernet connection:<br /> bash# cp /etc/sysconfig/network-scripts/ifcfg-eth0.default /etc/sysconfig/network-scripts/ifcfg-eth0<br /> bash# ifup eth0<br /> * Create a ramdisk on which to place temporary files during the installation:<br /> bash# mkfs.ext2 /dev/ram0<br /> bash# mount /dev/ram0 /mnt/usbcdrom<br /> bash# cd /mnt/usbcdrom<br /> bash# /usr/bin/wget http://hostname/path/to/m0n0wall<br /> bash# cp /bin/gunzip .<br /> bash# cp /bin/dd .<br /> * Now you're ready. You have created a ramdisk with the two utilities you will need to rewrite IDE disk-on-chip modules with m0n0wall. At this point, if you have modules containing copies of NeoLinux without wget, you should try using them first. That way if something goes wrong you can repeat these steps later. With the machine running, remove the IDE DOC that you booted from and replace it with the one you want to reprogram.<br /> * Then,<br /> gunzip -c m0n0wall-file-name.img | dd of=/dev/hda bs=16k<br /> Ignore the warning about trailing garbage.<br /> <br /> That's it! At this point you can remove the DOC and replace it with another one and repeat the reprogramming step, as many times as needed.<br /> <br /> When you next boot the machine, it should load m0n0wall exactly as it would on any other x86-compatible system. Jump right in with the m0n0wall quick-start guide for PC platforms. Chapter 3: Initial Configuration is probably where you will want to start. Good luck!<br /> <br /> Version 0.3 | Content date: 05 July 2008 | Page last generated: 2009-01-18 13:11 CST</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=Clasxt&diff=5317 2011-05-16T15:38:56Z

<p>129.57.167.199: </p> <hr /> <div>'''Clasxt's''' are mac mini's running MAC OS X.<br /> <br /> '''Initial installation'''<br /> <br /> * connect monitor, ethernet, keyboard and mouse and power up; sometimes it will not recognize keyboard or/and mouse, in that case just unplug mouse/keyboard and plug them back; follow instructions to identify keyboard<br /> <br /> * in '''System preferences/Network''': turn off '''AirPort'''; configure '''Ethernet''' as Manually and type IP address (ex. 129.56.167.xxx), mask (ex. 255.255.255.0), router (ex. 129.57.167.99), DNS server (ex. 129.57.167.5, 129.57.167.14) and search domain (ex. jlab.org)<br /> <br /> * in '''System preferences/Accounts''' change Admin's user password to the our clon root password; create new user '''clasrun''' with usual clasrun's pass, keep '''Automatic login''' is '''ON'''; click on '''Login Options''' and choose '''Automatic Login''' as '''clasrun'''<br /> <br /> * in '''System preferences/Energy Saver''' move '''Computer Sleep''' to '''Never''' to prevent user's forced logging off, and click on '''Start up automatically after a power failure'''<br /> <br /> * insert '''Mac OS X Install DVD''' and install '''Xcode''' and, optionally, '''Optional Installs'''<br /> <br /> * insert '''Applications Install DVD''' and click on '''Install Bundled Software''', then follow instructions<br /> <br /> * run '''Software Update'''<br /> <br /> <br /> <br /> '''OBSOLETE'''<br /> <br /> '''Clasxt''' machines are diskless 'thin clients' from neoware, running newlinux. We have 5 those machines still in use:<br /> <br /> * clasxt23<br /> <br /> * clasxt33<br /> <br /> * clasxt35<br /> <br /> * clasxt37<br /> <br /> * clasxt39<br /> <br /> * clasxt40<br /> <br /> To reboot in single user mode do following:<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt should display 'Software'<br /> * Enter ''Software -s ramdisk=12000'' and press enter<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt<br /> <br /> <br /> <br /> '''IMPORTANT:'''<br /> <br /> On clon machines where clasxt's suppose to login, XDM server must be running. On Solaris 10 XDM server is running as part of ''dtlogin''. By default it has following options:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 7799 1 0 17:25:38 ? 0:00 /usr/dt/bin/dtlogin -daemon -udpPort 0<br /> <br /> which means upd connection is not allowed. Looking into options will see following:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> dtlogin/args astring \ -udpPort\ 0<br /> <br /> To change that use following command:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot;\&quot;<br /> <br /> Now that option is gone:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> clon00:/etc&gt;<br /> <br /> To place that option back type following:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot; -udpPort 0\&quot;<br /> <br /> Restart dtlogin server:<br /> <br /> /etc/init.d/dtlogin stop<br /> /etc/init.d/dtlogin start<br /> <br /> Now it is running without upd restriction:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 11503 1 0 17:30:46 ? 0:00 /usr/dt/bin/dtlogin -daemon<br /> <br /> <br /> In addition to that, to make fonts loading process work enable xfs service. Normally it will be enabled on the machines with monitors, but on servers like clon00 and clon10 it will be disabled by default:<br /> <br /> clon00:/etc&gt; svcs -a | grep xfs<br /> disabled Jan_04 svc:/application/x11/xfs:default<br /> clon00:/etc&gt;<br /> <br /> so enable it:<br /> <br /> clon00:/etc&gt; svcadm enable svc:/application/x11/xfs<br /> clon00:/etc&gt; svcs | grep xfs<br /> online 12:55:53 svc:/application/x11/xfs:default<br /> clon00:/etc&gt; <br /> <br /> <br /> <br /> <br /> <br /> Some useful information can be found in following paper:<br /> <br /> Some reports indicate that 3.x builds do not work. The error that is reported is<br /> FATAL ERROR<br /> The device that contains the configuration file (config.xml) could not be found. m0n0wall cannot continue booting.<br /> I do not yet know of a solution. This tutorial should be construed to apply only to the 2.x builds in the meantime. Please email me if you get 3.x working on an EON.<br /> <br /> Here's how to install the latest build of the excellent m0n0wall firewall on a Neoware EON 4000 thin client. These machines make excellent firewalls for home users and small businesses because they are cheap, compact, sturdy, and powerful enough to run a several megabit connection. The hardware is available in a variety of configurations, with CPUs roughly equivalent to a 150-200Mhz Pentium. Before embarking on this little journey, you should be aware of a few caveats:<br /> <br /> * Some Neoware boxes come with a 32-pin Disk-on-Chip module in a socket on the motherboard. m0n0wall does not ship with the required driver to run this module. Therefore, on these systems you will need a hard drive, compact flash to IDE adapter, or similar device to boot from. You may also be able to netboot your firewall (this is supported on the built-in network device), though I do not cover that in this tutorial.<br /> * The motherboard accepts both PC133 DIMMs or SO-DIMMs. It will use both at the same time. However, when using a DIMM, be sure it is less than 1.1&quot; (28mm) tall, or you will not be able to install a second network card.<br /> * There are many different revisions of the NeoLinux operating system and not all include the necessary software to complete this tutorial.<br /> * You may need to purchase several EON 4000s to get suitable software and hardware.<br /> * These instructions were based on NeoLinux 2.4-100802, with kernel 2.2.20. Your particular configuration may vary slightly.<br /> <br /> With those potential issues in mind, follow along!<br /> <br /> There are three main steps to be completed to get m0n0wall running on your EON. First, you will need to get single-user access to the NeoLinux installation. Next, you need to enable networking and fetch and install m0n0wall. Third, you need to configure it to fit your requirements. I will address the first two of these, as adequate resources exist to help with the latter.<br /> <br /> To begin, you will need:<br /> <br /> * One or more Neoware EONs with disk-on-chip modules that plug into the IDE header<br /> * Access to the internet from your EON (or to a web server on a LAN)<br /> * A supported PCI network card. Common Intel or 3Com cards work fine.<br /> * At least 64MB of suitable memory. Some EONs ship with SO-DIMMs, others with DIMMs. These should be short enough to accomodate a PCI network card.<br /> * See the m0n0wall supported hardware page for more information.<br /> <br /> Step ONE: Get single-user access to the NeoLinux distribution.<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt may vary, but pressing tab should display either 'Software' or 'Eon_Software'.<br /> * Enter, as appropriate, either<br /> Software -s ramdisk=12000<br /> or<br /> Eon_Software -s ramdisk=12000<br /> and press enter.<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt.<br /> <br /> Step TWO: Fetch and install m0n0wall.<br /> <br /> * Check that your installation has the necessary software:<br /> bash# ls /usr/bin/wget<br /> . If NeoLinux reports that it is not found, you will have to try a different EON. Keep this hardware however: a single working EON can program m0n0wall onto several disk-on-chip modules, even those without the proper software. More on this later.<br /> * Plug the EON into a network which provides DHCP information and enable the ethernet connection:<br /> bash# cp /etc/sysconfig/network-scripts/ifcfg-eth0.default /etc/sysconfig/network-scripts/ifcfg-eth0<br /> bash# ifup eth0<br /> * Create a ramdisk on which to place temporary files during the installation:<br /> bash# mkfs.ext2 /dev/ram0<br /> bash# mount /dev/ram0 /mnt/usbcdrom<br /> bash# cd /mnt/usbcdrom<br /> bash# /usr/bin/wget http://hostname/path/to/m0n0wall<br /> bash# cp /bin/gunzip .<br /> bash# cp /bin/dd .<br /> * Now you're ready. You have created a ramdisk with the two utilities you will need to rewrite IDE disk-on-chip modules with m0n0wall. At this point, if you have modules containing copies of NeoLinux without wget, you should try using them first. That way if something goes wrong you can repeat these steps later. With the machine running, remove the IDE DOC that you booted from and replace it with the one you want to reprogram.<br /> * Then,<br /> gunzip -c m0n0wall-file-name.img | dd of=/dev/hda bs=16k<br /> Ignore the warning about trailing garbage.<br /> <br /> That's it! At this point you can remove the DOC and replace it with another one and repeat the reprogramming step, as many times as needed.<br /> <br /> When you next boot the machine, it should load m0n0wall exactly as it would on any other x86-compatible system. Jump right in with the m0n0wall quick-start guide for PC platforms. Chapter 3: Initial Configuration is probably where you will want to start. Good luck!<br /> <br /> Version 0.3 | Content date: 05 July 2008 | Page last generated: 2009-01-18 13:11 CST</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=Clasxt&diff=5316 2011-05-16T15:29:17Z

<p>129.57.167.199: </p> <hr /> <div>'''Clasxt's''' are mac mini's running MAC OS X.<br /> <br /> '''Initial installation'''<br /> <br /> * connect monitor, ethernet, keyboard and mouse and power up; sometimes it will not recognize keyboard or/and mouse, in that case just unplug mouse/keyboard and plug them back; follow instructions to identify keyboard<br /> <br /> * in '''System preferences/Network''': turn off '''AirPort'''; configure '''Ethernet''' as Manually and type IP address (ex. 129.56.167.xxx), mask (ex. 255.255.255.0), router (ex. 129.57.167.99), DNS server (ex. 129.57.167.5, 129.57.167.14) and search domain (ex. jlab.org)<br /> <br /> * in '''System preferences/Accounts''' change Admin's user password to the our clon root password; create new user '''clasrun''' with usual clasrun's pass, keep '''Automatic login''' is '''ON'''; click on '''Login Options''' and choose '''Automatic Login''' as '''clasrun'''<br /> <br /> * in '''System preferences/Energy Saver''' move '''Computer Sleep''' to '''Never''' to prevent user's forced logging off, and click on '''Start up automatically after a power failure'''<br /> <br /> * insert '''Mac OS X Install DVD''' and install '''Xcode'''<br /> <br /> * insert '''Applications Install DVD''' and click on '''Install Bundled Software''', then follow instructions<br /> <br /> * run '''Software Update'''<br /> <br /> <br /> <br /> '''OBSOLETE'''<br /> <br /> '''Clasxt''' machines are diskless 'thin clients' from neoware, running newlinux. We have 5 those machines still in use:<br /> <br /> * clasxt23<br /> <br /> * clasxt33<br /> <br /> * clasxt35<br /> <br /> * clasxt37<br /> <br /> * clasxt39<br /> <br /> * clasxt40<br /> <br /> To reboot in single user mode do following:<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt should display 'Software'<br /> * Enter ''Software -s ramdisk=12000'' and press enter<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt<br /> <br /> <br /> <br /> '''IMPORTANT:'''<br /> <br /> On clon machines where clasxt's suppose to login, XDM server must be running. On Solaris 10 XDM server is running as part of ''dtlogin''. By default it has following options:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 7799 1 0 17:25:38 ? 0:00 /usr/dt/bin/dtlogin -daemon -udpPort 0<br /> <br /> which means upd connection is not allowed. Looking into options will see following:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> dtlogin/args astring \ -udpPort\ 0<br /> <br /> To change that use following command:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot;\&quot;<br /> <br /> Now that option is gone:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> clon00:/etc&gt;<br /> <br /> To place that option back type following:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot; -udpPort 0\&quot;<br /> <br /> Restart dtlogin server:<br /> <br /> /etc/init.d/dtlogin stop<br /> /etc/init.d/dtlogin start<br /> <br /> Now it is running without upd restriction:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 11503 1 0 17:30:46 ? 0:00 /usr/dt/bin/dtlogin -daemon<br /> <br /> <br /> In addition to that, to make fonts loading process work enable xfs service. Normally it will be enabled on the machines with monitors, but on servers like clon00 and clon10 it will be disabled by default:<br /> <br /> clon00:/etc&gt; svcs -a | grep xfs<br /> disabled Jan_04 svc:/application/x11/xfs:default<br /> clon00:/etc&gt;<br /> <br /> so enable it:<br /> <br /> clon00:/etc&gt; svcadm enable svc:/application/x11/xfs<br /> clon00:/etc&gt; svcs | grep xfs<br /> online 12:55:53 svc:/application/x11/xfs:default<br /> clon00:/etc&gt; <br /> <br /> <br /> <br /> <br /> <br /> Some useful information can be found in following paper:<br /> <br /> Some reports indicate that 3.x builds do not work. The error that is reported is<br /> FATAL ERROR<br /> The device that contains the configuration file (config.xml) could not be found. m0n0wall cannot continue booting.<br /> I do not yet know of a solution. This tutorial should be construed to apply only to the 2.x builds in the meantime. Please email me if you get 3.x working on an EON.<br /> <br /> Here's how to install the latest build of the excellent m0n0wall firewall on a Neoware EON 4000 thin client. These machines make excellent firewalls for home users and small businesses because they are cheap, compact, sturdy, and powerful enough to run a several megabit connection. The hardware is available in a variety of configurations, with CPUs roughly equivalent to a 150-200Mhz Pentium. Before embarking on this little journey, you should be aware of a few caveats:<br /> <br /> * Some Neoware boxes come with a 32-pin Disk-on-Chip module in a socket on the motherboard. m0n0wall does not ship with the required driver to run this module. Therefore, on these systems you will need a hard drive, compact flash to IDE adapter, or similar device to boot from. You may also be able to netboot your firewall (this is supported on the built-in network device), though I do not cover that in this tutorial.<br /> * The motherboard accepts both PC133 DIMMs or SO-DIMMs. It will use both at the same time. However, when using a DIMM, be sure it is less than 1.1&quot; (28mm) tall, or you will not be able to install a second network card.<br /> * There are many different revisions of the NeoLinux operating system and not all include the necessary software to complete this tutorial.<br /> * You may need to purchase several EON 4000s to get suitable software and hardware.<br /> * These instructions were based on NeoLinux 2.4-100802, with kernel 2.2.20. Your particular configuration may vary slightly.<br /> <br /> With those potential issues in mind, follow along!<br /> <br /> There are three main steps to be completed to get m0n0wall running on your EON. First, you will need to get single-user access to the NeoLinux installation. Next, you need to enable networking and fetch and install m0n0wall. Third, you need to configure it to fit your requirements. I will address the first two of these, as adequate resources exist to help with the latter.<br /> <br /> To begin, you will need:<br /> <br /> * One or more Neoware EONs with disk-on-chip modules that plug into the IDE header<br /> * Access to the internet from your EON (or to a web server on a LAN)<br /> * A supported PCI network card. Common Intel or 3Com cards work fine.<br /> * At least 64MB of suitable memory. Some EONs ship with SO-DIMMs, others with DIMMs. These should be short enough to accomodate a PCI network card.<br /> * See the m0n0wall supported hardware page for more information.<br /> <br /> Step ONE: Get single-user access to the NeoLinux distribution.<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt may vary, but pressing tab should display either 'Software' or 'Eon_Software'.<br /> * Enter, as appropriate, either<br /> Software -s ramdisk=12000<br /> or<br /> Eon_Software -s ramdisk=12000<br /> and press enter.<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt.<br /> <br /> Step TWO: Fetch and install m0n0wall.<br /> <br /> * Check that your installation has the necessary software:<br /> bash# ls /usr/bin/wget<br /> . If NeoLinux reports that it is not found, you will have to try a different EON. Keep this hardware however: a single working EON can program m0n0wall onto several disk-on-chip modules, even those without the proper software. More on this later.<br /> * Plug the EON into a network which provides DHCP information and enable the ethernet connection:<br /> bash# cp /etc/sysconfig/network-scripts/ifcfg-eth0.default /etc/sysconfig/network-scripts/ifcfg-eth0<br /> bash# ifup eth0<br /> * Create a ramdisk on which to place temporary files during the installation:<br /> bash# mkfs.ext2 /dev/ram0<br /> bash# mount /dev/ram0 /mnt/usbcdrom<br /> bash# cd /mnt/usbcdrom<br /> bash# /usr/bin/wget http://hostname/path/to/m0n0wall<br /> bash# cp /bin/gunzip .<br /> bash# cp /bin/dd .<br /> * Now you're ready. You have created a ramdisk with the two utilities you will need to rewrite IDE disk-on-chip modules with m0n0wall. At this point, if you have modules containing copies of NeoLinux without wget, you should try using them first. That way if something goes wrong you can repeat these steps later. With the machine running, remove the IDE DOC that you booted from and replace it with the one you want to reprogram.<br /> * Then,<br /> gunzip -c m0n0wall-file-name.img | dd of=/dev/hda bs=16k<br /> Ignore the warning about trailing garbage.<br /> <br /> That's it! At this point you can remove the DOC and replace it with another one and repeat the reprogramming step, as many times as needed.<br /> <br /> When you next boot the machine, it should load m0n0wall exactly as it would on any other x86-compatible system. Jump right in with the m0n0wall quick-start guide for PC platforms. Chapter 3: Initial Configuration is probably where you will want to start. Good luck!<br /> <br /> Version 0.3 | Content date: 05 July 2008 | Page last generated: 2009-01-18 13:11 CST</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=Clasxt&diff=5315 2011-05-16T15:28:43Z

<p>129.57.167.199: </p> <hr /> <div>'''Clasxt's''' are mac mini's running MAC OS X.<br /> <br /> '''Initial installation'''<br /> <br /> * connect monitor, ethernet, keyboard and mouse and power up; sometimes it will not recognize keyboard or/and mouse, in that case just unplug mouse/keyboard and plug them back; follow instructions to identify keyboard<br /> <br /> * in '''System preferences/Network''': turn off '''AirPort'''; configure '''Ethernet''' as Manually and type IP address (ex. 129.56.167.xxx), mask (ex. 255.255.255.0), router (ex. 129.57.167.99), DNS server (ex. 129.57.167.5, 129.57.167.14) and search domain (ex. jlab.org)<br /> <br /> * in '''System preferences/Accounts''' change Admin's user password to the our clon root password; create new user '''clasrun''' with usual clasrun's pass, keep '''Automatic login''' is '''ON'''; click on '''Login Options''' and choose '''Automatic Login''' as '''clasrun'''<br /> <br /> * in '''System preferences/Energy Saver''' move '''Computer Sleep''' to '''Never''' to prevent user's forced logging off, and click on '''Start up automatically after a power failure'''<br /> <br /> * insert '''Mac OS X Install DVD''' and install '''Xcode'''<br /> <br /> * insert '''Application DVD''' and click on '''Install Bundled Software''', then follow instructions<br /> <br /> * run '''Software Update'''<br /> <br /> <br /> <br /> '''OBSOLETE'''<br /> <br /> '''Clasxt''' machines are diskless 'thin clients' from neoware, running newlinux. We have 5 those machines still in use:<br /> <br /> * clasxt23<br /> <br /> * clasxt33<br /> <br /> * clasxt35<br /> <br /> * clasxt37<br /> <br /> * clasxt39<br /> <br /> * clasxt40<br /> <br /> To reboot in single user mode do following:<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt should display 'Software'<br /> * Enter ''Software -s ramdisk=12000'' and press enter<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt<br /> <br /> <br /> <br /> '''IMPORTANT:'''<br /> <br /> On clon machines where clasxt's suppose to login, XDM server must be running. On Solaris 10 XDM server is running as part of ''dtlogin''. By default it has following options:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 7799 1 0 17:25:38 ? 0:00 /usr/dt/bin/dtlogin -daemon -udpPort 0<br /> <br /> which means upd connection is not allowed. Looking into options will see following:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> dtlogin/args astring \ -udpPort\ 0<br /> <br /> To change that use following command:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot;\&quot;<br /> <br /> Now that option is gone:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> clon00:/etc&gt;<br /> <br /> To place that option back type following:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot; -udpPort 0\&quot;<br /> <br /> Restart dtlogin server:<br /> <br /> /etc/init.d/dtlogin stop<br /> /etc/init.d/dtlogin start<br /> <br /> Now it is running without upd restriction:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 11503 1 0 17:30:46 ? 0:00 /usr/dt/bin/dtlogin -daemon<br /> <br /> <br /> In addition to that, to make fonts loading process work enable xfs service. Normally it will be enabled on the machines with monitors, but on servers like clon00 and clon10 it will be disabled by default:<br /> <br /> clon00:/etc&gt; svcs -a | grep xfs<br /> disabled Jan_04 svc:/application/x11/xfs:default<br /> clon00:/etc&gt;<br /> <br /> so enable it:<br /> <br /> clon00:/etc&gt; svcadm enable svc:/application/x11/xfs<br /> clon00:/etc&gt; svcs | grep xfs<br /> online 12:55:53 svc:/application/x11/xfs:default<br /> clon00:/etc&gt; <br /> <br /> <br /> <br /> <br /> <br /> Some useful information can be found in following paper:<br /> <br /> Some reports indicate that 3.x builds do not work. The error that is reported is<br /> FATAL ERROR<br /> The device that contains the configuration file (config.xml) could not be found. m0n0wall cannot continue booting.<br /> I do not yet know of a solution. This tutorial should be construed to apply only to the 2.x builds in the meantime. Please email me if you get 3.x working on an EON.<br /> <br /> Here's how to install the latest build of the excellent m0n0wall firewall on a Neoware EON 4000 thin client. These machines make excellent firewalls for home users and small businesses because they are cheap, compact, sturdy, and powerful enough to run a several megabit connection. The hardware is available in a variety of configurations, with CPUs roughly equivalent to a 150-200Mhz Pentium. Before embarking on this little journey, you should be aware of a few caveats:<br /> <br /> * Some Neoware boxes come with a 32-pin Disk-on-Chip module in a socket on the motherboard. m0n0wall does not ship with the required driver to run this module. Therefore, on these systems you will need a hard drive, compact flash to IDE adapter, or similar device to boot from. You may also be able to netboot your firewall (this is supported on the built-in network device), though I do not cover that in this tutorial.<br /> * The motherboard accepts both PC133 DIMMs or SO-DIMMs. It will use both at the same time. However, when using a DIMM, be sure it is less than 1.1&quot; (28mm) tall, or you will not be able to install a second network card.<br /> * There are many different revisions of the NeoLinux operating system and not all include the necessary software to complete this tutorial.<br /> * You may need to purchase several EON 4000s to get suitable software and hardware.<br /> * These instructions were based on NeoLinux 2.4-100802, with kernel 2.2.20. Your particular configuration may vary slightly.<br /> <br /> With those potential issues in mind, follow along!<br /> <br /> There are three main steps to be completed to get m0n0wall running on your EON. First, you will need to get single-user access to the NeoLinux installation. Next, you need to enable networking and fetch and install m0n0wall. Third, you need to configure it to fit your requirements. I will address the first two of these, as adequate resources exist to help with the latter.<br /> <br /> To begin, you will need:<br /> <br /> * One or more Neoware EONs with disk-on-chip modules that plug into the IDE header<br /> * Access to the internet from your EON (or to a web server on a LAN)<br /> * A supported PCI network card. Common Intel or 3Com cards work fine.<br /> * At least 64MB of suitable memory. Some EONs ship with SO-DIMMs, others with DIMMs. These should be short enough to accomodate a PCI network card.<br /> * See the m0n0wall supported hardware page for more information.<br /> <br /> Step ONE: Get single-user access to the NeoLinux distribution.<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt may vary, but pressing tab should display either 'Software' or 'Eon_Software'.<br /> * Enter, as appropriate, either<br /> Software -s ramdisk=12000<br /> or<br /> Eon_Software -s ramdisk=12000<br /> and press enter.<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt.<br /> <br /> Step TWO: Fetch and install m0n0wall.<br /> <br /> * Check that your installation has the necessary software:<br /> bash# ls /usr/bin/wget<br /> . If NeoLinux reports that it is not found, you will have to try a different EON. Keep this hardware however: a single working EON can program m0n0wall onto several disk-on-chip modules, even those without the proper software. More on this later.<br /> * Plug the EON into a network which provides DHCP information and enable the ethernet connection:<br /> bash# cp /etc/sysconfig/network-scripts/ifcfg-eth0.default /etc/sysconfig/network-scripts/ifcfg-eth0<br /> bash# ifup eth0<br /> * Create a ramdisk on which to place temporary files during the installation:<br /> bash# mkfs.ext2 /dev/ram0<br /> bash# mount /dev/ram0 /mnt/usbcdrom<br /> bash# cd /mnt/usbcdrom<br /> bash# /usr/bin/wget http://hostname/path/to/m0n0wall<br /> bash# cp /bin/gunzip .<br /> bash# cp /bin/dd .<br /> * Now you're ready. You have created a ramdisk with the two utilities you will need to rewrite IDE disk-on-chip modules with m0n0wall. At this point, if you have modules containing copies of NeoLinux without wget, you should try using them first. That way if something goes wrong you can repeat these steps later. With the machine running, remove the IDE DOC that you booted from and replace it with the one you want to reprogram.<br /> * Then,<br /> gunzip -c m0n0wall-file-name.img | dd of=/dev/hda bs=16k<br /> Ignore the warning about trailing garbage.<br /> <br /> That's it! At this point you can remove the DOC and replace it with another one and repeat the reprogramming step, as many times as needed.<br /> <br /> When you next boot the machine, it should load m0n0wall exactly as it would on any other x86-compatible system. Jump right in with the m0n0wall quick-start guide for PC platforms. Chapter 3: Initial Configuration is probably where you will want to start. Good luck!<br /> <br /> Version 0.3 | Content date: 05 July 2008 | Page last generated: 2009-01-18 13:11 CST</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=Clasxt&diff=5314 2011-05-16T15:15:23Z

<p>129.57.167.199: </p> <hr /> <div>'''Clasxt's''' are mac mini's running MAC OS X.<br /> <br /> '''Initial installation'''<br /> <br /> * connect monitor, ethernet, keyboard and mouse and power up; sometimes it will not recognize keyboard or/and mouse, in that case just unplug mouse/keyboard and plug them back; follow instructions to identify keyboard<br /> <br /> * in '''System preferences/Network''': turn off '''AirPort'''; configure '''Ethernet''' as Manually and type IP address (ex. 129.56.167.xxx), mask (ex. 255.255.255.0), router (ex. 129.57.167.99), DNS server (ex. 129.57.167.5, 129.57.167.14) and search domain (ex. jlab.org)<br /> <br /> * in '''System preferences/Accounts''' change Admin's user password to the our clon root password; create new user '''clasrun''' with usual clasrun's pass, keep '''Automatic login''' is '''ON'''; click on '''Login Options''' and choose '''Automatic Login''' as '''clasrun'''<br /> <br /> * in '''System preferences/Energy Saver''' move '''Computer Sleep''' to '''Never''' to prevent user's forced logging off, and click on '''Start up automatically after a power failure'''<br /> <br /> * insert '''Application DVD''' and click on '''Install Bundled Software''', then follow instructions<br /> <br /> * run '''Software Update'''<br /> <br /> <br /> <br /> '''OBSOLETE'''<br /> <br /> '''Clasxt''' machines are diskless 'thin clients' from neoware, running newlinux. We have 5 those machines still in use:<br /> <br /> * clasxt23<br /> <br /> * clasxt33<br /> <br /> * clasxt35<br /> <br /> * clasxt37<br /> <br /> * clasxt39<br /> <br /> * clasxt40<br /> <br /> To reboot in single user mode do following:<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt should display 'Software'<br /> * Enter ''Software -s ramdisk=12000'' and press enter<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt<br /> <br /> <br /> <br /> '''IMPORTANT:'''<br /> <br /> On clon machines where clasxt's suppose to login, XDM server must be running. On Solaris 10 XDM server is running as part of ''dtlogin''. By default it has following options:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 7799 1 0 17:25:38 ? 0:00 /usr/dt/bin/dtlogin -daemon -udpPort 0<br /> <br /> which means upd connection is not allowed. Looking into options will see following:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> dtlogin/args astring \ -udpPort\ 0<br /> <br /> To change that use following command:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot;\&quot;<br /> <br /> Now that option is gone:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> clon00:/etc&gt;<br /> <br /> To place that option back type following:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot; -udpPort 0\&quot;<br /> <br /> Restart dtlogin server:<br /> <br /> /etc/init.d/dtlogin stop<br /> /etc/init.d/dtlogin start<br /> <br /> Now it is running without upd restriction:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 11503 1 0 17:30:46 ? 0:00 /usr/dt/bin/dtlogin -daemon<br /> <br /> <br /> In addition to that, to make fonts loading process work enable xfs service. Normally it will be enabled on the machines with monitors, but on servers like clon00 and clon10 it will be disabled by default:<br /> <br /> clon00:/etc&gt; svcs -a | grep xfs<br /> disabled Jan_04 svc:/application/x11/xfs:default<br /> clon00:/etc&gt;<br /> <br /> so enable it:<br /> <br /> clon00:/etc&gt; svcadm enable svc:/application/x11/xfs<br /> clon00:/etc&gt; svcs | grep xfs<br /> online 12:55:53 svc:/application/x11/xfs:default<br /> clon00:/etc&gt; <br /> <br /> <br /> <br /> <br /> <br /> Some useful information can be found in following paper:<br /> <br /> Some reports indicate that 3.x builds do not work. The error that is reported is<br /> FATAL ERROR<br /> The device that contains the configuration file (config.xml) could not be found. m0n0wall cannot continue booting.<br /> I do not yet know of a solution. This tutorial should be construed to apply only to the 2.x builds in the meantime. Please email me if you get 3.x working on an EON.<br /> <br /> Here's how to install the latest build of the excellent m0n0wall firewall on a Neoware EON 4000 thin client. These machines make excellent firewalls for home users and small businesses because they are cheap, compact, sturdy, and powerful enough to run a several megabit connection. The hardware is available in a variety of configurations, with CPUs roughly equivalent to a 150-200Mhz Pentium. Before embarking on this little journey, you should be aware of a few caveats:<br /> <br /> * Some Neoware boxes come with a 32-pin Disk-on-Chip module in a socket on the motherboard. m0n0wall does not ship with the required driver to run this module. Therefore, on these systems you will need a hard drive, compact flash to IDE adapter, or similar device to boot from. You may also be able to netboot your firewall (this is supported on the built-in network device), though I do not cover that in this tutorial.<br /> * The motherboard accepts both PC133 DIMMs or SO-DIMMs. It will use both at the same time. However, when using a DIMM, be sure it is less than 1.1&quot; (28mm) tall, or you will not be able to install a second network card.<br /> * There are many different revisions of the NeoLinux operating system and not all include the necessary software to complete this tutorial.<br /> * You may need to purchase several EON 4000s to get suitable software and hardware.<br /> * These instructions were based on NeoLinux 2.4-100802, with kernel 2.2.20. Your particular configuration may vary slightly.<br /> <br /> With those potential issues in mind, follow along!<br /> <br /> There are three main steps to be completed to get m0n0wall running on your EON. First, you will need to get single-user access to the NeoLinux installation. Next, you need to enable networking and fetch and install m0n0wall. Third, you need to configure it to fit your requirements. I will address the first two of these, as adequate resources exist to help with the latter.<br /> <br /> To begin, you will need:<br /> <br /> * One or more Neoware EONs with disk-on-chip modules that plug into the IDE header<br /> * Access to the internet from your EON (or to a web server on a LAN)<br /> * A supported PCI network card. Common Intel or 3Com cards work fine.<br /> * At least 64MB of suitable memory. Some EONs ship with SO-DIMMs, others with DIMMs. These should be short enough to accomodate a PCI network card.<br /> * See the m0n0wall supported hardware page for more information.<br /> <br /> Step ONE: Get single-user access to the NeoLinux distribution.<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt may vary, but pressing tab should display either 'Software' or 'Eon_Software'.<br /> * Enter, as appropriate, either<br /> Software -s ramdisk=12000<br /> or<br /> Eon_Software -s ramdisk=12000<br /> and press enter.<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt.<br /> <br /> Step TWO: Fetch and install m0n0wall.<br /> <br /> * Check that your installation has the necessary software:<br /> bash# ls /usr/bin/wget<br /> . If NeoLinux reports that it is not found, you will have to try a different EON. Keep this hardware however: a single working EON can program m0n0wall onto several disk-on-chip modules, even those without the proper software. More on this later.<br /> * Plug the EON into a network which provides DHCP information and enable the ethernet connection:<br /> bash# cp /etc/sysconfig/network-scripts/ifcfg-eth0.default /etc/sysconfig/network-scripts/ifcfg-eth0<br /> bash# ifup eth0<br /> * Create a ramdisk on which to place temporary files during the installation:<br /> bash# mkfs.ext2 /dev/ram0<br /> bash# mount /dev/ram0 /mnt/usbcdrom<br /> bash# cd /mnt/usbcdrom<br /> bash# /usr/bin/wget http://hostname/path/to/m0n0wall<br /> bash# cp /bin/gunzip .<br /> bash# cp /bin/dd .<br /> * Now you're ready. You have created a ramdisk with the two utilities you will need to rewrite IDE disk-on-chip modules with m0n0wall. At this point, if you have modules containing copies of NeoLinux without wget, you should try using them first. That way if something goes wrong you can repeat these steps later. With the machine running, remove the IDE DOC that you booted from and replace it with the one you want to reprogram.<br /> * Then,<br /> gunzip -c m0n0wall-file-name.img | dd of=/dev/hda bs=16k<br /> Ignore the warning about trailing garbage.<br /> <br /> That's it! At this point you can remove the DOC and replace it with another one and repeat the reprogramming step, as many times as needed.<br /> <br /> When you next boot the machine, it should load m0n0wall exactly as it would on any other x86-compatible system. Jump right in with the m0n0wall quick-start guide for PC platforms. Chapter 3: Initial Configuration is probably where you will want to start. Good luck!<br /> <br /> Version 0.3 | Content date: 05 July 2008 | Page last generated: 2009-01-18 13:11 CST</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=Clasxt&diff=5313 2011-05-16T15:14:10Z

<p>129.57.167.199: </p> <hr /> <div>'''Clasxt's''' are mac mini's running MAC OS X.<br /> <br /> '''Initial installation'''<br /> <br /> * connect monitor, ethernet, keyboard and mouse and power up; sometimes it will not recognize keyboard or/and mouse, in that case just unplug mouse/keyboard and plug them back; follow instructions to identify keyboard<br /> <br /> * in '''System preferences/Network''': turn off '''AirPort'''; configure '''Ethernet''' as Manually and type IP address (ex. 129.56.167.xxx), mask (ex. 255.255.255.0), router (ex. 129.57.167.99), DNS server (ex. 129.57.167.5, 129.57.167.14) and search domain (ex. jlab.org)<br /> <br /> * in '''System preferences/Accounts''' change Admin's user password to the our clon root password; create new user '''clasrun''' with usual clasrun's pass, keep '''Automatic login''' is '''ON'''; click on '''Login Options''' and choose '''Automatic Login''' as '''clasrun'''<br /> <br /> * in '''System preferences/Energy Saver''' move '''Computer Sleep''' to '''Never''' to prevent user's forced logging off, and click on '''Start up automatically after a power failure'''<br /> <br /> * insert '''Application DVD''' and install '''Bundled Applications'''<br /> <br /> * run '''Software Update'''<br /> <br /> <br /> <br /> '''OBSOLETE'''<br /> <br /> '''Clasxt''' machines are diskless 'thin clients' from neoware, running newlinux. We have 5 those machines still in use:<br /> <br /> * clasxt23<br /> <br /> * clasxt33<br /> <br /> * clasxt35<br /> <br /> * clasxt37<br /> <br /> * clasxt39<br /> <br /> * clasxt40<br /> <br /> To reboot in single user mode do following:<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt should display 'Software'<br /> * Enter ''Software -s ramdisk=12000'' and press enter<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt<br /> <br /> <br /> <br /> '''IMPORTANT:'''<br /> <br /> On clon machines where clasxt's suppose to login, XDM server must be running. On Solaris 10 XDM server is running as part of ''dtlogin''. By default it has following options:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 7799 1 0 17:25:38 ? 0:00 /usr/dt/bin/dtlogin -daemon -udpPort 0<br /> <br /> which means upd connection is not allowed. Looking into options will see following:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> dtlogin/args astring \ -udpPort\ 0<br /> <br /> To change that use following command:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot;\&quot;<br /> <br /> Now that option is gone:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> clon00:/etc&gt;<br /> <br /> To place that option back type following:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot; -udpPort 0\&quot;<br /> <br /> Restart dtlogin server:<br /> <br /> /etc/init.d/dtlogin stop<br /> /etc/init.d/dtlogin start<br /> <br /> Now it is running without upd restriction:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 11503 1 0 17:30:46 ? 0:00 /usr/dt/bin/dtlogin -daemon<br /> <br /> <br /> In addition to that, to make fonts loading process work enable xfs service. Normally it will be enabled on the machines with monitors, but on servers like clon00 and clon10 it will be disabled by default:<br /> <br /> clon00:/etc&gt; svcs -a | grep xfs<br /> disabled Jan_04 svc:/application/x11/xfs:default<br /> clon00:/etc&gt;<br /> <br /> so enable it:<br /> <br /> clon00:/etc&gt; svcadm enable svc:/application/x11/xfs<br /> clon00:/etc&gt; svcs | grep xfs<br /> online 12:55:53 svc:/application/x11/xfs:default<br /> clon00:/etc&gt; <br /> <br /> <br /> <br /> <br /> <br /> Some useful information can be found in following paper:<br /> <br /> Some reports indicate that 3.x builds do not work. The error that is reported is<br /> FATAL ERROR<br /> The device that contains the configuration file (config.xml) could not be found. m0n0wall cannot continue booting.<br /> I do not yet know of a solution. This tutorial should be construed to apply only to the 2.x builds in the meantime. Please email me if you get 3.x working on an EON.<br /> <br /> Here's how to install the latest build of the excellent m0n0wall firewall on a Neoware EON 4000 thin client. These machines make excellent firewalls for home users and small businesses because they are cheap, compact, sturdy, and powerful enough to run a several megabit connection. The hardware is available in a variety of configurations, with CPUs roughly equivalent to a 150-200Mhz Pentium. Before embarking on this little journey, you should be aware of a few caveats:<br /> <br /> * Some Neoware boxes come with a 32-pin Disk-on-Chip module in a socket on the motherboard. m0n0wall does not ship with the required driver to run this module. Therefore, on these systems you will need a hard drive, compact flash to IDE adapter, or similar device to boot from. You may also be able to netboot your firewall (this is supported on the built-in network device), though I do not cover that in this tutorial.<br /> * The motherboard accepts both PC133 DIMMs or SO-DIMMs. It will use both at the same time. However, when using a DIMM, be sure it is less than 1.1&quot; (28mm) tall, or you will not be able to install a second network card.<br /> * There are many different revisions of the NeoLinux operating system and not all include the necessary software to complete this tutorial.<br /> * You may need to purchase several EON 4000s to get suitable software and hardware.<br /> * These instructions were based on NeoLinux 2.4-100802, with kernel 2.2.20. Your particular configuration may vary slightly.<br /> <br /> With those potential issues in mind, follow along!<br /> <br /> There are three main steps to be completed to get m0n0wall running on your EON. First, you will need to get single-user access to the NeoLinux installation. Next, you need to enable networking and fetch and install m0n0wall. Third, you need to configure it to fit your requirements. I will address the first two of these, as adequate resources exist to help with the latter.<br /> <br /> To begin, you will need:<br /> <br /> * One or more Neoware EONs with disk-on-chip modules that plug into the IDE header<br /> * Access to the internet from your EON (or to a web server on a LAN)<br /> * A supported PCI network card. Common Intel or 3Com cards work fine.<br /> * At least 64MB of suitable memory. Some EONs ship with SO-DIMMs, others with DIMMs. These should be short enough to accomodate a PCI network card.<br /> * See the m0n0wall supported hardware page for more information.<br /> <br /> Step ONE: Get single-user access to the NeoLinux distribution.<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt may vary, but pressing tab should display either 'Software' or 'Eon_Software'.<br /> * Enter, as appropriate, either<br /> Software -s ramdisk=12000<br /> or<br /> Eon_Software -s ramdisk=12000<br /> and press enter.<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt.<br /> <br /> Step TWO: Fetch and install m0n0wall.<br /> <br /> * Check that your installation has the necessary software:<br /> bash# ls /usr/bin/wget<br /> . If NeoLinux reports that it is not found, you will have to try a different EON. Keep this hardware however: a single working EON can program m0n0wall onto several disk-on-chip modules, even those without the proper software. More on this later.<br /> * Plug the EON into a network which provides DHCP information and enable the ethernet connection:<br /> bash# cp /etc/sysconfig/network-scripts/ifcfg-eth0.default /etc/sysconfig/network-scripts/ifcfg-eth0<br /> bash# ifup eth0<br /> * Create a ramdisk on which to place temporary files during the installation:<br /> bash# mkfs.ext2 /dev/ram0<br /> bash# mount /dev/ram0 /mnt/usbcdrom<br /> bash# cd /mnt/usbcdrom<br /> bash# /usr/bin/wget http://hostname/path/to/m0n0wall<br /> bash# cp /bin/gunzip .<br /> bash# cp /bin/dd .<br /> * Now you're ready. You have created a ramdisk with the two utilities you will need to rewrite IDE disk-on-chip modules with m0n0wall. At this point, if you have modules containing copies of NeoLinux without wget, you should try using them first. That way if something goes wrong you can repeat these steps later. With the machine running, remove the IDE DOC that you booted from and replace it with the one you want to reprogram.<br /> * Then,<br /> gunzip -c m0n0wall-file-name.img | dd of=/dev/hda bs=16k<br /> Ignore the warning about trailing garbage.<br /> <br /> That's it! At this point you can remove the DOC and replace it with another one and repeat the reprogramming step, as many times as needed.<br /> <br /> When you next boot the machine, it should load m0n0wall exactly as it would on any other x86-compatible system. Jump right in with the m0n0wall quick-start guide for PC platforms. Chapter 3: Initial Configuration is probably where you will want to start. Good luck!<br /> <br /> Version 0.3 | Content date: 05 July 2008 | Page last generated: 2009-01-18 13:11 CST</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=Clasxt&diff=5312 2011-05-16T15:13:32Z

<p>129.57.167.199: </p> <hr /> <div>'''Clasxt's''' are mac mini's running MAC OS X.<br /> <br /> '''Initial installation'''<br /> <br /> * connect monitor, ethernet, keyboard and mouse and power up; sometimes it will not recognize keyboard or/and mouse, in that case just unplug mouse/keyboard and plug them back; follow instructions to identify keyboard<br /> <br /> * in '''System preferences/Network''': turn off '''AirPort'''; configure '''Ethernet''' as Manually and type IP address (ex. 129.56.167.xxx), mask (ex. 255.255.255.0), router (ex. 129.57.167.99), DNS server (ex. 129.57.167.5, 129.57.167.14) and search domain (ex. jlab.org)<br /> <br /> * in '''System preferences/Accounts''' change Admin's user password to the our clon root password; create new user '''clasrun''' with usual clasrun's pass, keep '''Automatic login''' is '''ON'''; click on '''Login Options''' and choose '''Automatic Login''' as '''clasrun'''<br /> <br /> * in '''System preferences/Energy Saver''' move '''Computer Sleep''' to '''Never''' to prevent user's forced logging off, and click on '''Start up automatically after a power failure'''<br /> <br /> * insert '''Application DVD''' and install '''Bundled Applications'''<br /> <br /> '''OBSOLETE'''<br /> <br /> '''Clasxt''' machines are diskless 'thin clients' from neoware, running newlinux. We have 5 those machines still in use:<br /> <br /> * clasxt23<br /> <br /> * clasxt33<br /> <br /> * clasxt35<br /> <br /> * clasxt37<br /> <br /> * clasxt39<br /> <br /> * clasxt40<br /> <br /> To reboot in single user mode do following:<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt should display 'Software'<br /> * Enter ''Software -s ramdisk=12000'' and press enter<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt<br /> <br /> <br /> <br /> '''IMPORTANT:'''<br /> <br /> On clon machines where clasxt's suppose to login, XDM server must be running. On Solaris 10 XDM server is running as part of ''dtlogin''. By default it has following options:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 7799 1 0 17:25:38 ? 0:00 /usr/dt/bin/dtlogin -daemon -udpPort 0<br /> <br /> which means upd connection is not allowed. Looking into options will see following:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> dtlogin/args astring \ -udpPort\ 0<br /> <br /> To change that use following command:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot;\&quot;<br /> <br /> Now that option is gone:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> clon00:/etc&gt;<br /> <br /> To place that option back type following:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot; -udpPort 0\&quot;<br /> <br /> Restart dtlogin server:<br /> <br /> /etc/init.d/dtlogin stop<br /> /etc/init.d/dtlogin start<br /> <br /> Now it is running without upd restriction:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 11503 1 0 17:30:46 ? 0:00 /usr/dt/bin/dtlogin -daemon<br /> <br /> <br /> In addition to that, to make fonts loading process work enable xfs service. Normally it will be enabled on the machines with monitors, but on servers like clon00 and clon10 it will be disabled by default:<br /> <br /> clon00:/etc&gt; svcs -a | grep xfs<br /> disabled Jan_04 svc:/application/x11/xfs:default<br /> clon00:/etc&gt;<br /> <br /> so enable it:<br /> <br /> clon00:/etc&gt; svcadm enable svc:/application/x11/xfs<br /> clon00:/etc&gt; svcs | grep xfs<br /> online 12:55:53 svc:/application/x11/xfs:default<br /> clon00:/etc&gt; <br /> <br /> <br /> <br /> <br /> <br /> Some useful information can be found in following paper:<br /> <br /> Some reports indicate that 3.x builds do not work. The error that is reported is<br /> FATAL ERROR<br /> The device that contains the configuration file (config.xml) could not be found. m0n0wall cannot continue booting.<br /> I do not yet know of a solution. This tutorial should be construed to apply only to the 2.x builds in the meantime. Please email me if you get 3.x working on an EON.<br /> <br /> Here's how to install the latest build of the excellent m0n0wall firewall on a Neoware EON 4000 thin client. These machines make excellent firewalls for home users and small businesses because they are cheap, compact, sturdy, and powerful enough to run a several megabit connection. The hardware is available in a variety of configurations, with CPUs roughly equivalent to a 150-200Mhz Pentium. Before embarking on this little journey, you should be aware of a few caveats:<br /> <br /> * Some Neoware boxes come with a 32-pin Disk-on-Chip module in a socket on the motherboard. m0n0wall does not ship with the required driver to run this module. Therefore, on these systems you will need a hard drive, compact flash to IDE adapter, or similar device to boot from. You may also be able to netboot your firewall (this is supported on the built-in network device), though I do not cover that in this tutorial.<br /> * The motherboard accepts both PC133 DIMMs or SO-DIMMs. It will use both at the same time. However, when using a DIMM, be sure it is less than 1.1&quot; (28mm) tall, or you will not be able to install a second network card.<br /> * There are many different revisions of the NeoLinux operating system and not all include the necessary software to complete this tutorial.<br /> * You may need to purchase several EON 4000s to get suitable software and hardware.<br /> * These instructions were based on NeoLinux 2.4-100802, with kernel 2.2.20. Your particular configuration may vary slightly.<br /> <br /> With those potential issues in mind, follow along!<br /> <br /> There are three main steps to be completed to get m0n0wall running on your EON. First, you will need to get single-user access to the NeoLinux installation. Next, you need to enable networking and fetch and install m0n0wall. Third, you need to configure it to fit your requirements. I will address the first two of these, as adequate resources exist to help with the latter.<br /> <br /> To begin, you will need:<br /> <br /> * One or more Neoware EONs with disk-on-chip modules that plug into the IDE header<br /> * Access to the internet from your EON (or to a web server on a LAN)<br /> * A supported PCI network card. Common Intel or 3Com cards work fine.<br /> * At least 64MB of suitable memory. Some EONs ship with SO-DIMMs, others with DIMMs. These should be short enough to accomodate a PCI network card.<br /> * See the m0n0wall supported hardware page for more information.<br /> <br /> Step ONE: Get single-user access to the NeoLinux distribution.<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt may vary, but pressing tab should display either 'Software' or 'Eon_Software'.<br /> * Enter, as appropriate, either<br /> Software -s ramdisk=12000<br /> or<br /> Eon_Software -s ramdisk=12000<br /> and press enter.<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt.<br /> <br /> Step TWO: Fetch and install m0n0wall.<br /> <br /> * Check that your installation has the necessary software:<br /> bash# ls /usr/bin/wget<br /> . If NeoLinux reports that it is not found, you will have to try a different EON. Keep this hardware however: a single working EON can program m0n0wall onto several disk-on-chip modules, even those without the proper software. More on this later.<br /> * Plug the EON into a network which provides DHCP information and enable the ethernet connection:<br /> bash# cp /etc/sysconfig/network-scripts/ifcfg-eth0.default /etc/sysconfig/network-scripts/ifcfg-eth0<br /> bash# ifup eth0<br /> * Create a ramdisk on which to place temporary files during the installation:<br /> bash# mkfs.ext2 /dev/ram0<br /> bash# mount /dev/ram0 /mnt/usbcdrom<br /> bash# cd /mnt/usbcdrom<br /> bash# /usr/bin/wget http://hostname/path/to/m0n0wall<br /> bash# cp /bin/gunzip .<br /> bash# cp /bin/dd .<br /> * Now you're ready. You have created a ramdisk with the two utilities you will need to rewrite IDE disk-on-chip modules with m0n0wall. At this point, if you have modules containing copies of NeoLinux without wget, you should try using them first. That way if something goes wrong you can repeat these steps later. With the machine running, remove the IDE DOC that you booted from and replace it with the one you want to reprogram.<br /> * Then,<br /> gunzip -c m0n0wall-file-name.img | dd of=/dev/hda bs=16k<br /> Ignore the warning about trailing garbage.<br /> <br /> That's it! At this point you can remove the DOC and replace it with another one and repeat the reprogramming step, as many times as needed.<br /> <br /> When you next boot the machine, it should load m0n0wall exactly as it would on any other x86-compatible system. Jump right in with the m0n0wall quick-start guide for PC platforms. Chapter 3: Initial Configuration is probably where you will want to start. Good luck!<br /> <br /> Version 0.3 | Content date: 05 July 2008 | Page last generated: 2009-01-18 13:11 CST</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=Clasxt&diff=5311 2011-05-16T15:03:49Z

<p>129.57.167.199: </p> <hr /> <div>'''Clasxt's''' are mac mini's running MAC OS X.<br /> <br /> '''Initial installation'''<br /> <br /> * connect monitor, ethernet, keyboard and mouse and power up; sometimes it will not recognize keyboard or/and mouse, in that case just unplug mouse/keyboard and plug them back; follow instructions to identify keyboard<br /> <br /> * in '''System preferences/Network''': turn off '''AirPort'''; configure '''Ethernet''' as Manually and type IP address (ex. 129.56.167.xxx), mask (ex. 255.255.255.0), router (ex. 129.57.167.99), DNS server (ex. 129.57.167.5, 129.57.167.14) and search domain (ex. jlab.org)<br /> <br /> * in '''System preferences/Accounts''' change Admin's user password to the our clon root password; create new user '''clasrun''' with usual clasrun's pass, keep '''Automatic login''' is '''ON'''; click on '''Login Options''' and choose '''Automatic Login''' as '''clasrun'''<br /> <br /> * in '''System preferences/Energy Saver''' move '''Computer Sleep''' to '''Never''' to prevent user's forced logging off, and click on '''Start up automatically after a power failure'''<br /> <br /> * insert '''Application DVD''' and install all applications<br /> <br /> '''OBSOLETE'''<br /> <br /> '''Clasxt''' machines are diskless 'thin clients' from neoware, running newlinux. We have 5 those machines still in use:<br /> <br /> * clasxt23<br /> <br /> * clasxt33<br /> <br /> * clasxt35<br /> <br /> * clasxt37<br /> <br /> * clasxt39<br /> <br /> * clasxt40<br /> <br /> To reboot in single user mode do following:<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt should display 'Software'<br /> * Enter ''Software -s ramdisk=12000'' and press enter<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt<br /> <br /> <br /> <br /> '''IMPORTANT:'''<br /> <br /> On clon machines where clasxt's suppose to login, XDM server must be running. On Solaris 10 XDM server is running as part of ''dtlogin''. By default it has following options:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 7799 1 0 17:25:38 ? 0:00 /usr/dt/bin/dtlogin -daemon -udpPort 0<br /> <br /> which means upd connection is not allowed. Looking into options will see following:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> dtlogin/args astring \ -udpPort\ 0<br /> <br /> To change that use following command:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot;\&quot;<br /> <br /> Now that option is gone:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> clon00:/etc&gt;<br /> <br /> To place that option back type following:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot; -udpPort 0\&quot;<br /> <br /> Restart dtlogin server:<br /> <br /> /etc/init.d/dtlogin stop<br /> /etc/init.d/dtlogin start<br /> <br /> Now it is running without upd restriction:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 11503 1 0 17:30:46 ? 0:00 /usr/dt/bin/dtlogin -daemon<br /> <br /> <br /> In addition to that, to make fonts loading process work enable xfs service. Normally it will be enabled on the machines with monitors, but on servers like clon00 and clon10 it will be disabled by default:<br /> <br /> clon00:/etc&gt; svcs -a | grep xfs<br /> disabled Jan_04 svc:/application/x11/xfs:default<br /> clon00:/etc&gt;<br /> <br /> so enable it:<br /> <br /> clon00:/etc&gt; svcadm enable svc:/application/x11/xfs<br /> clon00:/etc&gt; svcs | grep xfs<br /> online 12:55:53 svc:/application/x11/xfs:default<br /> clon00:/etc&gt; <br /> <br /> <br /> <br /> <br /> <br /> Some useful information can be found in following paper:<br /> <br /> Some reports indicate that 3.x builds do not work. The error that is reported is<br /> FATAL ERROR<br /> The device that contains the configuration file (config.xml) could not be found. m0n0wall cannot continue booting.<br /> I do not yet know of a solution. This tutorial should be construed to apply only to the 2.x builds in the meantime. Please email me if you get 3.x working on an EON.<br /> <br /> Here's how to install the latest build of the excellent m0n0wall firewall on a Neoware EON 4000 thin client. These machines make excellent firewalls for home users and small businesses because they are cheap, compact, sturdy, and powerful enough to run a several megabit connection. The hardware is available in a variety of configurations, with CPUs roughly equivalent to a 150-200Mhz Pentium. Before embarking on this little journey, you should be aware of a few caveats:<br /> <br /> * Some Neoware boxes come with a 32-pin Disk-on-Chip module in a socket on the motherboard. m0n0wall does not ship with the required driver to run this module. Therefore, on these systems you will need a hard drive, compact flash to IDE adapter, or similar device to boot from. You may also be able to netboot your firewall (this is supported on the built-in network device), though I do not cover that in this tutorial.<br /> * The motherboard accepts both PC133 DIMMs or SO-DIMMs. It will use both at the same time. However, when using a DIMM, be sure it is less than 1.1&quot; (28mm) tall, or you will not be able to install a second network card.<br /> * There are many different revisions of the NeoLinux operating system and not all include the necessary software to complete this tutorial.<br /> * You may need to purchase several EON 4000s to get suitable software and hardware.<br /> * These instructions were based on NeoLinux 2.4-100802, with kernel 2.2.20. Your particular configuration may vary slightly.<br /> <br /> With those potential issues in mind, follow along!<br /> <br /> There are three main steps to be completed to get m0n0wall running on your EON. First, you will need to get single-user access to the NeoLinux installation. Next, you need to enable networking and fetch and install m0n0wall. Third, you need to configure it to fit your requirements. I will address the first two of these, as adequate resources exist to help with the latter.<br /> <br /> To begin, you will need:<br /> <br /> * One or more Neoware EONs with disk-on-chip modules that plug into the IDE header<br /> * Access to the internet from your EON (or to a web server on a LAN)<br /> * A supported PCI network card. Common Intel or 3Com cards work fine.<br /> * At least 64MB of suitable memory. Some EONs ship with SO-DIMMs, others with DIMMs. These should be short enough to accomodate a PCI network card.<br /> * See the m0n0wall supported hardware page for more information.<br /> <br /> Step ONE: Get single-user access to the NeoLinux distribution.<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt may vary, but pressing tab should display either 'Software' or 'Eon_Software'.<br /> * Enter, as appropriate, either<br /> Software -s ramdisk=12000<br /> or<br /> Eon_Software -s ramdisk=12000<br /> and press enter.<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt.<br /> <br /> Step TWO: Fetch and install m0n0wall.<br /> <br /> * Check that your installation has the necessary software:<br /> bash# ls /usr/bin/wget<br /> . If NeoLinux reports that it is not found, you will have to try a different EON. Keep this hardware however: a single working EON can program m0n0wall onto several disk-on-chip modules, even those without the proper software. More on this later.<br /> * Plug the EON into a network which provides DHCP information and enable the ethernet connection:<br /> bash# cp /etc/sysconfig/network-scripts/ifcfg-eth0.default /etc/sysconfig/network-scripts/ifcfg-eth0<br /> bash# ifup eth0<br /> * Create a ramdisk on which to place temporary files during the installation:<br /> bash# mkfs.ext2 /dev/ram0<br /> bash# mount /dev/ram0 /mnt/usbcdrom<br /> bash# cd /mnt/usbcdrom<br /> bash# /usr/bin/wget http://hostname/path/to/m0n0wall<br /> bash# cp /bin/gunzip .<br /> bash# cp /bin/dd .<br /> * Now you're ready. You have created a ramdisk with the two utilities you will need to rewrite IDE disk-on-chip modules with m0n0wall. At this point, if you have modules containing copies of NeoLinux without wget, you should try using them first. That way if something goes wrong you can repeat these steps later. With the machine running, remove the IDE DOC that you booted from and replace it with the one you want to reprogram.<br /> * Then,<br /> gunzip -c m0n0wall-file-name.img | dd of=/dev/hda bs=16k<br /> Ignore the warning about trailing garbage.<br /> <br /> That's it! At this point you can remove the DOC and replace it with another one and repeat the reprogramming step, as many times as needed.<br /> <br /> When you next boot the machine, it should load m0n0wall exactly as it would on any other x86-compatible system. Jump right in with the m0n0wall quick-start guide for PC platforms. Chapter 3: Initial Configuration is probably where you will want to start. Good luck!<br /> <br /> Version 0.3 | Content date: 05 July 2008 | Page last generated: 2009-01-18 13:11 CST</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=Clasxt&diff=5310 2011-05-16T15:01:35Z

<p>129.57.167.199: </p> <hr /> <div>'''Clasxt's''' are mac mini's running MAC OS X.<br /> <br /> '''Initial installation'''<br /> <br /> * connect monitor, ethernet, keyboard and mouse and power up; sometimes it will not recognize keyboard or/and mouse, in that case just unplug mouse/keyboard and plug them back; follow instructions to identify keyboard<br /> <br /> * in '''System preferences/Network''': turn off '''AirPort'''; configure '''Ethernet''' as Manually and type IP address (ex. 129.56.167.xxx), mask (ex. 255.255.255.0), router (ex. 129.57.167.99), DNS server (ex. 129.57.167.5, 129.57.167.14) and search domain (ex. jlab.org)<br /> <br /> * in '''System preferences/Accounts''' change Admin's user password to the our clon root password; create new user '''clasrun''' with usual clasrun's pass, keep '''Automatic login''' is '''ON'''; click on '''Login Options''' and choose '''Automatic Login''' as '''clasrun'''<br /> <br /> * in '''System preferences/Energy Saver''' move '''Computer Sleep''' to '''Never''' to prevent user's forced logging off, and click on '''Start up automatically after a power failure'''<br /> <br /> <br /> '''OBSOLETE'''<br /> <br /> '''Clasxt''' machines are diskless 'thin clients' from neoware, running newlinux. We have 5 those machines still in use:<br /> <br /> * clasxt23<br /> <br /> * clasxt33<br /> <br /> * clasxt35<br /> <br /> * clasxt37<br /> <br /> * clasxt39<br /> <br /> * clasxt40<br /> <br /> To reboot in single user mode do following:<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt should display 'Software'<br /> * Enter ''Software -s ramdisk=12000'' and press enter<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt<br /> <br /> <br /> <br /> '''IMPORTANT:'''<br /> <br /> On clon machines where clasxt's suppose to login, XDM server must be running. On Solaris 10 XDM server is running as part of ''dtlogin''. By default it has following options:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 7799 1 0 17:25:38 ? 0:00 /usr/dt/bin/dtlogin -daemon -udpPort 0<br /> <br /> which means upd connection is not allowed. Looking into options will see following:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> dtlogin/args astring \ -udpPort\ 0<br /> <br /> To change that use following command:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot;\&quot;<br /> <br /> Now that option is gone:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> clon00:/etc&gt;<br /> <br /> To place that option back type following:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot; -udpPort 0\&quot;<br /> <br /> Restart dtlogin server:<br /> <br /> /etc/init.d/dtlogin stop<br /> /etc/init.d/dtlogin start<br /> <br /> Now it is running without upd restriction:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 11503 1 0 17:30:46 ? 0:00 /usr/dt/bin/dtlogin -daemon<br /> <br /> <br /> In addition to that, to make fonts loading process work enable xfs service. Normally it will be enabled on the machines with monitors, but on servers like clon00 and clon10 it will be disabled by default:<br /> <br /> clon00:/etc&gt; svcs -a | grep xfs<br /> disabled Jan_04 svc:/application/x11/xfs:default<br /> clon00:/etc&gt;<br /> <br /> so enable it:<br /> <br /> clon00:/etc&gt; svcadm enable svc:/application/x11/xfs<br /> clon00:/etc&gt; svcs | grep xfs<br /> online 12:55:53 svc:/application/x11/xfs:default<br /> clon00:/etc&gt; <br /> <br /> <br /> <br /> <br /> <br /> Some useful information can be found in following paper:<br /> <br /> Some reports indicate that 3.x builds do not work. The error that is reported is<br /> FATAL ERROR<br /> The device that contains the configuration file (config.xml) could not be found. m0n0wall cannot continue booting.<br /> I do not yet know of a solution. This tutorial should be construed to apply only to the 2.x builds in the meantime. Please email me if you get 3.x working on an EON.<br /> <br /> Here's how to install the latest build of the excellent m0n0wall firewall on a Neoware EON 4000 thin client. These machines make excellent firewalls for home users and small businesses because they are cheap, compact, sturdy, and powerful enough to run a several megabit connection. The hardware is available in a variety of configurations, with CPUs roughly equivalent to a 150-200Mhz Pentium. Before embarking on this little journey, you should be aware of a few caveats:<br /> <br /> * Some Neoware boxes come with a 32-pin Disk-on-Chip module in a socket on the motherboard. m0n0wall does not ship with the required driver to run this module. Therefore, on these systems you will need a hard drive, compact flash to IDE adapter, or similar device to boot from. You may also be able to netboot your firewall (this is supported on the built-in network device), though I do not cover that in this tutorial.<br /> * The motherboard accepts both PC133 DIMMs or SO-DIMMs. It will use both at the same time. However, when using a DIMM, be sure it is less than 1.1&quot; (28mm) tall, or you will not be able to install a second network card.<br /> * There are many different revisions of the NeoLinux operating system and not all include the necessary software to complete this tutorial.<br /> * You may need to purchase several EON 4000s to get suitable software and hardware.<br /> * These instructions were based on NeoLinux 2.4-100802, with kernel 2.2.20. Your particular configuration may vary slightly.<br /> <br /> With those potential issues in mind, follow along!<br /> <br /> There are three main steps to be completed to get m0n0wall running on your EON. First, you will need to get single-user access to the NeoLinux installation. Next, you need to enable networking and fetch and install m0n0wall. Third, you need to configure it to fit your requirements. I will address the first two of these, as adequate resources exist to help with the latter.<br /> <br /> To begin, you will need:<br /> <br /> * One or more Neoware EONs with disk-on-chip modules that plug into the IDE header<br /> * Access to the internet from your EON (or to a web server on a LAN)<br /> * A supported PCI network card. Common Intel or 3Com cards work fine.<br /> * At least 64MB of suitable memory. Some EONs ship with SO-DIMMs, others with DIMMs. These should be short enough to accomodate a PCI network card.<br /> * See the m0n0wall supported hardware page for more information.<br /> <br /> Step ONE: Get single-user access to the NeoLinux distribution.<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt may vary, but pressing tab should display either 'Software' or 'Eon_Software'.<br /> * Enter, as appropriate, either<br /> Software -s ramdisk=12000<br /> or<br /> Eon_Software -s ramdisk=12000<br /> and press enter.<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt.<br /> <br /> Step TWO: Fetch and install m0n0wall.<br /> <br /> * Check that your installation has the necessary software:<br /> bash# ls /usr/bin/wget<br /> . If NeoLinux reports that it is not found, you will have to try a different EON. Keep this hardware however: a single working EON can program m0n0wall onto several disk-on-chip modules, even those without the proper software. More on this later.<br /> * Plug the EON into a network which provides DHCP information and enable the ethernet connection:<br /> bash# cp /etc/sysconfig/network-scripts/ifcfg-eth0.default /etc/sysconfig/network-scripts/ifcfg-eth0<br /> bash# ifup eth0<br /> * Create a ramdisk on which to place temporary files during the installation:<br /> bash# mkfs.ext2 /dev/ram0<br /> bash# mount /dev/ram0 /mnt/usbcdrom<br /> bash# cd /mnt/usbcdrom<br /> bash# /usr/bin/wget http://hostname/path/to/m0n0wall<br /> bash# cp /bin/gunzip .<br /> bash# cp /bin/dd .<br /> * Now you're ready. You have created a ramdisk with the two utilities you will need to rewrite IDE disk-on-chip modules with m0n0wall. At this point, if you have modules containing copies of NeoLinux without wget, you should try using them first. That way if something goes wrong you can repeat these steps later. With the machine running, remove the IDE DOC that you booted from and replace it with the one you want to reprogram.<br /> * Then,<br /> gunzip -c m0n0wall-file-name.img | dd of=/dev/hda bs=16k<br /> Ignore the warning about trailing garbage.<br /> <br /> That's it! At this point you can remove the DOC and replace it with another one and repeat the reprogramming step, as many times as needed.<br /> <br /> When you next boot the machine, it should load m0n0wall exactly as it would on any other x86-compatible system. Jump right in with the m0n0wall quick-start guide for PC platforms. Chapter 3: Initial Configuration is probably where you will want to start. Good luck!<br /> <br /> Version 0.3 | Content date: 05 July 2008 | Page last generated: 2009-01-18 13:11 CST</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=Clasxt&diff=5309 2011-05-16T14:56:50Z

<p>129.57.167.199: </p> <hr /> <div>'''Clasxt's''' are mac mini's running MAC OS X.<br /> <br /> '''Initial installation'''<br /> <br /> * connect monitor, ethernet, keyboard and mouse and power up; sometimes it will not recognize keyboard or/and mouse, in that case just unplug mouse/keyboard and plug them back; follow instructions to identify keyboard<br /> <br /> * in '''System preferences/Network''': turn off '''AirPort'''; configure '''Ethernet''' as Manually and type IP address (ex. 129.56.167.xxx), mask (ex. 255.255.255.0), router (ex. 129.57.167.99), DNS server (ex. 129.57.167.5, 129.57.167.14) and search domain (ex. jlab.org)<br /> <br /> * in '''System preferences/Accounts''' change Admin's user password to the our clon root password; create new user '''clasrun''' with usual clasrun's pass, keep '''Automatic login''' is '''ON'''<br /> <br /> * in '''System preferences/Energy Saver''' move '''Computer Sleep''' to '''Never''' to prevent user's forced logging off, and click on '''Start up automatically after a power failure'''<br /> <br /> <br /> '''OBSOLETE'''<br /> <br /> '''Clasxt''' machines are diskless 'thin clients' from neoware, running newlinux. We have 5 those machines still in use:<br /> <br /> * clasxt23<br /> <br /> * clasxt33<br /> <br /> * clasxt35<br /> <br /> * clasxt37<br /> <br /> * clasxt39<br /> <br /> * clasxt40<br /> <br /> To reboot in single user mode do following:<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt should display 'Software'<br /> * Enter ''Software -s ramdisk=12000'' and press enter<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt<br /> <br /> <br /> <br /> '''IMPORTANT:'''<br /> <br /> On clon machines where clasxt's suppose to login, XDM server must be running. On Solaris 10 XDM server is running as part of ''dtlogin''. By default it has following options:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 7799 1 0 17:25:38 ? 0:00 /usr/dt/bin/dtlogin -daemon -udpPort 0<br /> <br /> which means upd connection is not allowed. Looking into options will see following:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> dtlogin/args astring \ -udpPort\ 0<br /> <br /> To change that use following command:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot;\&quot;<br /> <br /> Now that option is gone:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> clon00:/etc&gt;<br /> <br /> To place that option back type following:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot; -udpPort 0\&quot;<br /> <br /> Restart dtlogin server:<br /> <br /> /etc/init.d/dtlogin stop<br /> /etc/init.d/dtlogin start<br /> <br /> Now it is running without upd restriction:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 11503 1 0 17:30:46 ? 0:00 /usr/dt/bin/dtlogin -daemon<br /> <br /> <br /> In addition to that, to make fonts loading process work enable xfs service. Normally it will be enabled on the machines with monitors, but on servers like clon00 and clon10 it will be disabled by default:<br /> <br /> clon00:/etc&gt; svcs -a | grep xfs<br /> disabled Jan_04 svc:/application/x11/xfs:default<br /> clon00:/etc&gt;<br /> <br /> so enable it:<br /> <br /> clon00:/etc&gt; svcadm enable svc:/application/x11/xfs<br /> clon00:/etc&gt; svcs | grep xfs<br /> online 12:55:53 svc:/application/x11/xfs:default<br /> clon00:/etc&gt; <br /> <br /> <br /> <br /> <br /> <br /> Some useful information can be found in following paper:<br /> <br /> Some reports indicate that 3.x builds do not work. The error that is reported is<br /> FATAL ERROR<br /> The device that contains the configuration file (config.xml) could not be found. m0n0wall cannot continue booting.<br /> I do not yet know of a solution. This tutorial should be construed to apply only to the 2.x builds in the meantime. Please email me if you get 3.x working on an EON.<br /> <br /> Here's how to install the latest build of the excellent m0n0wall firewall on a Neoware EON 4000 thin client. These machines make excellent firewalls for home users and small businesses because they are cheap, compact, sturdy, and powerful enough to run a several megabit connection. The hardware is available in a variety of configurations, with CPUs roughly equivalent to a 150-200Mhz Pentium. Before embarking on this little journey, you should be aware of a few caveats:<br /> <br /> * Some Neoware boxes come with a 32-pin Disk-on-Chip module in a socket on the motherboard. m0n0wall does not ship with the required driver to run this module. Therefore, on these systems you will need a hard drive, compact flash to IDE adapter, or similar device to boot from. You may also be able to netboot your firewall (this is supported on the built-in network device), though I do not cover that in this tutorial.<br /> * The motherboard accepts both PC133 DIMMs or SO-DIMMs. It will use both at the same time. However, when using a DIMM, be sure it is less than 1.1&quot; (28mm) tall, or you will not be able to install a second network card.<br /> * There are many different revisions of the NeoLinux operating system and not all include the necessary software to complete this tutorial.<br /> * You may need to purchase several EON 4000s to get suitable software and hardware.<br /> * These instructions were based on NeoLinux 2.4-100802, with kernel 2.2.20. Your particular configuration may vary slightly.<br /> <br /> With those potential issues in mind, follow along!<br /> <br /> There are three main steps to be completed to get m0n0wall running on your EON. First, you will need to get single-user access to the NeoLinux installation. Next, you need to enable networking and fetch and install m0n0wall. Third, you need to configure it to fit your requirements. I will address the first two of these, as adequate resources exist to help with the latter.<br /> <br /> To begin, you will need:<br /> <br /> * One or more Neoware EONs with disk-on-chip modules that plug into the IDE header<br /> * Access to the internet from your EON (or to a web server on a LAN)<br /> * A supported PCI network card. Common Intel or 3Com cards work fine.<br /> * At least 64MB of suitable memory. Some EONs ship with SO-DIMMs, others with DIMMs. These should be short enough to accomodate a PCI network card.<br /> * See the m0n0wall supported hardware page for more information.<br /> <br /> Step ONE: Get single-user access to the NeoLinux distribution.<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt may vary, but pressing tab should display either 'Software' or 'Eon_Software'.<br /> * Enter, as appropriate, either<br /> Software -s ramdisk=12000<br /> or<br /> Eon_Software -s ramdisk=12000<br /> and press enter.<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt.<br /> <br /> Step TWO: Fetch and install m0n0wall.<br /> <br /> * Check that your installation has the necessary software:<br /> bash# ls /usr/bin/wget<br /> . If NeoLinux reports that it is not found, you will have to try a different EON. Keep this hardware however: a single working EON can program m0n0wall onto several disk-on-chip modules, even those without the proper software. More on this later.<br /> * Plug the EON into a network which provides DHCP information and enable the ethernet connection:<br /> bash# cp /etc/sysconfig/network-scripts/ifcfg-eth0.default /etc/sysconfig/network-scripts/ifcfg-eth0<br /> bash# ifup eth0<br /> * Create a ramdisk on which to place temporary files during the installation:<br /> bash# mkfs.ext2 /dev/ram0<br /> bash# mount /dev/ram0 /mnt/usbcdrom<br /> bash# cd /mnt/usbcdrom<br /> bash# /usr/bin/wget http://hostname/path/to/m0n0wall<br /> bash# cp /bin/gunzip .<br /> bash# cp /bin/dd .<br /> * Now you're ready. You have created a ramdisk with the two utilities you will need to rewrite IDE disk-on-chip modules with m0n0wall. At this point, if you have modules containing copies of NeoLinux without wget, you should try using them first. That way if something goes wrong you can repeat these steps later. With the machine running, remove the IDE DOC that you booted from and replace it with the one you want to reprogram.<br /> * Then,<br /> gunzip -c m0n0wall-file-name.img | dd of=/dev/hda bs=16k<br /> Ignore the warning about trailing garbage.<br /> <br /> That's it! At this point you can remove the DOC and replace it with another one and repeat the reprogramming step, as many times as needed.<br /> <br /> When you next boot the machine, it should load m0n0wall exactly as it would on any other x86-compatible system. Jump right in with the m0n0wall quick-start guide for PC platforms. Chapter 3: Initial Configuration is probably where you will want to start. Good luck!<br /> <br /> Version 0.3 | Content date: 05 July 2008 | Page last generated: 2009-01-18 13:11 CST</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=Clasxt&diff=5308 2011-05-16T14:55:54Z

<p>129.57.167.199: </p> <hr /> <div>'''Clasxt's''' are mac mini's running MAC OS X.<br /> <br /> '''Initial installation'''<br /> <br /> * connect monitor, ethernet, keyboard and mouse and power up; sometimes it will not recognize keyboard or/and mouse, in that case just unplug mouse/keyboard and plug them back; follow instructions to identify keyboard<br /> <br /> * in '''System preferences/Network''': turn off '''AirPort'''; configure '''Ethernet''' as Manually and type IP address (ex. 129.56.167.xxx), mask (ex. 255.255.255.0), router (ex. 129.57.167.99), DNS server (ex. 129.57.167.5, 129.57.167.14) and search domain (ex. jlab.org)<br /> <br /> * in '''System preferences/Accounts''' change Admin's user password to the our clon root password; create new user '''clasrun''' with usual clasrun's pass, keep '''Automatic login''' is '''ON'''<br /> <br /> * in '''System preferences/Energy Saver''' move '''Computer Sleep''' to '''Never''' to prevent user's forced logging off<br /> <br /> <br /> '''OBSOLETE'''<br /> <br /> '''Clasxt''' machines are diskless 'thin clients' from neoware, running newlinux. We have 5 those machines still in use:<br /> <br /> * clasxt23<br /> <br /> * clasxt33<br /> <br /> * clasxt35<br /> <br /> * clasxt37<br /> <br /> * clasxt39<br /> <br /> * clasxt40<br /> <br /> To reboot in single user mode do following:<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt should display 'Software'<br /> * Enter ''Software -s ramdisk=12000'' and press enter<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt<br /> <br /> <br /> <br /> '''IMPORTANT:'''<br /> <br /> On clon machines where clasxt's suppose to login, XDM server must be running. On Solaris 10 XDM server is running as part of ''dtlogin''. By default it has following options:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 7799 1 0 17:25:38 ? 0:00 /usr/dt/bin/dtlogin -daemon -udpPort 0<br /> <br /> which means upd connection is not allowed. Looking into options will see following:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> dtlogin/args astring \ -udpPort\ 0<br /> <br /> To change that use following command:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot;\&quot;<br /> <br /> Now that option is gone:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> clon00:/etc&gt;<br /> <br /> To place that option back type following:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot; -udpPort 0\&quot;<br /> <br /> Restart dtlogin server:<br /> <br /> /etc/init.d/dtlogin stop<br /> /etc/init.d/dtlogin start<br /> <br /> Now it is running without upd restriction:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 11503 1 0 17:30:46 ? 0:00 /usr/dt/bin/dtlogin -daemon<br /> <br /> <br /> In addition to that, to make fonts loading process work enable xfs service. Normally it will be enabled on the machines with monitors, but on servers like clon00 and clon10 it will be disabled by default:<br /> <br /> clon00:/etc&gt; svcs -a | grep xfs<br /> disabled Jan_04 svc:/application/x11/xfs:default<br /> clon00:/etc&gt;<br /> <br /> so enable it:<br /> <br /> clon00:/etc&gt; svcadm enable svc:/application/x11/xfs<br /> clon00:/etc&gt; svcs | grep xfs<br /> online 12:55:53 svc:/application/x11/xfs:default<br /> clon00:/etc&gt; <br /> <br /> <br /> <br /> <br /> <br /> Some useful information can be found in following paper:<br /> <br /> Some reports indicate that 3.x builds do not work. The error that is reported is<br /> FATAL ERROR<br /> The device that contains the configuration file (config.xml) could not be found. m0n0wall cannot continue booting.<br /> I do not yet know of a solution. This tutorial should be construed to apply only to the 2.x builds in the meantime. Please email me if you get 3.x working on an EON.<br /> <br /> Here's how to install the latest build of the excellent m0n0wall firewall on a Neoware EON 4000 thin client. These machines make excellent firewalls for home users and small businesses because they are cheap, compact, sturdy, and powerful enough to run a several megabit connection. The hardware is available in a variety of configurations, with CPUs roughly equivalent to a 150-200Mhz Pentium. Before embarking on this little journey, you should be aware of a few caveats:<br /> <br /> * Some Neoware boxes come with a 32-pin Disk-on-Chip module in a socket on the motherboard. m0n0wall does not ship with the required driver to run this module. Therefore, on these systems you will need a hard drive, compact flash to IDE adapter, or similar device to boot from. You may also be able to netboot your firewall (this is supported on the built-in network device), though I do not cover that in this tutorial.<br /> * The motherboard accepts both PC133 DIMMs or SO-DIMMs. It will use both at the same time. However, when using a DIMM, be sure it is less than 1.1&quot; (28mm) tall, or you will not be able to install a second network card.<br /> * There are many different revisions of the NeoLinux operating system and not all include the necessary software to complete this tutorial.<br /> * You may need to purchase several EON 4000s to get suitable software and hardware.<br /> * These instructions were based on NeoLinux 2.4-100802, with kernel 2.2.20. Your particular configuration may vary slightly.<br /> <br /> With those potential issues in mind, follow along!<br /> <br /> There are three main steps to be completed to get m0n0wall running on your EON. First, you will need to get single-user access to the NeoLinux installation. Next, you need to enable networking and fetch and install m0n0wall. Third, you need to configure it to fit your requirements. I will address the first two of these, as adequate resources exist to help with the latter.<br /> <br /> To begin, you will need:<br /> <br /> * One or more Neoware EONs with disk-on-chip modules that plug into the IDE header<br /> * Access to the internet from your EON (or to a web server on a LAN)<br /> * A supported PCI network card. Common Intel or 3Com cards work fine.<br /> * At least 64MB of suitable memory. Some EONs ship with SO-DIMMs, others with DIMMs. These should be short enough to accomodate a PCI network card.<br /> * See the m0n0wall supported hardware page for more information.<br /> <br /> Step ONE: Get single-user access to the NeoLinux distribution.<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt may vary, but pressing tab should display either 'Software' or 'Eon_Software'.<br /> * Enter, as appropriate, either<br /> Software -s ramdisk=12000<br /> or<br /> Eon_Software -s ramdisk=12000<br /> and press enter.<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt.<br /> <br /> Step TWO: Fetch and install m0n0wall.<br /> <br /> * Check that your installation has the necessary software:<br /> bash# ls /usr/bin/wget<br /> . If NeoLinux reports that it is not found, you will have to try a different EON. Keep this hardware however: a single working EON can program m0n0wall onto several disk-on-chip modules, even those without the proper software. More on this later.<br /> * Plug the EON into a network which provides DHCP information and enable the ethernet connection:<br /> bash# cp /etc/sysconfig/network-scripts/ifcfg-eth0.default /etc/sysconfig/network-scripts/ifcfg-eth0<br /> bash# ifup eth0<br /> * Create a ramdisk on which to place temporary files during the installation:<br /> bash# mkfs.ext2 /dev/ram0<br /> bash# mount /dev/ram0 /mnt/usbcdrom<br /> bash# cd /mnt/usbcdrom<br /> bash# /usr/bin/wget http://hostname/path/to/m0n0wall<br /> bash# cp /bin/gunzip .<br /> bash# cp /bin/dd .<br /> * Now you're ready. You have created a ramdisk with the two utilities you will need to rewrite IDE disk-on-chip modules with m0n0wall. At this point, if you have modules containing copies of NeoLinux without wget, you should try using them first. That way if something goes wrong you can repeat these steps later. With the machine running, remove the IDE DOC that you booted from and replace it with the one you want to reprogram.<br /> * Then,<br /> gunzip -c m0n0wall-file-name.img | dd of=/dev/hda bs=16k<br /> Ignore the warning about trailing garbage.<br /> <br /> That's it! At this point you can remove the DOC and replace it with another one and repeat the reprogramming step, as many times as needed.<br /> <br /> When you next boot the machine, it should load m0n0wall exactly as it would on any other x86-compatible system. Jump right in with the m0n0wall quick-start guide for PC platforms. Chapter 3: Initial Configuration is probably where you will want to start. Good luck!<br /> <br /> Version 0.3 | Content date: 05 July 2008 | Page last generated: 2009-01-18 13:11 CST</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=Clasxt&diff=5307 2011-05-16T14:53:35Z

<p>129.57.167.199: </p> <hr /> <div>'''Clasxt's''' are mac mini's running MAC OS X.<br /> <br /> '''Initial installation'''<br /> <br /> * connect monitor, ethernet, keyboard and mouse and power up; sometimes it will not recognize keyboard or/and mouse, in that case just unplug mouse/keyboard and plug them back; follow instructions to identify keyboard<br /> <br /> * in '''System preferences/Network''': turn off '''AirPort'''; configure '''Ethernet''' as Manually and type IP address (ex. 129.56.167.xxx), mask (ex. 255.255.255.0), router (ex. 129.57.167.99), DNS server (ex. 129.57.167.5, 129.57.167.14) and search domain (ex. jlab.org)<br /> <br /> * in '''System preferences/Accounts''' change Admin's user password to the our clon root password; create new user '''clasrun''' with usual clasrun's pass, keep '''Automatic login''' is '''ON'''<br /> <br /> <br /> <br /> '''OBSOLETE'''<br /> <br /> '''Clasxt''' machines are diskless 'thin clients' from neoware, running newlinux. We have 5 those machines still in use:<br /> <br /> * clasxt23<br /> <br /> * clasxt33<br /> <br /> * clasxt35<br /> <br /> * clasxt37<br /> <br /> * clasxt39<br /> <br /> * clasxt40<br /> <br /> To reboot in single user mode do following:<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt should display 'Software'<br /> * Enter ''Software -s ramdisk=12000'' and press enter<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt<br /> <br /> <br /> <br /> '''IMPORTANT:'''<br /> <br /> On clon machines where clasxt's suppose to login, XDM server must be running. On Solaris 10 XDM server is running as part of ''dtlogin''. By default it has following options:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 7799 1 0 17:25:38 ? 0:00 /usr/dt/bin/dtlogin -daemon -udpPort 0<br /> <br /> which means upd connection is not allowed. Looking into options will see following:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> dtlogin/args astring \ -udpPort\ 0<br /> <br /> To change that use following command:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot;\&quot;<br /> <br /> Now that option is gone:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> clon00:/etc&gt;<br /> <br /> To place that option back type following:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot; -udpPort 0\&quot;<br /> <br /> Restart dtlogin server:<br /> <br /> /etc/init.d/dtlogin stop<br /> /etc/init.d/dtlogin start<br /> <br /> Now it is running without upd restriction:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 11503 1 0 17:30:46 ? 0:00 /usr/dt/bin/dtlogin -daemon<br /> <br /> <br /> In addition to that, to make fonts loading process work enable xfs service. Normally it will be enabled on the machines with monitors, but on servers like clon00 and clon10 it will be disabled by default:<br /> <br /> clon00:/etc&gt; svcs -a | grep xfs<br /> disabled Jan_04 svc:/application/x11/xfs:default<br /> clon00:/etc&gt;<br /> <br /> so enable it:<br /> <br /> clon00:/etc&gt; svcadm enable svc:/application/x11/xfs<br /> clon00:/etc&gt; svcs | grep xfs<br /> online 12:55:53 svc:/application/x11/xfs:default<br /> clon00:/etc&gt; <br /> <br /> <br /> <br /> <br /> <br /> Some useful information can be found in following paper:<br /> <br /> Some reports indicate that 3.x builds do not work. The error that is reported is<br /> FATAL ERROR<br /> The device that contains the configuration file (config.xml) could not be found. m0n0wall cannot continue booting.<br /> I do not yet know of a solution. This tutorial should be construed to apply only to the 2.x builds in the meantime. Please email me if you get 3.x working on an EON.<br /> <br /> Here's how to install the latest build of the excellent m0n0wall firewall on a Neoware EON 4000 thin client. These machines make excellent firewalls for home users and small businesses because they are cheap, compact, sturdy, and powerful enough to run a several megabit connection. The hardware is available in a variety of configurations, with CPUs roughly equivalent to a 150-200Mhz Pentium. Before embarking on this little journey, you should be aware of a few caveats:<br /> <br /> * Some Neoware boxes come with a 32-pin Disk-on-Chip module in a socket on the motherboard. m0n0wall does not ship with the required driver to run this module. Therefore, on these systems you will need a hard drive, compact flash to IDE adapter, or similar device to boot from. You may also be able to netboot your firewall (this is supported on the built-in network device), though I do not cover that in this tutorial.<br /> * The motherboard accepts both PC133 DIMMs or SO-DIMMs. It will use both at the same time. However, when using a DIMM, be sure it is less than 1.1&quot; (28mm) tall, or you will not be able to install a second network card.<br /> * There are many different revisions of the NeoLinux operating system and not all include the necessary software to complete this tutorial.<br /> * You may need to purchase several EON 4000s to get suitable software and hardware.<br /> * These instructions were based on NeoLinux 2.4-100802, with kernel 2.2.20. Your particular configuration may vary slightly.<br /> <br /> With those potential issues in mind, follow along!<br /> <br /> There are three main steps to be completed to get m0n0wall running on your EON. First, you will need to get single-user access to the NeoLinux installation. Next, you need to enable networking and fetch and install m0n0wall. Third, you need to configure it to fit your requirements. I will address the first two of these, as adequate resources exist to help with the latter.<br /> <br /> To begin, you will need:<br /> <br /> * One or more Neoware EONs with disk-on-chip modules that plug into the IDE header<br /> * Access to the internet from your EON (or to a web server on a LAN)<br /> * A supported PCI network card. Common Intel or 3Com cards work fine.<br /> * At least 64MB of suitable memory. Some EONs ship with SO-DIMMs, others with DIMMs. These should be short enough to accomodate a PCI network card.<br /> * See the m0n0wall supported hardware page for more information.<br /> <br /> Step ONE: Get single-user access to the NeoLinux distribution.<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt may vary, but pressing tab should display either 'Software' or 'Eon_Software'.<br /> * Enter, as appropriate, either<br /> Software -s ramdisk=12000<br /> or<br /> Eon_Software -s ramdisk=12000<br /> and press enter.<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt.<br /> <br /> Step TWO: Fetch and install m0n0wall.<br /> <br /> * Check that your installation has the necessary software:<br /> bash# ls /usr/bin/wget<br /> . If NeoLinux reports that it is not found, you will have to try a different EON. Keep this hardware however: a single working EON can program m0n0wall onto several disk-on-chip modules, even those without the proper software. More on this later.<br /> * Plug the EON into a network which provides DHCP information and enable the ethernet connection:<br /> bash# cp /etc/sysconfig/network-scripts/ifcfg-eth0.default /etc/sysconfig/network-scripts/ifcfg-eth0<br /> bash# ifup eth0<br /> * Create a ramdisk on which to place temporary files during the installation:<br /> bash# mkfs.ext2 /dev/ram0<br /> bash# mount /dev/ram0 /mnt/usbcdrom<br /> bash# cd /mnt/usbcdrom<br /> bash# /usr/bin/wget http://hostname/path/to/m0n0wall<br /> bash# cp /bin/gunzip .<br /> bash# cp /bin/dd .<br /> * Now you're ready. You have created a ramdisk with the two utilities you will need to rewrite IDE disk-on-chip modules with m0n0wall. At this point, if you have modules containing copies of NeoLinux without wget, you should try using them first. That way if something goes wrong you can repeat these steps later. With the machine running, remove the IDE DOC that you booted from and replace it with the one you want to reprogram.<br /> * Then,<br /> gunzip -c m0n0wall-file-name.img | dd of=/dev/hda bs=16k<br /> Ignore the warning about trailing garbage.<br /> <br /> That's it! At this point you can remove the DOC and replace it with another one and repeat the reprogramming step, as many times as needed.<br /> <br /> When you next boot the machine, it should load m0n0wall exactly as it would on any other x86-compatible system. Jump right in with the m0n0wall quick-start guide for PC platforms. Chapter 3: Initial Configuration is probably where you will want to start. Good luck!<br /> <br /> Version 0.3 | Content date: 05 July 2008 | Page last generated: 2009-01-18 13:11 CST</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=Clasxt&diff=5306 2011-05-16T14:46:57Z

<p>129.57.167.199: </p> <hr /> <div>'''Clasxt's''' are mac mini's running MAC OS X.<br /> <br /> '''Initial installation'''<br /> <br /> * connect monitor, ethernet, keyboard and mouse and power up; sometimes it will not recognize keyboard or/and mouse, in that case just unplug mouse/keyboard and plug them back; follow instructions to identify keyboard<br /> <br /> * in '''System preferences/Network''': turn off '''AirPort'''; configure '''Ethernet''' as Manually and type IP address (ex. 129.56.167.xxx), mask (ex. 255.255.255.0), router (ex. 129.57.167.99), DNS server (ex. 129.57.167.5, 129.57.167.14) and search domain (ex. jlab.org)<br /> <br /> <br /> <br /> <br /> <br /> '''OBSOLETE'''<br /> <br /> '''Clasxt''' machines are diskless 'thin clients' from neoware, running newlinux. We have 5 those machines still in use:<br /> <br /> * clasxt23<br /> <br /> * clasxt33<br /> <br /> * clasxt35<br /> <br /> * clasxt37<br /> <br /> * clasxt39<br /> <br /> * clasxt40<br /> <br /> To reboot in single user mode do following:<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt should display 'Software'<br /> * Enter ''Software -s ramdisk=12000'' and press enter<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt<br /> <br /> <br /> <br /> '''IMPORTANT:'''<br /> <br /> On clon machines where clasxt's suppose to login, XDM server must be running. On Solaris 10 XDM server is running as part of ''dtlogin''. By default it has following options:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 7799 1 0 17:25:38 ? 0:00 /usr/dt/bin/dtlogin -daemon -udpPort 0<br /> <br /> which means upd connection is not allowed. Looking into options will see following:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> dtlogin/args astring \ -udpPort\ 0<br /> <br /> To change that use following command:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot;\&quot;<br /> <br /> Now that option is gone:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> clon00:/etc&gt;<br /> <br /> To place that option back type following:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot; -udpPort 0\&quot;<br /> <br /> Restart dtlogin server:<br /> <br /> /etc/init.d/dtlogin stop<br /> /etc/init.d/dtlogin start<br /> <br /> Now it is running without upd restriction:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 11503 1 0 17:30:46 ? 0:00 /usr/dt/bin/dtlogin -daemon<br /> <br /> <br /> In addition to that, to make fonts loading process work enable xfs service. Normally it will be enabled on the machines with monitors, but on servers like clon00 and clon10 it will be disabled by default:<br /> <br /> clon00:/etc&gt; svcs -a | grep xfs<br /> disabled Jan_04 svc:/application/x11/xfs:default<br /> clon00:/etc&gt;<br /> <br /> so enable it:<br /> <br /> clon00:/etc&gt; svcadm enable svc:/application/x11/xfs<br /> clon00:/etc&gt; svcs | grep xfs<br /> online 12:55:53 svc:/application/x11/xfs:default<br /> clon00:/etc&gt; <br /> <br /> <br /> <br /> <br /> <br /> Some useful information can be found in following paper:<br /> <br /> Some reports indicate that 3.x builds do not work. The error that is reported is<br /> FATAL ERROR<br /> The device that contains the configuration file (config.xml) could not be found. m0n0wall cannot continue booting.<br /> I do not yet know of a solution. This tutorial should be construed to apply only to the 2.x builds in the meantime. Please email me if you get 3.x working on an EON.<br /> <br /> Here's how to install the latest build of the excellent m0n0wall firewall on a Neoware EON 4000 thin client. These machines make excellent firewalls for home users and small businesses because they are cheap, compact, sturdy, and powerful enough to run a several megabit connection. The hardware is available in a variety of configurations, with CPUs roughly equivalent to a 150-200Mhz Pentium. Before embarking on this little journey, you should be aware of a few caveats:<br /> <br /> * Some Neoware boxes come with a 32-pin Disk-on-Chip module in a socket on the motherboard. m0n0wall does not ship with the required driver to run this module. Therefore, on these systems you will need a hard drive, compact flash to IDE adapter, or similar device to boot from. You may also be able to netboot your firewall (this is supported on the built-in network device), though I do not cover that in this tutorial.<br /> * The motherboard accepts both PC133 DIMMs or SO-DIMMs. It will use both at the same time. However, when using a DIMM, be sure it is less than 1.1&quot; (28mm) tall, or you will not be able to install a second network card.<br /> * There are many different revisions of the NeoLinux operating system and not all include the necessary software to complete this tutorial.<br /> * You may need to purchase several EON 4000s to get suitable software and hardware.<br /> * These instructions were based on NeoLinux 2.4-100802, with kernel 2.2.20. Your particular configuration may vary slightly.<br /> <br /> With those potential issues in mind, follow along!<br /> <br /> There are three main steps to be completed to get m0n0wall running on your EON. First, you will need to get single-user access to the NeoLinux installation. Next, you need to enable networking and fetch and install m0n0wall. Third, you need to configure it to fit your requirements. I will address the first two of these, as adequate resources exist to help with the latter.<br /> <br /> To begin, you will need:<br /> <br /> * One or more Neoware EONs with disk-on-chip modules that plug into the IDE header<br /> * Access to the internet from your EON (or to a web server on a LAN)<br /> * A supported PCI network card. Common Intel or 3Com cards work fine.<br /> * At least 64MB of suitable memory. Some EONs ship with SO-DIMMs, others with DIMMs. These should be short enough to accomodate a PCI network card.<br /> * See the m0n0wall supported hardware page for more information.<br /> <br /> Step ONE: Get single-user access to the NeoLinux distribution.<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt may vary, but pressing tab should display either 'Software' or 'Eon_Software'.<br /> * Enter, as appropriate, either<br /> Software -s ramdisk=12000<br /> or<br /> Eon_Software -s ramdisk=12000<br /> and press enter.<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt.<br /> <br /> Step TWO: Fetch and install m0n0wall.<br /> <br /> * Check that your installation has the necessary software:<br /> bash# ls /usr/bin/wget<br /> . If NeoLinux reports that it is not found, you will have to try a different EON. Keep this hardware however: a single working EON can program m0n0wall onto several disk-on-chip modules, even those without the proper software. More on this later.<br /> * Plug the EON into a network which provides DHCP information and enable the ethernet connection:<br /> bash# cp /etc/sysconfig/network-scripts/ifcfg-eth0.default /etc/sysconfig/network-scripts/ifcfg-eth0<br /> bash# ifup eth0<br /> * Create a ramdisk on which to place temporary files during the installation:<br /> bash# mkfs.ext2 /dev/ram0<br /> bash# mount /dev/ram0 /mnt/usbcdrom<br /> bash# cd /mnt/usbcdrom<br /> bash# /usr/bin/wget http://hostname/path/to/m0n0wall<br /> bash# cp /bin/gunzip .<br /> bash# cp /bin/dd .<br /> * Now you're ready. You have created a ramdisk with the two utilities you will need to rewrite IDE disk-on-chip modules with m0n0wall. At this point, if you have modules containing copies of NeoLinux without wget, you should try using them first. That way if something goes wrong you can repeat these steps later. With the machine running, remove the IDE DOC that you booted from and replace it with the one you want to reprogram.<br /> * Then,<br /> gunzip -c m0n0wall-file-name.img | dd of=/dev/hda bs=16k<br /> Ignore the warning about trailing garbage.<br /> <br /> That's it! At this point you can remove the DOC and replace it with another one and repeat the reprogramming step, as many times as needed.<br /> <br /> When you next boot the machine, it should load m0n0wall exactly as it would on any other x86-compatible system. Jump right in with the m0n0wall quick-start guide for PC platforms. Chapter 3: Initial Configuration is probably where you will want to start. Good luck!<br /> <br /> Version 0.3 | Content date: 05 July 2008 | Page last generated: 2009-01-18 13:11 CST</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=Clasxt&diff=5305 2011-05-16T14:43:59Z

<p>129.57.167.199: </p> <hr /> <div>'''Clasxt's''' are mac mini's running MAC OS X.<br /> <br /> '''Initial installation'''<br /> <br /> * connect monitor, ethernet, keyboard and mouse and power up; sometimes it will not recognize keyboard or/and mouse, in that case just unplug mouse/keyboard and plug them back; follow instructions to identify keyboard<br /> <br /> * in '''System preferences/Network''': turn off '''AirPort'''; configure '''Ethernet''' as Manually and type IP address etc<br /> <br /> <br /> <br /> <br /> <br /> '''OBSOLETE'''<br /> <br /> '''Clasxt''' machines are diskless 'thin clients' from neoware, running newlinux. We have 5 those machines still in use:<br /> <br /> * clasxt23<br /> <br /> * clasxt33<br /> <br /> * clasxt35<br /> <br /> * clasxt37<br /> <br /> * clasxt39<br /> <br /> * clasxt40<br /> <br /> To reboot in single user mode do following:<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt should display 'Software'<br /> * Enter ''Software -s ramdisk=12000'' and press enter<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt<br /> <br /> <br /> <br /> '''IMPORTANT:'''<br /> <br /> On clon machines where clasxt's suppose to login, XDM server must be running. On Solaris 10 XDM server is running as part of ''dtlogin''. By default it has following options:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 7799 1 0 17:25:38 ? 0:00 /usr/dt/bin/dtlogin -daemon -udpPort 0<br /> <br /> which means upd connection is not allowed. Looking into options will see following:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> dtlogin/args astring \ -udpPort\ 0<br /> <br /> To change that use following command:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot;\&quot;<br /> <br /> Now that option is gone:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> clon00:/etc&gt;<br /> <br /> To place that option back type following:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot; -udpPort 0\&quot;<br /> <br /> Restart dtlogin server:<br /> <br /> /etc/init.d/dtlogin stop<br /> /etc/init.d/dtlogin start<br /> <br /> Now it is running without upd restriction:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 11503 1 0 17:30:46 ? 0:00 /usr/dt/bin/dtlogin -daemon<br /> <br /> <br /> In addition to that, to make fonts loading process work enable xfs service. Normally it will be enabled on the machines with monitors, but on servers like clon00 and clon10 it will be disabled by default:<br /> <br /> clon00:/etc&gt; svcs -a | grep xfs<br /> disabled Jan_04 svc:/application/x11/xfs:default<br /> clon00:/etc&gt;<br /> <br /> so enable it:<br /> <br /> clon00:/etc&gt; svcadm enable svc:/application/x11/xfs<br /> clon00:/etc&gt; svcs | grep xfs<br /> online 12:55:53 svc:/application/x11/xfs:default<br /> clon00:/etc&gt; <br /> <br /> <br /> <br /> <br /> <br /> Some useful information can be found in following paper:<br /> <br /> Some reports indicate that 3.x builds do not work. The error that is reported is<br /> FATAL ERROR<br /> The device that contains the configuration file (config.xml) could not be found. m0n0wall cannot continue booting.<br /> I do not yet know of a solution. This tutorial should be construed to apply only to the 2.x builds in the meantime. Please email me if you get 3.x working on an EON.<br /> <br /> Here's how to install the latest build of the excellent m0n0wall firewall on a Neoware EON 4000 thin client. These machines make excellent firewalls for home users and small businesses because they are cheap, compact, sturdy, and powerful enough to run a several megabit connection. The hardware is available in a variety of configurations, with CPUs roughly equivalent to a 150-200Mhz Pentium. Before embarking on this little journey, you should be aware of a few caveats:<br /> <br /> * Some Neoware boxes come with a 32-pin Disk-on-Chip module in a socket on the motherboard. m0n0wall does not ship with the required driver to run this module. Therefore, on these systems you will need a hard drive, compact flash to IDE adapter, or similar device to boot from. You may also be able to netboot your firewall (this is supported on the built-in network device), though I do not cover that in this tutorial.<br /> * The motherboard accepts both PC133 DIMMs or SO-DIMMs. It will use both at the same time. However, when using a DIMM, be sure it is less than 1.1&quot; (28mm) tall, or you will not be able to install a second network card.<br /> * There are many different revisions of the NeoLinux operating system and not all include the necessary software to complete this tutorial.<br /> * You may need to purchase several EON 4000s to get suitable software and hardware.<br /> * These instructions were based on NeoLinux 2.4-100802, with kernel 2.2.20. Your particular configuration may vary slightly.<br /> <br /> With those potential issues in mind, follow along!<br /> <br /> There are three main steps to be completed to get m0n0wall running on your EON. First, you will need to get single-user access to the NeoLinux installation. Next, you need to enable networking and fetch and install m0n0wall. Third, you need to configure it to fit your requirements. I will address the first two of these, as adequate resources exist to help with the latter.<br /> <br /> To begin, you will need:<br /> <br /> * One or more Neoware EONs with disk-on-chip modules that plug into the IDE header<br /> * Access to the internet from your EON (or to a web server on a LAN)<br /> * A supported PCI network card. Common Intel or 3Com cards work fine.<br /> * At least 64MB of suitable memory. Some EONs ship with SO-DIMMs, others with DIMMs. These should be short enough to accomodate a PCI network card.<br /> * See the m0n0wall supported hardware page for more information.<br /> <br /> Step ONE: Get single-user access to the NeoLinux distribution.<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt may vary, but pressing tab should display either 'Software' or 'Eon_Software'.<br /> * Enter, as appropriate, either<br /> Software -s ramdisk=12000<br /> or<br /> Eon_Software -s ramdisk=12000<br /> and press enter.<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt.<br /> <br /> Step TWO: Fetch and install m0n0wall.<br /> <br /> * Check that your installation has the necessary software:<br /> bash# ls /usr/bin/wget<br /> . If NeoLinux reports that it is not found, you will have to try a different EON. Keep this hardware however: a single working EON can program m0n0wall onto several disk-on-chip modules, even those without the proper software. More on this later.<br /> * Plug the EON into a network which provides DHCP information and enable the ethernet connection:<br /> bash# cp /etc/sysconfig/network-scripts/ifcfg-eth0.default /etc/sysconfig/network-scripts/ifcfg-eth0<br /> bash# ifup eth0<br /> * Create a ramdisk on which to place temporary files during the installation:<br /> bash# mkfs.ext2 /dev/ram0<br /> bash# mount /dev/ram0 /mnt/usbcdrom<br /> bash# cd /mnt/usbcdrom<br /> bash# /usr/bin/wget http://hostname/path/to/m0n0wall<br /> bash# cp /bin/gunzip .<br /> bash# cp /bin/dd .<br /> * Now you're ready. You have created a ramdisk with the two utilities you will need to rewrite IDE disk-on-chip modules with m0n0wall. At this point, if you have modules containing copies of NeoLinux without wget, you should try using them first. That way if something goes wrong you can repeat these steps later. With the machine running, remove the IDE DOC that you booted from and replace it with the one you want to reprogram.<br /> * Then,<br /> gunzip -c m0n0wall-file-name.img | dd of=/dev/hda bs=16k<br /> Ignore the warning about trailing garbage.<br /> <br /> That's it! At this point you can remove the DOC and replace it with another one and repeat the reprogramming step, as many times as needed.<br /> <br /> When you next boot the machine, it should load m0n0wall exactly as it would on any other x86-compatible system. Jump right in with the m0n0wall quick-start guide for PC platforms. Chapter 3: Initial Configuration is probably where you will want to start. Good luck!<br /> <br /> Version 0.3 | Content date: 05 July 2008 | Page last generated: 2009-01-18 13:11 CST</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=Clasxt&diff=5304 2011-05-16T14:38:31Z

<p>129.57.167.199: </p> <hr /> <div>'''Clasxt's''' are mac mini's running MAC OS X.<br /> <br /> '''Initial installation'''<br /> <br /> * <br /> <br /> <br /> <br /> <br /> <br /> '''OBSOLETE'''<br /> <br /> '''Clasxt''' machines are diskless 'thin clients' from neoware, running newlinux. We have 5 those machines still in use:<br /> <br /> * clasxt23<br /> <br /> * clasxt33<br /> <br /> * clasxt35<br /> <br /> * clasxt37<br /> <br /> * clasxt39<br /> <br /> * clasxt40<br /> <br /> To reboot in single user mode do following:<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt should display 'Software'<br /> * Enter ''Software -s ramdisk=12000'' and press enter<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt<br /> <br /> <br /> <br /> '''IMPORTANT:'''<br /> <br /> On clon machines where clasxt's suppose to login, XDM server must be running. On Solaris 10 XDM server is running as part of ''dtlogin''. By default it has following options:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 7799 1 0 17:25:38 ? 0:00 /usr/dt/bin/dtlogin -daemon -udpPort 0<br /> <br /> which means upd connection is not allowed. Looking into options will see following:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> dtlogin/args astring \ -udpPort\ 0<br /> <br /> To change that use following command:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot;\&quot;<br /> <br /> Now that option is gone:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> clon00:/etc&gt;<br /> <br /> To place that option back type following:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot; -udpPort 0\&quot;<br /> <br /> Restart dtlogin server:<br /> <br /> /etc/init.d/dtlogin stop<br /> /etc/init.d/dtlogin start<br /> <br /> Now it is running without upd restriction:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 11503 1 0 17:30:46 ? 0:00 /usr/dt/bin/dtlogin -daemon<br /> <br /> <br /> In addition to that, to make fonts loading process work enable xfs service. Normally it will be enabled on the machines with monitors, but on servers like clon00 and clon10 it will be disabled by default:<br /> <br /> clon00:/etc&gt; svcs -a | grep xfs<br /> disabled Jan_04 svc:/application/x11/xfs:default<br /> clon00:/etc&gt;<br /> <br /> so enable it:<br /> <br /> clon00:/etc&gt; svcadm enable svc:/application/x11/xfs<br /> clon00:/etc&gt; svcs | grep xfs<br /> online 12:55:53 svc:/application/x11/xfs:default<br /> clon00:/etc&gt; <br /> <br /> <br /> <br /> <br /> <br /> Some useful information can be found in following paper:<br /> <br /> Some reports indicate that 3.x builds do not work. The error that is reported is<br /> FATAL ERROR<br /> The device that contains the configuration file (config.xml) could not be found. m0n0wall cannot continue booting.<br /> I do not yet know of a solution. This tutorial should be construed to apply only to the 2.x builds in the meantime. Please email me if you get 3.x working on an EON.<br /> <br /> Here's how to install the latest build of the excellent m0n0wall firewall on a Neoware EON 4000 thin client. These machines make excellent firewalls for home users and small businesses because they are cheap, compact, sturdy, and powerful enough to run a several megabit connection. The hardware is available in a variety of configurations, with CPUs roughly equivalent to a 150-200Mhz Pentium. Before embarking on this little journey, you should be aware of a few caveats:<br /> <br /> * Some Neoware boxes come with a 32-pin Disk-on-Chip module in a socket on the motherboard. m0n0wall does not ship with the required driver to run this module. Therefore, on these systems you will need a hard drive, compact flash to IDE adapter, or similar device to boot from. You may also be able to netboot your firewall (this is supported on the built-in network device), though I do not cover that in this tutorial.<br /> * The motherboard accepts both PC133 DIMMs or SO-DIMMs. It will use both at the same time. However, when using a DIMM, be sure it is less than 1.1&quot; (28mm) tall, or you will not be able to install a second network card.<br /> * There are many different revisions of the NeoLinux operating system and not all include the necessary software to complete this tutorial.<br /> * You may need to purchase several EON 4000s to get suitable software and hardware.<br /> * These instructions were based on NeoLinux 2.4-100802, with kernel 2.2.20. Your particular configuration may vary slightly.<br /> <br /> With those potential issues in mind, follow along!<br /> <br /> There are three main steps to be completed to get m0n0wall running on your EON. First, you will need to get single-user access to the NeoLinux installation. Next, you need to enable networking and fetch and install m0n0wall. Third, you need to configure it to fit your requirements. I will address the first two of these, as adequate resources exist to help with the latter.<br /> <br /> To begin, you will need:<br /> <br /> * One or more Neoware EONs with disk-on-chip modules that plug into the IDE header<br /> * Access to the internet from your EON (or to a web server on a LAN)<br /> * A supported PCI network card. Common Intel or 3Com cards work fine.<br /> * At least 64MB of suitable memory. Some EONs ship with SO-DIMMs, others with DIMMs. These should be short enough to accomodate a PCI network card.<br /> * See the m0n0wall supported hardware page for more information.<br /> <br /> Step ONE: Get single-user access to the NeoLinux distribution.<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt may vary, but pressing tab should display either 'Software' or 'Eon_Software'.<br /> * Enter, as appropriate, either<br /> Software -s ramdisk=12000<br /> or<br /> Eon_Software -s ramdisk=12000<br /> and press enter.<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt.<br /> <br /> Step TWO: Fetch and install m0n0wall.<br /> <br /> * Check that your installation has the necessary software:<br /> bash# ls /usr/bin/wget<br /> . If NeoLinux reports that it is not found, you will have to try a different EON. Keep this hardware however: a single working EON can program m0n0wall onto several disk-on-chip modules, even those without the proper software. More on this later.<br /> * Plug the EON into a network which provides DHCP information and enable the ethernet connection:<br /> bash# cp /etc/sysconfig/network-scripts/ifcfg-eth0.default /etc/sysconfig/network-scripts/ifcfg-eth0<br /> bash# ifup eth0<br /> * Create a ramdisk on which to place temporary files during the installation:<br /> bash# mkfs.ext2 /dev/ram0<br /> bash# mount /dev/ram0 /mnt/usbcdrom<br /> bash# cd /mnt/usbcdrom<br /> bash# /usr/bin/wget http://hostname/path/to/m0n0wall<br /> bash# cp /bin/gunzip .<br /> bash# cp /bin/dd .<br /> * Now you're ready. You have created a ramdisk with the two utilities you will need to rewrite IDE disk-on-chip modules with m0n0wall. At this point, if you have modules containing copies of NeoLinux without wget, you should try using them first. That way if something goes wrong you can repeat these steps later. With the machine running, remove the IDE DOC that you booted from and replace it with the one you want to reprogram.<br /> * Then,<br /> gunzip -c m0n0wall-file-name.img | dd of=/dev/hda bs=16k<br /> Ignore the warning about trailing garbage.<br /> <br /> That's it! At this point you can remove the DOC and replace it with another one and repeat the reprogramming step, as many times as needed.<br /> <br /> When you next boot the machine, it should load m0n0wall exactly as it would on any other x86-compatible system. Jump right in with the m0n0wall quick-start guide for PC platforms. Chapter 3: Initial Configuration is probably where you will want to start. Good luck!<br /> <br /> Version 0.3 | Content date: 05 July 2008 | Page last generated: 2009-01-18 13:11 CST</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=Clasxt&diff=5303 2011-05-16T14:38:21Z

<p>129.57.167.199: </p> <hr /> <div>'''Clasxt's''' are mac mini's running MAC OS X.<br /> <br /> '''Initial installation'''<br /> <br /> * <br /> <br /> <br /> '''OBSOLETE'''<br /> <br /> '''Clasxt''' machines are diskless 'thin clients' from neoware, running newlinux. We have 5 those machines still in use:<br /> <br /> * clasxt23<br /> <br /> * clasxt33<br /> <br /> * clasxt35<br /> <br /> * clasxt37<br /> <br /> * clasxt39<br /> <br /> * clasxt40<br /> <br /> To reboot in single user mode do following:<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt should display 'Software'<br /> * Enter ''Software -s ramdisk=12000'' and press enter<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt<br /> <br /> <br /> <br /> '''IMPORTANT:'''<br /> <br /> On clon machines where clasxt's suppose to login, XDM server must be running. On Solaris 10 XDM server is running as part of ''dtlogin''. By default it has following options:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 7799 1 0 17:25:38 ? 0:00 /usr/dt/bin/dtlogin -daemon -udpPort 0<br /> <br /> which means upd connection is not allowed. Looking into options will see following:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> dtlogin/args astring \ -udpPort\ 0<br /> <br /> To change that use following command:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot;\&quot;<br /> <br /> Now that option is gone:<br /> <br /> clon00:/etc&gt; svcprop svc:/application/graphical-login/cde-login | grep udpPort<br /> clon00:/etc&gt;<br /> <br /> To place that option back type following:<br /> <br /> clon00:/etc&gt; svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\&quot; -udpPort 0\&quot;<br /> <br /> Restart dtlogin server:<br /> <br /> /etc/init.d/dtlogin stop<br /> /etc/init.d/dtlogin start<br /> <br /> Now it is running without upd restriction:<br /> <br /> clon00:/etc&gt; ps -ef | grep dtlogin<br /> root 11503 1 0 17:30:46 ? 0:00 /usr/dt/bin/dtlogin -daemon<br /> <br /> <br /> In addition to that, to make fonts loading process work enable xfs service. Normally it will be enabled on the machines with monitors, but on servers like clon00 and clon10 it will be disabled by default:<br /> <br /> clon00:/etc&gt; svcs -a | grep xfs<br /> disabled Jan_04 svc:/application/x11/xfs:default<br /> clon00:/etc&gt;<br /> <br /> so enable it:<br /> <br /> clon00:/etc&gt; svcadm enable svc:/application/x11/xfs<br /> clon00:/etc&gt; svcs | grep xfs<br /> online 12:55:53 svc:/application/x11/xfs:default<br /> clon00:/etc&gt; <br /> <br /> <br /> <br /> <br /> <br /> Some useful information can be found in following paper:<br /> <br /> Some reports indicate that 3.x builds do not work. The error that is reported is<br /> FATAL ERROR<br /> The device that contains the configuration file (config.xml) could not be found. m0n0wall cannot continue booting.<br /> I do not yet know of a solution. This tutorial should be construed to apply only to the 2.x builds in the meantime. Please email me if you get 3.x working on an EON.<br /> <br /> Here's how to install the latest build of the excellent m0n0wall firewall on a Neoware EON 4000 thin client. These machines make excellent firewalls for home users and small businesses because they are cheap, compact, sturdy, and powerful enough to run a several megabit connection. The hardware is available in a variety of configurations, with CPUs roughly equivalent to a 150-200Mhz Pentium. Before embarking on this little journey, you should be aware of a few caveats:<br /> <br /> * Some Neoware boxes come with a 32-pin Disk-on-Chip module in a socket on the motherboard. m0n0wall does not ship with the required driver to run this module. Therefore, on these systems you will need a hard drive, compact flash to IDE adapter, or similar device to boot from. You may also be able to netboot your firewall (this is supported on the built-in network device), though I do not cover that in this tutorial.<br /> * The motherboard accepts both PC133 DIMMs or SO-DIMMs. It will use both at the same time. However, when using a DIMM, be sure it is less than 1.1&quot; (28mm) tall, or you will not be able to install a second network card.<br /> * There are many different revisions of the NeoLinux operating system and not all include the necessary software to complete this tutorial.<br /> * You may need to purchase several EON 4000s to get suitable software and hardware.<br /> * These instructions were based on NeoLinux 2.4-100802, with kernel 2.2.20. Your particular configuration may vary slightly.<br /> <br /> With those potential issues in mind, follow along!<br /> <br /> There are three main steps to be completed to get m0n0wall running on your EON. First, you will need to get single-user access to the NeoLinux installation. Next, you need to enable networking and fetch and install m0n0wall. Third, you need to configure it to fit your requirements. I will address the first two of these, as adequate resources exist to help with the latter.<br /> <br /> To begin, you will need:<br /> <br /> * One or more Neoware EONs with disk-on-chip modules that plug into the IDE header<br /> * Access to the internet from your EON (or to a web server on a LAN)<br /> * A supported PCI network card. Common Intel or 3Com cards work fine.<br /> * At least 64MB of suitable memory. Some EONs ship with SO-DIMMs, others with DIMMs. These should be short enough to accomodate a PCI network card.<br /> * See the m0n0wall supported hardware page for more information.<br /> <br /> Step ONE: Get single-user access to the NeoLinux distribution.<br /> <br /> * Power on the EON and hold the left shift key down until you are shown a boot prompt<br /> * The boot prompt may vary, but pressing tab should display either 'Software' or 'Eon_Software'.<br /> * Enter, as appropriate, either<br /> Software -s ramdisk=12000<br /> or<br /> Eon_Software -s ramdisk=12000<br /> and press enter.<br /> * As the OS boots, press alt-F2 (possibly more than once) until you are greeted with a bash prompt.<br /> <br /> Step TWO: Fetch and install m0n0wall.<br /> <br /> * Check that your installation has the necessary software:<br /> bash# ls /usr/bin/wget<br /> . If NeoLinux reports that it is not found, you will have to try a different EON. Keep this hardware however: a single working EON can program m0n0wall onto several disk-on-chip modules, even those without the proper software. More on this later.<br /> * Plug the EON into a network which provides DHCP information and enable the ethernet connection:<br /> bash# cp /etc/sysconfig/network-scripts/ifcfg-eth0.default /etc/sysconfig/network-scripts/ifcfg-eth0<br /> bash# ifup eth0<br /> * Create a ramdisk on which to place temporary files during the installation:<br /> bash# mkfs.ext2 /dev/ram0<br /> bash# mount /dev/ram0 /mnt/usbcdrom<br /> bash# cd /mnt/usbcdrom<br /> bash# /usr/bin/wget http://hostname/path/to/m0n0wall<br /> bash# cp /bin/gunzip .<br /> bash# cp /bin/dd .<br /> * Now you're ready. You have created a ramdisk with the two utilities you will need to rewrite IDE disk-on-chip modules with m0n0wall. At this point, if you have modules containing copies of NeoLinux without wget, you should try using them first. That way if something goes wrong you can repeat these steps later. With the machine running, remove the IDE DOC that you booted from and replace it with the one you want to reprogram.<br /> * Then,<br /> gunzip -c m0n0wall-file-name.img | dd of=/dev/hda bs=16k<br /> Ignore the warning about trailing garbage.<br /> <br /> That's it! At this point you can remove the DOC and replace it with another one and repeat the reprogramming step, as many times as needed.<br /> <br /> When you next boot the machine, it should load m0n0wall exactly as it would on any other x86-compatible system. Jump right in with the m0n0wall quick-start guide for PC platforms. Chapter 3: Initial Configuration is probably where you will want to start. Good luck!<br /> <br /> Version 0.3 | Content date: 05 July 2008 | Page last generated: 2009-01-18 13:11 CST</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=GE_XVB601&diff=5188 2011-03-29T19:18:11Z

<p>129.57.167.199: </p> <hr /> <div>Company site: [http://www.ge-ip.com/products/family/embedded-systems GE Intelligent Platforms]<br /> <br /> Board page on company site: [http://www.ge-ip.com/products/3448 XVB601]<br /> <br /> Documentation: <br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_xvb601_ds_gfa1299.pdf Datasheet]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_xvb601_hr_500-930007815-000_E.pdf Hardware Reference]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_522-9300800627-000_A.book.pdf Installation Guide]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_Configuration_Guide_XVB601.pdf Product Configurations]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_Ruggedization_Levels_GFA-926a.pdf Ruggedization]<br /> <br /> == Customization for the CLON cluster ==<br /> <br /> '''List of boards'''<br /> <br /> * [01] 00:20:38:04:23:5E / 129.57.68.89 / croctest2<br /> <br /> '''Customizing kernel installed on the FLASH'''<br /> <br /> * ''/usr/bin/system-config-network''<br /> <br /> * fix ''/etc/passwd'', ''/etc/shadow'', ''/etc/group''<br /> <br /> * fix ''/etc/nsswitch.conf''<br /> <br /> * fix ''/etc/yp.conf'' (add lines ''domain CCCHP server clon00.jlab.org'' and ''ypserver clon10.jlab.org'')<br /> <br /> * fix ''/etc/sysconfig/network'' (add line ''NISDOMAIN=CCCHP'')<br /> <br /> * ''/etc/init.d/ypbind start''<br /> <br /> * ''chkconfig ypbind on''<br /> <br /> <br /> * set RHEL-style [[automounts]]<br /> <br /> * ''/etc/init.d/autofs restart''<br /> <br /> * fix symbolic links to /apps, /home, /usr/local etc<br /> <br /> <br /> <br /> '''Trying netboot following Bryan's instructions, using clonpc3'''<br /> <br /> * ''yum install system-config-netboot''<br /> <br /> * Change line (&lt;code&gt;/etc/xinetd.d/tftp&lt;/code&gt;):<br /> disable = yes<br /> : To<br /> disable = no<br /> <br /> * ''service xinetd restart''<br /> <br /> * Add these entries to &lt;code&gt;/etc/exports&lt;/code&gt;<br /> /diskless/x86_64/Centos5.5/root/ 129.57.167.0/255.255.255.0(ro,sync,no_root_squash)<br /> /diskless/x86_64/Centos5.5/snapshot/ 129.57.167.0/255.255.255.0(rw,sync,no_root_squash)<br /> : Where the &lt;code&gt;129.57.167.0/255.255.255.0&lt;/code&gt; only allows the 167 subnet to access these mounts.<br /> <br /> * Reload the NFS configuration or start NFS, if it's not started<br /> ''service nfs reload''<br /> <br /> * Make sure NFS is started at boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> * Enable remote syslog (optional)<br /> <br /> Change syslog argument in &lt;code&gt;/etc/sysconfig/syslog&lt;/code&gt; from:<br /> SYSLOGD_OPTIONS=&quot;-m 0&quot;<br /> :: To<br /> SYSLOGD_OPTIONS=&quot;-m 0 -r&quot;<br /> <br /> Restart syslogd<br /> service syslog restart<br /> <br /> '''DHCP Server Setup'''<br /> On the machine hosting the DHCP server.<br /> <br /> * Add an entry in &lt;code&gt;/etc/dhcpd.conf&lt;/code&gt;:<br /> &lt;pre&gt;<br /> host dafarm44<br /> {<br /> filename &quot;linux-install/pxelinux.0&quot;; # File location relative to /tftpboot/<br /> next-server 129.57.29.38; # TFTP server<br /> hardware ethernet 00:20:38:03:D8:52; # Client MAC<br /> fixed-address 129.57.29.54; # Client IP<br /> }<br /> &lt;/pre&gt;<br /> <br /> * Restart dhcpd<br /> service dhcpd restart<br /> <br /> '''Configure Client OS'''<br /> <br /> Here, we configure the OS that each and every Diskless Client will enjoy.<br /> <br /> '''Setup of Diskless Kernel'''<br /> Run system-config-netboot (on TFTP server):<br /> system-config-netboot<br /> <br /> * In &quot;First Time Druid&quot; window. Click on &quot;Diskless&quot;<br /> # Click &quot;Forward&quot; on first page<br /> # Enter Name and Description.<br /> # Enter IP address of TFTP server and the &quot;root&quot; directory exported via NFS<br /> # Select a kernel<br /> # Click on Apply.<br /> : This will take a minute or two to compile a boot kernel for the diskless client.<br /> <br /> '''Setup of chroot environment'''<br /> There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br /> This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br /> chroot /diskless/x86_64/Centos5.5/root<br /> mount /proc /proc -t proc<br /> mkdir /u <br /> mkdir /group<br /> mkdir /daqfs<br /> mv /home /home.old<br /> ln -s /u/apps /apps<br /> ln -s /u/site /site<br /> ln -s /daqfs/home /home<br /> <br /> '''Setup of diskless system configurations'''<br /> <br /> ''' Which NFS directories to mount '''<br /> <br /> * Add entry to &lt;code&gt;/etc/fstab&lt;/code&gt;<br /> phecda:/raid /daqfs nfs rw,soft,intr 0 0<br /> <br /> * Mount daqfs<br /> mount /daqfs<br /> <br /> ''' Which users/groups to allow access '''<br /> * Add entries to /etc/passwd<br /> +@da::::::<br /> +@ccc::::::<br /> +::::::/bin/false<br /> <br /> ''' A proxy for yum ''' (may be optional)<br /> * Add entry to /etc/yum.conf<br /> proxy=http://jprox:8080<br /> <br /> ''' domain servers for ypbind '''<br /> * Add entries to /etc/yp.conf<br /> domain CCCHP server nis2.jlab.org<br /> domain CCCHP server nis3.jlab.org<br /> <br /> * Make sure ypbind started at boot<br /> /sbin/chkconfig --level 345 nfs on <br /> <br /> ''' NTP setup ''' (optional... ntp must be installed)<br /> * Add entries to &lt;code&gt;/etc/ntp.conf&lt;/code&gt;<br /> server 127.0.0.1 # local clock<br /> fudge 127.0.0.1 stratum 10<br /> server ntp1.jlab.org<br /> server ntp2.jlab.org<br /> driftfile /etc/ntp/drift<br /> broadcastdelay 0.008<br /> authenticate no<br /> <br /> ''' Some additional JLab CUE directories to mount '''<br /> * Add entries to &lt;code&gt;/etc/auto.master&lt;/code&gt;<br /> /group /etc/auto.group --timeout=0<br /> /u auto.u.bb --DOSNAME=Linux-RHEL5<br /> <br /> ''' Additional files, not included in the standard diskless filesystem '''<br /> * Add a new file &lt;code&gt;/diskless/x86_64/Centos5.5/snapshot/files.custom&lt;/code&gt;. Entry:<br /> /tmp/<br /> /etc/minirc.dfl<br /> <br /> ''' Configure a NEW diskless client '''<br /> This operation must be peformed to add a new Diskless Client. <br /> <br /> ''' Configuration on the tftp/NFS server '''<br /> * In &lt;code&gt;system-config-netboot&lt;/code&gt; &quot;Network Installation and Diskless Environment&quot; window:<br /> # Click on &quot;New&quot;<br /> # Enter hostname<br /> # Select OS<br /> # Enter &quot;CCCHP&quot; in Enable NISDOMAIN box.<br /> # Enter options in &quot;Edit Extra Kernel Boot Options&quot; &lt;br /&gt; &lt;code&gt;vga=0x305 acpi=force&lt;/code&gt;<br /> # Enter hostname as snapshot name. Make sure &quot;generate&quot; is check-marked<br /> # Click &quot;OK&quot;<br /> <br /> ''' Configuration on the Diskless Client '''<br /> * PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br /> <br /> ''' Other useful packages to install '''<br /> Later on... I installed some other useful packages using the chroot environment. Here they are:<br /> <br /> * &lt;code&gt;xorg-x11-xauth&lt;/code&gt; - Required to run X-applications remotely<br /> * &lt;code&gt;ntp&lt;/code&gt; - Synchronize system clock with a central server<br /> : To Execute &lt;code&gt;ntpdate&lt;/code&gt; on server startup:<br /> :* Add &lt;code&gt;&lt;b&gt;-x&lt;/b&gt;&lt;/code&gt; to &lt;code&gt;OPTIONS&lt;/code&gt; in<br /> /etc/sysconfig/ntpd<br /> :* Make sure it starts on boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> == Network-based booting ==<br /> <br /> The page is geared towards the setup of Diskless nodes for Intel-based VME Controllers, but may be useful for similar other applications. Much of what is here was derived from the [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/3/html/System_Administration_Guide/ch-diskless.html Redhat Enterprise Linux 3 Documentation].<br /> <br /> This examples assumes:<br /> * The DHCP server (phecda: 129.57.29.104) has been installed and works. Here we're using the dhcp 3.0.1 package distributed by RHEL4.<br /> * The TFTP and NFS server (mizar: 129.57.29.100) is running RHEL5.5 x86_64.<br /> * The Diskless Client (dafarm44: 129.57.29.54) will run Centos 5.5 x86_64.<br /> <br /> There's nothing stopping you from having the DHCP server on the same machine as that servering TFTP and NFS. You can obviously have more than one diskless client.<br /> <br /> Once the first four steps have been completed, new clients can be configured individually with step 5.<br /> <br /> = Client Setup of OS in VirtualBox =<br /> Here, we've downloaded the latest and greatest Centos 5.5 x86_64 ISO and have set up a VirtualBox Client to use it to boot. We will not attempt to describe the VirtualBox installation or Setup of the ISO to boot as the VirtualBox Guest.<br /> <br /> The Centos 5.5 installation proceeds as normal installations go, but we opt to do a minimal installation (excluding KDE and/or GNOME components) since we're running on a VME controller. Other packages will be installed after first boot.<br /> <br /> === First Boot ===<br /> At first boot (after installation), a UI will appear and provide you with some options.:<br /> * Disable firewall and SELinux. SELinux setup can be double checked in the file:<br /> /etc/selinux/config<br /> * Disable sendmail, and other services not required for a VME controller<br /> <br /> === Update packages and transfer the OS to Server ===<br /> Login as root<br /> * Update all installed packages:<br /> yum update<br /> * Install the following packages, with:<br /> yum install &lt;i&gt;package&lt;/i&gt;<br /> :: busybox-anaconda<br /> :: gcc<br /> :: kernel-devel<br /> :: gdb<br /> :: valgrind<br /> :: cvs<br /> :: subversion<br /> :: compat-libstdc++-33<br /> :: redhat-rpm-config<br /> <br /> * Copy the Client OS to the tftp/NFS Server.<br /> ** On The Server:<br /> mkdir -p /diskless/x86_64/Centos5.5/root<br /> : In The VirtualBox Guest:<br /> rsync -Pav -e ssh --exclude='/proc/*' --exclude='/sys/*' / mizar:/diskless/x86_64/Centos5.5/root/<br /> <br /> You are now done with the Centos5.5 Guest installed in the VirtualBox. It can be closed down now.<br /> <br /> = tftp and NFS Server Setup =<br /> Follow these steps on the machine serving out tftp and NFS:<br /> <br /> ===Install &lt;code&gt;system-config-netboot&lt;/code&gt; ===<br /> (This should automatically install the tftp server)<br /> yum install system-config-netboot<br /> <br /> === Enable the tftp server to start at boot ===<br /> * Change line (&lt;code&gt;/etc/xinetd.d/tftp&lt;/code&gt;):<br /> disable = yes<br /> : To<br /> disable = no<br /> <br /> * Restart &lt;code&gt;xinetd&lt;/code&gt;<br /> service xinetd restart<br /> <br /> === Configure NFS ===<br /> * Add these entries to &lt;code&gt;/etc/exports&lt;/code&gt;<br /> /diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br /> /diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br /> : Where the &lt;code&gt;129.57.29.0/255.255.255.0&lt;/code&gt; only allows the 29 subnet to access these mounts.<br /> <br /> * Reload the NFS configuration or start NFS, if it's not started<br /> service nfs reload<br /> <br /> * Make sure NFS is started at boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> === Enable remote syslog (optional) ===<br /> * Change syslog argument in &lt;code&gt;/etc/sysconfig/syslog&lt;/code&gt; from:<br /> SYSLOGD_OPTIONS=&quot;-m 0&quot;<br /> :: To<br /> SYSLOGD_OPTIONS=&quot;-m 0 -r&quot;<br /> <br /> * Restart syslogd<br /> service syslog restart<br /> <br /> = DHCP Server Setup =<br /> On the machine hosting the DHCP server.<br /> <br /> * Add an entry in &lt;code&gt;/etc/dhcpd.conf&lt;/code&gt;:<br /> &lt;pre&gt;<br /> host dafarm44<br /> {<br /> filename &quot;linux-install/pxelinux.0&quot;; # File location relative to /tftpboot/<br /> next-server 129.57.29.38; # TFTP server<br /> hardware ethernet 00:20:38:03:D8:52; # Client MAC<br /> fixed-address 129.57.29.54; # Client IP<br /> }<br /> &lt;/pre&gt;<br /> <br /> * Restart dhcpd<br /> service dhcpd restart<br /> <br /> = Configure Client OS =<br /> <br /> Here, we configure the OS that each and every Diskless Client will enjoy.<br /> <br /> === Setup of Diskless Kernel ===<br /> Run system-config-netboot (on TFTP server):<br /> system-config-netboot<br /> <br /> * In &quot;First Time Druid&quot; window. Click on &quot;Diskless&quot;<br /> # Click &quot;Forward&quot; on first page<br /> # Enter Name and Description.<br /> # Enter IP address of TFTP server and the &quot;root&quot; directory exported via NFS<br /> # Select a kernel<br /> # Click on Apply.<br /> : This will take a minute or two to compile a boot kernel for the diskless client.<br /> <br /> === Setup of chroot environment === <br /> There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br /> This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br /> chroot /diskless/x86_64/Centos5.5/root<br /> mount /proc /proc -t proc<br /> mkdir /u <br /> mkdir /group<br /> mkdir /daqfs<br /> mv /home /home.old<br /> ln -s /u/apps /apps<br /> ln -s /u/site /site<br /> ln -s /daqfs/home /home<br /> <br /> === Setup of diskless system configurations ===<br /> ''' Which NFS directories to mount '''<br /> * Add entry to &lt;code&gt;/etc/fstab&lt;/code&gt;<br /> phecda:/raid /daqfs nfs rw,soft,intr 0 0<br /> <br /> * Mount daqfs<br /> mount /daqfs<br /> <br /> ''' Which users/groups to allow access '''<br /> * Add entries to /etc/passwd<br /> +@da::::::<br /> +@ccc::::::<br /> +::::::/bin/false<br /> <br /> ''' A proxy for yum ''' (may be optional)<br /> * Add entry to /etc/yum.conf<br /> proxy=http://jprox:8080<br /> <br /> ''' domain servers for ypbind '''<br /> * Add entries to /etc/yp.conf<br /> domain CCCHP server nis2.jlab.org<br /> domain CCCHP server nis3.jlab.org<br /> <br /> * Make sure ypbind started at boot<br /> /sbin/chkconfig --level 345 nfs on <br /> <br /> ''' NTP setup ''' (optional... ntp must be installed)<br /> * Add entries to &lt;code&gt;/etc/ntp.conf&lt;/code&gt;<br /> server 127.0.0.1 # local clock<br /> fudge 127.0.0.1 stratum 10<br /> server ntp1.jlab.org<br /> server ntp2.jlab.org<br /> driftfile /etc/ntp/drift<br /> broadcastdelay 0.008<br /> authenticate no<br /> <br /> ''' Some additional JLab CUE directories to mount '''<br /> * Add entries to &lt;code&gt;/etc/auto.master&lt;/code&gt;<br /> /group /etc/auto.group --timeout=0<br /> /u auto.u.bb --DOSNAME=Linux-RHEL5<br /> <br /> ''' Additional files, not included in the standard diskless filesystem '''<br /> * Add a new file &lt;code&gt;/diskless/x86_64/Centos5.5/snapshot/files.custom&lt;/code&gt;. Entry:<br /> /tmp/<br /> /etc/minirc.dfl<br /> <br /> = Configure a NEW diskless client =<br /> This operation must be peformed to add a new Diskless Client. <br /> <br /> === Configuration on the tftp/NFS server ===<br /> * In &lt;code&gt;system-config-netboot&lt;/code&gt; &quot;Network Installation and Diskless Environment&quot; window:<br /> # Click on &quot;New&quot;<br /> # Enter hostname<br /> # Select OS<br /> # Enter &quot;CCCHP&quot; in Enable NISDOMAIN box.<br /> # Enter options in &quot;Edit Extra Kernel Boot Options&quot; &lt;br /&gt; &lt;code&gt;vga=0x305 acpi=force&lt;/code&gt;<br /> # Enter hostname as snapshot name. Make sure &quot;generate&quot; is check-marked<br /> # Click &quot;OK&quot;<br /> <br /> === Configuration on the Diskless Client ===<br /> * PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br /> <br /> = Other useful packages to install =<br /> Later on... I installed some other useful packages using the chroot environment. Here they are:<br /> <br /> * &lt;code&gt;xorg-x11-xauth&lt;/code&gt; - Required to run X-applications remotely<br /> * &lt;code&gt;ntp&lt;/code&gt; - Synchronize system clock with a central server<br /> : To Execute &lt;code&gt;ntpdate&lt;/code&gt; on server startup:<br /> :* Add &lt;code&gt;&lt;b&gt;-x&lt;/b&gt;&lt;/code&gt; to &lt;code&gt;OPTIONS&lt;/code&gt; in<br /> /etc/sysconfig/ntpd<br /> :* Make sure it starts on boot<br /> /sbin/chkconfig --level 345 nfs on</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=GE_XVB601&diff=5187 2011-03-29T19:17:01Z

<p>129.57.167.199: </p> <hr /> <div>Company site: [http://www.ge-ip.com/products/family/embedded-systems GE Intelligent Platforms]<br /> <br /> Board page on company site: [http://www.ge-ip.com/products/3448 XVB601]<br /> <br /> Documentation: <br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_xvb601_ds_gfa1299.pdf Datasheet]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_xvb601_hr_500-930007815-000_E.pdf Hardware Reference]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_522-9300800627-000_A.book.pdf Installation Guide]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_Configuration_Guide_XVB601.pdf Sales Options]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_Ruggedization_Levels_GFA-926a.pdf Ruggedization]<br /> <br /> == Customization for the CLON cluster ==<br /> <br /> '''List of boards'''<br /> <br /> * [01] 00:20:38:04:23:5E / 129.57.68.89 / croctest2<br /> <br /> '''Customizing kernel installed on the FLASH'''<br /> <br /> * ''/usr/bin/system-config-network''<br /> <br /> * fix ''/etc/passwd'', ''/etc/shadow'', ''/etc/group''<br /> <br /> * fix ''/etc/nsswitch.conf''<br /> <br /> * fix ''/etc/yp.conf'' (add lines ''domain CCCHP server clon00.jlab.org'' and ''ypserver clon10.jlab.org'')<br /> <br /> * fix ''/etc/sysconfig/network'' (add line ''NISDOMAIN=CCCHP'')<br /> <br /> * ''/etc/init.d/ypbind start''<br /> <br /> * ''chkconfig ypbind on''<br /> <br /> <br /> * set RHEL-style [[automounts]]<br /> <br /> * ''/etc/init.d/autofs restart''<br /> <br /> * fix symbolic links to /apps, /home, /usr/local etc<br /> <br /> <br /> <br /> '''Trying netboot following Bryan's instructions, using clonpc3'''<br /> <br /> * ''yum install system-config-netboot''<br /> <br /> * Change line (&lt;code&gt;/etc/xinetd.d/tftp&lt;/code&gt;):<br /> disable = yes<br /> : To<br /> disable = no<br /> <br /> * ''service xinetd restart''<br /> <br /> * Add these entries to &lt;code&gt;/etc/exports&lt;/code&gt;<br /> /diskless/x86_64/Centos5.5/root/ 129.57.167.0/255.255.255.0(ro,sync,no_root_squash)<br /> /diskless/x86_64/Centos5.5/snapshot/ 129.57.167.0/255.255.255.0(rw,sync,no_root_squash)<br /> : Where the &lt;code&gt;129.57.167.0/255.255.255.0&lt;/code&gt; only allows the 167 subnet to access these mounts.<br /> <br /> * Reload the NFS configuration or start NFS, if it's not started<br /> ''service nfs reload''<br /> <br /> * Make sure NFS is started at boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> * Enable remote syslog (optional)<br /> <br /> Change syslog argument in &lt;code&gt;/etc/sysconfig/syslog&lt;/code&gt; from:<br /> SYSLOGD_OPTIONS=&quot;-m 0&quot;<br /> :: To<br /> SYSLOGD_OPTIONS=&quot;-m 0 -r&quot;<br /> <br /> Restart syslogd<br /> service syslog restart<br /> <br /> '''DHCP Server Setup'''<br /> On the machine hosting the DHCP server.<br /> <br /> * Add an entry in &lt;code&gt;/etc/dhcpd.conf&lt;/code&gt;:<br /> &lt;pre&gt;<br /> host dafarm44<br /> {<br /> filename &quot;linux-install/pxelinux.0&quot;; # File location relative to /tftpboot/<br /> next-server 129.57.29.38; # TFTP server<br /> hardware ethernet 00:20:38:03:D8:52; # Client MAC<br /> fixed-address 129.57.29.54; # Client IP<br /> }<br /> &lt;/pre&gt;<br /> <br /> * Restart dhcpd<br /> service dhcpd restart<br /> <br /> '''Configure Client OS'''<br /> <br /> Here, we configure the OS that each and every Diskless Client will enjoy.<br /> <br /> '''Setup of Diskless Kernel'''<br /> Run system-config-netboot (on TFTP server):<br /> system-config-netboot<br /> <br /> * In &quot;First Time Druid&quot; window. Click on &quot;Diskless&quot;<br /> # Click &quot;Forward&quot; on first page<br /> # Enter Name and Description.<br /> # Enter IP address of TFTP server and the &quot;root&quot; directory exported via NFS<br /> # Select a kernel<br /> # Click on Apply.<br /> : This will take a minute or two to compile a boot kernel for the diskless client.<br /> <br /> '''Setup of chroot environment'''<br /> There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br /> This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br /> chroot /diskless/x86_64/Centos5.5/root<br /> mount /proc /proc -t proc<br /> mkdir /u <br /> mkdir /group<br /> mkdir /daqfs<br /> mv /home /home.old<br /> ln -s /u/apps /apps<br /> ln -s /u/site /site<br /> ln -s /daqfs/home /home<br /> <br /> '''Setup of diskless system configurations'''<br /> <br /> ''' Which NFS directories to mount '''<br /> <br /> * Add entry to &lt;code&gt;/etc/fstab&lt;/code&gt;<br /> phecda:/raid /daqfs nfs rw,soft,intr 0 0<br /> <br /> * Mount daqfs<br /> mount /daqfs<br /> <br /> ''' Which users/groups to allow access '''<br /> * Add entries to /etc/passwd<br /> +@da::::::<br /> +@ccc::::::<br /> +::::::/bin/false<br /> <br /> ''' A proxy for yum ''' (may be optional)<br /> * Add entry to /etc/yum.conf<br /> proxy=http://jprox:8080<br /> <br /> ''' domain servers for ypbind '''<br /> * Add entries to /etc/yp.conf<br /> domain CCCHP server nis2.jlab.org<br /> domain CCCHP server nis3.jlab.org<br /> <br /> * Make sure ypbind started at boot<br /> /sbin/chkconfig --level 345 nfs on <br /> <br /> ''' NTP setup ''' (optional... ntp must be installed)<br /> * Add entries to &lt;code&gt;/etc/ntp.conf&lt;/code&gt;<br /> server 127.0.0.1 # local clock<br /> fudge 127.0.0.1 stratum 10<br /> server ntp1.jlab.org<br /> server ntp2.jlab.org<br /> driftfile /etc/ntp/drift<br /> broadcastdelay 0.008<br /> authenticate no<br /> <br /> ''' Some additional JLab CUE directories to mount '''<br /> * Add entries to &lt;code&gt;/etc/auto.master&lt;/code&gt;<br /> /group /etc/auto.group --timeout=0<br /> /u auto.u.bb --DOSNAME=Linux-RHEL5<br /> <br /> ''' Additional files, not included in the standard diskless filesystem '''<br /> * Add a new file &lt;code&gt;/diskless/x86_64/Centos5.5/snapshot/files.custom&lt;/code&gt;. Entry:<br /> /tmp/<br /> /etc/minirc.dfl<br /> <br /> ''' Configure a NEW diskless client '''<br /> This operation must be peformed to add a new Diskless Client. <br /> <br /> ''' Configuration on the tftp/NFS server '''<br /> * In &lt;code&gt;system-config-netboot&lt;/code&gt; &quot;Network Installation and Diskless Environment&quot; window:<br /> # Click on &quot;New&quot;<br /> # Enter hostname<br /> # Select OS<br /> # Enter &quot;CCCHP&quot; in Enable NISDOMAIN box.<br /> # Enter options in &quot;Edit Extra Kernel Boot Options&quot; &lt;br /&gt; &lt;code&gt;vga=0x305 acpi=force&lt;/code&gt;<br /> # Enter hostname as snapshot name. Make sure &quot;generate&quot; is check-marked<br /> # Click &quot;OK&quot;<br /> <br /> ''' Configuration on the Diskless Client '''<br /> * PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br /> <br /> ''' Other useful packages to install '''<br /> Later on... I installed some other useful packages using the chroot environment. Here they are:<br /> <br /> * &lt;code&gt;xorg-x11-xauth&lt;/code&gt; - Required to run X-applications remotely<br /> * &lt;code&gt;ntp&lt;/code&gt; - Synchronize system clock with a central server<br /> : To Execute &lt;code&gt;ntpdate&lt;/code&gt; on server startup:<br /> :* Add &lt;code&gt;&lt;b&gt;-x&lt;/b&gt;&lt;/code&gt; to &lt;code&gt;OPTIONS&lt;/code&gt; in<br /> /etc/sysconfig/ntpd<br /> :* Make sure it starts on boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> == Network-based booting ==<br /> <br /> The page is geared towards the setup of Diskless nodes for Intel-based VME Controllers, but may be useful for similar other applications. Much of what is here was derived from the [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/3/html/System_Administration_Guide/ch-diskless.html Redhat Enterprise Linux 3 Documentation].<br /> <br /> This examples assumes:<br /> * The DHCP server (phecda: 129.57.29.104) has been installed and works. Here we're using the dhcp 3.0.1 package distributed by RHEL4.<br /> * The TFTP and NFS server (mizar: 129.57.29.100) is running RHEL5.5 x86_64.<br /> * The Diskless Client (dafarm44: 129.57.29.54) will run Centos 5.5 x86_64.<br /> <br /> There's nothing stopping you from having the DHCP server on the same machine as that servering TFTP and NFS. You can obviously have more than one diskless client.<br /> <br /> Once the first four steps have been completed, new clients can be configured individually with step 5.<br /> <br /> = Client Setup of OS in VirtualBox =<br /> Here, we've downloaded the latest and greatest Centos 5.5 x86_64 ISO and have set up a VirtualBox Client to use it to boot. We will not attempt to describe the VirtualBox installation or Setup of the ISO to boot as the VirtualBox Guest.<br /> <br /> The Centos 5.5 installation proceeds as normal installations go, but we opt to do a minimal installation (excluding KDE and/or GNOME components) since we're running on a VME controller. Other packages will be installed after first boot.<br /> <br /> === First Boot ===<br /> At first boot (after installation), a UI will appear and provide you with some options.:<br /> * Disable firewall and SELinux. SELinux setup can be double checked in the file:<br /> /etc/selinux/config<br /> * Disable sendmail, and other services not required for a VME controller<br /> <br /> === Update packages and transfer the OS to Server ===<br /> Login as root<br /> * Update all installed packages:<br /> yum update<br /> * Install the following packages, with:<br /> yum install &lt;i&gt;package&lt;/i&gt;<br /> :: busybox-anaconda<br /> :: gcc<br /> :: kernel-devel<br /> :: gdb<br /> :: valgrind<br /> :: cvs<br /> :: subversion<br /> :: compat-libstdc++-33<br /> :: redhat-rpm-config<br /> <br /> * Copy the Client OS to the tftp/NFS Server.<br /> ** On The Server:<br /> mkdir -p /diskless/x86_64/Centos5.5/root<br /> : In The VirtualBox Guest:<br /> rsync -Pav -e ssh --exclude='/proc/*' --exclude='/sys/*' / mizar:/diskless/x86_64/Centos5.5/root/<br /> <br /> You are now done with the Centos5.5 Guest installed in the VirtualBox. It can be closed down now.<br /> <br /> = tftp and NFS Server Setup =<br /> Follow these steps on the machine serving out tftp and NFS:<br /> <br /> ===Install &lt;code&gt;system-config-netboot&lt;/code&gt; ===<br /> (This should automatically install the tftp server)<br /> yum install system-config-netboot<br /> <br /> === Enable the tftp server to start at boot ===<br /> * Change line (&lt;code&gt;/etc/xinetd.d/tftp&lt;/code&gt;):<br /> disable = yes<br /> : To<br /> disable = no<br /> <br /> * Restart &lt;code&gt;xinetd&lt;/code&gt;<br /> service xinetd restart<br /> <br /> === Configure NFS ===<br /> * Add these entries to &lt;code&gt;/etc/exports&lt;/code&gt;<br /> /diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br /> /diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br /> : Where the &lt;code&gt;129.57.29.0/255.255.255.0&lt;/code&gt; only allows the 29 subnet to access these mounts.<br /> <br /> * Reload the NFS configuration or start NFS, if it's not started<br /> service nfs reload<br /> <br /> * Make sure NFS is started at boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> === Enable remote syslog (optional) ===<br /> * Change syslog argument in &lt;code&gt;/etc/sysconfig/syslog&lt;/code&gt; from:<br /> SYSLOGD_OPTIONS=&quot;-m 0&quot;<br /> :: To<br /> SYSLOGD_OPTIONS=&quot;-m 0 -r&quot;<br /> <br /> * Restart syslogd<br /> service syslog restart<br /> <br /> = DHCP Server Setup =<br /> On the machine hosting the DHCP server.<br /> <br /> * Add an entry in &lt;code&gt;/etc/dhcpd.conf&lt;/code&gt;:<br /> &lt;pre&gt;<br /> host dafarm44<br /> {<br /> filename &quot;linux-install/pxelinux.0&quot;; # File location relative to /tftpboot/<br /> next-server 129.57.29.38; # TFTP server<br /> hardware ethernet 00:20:38:03:D8:52; # Client MAC<br /> fixed-address 129.57.29.54; # Client IP<br /> }<br /> &lt;/pre&gt;<br /> <br /> * Restart dhcpd<br /> service dhcpd restart<br /> <br /> = Configure Client OS =<br /> <br /> Here, we configure the OS that each and every Diskless Client will enjoy.<br /> <br /> === Setup of Diskless Kernel ===<br /> Run system-config-netboot (on TFTP server):<br /> system-config-netboot<br /> <br /> * In &quot;First Time Druid&quot; window. Click on &quot;Diskless&quot;<br /> # Click &quot;Forward&quot; on first page<br /> # Enter Name and Description.<br /> # Enter IP address of TFTP server and the &quot;root&quot; directory exported via NFS<br /> # Select a kernel<br /> # Click on Apply.<br /> : This will take a minute or two to compile a boot kernel for the diskless client.<br /> <br /> === Setup of chroot environment === <br /> There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br /> This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br /> chroot /diskless/x86_64/Centos5.5/root<br /> mount /proc /proc -t proc<br /> mkdir /u <br /> mkdir /group<br /> mkdir /daqfs<br /> mv /home /home.old<br /> ln -s /u/apps /apps<br /> ln -s /u/site /site<br /> ln -s /daqfs/home /home<br /> <br /> === Setup of diskless system configurations ===<br /> ''' Which NFS directories to mount '''<br /> * Add entry to &lt;code&gt;/etc/fstab&lt;/code&gt;<br /> phecda:/raid /daqfs nfs rw,soft,intr 0 0<br /> <br /> * Mount daqfs<br /> mount /daqfs<br /> <br /> ''' Which users/groups to allow access '''<br /> * Add entries to /etc/passwd<br /> +@da::::::<br /> +@ccc::::::<br /> +::::::/bin/false<br /> <br /> ''' A proxy for yum ''' (may be optional)<br /> * Add entry to /etc/yum.conf<br /> proxy=http://jprox:8080<br /> <br /> ''' domain servers for ypbind '''<br /> * Add entries to /etc/yp.conf<br /> domain CCCHP server nis2.jlab.org<br /> domain CCCHP server nis3.jlab.org<br /> <br /> * Make sure ypbind started at boot<br /> /sbin/chkconfig --level 345 nfs on <br /> <br /> ''' NTP setup ''' (optional... ntp must be installed)<br /> * Add entries to &lt;code&gt;/etc/ntp.conf&lt;/code&gt;<br /> server 127.0.0.1 # local clock<br /> fudge 127.0.0.1 stratum 10<br /> server ntp1.jlab.org<br /> server ntp2.jlab.org<br /> driftfile /etc/ntp/drift<br /> broadcastdelay 0.008<br /> authenticate no<br /> <br /> ''' Some additional JLab CUE directories to mount '''<br /> * Add entries to &lt;code&gt;/etc/auto.master&lt;/code&gt;<br /> /group /etc/auto.group --timeout=0<br /> /u auto.u.bb --DOSNAME=Linux-RHEL5<br /> <br /> ''' Additional files, not included in the standard diskless filesystem '''<br /> * Add a new file &lt;code&gt;/diskless/x86_64/Centos5.5/snapshot/files.custom&lt;/code&gt;. Entry:<br /> /tmp/<br /> /etc/minirc.dfl<br /> <br /> = Configure a NEW diskless client =<br /> This operation must be peformed to add a new Diskless Client. <br /> <br /> === Configuration on the tftp/NFS server ===<br /> * In &lt;code&gt;system-config-netboot&lt;/code&gt; &quot;Network Installation and Diskless Environment&quot; window:<br /> # Click on &quot;New&quot;<br /> # Enter hostname<br /> # Select OS<br /> # Enter &quot;CCCHP&quot; in Enable NISDOMAIN box.<br /> # Enter options in &quot;Edit Extra Kernel Boot Options&quot; &lt;br /&gt; &lt;code&gt;vga=0x305 acpi=force&lt;/code&gt;<br /> # Enter hostname as snapshot name. Make sure &quot;generate&quot; is check-marked<br /> # Click &quot;OK&quot;<br /> <br /> === Configuration on the Diskless Client ===<br /> * PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br /> <br /> = Other useful packages to install =<br /> Later on... I installed some other useful packages using the chroot environment. Here they are:<br /> <br /> * &lt;code&gt;xorg-x11-xauth&lt;/code&gt; - Required to run X-applications remotely<br /> * &lt;code&gt;ntp&lt;/code&gt; - Synchronize system clock with a central server<br /> : To Execute &lt;code&gt;ntpdate&lt;/code&gt; on server startup:<br /> :* Add &lt;code&gt;&lt;b&gt;-x&lt;/b&gt;&lt;/code&gt; to &lt;code&gt;OPTIONS&lt;/code&gt; in<br /> /etc/sysconfig/ntpd<br /> :* Make sure it starts on boot<br /> /sbin/chkconfig --level 345 nfs on</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=GE_XVB601&diff=5186 2011-03-29T19:15:50Z

<p>129.57.167.199: </p> <hr /> <div>Company site: [http://www.ge-ip.com/products/family/embedded-systems GE Intelligent Platforms]<br /> <br /> Board page on company site: [http://www.ge-ip.com/products/3448 XVB601]<br /> <br /> Documentation: [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_522-9300800627-000_A.book.pdf Installation Guide]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_Configuration_Guide_XVB601.pdf Sales Options]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_Ruggedization_Levels_GFA-926a.pdf Ruggedization]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_xvb601_ds_gfa1299.pdf Datasheet]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_xvb601_hr_500-930007815-000_E.pdf (pdf)]<br /> <br /> == Customization for the CLON cluster ==<br /> <br /> '''List of boards'''<br /> <br /> * [01] 00:20:38:04:23:5E / 129.57.68.89 / croctest2<br /> <br /> '''Customizing kernel installed on the FLASH'''<br /> <br /> * ''/usr/bin/system-config-network''<br /> <br /> * fix ''/etc/passwd'', ''/etc/shadow'', ''/etc/group''<br /> <br /> * fix ''/etc/nsswitch.conf''<br /> <br /> * fix ''/etc/yp.conf'' (add lines ''domain CCCHP server clon00.jlab.org'' and ''ypserver clon10.jlab.org'')<br /> <br /> * fix ''/etc/sysconfig/network'' (add line ''NISDOMAIN=CCCHP'')<br /> <br /> * ''/etc/init.d/ypbind start''<br /> <br /> * ''chkconfig ypbind on''<br /> <br /> <br /> * set RHEL-style [[automounts]]<br /> <br /> * ''/etc/init.d/autofs restart''<br /> <br /> * fix symbolic links to /apps, /home, /usr/local etc<br /> <br /> <br /> <br /> '''Trying netboot following Bryan's instructions, using clonpc3'''<br /> <br /> * ''yum install system-config-netboot''<br /> <br /> * Change line (&lt;code&gt;/etc/xinetd.d/tftp&lt;/code&gt;):<br /> disable = yes<br /> : To<br /> disable = no<br /> <br /> * ''service xinetd restart''<br /> <br /> * Add these entries to &lt;code&gt;/etc/exports&lt;/code&gt;<br /> /diskless/x86_64/Centos5.5/root/ 129.57.167.0/255.255.255.0(ro,sync,no_root_squash)<br /> /diskless/x86_64/Centos5.5/snapshot/ 129.57.167.0/255.255.255.0(rw,sync,no_root_squash)<br /> : Where the &lt;code&gt;129.57.167.0/255.255.255.0&lt;/code&gt; only allows the 167 subnet to access these mounts.<br /> <br /> * Reload the NFS configuration or start NFS, if it's not started<br /> ''service nfs reload''<br /> <br /> * Make sure NFS is started at boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> * Enable remote syslog (optional)<br /> <br /> Change syslog argument in &lt;code&gt;/etc/sysconfig/syslog&lt;/code&gt; from:<br /> SYSLOGD_OPTIONS=&quot;-m 0&quot;<br /> :: To<br /> SYSLOGD_OPTIONS=&quot;-m 0 -r&quot;<br /> <br /> Restart syslogd<br /> service syslog restart<br /> <br /> '''DHCP Server Setup'''<br /> On the machine hosting the DHCP server.<br /> <br /> * Add an entry in &lt;code&gt;/etc/dhcpd.conf&lt;/code&gt;:<br /> &lt;pre&gt;<br /> host dafarm44<br /> {<br /> filename &quot;linux-install/pxelinux.0&quot;; # File location relative to /tftpboot/<br /> next-server 129.57.29.38; # TFTP server<br /> hardware ethernet 00:20:38:03:D8:52; # Client MAC<br /> fixed-address 129.57.29.54; # Client IP<br /> }<br /> &lt;/pre&gt;<br /> <br /> * Restart dhcpd<br /> service dhcpd restart<br /> <br /> '''Configure Client OS'''<br /> <br /> Here, we configure the OS that each and every Diskless Client will enjoy.<br /> <br /> '''Setup of Diskless Kernel'''<br /> Run system-config-netboot (on TFTP server):<br /> system-config-netboot<br /> <br /> * In &quot;First Time Druid&quot; window. Click on &quot;Diskless&quot;<br /> # Click &quot;Forward&quot; on first page<br /> # Enter Name and Description.<br /> # Enter IP address of TFTP server and the &quot;root&quot; directory exported via NFS<br /> # Select a kernel<br /> # Click on Apply.<br /> : This will take a minute or two to compile a boot kernel for the diskless client.<br /> <br /> '''Setup of chroot environment'''<br /> There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br /> This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br /> chroot /diskless/x86_64/Centos5.5/root<br /> mount /proc /proc -t proc<br /> mkdir /u <br /> mkdir /group<br /> mkdir /daqfs<br /> mv /home /home.old<br /> ln -s /u/apps /apps<br /> ln -s /u/site /site<br /> ln -s /daqfs/home /home<br /> <br /> '''Setup of diskless system configurations'''<br /> <br /> ''' Which NFS directories to mount '''<br /> <br /> * Add entry to &lt;code&gt;/etc/fstab&lt;/code&gt;<br /> phecda:/raid /daqfs nfs rw,soft,intr 0 0<br /> <br /> * Mount daqfs<br /> mount /daqfs<br /> <br /> ''' Which users/groups to allow access '''<br /> * Add entries to /etc/passwd<br /> +@da::::::<br /> +@ccc::::::<br /> +::::::/bin/false<br /> <br /> ''' A proxy for yum ''' (may be optional)<br /> * Add entry to /etc/yum.conf<br /> proxy=http://jprox:8080<br /> <br /> ''' domain servers for ypbind '''<br /> * Add entries to /etc/yp.conf<br /> domain CCCHP server nis2.jlab.org<br /> domain CCCHP server nis3.jlab.org<br /> <br /> * Make sure ypbind started at boot<br /> /sbin/chkconfig --level 345 nfs on <br /> <br /> ''' NTP setup ''' (optional... ntp must be installed)<br /> * Add entries to &lt;code&gt;/etc/ntp.conf&lt;/code&gt;<br /> server 127.0.0.1 # local clock<br /> fudge 127.0.0.1 stratum 10<br /> server ntp1.jlab.org<br /> server ntp2.jlab.org<br /> driftfile /etc/ntp/drift<br /> broadcastdelay 0.008<br /> authenticate no<br /> <br /> ''' Some additional JLab CUE directories to mount '''<br /> * Add entries to &lt;code&gt;/etc/auto.master&lt;/code&gt;<br /> /group /etc/auto.group --timeout=0<br /> /u auto.u.bb --DOSNAME=Linux-RHEL5<br /> <br /> ''' Additional files, not included in the standard diskless filesystem '''<br /> * Add a new file &lt;code&gt;/diskless/x86_64/Centos5.5/snapshot/files.custom&lt;/code&gt;. Entry:<br /> /tmp/<br /> /etc/minirc.dfl<br /> <br /> ''' Configure a NEW diskless client '''<br /> This operation must be peformed to add a new Diskless Client. <br /> <br /> ''' Configuration on the tftp/NFS server '''<br /> * In &lt;code&gt;system-config-netboot&lt;/code&gt; &quot;Network Installation and Diskless Environment&quot; window:<br /> # Click on &quot;New&quot;<br /> # Enter hostname<br /> # Select OS<br /> # Enter &quot;CCCHP&quot; in Enable NISDOMAIN box.<br /> # Enter options in &quot;Edit Extra Kernel Boot Options&quot; &lt;br /&gt; &lt;code&gt;vga=0x305 acpi=force&lt;/code&gt;<br /> # Enter hostname as snapshot name. Make sure &quot;generate&quot; is check-marked<br /> # Click &quot;OK&quot;<br /> <br /> ''' Configuration on the Diskless Client '''<br /> * PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br /> <br /> ''' Other useful packages to install '''<br /> Later on... I installed some other useful packages using the chroot environment. Here they are:<br /> <br /> * &lt;code&gt;xorg-x11-xauth&lt;/code&gt; - Required to run X-applications remotely<br /> * &lt;code&gt;ntp&lt;/code&gt; - Synchronize system clock with a central server<br /> : To Execute &lt;code&gt;ntpdate&lt;/code&gt; on server startup:<br /> :* Add &lt;code&gt;&lt;b&gt;-x&lt;/b&gt;&lt;/code&gt; to &lt;code&gt;OPTIONS&lt;/code&gt; in<br /> /etc/sysconfig/ntpd<br /> :* Make sure it starts on boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> == Network-based booting ==<br /> <br /> The page is geared towards the setup of Diskless nodes for Intel-based VME Controllers, but may be useful for similar other applications. Much of what is here was derived from the [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/3/html/System_Administration_Guide/ch-diskless.html Redhat Enterprise Linux 3 Documentation].<br /> <br /> This examples assumes:<br /> * The DHCP server (phecda: 129.57.29.104) has been installed and works. Here we're using the dhcp 3.0.1 package distributed by RHEL4.<br /> * The TFTP and NFS server (mizar: 129.57.29.100) is running RHEL5.5 x86_64.<br /> * The Diskless Client (dafarm44: 129.57.29.54) will run Centos 5.5 x86_64.<br /> <br /> There's nothing stopping you from having the DHCP server on the same machine as that servering TFTP and NFS. You can obviously have more than one diskless client.<br /> <br /> Once the first four steps have been completed, new clients can be configured individually with step 5.<br /> <br /> = Client Setup of OS in VirtualBox =<br /> Here, we've downloaded the latest and greatest Centos 5.5 x86_64 ISO and have set up a VirtualBox Client to use it to boot. We will not attempt to describe the VirtualBox installation or Setup of the ISO to boot as the VirtualBox Guest.<br /> <br /> The Centos 5.5 installation proceeds as normal installations go, but we opt to do a minimal installation (excluding KDE and/or GNOME components) since we're running on a VME controller. Other packages will be installed after first boot.<br /> <br /> === First Boot ===<br /> At first boot (after installation), a UI will appear and provide you with some options.:<br /> * Disable firewall and SELinux. SELinux setup can be double checked in the file:<br /> /etc/selinux/config<br /> * Disable sendmail, and other services not required for a VME controller<br /> <br /> === Update packages and transfer the OS to Server ===<br /> Login as root<br /> * Update all installed packages:<br /> yum update<br /> * Install the following packages, with:<br /> yum install &lt;i&gt;package&lt;/i&gt;<br /> :: busybox-anaconda<br /> :: gcc<br /> :: kernel-devel<br /> :: gdb<br /> :: valgrind<br /> :: cvs<br /> :: subversion<br /> :: compat-libstdc++-33<br /> :: redhat-rpm-config<br /> <br /> * Copy the Client OS to the tftp/NFS Server.<br /> ** On The Server:<br /> mkdir -p /diskless/x86_64/Centos5.5/root<br /> : In The VirtualBox Guest:<br /> rsync -Pav -e ssh --exclude='/proc/*' --exclude='/sys/*' / mizar:/diskless/x86_64/Centos5.5/root/<br /> <br /> You are now done with the Centos5.5 Guest installed in the VirtualBox. It can be closed down now.<br /> <br /> = tftp and NFS Server Setup =<br /> Follow these steps on the machine serving out tftp and NFS:<br /> <br /> ===Install &lt;code&gt;system-config-netboot&lt;/code&gt; ===<br /> (This should automatically install the tftp server)<br /> yum install system-config-netboot<br /> <br /> === Enable the tftp server to start at boot ===<br /> * Change line (&lt;code&gt;/etc/xinetd.d/tftp&lt;/code&gt;):<br /> disable = yes<br /> : To<br /> disable = no<br /> <br /> * Restart &lt;code&gt;xinetd&lt;/code&gt;<br /> service xinetd restart<br /> <br /> === Configure NFS ===<br /> * Add these entries to &lt;code&gt;/etc/exports&lt;/code&gt;<br /> /diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br /> /diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br /> : Where the &lt;code&gt;129.57.29.0/255.255.255.0&lt;/code&gt; only allows the 29 subnet to access these mounts.<br /> <br /> * Reload the NFS configuration or start NFS, if it's not started<br /> service nfs reload<br /> <br /> * Make sure NFS is started at boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> === Enable remote syslog (optional) ===<br /> * Change syslog argument in &lt;code&gt;/etc/sysconfig/syslog&lt;/code&gt; from:<br /> SYSLOGD_OPTIONS=&quot;-m 0&quot;<br /> :: To<br /> SYSLOGD_OPTIONS=&quot;-m 0 -r&quot;<br /> <br /> * Restart syslogd<br /> service syslog restart<br /> <br /> = DHCP Server Setup =<br /> On the machine hosting the DHCP server.<br /> <br /> * Add an entry in &lt;code&gt;/etc/dhcpd.conf&lt;/code&gt;:<br /> &lt;pre&gt;<br /> host dafarm44<br /> {<br /> filename &quot;linux-install/pxelinux.0&quot;; # File location relative to /tftpboot/<br /> next-server 129.57.29.38; # TFTP server<br /> hardware ethernet 00:20:38:03:D8:52; # Client MAC<br /> fixed-address 129.57.29.54; # Client IP<br /> }<br /> &lt;/pre&gt;<br /> <br /> * Restart dhcpd<br /> service dhcpd restart<br /> <br /> = Configure Client OS =<br /> <br /> Here, we configure the OS that each and every Diskless Client will enjoy.<br /> <br /> === Setup of Diskless Kernel ===<br /> Run system-config-netboot (on TFTP server):<br /> system-config-netboot<br /> <br /> * In &quot;First Time Druid&quot; window. Click on &quot;Diskless&quot;<br /> # Click &quot;Forward&quot; on first page<br /> # Enter Name and Description.<br /> # Enter IP address of TFTP server and the &quot;root&quot; directory exported via NFS<br /> # Select a kernel<br /> # Click on Apply.<br /> : This will take a minute or two to compile a boot kernel for the diskless client.<br /> <br /> === Setup of chroot environment === <br /> There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br /> This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br /> chroot /diskless/x86_64/Centos5.5/root<br /> mount /proc /proc -t proc<br /> mkdir /u <br /> mkdir /group<br /> mkdir /daqfs<br /> mv /home /home.old<br /> ln -s /u/apps /apps<br /> ln -s /u/site /site<br /> ln -s /daqfs/home /home<br /> <br /> === Setup of diskless system configurations ===<br /> ''' Which NFS directories to mount '''<br /> * Add entry to &lt;code&gt;/etc/fstab&lt;/code&gt;<br /> phecda:/raid /daqfs nfs rw,soft,intr 0 0<br /> <br /> * Mount daqfs<br /> mount /daqfs<br /> <br /> ''' Which users/groups to allow access '''<br /> * Add entries to /etc/passwd<br /> +@da::::::<br /> +@ccc::::::<br /> +::::::/bin/false<br /> <br /> ''' A proxy for yum ''' (may be optional)<br /> * Add entry to /etc/yum.conf<br /> proxy=http://jprox:8080<br /> <br /> ''' domain servers for ypbind '''<br /> * Add entries to /etc/yp.conf<br /> domain CCCHP server nis2.jlab.org<br /> domain CCCHP server nis3.jlab.org<br /> <br /> * Make sure ypbind started at boot<br /> /sbin/chkconfig --level 345 nfs on <br /> <br /> ''' NTP setup ''' (optional... ntp must be installed)<br /> * Add entries to &lt;code&gt;/etc/ntp.conf&lt;/code&gt;<br /> server 127.0.0.1 # local clock<br /> fudge 127.0.0.1 stratum 10<br /> server ntp1.jlab.org<br /> server ntp2.jlab.org<br /> driftfile /etc/ntp/drift<br /> broadcastdelay 0.008<br /> authenticate no<br /> <br /> ''' Some additional JLab CUE directories to mount '''<br /> * Add entries to &lt;code&gt;/etc/auto.master&lt;/code&gt;<br /> /group /etc/auto.group --timeout=0<br /> /u auto.u.bb --DOSNAME=Linux-RHEL5<br /> <br /> ''' Additional files, not included in the standard diskless filesystem '''<br /> * Add a new file &lt;code&gt;/diskless/x86_64/Centos5.5/snapshot/files.custom&lt;/code&gt;. Entry:<br /> /tmp/<br /> /etc/minirc.dfl<br /> <br /> = Configure a NEW diskless client =<br /> This operation must be peformed to add a new Diskless Client. <br /> <br /> === Configuration on the tftp/NFS server ===<br /> * In &lt;code&gt;system-config-netboot&lt;/code&gt; &quot;Network Installation and Diskless Environment&quot; window:<br /> # Click on &quot;New&quot;<br /> # Enter hostname<br /> # Select OS<br /> # Enter &quot;CCCHP&quot; in Enable NISDOMAIN box.<br /> # Enter options in &quot;Edit Extra Kernel Boot Options&quot; &lt;br /&gt; &lt;code&gt;vga=0x305 acpi=force&lt;/code&gt;<br /> # Enter hostname as snapshot name. Make sure &quot;generate&quot; is check-marked<br /> # Click &quot;OK&quot;<br /> <br /> === Configuration on the Diskless Client ===<br /> * PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br /> <br /> = Other useful packages to install =<br /> Later on... I installed some other useful packages using the chroot environment. Here they are:<br /> <br /> * &lt;code&gt;xorg-x11-xauth&lt;/code&gt; - Required to run X-applications remotely<br /> * &lt;code&gt;ntp&lt;/code&gt; - Synchronize system clock with a central server<br /> : To Execute &lt;code&gt;ntpdate&lt;/code&gt; on server startup:<br /> :* Add &lt;code&gt;&lt;b&gt;-x&lt;/b&gt;&lt;/code&gt; to &lt;code&gt;OPTIONS&lt;/code&gt; in<br /> /etc/sysconfig/ntpd<br /> :* Make sure it starts on boot<br /> /sbin/chkconfig --level 345 nfs on</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=GE_XVB601&diff=5185 2011-03-29T19:15:10Z

<p>129.57.167.199: </p> <hr /> <div>Company site: [http://www.ge-ip.com/products/family/embedded-systems GE Intelligent Platforms]<br /> <br /> Board page on company site: [http://www.ge-ip.com/products/3448 XVB601]<br /> <br /> Documentation: [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_522-9300800627-000_A.book.pdf Installation Guide]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_Configuration_Guide_XVB601.pdf Sales Options]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_Ruggedization_Levels_GFA-926a.pdf Ruggedization]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_xvb601_ds_gfa1299.pdf (pdf)]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_xvb601_hr_500-930007815-000_E.pdf (pdf)]<br /> <br /> == Customization for the CLON cluster ==<br /> <br /> '''List of boards'''<br /> <br /> * [01] 00:20:38:04:23:5E / 129.57.68.89 / croctest2<br /> <br /> '''Customizing kernel installed on the FLASH'''<br /> <br /> * ''/usr/bin/system-config-network''<br /> <br /> * fix ''/etc/passwd'', ''/etc/shadow'', ''/etc/group''<br /> <br /> * fix ''/etc/nsswitch.conf''<br /> <br /> * fix ''/etc/yp.conf'' (add lines ''domain CCCHP server clon00.jlab.org'' and ''ypserver clon10.jlab.org'')<br /> <br /> * fix ''/etc/sysconfig/network'' (add line ''NISDOMAIN=CCCHP'')<br /> <br /> * ''/etc/init.d/ypbind start''<br /> <br /> * ''chkconfig ypbind on''<br /> <br /> <br /> * set RHEL-style [[automounts]]<br /> <br /> * ''/etc/init.d/autofs restart''<br /> <br /> * fix symbolic links to /apps, /home, /usr/local etc<br /> <br /> <br /> <br /> '''Trying netboot following Bryan's instructions, using clonpc3'''<br /> <br /> * ''yum install system-config-netboot''<br /> <br /> * Change line (&lt;code&gt;/etc/xinetd.d/tftp&lt;/code&gt;):<br /> disable = yes<br /> : To<br /> disable = no<br /> <br /> * ''service xinetd restart''<br /> <br /> * Add these entries to &lt;code&gt;/etc/exports&lt;/code&gt;<br /> /diskless/x86_64/Centos5.5/root/ 129.57.167.0/255.255.255.0(ro,sync,no_root_squash)<br /> /diskless/x86_64/Centos5.5/snapshot/ 129.57.167.0/255.255.255.0(rw,sync,no_root_squash)<br /> : Where the &lt;code&gt;129.57.167.0/255.255.255.0&lt;/code&gt; only allows the 167 subnet to access these mounts.<br /> <br /> * Reload the NFS configuration or start NFS, if it's not started<br /> ''service nfs reload''<br /> <br /> * Make sure NFS is started at boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> * Enable remote syslog (optional)<br /> <br /> Change syslog argument in &lt;code&gt;/etc/sysconfig/syslog&lt;/code&gt; from:<br /> SYSLOGD_OPTIONS=&quot;-m 0&quot;<br /> :: To<br /> SYSLOGD_OPTIONS=&quot;-m 0 -r&quot;<br /> <br /> Restart syslogd<br /> service syslog restart<br /> <br /> '''DHCP Server Setup'''<br /> On the machine hosting the DHCP server.<br /> <br /> * Add an entry in &lt;code&gt;/etc/dhcpd.conf&lt;/code&gt;:<br /> &lt;pre&gt;<br /> host dafarm44<br /> {<br /> filename &quot;linux-install/pxelinux.0&quot;; # File location relative to /tftpboot/<br /> next-server 129.57.29.38; # TFTP server<br /> hardware ethernet 00:20:38:03:D8:52; # Client MAC<br /> fixed-address 129.57.29.54; # Client IP<br /> }<br /> &lt;/pre&gt;<br /> <br /> * Restart dhcpd<br /> service dhcpd restart<br /> <br /> '''Configure Client OS'''<br /> <br /> Here, we configure the OS that each and every Diskless Client will enjoy.<br /> <br /> '''Setup of Diskless Kernel'''<br /> Run system-config-netboot (on TFTP server):<br /> system-config-netboot<br /> <br /> * In &quot;First Time Druid&quot; window. Click on &quot;Diskless&quot;<br /> # Click &quot;Forward&quot; on first page<br /> # Enter Name and Description.<br /> # Enter IP address of TFTP server and the &quot;root&quot; directory exported via NFS<br /> # Select a kernel<br /> # Click on Apply.<br /> : This will take a minute or two to compile a boot kernel for the diskless client.<br /> <br /> '''Setup of chroot environment'''<br /> There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br /> This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br /> chroot /diskless/x86_64/Centos5.5/root<br /> mount /proc /proc -t proc<br /> mkdir /u <br /> mkdir /group<br /> mkdir /daqfs<br /> mv /home /home.old<br /> ln -s /u/apps /apps<br /> ln -s /u/site /site<br /> ln -s /daqfs/home /home<br /> <br /> '''Setup of diskless system configurations'''<br /> <br /> ''' Which NFS directories to mount '''<br /> <br /> * Add entry to &lt;code&gt;/etc/fstab&lt;/code&gt;<br /> phecda:/raid /daqfs nfs rw,soft,intr 0 0<br /> <br /> * Mount daqfs<br /> mount /daqfs<br /> <br /> ''' Which users/groups to allow access '''<br /> * Add entries to /etc/passwd<br /> +@da::::::<br /> +@ccc::::::<br /> +::::::/bin/false<br /> <br /> ''' A proxy for yum ''' (may be optional)<br /> * Add entry to /etc/yum.conf<br /> proxy=http://jprox:8080<br /> <br /> ''' domain servers for ypbind '''<br /> * Add entries to /etc/yp.conf<br /> domain CCCHP server nis2.jlab.org<br /> domain CCCHP server nis3.jlab.org<br /> <br /> * Make sure ypbind started at boot<br /> /sbin/chkconfig --level 345 nfs on <br /> <br /> ''' NTP setup ''' (optional... ntp must be installed)<br /> * Add entries to &lt;code&gt;/etc/ntp.conf&lt;/code&gt;<br /> server 127.0.0.1 # local clock<br /> fudge 127.0.0.1 stratum 10<br /> server ntp1.jlab.org<br /> server ntp2.jlab.org<br /> driftfile /etc/ntp/drift<br /> broadcastdelay 0.008<br /> authenticate no<br /> <br /> ''' Some additional JLab CUE directories to mount '''<br /> * Add entries to &lt;code&gt;/etc/auto.master&lt;/code&gt;<br /> /group /etc/auto.group --timeout=0<br /> /u auto.u.bb --DOSNAME=Linux-RHEL5<br /> <br /> ''' Additional files, not included in the standard diskless filesystem '''<br /> * Add a new file &lt;code&gt;/diskless/x86_64/Centos5.5/snapshot/files.custom&lt;/code&gt;. Entry:<br /> /tmp/<br /> /etc/minirc.dfl<br /> <br /> ''' Configure a NEW diskless client '''<br /> This operation must be peformed to add a new Diskless Client. <br /> <br /> ''' Configuration on the tftp/NFS server '''<br /> * In &lt;code&gt;system-config-netboot&lt;/code&gt; &quot;Network Installation and Diskless Environment&quot; window:<br /> # Click on &quot;New&quot;<br /> # Enter hostname<br /> # Select OS<br /> # Enter &quot;CCCHP&quot; in Enable NISDOMAIN box.<br /> # Enter options in &quot;Edit Extra Kernel Boot Options&quot; &lt;br /&gt; &lt;code&gt;vga=0x305 acpi=force&lt;/code&gt;<br /> # Enter hostname as snapshot name. Make sure &quot;generate&quot; is check-marked<br /> # Click &quot;OK&quot;<br /> <br /> ''' Configuration on the Diskless Client '''<br /> * PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br /> <br /> ''' Other useful packages to install '''<br /> Later on... I installed some other useful packages using the chroot environment. Here they are:<br /> <br /> * &lt;code&gt;xorg-x11-xauth&lt;/code&gt; - Required to run X-applications remotely<br /> * &lt;code&gt;ntp&lt;/code&gt; - Synchronize system clock with a central server<br /> : To Execute &lt;code&gt;ntpdate&lt;/code&gt; on server startup:<br /> :* Add &lt;code&gt;&lt;b&gt;-x&lt;/b&gt;&lt;/code&gt; to &lt;code&gt;OPTIONS&lt;/code&gt; in<br /> /etc/sysconfig/ntpd<br /> :* Make sure it starts on boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> == Network-based booting ==<br /> <br /> The page is geared towards the setup of Diskless nodes for Intel-based VME Controllers, but may be useful for similar other applications. Much of what is here was derived from the [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/3/html/System_Administration_Guide/ch-diskless.html Redhat Enterprise Linux 3 Documentation].<br /> <br /> This examples assumes:<br /> * The DHCP server (phecda: 129.57.29.104) has been installed and works. Here we're using the dhcp 3.0.1 package distributed by RHEL4.<br /> * The TFTP and NFS server (mizar: 129.57.29.100) is running RHEL5.5 x86_64.<br /> * The Diskless Client (dafarm44: 129.57.29.54) will run Centos 5.5 x86_64.<br /> <br /> There's nothing stopping you from having the DHCP server on the same machine as that servering TFTP and NFS. You can obviously have more than one diskless client.<br /> <br /> Once the first four steps have been completed, new clients can be configured individually with step 5.<br /> <br /> = Client Setup of OS in VirtualBox =<br /> Here, we've downloaded the latest and greatest Centos 5.5 x86_64 ISO and have set up a VirtualBox Client to use it to boot. We will not attempt to describe the VirtualBox installation or Setup of the ISO to boot as the VirtualBox Guest.<br /> <br /> The Centos 5.5 installation proceeds as normal installations go, but we opt to do a minimal installation (excluding KDE and/or GNOME components) since we're running on a VME controller. Other packages will be installed after first boot.<br /> <br /> === First Boot ===<br /> At first boot (after installation), a UI will appear and provide you with some options.:<br /> * Disable firewall and SELinux. SELinux setup can be double checked in the file:<br /> /etc/selinux/config<br /> * Disable sendmail, and other services not required for a VME controller<br /> <br /> === Update packages and transfer the OS to Server ===<br /> Login as root<br /> * Update all installed packages:<br /> yum update<br /> * Install the following packages, with:<br /> yum install &lt;i&gt;package&lt;/i&gt;<br /> :: busybox-anaconda<br /> :: gcc<br /> :: kernel-devel<br /> :: gdb<br /> :: valgrind<br /> :: cvs<br /> :: subversion<br /> :: compat-libstdc++-33<br /> :: redhat-rpm-config<br /> <br /> * Copy the Client OS to the tftp/NFS Server.<br /> ** On The Server:<br /> mkdir -p /diskless/x86_64/Centos5.5/root<br /> : In The VirtualBox Guest:<br /> rsync -Pav -e ssh --exclude='/proc/*' --exclude='/sys/*' / mizar:/diskless/x86_64/Centos5.5/root/<br /> <br /> You are now done with the Centos5.5 Guest installed in the VirtualBox. It can be closed down now.<br /> <br /> = tftp and NFS Server Setup =<br /> Follow these steps on the machine serving out tftp and NFS:<br /> <br /> ===Install &lt;code&gt;system-config-netboot&lt;/code&gt; ===<br /> (This should automatically install the tftp server)<br /> yum install system-config-netboot<br /> <br /> === Enable the tftp server to start at boot ===<br /> * Change line (&lt;code&gt;/etc/xinetd.d/tftp&lt;/code&gt;):<br /> disable = yes<br /> : To<br /> disable = no<br /> <br /> * Restart &lt;code&gt;xinetd&lt;/code&gt;<br /> service xinetd restart<br /> <br /> === Configure NFS ===<br /> * Add these entries to &lt;code&gt;/etc/exports&lt;/code&gt;<br /> /diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br /> /diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br /> : Where the &lt;code&gt;129.57.29.0/255.255.255.0&lt;/code&gt; only allows the 29 subnet to access these mounts.<br /> <br /> * Reload the NFS configuration or start NFS, if it's not started<br /> service nfs reload<br /> <br /> * Make sure NFS is started at boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> === Enable remote syslog (optional) ===<br /> * Change syslog argument in &lt;code&gt;/etc/sysconfig/syslog&lt;/code&gt; from:<br /> SYSLOGD_OPTIONS=&quot;-m 0&quot;<br /> :: To<br /> SYSLOGD_OPTIONS=&quot;-m 0 -r&quot;<br /> <br /> * Restart syslogd<br /> service syslog restart<br /> <br /> = DHCP Server Setup =<br /> On the machine hosting the DHCP server.<br /> <br /> * Add an entry in &lt;code&gt;/etc/dhcpd.conf&lt;/code&gt;:<br /> &lt;pre&gt;<br /> host dafarm44<br /> {<br /> filename &quot;linux-install/pxelinux.0&quot;; # File location relative to /tftpboot/<br /> next-server 129.57.29.38; # TFTP server<br /> hardware ethernet 00:20:38:03:D8:52; # Client MAC<br /> fixed-address 129.57.29.54; # Client IP<br /> }<br /> &lt;/pre&gt;<br /> <br /> * Restart dhcpd<br /> service dhcpd restart<br /> <br /> = Configure Client OS =<br /> <br /> Here, we configure the OS that each and every Diskless Client will enjoy.<br /> <br /> === Setup of Diskless Kernel ===<br /> Run system-config-netboot (on TFTP server):<br /> system-config-netboot<br /> <br /> * In &quot;First Time Druid&quot; window. Click on &quot;Diskless&quot;<br /> # Click &quot;Forward&quot; on first page<br /> # Enter Name and Description.<br /> # Enter IP address of TFTP server and the &quot;root&quot; directory exported via NFS<br /> # Select a kernel<br /> # Click on Apply.<br /> : This will take a minute or two to compile a boot kernel for the diskless client.<br /> <br /> === Setup of chroot environment === <br /> There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br /> This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br /> chroot /diskless/x86_64/Centos5.5/root<br /> mount /proc /proc -t proc<br /> mkdir /u <br /> mkdir /group<br /> mkdir /daqfs<br /> mv /home /home.old<br /> ln -s /u/apps /apps<br /> ln -s /u/site /site<br /> ln -s /daqfs/home /home<br /> <br /> === Setup of diskless system configurations ===<br /> ''' Which NFS directories to mount '''<br /> * Add entry to &lt;code&gt;/etc/fstab&lt;/code&gt;<br /> phecda:/raid /daqfs nfs rw,soft,intr 0 0<br /> <br /> * Mount daqfs<br /> mount /daqfs<br /> <br /> ''' Which users/groups to allow access '''<br /> * Add entries to /etc/passwd<br /> +@da::::::<br /> +@ccc::::::<br /> +::::::/bin/false<br /> <br /> ''' A proxy for yum ''' (may be optional)<br /> * Add entry to /etc/yum.conf<br /> proxy=http://jprox:8080<br /> <br /> ''' domain servers for ypbind '''<br /> * Add entries to /etc/yp.conf<br /> domain CCCHP server nis2.jlab.org<br /> domain CCCHP server nis3.jlab.org<br /> <br /> * Make sure ypbind started at boot<br /> /sbin/chkconfig --level 345 nfs on <br /> <br /> ''' NTP setup ''' (optional... ntp must be installed)<br /> * Add entries to &lt;code&gt;/etc/ntp.conf&lt;/code&gt;<br /> server 127.0.0.1 # local clock<br /> fudge 127.0.0.1 stratum 10<br /> server ntp1.jlab.org<br /> server ntp2.jlab.org<br /> driftfile /etc/ntp/drift<br /> broadcastdelay 0.008<br /> authenticate no<br /> <br /> ''' Some additional JLab CUE directories to mount '''<br /> * Add entries to &lt;code&gt;/etc/auto.master&lt;/code&gt;<br /> /group /etc/auto.group --timeout=0<br /> /u auto.u.bb --DOSNAME=Linux-RHEL5<br /> <br /> ''' Additional files, not included in the standard diskless filesystem '''<br /> * Add a new file &lt;code&gt;/diskless/x86_64/Centos5.5/snapshot/files.custom&lt;/code&gt;. Entry:<br /> /tmp/<br /> /etc/minirc.dfl<br /> <br /> = Configure a NEW diskless client =<br /> This operation must be peformed to add a new Diskless Client. <br /> <br /> === Configuration on the tftp/NFS server ===<br /> * In &lt;code&gt;system-config-netboot&lt;/code&gt; &quot;Network Installation and Diskless Environment&quot; window:<br /> # Click on &quot;New&quot;<br /> # Enter hostname<br /> # Select OS<br /> # Enter &quot;CCCHP&quot; in Enable NISDOMAIN box.<br /> # Enter options in &quot;Edit Extra Kernel Boot Options&quot; &lt;br /&gt; &lt;code&gt;vga=0x305 acpi=force&lt;/code&gt;<br /> # Enter hostname as snapshot name. Make sure &quot;generate&quot; is check-marked<br /> # Click &quot;OK&quot;<br /> <br /> === Configuration on the Diskless Client ===<br /> * PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br /> <br /> = Other useful packages to install =<br /> Later on... I installed some other useful packages using the chroot environment. Here they are:<br /> <br /> * &lt;code&gt;xorg-x11-xauth&lt;/code&gt; - Required to run X-applications remotely<br /> * &lt;code&gt;ntp&lt;/code&gt; - Synchronize system clock with a central server<br /> : To Execute &lt;code&gt;ntpdate&lt;/code&gt; on server startup:<br /> :* Add &lt;code&gt;&lt;b&gt;-x&lt;/b&gt;&lt;/code&gt; to &lt;code&gt;OPTIONS&lt;/code&gt; in<br /> /etc/sysconfig/ntpd<br /> :* Make sure it starts on boot<br /> /sbin/chkconfig --level 345 nfs on</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=GE_XVB601&diff=5184 2011-03-29T19:14:13Z

<p>129.57.167.199: </p> <hr /> <div>Company site: [http://www.ge-ip.com/products/family/embedded-systems GE Intelligent Platforms]<br /> <br /> Board page on company site: [http://www.ge-ip.com/products/3448 XVB601]<br /> <br /> Documentation: [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_522-9300800627-000_A.book.pdf Installation Guide]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_Configuration_Guide_XVB601.pdf Sales Options]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_Ruggedization_Levels_GFA-926a.pdf (pdf)]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_xvb601_ds_gfa1299.pdf (pdf)]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_xvb601_hr_500-930007815-000_E.pdf (pdf)]<br /> <br /> == Customization for the CLON cluster ==<br /> <br /> '''List of boards'''<br /> <br /> * [01] 00:20:38:04:23:5E / 129.57.68.89 / croctest2<br /> <br /> '''Customizing kernel installed on the FLASH'''<br /> <br /> * ''/usr/bin/system-config-network''<br /> <br /> * fix ''/etc/passwd'', ''/etc/shadow'', ''/etc/group''<br /> <br /> * fix ''/etc/nsswitch.conf''<br /> <br /> * fix ''/etc/yp.conf'' (add lines ''domain CCCHP server clon00.jlab.org'' and ''ypserver clon10.jlab.org'')<br /> <br /> * fix ''/etc/sysconfig/network'' (add line ''NISDOMAIN=CCCHP'')<br /> <br /> * ''/etc/init.d/ypbind start''<br /> <br /> * ''chkconfig ypbind on''<br /> <br /> <br /> * set RHEL-style [[automounts]]<br /> <br /> * ''/etc/init.d/autofs restart''<br /> <br /> * fix symbolic links to /apps, /home, /usr/local etc<br /> <br /> <br /> <br /> '''Trying netboot following Bryan's instructions, using clonpc3'''<br /> <br /> * ''yum install system-config-netboot''<br /> <br /> * Change line (&lt;code&gt;/etc/xinetd.d/tftp&lt;/code&gt;):<br /> disable = yes<br /> : To<br /> disable = no<br /> <br /> * ''service xinetd restart''<br /> <br /> * Add these entries to &lt;code&gt;/etc/exports&lt;/code&gt;<br /> /diskless/x86_64/Centos5.5/root/ 129.57.167.0/255.255.255.0(ro,sync,no_root_squash)<br /> /diskless/x86_64/Centos5.5/snapshot/ 129.57.167.0/255.255.255.0(rw,sync,no_root_squash)<br /> : Where the &lt;code&gt;129.57.167.0/255.255.255.0&lt;/code&gt; only allows the 167 subnet to access these mounts.<br /> <br /> * Reload the NFS configuration or start NFS, if it's not started<br /> ''service nfs reload''<br /> <br /> * Make sure NFS is started at boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> * Enable remote syslog (optional)<br /> <br /> Change syslog argument in &lt;code&gt;/etc/sysconfig/syslog&lt;/code&gt; from:<br /> SYSLOGD_OPTIONS=&quot;-m 0&quot;<br /> :: To<br /> SYSLOGD_OPTIONS=&quot;-m 0 -r&quot;<br /> <br /> Restart syslogd<br /> service syslog restart<br /> <br /> '''DHCP Server Setup'''<br /> On the machine hosting the DHCP server.<br /> <br /> * Add an entry in &lt;code&gt;/etc/dhcpd.conf&lt;/code&gt;:<br /> &lt;pre&gt;<br /> host dafarm44<br /> {<br /> filename &quot;linux-install/pxelinux.0&quot;; # File location relative to /tftpboot/<br /> next-server 129.57.29.38; # TFTP server<br /> hardware ethernet 00:20:38:03:D8:52; # Client MAC<br /> fixed-address 129.57.29.54; # Client IP<br /> }<br /> &lt;/pre&gt;<br /> <br /> * Restart dhcpd<br /> service dhcpd restart<br /> <br /> '''Configure Client OS'''<br /> <br /> Here, we configure the OS that each and every Diskless Client will enjoy.<br /> <br /> '''Setup of Diskless Kernel'''<br /> Run system-config-netboot (on TFTP server):<br /> system-config-netboot<br /> <br /> * In &quot;First Time Druid&quot; window. Click on &quot;Diskless&quot;<br /> # Click &quot;Forward&quot; on first page<br /> # Enter Name and Description.<br /> # Enter IP address of TFTP server and the &quot;root&quot; directory exported via NFS<br /> # Select a kernel<br /> # Click on Apply.<br /> : This will take a minute or two to compile a boot kernel for the diskless client.<br /> <br /> '''Setup of chroot environment'''<br /> There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br /> This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br /> chroot /diskless/x86_64/Centos5.5/root<br /> mount /proc /proc -t proc<br /> mkdir /u <br /> mkdir /group<br /> mkdir /daqfs<br /> mv /home /home.old<br /> ln -s /u/apps /apps<br /> ln -s /u/site /site<br /> ln -s /daqfs/home /home<br /> <br /> '''Setup of diskless system configurations'''<br /> <br /> ''' Which NFS directories to mount '''<br /> <br /> * Add entry to &lt;code&gt;/etc/fstab&lt;/code&gt;<br /> phecda:/raid /daqfs nfs rw,soft,intr 0 0<br /> <br /> * Mount daqfs<br /> mount /daqfs<br /> <br /> ''' Which users/groups to allow access '''<br /> * Add entries to /etc/passwd<br /> +@da::::::<br /> +@ccc::::::<br /> +::::::/bin/false<br /> <br /> ''' A proxy for yum ''' (may be optional)<br /> * Add entry to /etc/yum.conf<br /> proxy=http://jprox:8080<br /> <br /> ''' domain servers for ypbind '''<br /> * Add entries to /etc/yp.conf<br /> domain CCCHP server nis2.jlab.org<br /> domain CCCHP server nis3.jlab.org<br /> <br /> * Make sure ypbind started at boot<br /> /sbin/chkconfig --level 345 nfs on <br /> <br /> ''' NTP setup ''' (optional... ntp must be installed)<br /> * Add entries to &lt;code&gt;/etc/ntp.conf&lt;/code&gt;<br /> server 127.0.0.1 # local clock<br /> fudge 127.0.0.1 stratum 10<br /> server ntp1.jlab.org<br /> server ntp2.jlab.org<br /> driftfile /etc/ntp/drift<br /> broadcastdelay 0.008<br /> authenticate no<br /> <br /> ''' Some additional JLab CUE directories to mount '''<br /> * Add entries to &lt;code&gt;/etc/auto.master&lt;/code&gt;<br /> /group /etc/auto.group --timeout=0<br /> /u auto.u.bb --DOSNAME=Linux-RHEL5<br /> <br /> ''' Additional files, not included in the standard diskless filesystem '''<br /> * Add a new file &lt;code&gt;/diskless/x86_64/Centos5.5/snapshot/files.custom&lt;/code&gt;. Entry:<br /> /tmp/<br /> /etc/minirc.dfl<br /> <br /> ''' Configure a NEW diskless client '''<br /> This operation must be peformed to add a new Diskless Client. <br /> <br /> ''' Configuration on the tftp/NFS server '''<br /> * In &lt;code&gt;system-config-netboot&lt;/code&gt; &quot;Network Installation and Diskless Environment&quot; window:<br /> # Click on &quot;New&quot;<br /> # Enter hostname<br /> # Select OS<br /> # Enter &quot;CCCHP&quot; in Enable NISDOMAIN box.<br /> # Enter options in &quot;Edit Extra Kernel Boot Options&quot; &lt;br /&gt; &lt;code&gt;vga=0x305 acpi=force&lt;/code&gt;<br /> # Enter hostname as snapshot name. Make sure &quot;generate&quot; is check-marked<br /> # Click &quot;OK&quot;<br /> <br /> ''' Configuration on the Diskless Client '''<br /> * PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br /> <br /> ''' Other useful packages to install '''<br /> Later on... I installed some other useful packages using the chroot environment. Here they are:<br /> <br /> * &lt;code&gt;xorg-x11-xauth&lt;/code&gt; - Required to run X-applications remotely<br /> * &lt;code&gt;ntp&lt;/code&gt; - Synchronize system clock with a central server<br /> : To Execute &lt;code&gt;ntpdate&lt;/code&gt; on server startup:<br /> :* Add &lt;code&gt;&lt;b&gt;-x&lt;/b&gt;&lt;/code&gt; to &lt;code&gt;OPTIONS&lt;/code&gt; in<br /> /etc/sysconfig/ntpd<br /> :* Make sure it starts on boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> == Network-based booting ==<br /> <br /> The page is geared towards the setup of Diskless nodes for Intel-based VME Controllers, but may be useful for similar other applications. Much of what is here was derived from the [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/3/html/System_Administration_Guide/ch-diskless.html Redhat Enterprise Linux 3 Documentation].<br /> <br /> This examples assumes:<br /> * The DHCP server (phecda: 129.57.29.104) has been installed and works. Here we're using the dhcp 3.0.1 package distributed by RHEL4.<br /> * The TFTP and NFS server (mizar: 129.57.29.100) is running RHEL5.5 x86_64.<br /> * The Diskless Client (dafarm44: 129.57.29.54) will run Centos 5.5 x86_64.<br /> <br /> There's nothing stopping you from having the DHCP server on the same machine as that servering TFTP and NFS. You can obviously have more than one diskless client.<br /> <br /> Once the first four steps have been completed, new clients can be configured individually with step 5.<br /> <br /> = Client Setup of OS in VirtualBox =<br /> Here, we've downloaded the latest and greatest Centos 5.5 x86_64 ISO and have set up a VirtualBox Client to use it to boot. We will not attempt to describe the VirtualBox installation or Setup of the ISO to boot as the VirtualBox Guest.<br /> <br /> The Centos 5.5 installation proceeds as normal installations go, but we opt to do a minimal installation (excluding KDE and/or GNOME components) since we're running on a VME controller. Other packages will be installed after first boot.<br /> <br /> === First Boot ===<br /> At first boot (after installation), a UI will appear and provide you with some options.:<br /> * Disable firewall and SELinux. SELinux setup can be double checked in the file:<br /> /etc/selinux/config<br /> * Disable sendmail, and other services not required for a VME controller<br /> <br /> === Update packages and transfer the OS to Server ===<br /> Login as root<br /> * Update all installed packages:<br /> yum update<br /> * Install the following packages, with:<br /> yum install &lt;i&gt;package&lt;/i&gt;<br /> :: busybox-anaconda<br /> :: gcc<br /> :: kernel-devel<br /> :: gdb<br /> :: valgrind<br /> :: cvs<br /> :: subversion<br /> :: compat-libstdc++-33<br /> :: redhat-rpm-config<br /> <br /> * Copy the Client OS to the tftp/NFS Server.<br /> ** On The Server:<br /> mkdir -p /diskless/x86_64/Centos5.5/root<br /> : In The VirtualBox Guest:<br /> rsync -Pav -e ssh --exclude='/proc/*' --exclude='/sys/*' / mizar:/diskless/x86_64/Centos5.5/root/<br /> <br /> You are now done with the Centos5.5 Guest installed in the VirtualBox. It can be closed down now.<br /> <br /> = tftp and NFS Server Setup =<br /> Follow these steps on the machine serving out tftp and NFS:<br /> <br /> ===Install &lt;code&gt;system-config-netboot&lt;/code&gt; ===<br /> (This should automatically install the tftp server)<br /> yum install system-config-netboot<br /> <br /> === Enable the tftp server to start at boot ===<br /> * Change line (&lt;code&gt;/etc/xinetd.d/tftp&lt;/code&gt;):<br /> disable = yes<br /> : To<br /> disable = no<br /> <br /> * Restart &lt;code&gt;xinetd&lt;/code&gt;<br /> service xinetd restart<br /> <br /> === Configure NFS ===<br /> * Add these entries to &lt;code&gt;/etc/exports&lt;/code&gt;<br /> /diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br /> /diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br /> : Where the &lt;code&gt;129.57.29.0/255.255.255.0&lt;/code&gt; only allows the 29 subnet to access these mounts.<br /> <br /> * Reload the NFS configuration or start NFS, if it's not started<br /> service nfs reload<br /> <br /> * Make sure NFS is started at boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> === Enable remote syslog (optional) ===<br /> * Change syslog argument in &lt;code&gt;/etc/sysconfig/syslog&lt;/code&gt; from:<br /> SYSLOGD_OPTIONS=&quot;-m 0&quot;<br /> :: To<br /> SYSLOGD_OPTIONS=&quot;-m 0 -r&quot;<br /> <br /> * Restart syslogd<br /> service syslog restart<br /> <br /> = DHCP Server Setup =<br /> On the machine hosting the DHCP server.<br /> <br /> * Add an entry in &lt;code&gt;/etc/dhcpd.conf&lt;/code&gt;:<br /> &lt;pre&gt;<br /> host dafarm44<br /> {<br /> filename &quot;linux-install/pxelinux.0&quot;; # File location relative to /tftpboot/<br /> next-server 129.57.29.38; # TFTP server<br /> hardware ethernet 00:20:38:03:D8:52; # Client MAC<br /> fixed-address 129.57.29.54; # Client IP<br /> }<br /> &lt;/pre&gt;<br /> <br /> * Restart dhcpd<br /> service dhcpd restart<br /> <br /> = Configure Client OS =<br /> <br /> Here, we configure the OS that each and every Diskless Client will enjoy.<br /> <br /> === Setup of Diskless Kernel ===<br /> Run system-config-netboot (on TFTP server):<br /> system-config-netboot<br /> <br /> * In &quot;First Time Druid&quot; window. Click on &quot;Diskless&quot;<br /> # Click &quot;Forward&quot; on first page<br /> # Enter Name and Description.<br /> # Enter IP address of TFTP server and the &quot;root&quot; directory exported via NFS<br /> # Select a kernel<br /> # Click on Apply.<br /> : This will take a minute or two to compile a boot kernel for the diskless client.<br /> <br /> === Setup of chroot environment === <br /> There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br /> This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br /> chroot /diskless/x86_64/Centos5.5/root<br /> mount /proc /proc -t proc<br /> mkdir /u <br /> mkdir /group<br /> mkdir /daqfs<br /> mv /home /home.old<br /> ln -s /u/apps /apps<br /> ln -s /u/site /site<br /> ln -s /daqfs/home /home<br /> <br /> === Setup of diskless system configurations ===<br /> ''' Which NFS directories to mount '''<br /> * Add entry to &lt;code&gt;/etc/fstab&lt;/code&gt;<br /> phecda:/raid /daqfs nfs rw,soft,intr 0 0<br /> <br /> * Mount daqfs<br /> mount /daqfs<br /> <br /> ''' Which users/groups to allow access '''<br /> * Add entries to /etc/passwd<br /> +@da::::::<br /> +@ccc::::::<br /> +::::::/bin/false<br /> <br /> ''' A proxy for yum ''' (may be optional)<br /> * Add entry to /etc/yum.conf<br /> proxy=http://jprox:8080<br /> <br /> ''' domain servers for ypbind '''<br /> * Add entries to /etc/yp.conf<br /> domain CCCHP server nis2.jlab.org<br /> domain CCCHP server nis3.jlab.org<br /> <br /> * Make sure ypbind started at boot<br /> /sbin/chkconfig --level 345 nfs on <br /> <br /> ''' NTP setup ''' (optional... ntp must be installed)<br /> * Add entries to &lt;code&gt;/etc/ntp.conf&lt;/code&gt;<br /> server 127.0.0.1 # local clock<br /> fudge 127.0.0.1 stratum 10<br /> server ntp1.jlab.org<br /> server ntp2.jlab.org<br /> driftfile /etc/ntp/drift<br /> broadcastdelay 0.008<br /> authenticate no<br /> <br /> ''' Some additional JLab CUE directories to mount '''<br /> * Add entries to &lt;code&gt;/etc/auto.master&lt;/code&gt;<br /> /group /etc/auto.group --timeout=0<br /> /u auto.u.bb --DOSNAME=Linux-RHEL5<br /> <br /> ''' Additional files, not included in the standard diskless filesystem '''<br /> * Add a new file &lt;code&gt;/diskless/x86_64/Centos5.5/snapshot/files.custom&lt;/code&gt;. Entry:<br /> /tmp/<br /> /etc/minirc.dfl<br /> <br /> = Configure a NEW diskless client =<br /> This operation must be peformed to add a new Diskless Client. <br /> <br /> === Configuration on the tftp/NFS server ===<br /> * In &lt;code&gt;system-config-netboot&lt;/code&gt; &quot;Network Installation and Diskless Environment&quot; window:<br /> # Click on &quot;New&quot;<br /> # Enter hostname<br /> # Select OS<br /> # Enter &quot;CCCHP&quot; in Enable NISDOMAIN box.<br /> # Enter options in &quot;Edit Extra Kernel Boot Options&quot; &lt;br /&gt; &lt;code&gt;vga=0x305 acpi=force&lt;/code&gt;<br /> # Enter hostname as snapshot name. Make sure &quot;generate&quot; is check-marked<br /> # Click &quot;OK&quot;<br /> <br /> === Configuration on the Diskless Client ===<br /> * PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br /> <br /> = Other useful packages to install =<br /> Later on... I installed some other useful packages using the chroot environment. Here they are:<br /> <br /> * &lt;code&gt;xorg-x11-xauth&lt;/code&gt; - Required to run X-applications remotely<br /> * &lt;code&gt;ntp&lt;/code&gt; - Synchronize system clock with a central server<br /> : To Execute &lt;code&gt;ntpdate&lt;/code&gt; on server startup:<br /> :* Add &lt;code&gt;&lt;b&gt;-x&lt;/b&gt;&lt;/code&gt; to &lt;code&gt;OPTIONS&lt;/code&gt; in<br /> /etc/sysconfig/ntpd<br /> :* Make sure it starts on boot<br /> /sbin/chkconfig --level 345 nfs on</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=GE_XVB601&diff=5183 2011-03-29T19:12:03Z

<p>129.57.167.199: </p> <hr /> <div>Company site: [http://www.ge-ip.com/products/family/embedded-systems GE Intelligent Platforms]<br /> <br /> Board page on company site: [http://www.ge-ip.com/products/3448 XVB601]<br /> <br /> Documentation: [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_522-9300800627-000_A.book.pdf Installation Guide]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_Configuration_Guide_XVB601.pdf (pdf)]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_Ruggedization_Levels_GFA-926a.pdf (pdf)]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_xvb601_ds_gfa1299.pdf (pdf)]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_xvb601_hr_500-930007815-000_E.pdf (pdf)]<br /> <br /> == Customization for the CLON cluster ==<br /> <br /> '''List of boards'''<br /> <br /> * [01] 00:20:38:04:23:5E / 129.57.68.89 / croctest2<br /> <br /> '''Customizing kernel installed on the FLASH'''<br /> <br /> * ''/usr/bin/system-config-network''<br /> <br /> * fix ''/etc/passwd'', ''/etc/shadow'', ''/etc/group''<br /> <br /> * fix ''/etc/nsswitch.conf''<br /> <br /> * fix ''/etc/yp.conf'' (add lines ''domain CCCHP server clon00.jlab.org'' and ''ypserver clon10.jlab.org'')<br /> <br /> * fix ''/etc/sysconfig/network'' (add line ''NISDOMAIN=CCCHP'')<br /> <br /> * ''/etc/init.d/ypbind start''<br /> <br /> * ''chkconfig ypbind on''<br /> <br /> <br /> * set RHEL-style [[automounts]]<br /> <br /> * ''/etc/init.d/autofs restart''<br /> <br /> * fix symbolic links to /apps, /home, /usr/local etc<br /> <br /> <br /> <br /> '''Trying netboot following Bryan's instructions, using clonpc3'''<br /> <br /> * ''yum install system-config-netboot''<br /> <br /> * Change line (&lt;code&gt;/etc/xinetd.d/tftp&lt;/code&gt;):<br /> disable = yes<br /> : To<br /> disable = no<br /> <br /> * ''service xinetd restart''<br /> <br /> * Add these entries to &lt;code&gt;/etc/exports&lt;/code&gt;<br /> /diskless/x86_64/Centos5.5/root/ 129.57.167.0/255.255.255.0(ro,sync,no_root_squash)<br /> /diskless/x86_64/Centos5.5/snapshot/ 129.57.167.0/255.255.255.0(rw,sync,no_root_squash)<br /> : Where the &lt;code&gt;129.57.167.0/255.255.255.0&lt;/code&gt; only allows the 167 subnet to access these mounts.<br /> <br /> * Reload the NFS configuration or start NFS, if it's not started<br /> ''service nfs reload''<br /> <br /> * Make sure NFS is started at boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> * Enable remote syslog (optional)<br /> <br /> Change syslog argument in &lt;code&gt;/etc/sysconfig/syslog&lt;/code&gt; from:<br /> SYSLOGD_OPTIONS=&quot;-m 0&quot;<br /> :: To<br /> SYSLOGD_OPTIONS=&quot;-m 0 -r&quot;<br /> <br /> Restart syslogd<br /> service syslog restart<br /> <br /> '''DHCP Server Setup'''<br /> On the machine hosting the DHCP server.<br /> <br /> * Add an entry in &lt;code&gt;/etc/dhcpd.conf&lt;/code&gt;:<br /> &lt;pre&gt;<br /> host dafarm44<br /> {<br /> filename &quot;linux-install/pxelinux.0&quot;; # File location relative to /tftpboot/<br /> next-server 129.57.29.38; # TFTP server<br /> hardware ethernet 00:20:38:03:D8:52; # Client MAC<br /> fixed-address 129.57.29.54; # Client IP<br /> }<br /> &lt;/pre&gt;<br /> <br /> * Restart dhcpd<br /> service dhcpd restart<br /> <br /> '''Configure Client OS'''<br /> <br /> Here, we configure the OS that each and every Diskless Client will enjoy.<br /> <br /> '''Setup of Diskless Kernel'''<br /> Run system-config-netboot (on TFTP server):<br /> system-config-netboot<br /> <br /> * In &quot;First Time Druid&quot; window. Click on &quot;Diskless&quot;<br /> # Click &quot;Forward&quot; on first page<br /> # Enter Name and Description.<br /> # Enter IP address of TFTP server and the &quot;root&quot; directory exported via NFS<br /> # Select a kernel<br /> # Click on Apply.<br /> : This will take a minute or two to compile a boot kernel for the diskless client.<br /> <br /> '''Setup of chroot environment'''<br /> There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br /> This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br /> chroot /diskless/x86_64/Centos5.5/root<br /> mount /proc /proc -t proc<br /> mkdir /u <br /> mkdir /group<br /> mkdir /daqfs<br /> mv /home /home.old<br /> ln -s /u/apps /apps<br /> ln -s /u/site /site<br /> ln -s /daqfs/home /home<br /> <br /> '''Setup of diskless system configurations'''<br /> <br /> ''' Which NFS directories to mount '''<br /> <br /> * Add entry to &lt;code&gt;/etc/fstab&lt;/code&gt;<br /> phecda:/raid /daqfs nfs rw,soft,intr 0 0<br /> <br /> * Mount daqfs<br /> mount /daqfs<br /> <br /> ''' Which users/groups to allow access '''<br /> * Add entries to /etc/passwd<br /> +@da::::::<br /> +@ccc::::::<br /> +::::::/bin/false<br /> <br /> ''' A proxy for yum ''' (may be optional)<br /> * Add entry to /etc/yum.conf<br /> proxy=http://jprox:8080<br /> <br /> ''' domain servers for ypbind '''<br /> * Add entries to /etc/yp.conf<br /> domain CCCHP server nis2.jlab.org<br /> domain CCCHP server nis3.jlab.org<br /> <br /> * Make sure ypbind started at boot<br /> /sbin/chkconfig --level 345 nfs on <br /> <br /> ''' NTP setup ''' (optional... ntp must be installed)<br /> * Add entries to &lt;code&gt;/etc/ntp.conf&lt;/code&gt;<br /> server 127.0.0.1 # local clock<br /> fudge 127.0.0.1 stratum 10<br /> server ntp1.jlab.org<br /> server ntp2.jlab.org<br /> driftfile /etc/ntp/drift<br /> broadcastdelay 0.008<br /> authenticate no<br /> <br /> ''' Some additional JLab CUE directories to mount '''<br /> * Add entries to &lt;code&gt;/etc/auto.master&lt;/code&gt;<br /> /group /etc/auto.group --timeout=0<br /> /u auto.u.bb --DOSNAME=Linux-RHEL5<br /> <br /> ''' Additional files, not included in the standard diskless filesystem '''<br /> * Add a new file &lt;code&gt;/diskless/x86_64/Centos5.5/snapshot/files.custom&lt;/code&gt;. Entry:<br /> /tmp/<br /> /etc/minirc.dfl<br /> <br /> ''' Configure a NEW diskless client '''<br /> This operation must be peformed to add a new Diskless Client. <br /> <br /> ''' Configuration on the tftp/NFS server '''<br /> * In &lt;code&gt;system-config-netboot&lt;/code&gt; &quot;Network Installation and Diskless Environment&quot; window:<br /> # Click on &quot;New&quot;<br /> # Enter hostname<br /> # Select OS<br /> # Enter &quot;CCCHP&quot; in Enable NISDOMAIN box.<br /> # Enter options in &quot;Edit Extra Kernel Boot Options&quot; &lt;br /&gt; &lt;code&gt;vga=0x305 acpi=force&lt;/code&gt;<br /> # Enter hostname as snapshot name. Make sure &quot;generate&quot; is check-marked<br /> # Click &quot;OK&quot;<br /> <br /> ''' Configuration on the Diskless Client '''<br /> * PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br /> <br /> ''' Other useful packages to install '''<br /> Later on... I installed some other useful packages using the chroot environment. Here they are:<br /> <br /> * &lt;code&gt;xorg-x11-xauth&lt;/code&gt; - Required to run X-applications remotely<br /> * &lt;code&gt;ntp&lt;/code&gt; - Synchronize system clock with a central server<br /> : To Execute &lt;code&gt;ntpdate&lt;/code&gt; on server startup:<br /> :* Add &lt;code&gt;&lt;b&gt;-x&lt;/b&gt;&lt;/code&gt; to &lt;code&gt;OPTIONS&lt;/code&gt; in<br /> /etc/sysconfig/ntpd<br /> :* Make sure it starts on boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> == Network-based booting ==<br /> <br /> The page is geared towards the setup of Diskless nodes for Intel-based VME Controllers, but may be useful for similar other applications. Much of what is here was derived from the [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/3/html/System_Administration_Guide/ch-diskless.html Redhat Enterprise Linux 3 Documentation].<br /> <br /> This examples assumes:<br /> * The DHCP server (phecda: 129.57.29.104) has been installed and works. Here we're using the dhcp 3.0.1 package distributed by RHEL4.<br /> * The TFTP and NFS server (mizar: 129.57.29.100) is running RHEL5.5 x86_64.<br /> * The Diskless Client (dafarm44: 129.57.29.54) will run Centos 5.5 x86_64.<br /> <br /> There's nothing stopping you from having the DHCP server on the same machine as that servering TFTP and NFS. You can obviously have more than one diskless client.<br /> <br /> Once the first four steps have been completed, new clients can be configured individually with step 5.<br /> <br /> = Client Setup of OS in VirtualBox =<br /> Here, we've downloaded the latest and greatest Centos 5.5 x86_64 ISO and have set up a VirtualBox Client to use it to boot. We will not attempt to describe the VirtualBox installation or Setup of the ISO to boot as the VirtualBox Guest.<br /> <br /> The Centos 5.5 installation proceeds as normal installations go, but we opt to do a minimal installation (excluding KDE and/or GNOME components) since we're running on a VME controller. Other packages will be installed after first boot.<br /> <br /> === First Boot ===<br /> At first boot (after installation), a UI will appear and provide you with some options.:<br /> * Disable firewall and SELinux. SELinux setup can be double checked in the file:<br /> /etc/selinux/config<br /> * Disable sendmail, and other services not required for a VME controller<br /> <br /> === Update packages and transfer the OS to Server ===<br /> Login as root<br /> * Update all installed packages:<br /> yum update<br /> * Install the following packages, with:<br /> yum install &lt;i&gt;package&lt;/i&gt;<br /> :: busybox-anaconda<br /> :: gcc<br /> :: kernel-devel<br /> :: gdb<br /> :: valgrind<br /> :: cvs<br /> :: subversion<br /> :: compat-libstdc++-33<br /> :: redhat-rpm-config<br /> <br /> * Copy the Client OS to the tftp/NFS Server.<br /> ** On The Server:<br /> mkdir -p /diskless/x86_64/Centos5.5/root<br /> : In The VirtualBox Guest:<br /> rsync -Pav -e ssh --exclude='/proc/*' --exclude='/sys/*' / mizar:/diskless/x86_64/Centos5.5/root/<br /> <br /> You are now done with the Centos5.5 Guest installed in the VirtualBox. It can be closed down now.<br /> <br /> = tftp and NFS Server Setup =<br /> Follow these steps on the machine serving out tftp and NFS:<br /> <br /> ===Install &lt;code&gt;system-config-netboot&lt;/code&gt; ===<br /> (This should automatically install the tftp server)<br /> yum install system-config-netboot<br /> <br /> === Enable the tftp server to start at boot ===<br /> * Change line (&lt;code&gt;/etc/xinetd.d/tftp&lt;/code&gt;):<br /> disable = yes<br /> : To<br /> disable = no<br /> <br /> * Restart &lt;code&gt;xinetd&lt;/code&gt;<br /> service xinetd restart<br /> <br /> === Configure NFS ===<br /> * Add these entries to &lt;code&gt;/etc/exports&lt;/code&gt;<br /> /diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br /> /diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br /> : Where the &lt;code&gt;129.57.29.0/255.255.255.0&lt;/code&gt; only allows the 29 subnet to access these mounts.<br /> <br /> * Reload the NFS configuration or start NFS, if it's not started<br /> service nfs reload<br /> <br /> * Make sure NFS is started at boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> === Enable remote syslog (optional) ===<br /> * Change syslog argument in &lt;code&gt;/etc/sysconfig/syslog&lt;/code&gt; from:<br /> SYSLOGD_OPTIONS=&quot;-m 0&quot;<br /> :: To<br /> SYSLOGD_OPTIONS=&quot;-m 0 -r&quot;<br /> <br /> * Restart syslogd<br /> service syslog restart<br /> <br /> = DHCP Server Setup =<br /> On the machine hosting the DHCP server.<br /> <br /> * Add an entry in &lt;code&gt;/etc/dhcpd.conf&lt;/code&gt;:<br /> &lt;pre&gt;<br /> host dafarm44<br /> {<br /> filename &quot;linux-install/pxelinux.0&quot;; # File location relative to /tftpboot/<br /> next-server 129.57.29.38; # TFTP server<br /> hardware ethernet 00:20:38:03:D8:52; # Client MAC<br /> fixed-address 129.57.29.54; # Client IP<br /> }<br /> &lt;/pre&gt;<br /> <br /> * Restart dhcpd<br /> service dhcpd restart<br /> <br /> = Configure Client OS =<br /> <br /> Here, we configure the OS that each and every Diskless Client will enjoy.<br /> <br /> === Setup of Diskless Kernel ===<br /> Run system-config-netboot (on TFTP server):<br /> system-config-netboot<br /> <br /> * In &quot;First Time Druid&quot; window. Click on &quot;Diskless&quot;<br /> # Click &quot;Forward&quot; on first page<br /> # Enter Name and Description.<br /> # Enter IP address of TFTP server and the &quot;root&quot; directory exported via NFS<br /> # Select a kernel<br /> # Click on Apply.<br /> : This will take a minute or two to compile a boot kernel for the diskless client.<br /> <br /> === Setup of chroot environment === <br /> There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br /> This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br /> chroot /diskless/x86_64/Centos5.5/root<br /> mount /proc /proc -t proc<br /> mkdir /u <br /> mkdir /group<br /> mkdir /daqfs<br /> mv /home /home.old<br /> ln -s /u/apps /apps<br /> ln -s /u/site /site<br /> ln -s /daqfs/home /home<br /> <br /> === Setup of diskless system configurations ===<br /> ''' Which NFS directories to mount '''<br /> * Add entry to &lt;code&gt;/etc/fstab&lt;/code&gt;<br /> phecda:/raid /daqfs nfs rw,soft,intr 0 0<br /> <br /> * Mount daqfs<br /> mount /daqfs<br /> <br /> ''' Which users/groups to allow access '''<br /> * Add entries to /etc/passwd<br /> +@da::::::<br /> +@ccc::::::<br /> +::::::/bin/false<br /> <br /> ''' A proxy for yum ''' (may be optional)<br /> * Add entry to /etc/yum.conf<br /> proxy=http://jprox:8080<br /> <br /> ''' domain servers for ypbind '''<br /> * Add entries to /etc/yp.conf<br /> domain CCCHP server nis2.jlab.org<br /> domain CCCHP server nis3.jlab.org<br /> <br /> * Make sure ypbind started at boot<br /> /sbin/chkconfig --level 345 nfs on <br /> <br /> ''' NTP setup ''' (optional... ntp must be installed)<br /> * Add entries to &lt;code&gt;/etc/ntp.conf&lt;/code&gt;<br /> server 127.0.0.1 # local clock<br /> fudge 127.0.0.1 stratum 10<br /> server ntp1.jlab.org<br /> server ntp2.jlab.org<br /> driftfile /etc/ntp/drift<br /> broadcastdelay 0.008<br /> authenticate no<br /> <br /> ''' Some additional JLab CUE directories to mount '''<br /> * Add entries to &lt;code&gt;/etc/auto.master&lt;/code&gt;<br /> /group /etc/auto.group --timeout=0<br /> /u auto.u.bb --DOSNAME=Linux-RHEL5<br /> <br /> ''' Additional files, not included in the standard diskless filesystem '''<br /> * Add a new file &lt;code&gt;/diskless/x86_64/Centos5.5/snapshot/files.custom&lt;/code&gt;. Entry:<br /> /tmp/<br /> /etc/minirc.dfl<br /> <br /> = Configure a NEW diskless client =<br /> This operation must be peformed to add a new Diskless Client. <br /> <br /> === Configuration on the tftp/NFS server ===<br /> * In &lt;code&gt;system-config-netboot&lt;/code&gt; &quot;Network Installation and Diskless Environment&quot; window:<br /> # Click on &quot;New&quot;<br /> # Enter hostname<br /> # Select OS<br /> # Enter &quot;CCCHP&quot; in Enable NISDOMAIN box.<br /> # Enter options in &quot;Edit Extra Kernel Boot Options&quot; &lt;br /&gt; &lt;code&gt;vga=0x305 acpi=force&lt;/code&gt;<br /> # Enter hostname as snapshot name. Make sure &quot;generate&quot; is check-marked<br /> # Click &quot;OK&quot;<br /> <br /> === Configuration on the Diskless Client ===<br /> * PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br /> <br /> = Other useful packages to install =<br /> Later on... I installed some other useful packages using the chroot environment. Here they are:<br /> <br /> * &lt;code&gt;xorg-x11-xauth&lt;/code&gt; - Required to run X-applications remotely<br /> * &lt;code&gt;ntp&lt;/code&gt; - Synchronize system clock with a central server<br /> : To Execute &lt;code&gt;ntpdate&lt;/code&gt; on server startup:<br /> :* Add &lt;code&gt;&lt;b&gt;-x&lt;/b&gt;&lt;/code&gt; to &lt;code&gt;OPTIONS&lt;/code&gt; in<br /> /etc/sysconfig/ntpd<br /> :* Make sure it starts on boot<br /> /sbin/chkconfig --level 345 nfs on</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=GE_XVB601&diff=5182 2011-03-29T19:11:45Z

<p>129.57.167.199: </p> <hr /> <div>Company site: [http://www.ge-ip.com/products/family/embedded-systems GE Intelligent Platforms]<br /> <br /> Board page on company site: [http://www.ge-ip.com/products/3448 XVB601]<br /> <br /> Documentation: [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_522-9300800627-000_A.book.pdf (Installation Guide)]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_Configuration_Guide_XVB601.pdf (pdf)]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_Ruggedization_Levels_GFA-926a.pdf (pdf)]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_xvb601_ds_gfa1299.pdf (pdf)]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_xvb601_hr_500-930007815-000_E.pdf (pdf)]<br /> <br /> == Customization for the CLON cluster ==<br /> <br /> '''List of boards'''<br /> <br /> * [01] 00:20:38:04:23:5E / 129.57.68.89 / croctest2<br /> <br /> '''Customizing kernel installed on the FLASH'''<br /> <br /> * ''/usr/bin/system-config-network''<br /> <br /> * fix ''/etc/passwd'', ''/etc/shadow'', ''/etc/group''<br /> <br /> * fix ''/etc/nsswitch.conf''<br /> <br /> * fix ''/etc/yp.conf'' (add lines ''domain CCCHP server clon00.jlab.org'' and ''ypserver clon10.jlab.org'')<br /> <br /> * fix ''/etc/sysconfig/network'' (add line ''NISDOMAIN=CCCHP'')<br /> <br /> * ''/etc/init.d/ypbind start''<br /> <br /> * ''chkconfig ypbind on''<br /> <br /> <br /> * set RHEL-style [[automounts]]<br /> <br /> * ''/etc/init.d/autofs restart''<br /> <br /> * fix symbolic links to /apps, /home, /usr/local etc<br /> <br /> <br /> <br /> '''Trying netboot following Bryan's instructions, using clonpc3'''<br /> <br /> * ''yum install system-config-netboot''<br /> <br /> * Change line (&lt;code&gt;/etc/xinetd.d/tftp&lt;/code&gt;):<br /> disable = yes<br /> : To<br /> disable = no<br /> <br /> * ''service xinetd restart''<br /> <br /> * Add these entries to &lt;code&gt;/etc/exports&lt;/code&gt;<br /> /diskless/x86_64/Centos5.5/root/ 129.57.167.0/255.255.255.0(ro,sync,no_root_squash)<br /> /diskless/x86_64/Centos5.5/snapshot/ 129.57.167.0/255.255.255.0(rw,sync,no_root_squash)<br /> : Where the &lt;code&gt;129.57.167.0/255.255.255.0&lt;/code&gt; only allows the 167 subnet to access these mounts.<br /> <br /> * Reload the NFS configuration or start NFS, if it's not started<br /> ''service nfs reload''<br /> <br /> * Make sure NFS is started at boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> * Enable remote syslog (optional)<br /> <br /> Change syslog argument in &lt;code&gt;/etc/sysconfig/syslog&lt;/code&gt; from:<br /> SYSLOGD_OPTIONS=&quot;-m 0&quot;<br /> :: To<br /> SYSLOGD_OPTIONS=&quot;-m 0 -r&quot;<br /> <br /> Restart syslogd<br /> service syslog restart<br /> <br /> '''DHCP Server Setup'''<br /> On the machine hosting the DHCP server.<br /> <br /> * Add an entry in &lt;code&gt;/etc/dhcpd.conf&lt;/code&gt;:<br /> &lt;pre&gt;<br /> host dafarm44<br /> {<br /> filename &quot;linux-install/pxelinux.0&quot;; # File location relative to /tftpboot/<br /> next-server 129.57.29.38; # TFTP server<br /> hardware ethernet 00:20:38:03:D8:52; # Client MAC<br /> fixed-address 129.57.29.54; # Client IP<br /> }<br /> &lt;/pre&gt;<br /> <br /> * Restart dhcpd<br /> service dhcpd restart<br /> <br /> '''Configure Client OS'''<br /> <br /> Here, we configure the OS that each and every Diskless Client will enjoy.<br /> <br /> '''Setup of Diskless Kernel'''<br /> Run system-config-netboot (on TFTP server):<br /> system-config-netboot<br /> <br /> * In &quot;First Time Druid&quot; window. Click on &quot;Diskless&quot;<br /> # Click &quot;Forward&quot; on first page<br /> # Enter Name and Description.<br /> # Enter IP address of TFTP server and the &quot;root&quot; directory exported via NFS<br /> # Select a kernel<br /> # Click on Apply.<br /> : This will take a minute or two to compile a boot kernel for the diskless client.<br /> <br /> '''Setup of chroot environment'''<br /> There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br /> This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br /> chroot /diskless/x86_64/Centos5.5/root<br /> mount /proc /proc -t proc<br /> mkdir /u <br /> mkdir /group<br /> mkdir /daqfs<br /> mv /home /home.old<br /> ln -s /u/apps /apps<br /> ln -s /u/site /site<br /> ln -s /daqfs/home /home<br /> <br /> '''Setup of diskless system configurations'''<br /> <br /> ''' Which NFS directories to mount '''<br /> <br /> * Add entry to &lt;code&gt;/etc/fstab&lt;/code&gt;<br /> phecda:/raid /daqfs nfs rw,soft,intr 0 0<br /> <br /> * Mount daqfs<br /> mount /daqfs<br /> <br /> ''' Which users/groups to allow access '''<br /> * Add entries to /etc/passwd<br /> +@da::::::<br /> +@ccc::::::<br /> +::::::/bin/false<br /> <br /> ''' A proxy for yum ''' (may be optional)<br /> * Add entry to /etc/yum.conf<br /> proxy=http://jprox:8080<br /> <br /> ''' domain servers for ypbind '''<br /> * Add entries to /etc/yp.conf<br /> domain CCCHP server nis2.jlab.org<br /> domain CCCHP server nis3.jlab.org<br /> <br /> * Make sure ypbind started at boot<br /> /sbin/chkconfig --level 345 nfs on <br /> <br /> ''' NTP setup ''' (optional... ntp must be installed)<br /> * Add entries to &lt;code&gt;/etc/ntp.conf&lt;/code&gt;<br /> server 127.0.0.1 # local clock<br /> fudge 127.0.0.1 stratum 10<br /> server ntp1.jlab.org<br /> server ntp2.jlab.org<br /> driftfile /etc/ntp/drift<br /> broadcastdelay 0.008<br /> authenticate no<br /> <br /> ''' Some additional JLab CUE directories to mount '''<br /> * Add entries to &lt;code&gt;/etc/auto.master&lt;/code&gt;<br /> /group /etc/auto.group --timeout=0<br /> /u auto.u.bb --DOSNAME=Linux-RHEL5<br /> <br /> ''' Additional files, not included in the standard diskless filesystem '''<br /> * Add a new file &lt;code&gt;/diskless/x86_64/Centos5.5/snapshot/files.custom&lt;/code&gt;. Entry:<br /> /tmp/<br /> /etc/minirc.dfl<br /> <br /> ''' Configure a NEW diskless client '''<br /> This operation must be peformed to add a new Diskless Client. <br /> <br /> ''' Configuration on the tftp/NFS server '''<br /> * In &lt;code&gt;system-config-netboot&lt;/code&gt; &quot;Network Installation and Diskless Environment&quot; window:<br /> # Click on &quot;New&quot;<br /> # Enter hostname<br /> # Select OS<br /> # Enter &quot;CCCHP&quot; in Enable NISDOMAIN box.<br /> # Enter options in &quot;Edit Extra Kernel Boot Options&quot; &lt;br /&gt; &lt;code&gt;vga=0x305 acpi=force&lt;/code&gt;<br /> # Enter hostname as snapshot name. Make sure &quot;generate&quot; is check-marked<br /> # Click &quot;OK&quot;<br /> <br /> ''' Configuration on the Diskless Client '''<br /> * PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br /> <br /> ''' Other useful packages to install '''<br /> Later on... I installed some other useful packages using the chroot environment. Here they are:<br /> <br /> * &lt;code&gt;xorg-x11-xauth&lt;/code&gt; - Required to run X-applications remotely<br /> * &lt;code&gt;ntp&lt;/code&gt; - Synchronize system clock with a central server<br /> : To Execute &lt;code&gt;ntpdate&lt;/code&gt; on server startup:<br /> :* Add &lt;code&gt;&lt;b&gt;-x&lt;/b&gt;&lt;/code&gt; to &lt;code&gt;OPTIONS&lt;/code&gt; in<br /> /etc/sysconfig/ntpd<br /> :* Make sure it starts on boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> == Network-based booting ==<br /> <br /> The page is geared towards the setup of Diskless nodes for Intel-based VME Controllers, but may be useful for similar other applications. Much of what is here was derived from the [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/3/html/System_Administration_Guide/ch-diskless.html Redhat Enterprise Linux 3 Documentation].<br /> <br /> This examples assumes:<br /> * The DHCP server (phecda: 129.57.29.104) has been installed and works. Here we're using the dhcp 3.0.1 package distributed by RHEL4.<br /> * The TFTP and NFS server (mizar: 129.57.29.100) is running RHEL5.5 x86_64.<br /> * The Diskless Client (dafarm44: 129.57.29.54) will run Centos 5.5 x86_64.<br /> <br /> There's nothing stopping you from having the DHCP server on the same machine as that servering TFTP and NFS. You can obviously have more than one diskless client.<br /> <br /> Once the first four steps have been completed, new clients can be configured individually with step 5.<br /> <br /> = Client Setup of OS in VirtualBox =<br /> Here, we've downloaded the latest and greatest Centos 5.5 x86_64 ISO and have set up a VirtualBox Client to use it to boot. We will not attempt to describe the VirtualBox installation or Setup of the ISO to boot as the VirtualBox Guest.<br /> <br /> The Centos 5.5 installation proceeds as normal installations go, but we opt to do a minimal installation (excluding KDE and/or GNOME components) since we're running on a VME controller. Other packages will be installed after first boot.<br /> <br /> === First Boot ===<br /> At first boot (after installation), a UI will appear and provide you with some options.:<br /> * Disable firewall and SELinux. SELinux setup can be double checked in the file:<br /> /etc/selinux/config<br /> * Disable sendmail, and other services not required for a VME controller<br /> <br /> === Update packages and transfer the OS to Server ===<br /> Login as root<br /> * Update all installed packages:<br /> yum update<br /> * Install the following packages, with:<br /> yum install &lt;i&gt;package&lt;/i&gt;<br /> :: busybox-anaconda<br /> :: gcc<br /> :: kernel-devel<br /> :: gdb<br /> :: valgrind<br /> :: cvs<br /> :: subversion<br /> :: compat-libstdc++-33<br /> :: redhat-rpm-config<br /> <br /> * Copy the Client OS to the tftp/NFS Server.<br /> ** On The Server:<br /> mkdir -p /diskless/x86_64/Centos5.5/root<br /> : In The VirtualBox Guest:<br /> rsync -Pav -e ssh --exclude='/proc/*' --exclude='/sys/*' / mizar:/diskless/x86_64/Centos5.5/root/<br /> <br /> You are now done with the Centos5.5 Guest installed in the VirtualBox. It can be closed down now.<br /> <br /> = tftp and NFS Server Setup =<br /> Follow these steps on the machine serving out tftp and NFS:<br /> <br /> ===Install &lt;code&gt;system-config-netboot&lt;/code&gt; ===<br /> (This should automatically install the tftp server)<br /> yum install system-config-netboot<br /> <br /> === Enable the tftp server to start at boot ===<br /> * Change line (&lt;code&gt;/etc/xinetd.d/tftp&lt;/code&gt;):<br /> disable = yes<br /> : To<br /> disable = no<br /> <br /> * Restart &lt;code&gt;xinetd&lt;/code&gt;<br /> service xinetd restart<br /> <br /> === Configure NFS ===<br /> * Add these entries to &lt;code&gt;/etc/exports&lt;/code&gt;<br /> /diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br /> /diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br /> : Where the &lt;code&gt;129.57.29.0/255.255.255.0&lt;/code&gt; only allows the 29 subnet to access these mounts.<br /> <br /> * Reload the NFS configuration or start NFS, if it's not started<br /> service nfs reload<br /> <br /> * Make sure NFS is started at boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> === Enable remote syslog (optional) ===<br /> * Change syslog argument in &lt;code&gt;/etc/sysconfig/syslog&lt;/code&gt; from:<br /> SYSLOGD_OPTIONS=&quot;-m 0&quot;<br /> :: To<br /> SYSLOGD_OPTIONS=&quot;-m 0 -r&quot;<br /> <br /> * Restart syslogd<br /> service syslog restart<br /> <br /> = DHCP Server Setup =<br /> On the machine hosting the DHCP server.<br /> <br /> * Add an entry in &lt;code&gt;/etc/dhcpd.conf&lt;/code&gt;:<br /> &lt;pre&gt;<br /> host dafarm44<br /> {<br /> filename &quot;linux-install/pxelinux.0&quot;; # File location relative to /tftpboot/<br /> next-server 129.57.29.38; # TFTP server<br /> hardware ethernet 00:20:38:03:D8:52; # Client MAC<br /> fixed-address 129.57.29.54; # Client IP<br /> }<br /> &lt;/pre&gt;<br /> <br /> * Restart dhcpd<br /> service dhcpd restart<br /> <br /> = Configure Client OS =<br /> <br /> Here, we configure the OS that each and every Diskless Client will enjoy.<br /> <br /> === Setup of Diskless Kernel ===<br /> Run system-config-netboot (on TFTP server):<br /> system-config-netboot<br /> <br /> * In &quot;First Time Druid&quot; window. Click on &quot;Diskless&quot;<br /> # Click &quot;Forward&quot; on first page<br /> # Enter Name and Description.<br /> # Enter IP address of TFTP server and the &quot;root&quot; directory exported via NFS<br /> # Select a kernel<br /> # Click on Apply.<br /> : This will take a minute or two to compile a boot kernel for the diskless client.<br /> <br /> === Setup of chroot environment === <br /> There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br /> This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br /> chroot /diskless/x86_64/Centos5.5/root<br /> mount /proc /proc -t proc<br /> mkdir /u <br /> mkdir /group<br /> mkdir /daqfs<br /> mv /home /home.old<br /> ln -s /u/apps /apps<br /> ln -s /u/site /site<br /> ln -s /daqfs/home /home<br /> <br /> === Setup of diskless system configurations ===<br /> ''' Which NFS directories to mount '''<br /> * Add entry to &lt;code&gt;/etc/fstab&lt;/code&gt;<br /> phecda:/raid /daqfs nfs rw,soft,intr 0 0<br /> <br /> * Mount daqfs<br /> mount /daqfs<br /> <br /> ''' Which users/groups to allow access '''<br /> * Add entries to /etc/passwd<br /> +@da::::::<br /> +@ccc::::::<br /> +::::::/bin/false<br /> <br /> ''' A proxy for yum ''' (may be optional)<br /> * Add entry to /etc/yum.conf<br /> proxy=http://jprox:8080<br /> <br /> ''' domain servers for ypbind '''<br /> * Add entries to /etc/yp.conf<br /> domain CCCHP server nis2.jlab.org<br /> domain CCCHP server nis3.jlab.org<br /> <br /> * Make sure ypbind started at boot<br /> /sbin/chkconfig --level 345 nfs on <br /> <br /> ''' NTP setup ''' (optional... ntp must be installed)<br /> * Add entries to &lt;code&gt;/etc/ntp.conf&lt;/code&gt;<br /> server 127.0.0.1 # local clock<br /> fudge 127.0.0.1 stratum 10<br /> server ntp1.jlab.org<br /> server ntp2.jlab.org<br /> driftfile /etc/ntp/drift<br /> broadcastdelay 0.008<br /> authenticate no<br /> <br /> ''' Some additional JLab CUE directories to mount '''<br /> * Add entries to &lt;code&gt;/etc/auto.master&lt;/code&gt;<br /> /group /etc/auto.group --timeout=0<br /> /u auto.u.bb --DOSNAME=Linux-RHEL5<br /> <br /> ''' Additional files, not included in the standard diskless filesystem '''<br /> * Add a new file &lt;code&gt;/diskless/x86_64/Centos5.5/snapshot/files.custom&lt;/code&gt;. Entry:<br /> /tmp/<br /> /etc/minirc.dfl<br /> <br /> = Configure a NEW diskless client =<br /> This operation must be peformed to add a new Diskless Client. <br /> <br /> === Configuration on the tftp/NFS server ===<br /> * In &lt;code&gt;system-config-netboot&lt;/code&gt; &quot;Network Installation and Diskless Environment&quot; window:<br /> # Click on &quot;New&quot;<br /> # Enter hostname<br /> # Select OS<br /> # Enter &quot;CCCHP&quot; in Enable NISDOMAIN box.<br /> # Enter options in &quot;Edit Extra Kernel Boot Options&quot; &lt;br /&gt; &lt;code&gt;vga=0x305 acpi=force&lt;/code&gt;<br /> # Enter hostname as snapshot name. Make sure &quot;generate&quot; is check-marked<br /> # Click &quot;OK&quot;<br /> <br /> === Configuration on the Diskless Client ===<br /> * PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br /> <br /> = Other useful packages to install =<br /> Later on... I installed some other useful packages using the chroot environment. Here they are:<br /> <br /> * &lt;code&gt;xorg-x11-xauth&lt;/code&gt; - Required to run X-applications remotely<br /> * &lt;code&gt;ntp&lt;/code&gt; - Synchronize system clock with a central server<br /> : To Execute &lt;code&gt;ntpdate&lt;/code&gt; on server startup:<br /> :* Add &lt;code&gt;&lt;b&gt;-x&lt;/b&gt;&lt;/code&gt; to &lt;code&gt;OPTIONS&lt;/code&gt; in<br /> /etc/sysconfig/ntpd<br /> :* Make sure it starts on boot<br /> /sbin/chkconfig --level 345 nfs on</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=GE_XVB601&diff=5181 2011-03-29T19:11:17Z

<p>129.57.167.199: </p> <hr /> <div>Company site: [http://www.ge-ip.com/products/family/embedded-systems GE Intelligent Platforms]<br /> <br /> Board page on company site: [http://www.ge-ip.com/products/3448 XVB601]<br /> <br /> Documentation: [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_522-9300800627-000_A.book.pdf (pdf)]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_Configuration_Guide_XVB601.pdf (pdf)]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_Ruggedization_Levels_GFA-926a.pdf (pdf)]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_xvb601_ds_gfa1299.pdf (pdf)]<br /> [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_xvb601_hr_500-930007815-000_E.pdf (pdf)]<br /> <br /> == Customization for the CLON cluster ==<br /> <br /> '''List of boards'''<br /> <br /> * [01] 00:20:38:04:23:5E / 129.57.68.89 / croctest2<br /> <br /> '''Customizing kernel installed on the FLASH'''<br /> <br /> * ''/usr/bin/system-config-network''<br /> <br /> * fix ''/etc/passwd'', ''/etc/shadow'', ''/etc/group''<br /> <br /> * fix ''/etc/nsswitch.conf''<br /> <br /> * fix ''/etc/yp.conf'' (add lines ''domain CCCHP server clon00.jlab.org'' and ''ypserver clon10.jlab.org'')<br /> <br /> * fix ''/etc/sysconfig/network'' (add line ''NISDOMAIN=CCCHP'')<br /> <br /> * ''/etc/init.d/ypbind start''<br /> <br /> * ''chkconfig ypbind on''<br /> <br /> <br /> * set RHEL-style [[automounts]]<br /> <br /> * ''/etc/init.d/autofs restart''<br /> <br /> * fix symbolic links to /apps, /home, /usr/local etc<br /> <br /> <br /> <br /> '''Trying netboot following Bryan's instructions, using clonpc3'''<br /> <br /> * ''yum install system-config-netboot''<br /> <br /> * Change line (&lt;code&gt;/etc/xinetd.d/tftp&lt;/code&gt;):<br /> disable = yes<br /> : To<br /> disable = no<br /> <br /> * ''service xinetd restart''<br /> <br /> * Add these entries to &lt;code&gt;/etc/exports&lt;/code&gt;<br /> /diskless/x86_64/Centos5.5/root/ 129.57.167.0/255.255.255.0(ro,sync,no_root_squash)<br /> /diskless/x86_64/Centos5.5/snapshot/ 129.57.167.0/255.255.255.0(rw,sync,no_root_squash)<br /> : Where the &lt;code&gt;129.57.167.0/255.255.255.0&lt;/code&gt; only allows the 167 subnet to access these mounts.<br /> <br /> * Reload the NFS configuration or start NFS, if it's not started<br /> ''service nfs reload''<br /> <br /> * Make sure NFS is started at boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> * Enable remote syslog (optional)<br /> <br /> Change syslog argument in &lt;code&gt;/etc/sysconfig/syslog&lt;/code&gt; from:<br /> SYSLOGD_OPTIONS=&quot;-m 0&quot;<br /> :: To<br /> SYSLOGD_OPTIONS=&quot;-m 0 -r&quot;<br /> <br /> Restart syslogd<br /> service syslog restart<br /> <br /> '''DHCP Server Setup'''<br /> On the machine hosting the DHCP server.<br /> <br /> * Add an entry in &lt;code&gt;/etc/dhcpd.conf&lt;/code&gt;:<br /> &lt;pre&gt;<br /> host dafarm44<br /> {<br /> filename &quot;linux-install/pxelinux.0&quot;; # File location relative to /tftpboot/<br /> next-server 129.57.29.38; # TFTP server<br /> hardware ethernet 00:20:38:03:D8:52; # Client MAC<br /> fixed-address 129.57.29.54; # Client IP<br /> }<br /> &lt;/pre&gt;<br /> <br /> * Restart dhcpd<br /> service dhcpd restart<br /> <br /> '''Configure Client OS'''<br /> <br /> Here, we configure the OS that each and every Diskless Client will enjoy.<br /> <br /> '''Setup of Diskless Kernel'''<br /> Run system-config-netboot (on TFTP server):<br /> system-config-netboot<br /> <br /> * In &quot;First Time Druid&quot; window. Click on &quot;Diskless&quot;<br /> # Click &quot;Forward&quot; on first page<br /> # Enter Name and Description.<br /> # Enter IP address of TFTP server and the &quot;root&quot; directory exported via NFS<br /> # Select a kernel<br /> # Click on Apply.<br /> : This will take a minute or two to compile a boot kernel for the diskless client.<br /> <br /> '''Setup of chroot environment'''<br /> There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br /> This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br /> chroot /diskless/x86_64/Centos5.5/root<br /> mount /proc /proc -t proc<br /> mkdir /u <br /> mkdir /group<br /> mkdir /daqfs<br /> mv /home /home.old<br /> ln -s /u/apps /apps<br /> ln -s /u/site /site<br /> ln -s /daqfs/home /home<br /> <br /> '''Setup of diskless system configurations'''<br /> <br /> ''' Which NFS directories to mount '''<br /> <br /> * Add entry to &lt;code&gt;/etc/fstab&lt;/code&gt;<br /> phecda:/raid /daqfs nfs rw,soft,intr 0 0<br /> <br /> * Mount daqfs<br /> mount /daqfs<br /> <br /> ''' Which users/groups to allow access '''<br /> * Add entries to /etc/passwd<br /> +@da::::::<br /> +@ccc::::::<br /> +::::::/bin/false<br /> <br /> ''' A proxy for yum ''' (may be optional)<br /> * Add entry to /etc/yum.conf<br /> proxy=http://jprox:8080<br /> <br /> ''' domain servers for ypbind '''<br /> * Add entries to /etc/yp.conf<br /> domain CCCHP server nis2.jlab.org<br /> domain CCCHP server nis3.jlab.org<br /> <br /> * Make sure ypbind started at boot<br /> /sbin/chkconfig --level 345 nfs on <br /> <br /> ''' NTP setup ''' (optional... ntp must be installed)<br /> * Add entries to &lt;code&gt;/etc/ntp.conf&lt;/code&gt;<br /> server 127.0.0.1 # local clock<br /> fudge 127.0.0.1 stratum 10<br /> server ntp1.jlab.org<br /> server ntp2.jlab.org<br /> driftfile /etc/ntp/drift<br /> broadcastdelay 0.008<br /> authenticate no<br /> <br /> ''' Some additional JLab CUE directories to mount '''<br /> * Add entries to &lt;code&gt;/etc/auto.master&lt;/code&gt;<br /> /group /etc/auto.group --timeout=0<br /> /u auto.u.bb --DOSNAME=Linux-RHEL5<br /> <br /> ''' Additional files, not included in the standard diskless filesystem '''<br /> * Add a new file &lt;code&gt;/diskless/x86_64/Centos5.5/snapshot/files.custom&lt;/code&gt;. Entry:<br /> /tmp/<br /> /etc/minirc.dfl<br /> <br /> ''' Configure a NEW diskless client '''<br /> This operation must be peformed to add a new Diskless Client. <br /> <br /> ''' Configuration on the tftp/NFS server '''<br /> * In &lt;code&gt;system-config-netboot&lt;/code&gt; &quot;Network Installation and Diskless Environment&quot; window:<br /> # Click on &quot;New&quot;<br /> # Enter hostname<br /> # Select OS<br /> # Enter &quot;CCCHP&quot; in Enable NISDOMAIN box.<br /> # Enter options in &quot;Edit Extra Kernel Boot Options&quot; &lt;br /&gt; &lt;code&gt;vga=0x305 acpi=force&lt;/code&gt;<br /> # Enter hostname as snapshot name. Make sure &quot;generate&quot; is check-marked<br /> # Click &quot;OK&quot;<br /> <br /> ''' Configuration on the Diskless Client '''<br /> * PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br /> <br /> ''' Other useful packages to install '''<br /> Later on... I installed some other useful packages using the chroot environment. Here they are:<br /> <br /> * &lt;code&gt;xorg-x11-xauth&lt;/code&gt; - Required to run X-applications remotely<br /> * &lt;code&gt;ntp&lt;/code&gt; - Synchronize system clock with a central server<br /> : To Execute &lt;code&gt;ntpdate&lt;/code&gt; on server startup:<br /> :* Add &lt;code&gt;&lt;b&gt;-x&lt;/b&gt;&lt;/code&gt; to &lt;code&gt;OPTIONS&lt;/code&gt; in<br /> /etc/sysconfig/ntpd<br /> :* Make sure it starts on boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> == Network-based booting ==<br /> <br /> The page is geared towards the setup of Diskless nodes for Intel-based VME Controllers, but may be useful for similar other applications. Much of what is here was derived from the [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/3/html/System_Administration_Guide/ch-diskless.html Redhat Enterprise Linux 3 Documentation].<br /> <br /> This examples assumes:<br /> * The DHCP server (phecda: 129.57.29.104) has been installed and works. Here we're using the dhcp 3.0.1 package distributed by RHEL4.<br /> * The TFTP and NFS server (mizar: 129.57.29.100) is running RHEL5.5 x86_64.<br /> * The Diskless Client (dafarm44: 129.57.29.54) will run Centos 5.5 x86_64.<br /> <br /> There's nothing stopping you from having the DHCP server on the same machine as that servering TFTP and NFS. You can obviously have more than one diskless client.<br /> <br /> Once the first four steps have been completed, new clients can be configured individually with step 5.<br /> <br /> = Client Setup of OS in VirtualBox =<br /> Here, we've downloaded the latest and greatest Centos 5.5 x86_64 ISO and have set up a VirtualBox Client to use it to boot. We will not attempt to describe the VirtualBox installation or Setup of the ISO to boot as the VirtualBox Guest.<br /> <br /> The Centos 5.5 installation proceeds as normal installations go, but we opt to do a minimal installation (excluding KDE and/or GNOME components) since we're running on a VME controller. Other packages will be installed after first boot.<br /> <br /> === First Boot ===<br /> At first boot (after installation), a UI will appear and provide you with some options.:<br /> * Disable firewall and SELinux. SELinux setup can be double checked in the file:<br /> /etc/selinux/config<br /> * Disable sendmail, and other services not required for a VME controller<br /> <br /> === Update packages and transfer the OS to Server ===<br /> Login as root<br /> * Update all installed packages:<br /> yum update<br /> * Install the following packages, with:<br /> yum install &lt;i&gt;package&lt;/i&gt;<br /> :: busybox-anaconda<br /> :: gcc<br /> :: kernel-devel<br /> :: gdb<br /> :: valgrind<br /> :: cvs<br /> :: subversion<br /> :: compat-libstdc++-33<br /> :: redhat-rpm-config<br /> <br /> * Copy the Client OS to the tftp/NFS Server.<br /> ** On The Server:<br /> mkdir -p /diskless/x86_64/Centos5.5/root<br /> : In The VirtualBox Guest:<br /> rsync -Pav -e ssh --exclude='/proc/*' --exclude='/sys/*' / mizar:/diskless/x86_64/Centos5.5/root/<br /> <br /> You are now done with the Centos5.5 Guest installed in the VirtualBox. It can be closed down now.<br /> <br /> = tftp and NFS Server Setup =<br /> Follow these steps on the machine serving out tftp and NFS:<br /> <br /> ===Install &lt;code&gt;system-config-netboot&lt;/code&gt; ===<br /> (This should automatically install the tftp server)<br /> yum install system-config-netboot<br /> <br /> === Enable the tftp server to start at boot ===<br /> * Change line (&lt;code&gt;/etc/xinetd.d/tftp&lt;/code&gt;):<br /> disable = yes<br /> : To<br /> disable = no<br /> <br /> * Restart &lt;code&gt;xinetd&lt;/code&gt;<br /> service xinetd restart<br /> <br /> === Configure NFS ===<br /> * Add these entries to &lt;code&gt;/etc/exports&lt;/code&gt;<br /> /diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br /> /diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br /> : Where the &lt;code&gt;129.57.29.0/255.255.255.0&lt;/code&gt; only allows the 29 subnet to access these mounts.<br /> <br /> * Reload the NFS configuration or start NFS, if it's not started<br /> service nfs reload<br /> <br /> * Make sure NFS is started at boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> === Enable remote syslog (optional) ===<br /> * Change syslog argument in &lt;code&gt;/etc/sysconfig/syslog&lt;/code&gt; from:<br /> SYSLOGD_OPTIONS=&quot;-m 0&quot;<br /> :: To<br /> SYSLOGD_OPTIONS=&quot;-m 0 -r&quot;<br /> <br /> * Restart syslogd<br /> service syslog restart<br /> <br /> = DHCP Server Setup =<br /> On the machine hosting the DHCP server.<br /> <br /> * Add an entry in &lt;code&gt;/etc/dhcpd.conf&lt;/code&gt;:<br /> &lt;pre&gt;<br /> host dafarm44<br /> {<br /> filename &quot;linux-install/pxelinux.0&quot;; # File location relative to /tftpboot/<br /> next-server 129.57.29.38; # TFTP server<br /> hardware ethernet 00:20:38:03:D8:52; # Client MAC<br /> fixed-address 129.57.29.54; # Client IP<br /> }<br /> &lt;/pre&gt;<br /> <br /> * Restart dhcpd<br /> service dhcpd restart<br /> <br /> = Configure Client OS =<br /> <br /> Here, we configure the OS that each and every Diskless Client will enjoy.<br /> <br /> === Setup of Diskless Kernel ===<br /> Run system-config-netboot (on TFTP server):<br /> system-config-netboot<br /> <br /> * In &quot;First Time Druid&quot; window. Click on &quot;Diskless&quot;<br /> # Click &quot;Forward&quot; on first page<br /> # Enter Name and Description.<br /> # Enter IP address of TFTP server and the &quot;root&quot; directory exported via NFS<br /> # Select a kernel<br /> # Click on Apply.<br /> : This will take a minute or two to compile a boot kernel for the diskless client.<br /> <br /> === Setup of chroot environment === <br /> There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br /> This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br /> chroot /diskless/x86_64/Centos5.5/root<br /> mount /proc /proc -t proc<br /> mkdir /u <br /> mkdir /group<br /> mkdir /daqfs<br /> mv /home /home.old<br /> ln -s /u/apps /apps<br /> ln -s /u/site /site<br /> ln -s /daqfs/home /home<br /> <br /> === Setup of diskless system configurations ===<br /> ''' Which NFS directories to mount '''<br /> * Add entry to &lt;code&gt;/etc/fstab&lt;/code&gt;<br /> phecda:/raid /daqfs nfs rw,soft,intr 0 0<br /> <br /> * Mount daqfs<br /> mount /daqfs<br /> <br /> ''' Which users/groups to allow access '''<br /> * Add entries to /etc/passwd<br /> +@da::::::<br /> +@ccc::::::<br /> +::::::/bin/false<br /> <br /> ''' A proxy for yum ''' (may be optional)<br /> * Add entry to /etc/yum.conf<br /> proxy=http://jprox:8080<br /> <br /> ''' domain servers for ypbind '''<br /> * Add entries to /etc/yp.conf<br /> domain CCCHP server nis2.jlab.org<br /> domain CCCHP server nis3.jlab.org<br /> <br /> * Make sure ypbind started at boot<br /> /sbin/chkconfig --level 345 nfs on <br /> <br /> ''' NTP setup ''' (optional... ntp must be installed)<br /> * Add entries to &lt;code&gt;/etc/ntp.conf&lt;/code&gt;<br /> server 127.0.0.1 # local clock<br /> fudge 127.0.0.1 stratum 10<br /> server ntp1.jlab.org<br /> server ntp2.jlab.org<br /> driftfile /etc/ntp/drift<br /> broadcastdelay 0.008<br /> authenticate no<br /> <br /> ''' Some additional JLab CUE directories to mount '''<br /> * Add entries to &lt;code&gt;/etc/auto.master&lt;/code&gt;<br /> /group /etc/auto.group --timeout=0<br /> /u auto.u.bb --DOSNAME=Linux-RHEL5<br /> <br /> ''' Additional files, not included in the standard diskless filesystem '''<br /> * Add a new file &lt;code&gt;/diskless/x86_64/Centos5.5/snapshot/files.custom&lt;/code&gt;. Entry:<br /> /tmp/<br /> /etc/minirc.dfl<br /> <br /> = Configure a NEW diskless client =<br /> This operation must be peformed to add a new Diskless Client. <br /> <br /> === Configuration on the tftp/NFS server ===<br /> * In &lt;code&gt;system-config-netboot&lt;/code&gt; &quot;Network Installation and Diskless Environment&quot; window:<br /> # Click on &quot;New&quot;<br /> # Enter hostname<br /> # Select OS<br /> # Enter &quot;CCCHP&quot; in Enable NISDOMAIN box.<br /> # Enter options in &quot;Edit Extra Kernel Boot Options&quot; &lt;br /&gt; &lt;code&gt;vga=0x305 acpi=force&lt;/code&gt;<br /> # Enter hostname as snapshot name. Make sure &quot;generate&quot; is check-marked<br /> # Click &quot;OK&quot;<br /> <br /> === Configuration on the Diskless Client ===<br /> * PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br /> <br /> = Other useful packages to install =<br /> Later on... I installed some other useful packages using the chroot environment. Here they are:<br /> <br /> * &lt;code&gt;xorg-x11-xauth&lt;/code&gt; - Required to run X-applications remotely<br /> * &lt;code&gt;ntp&lt;/code&gt; - Synchronize system clock with a central server<br /> : To Execute &lt;code&gt;ntpdate&lt;/code&gt; on server startup:<br /> :* Add &lt;code&gt;&lt;b&gt;-x&lt;/b&gt;&lt;/code&gt; to &lt;code&gt;OPTIONS&lt;/code&gt; in<br /> /etc/sysconfig/ntpd<br /> :* Make sure it starts on boot<br /> /sbin/chkconfig --level 345 nfs on</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=GE_XVB601&diff=5180 2011-03-29T19:08:20Z

<p>129.57.167.199: </p> <hr /> <div>Company site: [http://www.ge-ip.com/products/family/embedded-systems GE Intelligent Platforms]<br /> <br /> Board page on company site: [http://www.ge-ip.com/products/3448 XVB601]<br /> <br /> Documentation: [https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_522-9300800627-000_A.book.pdf (pdf)]<br /> <br /> == Customization for the CLON cluster ==<br /> <br /> '''List of boards'''<br /> <br /> * [01] 00:20:38:04:23:5E / 129.57.68.89 / croctest2<br /> <br /> '''Customizing kernel installed on the FLASH'''<br /> <br /> * ''/usr/bin/system-config-network''<br /> <br /> * fix ''/etc/passwd'', ''/etc/shadow'', ''/etc/group''<br /> <br /> * fix ''/etc/nsswitch.conf''<br /> <br /> * fix ''/etc/yp.conf'' (add lines ''domain CCCHP server clon00.jlab.org'' and ''ypserver clon10.jlab.org'')<br /> <br /> * fix ''/etc/sysconfig/network'' (add line ''NISDOMAIN=CCCHP'')<br /> <br /> * ''/etc/init.d/ypbind start''<br /> <br /> * ''chkconfig ypbind on''<br /> <br /> <br /> * set RHEL-style [[automounts]]<br /> <br /> * ''/etc/init.d/autofs restart''<br /> <br /> * fix symbolic links to /apps, /home, /usr/local etc<br /> <br /> <br /> <br /> '''Trying netboot following Bryan's instructions, using clonpc3'''<br /> <br /> * ''yum install system-config-netboot''<br /> <br /> * Change line (&lt;code&gt;/etc/xinetd.d/tftp&lt;/code&gt;):<br /> disable = yes<br /> : To<br /> disable = no<br /> <br /> * ''service xinetd restart''<br /> <br /> * Add these entries to &lt;code&gt;/etc/exports&lt;/code&gt;<br /> /diskless/x86_64/Centos5.5/root/ 129.57.167.0/255.255.255.0(ro,sync,no_root_squash)<br /> /diskless/x86_64/Centos5.5/snapshot/ 129.57.167.0/255.255.255.0(rw,sync,no_root_squash)<br /> : Where the &lt;code&gt;129.57.167.0/255.255.255.0&lt;/code&gt; only allows the 167 subnet to access these mounts.<br /> <br /> * Reload the NFS configuration or start NFS, if it's not started<br /> ''service nfs reload''<br /> <br /> * Make sure NFS is started at boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> * Enable remote syslog (optional)<br /> <br /> Change syslog argument in &lt;code&gt;/etc/sysconfig/syslog&lt;/code&gt; from:<br /> SYSLOGD_OPTIONS=&quot;-m 0&quot;<br /> :: To<br /> SYSLOGD_OPTIONS=&quot;-m 0 -r&quot;<br /> <br /> Restart syslogd<br /> service syslog restart<br /> <br /> '''DHCP Server Setup'''<br /> On the machine hosting the DHCP server.<br /> <br /> * Add an entry in &lt;code&gt;/etc/dhcpd.conf&lt;/code&gt;:<br /> &lt;pre&gt;<br /> host dafarm44<br /> {<br /> filename &quot;linux-install/pxelinux.0&quot;; # File location relative to /tftpboot/<br /> next-server 129.57.29.38; # TFTP server<br /> hardware ethernet 00:20:38:03:D8:52; # Client MAC<br /> fixed-address 129.57.29.54; # Client IP<br /> }<br /> &lt;/pre&gt;<br /> <br /> * Restart dhcpd<br /> service dhcpd restart<br /> <br /> '''Configure Client OS'''<br /> <br /> Here, we configure the OS that each and every Diskless Client will enjoy.<br /> <br /> '''Setup of Diskless Kernel'''<br /> Run system-config-netboot (on TFTP server):<br /> system-config-netboot<br /> <br /> * In &quot;First Time Druid&quot; window. Click on &quot;Diskless&quot;<br /> # Click &quot;Forward&quot; on first page<br /> # Enter Name and Description.<br /> # Enter IP address of TFTP server and the &quot;root&quot; directory exported via NFS<br /> # Select a kernel<br /> # Click on Apply.<br /> : This will take a minute or two to compile a boot kernel for the diskless client.<br /> <br /> '''Setup of chroot environment'''<br /> There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br /> This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br /> chroot /diskless/x86_64/Centos5.5/root<br /> mount /proc /proc -t proc<br /> mkdir /u <br /> mkdir /group<br /> mkdir /daqfs<br /> mv /home /home.old<br /> ln -s /u/apps /apps<br /> ln -s /u/site /site<br /> ln -s /daqfs/home /home<br /> <br /> '''Setup of diskless system configurations'''<br /> <br /> ''' Which NFS directories to mount '''<br /> <br /> * Add entry to &lt;code&gt;/etc/fstab&lt;/code&gt;<br /> phecda:/raid /daqfs nfs rw,soft,intr 0 0<br /> <br /> * Mount daqfs<br /> mount /daqfs<br /> <br /> ''' Which users/groups to allow access '''<br /> * Add entries to /etc/passwd<br /> +@da::::::<br /> +@ccc::::::<br /> +::::::/bin/false<br /> <br /> ''' A proxy for yum ''' (may be optional)<br /> * Add entry to /etc/yum.conf<br /> proxy=http://jprox:8080<br /> <br /> ''' domain servers for ypbind '''<br /> * Add entries to /etc/yp.conf<br /> domain CCCHP server nis2.jlab.org<br /> domain CCCHP server nis3.jlab.org<br /> <br /> * Make sure ypbind started at boot<br /> /sbin/chkconfig --level 345 nfs on <br /> <br /> ''' NTP setup ''' (optional... ntp must be installed)<br /> * Add entries to &lt;code&gt;/etc/ntp.conf&lt;/code&gt;<br /> server 127.0.0.1 # local clock<br /> fudge 127.0.0.1 stratum 10<br /> server ntp1.jlab.org<br /> server ntp2.jlab.org<br /> driftfile /etc/ntp/drift<br /> broadcastdelay 0.008<br /> authenticate no<br /> <br /> ''' Some additional JLab CUE directories to mount '''<br /> * Add entries to &lt;code&gt;/etc/auto.master&lt;/code&gt;<br /> /group /etc/auto.group --timeout=0<br /> /u auto.u.bb --DOSNAME=Linux-RHEL5<br /> <br /> ''' Additional files, not included in the standard diskless filesystem '''<br /> * Add a new file &lt;code&gt;/diskless/x86_64/Centos5.5/snapshot/files.custom&lt;/code&gt;. Entry:<br /> /tmp/<br /> /etc/minirc.dfl<br /> <br /> ''' Configure a NEW diskless client '''<br /> This operation must be peformed to add a new Diskless Client. <br /> <br /> ''' Configuration on the tftp/NFS server '''<br /> * In &lt;code&gt;system-config-netboot&lt;/code&gt; &quot;Network Installation and Diskless Environment&quot; window:<br /> # Click on &quot;New&quot;<br /> # Enter hostname<br /> # Select OS<br /> # Enter &quot;CCCHP&quot; in Enable NISDOMAIN box.<br /> # Enter options in &quot;Edit Extra Kernel Boot Options&quot; &lt;br /&gt; &lt;code&gt;vga=0x305 acpi=force&lt;/code&gt;<br /> # Enter hostname as snapshot name. Make sure &quot;generate&quot; is check-marked<br /> # Click &quot;OK&quot;<br /> <br /> ''' Configuration on the Diskless Client '''<br /> * PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br /> <br /> ''' Other useful packages to install '''<br /> Later on... I installed some other useful packages using the chroot environment. Here they are:<br /> <br /> * &lt;code&gt;xorg-x11-xauth&lt;/code&gt; - Required to run X-applications remotely<br /> * &lt;code&gt;ntp&lt;/code&gt; - Synchronize system clock with a central server<br /> : To Execute &lt;code&gt;ntpdate&lt;/code&gt; on server startup:<br /> :* Add &lt;code&gt;&lt;b&gt;-x&lt;/b&gt;&lt;/code&gt; to &lt;code&gt;OPTIONS&lt;/code&gt; in<br /> /etc/sysconfig/ntpd<br /> :* Make sure it starts on boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> == Network-based booting ==<br /> <br /> The page is geared towards the setup of Diskless nodes for Intel-based VME Controllers, but may be useful for similar other applications. Much of what is here was derived from the [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/3/html/System_Administration_Guide/ch-diskless.html Redhat Enterprise Linux 3 Documentation].<br /> <br /> This examples assumes:<br /> * The DHCP server (phecda: 129.57.29.104) has been installed and works. Here we're using the dhcp 3.0.1 package distributed by RHEL4.<br /> * The TFTP and NFS server (mizar: 129.57.29.100) is running RHEL5.5 x86_64.<br /> * The Diskless Client (dafarm44: 129.57.29.54) will run Centos 5.5 x86_64.<br /> <br /> There's nothing stopping you from having the DHCP server on the same machine as that servering TFTP and NFS. You can obviously have more than one diskless client.<br /> <br /> Once the first four steps have been completed, new clients can be configured individually with step 5.<br /> <br /> = Client Setup of OS in VirtualBox =<br /> Here, we've downloaded the latest and greatest Centos 5.5 x86_64 ISO and have set up a VirtualBox Client to use it to boot. We will not attempt to describe the VirtualBox installation or Setup of the ISO to boot as the VirtualBox Guest.<br /> <br /> The Centos 5.5 installation proceeds as normal installations go, but we opt to do a minimal installation (excluding KDE and/or GNOME components) since we're running on a VME controller. Other packages will be installed after first boot.<br /> <br /> === First Boot ===<br /> At first boot (after installation), a UI will appear and provide you with some options.:<br /> * Disable firewall and SELinux. SELinux setup can be double checked in the file:<br /> /etc/selinux/config<br /> * Disable sendmail, and other services not required for a VME controller<br /> <br /> === Update packages and transfer the OS to Server ===<br /> Login as root<br /> * Update all installed packages:<br /> yum update<br /> * Install the following packages, with:<br /> yum install &lt;i&gt;package&lt;/i&gt;<br /> :: busybox-anaconda<br /> :: gcc<br /> :: kernel-devel<br /> :: gdb<br /> :: valgrind<br /> :: cvs<br /> :: subversion<br /> :: compat-libstdc++-33<br /> :: redhat-rpm-config<br /> <br /> * Copy the Client OS to the tftp/NFS Server.<br /> ** On The Server:<br /> mkdir -p /diskless/x86_64/Centos5.5/root<br /> : In The VirtualBox Guest:<br /> rsync -Pav -e ssh --exclude='/proc/*' --exclude='/sys/*' / mizar:/diskless/x86_64/Centos5.5/root/<br /> <br /> You are now done with the Centos5.5 Guest installed in the VirtualBox. It can be closed down now.<br /> <br /> = tftp and NFS Server Setup =<br /> Follow these steps on the machine serving out tftp and NFS:<br /> <br /> ===Install &lt;code&gt;system-config-netboot&lt;/code&gt; ===<br /> (This should automatically install the tftp server)<br /> yum install system-config-netboot<br /> <br /> === Enable the tftp server to start at boot ===<br /> * Change line (&lt;code&gt;/etc/xinetd.d/tftp&lt;/code&gt;):<br /> disable = yes<br /> : To<br /> disable = no<br /> <br /> * Restart &lt;code&gt;xinetd&lt;/code&gt;<br /> service xinetd restart<br /> <br /> === Configure NFS ===<br /> * Add these entries to &lt;code&gt;/etc/exports&lt;/code&gt;<br /> /diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br /> /diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br /> : Where the &lt;code&gt;129.57.29.0/255.255.255.0&lt;/code&gt; only allows the 29 subnet to access these mounts.<br /> <br /> * Reload the NFS configuration or start NFS, if it's not started<br /> service nfs reload<br /> <br /> * Make sure NFS is started at boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> === Enable remote syslog (optional) ===<br /> * Change syslog argument in &lt;code&gt;/etc/sysconfig/syslog&lt;/code&gt; from:<br /> SYSLOGD_OPTIONS=&quot;-m 0&quot;<br /> :: To<br /> SYSLOGD_OPTIONS=&quot;-m 0 -r&quot;<br /> <br /> * Restart syslogd<br /> service syslog restart<br /> <br /> = DHCP Server Setup =<br /> On the machine hosting the DHCP server.<br /> <br /> * Add an entry in &lt;code&gt;/etc/dhcpd.conf&lt;/code&gt;:<br /> &lt;pre&gt;<br /> host dafarm44<br /> {<br /> filename &quot;linux-install/pxelinux.0&quot;; # File location relative to /tftpboot/<br /> next-server 129.57.29.38; # TFTP server<br /> hardware ethernet 00:20:38:03:D8:52; # Client MAC<br /> fixed-address 129.57.29.54; # Client IP<br /> }<br /> &lt;/pre&gt;<br /> <br /> * Restart dhcpd<br /> service dhcpd restart<br /> <br /> = Configure Client OS =<br /> <br /> Here, we configure the OS that each and every Diskless Client will enjoy.<br /> <br /> === Setup of Diskless Kernel ===<br /> Run system-config-netboot (on TFTP server):<br /> system-config-netboot<br /> <br /> * In &quot;First Time Druid&quot; window. Click on &quot;Diskless&quot;<br /> # Click &quot;Forward&quot; on first page<br /> # Enter Name and Description.<br /> # Enter IP address of TFTP server and the &quot;root&quot; directory exported via NFS<br /> # Select a kernel<br /> # Click on Apply.<br /> : This will take a minute or two to compile a boot kernel for the diskless client.<br /> <br /> === Setup of chroot environment === <br /> There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br /> This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br /> chroot /diskless/x86_64/Centos5.5/root<br /> mount /proc /proc -t proc<br /> mkdir /u <br /> mkdir /group<br /> mkdir /daqfs<br /> mv /home /home.old<br /> ln -s /u/apps /apps<br /> ln -s /u/site /site<br /> ln -s /daqfs/home /home<br /> <br /> === Setup of diskless system configurations ===<br /> ''' Which NFS directories to mount '''<br /> * Add entry to &lt;code&gt;/etc/fstab&lt;/code&gt;<br /> phecda:/raid /daqfs nfs rw,soft,intr 0 0<br /> <br /> * Mount daqfs<br /> mount /daqfs<br /> <br /> ''' Which users/groups to allow access '''<br /> * Add entries to /etc/passwd<br /> +@da::::::<br /> +@ccc::::::<br /> +::::::/bin/false<br /> <br /> ''' A proxy for yum ''' (may be optional)<br /> * Add entry to /etc/yum.conf<br /> proxy=http://jprox:8080<br /> <br /> ''' domain servers for ypbind '''<br /> * Add entries to /etc/yp.conf<br /> domain CCCHP server nis2.jlab.org<br /> domain CCCHP server nis3.jlab.org<br /> <br /> * Make sure ypbind started at boot<br /> /sbin/chkconfig --level 345 nfs on <br /> <br /> ''' NTP setup ''' (optional... ntp must be installed)<br /> * Add entries to &lt;code&gt;/etc/ntp.conf&lt;/code&gt;<br /> server 127.0.0.1 # local clock<br /> fudge 127.0.0.1 stratum 10<br /> server ntp1.jlab.org<br /> server ntp2.jlab.org<br /> driftfile /etc/ntp/drift<br /> broadcastdelay 0.008<br /> authenticate no<br /> <br /> ''' Some additional JLab CUE directories to mount '''<br /> * Add entries to &lt;code&gt;/etc/auto.master&lt;/code&gt;<br /> /group /etc/auto.group --timeout=0<br /> /u auto.u.bb --DOSNAME=Linux-RHEL5<br /> <br /> ''' Additional files, not included in the standard diskless filesystem '''<br /> * Add a new file &lt;code&gt;/diskless/x86_64/Centos5.5/snapshot/files.custom&lt;/code&gt;. Entry:<br /> /tmp/<br /> /etc/minirc.dfl<br /> <br /> = Configure a NEW diskless client =<br /> This operation must be peformed to add a new Diskless Client. <br /> <br /> === Configuration on the tftp/NFS server ===<br /> * In &lt;code&gt;system-config-netboot&lt;/code&gt; &quot;Network Installation and Diskless Environment&quot; window:<br /> # Click on &quot;New&quot;<br /> # Enter hostname<br /> # Select OS<br /> # Enter &quot;CCCHP&quot; in Enable NISDOMAIN box.<br /> # Enter options in &quot;Edit Extra Kernel Boot Options&quot; &lt;br /&gt; &lt;code&gt;vga=0x305 acpi=force&lt;/code&gt;<br /> # Enter hostname as snapshot name. Make sure &quot;generate&quot; is check-marked<br /> # Click &quot;OK&quot;<br /> <br /> === Configuration on the Diskless Client ===<br /> * PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br /> <br /> = Other useful packages to install =<br /> Later on... I installed some other useful packages using the chroot environment. Here they are:<br /> <br /> * &lt;code&gt;xorg-x11-xauth&lt;/code&gt; - Required to run X-applications remotely<br /> * &lt;code&gt;ntp&lt;/code&gt; - Synchronize system clock with a central server<br /> : To Execute &lt;code&gt;ntpdate&lt;/code&gt; on server startup:<br /> :* Add &lt;code&gt;&lt;b&gt;-x&lt;/b&gt;&lt;/code&gt; to &lt;code&gt;OPTIONS&lt;/code&gt; in<br /> /etc/sysconfig/ntpd<br /> :* Make sure it starts on boot<br /> /sbin/chkconfig --level 345 nfs on</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=GE_XVB601&diff=5179 2011-03-29T19:05:43Z

<p>129.57.167.199: </p> <hr /> <div>Company site: [http://www.ge-ip.com/products/family/embedded-systems GE Intelligent Platforms]<br /> <br /> Board page on company site: [http://www.ge-ip.com/products/3448 XVB601]<br /> <br /> Documentation: [[]]<br /> <br /> == Customization for the CLON cluster ==<br /> <br /> '''List of boards'''<br /> <br /> * [01] 00:20:38:04:23:5E / 129.57.68.89 / croctest2<br /> <br /> '''Customizing kernel installed on the FLASH'''<br /> <br /> * ''/usr/bin/system-config-network''<br /> <br /> * fix ''/etc/passwd'', ''/etc/shadow'', ''/etc/group''<br /> <br /> * fix ''/etc/nsswitch.conf''<br /> <br /> * fix ''/etc/yp.conf'' (add lines ''domain CCCHP server clon00.jlab.org'' and ''ypserver clon10.jlab.org'')<br /> <br /> * fix ''/etc/sysconfig/network'' (add line ''NISDOMAIN=CCCHP'')<br /> <br /> * ''/etc/init.d/ypbind start''<br /> <br /> * ''chkconfig ypbind on''<br /> <br /> <br /> * set RHEL-style [[automounts]]<br /> <br /> * ''/etc/init.d/autofs restart''<br /> <br /> * fix symbolic links to /apps, /home, /usr/local etc<br /> <br /> <br /> <br /> '''Trying netboot following Bryan's instructions, using clonpc3'''<br /> <br /> * ''yum install system-config-netboot''<br /> <br /> * Change line (&lt;code&gt;/etc/xinetd.d/tftp&lt;/code&gt;):<br /> disable = yes<br /> : To<br /> disable = no<br /> <br /> * ''service xinetd restart''<br /> <br /> * Add these entries to &lt;code&gt;/etc/exports&lt;/code&gt;<br /> /diskless/x86_64/Centos5.5/root/ 129.57.167.0/255.255.255.0(ro,sync,no_root_squash)<br /> /diskless/x86_64/Centos5.5/snapshot/ 129.57.167.0/255.255.255.0(rw,sync,no_root_squash)<br /> : Where the &lt;code&gt;129.57.167.0/255.255.255.0&lt;/code&gt; only allows the 167 subnet to access these mounts.<br /> <br /> * Reload the NFS configuration or start NFS, if it's not started<br /> ''service nfs reload''<br /> <br /> * Make sure NFS is started at boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> * Enable remote syslog (optional)<br /> <br /> Change syslog argument in &lt;code&gt;/etc/sysconfig/syslog&lt;/code&gt; from:<br /> SYSLOGD_OPTIONS=&quot;-m 0&quot;<br /> :: To<br /> SYSLOGD_OPTIONS=&quot;-m 0 -r&quot;<br /> <br /> Restart syslogd<br /> service syslog restart<br /> <br /> '''DHCP Server Setup'''<br /> On the machine hosting the DHCP server.<br /> <br /> * Add an entry in &lt;code&gt;/etc/dhcpd.conf&lt;/code&gt;:<br /> &lt;pre&gt;<br /> host dafarm44<br /> {<br /> filename &quot;linux-install/pxelinux.0&quot;; # File location relative to /tftpboot/<br /> next-server 129.57.29.38; # TFTP server<br /> hardware ethernet 00:20:38:03:D8:52; # Client MAC<br /> fixed-address 129.57.29.54; # Client IP<br /> }<br /> &lt;/pre&gt;<br /> <br /> * Restart dhcpd<br /> service dhcpd restart<br /> <br /> '''Configure Client OS'''<br /> <br /> Here, we configure the OS that each and every Diskless Client will enjoy.<br /> <br /> '''Setup of Diskless Kernel'''<br /> Run system-config-netboot (on TFTP server):<br /> system-config-netboot<br /> <br /> * In &quot;First Time Druid&quot; window. Click on &quot;Diskless&quot;<br /> # Click &quot;Forward&quot; on first page<br /> # Enter Name and Description.<br /> # Enter IP address of TFTP server and the &quot;root&quot; directory exported via NFS<br /> # Select a kernel<br /> # Click on Apply.<br /> : This will take a minute or two to compile a boot kernel for the diskless client.<br /> <br /> '''Setup of chroot environment'''<br /> There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br /> This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br /> chroot /diskless/x86_64/Centos5.5/root<br /> mount /proc /proc -t proc<br /> mkdir /u <br /> mkdir /group<br /> mkdir /daqfs<br /> mv /home /home.old<br /> ln -s /u/apps /apps<br /> ln -s /u/site /site<br /> ln -s /daqfs/home /home<br /> <br /> '''Setup of diskless system configurations'''<br /> <br /> ''' Which NFS directories to mount '''<br /> <br /> * Add entry to &lt;code&gt;/etc/fstab&lt;/code&gt;<br /> phecda:/raid /daqfs nfs rw,soft,intr 0 0<br /> <br /> * Mount daqfs<br /> mount /daqfs<br /> <br /> ''' Which users/groups to allow access '''<br /> * Add entries to /etc/passwd<br /> +@da::::::<br /> +@ccc::::::<br /> +::::::/bin/false<br /> <br /> ''' A proxy for yum ''' (may be optional)<br /> * Add entry to /etc/yum.conf<br /> proxy=http://jprox:8080<br /> <br /> ''' domain servers for ypbind '''<br /> * Add entries to /etc/yp.conf<br /> domain CCCHP server nis2.jlab.org<br /> domain CCCHP server nis3.jlab.org<br /> <br /> * Make sure ypbind started at boot<br /> /sbin/chkconfig --level 345 nfs on <br /> <br /> ''' NTP setup ''' (optional... ntp must be installed)<br /> * Add entries to &lt;code&gt;/etc/ntp.conf&lt;/code&gt;<br /> server 127.0.0.1 # local clock<br /> fudge 127.0.0.1 stratum 10<br /> server ntp1.jlab.org<br /> server ntp2.jlab.org<br /> driftfile /etc/ntp/drift<br /> broadcastdelay 0.008<br /> authenticate no<br /> <br /> ''' Some additional JLab CUE directories to mount '''<br /> * Add entries to &lt;code&gt;/etc/auto.master&lt;/code&gt;<br /> /group /etc/auto.group --timeout=0<br /> /u auto.u.bb --DOSNAME=Linux-RHEL5<br /> <br /> ''' Additional files, not included in the standard diskless filesystem '''<br /> * Add a new file &lt;code&gt;/diskless/x86_64/Centos5.5/snapshot/files.custom&lt;/code&gt;. Entry:<br /> /tmp/<br /> /etc/minirc.dfl<br /> <br /> ''' Configure a NEW diskless client '''<br /> This operation must be peformed to add a new Diskless Client. <br /> <br /> ''' Configuration on the tftp/NFS server '''<br /> * In &lt;code&gt;system-config-netboot&lt;/code&gt; &quot;Network Installation and Diskless Environment&quot; window:<br /> # Click on &quot;New&quot;<br /> # Enter hostname<br /> # Select OS<br /> # Enter &quot;CCCHP&quot; in Enable NISDOMAIN box.<br /> # Enter options in &quot;Edit Extra Kernel Boot Options&quot; &lt;br /&gt; &lt;code&gt;vga=0x305 acpi=force&lt;/code&gt;<br /> # Enter hostname as snapshot name. Make sure &quot;generate&quot; is check-marked<br /> # Click &quot;OK&quot;<br /> <br /> ''' Configuration on the Diskless Client '''<br /> * PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br /> <br /> ''' Other useful packages to install '''<br /> Later on... I installed some other useful packages using the chroot environment. Here they are:<br /> <br /> * &lt;code&gt;xorg-x11-xauth&lt;/code&gt; - Required to run X-applications remotely<br /> * &lt;code&gt;ntp&lt;/code&gt; - Synchronize system clock with a central server<br /> : To Execute &lt;code&gt;ntpdate&lt;/code&gt; on server startup:<br /> :* Add &lt;code&gt;&lt;b&gt;-x&lt;/b&gt;&lt;/code&gt; to &lt;code&gt;OPTIONS&lt;/code&gt; in<br /> /etc/sysconfig/ntpd<br /> :* Make sure it starts on boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> == Network-based booting ==<br /> <br /> The page is geared towards the setup of Diskless nodes for Intel-based VME Controllers, but may be useful for similar other applications. Much of what is here was derived from the [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/3/html/System_Administration_Guide/ch-diskless.html Redhat Enterprise Linux 3 Documentation].<br /> <br /> This examples assumes:<br /> * The DHCP server (phecda: 129.57.29.104) has been installed and works. Here we're using the dhcp 3.0.1 package distributed by RHEL4.<br /> * The TFTP and NFS server (mizar: 129.57.29.100) is running RHEL5.5 x86_64.<br /> * The Diskless Client (dafarm44: 129.57.29.54) will run Centos 5.5 x86_64.<br /> <br /> There's nothing stopping you from having the DHCP server on the same machine as that servering TFTP and NFS. You can obviously have more than one diskless client.<br /> <br /> Once the first four steps have been completed, new clients can be configured individually with step 5.<br /> <br /> = Client Setup of OS in VirtualBox =<br /> Here, we've downloaded the latest and greatest Centos 5.5 x86_64 ISO and have set up a VirtualBox Client to use it to boot. We will not attempt to describe the VirtualBox installation or Setup of the ISO to boot as the VirtualBox Guest.<br /> <br /> The Centos 5.5 installation proceeds as normal installations go, but we opt to do a minimal installation (excluding KDE and/or GNOME components) since we're running on a VME controller. Other packages will be installed after first boot.<br /> <br /> === First Boot ===<br /> At first boot (after installation), a UI will appear and provide you with some options.:<br /> * Disable firewall and SELinux. SELinux setup can be double checked in the file:<br /> /etc/selinux/config<br /> * Disable sendmail, and other services not required for a VME controller<br /> <br /> === Update packages and transfer the OS to Server ===<br /> Login as root<br /> * Update all installed packages:<br /> yum update<br /> * Install the following packages, with:<br /> yum install &lt;i&gt;package&lt;/i&gt;<br /> :: busybox-anaconda<br /> :: gcc<br /> :: kernel-devel<br /> :: gdb<br /> :: valgrind<br /> :: cvs<br /> :: subversion<br /> :: compat-libstdc++-33<br /> :: redhat-rpm-config<br /> <br /> * Copy the Client OS to the tftp/NFS Server.<br /> ** On The Server:<br /> mkdir -p /diskless/x86_64/Centos5.5/root<br /> : In The VirtualBox Guest:<br /> rsync -Pav -e ssh --exclude='/proc/*' --exclude='/sys/*' / mizar:/diskless/x86_64/Centos5.5/root/<br /> <br /> You are now done with the Centos5.5 Guest installed in the VirtualBox. It can be closed down now.<br /> <br /> = tftp and NFS Server Setup =<br /> Follow these steps on the machine serving out tftp and NFS:<br /> <br /> ===Install &lt;code&gt;system-config-netboot&lt;/code&gt; ===<br /> (This should automatically install the tftp server)<br /> yum install system-config-netboot<br /> <br /> === Enable the tftp server to start at boot ===<br /> * Change line (&lt;code&gt;/etc/xinetd.d/tftp&lt;/code&gt;):<br /> disable = yes<br /> : To<br /> disable = no<br /> <br /> * Restart &lt;code&gt;xinetd&lt;/code&gt;<br /> service xinetd restart<br /> <br /> === Configure NFS ===<br /> * Add these entries to &lt;code&gt;/etc/exports&lt;/code&gt;<br /> /diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br /> /diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br /> : Where the &lt;code&gt;129.57.29.0/255.255.255.0&lt;/code&gt; only allows the 29 subnet to access these mounts.<br /> <br /> * Reload the NFS configuration or start NFS, if it's not started<br /> service nfs reload<br /> <br /> * Make sure NFS is started at boot<br /> /sbin/chkconfig --level 345 nfs on<br /> <br /> === Enable remote syslog (optional) ===<br /> * Change syslog argument in &lt;code&gt;/etc/sysconfig/syslog&lt;/code&gt; from:<br /> SYSLOGD_OPTIONS=&quot;-m 0&quot;<br /> :: To<br /> SYSLOGD_OPTIONS=&quot;-m 0 -r&quot;<br /> <br /> * Restart syslogd<br /> service syslog restart<br /> <br /> = DHCP Server Setup =<br /> On the machine hosting the DHCP server.<br /> <br /> * Add an entry in &lt;code&gt;/etc/dhcpd.conf&lt;/code&gt;:<br /> &lt;pre&gt;<br /> host dafarm44<br /> {<br /> filename &quot;linux-install/pxelinux.0&quot;; # File location relative to /tftpboot/<br /> next-server 129.57.29.38; # TFTP server<br /> hardware ethernet 00:20:38:03:D8:52; # Client MAC<br /> fixed-address 129.57.29.54; # Client IP<br /> }<br /> &lt;/pre&gt;<br /> <br /> * Restart dhcpd<br /> service dhcpd restart<br /> <br /> = Configure Client OS =<br /> <br /> Here, we configure the OS that each and every Diskless Client will enjoy.<br /> <br /> === Setup of Diskless Kernel ===<br /> Run system-config-netboot (on TFTP server):<br /> system-config-netboot<br /> <br /> * In &quot;First Time Druid&quot; window. Click on &quot;Diskless&quot;<br /> # Click &quot;Forward&quot; on first page<br /> # Enter Name and Description.<br /> # Enter IP address of TFTP server and the &quot;root&quot; directory exported via NFS<br /> # Select a kernel<br /> # Click on Apply.<br /> : This will take a minute or two to compile a boot kernel for the diskless client.<br /> <br /> === Setup of chroot environment === <br /> There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br /> This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br /> chroot /diskless/x86_64/Centos5.5/root<br /> mount /proc /proc -t proc<br /> mkdir /u <br /> mkdir /group<br /> mkdir /daqfs<br /> mv /home /home.old<br /> ln -s /u/apps /apps<br /> ln -s /u/site /site<br /> ln -s /daqfs/home /home<br /> <br /> === Setup of diskless system configurations ===<br /> ''' Which NFS directories to mount '''<br /> * Add entry to &lt;code&gt;/etc/fstab&lt;/code&gt;<br /> phecda:/raid /daqfs nfs rw,soft,intr 0 0<br /> <br /> * Mount daqfs<br /> mount /daqfs<br /> <br /> ''' Which users/groups to allow access '''<br /> * Add entries to /etc/passwd<br /> +@da::::::<br /> +@ccc::::::<br /> +::::::/bin/false<br /> <br /> ''' A proxy for yum ''' (may be optional)<br /> * Add entry to /etc/yum.conf<br /> proxy=http://jprox:8080<br /> <br /> ''' domain servers for ypbind '''<br /> * Add entries to /etc/yp.conf<br /> domain CCCHP server nis2.jlab.org<br /> domain CCCHP server nis3.jlab.org<br /> <br /> * Make sure ypbind started at boot<br /> /sbin/chkconfig --level 345 nfs on <br /> <br /> ''' NTP setup ''' (optional... ntp must be installed)<br /> * Add entries to &lt;code&gt;/etc/ntp.conf&lt;/code&gt;<br /> server 127.0.0.1 # local clock<br /> fudge 127.0.0.1 stratum 10<br /> server ntp1.jlab.org<br /> server ntp2.jlab.org<br /> driftfile /etc/ntp/drift<br /> broadcastdelay 0.008<br /> authenticate no<br /> <br /> ''' Some additional JLab CUE directories to mount '''<br /> * Add entries to &lt;code&gt;/etc/auto.master&lt;/code&gt;<br /> /group /etc/auto.group --timeout=0<br /> /u auto.u.bb --DOSNAME=Linux-RHEL5<br /> <br /> ''' Additional files, not included in the standard diskless filesystem '''<br /> * Add a new file &lt;code&gt;/diskless/x86_64/Centos5.5/snapshot/files.custom&lt;/code&gt;. Entry:<br /> /tmp/<br /> /etc/minirc.dfl<br /> <br /> = Configure a NEW diskless client =<br /> This operation must be peformed to add a new Diskless Client. <br /> <br /> === Configuration on the tftp/NFS server ===<br /> * In &lt;code&gt;system-config-netboot&lt;/code&gt; &quot;Network Installation and Diskless Environment&quot; window:<br /> # Click on &quot;New&quot;<br /> # Enter hostname<br /> # Select OS<br /> # Enter &quot;CCCHP&quot; in Enable NISDOMAIN box.<br /> # Enter options in &quot;Edit Extra Kernel Boot Options&quot; &lt;br /&gt; &lt;code&gt;vga=0x305 acpi=force&lt;/code&gt;<br /> # Enter hostname as snapshot name. Make sure &quot;generate&quot; is check-marked<br /> # Click &quot;OK&quot;<br /> <br /> === Configuration on the Diskless Client ===<br /> * PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br /> <br /> = Other useful packages to install =<br /> Later on... I installed some other useful packages using the chroot environment. Here they are:<br /> <br /> * &lt;code&gt;xorg-x11-xauth&lt;/code&gt; - Required to run X-applications remotely<br /> * &lt;code&gt;ntp&lt;/code&gt; - Synchronize system clock with a central server<br /> : To Execute &lt;code&gt;ntpdate&lt;/code&gt; on server startup:<br /> :* Add &lt;code&gt;&lt;b&gt;-x&lt;/b&gt;&lt;/code&gt; to &lt;code&gt;OPTIONS&lt;/code&gt; in<br /> /etc/sysconfig/ntpd<br /> :* Make sure it starts on boot<br /> /sbin/chkconfig --level 345 nfs on</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=JLAB_FANIO&diff=5093 2011-01-21T21:14:20Z

<p>129.57.167.199: </p> <hr /> <div>Manual in [https://clonwiki.jlab.org/wiki/clondocs/man/VME/JLAB_VME_FANIO_manual.pdf (pdf)]</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=JLAB_FANIO&diff=5092 2011-01-21T21:13:53Z

<p>129.57.167.199: </p> <hr /> <div>Manual in [https://clonwiki.jlab.org/wiki/clondocs/man/VME/JLAB_VME_FANIO.pdf (pdf)]</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=CLON_Index&diff=5091 2011-01-21T21:12:56Z

<p>129.57.167.199: </p> <hr /> <div>[[Apache]]<br /> <br /> [[automounts]]<br /> <br /> [[Bertan MWPC]] High Voltage Power Supplies<br /> <br /> [[Bootp]]<br /> <br /> [[Cacti]]<br /> <br /> [[CAEN A464]] caenet board (installed in sy527 mainframes)<br /> <br /> [[CAEN A1733 A1833]] 12/28 ch. 3kV/3mA, 4kV/2mA High Voltage Boards ( SY1527 / SY2527 / SY3527 Universal Multichannel System )<br /> <br /> [[CAEN A1932A]] 48 ch. 3kV 500uA High Voltage Board ( SY1527 / SY2527 / SY3527 Universal Multichannel System )<br /> <br /> [[CAEN SY1527 Mainframe]]<br /> <br /> [[CAEN SY527 Mainframe]] and modules<br /> <br /> [[CAEN V1190]] TDC board (128 ch 100 ps)<br /> <br /> [[CAEN V1290]] TDC board (32 ch 25 ps)<br /> <br /> [[CAEN V1495]] General Purpose VME Board<br /> <br /> [[CAEN V288]]<br /> <br /> [[CAEN V560]] scaler board<br /> <br /> [[CAEN V775]] TDC Board<br /> <br /> [[CAEN V895]] 16 ch. Leading Edge Discriminator with individual thresholds<br /> <br /> [[Capfast]]<br /> <br /> [[Cisco Switches]]<br /> <br /> [[Clasweb]]<br /> <br /> [[Clasxt]]<br /> <br /> [[Clon00]]<br /> <br /> [[Clon01]]<br /> <br /> [[Clon02]]<br /> <br /> [[Clon03]]<br /> <br /> [[Clon04]]<br /> <br /> [[Clon05]]<br /> <br /> [[Clon06]]<br /> <br /> [[Clon10]]<br /> <br /> [[Clon20]]<br /> <br /> [[Clondaq1]]<br /> <br /> [[Clondaq2]]<br /> <br /> [[Clondb1]]<br /> <br /> [[Clondb2]]<br /> <br /> [[Clondb3]]<br /> <br /> [[Clonfs]] Main RAID System<br /> <br /> [[Clonfs1]]<br /> <br /> [[Clonfs2]]<br /> <br /> [[Clonmon]]<br /> <br /> [[Clonmon0]]<br /> <br /> [[Clonmon1]]<br /> <br /> [[Clonmon2]]<br /> <br /> [[Clonpc1]]<br /> <br /> [[Clonpc2]]<br /> <br /> [[Clonpc3]]<br /> <br /> [[Clonpc5]]<br /> <br /> [[Clonpc6]]<br /> <br /> [[Clonpc8]]<br /> <br /> [[Clontrig0]]<br /> <br /> [[Clonweb]]<br /> <br /> [[Clonwiki]]<br /> <br /> [[clonhp]]<br /> <br /> [[clonhp2]]<br /> <br /> [[Coda]]<br /> <br /> [[Compcontrol CC121]]<br /> <br /> [[CycladesTS1000]]<br /> <br /> [[DATEL DVME-628]]<br /> <br /> [[DNS server]]<br /> <br /> [[Electronics Documentation]]<br /> <br /> [[EtherLite32]]<br /> <br /> [[EPICS Base Installation]]<br /> <br /> [[EPICS: Generation of IOC with different options and customization for HallB]]<br /> <br /> [[EPICS: Software IOC]]<br /> <br /> [[EPICS: vxWorks IOC]]<br /> <br /> [[EPICS: Software IOC for CAEN HV]]<br /> <br /> [[EPICS: generation of DBs and GUIs for HV]]<br /> <br /> [[EPICS: CVS usage examples]]<br /> <br /> [[EPICS: Timeline Histories]]<br /> <br /> [[EPICS: Gamma Profiler]]<br /> <br /> [[EPICS: EDM compilation and configuration]]<br /> <br /> [[Event Monitor]]<br /> <br /> [[Fiber Channel Switches]]<br /> <br /> [[FieldPoint]]<br /> <br /> [[Flash ADC Studies]]<br /> <br /> [[Foundry BigIron 15000 Switch]]<br /> <br /> [[Foundry Switches]]<br /> <br /> [[Helicity Signals from MCC]]<br /> <br /> [[HYTEC VSD2992]]<br /> <br /> [[JAVA installation]]<br /> <br /> [[JLAB Discriminators]]<br /> <br /> [[JLAB FLEXIO]]<br /> <br /> [[JLAB FANIO]] VME TDC FanIO board for v1190/v1290 CAEN TDCs<br /> <br /> [[JLAB LF]] VME Latch FIFO Board<br /> <br /> [[JLAB LD]] VME Latch Driver Board<br /> <br /> [[JLAB Level2 Majority]] Logic Unit<br /> <br /> [[JLAB MLU]] VME Memory Lookup Unit (MLU)<br /> <br /> [[JLAB OR]] VME Programmable “OR” Module<br /> <br /> [[JLAB TS2]] VXI D-size Trigger Supervisor Module<br /> <br /> [[JLAB TI]] CODA Trigger Interface Cards<br /> <br /> [[JLAB PCI TI]] PCI Trigger Interface Card<br /> <br /> [[JLAB VME TI]] VME Trigger Interface Module<br /> <br /> [[Joerger VSC16]]<br /> <br /> [[KineticSystems 2917]]<br /> <br /> [[Labeling Machines]]<br /> <br /> [[Linux Installation Procedure]]<br /> <br /> [[Linux Customization on CLON Cluster]]<br /> <br /> [[Lnf cluster]]<br /> <br /> [[Mac OS X Installation Procedure]]<br /> <br /> [[Motorola MVME5500]]<br /> <br /> [[MRTG]]<br /> <br /> [[mSQL]]<br /> <br /> [[MySQL Installation]]<br /> <br /> [[MySQL Usage]]<br /> <br /> [[Nagios]]<br /> <br /> [[Nagios Plugins]]<br /> <br /> [[Net-SNMP]]<br /> <br /> [[NFS]]<br /> <br /> [[NIS server]]<br /> <br /> [[Nrpe]]<br /> <br /> [[Ntp]]<br /> <br /> [[OMS VME44]] by Oregon Micro Systems<br /> <br /> [[OMS VS4]] by Oregon Micro Systems<br /> <br /> [[OpenSSL]]<br /> <br /> [[PERL]]<br /> <br /> [[Procmail]]<br /> <br /> [[PrPMC]]<br /> <br /> [[raidold]]<br /> <br /> [[Routing]]<br /> <br /> [[Rrdtool]]<br /> <br /> [[SBS VIPC616]]<br /> <br /> [[Serial Connections from Computer Ports]]<br /> <br /> [[Sfs61]]<br /> <br /> [[Slow Controls Time History]]<br /> <br /> [[SmartSockets]]<br /> <br /> [[SNMP]]<br /> <br /> [[Software Documentation]]<br /> <br /> [[Solaris Installation Procedure]]<br /> <br /> [[Solaris Customization on CLON Cluster]]<br /> <br /> [[Solaris Patches]]<br /> <br /> [[SSH]]<br /> <br /> [[Struck SIS3801]]<br /> <br /> [[Sudo]]<br /> <br /> [[SUN Microsystems]]<br /> <br /> [[SYSTRAN VMESC5]]<br /> <br /> [[Tcl/Tk]]<br /> <br /> [[Tftp]]<br /> <br /> [[Troubleshooting printing]]<br /> <br /> [[UNIX Automount on CLON Cluster]]<br /> <br /> [[UPS (Uninterruptible Power Supplies)]]<br /> <br /> [[UPS CHB1]]<br /> <br /> [[UPS CHB2]]<br /> <br /> [[UPS Troubleshooting]]<br /> <br /> [[VI editor]]<br /> <br /> [[VMIC VMIVME-3122]]<br /> <br /> [[VMIC VMIVME-2120]]<br /> <br /> [[VMIC VMIVME-1129]]<br /> <br /> [[VMIC VMIVME-2232]]<br /> <br /> [[VMIC VMIVME-6015]]<br /> <br /> [[VMIC VMIVME-6016]]<br /> <br /> [[VNC]]<br /> <br /> [[WIENER]]<br /> <br /> [[Wiki]]<br /> <br /> [[Wiring]]<br /> <br /> [[X server]]<br /> <br /> [[Xycom DIO XVME-240]]<br /> <br /> [[Xycom XVME-564]]<br /> <br /> [[Xycom XVME-560]]<br /> <br /> [[ZFS]]</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=PrPMC&diff=5090 2011-01-21T16:57:13Z

<p>129.57.167.199: </p> <hr /> <div>PrPMC co-processor boards are installed on VME controllers mvme5100/mvme5500/mvme6100.<br /> Most of PMCs are PrPMC280 and PrPMC2800, although some older PrPMC880 may be in use as well.<br /> <br /> PPMC280 Installation Guide [https://clonwiki.jlab.org/wiki/clondocs/Docs/PPMC280InstallationGuide.pdf (pdf)]<br /> <br /> PPMC280 VxWorks Installation Guide [https://clonwiki.jlab.org/wiki/clondocs/Docs/PPMC280VxWorksInstallationGuide.pdf (pdf)]<br /> <br /> PPMC280 VxWorks Programmers Guide [https://clonwiki.jlab.org/wiki/clondocs/Docs/PPMC280VxWorksProgrammersGuide.pdf (pdf)]<br /> <br /> PrPMC880 Installation and Use [https://clonwiki.jlab.org/wiki/clondocs/Docs/prpmc880a_ih.pdf (pdf)]<br /> <br /> PrPMC800 Installation and Use [https://clonwiki.jlab.org/wiki/clondocs/Docs/PrPMC800_Installation_and_Use.pdf (pdf)]</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=PrPMC&diff=5089 2011-01-21T16:51:56Z

<p>129.57.167.199: </p> <hr /> <div>PrPMC co-processor boards are installed on VME controllers mvme5100/mvme5500/mvme6100.<br /> Most of PMCs are PrPMC280 and PrPMC2800, although some older PrPMC880 may be in use as well.<br /> <br /> PPMC280 Installation Guide [https://clonwiki.jlab.org/wiki/clondocs/Docs/PPMC280InstallationGuide.pdf (pdf)]<br /> <br /> PPMC280 VxWorks Installation Guide [https://clonwiki.jlab.org/wiki/clondocs/Docs/PPMC280VxWorksInstallationGuide.pdf (pdf)]<br /> <br /> PPMC280 VxWorks Programmers Guide [https://clonwiki.jlab.org/wiki/clondocs/Docs/PPMC280VxWorksProgrammersGuide.pdf (pdf)]<br /> <br /> PrPMC880 Installation and Use [https://clonwiki.jlab.org/wiki/clondocs/Docs/prpmc880a_ih.pdf (pdf)]</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=PrPMC&diff=5088 2011-01-21T16:46:11Z

<p>129.57.167.199: </p> <hr /> <div>PrPMC co-processor boards are installed on VME controllers mvme5100/mvme5500/mvme6100.<br /> Most of PMCs are PrPMC280 and PrPMC2800, although some older PrPMC880 may be in use as well.<br /> <br /> PPMC280 Installation Guide [https://clonwiki.jlab.org/wiki/clondocs/Docs/PPMC280InstallationGuide.pdf (pdf)]<br /> <br /> PPMC280 VxWorks Installation Guide [https://clonwiki.jlab.org/wiki/clondocs/Docs/PPMC280VxWorksInstallationGuide.pdf (pdf)]<br /> <br /> PPMC280 VxWorks Programmers Guide [https://clonwiki.jlab.org/wiki/clondocs/Docs/PPMC280VxWorksProgrammersGuide.pdf (pdf)]<br /> <br /> PrPMC880 Guide [https://clonwiki.jlab.org/wiki/clondocs/Docs/prpmc880a_ih.pdf (pdf)]</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=PrPMC&diff=5087 2011-01-21T16:44:20Z

<p>129.57.167.199: </p> <hr /> <div>PrPMC co-processor boards are installed on VME controllers mvme5100/mvme5500/mvme6100.<br /> Most of PMCs are PrPMC280 and PrPMC2800, although some older PrPMC880 may be in use as well.<br /> <br /> PPMC280 Installation Guide [https://clonwiki.jlab.org/wiki/clondocs/Docs/PPMC280InstallationGuide.pdf (pdf)]<br /> <br /> PPMC280 VxWorks Installation Guide [https://clonwiki.jlab.org/wiki/clondocs/Docs/PPMC280VxWorksInstallationGuide.pdf (pdf)]<br /> <br /> PPMC280 VxWorks Programmers Guide [https://clonwiki.jlab.org/wiki/clondocs/Docs/PPMC280VxWorksProgrammersGuide.pdf (pdf)]</div>

129.57.167.199 https://clonwiki0.jlab.org/wiki/index.php?title=PrPMC&diff=5086 2011-01-21T16:02:51Z

<p>129.57.167.199: </p> <hr /> <div>PrPMC co-processor boards are installed on VME controllers mvme5100/mvme5500/mvme6100.<br /> Most of PMCs are PrPMC280 and PrPMC2800, although some older PrPMC880 may be in use as well.<br /> <br /> PrPMC280 Installation Guide [https://clonwiki.jlab.org/wiki/clondocs/Docs/PPMC280InstallationGuide.pdf (pdf)]</div>

129.57.167.199