Return to Tipsheets

Tipsheets

How to Create an Overload for Radmind

  1. 1. Go to a machine you'd like to use to create your overload. Download application installer and store it in Student Data folder.
  2. 2. Install and key the application. Place the application in the correct folder. Create alias(es) for the application and place them in the correct directories.
  3. 3. Reboot the machine. Check if the aliases point to the right application. (In Finder window, click on the alias, and click More Info. Click Select New Original if the alias doesn't point to the right application.)
  4. Reboot the machine again. Test whether the application is running properly and if the aliases launch the application correctly.
  5. Clear the Trash in the dock. Go to Go (top bar) and clear Recent Folder. Click on Apple (top bar) and clear Recent Items. Reboot.
  6. Go to the vserver machine (in the office) and run Terminal.
  7. Type: “sudo s” and enter the password (ask Vince) to go to the root.
  8. At the root, type : ssh labuser@ipaddress (ipaddress = the IP address of the machine you just used to install the new program.) Enter labuser's password. This command means you're logging into the machine using labuser as login name.
  9. Type : sudo -s (to go to the root) and enter once again, labuser's password.
  10. Type:screen. This will bring you to an information page. Press space/enter to continue. Now we're officially inside the system.
  11. Type: setenv PATH {$PATH}:/usr/local/bin:/usr/local/sbin
  12. Type: fsdiff -C -c sha1 -o /var/radmind/client/file.T / (note: file.T is the name of the overload. For example, if I just installed Isadora, I can name the overload isadora.T Also, notice there's an empty space between .T and the last forward slash.)
  13. This process takes from 15 - 60 minutes depending on the size of the overload. However, you can't leave it for too long because it'll automatically be dumped to the server after some time, which will create an error later on. So, drop in to check the progress every 15 minutes or so, to make sure things are going alright.
  14. Continue to next step when you have [nameofcomputer:~] root# displayed on the screen.
  15. Next, type: pico -w /var/radmind/client/file.T This will give you a list of all the files inside file.T. Put a negative sign in front of all .DS Store files.
  16. When you are done, press Ctrl+O and Enter to save the changes. Press Ctrl+X to exit.
  17. Type: lcreate -h 129.133.127.33 /var/radmind/client/file.T This command will dump the overload into the server.
  18. Open a couple new terminal windows. Type: sudo -s which brings you to the root of the server.
  19. Make sure you get [vserver:~] root# ,
    then type: setenv PATH {$PATH}:/usr/local/bin:/usr/local/sbin
  20. Type:cd /var/radmind/tmp/transcrip
  21. Type:ls You should get file.T in the next line, which confirms that the overload has been successfully dumped into the server.
  22. Type: lcksum -c sha1 -n file.T
  23. You should get file.T: verified. If you get an error message instead, go back and check all your commands and make sure they are typed correctly.
  24. Now, type: cd / to go back to the root (because just now we're inside the directory)
  25. Type: mv /var/radmind/tmp/transcript/file.T /var/radmind/transcript/
    (We're moving file.T from tmp folder to transcript folder)
  26. Type: mv /var/radmind/tmp/file/file.T /var/radmind/file/.
  27. In another terminal window, go to the root (Type: sudo -s and enter the password if necessary, to get [vserver:~] root# ). In this window, type: cd /var/radmind/command/ Type ls to obtain a list of commands that we need to update by adding a new line for the new overload. (see example below)
  28. Go back to the previous window. Type: pico -w /var/radmind/command/command.K
    (command.K being the file you need to update, depending on which computers need to get this radmind updates).
  29. Right above the labstats_reset.T line, insert your overload file. (eg. Type: p file.T)
  30. Press Ctrl+O and press Enter to save the changes. Press Ctrl+X to exit.
  31. Repeat the steps above for all the commands that need to be updated.
  32. Test the overload on a test box and see if radmind runs properly (no error). And after radminding, test to see if the new program is working properly and if the aliases are launching the correct application.
  33. Congratulations! You just created your first overload!!!