62%
20.06.2012
:root
bin:x:1:root,bin,daemon
daemon:x:2:root,bin,daemon
sys:x:3:root,bin,adm
adm:x:4:root,adm,daemon
tty:x:5:
disk:x:6:root
lp:x:7:daemon,lp
mem:x:8:
kmem:x:9:
wheel:x:10:root
mail:x:12:mail
uucp:x:14 ... Warewulf Cluster Manager – Part 2
62%
30.11.2020
runtime is surrounded by confusion and ambiguity. The CRI-O runtime [3] is an Open Container Initiative (OCI)-compliant container runtime. Both runC and Kata Containers are currently supported
62%
28.11.2023
36 [notify]
37 startup_notification = true
38 reminder_interval = 300
39
40 [notify.webhook]
41 hook_url = "https://webhook.site/4406e2a4-13cd-4c99-975c-d3456a148b26"
42
43 [probe]
44 [[probe
62%
30.11.2025
In KBOut PktOut
05 3 1 1421 2168 0 0 41000 90 0 2 0 0
06 3 2 1509 2198 64 2 49712 109 0 2 0 0
07 3 2 1403 2192 ... 9
62%
24.02.2022
machines; (2) the Metadata Service (MDS), which contains Metadata Targets (MDTs); (3) Object Storage Services (OSS), which store file data on one or more Object Storage Targets (OSTs); and (4) the clients
62%
23.03.2022
Inodes IUsed IFree IUse% Mounted on
udev 32968052 916 32967136 1% /dev
tmpfs 32983590 1409 32982181 1% /run
/dev/nvme0n1p2 31227904 814030 30413874 3% /
tmpfs 32983590
62%
21.01.2021
This first article of a series looks at the forces that have driven desktop supercomputing, beginning with the history of PC and supercomputing processors through the 1990s into the early 2000s.
...
May 1988
AMD K6-2
MMX and 3DNOW! SIMD, 200–570MHz; 64KiB L1 cache
Jun 1998
Pentium II Xeon
SIMD; L2 cache from 512KB to 2MB
Feb 1999
Pentium III
9 ...
This first article of a series looks at the forces that have driven desktop supercomputing, beginning with the history of PC and supercomputing processors through the 1990s into the early 2000s.
62%
03.01.2013
data on the Device (GPU)
dA = gpuSetData(A);
dC = gpuSetData(C);
d1 = gpuMult(A,B);
d2 = gpuMult(dA,dC);
d3 = gpuMult(d1,d2);
result = gpuGetData(d3); // Get result on host
// Free device memory
dA
62%
06.10.2019
": executable file not found in $PATH
0a2091b63bc5de710238fadc68ba3f5e0f9af8800ec7f76fd52a84c49a1ab0a7
Listing 3 shows that I do have a working container, so I'll deal with the network namespace
error now
62%
07.04.2022
,BROADCAST,RUNNING,MULTICAST> mtu 1460
inet 10.0.0.2 netmask 255.255.255.255 broadcast 0.0.0.0
inet6 fe80::bfd3:1a4b:f76b:872a prefixlen 64 scopeid 0x20
ether 42:01:0a:80:00:02 txqueuelen 1000
