20%
30.11.2025
-net.rules -e "s/$oldmac/$newmac/"
19 virt-edit $vmname /etc/sysconfig/network -e "s/vm1/$vmname/"
20
21 echo $newid >> vm-list.txt
22
23 echo "cloning finished, starting vm"
24 virsh start $vmname
20%
21.08.2012
-14.el6_3.x86_64.rpm | 2.2 MB 00:01
(3/4): php-common-5.3.3-14.el6_3.x86_64.rpm | 522 kB 00:00
(4/4): php-gd-5.3.3-14.el6_3.x86_64.rpm
20%
14.03.2013
(pr->pr_path), 0);
17 [...]
18 error = copyinstr(j.hostname,
19 &pr->pr_host, sizeof(pr->pr_host), 0);
20 [...]
21 pr->pr_ip = j.ip_number;
22 pr->pr_linux = NULL;
23 pr->pr_securelevel = securelevel
20%
09.08.2015
'
'/[Mm]an/p'
sed -n '/[Mm]an/p' textdata.txt
2
All lines except 3 through 5
'3,5!'
sed -n '3,5!'p textdata.txt
3
All lines except those containing 'Man
19%
30.11.2025
/sda
20 Account information:
21 ACL information:
22 ALL
Network Bonding
To prevent the network cards and thus the connection to the cluster and storage network from becoming a single
19%
11.06.2014
image, and then Volatility [3] and Mandiant Redline [4] for further investigation. In this paper, I dive more deeply into Redline and Volatility.
To begin, I review a raw memory dump of a known malware
19%
11.04.2016
? 00:02:39 systemd
You can define a container launched in this way as a system service with
machinectl start Fedora-Cloud-Base-22-20150521.x86_64
and then log in to the container using
19%
13.06.2016
the Containers
# machinectl pull-raw --verify=no http://ftp.halifax.rwth-aachen.de/fedora/linux/releases/22/Cloud/x86_64/Images/Fedora-Cloud-Base-22-20150521.x86_64.raw.xz
# systemd-nspawn -M Fedora
19%
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
19%
30.11.2025
compared with version 1.x are noticeable in Tomoyo versions 2.2.x and 2.3.x; the current version 2.5 only lacks a couple of features. Unfortunately, version 2.5 is only available in Linux kernel 3.2, which
