Package: os-prober
Version: 1.63
Followup-For: Bug #648251
Dear Maintainer,
* What led up to the situation?
I have Fedora installed on /dev/md5(RAID1) but update-grub / os-prober didn't
found it.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Implementing the patch from this bugreport was effective.
* What was the outcome of this action?
Linux on md device could not be started.
* What outcome did you expect instead?
Correct detection and starting of other Distribution on md.
BTW:
The following System Information was not correctly detected or the wiki is
outdated.
As described on https://wiki.debian.org/AptPreferences I have created
/etc/apt/preferences:
Package: *
Pin: release n=stable
Pin-Priority: 900
Package: *
Pin: release n=testing
Pin-Priority: 800
-- System Information:
Debian Release: 7.4
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages os-prober depends on:
ii libc6 2.13-38+deb7u1
os-prober recommends no packages.
os-prober suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/20140220040902.15449.35999.report...@rescue.ovh.net
