17%
11.04.2016
records in
1000000+0 records out
512000000 bytes (512 MB) copied, 1.58155 s, 324 MB/s
# dd of=file if=/dev/zero bs=512 count=1000000 oflag=direct
1000000+0 records in
1000000+0 records out
512000000 bytes
17%
07.06.2019
_web latest c100b674c0b5 13 months ago 19MB
nginx alpine bf85f2b6bf52 13 months ago 15.5MB
With the image ID in hand, you can inspect the image manifest:
docker inspect bf85f2b6bf52
17%
28.11.2022
/s, 133M issued at 133M/s, 81.6M total
0B repaired, 163.06% done, no estimated completion time
scan: resilvered (draid1:3d:5c:1s-0) 20.2M in 00:00:00 with 0 errors on Mon Oct 24 17:11:22 2022
17%
30.11.2025
an application happens to fail. In this article, I will look at a practical example in which VMware Server 2.0 refused to cooperate after the administrator updated the underlying operating system from Fedora 13 ... VMware Server 2.0 on recent Linux distributions
17%
30.11.2025
= debug
06 identity = rawhide.tuxgeek.de
07
08 # connector plugin config
09 connector = stomp
10 plugin.stomp.host = activemq.tuxgeek.de
11 plugin.stomp.port = 6163
12 plugin.stomp.user = unset
13 plugin
17%
30.11.2025
/nsswitch.conf (Konfigurieren der Namensauflösung)
08 ...
09 hosts files dns
10 ipnodes files dns
11 ...
12 # vi /etc/hosts
13 ::1 localhost
14 127.0.0.1 localhost
15 192.168.1.200 myiscsiserver myiscsiserver.local loghost
16 ... 0
17%
19.11.2019
locations and, in turn, introducing latency. As great as this sounds, SSDs are still more expensive than HDDs. HDD prices have settled to around $0.03/GB; SSD prices vary but sit at around $0.13-$0.15/GB
17%
30.01.2020
=1): err= 0: pid=1634: Mon Oct 14 22:18:59 2019
write: IOPS=118k, BW=463MiB/s (485MB/s)(10.0GiB/22123msec); 0 zone resets
[ ... ]
Run status group 0 (all jobs):
WRITE: bw=463MiB/s (485MB/s), 463Mi
17%
04.08.2020
-slim[build]: info=image id=sha256:231d40e811cd970168fb0c4770f2161aa30b9ba6fe8e68527504df69643aa145 size.bytes=126323486 size.human=126 MB
docker-slim[build]: info=image.stack index=0 name='nginx:latest' id='sha256
17%
03.02.2022
CPUs.
Listing 5
numactl
$ numactl --hardware
available: 1 nodes (0)
node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38
