Kksnishi: /* HowTo: Perform a cortical porosity and finite element analysis of HR-pQCT scans */

How To's

2010-06-07T22:23:50Z

Kksnishi: /* HowTo: Restore a zipped archive file from mike.kin */

Vtkski development

2010-06-01T19:33:41Z

Kksnishi: /* Compiling */

==Documentation for vtkski==

On-line documentation for vtkski is available at http://mike.kin.ucalgary.ca/vtkski/ .

Also, see [[vtkMeshModel]] which contains some examples of using the class vtkMeshModel .

==Compiling and Installation==

===Getting the source code===

Get the sources from the subversion repository.

svn checkout https://mike.kin.ucalgary.ca/svn/bonelab/trunk/vtkski

See the section on svn for more info: [[Subversion (SVN)]]

===Compiling===

From the vtkski project directory, create a build directory in trunk/Libraries and use cmake to configure the build:

mkdir build
cd build
cmake-gui ..

The most important cmake variable is <tt>VTK_DIR</tt>. If you intend to also build the paraview plugins, then you must build vtkski against the internal version of VTK inside the paraview build directory. (See [[Paraview development]] if you need to install ParaView). As an example, on my system I set <tt>VTK_DIR</tt> to <tt>/home/eric/source/paraview-3.8.0/build/VTK</tt>. You will also need to specify the boost include directory.

Then within build directory run:

make

===Building Doxygen documentation===

To build the Doxygen documentation, set the cmake variable BUILD_DOCUMENTATION to ON. This variable is marked as advanced. You will need to have installed Doxygen ( http://www.doxygen.org/ ) in order to build the documentation.

The documentation is not automatically built with make (it takes a very long time to build). Instead, you will need to explicitly request it, like this:
make vtkskiDoxygenDoc

====Installing the Doxygen documentation on mike.kin====

I recommend that you build the documentation with the cmake flag DOCUMENTATION_HTML_TARZ set to on (this variable is an advanced setting). Then the build process will automatically make a tar ball of all the HTML documentation, build/Utilities/Doxygen/vtkski-html.tar.gz , which is easy to copy over to mik.kin (using FTP or scp or the mounted Data0 volume).

The documentation needs to live in /Library/WebServer/Documents/vtkski . The commands would look something like this
tar xvzf vtkski-html.tar.gz
sudo rm -rf /Library/WebServer/Documents/vtkski # remove old docs
sudo mv html /Library/WebServer/Documents/vtkski
sudo chown -R root /Library/WebServer/Documents/vtkski

==Checklist for new vtkski classes==

* Select a category for your new class, for example 'IO', and put your source files in that directory.
* Modify the CmakeLists.txt file in that directory to add your new source files to the list of source files.
* Build vtkski and make sure that your class compiles.
* Refer to [[Creating VTK Classes]] for important coding style tips.
* Add your class, with a brief description, to [[Class List for vtkski]].

For help writing VTK classes, refer to the book "VTK User's Guide", Part III, "Developer's Guide". There are a couple of copies in the lab.

Vtkski development

2010-06-01T19:06:31Z

Kksnishi: /* Compiling */

==Documentation for vtkski==

On-line documentation for vtkski is available at http://mike.kin.ucalgary.ca/vtkski/ .

Also, see [[vtkMeshModel]] which contains some examples of using the class vtkMeshModel .

==Compiling and Installation==

===Getting the source code===

Get the sources from the subversion repository.

svn checkout https://mike.kin.ucalgary.ca/svn/bonelab/trunk/vtkski

See the section on svn for more info: [[Subversion (SVN)]]

===Compiling===

From the vtkski project directory, create a build directory in trunk/Libraries and use cmake to configure the build:

mkdir build
cd build
cmake-gui ..

The most important cmake variable is <tt>VTK_DIR</tt>. If you intend to also build the paraview plugins, then you must build vtkski against the internal version of VTK inside the paraview build directory. (See [[Paraview development]] if you need to install ParaView). As an example, on my system I set <tt>VTK_DIR</tt> to <tt>/home/eric/source/paraview-3.6.1/build/VTK</tt>.

===Building Doxygen documentation===

To build the Doxygen documentation, set the cmake variable BUILD_DOCUMENTATION to ON. This variable is marked as advanced. You will need to have installed Doxygen ( http://www.doxygen.org/ ) in order to build the documentation.

The documentation is not automatically built with make (it takes a very long time to build). Instead, you will need to explicitly request it, like this:
make vtkskiDoxygenDoc

====Installing the Doxygen documentation on mike.kin====

I recommend that you build the documentation with the cmake flag DOCUMENTATION_HTML_TARZ set to on (this variable is an advanced setting). Then the build process will automatically make a tar ball of all the HTML documentation, build/Utilities/Doxygen/vtkski-html.tar.gz , which is easy to copy over to mik.kin (using FTP or scp or the mounted Data0 volume).

The documentation needs to live in /Library/WebServer/Documents/vtkski . The commands would look something like this
tar xvzf vtkski-html.tar.gz
sudo rm -rf /Library/WebServer/Documents/vtkski # remove old docs
sudo mv html /Library/WebServer/Documents/vtkski
sudo chown -R root /Library/WebServer/Documents/vtkski

==Checklist for new vtkski classes==

* Select a category for your new class, for example 'IO', and put your source files in that directory.
* Modify the CmakeLists.txt file in that directory to add your new source files to the list of source files.
* Build vtkski and make sure that your class compiles.
* Refer to [[Creating VTK Classes]] for important coding style tips.
* Add your class, with a brief description, to [[Class List for vtkski]].

For help writing VTK classes, refer to the book "VTK User's Guide", Part III, "Developer's Guide". There are a couple of copies in the lab.

File:Tk-858-decarbon.patch

2010-05-28T20:50:56Z

Kksnishi:

Lab Administration

2009-08-28T17:43:00Z

Kksnishi: /* Conferences 2009 */

Lab Administration

2008-10-07T22:00:57Z

Kksnishi:

==Research Group Contact Info==

'''Bone Imaging Laboratory (a.k.a. the fishbowl)''' 
Kinesiology (KNB 2225) 
220-3188 

'''3D Morphometrics Laboratory''' 
Heritage Medical Research Building (HMRB 405) 
220-8411, 220-3131 

'''Steve Boyd''' 
email: skboyd@ucalgary.ca 
office: 220-4173 
home: 284-3550 
cell: 978-3550 

'''Helen Buie''' 
email: hbuie@ucalgary.ca 
office: 220-2452 
cell: 816-7943 

'''Graeme Campbell''' 
email: gmcampbe@ucalgary.ca 
office: 210-8965 
home: 210-1443 
cell: 852-5554 

'''Josh Klinck''' 
email: rjklinck@ucalgary.ca 
office: 220-5450 
home1: 281-0032 
home2: 254-2992 

'''Erika Kristensen''' 
email: ekristensen@kin.ucalgary.ca 
office: 210-8933 
home: 697-3850 

'''Josh MacNeil''' 
email: jamacnei@ucalgary.ca 
office: 220-2802 
home: 262-3299 

'''Michael Hofmann''' 
email: mhofmann@student.ethz.ch 

'''Etienne Schwyter''' 
email: eschwyter@kin.ucalgary.ca 

'''Jerome Gire''' 
email: jgire@kin.ucalgary.ca 

'''Yves Pauchard''' 
email: yves.pauchard@ucalgary.ca 
office: 220-3841 
home: 475-2454 

'''James DuMont 
email: jimmydt@gmail.com 
office: 220-3188 
home: 998-7555 

'''Patrick Meunier 
email: pjymeuni@ucalgary.ca 
office: 220-3188 
home: 521-0207 

'''Steve Sandercott 
email: ssandercott@kin.ucalgary.ca, ssanderc@waterloo.ca 
office: 210-8965 
home: 519-546-6218 

'''Chris Moore 
email: cpmoore@ucalgary.ca 
office: 220-3188 
home: 932-0776 

'''Rochelle Nieuwenhuis 
email: midnights_pet@hotmail.com 
office: 220-3188 
home: 243-2955 

'''Fábio Ayres 
email: fjayres@ucalgary.ca 
room: KNB 2202 
office: 220-4687 
home: 532-3919 

'''Kyle Nishiyama 
email: kksnishi@ucalgary.ca 
office: 220-3853 
cell: 400-6315 
home: 455-0770 

==Conferences ==

===Conferences 2006===

'''International Bone Densitometry Workshop (IBDW)'''
:http://www.procom-i.co.jp/ibdw2006/frameindex.html

:IBDW 2006
:Kyoto, Japan
:November 5-9, 2006

:abstracts due June 15, 2006
:pre-registration deadline: June 30th, 2006

'''Osteoarthritis Research Society International (OARSI)'''
:http://www.oarsi.org/conference/06Congress/AbstractInfo.htm

:OARSI 2006 World Congress
:Prague, Czech Republic
:December 7-10, 2006

:abstracts due: July 31, 2006
:pre-registration deadline: ?

'''American Society of Bone and Mineral Research (ASBMR)''' 
:http://www.asbmr.org/

:ASBMR 28th annual meeting
:Philadelphia, PA, USA
:September 15-19, 2006

:abstracts due: April 29, 2006 at 5pm CDT
:pre-registration deadline: July 20, 2006

'''American Society of Biomechanics (ASB)''' 
:http://www.asbweb.org/

:30th annual meeting of the ASB
:Blacksburg, Virginia, USA
:September 6-9, 2006

:abstracts due: April 3, 2006
:pre-registration deadline: July 1, 2006

'''International Society of Biomechanics (ISB)''' 
:http://www.isbweb.org/

:5th world congress of biomechanics
:Munich, Germany
:July 29-August 4, 2006

:abstracts due: February 15, 2006
:pre-registration deadline: May 1, 2006

'''European Society of Biomechanics (ESB)''' 
:http://www.esbiomech.org/

:15th conference of the ESB (as part of 5th world congress of biomechanics)
:Munich, Germany
:July 29-August 4, 2006

:abstracts due: February 15, 2006
:pre-registration deadline: May 1, 2006

'''American Society of Mechanical Engineers (ASME)''' 
:http://divisions.asme.org/bed/

:2006 Summer Bioengineering Conference
:Amelia Island, Florida, USA
:June 21-25, 2006

:abstracts due: January 27, 2006
:pre-registration deadline: May 13, 2006

===Conferences 2007===

'''Orthopaedic Research Society (ORS)''' 
:http://www.ors.org/

:The 6th combined meeting of the ORS
:Honolulu, Hawaii, USA
:October 20-24, 2007

:abstracts due: July 31, 2006
:pre-registration deadline: ?

'''IEEE Engineering in Medicine and Biology Society (EMBS)''' 
:http://www.embs.org/

:29th Annual International Conference of the IEEE Engineering in Medicine and Biology Society (IEEE EMBC)
:Lyon, France
:August 23-26, 2007
:http://www.embc07.ulster.ac.uk/

:abstracts due: Monday April 2, 2007
:notification: June 15, 2007
:pre-registration deadline: July 10, 2007

'''Orthopaedic Research Society (ORS)''' 
:http://www.ors.org/

:The 53rd annual meeting of the ORS
:San Diego, California, USA
:February 11-14, 2007

:abstracts due: Monday July 31, 2006
:pre-registration deadline: ?

===Conferences 2008===

'''The International Society for Optical Engineering (SPIE)''' 
:http://www.spie.org

:SPIE Annual Conference on Medical Imaging
:San Diego, California, USA
:February 16-21, 2008

:abstracts due: Aug 6th, 2007
:manuscripts due: Jan 21st, 2008
:pre-registration deadline: ?

'''Orthopaedic Research Society (ORS)''' 
:http://www.ors.org/

:The 54th annual meeting of the ORS
:San Francisco, California, USA
:March 2-5, 2008

:abstracts due: Sept 5th, 2007
:pre-registration deadline: ?

'''IEEE Signal Processing Society (SPS)''' 
:http://www.ieee.org/organizations/society/sp/

:The 33rd IEEE International Conference on Acoustics, Speech, and Signal Processing (ICASSP)
:Las Vegas, Nevada, USA
:March 31 - April 4, 2008
:http://www.icassp2008.org/

:4-page paper due: Oct 7th, 2007
:notification: Dec 14th, 2007
:pre-registration deadline: Jan 18th, 2008

'''IEEE Signal Processing Society (SPS) & IEEE Engineering in Medicine and Biology Society (EMBS)''' 
:http://www.ieee.org/organizations/society/sp/
:http://www.embs.org/

:5th IEEE International Symposium on Biomedical Imaging (ISBI 2008)
:Paris, France
:May 14 - May 17, 2008
:http://www.biomedicalimaging.org/

:4-page paper due: Dec 7th, 2007
:notification: Feb 15th, 2008
:pre-registration deadline: March 14th, 2008

'''ACM SIGGRAPH''' 
:http://www.siggraph.org

:The 35th International Conference on Computer Graphics SIGGRAPH2008
:TBA
:TBA (probably August 2008)

:abstracts due: TBA (probably January 2008)
:pre-registration deadline: ?

===Conferences 2009===

'''The International Society for Optical Engineering (SPIE)''' 
:http://www.spie.org

:SPIE Annual Conference on Medical Imaging
:Orlando, Florida, USA
:February 7-12, 2009

:abstracts due: July 28th, 2008
:manuscripts due: Jan 12, 2009
:pre-registration deadline: ?

'''IEEE Signal Processing Society (SPS) & IEEE Engineering in Medicine and Biology Society (EMBS)''' 
:http://www.ieee.org/organizations/society/sp/
:http://www.embs.org/

:6th IEEE International Symposium on Biomedical Imaging (ISBI 2009)
:Boston, Massachusetts
:June 29th - July 1st, 2009
:http://www.biomedicalimaging.org/

:4-page paper due: Jan 19, 2009
:notification: March 30, 2009
:pre-registration deadline: May 1, 2009

==Journal Club==

===High Priority Journals===

[http://www.jbmr-online.com/ Journal of Bone and Mineral Research ] (2002 6.329)

Lab member responsible for this journal: Steve

[http://www.sciencedirect.com.ezproxy.lib.ucalgary.ca:2048/science?_ob=JournalURL&_cdi=4987&_auth=y&_acct=C000051253&_version=1&_urlVersion=0&_userid=1067480&md5=00f0a210c77f892821ee55e76b66cd13 Bone] (2005 3.572)

Lab member responsible for this journal: Erika

[http://www.springerlink.com/(rexfj3u4l55pkznoycbqxke2)/app/home/journal.asp?referrer=parent&backto=linkingpublicationresults,1:100120,1 Calcified Tissue International] (2004 2.258)

Lab member responsible for this journal: Josh K.

[http://www.springerlink.com/(yz0q05yc4dlalxruqy2j1b55)/app/home/journal.asp?referrer=parent&backto=linkingpublicationresults,1:102828,1 Osteoporosis International] (2003 3.799)

Lab member responsible for this journal: Graeme

[http://ees.elsevier.com/mep/ Medical Engineering and Physics] (2002 0.769)

Lab member responsible for this journal: Yves

===Medium Priority Journals===

[http://www.bme.gatech.edu/abme/ Annals of Biomedical Engineering] (2002 1.573)

Lab member responsible for this journal: Erika

[http://arjournals.annualreviews.org/loi/bioeng;jsessionid=o0AwcCow3M48 Annual Review of Biomedical Engineering] (2002 3.537)

Lab member responsible for this journal: Josh M.

[http://www.sciencedirect.com/science?_ob=JournalURL&_cdi=5074&_auth=y&_acct=C000051253&_version=1&_urlVersion=0&_userid=1067480&md5=5628a498ee2c4c8c03998426a4fa02bd Journal of Biomechanics] (2002 1.889)

Lab member responsible for this journal: Graeme

[http://www.sciencedirect.com.ezproxy.lib.ucalgary.ca:2048/science?_ob=JournalURL&_cdi=6979&_auth=y&_acct=C000051253&_version=1&_urlVersion=0&_userid=1067480&md5=4374752f61a4ccf8ae807c734ffb6867 Osteoarthritis and Cartilage] (2004 3.572)

Lab member responsible for this journal: Graeme

[http://www.sciencedirect.com.ezproxy.lib.ucalgary.ca:2048/science?_ob=JournalURL&_cdi=6633&_auth=y&_acct=C000051253&_version=1&_urlVersion=0&_userid=1067480&md5=7a0210a3980a9920e6bdb9978594d646 Journal of Orthopedic Research] (2004: 2.720)

Lab member responsible for this journal: Erika

[http://scitation.aip.org/ASMEJournals/Biomechanical/ Journal of Biomechanical Engineering] (2003 1.6)

Lab member responsible for this journal: Josh K.

===Low Priority Journals===

[http://www.sciencedirect.com/science?_ob=JournalURL&_cdi=4997&_auth=y&_acct=C000051253&_version=1&_urlVersion=0&_userid=1067480&md5=75f54fa07d8f798de0f3f0f3ccc8681a Clinical Biomechanics] (2002 0.996)

Lab member responsible for this journal: Graeme

[http://www.tandf.co.uk/journals/online/1025-5842.asp Computer Methods in Biomechanics and Biomedical Engineering]

Lab member responsible for this journal: Erika

[http://ieeexplore.ieee.org/xpl/RecentIssue.jsp?punumber=10 IEEE Transactions on Biomedical Engineering] (2002 1.665)

Lab member responsible for this journal: Yves

[http://ieeexplore.ieee.org/xpl/RecentIssue.jsp?puNumber=42 IEEE Transactions on Medical Imaging] (2002 2.911)

Lab member responsible for this journal: Yves

==Laboratory Equipment List==

===Computers===

* Percy - Alphastation DS15, single processor, HP1955, OpenVMS (KNB2225)
* Thomas - Alphastation DS25, dual processor, HP1955, OpenVMS (KNB2227A)
* Henry - HP XW4300, 2GB RAM, Windows XP, HP2035 (KNB2225)
* Donald - HP XW9300 dual processor, HP2035, 8GB RAM, Linux (KNB2225)
* Douglas - HP XW9300 single processor, HP2035, 2GB RAM, Linux (KNB2225)
* Lady - ECI original PC, 2GB RAM, 18" NEC, Linux (KNB2225)
* Daisy - ECI original PC, 2GB RAM, 18" NEC, Linux (KNB2225)
* Dennis - ECI original PC, 2GB RAM, 18" NEC, Linux (Fabio Ayres, KNB 2202)
* CCIT - ECI original PC, 2GB RAM, 18" NEC, Linux (CCIT 125)
* Edward - HP DX5150, 2GB RAM, HP1906, Windows XP (Kyle Nishiyama)
* Emily - HP DX5150, 2GB RAM, HP1906, Windows XP (Helen Buie)
* Gordon - HP DX5150, 2GB RAM, HP1906, Windows XP (Erika Kristensen)
* Toby - HP DX5150, 2GB RAM, HP1906, Windows XP (Graeme Campbell)
* Murdoch - IBM T43 laptop, 2GB RAM, Windows XP (Steven Boyd)
* Temple - SunBlade 2500, 4GB RAM, Sun 18" monitor, Solaris 10 (CCIT 125)
* Oliver - HP DX5750, 2GB RAM, AMD DualCore 2GHz, HP1940, Windows XP (Yves Pauchard)
* Splatter - HP xw9400, 8GB RAM, 2x AMD DualCore Opteron, Nvidia Quadraplex (2GPUs), Windows XP and Ubuntu Linux (Eric Nodwell)

===Other equipment===

* Nikon D70 w/ 28-80 lens
* Crystal eyes glasses (2 pair) and emitter
* Viewsonic G220fb
* HP LaserJet 4650dn
* Disk array on Thomas, 7x 300GB SCSI
* Disk array on HPL-NT, 6x 300GB SCSI

===Third Floor Freezer===

* Combination: 15-28-01

==Publications==

Link to the the lab's: [[Publications]] section

2007-11-02T18:16:57Z

Kksnishi:

Developer

2007-11-02T18:14:37Z

Kksnishi: /* vtkMy */

==Hardware==

Used Alpha stations at http://www.islandco.com

==VMS Development==

===Getting started===

Editor:
<pre>
$! Define the editor
$ eve == "spawn/nowait edit/display=decwindows/tpu"
$ eve filename.txt
</pre>

Compiler:
<pre>
$! Define the compiler
$ C64 :== CC/POINTER_SIZE=64/check=pointer=all/optimize=(tune=ev6,level=5)

$! Compile the program 'ipl_scanco_c' and link it to existing libraries
$ c64 ipl:ipl_scanco_c
$!
$ link /exe=ipl:ipl_SCANCO_c -
ipl:ipl_scanco_c, -
ipl:ipl_scanco_c_ident/opt, -
ipl:ipl_proc/lib, -
ipl:ipl/lib, -
mu:scanco_ext/lib, -
dsrc:d3p_scanco/lib, -
scanco_lib/lib
</pre>

===SCTHIN (DS10L)===
<pre>
duck.kin.ucalgary.ca has been assigned IP address 136.159.130.33
netmask 255.255.255.0
default router 136.159.130.34
DNS servers 136.159.130.130, 136.159.130.3
</pre>

Login <code>microct</code> or <code>devel</code> with <code>not2lame</code>.

To boot into the cluster
<pre>
>>>boot ewa0
</pre>
To boot out of the cluster, unplug the ethernet cable and
<pre>
>>>boot
</pre>

To get to boot prompt, type <code>shutdown</code> on the login screen. Or, after powerdown, hit <code>ctrl-P</code> repeatedly.

There are two accounts:
:*microct
:*devel

===Installing packages on VMS===

Contacts:
Piet Schuermans
Mark Blanchard

====Freeware source====
http://h71000.www7.hp.com/freeware/freeware80/

Instructions for unpacking .tar.gz files on VMS
:1. Rename the file to file.tgz
:2. gunzip file.tgz (creates a file.tar)
:3. vmstar file.tar

====VMSTAR====

A tar program for VMS.

Either install from the source (build it), or apparently the binary can be downloaded from

http://h71000.www7.hp.com/freeware/freeware50/vmstar/alpha/

where you will find VMSTAR.EXE

When extracting files that contain "unix" filenames (e.g., config.h.in), make sure to extract the files with
<pre>
$ cvstar xof file.tar ! Option 'o' extracts ODS5 files with ODS2 format
</pre>

====CVS====

The sources can be retrieved from http://ftp.gnu.org/non-gnu/cvs/source/stable/

You will need a C compiler on OpenVMS. There are several versions of CVS available, but all of them need some tweaking before they can be successfully built.

:cvs-1.11.18 (see build instructions at http://lists.gnu.org/archive/html/bug-cvs/2005-01/msg00280.html)
:cvs-1.11.21 (do not use)
:cvs-1.11.22 (latest version as of May 26, 2007 -- may be built, but follow instructions as per v.18 above)

Download the .tar.gz file, rename it to .tgz once on vms system, use gunzip then vmstar:
<pre>
$ rename cvs-1.11.22.tar.gz cvs-1.11.22.tgz
$ gunzip cvs-1.11.22.tgz
$ vmstar xof cvs-1.11.22.tar ! option 'o' allows ODS2 naming.
</pre>

For all versions, make the following changes before starting:
:1. Before you attempt to compile 1.11.22 or later you will need make a copy of [.LIB]FNMATCH_H.IN as [.LIB]FNMATCH.H
:2. Correct typo in [.SRC]BUILD_SRC.COM change "libz" to "zlib"

Note:
The directory names would have been cvs-1.11.21.dir on Linux. However VMS doesn't allow more than 1 . in the name. If you enter

<pre>$ set process/parse=extended</pre>

in a terminal you'll be able to access these files. You rename them (i.e. cvs-1_11_21.dir).

NOTE
Piet Schuermans (mailps@mac.com) sent me a binary version of CVS on May 25, 2007 that I am currently using.

USAGE

Note that I have a "getting started on cvs for vms" document that can help.

OpenVMS is case sensitive for passing parameters. So put the parameters between " "

<pre>
$ cvs -d ":pserver:anonymous@public.kitware.com:/cvsroot/VTK" login
$ cvs -d ":pserver:anonymous@public.kitware.com:/cvsroot/VTK" co "vtknew/CMake"
</pre>

If your using this repository location frequently then
<pre>
$ define cvsroot ":pserver:anonymous@public.kitware.com:/cvsroot/VTK"
</pre>
after this you can skip the -d ...... parameter
<pre>
$ cvs login
vtk
</pre>

This will create .cvspass file in your home directory so your only
need to use the cvs login once
<pre>
$ cvs co "vtknew"
</pre>

public.kitware.com has ip address 66.194.253.19

===Update VMS licenses===

As user system:

<pre>$ lic list/full</pre>

and check which licenses are currently from 'MONTAGAR' and expire on Aug 31.

I recommend to only then replace those licenses with the new ones, and not load the whole license text file that you get from HP. Make a 'shortlist' of the licenses you need, then FTP them to the VMS system and copy and paste.

Layered Products (any licence, but NOT the openvms-Alpha itself!)

<pre>
$ lic del OPENVMS-ALPHA-USER
$ LICENSE REGISTER OPENVMS-ALPHA-USER -
/ACTIVITY=CONSTANT=100 -
/AUTHORIZATION=EDU-711643-12345 -
/DATE=31-AUG-2007 -
/ISSUER=MONTAGAR -
/PRODUCER=DEC -
/TERMINATION=31-AUG-2007 -
/UNITS=0 -
/CHECKSUM=1-BBME-NKAP-EAFK-CNCA
$ lic load OPENVMS-ALPHA-USER

$ lic del vmscluster
$ LICENSE REGISTER VMSCLUSTER -
/ACTIVITY=CONSTANT=100 -
/AUTHORIZATION=EDU-711643-12345 -
/DATE=31-AUG-2007 -
/ISSUER=MONTAGAR -
/PRODUCER=DEC -
/TERMINATION=31-AUG-2007 -
/UNITS=0 -
/CHECKSUM=1-GOOP-ALPF-PGKG-OBND
$ lic load vmscluster
</pre>

Then, on SCTHIN, for the basic 'openvms-alpha' license itself. In a cluster, this license must be limited to one computer only, so first, to delete the correct of the multiple openvms-alpha licenses only. If I ever wanted SCTHIN to be the server in a cluster, I should do the following (very unlikely!):
<pre>
$ lic list openvms-alpha/ful

$ lic delete openvms-alpha/auth=xxxxxx
! after first looking up the authori. of that montagar license.

$ LICENSE REGISTER OPENVMS-ALPHA -
/ISSUER=MONTAGAR -
/AUTHORIZATION=EDU-742405-743161 -
/PRODUCER=DEC -
/UNITS=0 -
/TERMINATION_DATE=31-AUG-2008 -
/ACTIVITY=A -
/OPTIONS=(NO_SHARE) -
/CHECKSUM=2-JMOA-GOFL-AKID-DHCJ

$ lic modify openvms-alpha/auth=EDU-742405-743161/include=scthin
! to make it available to scthin only.
</pre>

===MMS: VMS 'make' tool===

To start:
<pre>
$ mms
</pre>

An example from Bruno Koller of <code>descrip.mms</code>:
<pre>
.IGNORE
FFLAGS = /FAST/OPT=(LEVEL=5,TUNE=EV68,INL=ALL)/OBJECT=$(MMS$TARGET_NAME).OBJ
FGENER = /ALIGN=(NATURAL,SEQUENCE)/ASSUME=NOACCURACY/OPT=(LEVEL=5,TUNE=GENERIC,INL=ALL)/OBJECT=$(MMS$TARGET_NAME).OBJ_G

.FOR.OBJ
$(FORT)$(FFLAGS) UD:$(MMS$TARGET_NAME).FOR
$(FORT)$(FGENER) UD:$(MMS$TARGET_NAME).FOR
.FOR.INC
$(FORT)$(FFLAGS) UD:$(MMS$TARGET_NAME).FOR
$(FORT)$(FGENER) UD:$(MMS$TARGET_NAME).FOR

all :: uct_reconstruction.exe, uct_reconstruction.exe_generic
write sys$output "UCT_RECONSTRUCTION.EXE generated"

uct_reconstruction.exe :: -
recoident.opt, -
uct_reconstruction.obj, -
scli:uct_reco_constants.inc, -
calc_fan_beam_angles.obj, -
rebinning.obj, -
raw_to_rpro.obj, -
conereco.obj

link/exe=uct_reconstruction.exe -
recoident/opt, -
uct_reconstruction.obj, -
calc_fan_beam_angles, -
rebinning, -
raw_to_rpro, -
conereco, -
scanco_lib/lib

uct_reconstruction.exe_generic :: -
recoident.opt_g, -
uct_reconstruction.obj_g, -
scli:uct_reco_constants.inc, -
calc_fan_beam_angles.obj_g, -
raw_to_rpro.obj_g, -
rebinning.obj_g, -
conereco.obj_g

link/exe=uct_reconstruction.exe_generic -
recoident/opt, -
uct_reconstruction.obj_g, -
calc_fan_beam_angles.obj_g, -
raw_to_rpro.obj_g, -
rebinning.obj_g, -
conereco.obj_g, -
scanco_lib/lib

uct_reconstruction.obj :: ud:uct_reconstruction.for, -
scli:uct_reco_constants.inc

calc_fan_beam_angles.obj :: ud:calc_fan_beam_angles.for, -
scli:uct_reco_constants.inc

raw_to_rpro.obj :: ud:raw_to_rpro.for, -
scli:uct_reco_constants.inc

rebinning.obj :: ud:rebinning.for, -
scli:uct_reco_constants.inc, -
scli:ctdata_header_structure.inc

conereco.obj :: ud:conereco.for, -
scli:uct_reco_constants.inc
</pre>

Some notes:
:*UD is a logical for user disk search list over different disks, so I can compile on both alpha and vax with just having one source.

:*No need to put "ud:" at your site. Also, a few lines may have been wrapped which should be on one line (/fflag...) by the mail program.

:*Let me know if you want the mms installation file, you will need the hp campus mms license herefore (which you may already have)

===Alternative to MMS: MMK===

A free MMS replacement is called Madgoat MMK (http://www.madgoat.com/mmk.html).

===Alternative to EVE: NEDIT===

NEDIT is also available for VMS and offers a nicer editor, in my opinion (Mark Blanchard).

===Online VMS discussion lists===

info-vax (comp.os.vms)

==Linux Machines==

===Accessing Sodor disk===

From Konqueror in KDE, use a path like:

<pre>smb://HPL-NT\sboyd@hal/Sodor</pre>

==vtkMy==

===vtkMy Development - Windows Setup:===
 
'''Required Software: '''
Cmake 2.4.7 
WinCVS 2.0 
ITK 2.8.1 
VTK 2006-09-01 
Qt 3.3.6 Academic 

#Create directory C:\pack to keep all programs
#Download and install cmake-2.4.7.zip from: http://www.cmake.org/HTML/Download.html
#Download and install WinCvs 2.0.2.4 (released 2005-08-15) from:http://www.wincvs.org/download.html#WINCVS
#Download InsightToolkit-2.8.1.zip (hosted at SourceForge) from:http://www.itk.org/HTML/Download.htm
#Use WinCVS to download source files for VTK:
#*a. Open WinCVS and click menu Admin-> Preferences-> CVS Tab
#**Enter HOME: C:\pack
#**Click Ok
#*b. Open menu Admin-> Command Line
#**Enter the following:
#:::cvs -d :pserver:anonymous@public.kitware.com:/cvsroot/VTK login 
#:::cvs -d :pserver:anonymous@public.kitware.com:/cvsroot/VTK checkout –d 2006-09-01 VTK
#**Click Ok
#**You will be prompted for the password. Enter: vtk
#**Wait for checkout to complete
#Download vtkMy source using WinCVS
#*a. Verify home directory as set up in Step 5.a.i.
#*b. Open menu Remote-> Checkout Module
#** Enter the following settings:
#:::Module name and path on server: vtkMy
#:::Local folder to checkout to: C:\pack\
#:::Check box: CVSROOT
#:::CVSROOT: :ssh:username@m177.enme.ucalgary.ca:/localhost/cvsroot
#**Click Ok
#**You will be prompted for your password to access the machine
#**Wait for checkout to complete
#Build ITK using Cmake
#*a. Open Cmake
#*b. Choose C:\pack\InsightToolkit-2.8.1 as source code
#*c. Make C:\pack\ITK binary code location
#*d. Click ‘Configure’ and choose desired compiler
#*e. Use the following Cache values:
#::BUILD_EXAMPLES: ON
#::BUILD_SHARED_LIBS: ON
#::BUILD_TESTING: ON
#::BUILD_BACKWARDS_COMPATIBILITY: 2.4
#::CMAKE_INSTALL_PREFIX: C:/Program Files/ITK
#*f. Click ‘Configure’, all red values should turn grey
#*g. Click ‘Ok’, wait as Cmake will close automatically
#Build VTK using Cmake
#*a. Open Cmake
#*b. Choose C:\pack\VTK-2006-09-01 as source code
#*c. Make C:\pack\VTK binary code location
#*d. Click ‘Configure’ and choose desired compiler
#*e. Click the ‘Show Advanced Values’ checkbox and verify the following settings, all others can be left as defaults:
#::BUILD_EXAMPLES: ON
#::BUILD_SHARED_LIBS: ON
#::BUILD_TESTING: ON
#::BUILD_BACKWARDS_COMPATIBILITY: 2.4
#::CMAKE_INSTALL_PREFIX: C:/Program Files/VTK
#::VTK_USE_ANSI_STDLIB: ON
#*f. Click ‘Configure’, all red values should turn grey
#*g. Click ‘Ok’, wait as Cmake will close automatically
#Install Qt 3.3.6 Academic version
#*a. Run “qt-win-academic-3.3.6.exe”
#*b. When asked for license information choose to use license file and open “qt-license-3.3.6”
#*c. For installation options use defaults and be sure to build with shared libraries in Step 8 [[Image:Wincvs general.jpg|center]]
#Build vtkMy using Cmake
#*a. Open Cmake
#*b. Choose C:\pack\vtkMy\src as source code
#*c. Make C:\pack\vtkMy\bin binary code location
#*d. Click ‘Configure’ and choose desired compiler
#*e. Click the ‘Show Advanced Values’ check box and verify the following settings, all others can be left as defaults:
#::BUILD_APPLICATIONS: ON
#::BUILD_SHARED_LIBS: ON
#::BUILD_TEST_PROJECTS: ON
#::BUILD_BACKWARDS_COMPATIBILITY: 2.4
#::CMAKE_INSTALL_PREFIX: C:/Program Files/VTKMY
#::USE_ITK: ON
#::USE_QT: ON
#::USE_FLTK: OFF
#::VTK_DIR: C:/pack/VTK
#::ITK_DIR: C:/pack/ITK
#*f. Click ‘Configure’, all red values should turn grey
#*g. May have to click configure again if any red values are still present
#*h. Click ‘Ok’, wait as Cmake will close automatically
#Build VTK using Visual C++ 6.0 (or desired program)
## Open C:\pack\VTK\vtk.dsw
## Click ‘Build’
#Build ITK using Visual C++ 6.0 (or desired program)
#*a. Open C:\pack\ITK\itk.dsw
#*b. Click ‘Build’
#Build vtkMy using Visual C++ 6.0 (or desired program)
#*a. Open C:\pack\vtkMy\bin\vtkmy.dsw
#*b. Click ‘Build’

===WinCVS and PuTTY for vtkMy===

NOTE: An alternative CVS client has been suggested, but not tested:
<pre>
SmartCVS from www.syntevo.com with a foundation license.
</pre>

Setting up WinCVS to use PuTTY is fairly straightforward, but does require a few configuration settings in addition to installing the software. You can do it with the following steps.

#Install PuTTY (http://www.chiark.greenend.org.uk/~sgtatham/putty/).
#Install wincvs (http://www.wincvs.org/)
#Make a key:
#*Follow menus: Start/Programs/PuTTY/PuTTYgen From the PuTTY Manual: 
#:...press the "Generate" button and PuTTYgen will begin the process of actually generating the key.
#*First, a progress bar will appear and PuTTYgen will ask you to move the mouse around to generate randomness. Wave the mouse in circles over the blank area in the PuTTYgen window, and the progress bar will gradually fill up as PuTTYgen collects enough randomness. You don't need to wave the mouse in particularly imaginative patterns (although it can't hurt); PuTTYgen will collect enough randomness just from the fine detail of exactly how far the mouse has moved each time Windows samples its position.
#*When the progress bar reaches the end, PuTTYgen will begin creating the key. The progress bar will reset to the start, and gradually move up again to track the progress of the key generation. It will not move evenly, and may occasionally slow down to a stop; this is unfortunately unavoidable, because key generation is a random process and it is impossible to reliably predict how long it will take.
#*When the key generation is complete, a new set of controls will appear in the window to indicate this.
[[Image:putty_key_generator.jpg|center]]
# Set the key comment and password. Set the key comment to your email address by typing it into the "Key Comment" box. Set the password by entering it twice, once in the "Key passphrase" box and once in the "Confirm Passphrase" box.
#Save the keys: save the public key on your desktop as <code>identity.pub</code> and the private one as <code>identity.ppk</code>
#Email the identity.pub file as an attachment to skboyd@ucalgary.ca and ask for it to be added to the .ssh/authorized_keys file for your cvs repository. Please specify which repository you are requesting access to in the e-mail (i.e., vtkMy).
#Setup environment variables
#* Choose Menus: Start/Settings/Control Panel
#* Double click on the "System" Control Panel
#* Pick the "Advanced" tab and pick "Environment Varibles..."
#* Add User environement variables
#:- Add PLINK_PROTOCOL value "ssh"
#:- Add CVS_RSH value "plink"
#:- Edit or Add PATH appending value ";C:\Program Files\PuTTY"
# In WinCVS, bring up the "Preferences" dialogue box from the Admin menu
#* In the "General" tab put in your CVSROOT value, (i.e. <code>:ext:myusername@m177.enme.ucalgary.ca:/localhost/cvsroot</code>) [[Image:Wincvs general.jpg|center]]
#* Switch to the "Ports" tab.
#* Tick the box there labelled "Check for an alternate rsh name" and in the text entry field to the right enter "plink". [[Image:Wincvs ports tab.jpg|center]]
#* Select "OK" on teh "Preferences" dialogue box.
# Once you've heard back from the administrator (skboyd) that your ssh keys have been added, test your putty key configuration:
#*Double click on "identity.ppk" on your desktop. If this doesn’t start pagaent.exe automatically, then manually start the program from the directory you installed putty.exe.
#* If your identity file isn't already loaded, you will be prompted for the password you entered in step 4.
#*The Pageant icon (a little PC with a hat) should appear in the bottom right menu bar.

You should now be able to use WinCVS to access the repository, with a secure connection whenever Pageant is running. You can start Pageant by double-clicking on your identity.ppk file.

===Setting up CVS access from Linux/Unix===
*To understand the codes for a CVS update, see page 121 of CVS users guide, section A.16.2.
# Valuable resource for understanding ssh:
#* http://www-106.ibm.com/developerworks/library/l-keyc.html
#* http://www-106.ibm.com/developerworks/library/l-keyc2/
# Setting up SSH access from "localbox" to "remotebox": Localbox:
#* ssh-keygen -t rsa [use a passphrase]
#: NOTE: Put the "id_rsa" (private file) in ~/.ssh. There should only be one of these on a machine account.
#: NOTE: Put the “id_rsa.pub�? (public file) in ~/.ssh as “authorized_keys�? on remote machines; see “Remotebox�? below.
#* scp identity.pub skboyd@remotebox: [don't forget the last colon]
#* in ~/.bashrc:
#* export CVS_RSH=ssh
#* export CVSROOT=:ext:skboyd@m177.enme.ucalgary.ca:/localhost/cvsroot
#* eval `ssh-agent` {use the funny back single quotes}
: Remotebox:
#* cat identity.pub >> ~/.ssh/authorized_keys
# To avoid writing your passphrase every time you log on, run:
#* ssh-add
#: Should work if ssh-agent is already running (eval `ssh-agent` in the .bashrc file).
# Do the following to limit access to cvs for the users:
#* edit the public key installed in the .ssh/authorized_keys file with the following at the beginning of the public key line:
#: command="/usr/bin/ssh server"

NOTES ABOUT KEYS
Remember, the "authorized_keys" file is a concatenation of public (id_rsa.pub) keys,
and the "id_rsa" is the private key.
Every user on every computer should only have ONE "id_rsa" file,
but can have multiple "id_rsa.pub" files concatenated into
their "authorized_keys" file.

===Using CVS from a command line===
# To find a difference:
#* <code> $ cvs diff mylocalfile.cxx </code>
# To add a new file:
#* <code> $ cvs add mynewfile.cxx </code>
#* <code> $ cvs commit mynewfile.cxx </code>
# To update local file:
#* <code> $ cvs update -dCP </code>
#: or
#* <code> $ cvs update -dCP myfile.cxx </code>
# To check if a more recent version is available:
#* <code> $ cvs diff myfile.cxx </code>
#: or
#* <code> $ cvs update </code>
# To update CVS repository:
#* <code> $ cvs commit mylocalfile.cxx </code>

===Add a project to vtkMy===

# Add a new project directory in the vtkMy/src/Applications directory.
# Update the CMakeLists.txt file in /src/Applications to include the new directory in the SUBDIRS() list.
# Copy the CMakeLists.txt and source code files from an existing project such as AppMohr and put them into the new directory. These files can be edited for your new project.
# Edit the copied CMakeList.txt file and the change the name of the .cxx to the name of the new project.
# Run CMake, taking the source code from vtkMy/src and building the binaries in vtkMy/bin.
# Open the Visual C++ workspace and edit the source code (since at the moment it will be a duplicate of whatever project you copied in step 3).
# Compile your new code. Usually, all the development should be done in the “Debug�? mode (rather than “Release�?, etc.).
# If, to run your application, you need to include command line arguments, go to the menu item [Project][Settings], and on the ‘debug’ tab set the Program Arguments as shown.

[[Image:VtkMy_Project_Settings.jpg|center]]

==XEmacs==

===Pretty print===

:*For colour printing, select "Options", "Syntax Highlighting", "In this buffer"
:*In "Page Setup" set the margins to be 10 mm on the left and rights sides
:*In the "Printer Properties" on the "Effects" tab, use 90% of Normal size

==C Shell Scripts==

These scripts must be executable.
<pre>
$ chmod 775 myscript.com
</pre>

===Sample 1===

This file <code>aim2voi.com</code> shows the use of command line arguments in a CSH script.

<pre>
#!/bin/csh
#------------------------------------------------------------------------------
onintr end
if ($#argv < 1) goto usage
#------------------------------------------------------------------------------
aix $1.aim > $1.dsc
aic2voi $1.aim $1.voi
goto end
#------------------------------------------------------------------------------
usage:
#
echo ""
echo "Usage:"
echo ""
echo "aim2voi aim_filename (without aim extension)"
echo "will create a voi and dsc file from an aim"
echo ""
#
exit
#------------------------------------------------------------------------------
end:
exit
#------------------------------------------------------------------------------
</pre>

===Sample 2===

Similar to above, but <code>aim2bid.com</code> generates a temporary file called <code>stack</code> which
is used as input.

<pre>
#!/bin/csh
#------------------------------------------------------------------------------
onintr end
if ($#argv < 4) goto usage
#------------------------------------------------------------------------------
set i = $3
while ($i <= $4)
set nr = $i
if ($nr<10) set nr = "0"$nr""
if ($nr<100) set nr = "0"$nr""
# if ($nr<1000) set nr = "0"$nr""
echo "XY" >! stack
echo "$i" >> stack
echo "$5" >> stack
if ($6 != "") then
echo "0" >> stack
aio $1 "$2"_"$nr".bid 14 < stack
convert -size "$7" "$2"_"$nr".bid "$2"_"$nr"."$6"
\rm -f "$2"_"$nr".bid
else
echo "2" >> stack
aio $1 "$2"_"$nr".bid 14 < stack
endif
\rm -f stack
@ i = $i + 1
end
goto end
#------------------------------------------------------------------------------
usage:
#
echo ""
echo "Usage:"
echo ""
echo "aim2bid aim_filename bid_prefix first_slice last_slice scal_factor [form size])"
echo " (values are one-based) gif/tif/..."
echo ""
#
exit
#------------------------------------------------------------------------------
end:
exit
#------------------------------------------------------------------------------
</pre>

===Sample 3===

An example where a sequence of commands are executed resulting in an e-mail to let the user
know that their job is finished.

<pre>
#!/bin/csh
#
nohup faim -s $1; /bin/csh -cbf "Mail -s 'JOB $1 FINISHED' boyd@kin < ~/adm/mailer/faimjob.txt" &
</pre>

You would run this script called <code>faim.com</code> as follows

<pre>
$ faim.com inputfile
</pre>

===Sample 4===

This example uses two files. One called <code>wrap.com</code> is the base program that is called in
a more general program called <code>wrap_all.com</code> so that many different files can be processed
by the base script.

*wrap.com
<pre>
#!/bin/csh

echo "0" >! stack
echo "0" >> stack
echo "0" >> stack

/home/skb/works/fio/aim_io $1.aim $1_sub.aim minimal 15 < stack

/rm -f stack

exit
</pre>

*wrap_all.com
<pre>
#!/bin/csh

~/works/com/wrap calgary_dog_aclx_03-04_med_fem_left
~/works/com/wrap calgary_dog_aclx_03-04_med_fem_right
~/works/com/wrap calgary_dog_aclx_03-04_med_tib_left
~/works/com/wrap calgary_dog_aclx_03-04_med_tib_right

echo "DONE!"
exit
</pre>

==temple.ucalgary.ca==

===Configuration Details===

I include in the attachments my checklist I use for a Solaris 10
installation, adjusted to show only items particular to yours
and not my entire decision tree. I added brief explanations
for some of the items that might seem arbitrary otherwise.

Very similar decisions are made when installing any release
of Linux, Solaris, MS Windows or yet another operating
system - the details vary though.

http://docs.sun.com/ has all (too many) the details.

:*Operating System [[Media:01_OS.pdf| Download PDF]]
:*Configuration [[Media:02_Configuration.pdf|Download PDF]]
:*Mirror [[Media:03_Mirror.pdf|Download PDF]]
:*RAID5 [[Media:04_RAID5.pdf|Download PDF]]
:*Finishing Steps [[Media:05_Finishing_Steps.pdf|Download PDF]]

===Install XEmacs===
However, I would not install both Emacs and XEmacs at the same
time. Nowadays, I highly recommend installing only one of them,
with my preference given to XEmacs. Of course, only when
there are no specialized Lisp packages that require Emacs.

Then my installation would be like below:
<pre>
$ cd /cdrom/s10_software_companion/components/sparc/Packages
$ cat > /tmp/nointeraction
mail=
instance=unique
partial=nocheck
runlevel=nocheck
idepend=nocheck
rdepend=nocheck
space=quit
setuid=nocheck
conflict=quit
action=nocheck
basedir=default

$ pkgadd -a /tmp/nointeraction -d . -n SFWbdb SFWgcc34l SFWxmacs
[ Copyright and legal notices omitted for brevity. ]
21872 blocks

Installation of <SFWbdb> was successful.
[ Copyright and legal notices omitted for brevity. ]
69953 blocks

Installation of <SFWgcc34l> was successful.
[Copyright and legal notices omitted for brevity. ]
264202 blocks

Installation of <SFWxmacs> was successful.

$ emacs () { /opt/sfw/bin/xemacs $* ; }

$ pkgadd -a /tmp/nointeraction -d . -n SFWddd SFWgbin SFWgdb
[ To complete installation of the other packages you require. ]

$ pkginfo SFWbdb SFWddd SFWgbin SFWgcc34l SFWgdb SFWxmacs
system SFWbdb berkeleyDB - Berkeley Database Library
system SFWddd ddd - GNU Data Display Debugger
system SFWgbin binutils - GNU binary utilities
system SFWgcc34l gcc-3.4.2 - GNU Compiler Collection Runtime Libraries
system SFWgdb gdb - GNU source level debugger
system SFWxmacs XEmacs - text editor
</pre>

Developer

2007-11-02T18:11:18Z

Kksnishi: /* WinCVS and PuTTY for vtkMy */

==Hardware==

Used Alpha stations at http://www.islandco.com

==VMS Development==

===Getting started===

Editor:
<pre>
$! Define the editor
$ eve == "spawn/nowait edit/display=decwindows/tpu"
$ eve filename.txt
</pre>

Compiler:
<pre>
$! Define the compiler
$ C64 :== CC/POINTER_SIZE=64/check=pointer=all/optimize=(tune=ev6,level=5)

$! Compile the program 'ipl_scanco_c' and link it to existing libraries
$ c64 ipl:ipl_scanco_c
$!
$ link /exe=ipl:ipl_SCANCO_c -
ipl:ipl_scanco_c, -
ipl:ipl_scanco_c_ident/opt, -
ipl:ipl_proc/lib, -
ipl:ipl/lib, -
mu:scanco_ext/lib, -
dsrc:d3p_scanco/lib, -
scanco_lib/lib
</pre>

===SCTHIN (DS10L)===
<pre>
duck.kin.ucalgary.ca has been assigned IP address 136.159.130.33
netmask 255.255.255.0
default router 136.159.130.34
DNS servers 136.159.130.130, 136.159.130.3
</pre>

Login <code>microct</code> or <code>devel</code> with <code>not2lame</code>.

To boot into the cluster
<pre>
>>>boot ewa0
</pre>
To boot out of the cluster, unplug the ethernet cable and
<pre>
>>>boot
</pre>

To get to boot prompt, type <code>shutdown</code> on the login screen. Or, after powerdown, hit <code>ctrl-P</code> repeatedly.

There are two accounts:
:*microct
:*devel

===Installing packages on VMS===

Contacts:
Piet Schuermans
Mark Blanchard

====Freeware source====
http://h71000.www7.hp.com/freeware/freeware80/

Instructions for unpacking .tar.gz files on VMS
:1. Rename the file to file.tgz
:2. gunzip file.tgz (creates a file.tar)
:3. vmstar file.tar

====VMSTAR====

A tar program for VMS.

Either install from the source (build it), or apparently the binary can be downloaded from

http://h71000.www7.hp.com/freeware/freeware50/vmstar/alpha/

where you will find VMSTAR.EXE

When extracting files that contain "unix" filenames (e.g., config.h.in), make sure to extract the files with
<pre>
$ cvstar xof file.tar ! Option 'o' extracts ODS5 files with ODS2 format
</pre>

====CVS====

The sources can be retrieved from http://ftp.gnu.org/non-gnu/cvs/source/stable/

You will need a C compiler on OpenVMS. There are several versions of CVS available, but all of them need some tweaking before they can be successfully built.

:cvs-1.11.18 (see build instructions at http://lists.gnu.org/archive/html/bug-cvs/2005-01/msg00280.html)
:cvs-1.11.21 (do not use)
:cvs-1.11.22 (latest version as of May 26, 2007 -- may be built, but follow instructions as per v.18 above)

Download the .tar.gz file, rename it to .tgz once on vms system, use gunzip then vmstar:
<pre>
$ rename cvs-1.11.22.tar.gz cvs-1.11.22.tgz
$ gunzip cvs-1.11.22.tgz
$ vmstar xof cvs-1.11.22.tar ! option 'o' allows ODS2 naming.
</pre>

For all versions, make the following changes before starting:
:1. Before you attempt to compile 1.11.22 or later you will need make a copy of [.LIB]FNMATCH_H.IN as [.LIB]FNMATCH.H
:2. Correct typo in [.SRC]BUILD_SRC.COM change "libz" to "zlib"

Note:
The directory names would have been cvs-1.11.21.dir on Linux. However VMS doesn't allow more than 1 . in the name. If you enter

<pre>$ set process/parse=extended</pre>

in a terminal you'll be able to access these files. You rename them (i.e. cvs-1_11_21.dir).

NOTE
Piet Schuermans (mailps@mac.com) sent me a binary version of CVS on May 25, 2007 that I am currently using.

USAGE

Note that I have a "getting started on cvs for vms" document that can help.

OpenVMS is case sensitive for passing parameters. So put the parameters between " "

<pre>
$ cvs -d ":pserver:anonymous@public.kitware.com:/cvsroot/VTK" login
$ cvs -d ":pserver:anonymous@public.kitware.com:/cvsroot/VTK" co "vtknew/CMake"
</pre>

If your using this repository location frequently then
<pre>
$ define cvsroot ":pserver:anonymous@public.kitware.com:/cvsroot/VTK"
</pre>
after this you can skip the -d ...... parameter
<pre>
$ cvs login
vtk
</pre>

This will create .cvspass file in your home directory so your only
need to use the cvs login once
<pre>
$ cvs co "vtknew"
</pre>

public.kitware.com has ip address 66.194.253.19

===Update VMS licenses===

As user system:

<pre>$ lic list/full</pre>

and check which licenses are currently from 'MONTAGAR' and expire on Aug 31.

I recommend to only then replace those licenses with the new ones, and not load the whole license text file that you get from HP. Make a 'shortlist' of the licenses you need, then FTP them to the VMS system and copy and paste.

Layered Products (any licence, but NOT the openvms-Alpha itself!)

<pre>
$ lic del OPENVMS-ALPHA-USER
$ LICENSE REGISTER OPENVMS-ALPHA-USER -
/ACTIVITY=CONSTANT=100 -
/AUTHORIZATION=EDU-711643-12345 -
/DATE=31-AUG-2007 -
/ISSUER=MONTAGAR -
/PRODUCER=DEC -
/TERMINATION=31-AUG-2007 -
/UNITS=0 -
/CHECKSUM=1-BBME-NKAP-EAFK-CNCA
$ lic load OPENVMS-ALPHA-USER

$ lic del vmscluster
$ LICENSE REGISTER VMSCLUSTER -
/ACTIVITY=CONSTANT=100 -
/AUTHORIZATION=EDU-711643-12345 -
/DATE=31-AUG-2007 -
/ISSUER=MONTAGAR -
/PRODUCER=DEC -
/TERMINATION=31-AUG-2007 -
/UNITS=0 -
/CHECKSUM=1-GOOP-ALPF-PGKG-OBND
$ lic load vmscluster
</pre>

Then, on SCTHIN, for the basic 'openvms-alpha' license itself. In a cluster, this license must be limited to one computer only, so first, to delete the correct of the multiple openvms-alpha licenses only. If I ever wanted SCTHIN to be the server in a cluster, I should do the following (very unlikely!):
<pre>
$ lic list openvms-alpha/ful

$ lic delete openvms-alpha/auth=xxxxxx
! after first looking up the authori. of that montagar license.

$ LICENSE REGISTER OPENVMS-ALPHA -
/ISSUER=MONTAGAR -
/AUTHORIZATION=EDU-742405-743161 -
/PRODUCER=DEC -
/UNITS=0 -
/TERMINATION_DATE=31-AUG-2008 -
/ACTIVITY=A -
/OPTIONS=(NO_SHARE) -
/CHECKSUM=2-JMOA-GOFL-AKID-DHCJ

$ lic modify openvms-alpha/auth=EDU-742405-743161/include=scthin
! to make it available to scthin only.
</pre>

===MMS: VMS 'make' tool===

To start:
<pre>
$ mms
</pre>

An example from Bruno Koller of <code>descrip.mms</code>:
<pre>
.IGNORE
FFLAGS = /FAST/OPT=(LEVEL=5,TUNE=EV68,INL=ALL)/OBJECT=$(MMS$TARGET_NAME).OBJ
FGENER = /ALIGN=(NATURAL,SEQUENCE)/ASSUME=NOACCURACY/OPT=(LEVEL=5,TUNE=GENERIC,INL=ALL)/OBJECT=$(MMS$TARGET_NAME).OBJ_G

.FOR.OBJ
$(FORT)$(FFLAGS) UD:$(MMS$TARGET_NAME).FOR
$(FORT)$(FGENER) UD:$(MMS$TARGET_NAME).FOR
.FOR.INC
$(FORT)$(FFLAGS) UD:$(MMS$TARGET_NAME).FOR
$(FORT)$(FGENER) UD:$(MMS$TARGET_NAME).FOR

all :: uct_reconstruction.exe, uct_reconstruction.exe_generic
write sys$output "UCT_RECONSTRUCTION.EXE generated"

uct_reconstruction.exe :: -
recoident.opt, -
uct_reconstruction.obj, -
scli:uct_reco_constants.inc, -
calc_fan_beam_angles.obj, -
rebinning.obj, -
raw_to_rpro.obj, -
conereco.obj

link/exe=uct_reconstruction.exe -
recoident/opt, -
uct_reconstruction.obj, -
calc_fan_beam_angles, -
rebinning, -
raw_to_rpro, -
conereco, -
scanco_lib/lib

uct_reconstruction.exe_generic :: -
recoident.opt_g, -
uct_reconstruction.obj_g, -
scli:uct_reco_constants.inc, -
calc_fan_beam_angles.obj_g, -
raw_to_rpro.obj_g, -
rebinning.obj_g, -
conereco.obj_g

link/exe=uct_reconstruction.exe_generic -
recoident/opt, -
uct_reconstruction.obj_g, -
calc_fan_beam_angles.obj_g, -
raw_to_rpro.obj_g, -
rebinning.obj_g, -
conereco.obj_g, -
scanco_lib/lib

uct_reconstruction.obj :: ud:uct_reconstruction.for, -
scli:uct_reco_constants.inc

calc_fan_beam_angles.obj :: ud:calc_fan_beam_angles.for, -
scli:uct_reco_constants.inc

raw_to_rpro.obj :: ud:raw_to_rpro.for, -
scli:uct_reco_constants.inc

rebinning.obj :: ud:rebinning.for, -
scli:uct_reco_constants.inc, -
scli:ctdata_header_structure.inc

conereco.obj :: ud:conereco.for, -
scli:uct_reco_constants.inc
</pre>

Some notes:
:*UD is a logical for user disk search list over different disks, so I can compile on both alpha and vax with just having one source.

:*No need to put "ud:" at your site. Also, a few lines may have been wrapped which should be on one line (/fflag...) by the mail program.

:*Let me know if you want the mms installation file, you will need the hp campus mms license herefore (which you may already have)

===Alternative to MMS: MMK===

A free MMS replacement is called Madgoat MMK (http://www.madgoat.com/mmk.html).

===Alternative to EVE: NEDIT===

NEDIT is also available for VMS and offers a nicer editor, in my opinion (Mark Blanchard).

===Online VMS discussion lists===

info-vax (comp.os.vms)

==Linux Machines==

===Accessing Sodor disk===

From Konqueror in KDE, use a path like:

<pre>smb://HPL-NT\sboyd@hal/Sodor</pre>

==vtkMy==

vtkMy Development

Windows Setup:

'''Required Software: '''
Cmake 2.4.7 
WinCVS 2.0 
ITK 2.8.1 
VTK 2006-09-01 
Qt 3.3.6 Academic 

#Create directory C:\pack to keep all programs
#Download and install cmake-2.4.7.zip from: http://www.cmake.org/HTML/Download.html
#Download and install WinCvs 2.0.2.4 (released 2005-08-15) from:http://www.wincvs.org/download.html#WINCVS
#Download InsightToolkit-2.8.1.zip (hosted at SourceForge) from:http://www.itk.org/HTML/Download.htm
#Use WinCVS to download source files for VTK:
#*a. Open WinCVS and click menu Admin-> Preferences-> CVS Tab
#**Enter HOME: C:\pack
#**Click Ok
#*b. Open menu Admin-> Command Line
#**Enter the following:
#:::cvs -d :pserver:anonymous@public.kitware.com:/cvsroot/VTK login 
#:::cvs -d :pserver:anonymous@public.kitware.com:/cvsroot/VTK checkout –d 2006-09-01 VTK
#**Click Ok
#**You will be prompted for the password. Enter: vtk
#**Wait for checkout to complete
#Download vtkMy source using WinCVS
#*a. Verify home directory as set up in Step 5.a.i.
#*b. Open menu Remote-> Checkout Module
#** Enter the following settings:
#:::Module name and path on server: vtkMy
#:::Local folder to checkout to: C:\pack\
#:::Check box: CVSROOT
#:::CVSROOT: :ssh:username@m177.enme.ucalgary.ca:/localhost/cvsroot
#**Click Ok
#**You will be prompted for your password to access the machine
#**Wait for checkout to complete
#Build ITK using Cmake
#*a. Open Cmake
#*b. Choose C:\pack\InsightToolkit-2.8.1 as source code
#*c. Make C:\pack\ITK binary code location
#*d. Click ‘Configure’ and choose desired compiler
#*e. Use the following Cache values:
#::BUILD_EXAMPLES: ON
#::BUILD_SHARED_LIBS: ON
#::BUILD_TESTING: ON
#::BUILD_BACKWARDS_COMPATIBILITY: 2.4
#::CMAKE_INSTALL_PREFIX: C:/Program Files/ITK
#*f. Click ‘Configure’, all red values should turn grey
#*g. Click ‘Ok’, wait as Cmake will close automatically
#Build VTK using Cmake
#*a. Open Cmake
#*b. Choose C:\pack\VTK-2006-09-01 as source code
#*c. Make C:\pack\VTK binary code location
#*d. Click ‘Configure’ and choose desired compiler
#*e. Click the ‘Show Advanced Values’ checkbox and verify the following settings, all others can be left as defaults:
#::BUILD_EXAMPLES: ON
#::BUILD_SHARED_LIBS: ON
#::BUILD_TESTING: ON
#::BUILD_BACKWARDS_COMPATIBILITY: 2.4
#::CMAKE_INSTALL_PREFIX: C:/Program Files/VTK
#::VTK_USE_ANSI_STDLIB: ON
#*f. Click ‘Configure’, all red values should turn grey
#*g. Click ‘Ok’, wait as Cmake will close automatically
#Install Qt 3.3.6 Academic version
#*a. Run “qt-win-academic-3.3.6.exe”
#*b. When asked for license information choose to use license file and open “qt-license-3.3.6”
#*c. For installation options use defaults and be sure to build with shared libraries in Step 8
#:IMAGE
#Build vtkMy using Cmake
#*a. Open Cmake
#*b. Choose C:\pack\vtkMy\src as source code
#*c. Make C:\pack\vtkMy\bin binary code location
#*d. Click ‘Configure’ and choose desired compiler
#*e. Click the ‘Show Advanced Values’ check box and verify the following settings, all others can be left as defaults:
#::BUILD_APPLICATIONS: ON
#::BUILD_SHARED_LIBS: ON
#::BUILD_TEST_PROJECTS: ON
#::BUILD_BACKWARDS_COMPATIBILITY: 2.4
#::CMAKE_INSTALL_PREFIX: C:/Program Files/VTKMY
#::USE_ITK: ON
#::USE_QT: ON
#::USE_FLTK: OFF
#::VTK_DIR: C:/pack/VTK
#::ITK_DIR: C:/pack/ITK
#*f. Click ‘Configure’, all red values should turn grey
#*g. May have to click configure again if any red values are still present
#*h. Click ‘Ok’, wait as Cmake will close automatically
#Build VTK using Visual C++ 6.0 (or desired program)
## Open C:\pack\VTK\vtk.dsw
## Click ‘Build’
#Build ITK using Visual C++ 6.0 (or desired program)
#*a. Open C:\pack\ITK\itk.dsw
#*b. Click ‘Build’
#Build vtkMy using Visual C++ 6.0 (or desired program)
#*a. Open C:\pack\vtkMy\bin\vtkmy.dsw
#*b. Click ‘Build’

===WinCVS and PuTTY for vtkMy===

NOTE: An alternative CVS client has been suggested, but not tested:
<pre>
SmartCVS from www.syntevo.com with a foundation license.
</pre>

Setting up WinCVS to use PuTTY is fairly straightforward, but does require a few configuration settings in addition to installing the software. You can do it with the following steps.

#Install PuTTY (http://www.chiark.greenend.org.uk/~sgtatham/putty/).
#Install wincvs (http://www.wincvs.org/)
#Make a key:
#*Follow menus: Start/Programs/PuTTY/PuTTYgen From the PuTTY Manual: 
#:...press the "Generate" button and PuTTYgen will begin the process of actually generating the key.
#*First, a progress bar will appear and PuTTYgen will ask you to move the mouse around to generate randomness. Wave the mouse in circles over the blank area in the PuTTYgen window, and the progress bar will gradually fill up as PuTTYgen collects enough randomness. You don't need to wave the mouse in particularly imaginative patterns (although it can't hurt); PuTTYgen will collect enough randomness just from the fine detail of exactly how far the mouse has moved each time Windows samples its position.
#*When the progress bar reaches the end, PuTTYgen will begin creating the key. The progress bar will reset to the start, and gradually move up again to track the progress of the key generation. It will not move evenly, and may occasionally slow down to a stop; this is unfortunately unavoidable, because key generation is a random process and it is impossible to reliably predict how long it will take.
#*When the key generation is complete, a new set of controls will appear in the window to indicate this.
[[Image:putty_key_generator.jpg|center]]
# Set the key comment and password. Set the key comment to your email address by typing it into the "Key Comment" box. Set the password by entering it twice, once in the "Key passphrase" box and once in the "Confirm Passphrase" box.
#Save the keys: save the public key on your desktop as <code>identity.pub</code> and the private one as <code>identity.ppk</code>
#Email the identity.pub file as an attachment to skboyd@ucalgary.ca and ask for it to be added to the .ssh/authorized_keys file for your cvs repository. Please specify which repository you are requesting access to in the e-mail (i.e., vtkMy).
#Setup environment variables
#* Choose Menus: Start/Settings/Control Panel
#* Double click on the "System" Control Panel
#* Pick the "Advanced" tab and pick "Environment Varibles..."
#* Add User environement variables
#:- Add PLINK_PROTOCOL value "ssh"
#:- Add CVS_RSH value "plink"
#:- Edit or Add PATH appending value ";C:\Program Files\PuTTY"
# In WinCVS, bring up the "Preferences" dialogue box from the Admin menu
#* In the "General" tab put in your CVSROOT value, (i.e. <code>:ext:myusername@m177.enme.ucalgary.ca:/localhost/cvsroot</code>) [[Image:Wincvs general.jpg|center]]
#* Switch to the "Ports" tab.
#* Tick the box there labelled "Check for an alternate rsh name" and in the text entry field to the right enter "plink". [[Image:Wincvs ports tab.jpg|center]]
#* Select "OK" on teh "Preferences" dialogue box.
# Once you've heard back from the administrator (skboyd) that your ssh keys have been added, test your putty key configuration:
#*Double click on "identity.ppk" on your desktop. If this doesn’t start pagaent.exe automatically, then manually start the program from the directory you installed putty.exe.
#* If your identity file isn't already loaded, you will be prompted for the password you entered in step 4.
#*The Pageant icon (a little PC with a hat) should appear in the bottom right menu bar.

You should now be able to use WinCVS to access the repository, with a secure connection whenever Pageant is running. You can start Pageant by double-clicking on your identity.ppk file.

===Setting up CVS access from Linux/Unix===
*To understand the codes for a CVS update, see page 121 of CVS users guide, section A.16.2.
# Valuable resource for understanding ssh:
#* http://www-106.ibm.com/developerworks/library/l-keyc.html
#* http://www-106.ibm.com/developerworks/library/l-keyc2/
# Setting up SSH access from "localbox" to "remotebox": Localbox:
#* ssh-keygen -t rsa [use a passphrase]
#: NOTE: Put the "id_rsa" (private file) in ~/.ssh. There should only be one of these on a machine account.
#: NOTE: Put the “id_rsa.pub�? (public file) in ~/.ssh as “authorized_keys�? on remote machines; see “Remotebox�? below.
#* scp identity.pub skboyd@remotebox: [don't forget the last colon]
#* in ~/.bashrc:
#* export CVS_RSH=ssh
#* export CVSROOT=:ext:skboyd@m177.enme.ucalgary.ca:/localhost/cvsroot
#* eval `ssh-agent` {use the funny back single quotes}
: Remotebox:
#* cat identity.pub >> ~/.ssh/authorized_keys
# To avoid writing your passphrase every time you log on, run:
#* ssh-add
#: Should work if ssh-agent is already running (eval `ssh-agent` in the .bashrc file).
# Do the following to limit access to cvs for the users:
#* edit the public key installed in the .ssh/authorized_keys file with the following at the beginning of the public key line:
#: command="/usr/bin/ssh server"

NOTES ABOUT KEYS
Remember, the "authorized_keys" file is a concatenation of public (id_rsa.pub) keys,
and the "id_rsa" is the private key.
Every user on every computer should only have ONE "id_rsa" file,
but can have multiple "id_rsa.pub" files concatenated into
their "authorized_keys" file.

===Using CVS from a command line===
# To find a difference:
#* <code> $ cvs diff mylocalfile.cxx </code>
# To add a new file:
#* <code> $ cvs add mynewfile.cxx </code>
#* <code> $ cvs commit mynewfile.cxx </code>
# To update local file:
#* <code> $ cvs update -dCP </code>
#: or
#* <code> $ cvs update -dCP myfile.cxx </code>
# To check if a more recent version is available:
#* <code> $ cvs diff myfile.cxx </code>
#: or
#* <code> $ cvs update </code>
# To update CVS repository:
#* <code> $ cvs commit mylocalfile.cxx </code>

===Add a project to vtkMy===

# Add a new project directory in the vtkMy/src/Applications directory.
# Update the CMakeLists.txt file in /src/Applications to include the new directory in the SUBDIRS() list.
# Copy the CMakeLists.txt and source code files from an existing project such as AppMohr and put them into the new directory. These files can be edited for your new project.
# Edit the copied CMakeList.txt file and the change the name of the .cxx to the name of the new project.
# Run CMake, taking the source code from vtkMy/src and building the binaries in vtkMy/bin.
# Open the Visual C++ workspace and edit the source code (since at the moment it will be a duplicate of whatever project you copied in step 3).
# Compile your new code. Usually, all the development should be done in the “Debug�? mode (rather than “Release�?, etc.).
# If, to run your application, you need to include command line arguments, go to the menu item [Project][Settings], and on the ‘debug’ tab set the Program Arguments as shown.

[[Image:VtkMy_Project_Settings.jpg|center]]

==XEmacs==

===Pretty print===

:*For colour printing, select "Options", "Syntax Highlighting", "In this buffer"
:*In "Page Setup" set the margins to be 10 mm on the left and rights sides
:*In the "Printer Properties" on the "Effects" tab, use 90% of Normal size

==C Shell Scripts==

These scripts must be executable.
<pre>
$ chmod 775 myscript.com
</pre>

===Sample 1===

This file <code>aim2voi.com</code> shows the use of command line arguments in a CSH script.

<pre>
#!/bin/csh
#------------------------------------------------------------------------------
onintr end
if ($#argv < 1) goto usage
#------------------------------------------------------------------------------
aix $1.aim > $1.dsc
aic2voi $1.aim $1.voi
goto end
#------------------------------------------------------------------------------
usage:
#
echo ""
echo "Usage:"
echo ""
echo "aim2voi aim_filename (without aim extension)"
echo "will create a voi and dsc file from an aim"
echo ""
#
exit
#------------------------------------------------------------------------------
end:
exit
#------------------------------------------------------------------------------
</pre>

===Sample 2===

Similar to above, but <code>aim2bid.com</code> generates a temporary file called <code>stack</code> which
is used as input.

<pre>
#!/bin/csh
#------------------------------------------------------------------------------
onintr end
if ($#argv < 4) goto usage
#------------------------------------------------------------------------------
set i = $3
while ($i <= $4)
set nr = $i
if ($nr<10) set nr = "0"$nr""
if ($nr<100) set nr = "0"$nr""
# if ($nr<1000) set nr = "0"$nr""
echo "XY" >! stack
echo "$i" >> stack
echo "$5" >> stack
if ($6 != "") then
echo "0" >> stack
aio $1 "$2"_"$nr".bid 14 < stack
convert -size "$7" "$2"_"$nr".bid "$2"_"$nr"."$6"
\rm -f "$2"_"$nr".bid
else
echo "2" >> stack
aio $1 "$2"_"$nr".bid 14 < stack
endif
\rm -f stack
@ i = $i + 1
end
goto end
#------------------------------------------------------------------------------
usage:
#
echo ""
echo "Usage:"
echo ""
echo "aim2bid aim_filename bid_prefix first_slice last_slice scal_factor [form size])"
echo " (values are one-based) gif/tif/..."
echo ""
#
exit
#------------------------------------------------------------------------------
end:
exit
#------------------------------------------------------------------------------
</pre>

===Sample 3===

An example where a sequence of commands are executed resulting in an e-mail to let the user
know that their job is finished.

<pre>
#!/bin/csh
#
nohup faim -s $1; /bin/csh -cbf "Mail -s 'JOB $1 FINISHED' boyd@kin < ~/adm/mailer/faimjob.txt" &
</pre>

You would run this script called <code>faim.com</code> as follows

<pre>
$ faim.com inputfile
</pre>

===Sample 4===

This example uses two files. One called <code>wrap.com</code> is the base program that is called in
a more general program called <code>wrap_all.com</code> so that many different files can be processed
by the base script.

*wrap.com
<pre>
#!/bin/csh

echo "0" >! stack
echo "0" >> stack
echo "0" >> stack

/home/skb/works/fio/aim_io $1.aim $1_sub.aim minimal 15 < stack

/rm -f stack

exit
</pre>

*wrap_all.com
<pre>
#!/bin/csh

~/works/com/wrap calgary_dog_aclx_03-04_med_fem_left
~/works/com/wrap calgary_dog_aclx_03-04_med_fem_right
~/works/com/wrap calgary_dog_aclx_03-04_med_tib_left
~/works/com/wrap calgary_dog_aclx_03-04_med_tib_right

echo "DONE!"
exit
</pre>

==temple.ucalgary.ca==

===Configuration Details===

I include in the attachments my checklist I use for a Solaris 10
installation, adjusted to show only items particular to yours
and not my entire decision tree. I added brief explanations
for some of the items that might seem arbitrary otherwise.

Very similar decisions are made when installing any release
of Linux, Solaris, MS Windows or yet another operating
system - the details vary though.

http://docs.sun.com/ has all (too many) the details.

:*Operating System [[Media:01_OS.pdf| Download PDF]]
:*Configuration [[Media:02_Configuration.pdf|Download PDF]]
:*Mirror [[Media:03_Mirror.pdf|Download PDF]]
:*RAID5 [[Media:04_RAID5.pdf|Download PDF]]
:*Finishing Steps [[Media:05_Finishing_Steps.pdf|Download PDF]]

===Install XEmacs===
However, I would not install both Emacs and XEmacs at the same
time. Nowadays, I highly recommend installing only one of them,
with my preference given to XEmacs. Of course, only when
there are no specialized Lisp packages that require Emacs.

Then my installation would be like below:
<pre>
$ cd /cdrom/s10_software_companion/components/sparc/Packages
$ cat > /tmp/nointeraction
mail=
instance=unique
partial=nocheck
runlevel=nocheck
idepend=nocheck
rdepend=nocheck
space=quit
setuid=nocheck
conflict=quit
action=nocheck
basedir=default

$ pkgadd -a /tmp/nointeraction -d . -n SFWbdb SFWgcc34l SFWxmacs
[ Copyright and legal notices omitted for brevity. ]
21872 blocks

Installation of <SFWbdb> was successful.
[ Copyright and legal notices omitted for brevity. ]
69953 blocks

Installation of <SFWgcc34l> was successful.
[Copyright and legal notices omitted for brevity. ]
264202 blocks

Installation of <SFWxmacs> was successful.

$ emacs () { /opt/sfw/bin/xemacs $* ; }

$ pkgadd -a /tmp/nointeraction -d . -n SFWddd SFWgbin SFWgdb
[ To complete installation of the other packages you require. ]

$ pkginfo SFWbdb SFWddd SFWgbin SFWgcc34l SFWgdb SFWxmacs
system SFWbdb berkeleyDB - Berkeley Database Library
system SFWddd ddd - GNU Data Display Debugger
system SFWgbin binutils - GNU binary utilities
system SFWgcc34l gcc-3.4.2 - GNU Compiler Collection Runtime Libraries
system SFWgdb gdb - GNU source level debugger
system SFWxmacs XEmacs - text editor
</pre>