10%
07.04.2022
_time update )
Persistent mount opts: user_xattr,errors=remount-ro
Parameters:
checking for existing Lustre data: not found
device size = 48128MB
formatting backing filesystem ldiskfs on /dev/sdb
target
10%
10.11.2021
levels ranging from -7
, which is the fastest but least compression, to 22
, which is the slowest and greatest compression. According to the zstd
site, the compression speeds vary greatly
10%
11.05.2021
.50GHz
Processor base frequency 2.5GHz
Max turbo frequency 4.5GHz
Cache 8MB
Four cores (eight with hyper-threading)
45W TDP
8GB DDR4-2933 memory
Maximum of two memory channels
10%
29.09.2020
and doubles the cache size (from 3 to 6MB), in exchange for a small drop in baseline clock speed – 2.3 to 2.2GHz (peak drops from 3.2 to 3.1GHz).
Major Surgery
Legend has it that no one has ever
opened
10%
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
10%
05.08.2024
spans 100 million elements, taking up 800MB of RAM – not at all an unusual size in any kind of numerical computing. This system is equipped with 8GB of RAM, so allocating the array itself is no trouble
10%
03.04.2024
on machines with only one CPU core and 512MB of RAM; the minimalist K3s setup itself only uses 250MB. As one of the radical cost-cutting measures, K3s dispenses with the I/O-intensive etcd database
10%
05.12.2014
.519354 pkts=6 kpps=0.0 kbytes=0 mbps=0.0 nic_pkts=16 nic_drops=0 u=2 t=2 i=0 o=0 nonip=2
1415510244.519597 pkts=6 kpps=0.0 kbytes=0 mbps=0.0 nic_pkts=22 nic_drops=0 u=2 t=2 i=0 o=0 nonip=2
1415510247
10%
05.09.2011
can see how the arp cache poisoning works:
$ sudo nemesis arp -v -r -d eth0 -S 192.168.1.2 \
-D 192.168.1.133 -h 00:22:6E:71:04:BB -m 00:0C:29:B2:78:9E \
-H 00:22:6E:71:04:BB -M 00:0C:29:B2:78:9E
10%
26.01.2012
32KB < < 128KB
64
128KB < < 256KB
0
256KB < < 512KB
2
512KB < < 1MB
3
1MB < < 10MB
87
10MB < < 100MB
0
100MB < < 1GB
