On Sun, Jan 20, 2019 at 10:25:54AM -0500, Hendrik Boom wrote:
>Just for comparison, on Devuan ascii (stretch wirhout systend), I get:
>
>root@midwinter:/home/hendrik# os-prober
>File descriptor 8 (socket:[13898]) leaked on lvs invocation. Parent PID 2831:
>/bin/sh
>File descriptor 9 (socket:[13899]) leaked on lvs invocation. Parent PID 2831:
>/bin/sh
>File descriptor 10 (socket:[16454]) leaked on lvs invocation. Parent PID 2831:
>/bin/sh
>File descriptor 11 (socket:[16455]) leaked on lvs invocation. Parent PID 2831:
>/bin/sh
>File descriptor 18 (socket:[13991]) leaked on lvs invocation. Parent PID 2831:
>/bin/sh
>/dev/sda6:Debian GNU/Linux buster/sid:Debian:linux
>root@midwinter:/home/hendrik#
>
>Here it also does not recognise the OS it runs on, but it *does* recognise
>Debian.
>
>Could the problem be that it is does not recognise
> (a) its own OS, nor
os-prober is not supposed to find the OS it's running under, that's
the design. It's only looking for other OS installations.
> (b) any OS those root partition in on an LVM volume, even if its /boot
> is on a primary partition?
It should happily find such setups. One of my own test systems at home
has root on LVM, no issues.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"Arguing that you don't care about the right to privacy because you have
nothing to hide is no different than saying you don't care about free
speech because you have nothing to say."
-- Edward Snowden
