Content moved:
https://staff.eecis.udel.edu/docs/software/
1. Licensed ECE and CIS Software
ECE/CIS no longer manages downloadable licensed software: see UDeploy instead. Network licenses are still maintained for some commercial software.
1.1 ECE and CIS Personal systems
ECE and CIS Students/Faculty/Staff can access the MS Software catalog for research/academic personal use under the DreamSpark program. This is now handled at the College of Engineering level: please request a COE DreamSpark account via their help system at http://www.engr.udel.edu/admin/help/index.html
Some packages you download from DreamSpark are .iso disk images that are written to a blank CD or DVD disk for install. An alternative is a program Virtual CloneDrive that we use. It's free and will mount an .iso file directly as a disk, without having to use a blank CD/DVD. Virtual CloneDrive
2. StarOffice and OpenOffice Suites
OpenOffice is a suite that supports office productivity tools such as a word processor, spreadsheet, presentation and others. It is an Open Source GUI package with support for most common operating systems. It is installed at /usr/local/OpenOffice2
and can be started with the ooffice
command. It offers support for many file formats and has good compatibility with MS Office files.
StarOffice is based on OpenOffice, has commercial backing and is free for academic and research use. It is installed at /usr/local/StarOffice
and can be started with the soffice
command.
These office suites offer the following features:
One bug that has been noted is that exporting drawings in gif format doesn't work correctly. To work around this save your drawing in another format (jpeg, png, tiff) and use the convert
command to convert to a gif if you need to.
3. Window Managers
Supported window managers are fvwm2, windowmaker and JDS. Sample rc files for fvwm2 are in /usr/local/lib/startup/
. There is also an rc file for twm
located there which is an older basic window manager lacking many newer features found in others such as virtual screens.
The new Sun Java Desktop (JDS) is available and is the default for newer Solaris systems. It is based on GNOME and has many features that make Solaris an excellent desktop system. It uses a lot of memory and is not suggested to be ran on older systems, but runs well on new systems with enough memory and cpu power. Sun has an FAQ about GNOME here.
To switch your login to use JDS substitute the current WM command with gnome-session
in the ~/.xinitrc file. For example an edited .xinitrc file may include this section:
#choose your window manager
# uncomment the one that you want
#
## comment the following line for twm, one screen, uses ~/.twmrc
#twm
## comment the following line for fvwm2, uses multiple screens, uses ~/.fvwm2rc
#fvwm2
# or comment both and add another
gnome-session
This should complete the installation of the Sun Java Desktop.
3.1 Tips on using Sun Java Desktop (JDS)
Adding applications to the Launch
menu:
Using the Java Desktop, it is no longer necessary to edit config files to add new items to the Launch
menu. This is an example to show how to add Mozilla Firefox to the Internet
menu:
- Navigate the
Launch
menu and find the Internet
menu.
- Right-click inside the
Internet
menu and select Entire menu
in the pop-up menu
- Select
Add new item to this menu
- Fill in the dialog (Name: Mozilla Firefox; Command:
firefox
) and select an icon by clicking the button
- Click OK
This will create the launcher inside the Internet
menu. To copy the launcher to the Desktop, the menu icon can be dragged from the menu over to the Desktop and dropped. The icon will appear with no further configuration.
Enabling the Esound Daemon:
If your application can pipe sound events to a command you may want to enable the esound daemon for Sun Java Desktop. To enable this open the Launch
menu:
select Preferences
-->Desktop Preferences
-->Sound
and place a check mark next to Enable sound server startup
. Now, in your application pipe the sound output to the command esdplay
.
For Gaim, this option is in Preferences
-->Sounds
-->Sound command
.
3.2 Window Maker
Window Maker tries to emulate the elegant look and feel of the NeXTSTEP(tm) GUI. It is relatively fast, feature rich, and easy to configure and use.
For Window Maker (this is documented in /usr/local/WindowMaker/README_EECIS also), Set your PATH to have the bin directory included in it:
setenv PATH /usr/local/WindowMaker/bin:$PATH
Edit your .xinitrc to execute wmaker
And finally, run the Window Maker installation script:
% wmaker.inst
Other Sun developed and integrated desktop environments are available on Solaris. In particular CDE is installed, but not supported. To "run CDE" just use /usr/dt/bin/dtwm
as your window manager. Some of the "features" will/may not work.
There may be others installed, but not supported, so you are on your own with them.
4. Matlab
Matlab is one of the more popular applications and can be run using the matlab
command. It is available on Solaris (sparc) and Linux systems. A version for Solaris on x86/amd64 processors does not exist and Mathworks refuses to create one.
If you're experiencing crashes or problems when you use OpenGL -such as plotting 3 dimensional data (surf() etc.)- you can enable software emulation with the command opengl('software'). Often this is needed when using MATLAB remotely (such as SunRay).
For installing matlab on your own machine, see http://www.eecis.udel.edu/licdata.
5. Cadence
Cadence is available on Solaris (sparc) and Linux systems. Please read the file /usr/local/cadence/README for info on how to run Cadence.
6. Software available in /usr/local
All locally added on software is under /usr/local
. Everything else under /usr
, comes with the Operating System. All major/large packages have directories in /usr/local
, most with bin directories, which contain binaries to run and man directories with man pages. Many packages will have a README file under their top level directory to list bugs, resources, and helpful hints on running the programs. The following are some major directories with common software:
/usr/local/bin
-- many common programs
/usr/local/ucb
-- printing and other programs
/usr/local/etc
-- sysinfo and other programs
/usr/local/man
-- man pages
/usr/local/gnu
-- GNU software
/usr/local/X
-- X11 software
/usr/local/[package]
-- software for [package]
7. Java
Java is available under /usr/local/java
. Add /usr/local/java/bin
to your path to use it. There is also some documentation there for it.
On Solaris java is integrated for 32bit and 64bit, so both binaries can be found under /usr/local/java/. For Linux /usr/local/java/ is 32bit and the 64bit version can be found under /usr/local/java64/.
The version of java that you are using can be checked by running java -version
. You may also find a version of java that comes with the OS in /usr
8. Perl
The scripting language Perl is under /usr/local/perl5
, which includes man pages as well as the binaries and libraries. The suggested way to start your perl scripts is as follows.
#!/usr/local/bin/perl -w
The -w option is for warnings and can be removed once your script has been fully debugged and is ready for production use.
9. GNU
GNU software is under /usr/local/gnu
and includes popular programs such as gcc
and emacs
.
To have Solaris feel more like a GNU/Linux environment, put /usr/local/gnu/bin
in your path before /usr/bin
. It is best to leave /usr/bin
first though. Some of the more useful GNU programs start with a g to make them easier to call instead of the default one. For example there is gmake
, and gtar
.
10. Tcl/Tk
Tcl/Tk is available under /usr/local/tcl-tk
. There are also symbolic links out of /usr/local/X
for it. Also see /usr/local/tcl-tk/README
for more info.
11. Lisp
Lisp is under the /usr/local/lisp
directory. The current version being supported is sbcl and may be ran with the sbcl
command
12. Prolog
SWI-Prolog is installed in the /usr/local/SWI-Prolog/
. To use it add /usr/local/SWI-Prolog/bin
to your path and run pl
. Currently it is installed for Solaris (x86/amd64 and sparc). Some of the tests failed when testing on our Linux distribution, so it is not installed on Linux hosts.
13. LaTeX
Latex is installed under /usr/local/latex
and the installations for Solaris sparc, Solaris x86 and Linux all share the same configuration and font files.
The following are the commands used in processing LaTeX documents:
- latex - Is used to compile the LaTeX file into a DVI file. For example "
latex file.tex
" will produce file.dvi.
- dvips - Is used to convert the DVI file into PostScript. For example "
dvips file.dvi -o
" will produce file.ps. Leaving the -o off will cause the file to be printed instead. A -Pprintername can also be added to send it to another printer.
- xdvi - Will allow you to view the DVI file.
- dvipdf - Will convert a dvi file to a pdf file. For example "
dvipdf file.dvi
" will produce file.pdf. Notice no -o is given.
- ps2pdf and pdf2ps - Used convert a file from ps format to pdf or a pdf to ps.
- gv - If you don't like xdvi, you can use ghostview or gv instead to view the PS or PDF file instead.
See Latex for more information. Also, a good LaTeXe help guide is available here.
14. X11 programs
X11 programs can exist in many places. The main place for Solaris is /usr/openwin
, and for local additions /usr/local/X
.
15. MPICH2
MPICH2 v1.2.1 has been installed into /usr/local/mpich2 for:
- Solaris x86
- Solaris Sparc
- CentOS Linux x86_64
Note: The majority of the following information is also available in /usr/local/mpich2/README.
Please only use MPICH2 on machines you are authorized to do so. To see if the machine is general purpose or restricted to a specific user see sysinfo. http://www.eecis.udel.edu/wiki/ececis-docs/index.php/FAQ/GeneralInformation#toc4
In order to use mpich2 you will need to place /usr/local/mpich2/bin early in your path. tcsh users can do the following: set path = ( /usr/local/mpich2/bin $path )
You can verify the commands are found with: which mpd mpiexec mpirun
Next .mpd.conf should be created in your home directory:
touch .mpd.conf && chmod 600 .mpd.conf
Once that is done you'll need to create a password for MPD, this should be something random but should not be a password you use for anything else. Replace 'random-password' with your chosen password:
echo secretword=random-password >> .mpd.conf
To verify all of the above steps worked okay do the following:
mpd &
Wait a few seconds for MPD to start, then:
mpdtrace
mpdallexit
The output should be the hostname you are running on. Now you should create a file to store a list of hostnames to use, an example of this may be (tcsh):
touch mpd.hosts
foreach i ( node1 node2 node3 node4 node5 node6 node7 node8 )
echo $i >> mpd.hosts
end
For multiprocessor/multicore systems append :<n> after the hostname where n is the number of cpu cores the host has.
Then you can start the daemons on some of the hosts from mpd.hosts where <n> is the number of daemons to start:
mpdboot -n <n> &
For a compute cluster with a head node <n> should be the number of compute nodes plus one for the head node. Be sure to use the -1 option to mpiexec to not include the head node in computation.
Make sure you kill off your mpd processes with mpdallexit when finished!!
On systems that have more than one processor (SMP system) mpd and mpdboot take a --ncpus=n options to specify how many cpus the system(s) have. This changes the order in which processes start on which system. See section 5.1.7 of the install guide for more info.
To test the ring of mpds:
mpdtrace
Each host with mpd running should be listed. The command mpdringtest
can be used to test how long it takes to go around the ring. To test the ring is working:
mpiexec -1 -n <number> hostname
You will run your MPI code this way:
mpiexec -1 -n <number> mpi-program
The -1 option is so the job will not run on the head node.
For more help with mpiexec:
mpiexec --help
15.1 ECE/CIS Cluster for MPICH2
An ECE/CIS Research Linux compute cluster has been constructed using existing hardware. The cluster consists of four compute nodes and a head node. The four nodes are hoek{1-4}.eecis.udel.edu with the head node being mpi1.eecis.udel.edu. To use the cluster log onto the head node and launch jobs to run on the compute nodes.
Assuming you follow the above generic instructions you should be fine. Here are some specifics on how things should be done for this cluster. For the mpd.hosts file place the following four lines in it:
hoek1:8
hoek2:8
hoek3:8
hoek4:8
The 8 means that they have 8 cores each and the first 8 jobs will go to the first host list, the second 8 to the next host and so on.
For mpdboot run the following on mpi1.eecis.udel.edu:
mpdboot -n 5 --ncpus=8
Since there are four compute nodes with eight cores each the argument to the -n option to mpiexec should not exceed 32 and be sure to run with the -1 option so jobs will not run on the head node.
The hoeks may have a load on them from other users using mpi or other applications. To view the current status of the cluster visit http://ganglia.eecis.udel.edu/ganglia-hoeks/ from a host on the ECE/CIS network. You may want to adjust you mpd.hosts file according to the current load on the nodes for example.
16. MySQL
MySQL is a popular open source database program and is installed under /usr/local/mysql
.
The mysql client program command is mysql
. For more information see the MySQL documentation.
There is a server available for running mysql databases for research
activities. The hostname is db.eecis.udel.edu
and the mysql server
runs on the default port. Users may request a database for research
use by using the help system and request that a mysql database and user
be created. The request should include what the database name should
be. The database will be created with a default quota of 1GB and the
user's password will be set to a temporary value which should then be
changed. If multiple users need access to the database mention that in
the request. To change a mysql user password log into the database
with the temporary password and then change the password as the
following example shows.
% mysql -u (username) -h db.eecis.udel.edu -p (databasename)
(enter temporary password)
mysql> set password=PASSWORD('newpassword');
mysql> quit
% rm .mysql_history
% mysql -u (username) -h db.eecis.udel.edu -p (databasename)
(enter new password)
The .mysql_history
file is removed in the example to remove the storing of
the new password in plaintext.
If a server is needed where users need root access to the mysql
database a separate daemon can be started up running on another port
number and will run as a service on the database server. If this is
required be sure to mention that in the request. A reminder that this
server is intended for ECE/CIS research related activities.
For security purposes all traffic to db.eecis.udel.edu is blocked from the
outside. In other words only hosts on ECE/CIS networks may connect to it.
Alternatively you may start up your own by doing the following:
- Initialize the database administrative files with:
/usr/local/mysql/bin/mysql_install_db --datadir=/path/to/datafiles
- Be sure to follow the instructions it prints out on setting up the root user for your database.
- Start up the server by running:
/usr/local/mysql/libexec/mysqld --datadir=/path/to/datafiles &
- Where
/path/to/datafiles
is the directory you want to store your data.
The advantage of use db.eecis.udel.edu
is that the database will be installed as a service that will be up, as long as, the server is running.
17. CUDA
CUDA is now available on cuda.acad.ece.udel.edu
. The machine has four nVidia GT200 (Tesla C1060) GPU cards available for use.
https://computing.llnl.gov/linux/slurm? (Simple Linux Utility for Resource Management) is used to queue and run jobs on the CUDA hardware.
Jobs can be queued to run using the srun
command:
srun -N1 --gres=gpu:G <command>
-N1
indicates the number of nodes (computers). Currently, only one CUDA machine exists, so don't change this option.
G
is the number of GPU cards the job requires. Currently 4 cards are available for jobs on cuda.acad
.
Additional SLURM commands are:
squeue
- Shows the current state of the SLURM queue for cuda.acad
.
sinfo
- Shows info about the current SLURM configuration.
scancel
- Used to cancel a currently running job.
More information and documentation about SLURM is available at https://computing.llnl.gov/linux/slurm/documentation.html
CUDA is installed to /software/cuda
and the SDK to /software/cuda-sdk
. You may need to add /software/cuda/bin
to your path, and /software/cuda/lib
, /software/cuda/lib64
to your LD_LIBRARY_PATH. Please avoid setting your LD_LIBRARY_PATH if things are working without setting it. If you need space outside of your ACAD home directory submit a request for access to the /data partition. Note that this partition is NOT backed up, and is shared among the users.
SLURM is installed in /software/slurm
. You may need to add /software/slurm/bin
to your path.SLURM man
pages are available, you will need to add /software/slurm/share/man
to your MANPATH environment variable.
MATLAB versions R2010b and later can access CUDA equipped GPUs and benefit from some GPU performance features. An example commandline to run a MATLAB CUDA m-file of the Mathworks paralleldemo_gpu_backslash script:
srun -N1 --gres=gpu:2 /usr/local/Matlab_R2011a/bin/matlab -nodisplay -r paralleldemo_gpu_backslash
Matlab GPU paralleldemo_gpu_backslash
18. Finding files and folders with locate
If you cannot find what you are looking for you can use the locate
program to find what you are looking for. It is located in /usr/local/gnu/bin
and is much faster than using find
and many orders of magnitude easier on the servers.
19. Encryption
Encryption is the process of taking information (the plaintext input), applying an algorithm with a (secret) key to produce the encrypted output (ciphertext). To decrypt the ciphertext one would need to use a key with the correct algorithm to be able to read the plaintext information. This is very important in keeping information confidential. For information going over the network SSH and SSL/TLS are used. For information stored on filesystems there are a number of programs available to encrypt your data. Encryption is also critical in the protection of private information.
There are two types of encryption in common use, symmetric and assymmetric. Symmetric encryption involves a secret key, which is like a password. Symmetric algorithms include DES, 3DES, AES , and blowfish. The security of data encrypted with symmectric algorithms depends on the key (must be kept confidential), and key length. Generally, the longer the key the better. DES is not considered secure anymore and should not be used. Symmetric algorithms would be what you what to use to encrypt files for example. It is suggested that a secure algorithm like AES or blowfish be used to protect sensitive data (any data covered under PNPI) with a long enough difficult to guess key. Note that a strong encryption algorithm is only as good as the key given to it. The key should be sufficiently long enough and hard to guess to make a brute force attack infeasible. The key itself must also be kept secure. There is also a crypt
command but the encryption provided by it is not very strong.
Assymmetric encryption is also called public key. It has two keys that are related mathematically. One of the keys is public to be used by others and the other must be kept private to be used by the owner. These algorithms (RSA being the most popular) are used more by signing and in key exchange as they are more cpu intensive. Again, security is dependent on key length with longer being better. SSH and SSL/TLS make use of both types of encryption.
Hash algorithms are also important and associated with encryption. The most popular of these algorithms are MD5 and SHA1. They read in data as input and produce a signature (or hash, or fingerprint) of the data. In the case of MD5 it produces a 128-bit signature and SHA1 produces 160-bit signature.
When encrypting, compression, if done, should be done before encryption. This shortens the input to the encryption algorithm so it will run faster and can improve the result. Compression after encryption is worthless as encrypted data does not compress well and the file will probably actually be bigger. Compression with ZIP is the default for gpg.
19.1 Programs for encryption with examples
All Solaris and Linux systems have gpg
and openssl
installed, which provide many encryption options. Solaris also has the encrypt
command standard. For hash algorithms all Solaris and Linux systems have md5sum
and sha1sum
. Solaris also has the digest
command standard.
Some examples are provided here using openssl
, gpg
and encrypt
. In the examples %
is used to represent your shell prompt and the remainder of the line should be typed in.
OpenSSL
To encrypt a file using openssl
and AES with a 256 bit key do the following:
% openssl enc -e -in plaintextin -out ciphertextout -aes256
enter aes-256-cbc encryption password:
Verifying - enter aes-256-cbc encryption password:
Note the -e for encryption and that it prompts for the password used as the key twice. It is very important to remember the password (key) otherwise you will not be able to decrypt. After the file has been encrypted test decrypting it (example follows) and delete the plaintext input.
To decrypt (notice the -d for decryption) the file created in the previous example do the following:
% openssl enc -d -in ciphertextout -out outputfile -aes256
enter aes-256-cbc decryption password:
If the password is correct the plaintext will appear in outputfile
. Be sure to delete or protect this file when done. At all times also make sure that standard permissions would not allow someone to read the plaintext file.
If an incorrect password is enter something like this will be displayed:
bad decrypt
11044:error:06065064:digital envelope routines:EVP_DecryptFinal:bad decrypt:evp_enc.c:450:
Several other algorithms and key lengths can be used. For example to use AES with a 128 bit key use aes128 instead of aes256 and for AES with a 192 bit key use aes192. To use blowfish just replace aes256 in the examples with blowfish
To get more options run openssl
with no arguments and then type help
or enc help
.
The gpg
command is also very powerful. To get a list of options run gpg --help
. Near the top you will see the algorithms it supports:
Supported algorithms:
Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA, ELG
Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH
Hash: MD5, SHA1, RIPEMD160, SHA256
Compression: Uncompressed, ZIP, ZLIB
To encrypt a file with AES encryption and a 256bit key with gpg
use:
% gpg --symmetric --cipher-algo aes256 filename
Enter passphrase:
Repeat passphrase:
The encrypted output will be put into filename.gpg
Notice that it asks for a passphrase to emphasize the the length should not be too short. After verifying that you can decrypt the encrypted file be sure to delete the plaintext file. The --symmetric
option could be replaced with the shorter -c
option. To encrypt with another algorithm replace the aes256 with aes (for 128bit aes), aes192 or blowfish.
To decrypt a file encrypted with gpg
(regardless of the algorithm) do the following.
% gpg --decrypt filename.gpg
gpg: AES256 encrypted data
Enter passphrase:
Note that the algorithm used is displayed. The --decrypt
could be replaced with the shorter -d
option or left off entirely as decryption is the default. If a bad passphase is entered the following will be displayed:
gpg: decryption failed: bad key
Both openssl
and gpg
can do much more, such as assymmetric encryption and verification, but that is not covered here.
The Solaris encrypt program
To see a summary of what encrypt
can do run it with the -l option. The usage looks like this:
usage: encrypt -l | -a <algorithm> [-k <keyfile>] [-i <infile>] [-o <outfile>]
To use it to encrypt with aes do this:
% encrypt -a aes -i plaintextin -o ciphertextout
Enter key:
Note that it only asks for the key once. If the -o option and output file are left off the output will go to standard output. To decrypt use the decrypt
command like this:
usage: decrypt -l | -a <algorithm> [-k <keyfile>] [-i <infile>] [-o <outfile>]
encrypt -a aes -i ciphertext -o plaintextout
Enter key:
If the incorrect key is entered you will see the following:
decrypt: crypto operation failed: CKR_ENCRYPTED_DATA_INVALID
Again if the -o option and output filename are not given then output is to standard out. Both of the programs will also read from standard input if the -i option and input filename are not given.
The encrypt
and decrypt
commands are not as powerful as openssl
and gpg
, but are standard with Solaris and may be easier to use for some people.
For Windows users the University has some suggestions for encryption on their PNPI website.
20. Compression programs
There are several compression programs available. One that is becoming more popular and generally produces the smallest files is bzip2. The major programs involved with this algorithm are bzip2, bunzip2, bzcat
. The file extension used for a bzip2 file is .bz2
.
The GNU gzip format is very popular and performs well. It generally produces slightly larger files than bzip2, but is faster. The major programs are gzip, gunzip, gzcat
. The file extension used is .gz
.
The standard unix compress format is used by compress, uncompress
and zcat
and a .Z
extension is used. This format is not as common today.
The ZIP format, which should be familiar to Windows users, is also available with the zip
and unzip
commands.
21. Hash programs
There are several has algorithms (digital signatures), but MD5 and SHA1 are the most popular. Hash algorithms take data (usually a file) as input and produce as hash or signature or fingerprint of the data. MD5 produces a 128 bit hash (or Message Digest) of its input. SHA1 produces a 160 bit hash of its input. There are some security concerns with both of these algorithms and problems may be found in the future. They are still in common use. For new applications one should consider using SHA-224, SHA-256, SHA-384 or SHA-512, which produce a longer hash.
MD5 is used for many things. One of the more common is to verify that files have been downloaded correctly. It is common for a web site to include MD5 signatures for files that you download (for example source code). The idea is that you compute the MD5 signature of the file after downloading it and see if it matches what the web site says. If it doesn't then something must have went wrong. For this there is the gnu program md5sum
to compute the md5 signature (or checksum) of the file. To compute the SHA1 signature there is also a sha1sum
program. Solaris also has the digest
command that computes MD5 and SHA1 signatures. To compute the MD5 signature run digest -a md5 filename
. To use SHA1 instead replace md5 with sha1. Also, see the man page (man digest
) for more info.
Note that although the MD5 sum may match what a website says that is no guarantee that that the file is not a trojan (the attacker may have changed the MD5 listed to match the trojan file). More sites that have software down loads are now using public key signing with gpg which is more of a guarantee that the file is valid as it would be signed with someones private key.
22. Using gpg to verify downloads
More sites are using public key signing with gpg so one can verify that what was downloaded (usually source code or pre-compiled binaries) is what the person actually intended. It is a good idea to verify the signature of any downloads that provide a gpg detached file. To create the signature file one would produce a public/private key pair, use gpg with the private key to sign the file and make the public key available.
To verify a signature one needs 3 things:
- The downloaded file (often time a compressed tar file)
- The detached signature file for the file (usually has the same name as the file, but with a .asc, .sig or .sign extension added)
- The public key of the person that signed the file
To use gpg to verify a downloaded file do the following. First download both the file you want and the detached signature file associated with it. Then run gpg --verify downloaded.file.sig
with the name of the signature file you downloaded. Since you probably do not have the person's public key in your key ring yet gpg would not be able to check the signature. However, gpg will output what the key ID is. Some sites may have the public key listed in which case you can use the --import
option to import it. But the more general solution is to use the --recv-keys
option which imports the public key from a key server. An example using GNU tar version 1.15.1 follows.
$ gpg --verify tar-1.15.1.tar.bz2.sig
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
gpg: Signature made Tue Dec 21 10:22:40 2004 EST using DSA key ID 55D0C732
gpg: Can't check signature: public key not found
$ gpg --recv-keys 0x55D0C732
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
gpg: key 55D0C732: public key "Sergey Poznyakoff (Gray) <EMAIL REMOVED>" imported
gpg: Total number processed: 1
gpg: imported: 1
$ gpg --verify tar-1.15.1.tar.bz2.sig
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
gpg: Signature made Tue Dec 21 10:22:40 2004 EST using DSA key ID 55D0C732
gpg: Good signature from "Sergey Poznyakoff (Gray) <EMAIL REMOVED>"
gpg: checking the trustdb
gpg: no ultimately trusted keys found
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 325F 650C 4C2B 6AD5 8807 327A 3602 B07F 55D0 C732
Notice when using --recv-keys
that 0x is put in front of the key ID. This example shows that the signature is good for that public key. If it was not a good signing a bad signature message would be printed and in that case the file should not be trusted.
For more info see:
23. Version Control - CVS and Subversion
We support the Subversion version control system. There are two department servers specifically set up for running and managing subversion repositories. These are svn.eecis.udel.edu
for research use and svn.acad.ece.udel.edu
for academic use. The ECE/CIS Subversion How-To has all the information about requesting an ECE/CIS managed repository or setting up your own.
24. Department Wiki Server
A wiki installation has been set up for use by faculty, staff, and students working on research projects. The wiki 'flavor' is PmWiki, and a separate wiki site can be created for each user. All wikis are stored under http://www.eecis.udel.edu/wiki/<wikiname> and can be modified as if it were a standalone wiki. This installation is upgraded when new versions are released. Request a wiki by using the Help Request System. More information about our wiki is available on the main wiki page.
25. Virtual Box
Sun's Virtual Box is a free (for academic use) and fairly easy to use virtual machine environment. ECECIS maintains a few virtual images that can be used from within Virtual Box. Please see the Virtual Box HowTo for more information.
26. Intel VTune Performance Analyzer
From Intel's website, "Intel® VTune™ Performance Analyzer makes application performance tuning easier with a graphical user interface and no recompiles required. It is compiler and language independent so it works with C, C++, Fortran, C#, Java, .NET and more†. Unlike some products that offer only call graph analysis or only a limited set of sampling events, VTune analyzer offers both with an extensive set of tuning events for all the latest Intel® processors."
Our installation of VTune can be accessed by logging into vtune.acad.ece.udel.edu
. Instructions for use are provided when you login. To request access to the vtune group, please submit a Help Request.
27. On Campus Open Source Mirror
The UD Linux User Group mirrors a wide variety of open source software including some of the ECE/CIS supported operating systems and package repositories on their 24TB Sun X4500 (Thumper) server. Due to the location of the server it should provide a fast a reliable connection for users on campus.
For Information See:
http://lug.udel.edu
28. Cloud Computing
28.1 Seattle Cluster
We have a small 8-node cluster setup and available to the Seattle open computing project. [https://seattle.cs.washington.edu/html/]. Currently used in UD-CIS cloud computing courses and available by contacting ECE/CIS through the Help System.
28.2 Apache Hadoop
We have the same small 8-node cluster available via the Apache Hadoop cloud [http://hadoop.apache.org/]. It is available to the Academic Linux computers, located in the /usr/local/hadoop directory on those machines.
Comments
To add a comment, click the link below. You are free to contribute anonymously, but it is preferred that you sign your comments with your name. Simply add ~~
~~
to the end of your comment to sign it. Regardless of whether you sign your comment, your username will be visible on the History page.
(Add Your Own)