| Server IP : 88.99.149.37 / Your IP : 216.73.216.141 Web Server : nginx/1.31.2 System : Linux server-88-99-149-37 6.12.0-124.56.5.el10_1.x86_64 #1 SMP PREEMPT_DYNAMIC Fri May 15 06:12:08 EDT 2026 x86_64 User : muralimurth ( 1015) PHP Version : 8.4.23 Disable Function : exec,system,passthru,shell_exec,proc_close,proc_open,dl,popen,show_source,posix_kill,posix_mkfifo,posix_getpwuid,posix_setpgid,posix_setsid,posix_setuid,posix_setgid,posix_seteuid,posix_setegid,posix_uname MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /proc/1/cwd/usr/share/doc/os-prober/ |
Upload File : |
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.