13%
30.11.2025
-APIC-fasteoi pciehp, ath9k
10 18: 0 0 IO-APIC-fasteoi uhci_hcd:usb4
11 19: 2384012 0 IO-APIC-fasteoi ehci_hcd:usb1
12 20: 199725 0 IO-APIC-fasteoi uhci_hcd:usb2
13 21
13%
30.11.2025
user_u:system_r:httpd_t root 3728 1 2 10:49 ? 00:00:00 /usr/sbin/httpd
07 user_u:system_r:httpd_t apache 3730 3728 0 10:49 ? 00:00:00 /usr/sbin/httpd
08 ...
The weird
13%
05.02.2019
:
$ curl http://169.254.169.254
1.0
2007-01-19
2007-03-01
2007-08-29
2007-10-10
2007-12-15
2008-02-01
2008-09-01
2009-04-04
The cloud-init
package installed on an instance contains utilities for its early
13%
01.08.2019
is the registry – the storage space for Docker images – which did not even have a mechanism for authentication. Later, the image format was changed and Registry 2.0 (a.k.a., "Docker Distribution") was released
13%
30.11.2025
"creating" $vmname
09
10 virsh suspend rhstorage
11 virt-clone -o rhstorage -n $vmname -f /var/lib/libvirt/images/$vmname.qcow
12 virsh resume rhstorage
13
14 oldmac="52:54:00:B4:DF:EB"
15 newmac
13%
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
13%
12.05.2020
.04"
],
"RepoDigests": [
"nvidia/cuda@sha256:3cb86d1437161ef6998c4a681f2ca4150368946cc8e09c5e5178e3598110539f"
],
"Parent": "",
"Comment": "",
"Created": "2019-11-27T20:00:08
13%
18.07.2013
rq2 ra92
08 set rq3 cdrom
09
10 attach rq0 d0.dsk
11 attach rq1 d1.dsk
12 attach rq2 d2.dsk
13
14 attach -r rq3 cdrom.iso
15
16 set rl disable
17 set ts disable
18
19 set xq mac=08-00-2B-AA-BB-CC
20
13%
27.09.2021
08 integer :: counter
09 integer :: counter_limit
10 integer :: ierr
11
12 type(rec) :: my_record
13
14 counter_limit = 2000
15
16 ierr = -1
17 open(unit=8,file
13%
31.10.2025
of options, including dual four-core Xeon, dual six-core Xeon, or quad 12-core AMD processors ranging in speed from 2.2 to 2.9GHz with 24 to 128GB of RAM per server and up to 1TB of scratch local storage per
