| Server IP : 49.231.201.246 / Your IP : 216.73.216.248 Web Server : Apache/2.4.18 (Ubuntu) System : Linux 246 4.4.0-210-generic #242-Ubuntu SMP Fri Apr 16 09:57:56 UTC 2021 x86_64 User : root ( 0) PHP Version : 7.0.33-0ubuntu0.16.04.16 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority, MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /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.