27%
30.11.2025
in a specified city.
Listing 1
Display Date and Time
01 if [ "$1" = "" ]; then
02 echo "City name required."
03 exit
04 fi
05 city=`echo $1 | sed -e 's/ /_/g'`
06 z=`find /usr
27%
31.10.2025
will provide sub-par performance. A deeper treatment of these issues can be found in a recent article called "Will HPC Work in the Cloud?" [3].
Finally, any remote computation scheme needs to address
27%
30.11.2025
to give you consistent results with a running system. A cleaner approach would be to use an image backup program for Linux, such as Clonezilla [2] or Partimage [3], which means shutting down the system
27%
30.11.2025
GKF8S
16
DDR3, Registered, ECC, 4 rank
8.710
0.54
AL24M72E4BKH9S
8
DDR3, Registered, ECC, 2 rank
6.132
0.77
AL12M72B8BKH9S
27%
30.11.2025
.33
164.69
0.75
rand_mat_stat
3.37
39.34
11.64
54.54
22.07
8.12
rand_mat_mul
1.00
1.18
0.70
1.65
8
27%
31.10.2025
(pi*x)*dexp(-pi)
098 ENDDO
099
100 ! Bottom of unit square: (S)
101 DO i=1,m
102 x=delta*i
103 u(i,1) = dsin(pi*x)
104 ENDDO
105
106 ! Right hand side of unit square: (E)
107 DO j=1,m
108 u(m,j) = 0.0d0
109
27%
30.11.2025
to a remote host, allow this with the command
$ xhost +
and then export your display to the remote host on which you want to view the applications.
$ export DISPLAY=hostname:0.0
On the system
26%
31.10.2025
of a filesystem to which you entrust your valuable data.
Although Btrfs is on the right path to becoming the default filesystem on Linux, it will take a number of kernel releases until it equals ext3's reputation
26%
07.09.2025
Hub, S3, Samba v2 and v3, Dropbox, and possibly others.
One aspect of ratarmount
that I don’t like is that it mounts the archive as read-only and then keeps any changes or new files in a separate
26%
30.11.2025
CPU PROCESS/NLWP
# 173 daemon 17M 11M sleep 59 0 3:18:42 0.2% rcapd/1
# 17676 apl 6916K 3468K cpu4 59 0 0:00:00 0.1% prstat/1
# ...
# ZONEID NPROC SWAP RSS MEMORY TIME
