16%
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
16%
05.08.2024
relative to the base container, ubuntu
, changed significantly just by adding in the GCC compiler.
Listing 5: Build Process
$ podman build -t ubuntu-dev -f Dockerfile .
STEP 1/2: FROM ubuntu
STEP 2/2: RUN
16%
07.06.2019
6d2feb5e84bad9184441170d4898
mariadb latest mariadb@sha256:12e32f8d1e8958cd076660bc22d19aa74f2da63f286e100fb58d41b740c57006 RepoId
mariadb latest b468922dbbd73bdc874c751778f1ec0ec10817691624976865cb3
16%
25.03.2020
---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme0n1 152e778212a62015 Linux 1 21.00 TB / 21.00 TB 4 KiB + 0 B 5.4.12-0
You are now able to read and write from and to /dev
16%
18.12.2013
__ == "__main__":
12
13 local_dict = {'x':0, 'y':0, 'z':0,'value':0.0};
14 my_record = []; # define list
15
16 counter_limit = 2000;
17
18 f = open('test.bin', 'r+')
19 for counter in range(1,counter
16%
18.07.2013
buffered disk reads: 616 MB in
3.00 seconds = 205.03 MB/sec
$ hdparm -T /dev/sda
/dev/sda:
Timing cached reads: 6292 MB in
2.00 seconds = 3153.09 MB/sec
If this were a spinning disk, you would also
16%
30.11.2025
of read requests issued to the device per second.
w/s
: Number of write requests issued to the device per second.
rMB/s
: Number of megabytes read from the device per second.
wMB/s
: Number
16%
16.10.2012
6), and start stream blocking (line 7), which executes the command and waits for the response. Now, write the output to a variable (lines 9-12), close the stream (line 14), and send the response
16%
30.11.2025
dh_group modp1024;
09 }
10 generate_policy off;
11 }
12
13 sainfo address 192.168.2.0/24 any address 172.16.0.0/16 any {
14 pfs_group modp1024;
15 encryption_algorithm aes256;
16
16%
31.10.2025
System, DUP: total=8.00MB, used=4.00KB
Metadata, DUP: total=1.00GB, used=79.20MB
If Btrfs only has one device available when the filesystem is created, it automatically generates a duplicate
