25%
27.11.2011
needs direct access to the hardware and thus typically runs with root privileges. The exceptions are Mac OS X and Solaris, where the user only needs access privileges for the network interface card device
25%
12.03.2013
.6.32-220.4.1.el6.x86_64 kernel
GigaByte MAA78GM-US2H motherboard
AMD Phenom II X4 920 CPU (four cores)
8GB of memory (DDR2-800)
The OS and boot drive are on an IBM DTLA-307020 (20GB drive at Ultra ATA
25%
14.11.2013
. This translates to Google's experiencing about 25,000-75,000 correctable errors (CE) per billion device hours per megabit, which translates to 2,000-6,000 CE/GB-yr (or about 250-750 CE/Gb-yr). This is much higher
25%
11.06.2014
RewriteRule ^\.well-known/caldav / [R,L]
18 RewriteRule ^\.well-known/carddav / [R,L]
19
20 RewriteCond %{REQUEST_FILENAME} !-f
21 RewriteCond %{REQUEST_FILENAME} !-d
22 ... data available on iOS and Mac OS X and in Thunderbird and Evolution.
25%
11.02.2016
19
20 mysql> CREATE TABLE `data_random` (
21 `id` CHAR(32) NOT NULL,
22 `data` VARCHAR(64) DEFAULT NULL,
23 `ts` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
24
25%
10.06.2014
],
15 "nics": [
16 {
17 "nic_tag": "admin",
18 "model": "virtio",
19 "ip": "dhcp",
20 "primary": 1
21 }
22 ]
23 }
You can use this option for Windows virtual machines
25%
17.06.2017
a complete loss of data is in the cards.
Distributed Storage
Distributed file storage, as provided by the Network File System (NFS) [19], GlusterFS [20], or Ceph [21], offers a remedy. In principle
25%
18.07.2013
proxy_intercept_errors on;
17 ...
18 Filming location
19 ...
20 error_page 502 @ fallback;
21 proxy_next_upstream HTTP_500 http_502 http_503 http_504 timeout error invalid_header;
22 proxy_pass http
25%
18.07.2013
into Red Hat's cloud stack (Figure 1). After all, CloudForms 1.1, DeltaCloud 1.0, Storage Server 2.0, JBoss Middleware, and Enterprise Virtualization 3.1 form the foundation for the new products
25%
15.08.2016
ns2 ip addr add 1.1.1.2/10 dev veth2
18 $ ip netns exec ns1 ip link set veth1 up
19 $ ip netns exec ns2 ip link set veth2 up
20
21 $ ip netns exec ns1 ping -c2 1.1.1.2
22 PING 1.1.1.2 (1.1.1.2) 56
