16%
12.09.2013
packages/conf/distributions
Origin: TKmon
Label: tkmon
Codename: precise
Suite: stable
Architectures: i386 amd64 source
Components: main optional
SignWith: 0B8738CA
$ vi packages/conf/options
verbose
ask
16%
14.03.2013
will be using the Mongo shell to create a document (Listing 1).
Listing 1
Test
01 # mongo
02 MongoDB shell version: 2.2.0
03 connecting to: test
04 > use football
05 switched to db football
06 > db
16%
14.03.2013
, NCLOB), because you do not want to convert binary data, of course.
Conversion takes place automatically in transit (via Oracle Net); for example, a Euro sign typed on a Windows machine (0x80 in WIN-1252
16%
16.05.2013
in Listing 2, in which two modules are loaded (fftw and mpich2) before logging in to another node (n0 in this case). On the first login, the modules are loaded on the remote node. On the second login
16%
30.11.2025
status, and many others.
IPMI (Intelligent Platform Management Interface) was introduced in 1998 as a cross-vendor server management standard by Intel, HP, NEC, and Dell. The current IPMI 2.0 specifically
16%
30.11.2025
and Xen virtualization solutions. After adding the last missing components for cooperation with the Xen hypervisor to kernel version 3.0, the developers turned their attention to the Xen PCI back end
16%
03.09.2013
should not use legacy 10Mb technology, which is often encountered in the form of small switches that are still running, even if everything else has been modernized. Each hardware bottleneck leads to poor
16%
11.06.2013
available devices, including any LVM groups or RAID arrays.
In the example, Anaconda automatically creates the LVM group for the Fedora partition during the partitioning, and the same goes for the 500MB boot
16%
24.10.2011
, the CPU, the RAM (1,024MB), and the hard disk (320GB).
After investigating prices, the authors found that the hardware cost for an upgrade would be about half of the cost of a new machine. For large
16%
03.12.2015
the agent required for VMM from the dashboard – 7MB are unlikely to be an obstacle.
Figure 2: Scenarios supported by Azure Site Recovery – An overview
