Hi,
On Sun, May 19, 2013 at 12:11:30AM +0100, Colin Watson wrote:
On Sun, Mar 24, 2013 at 01:29:54PM +0100, Ivo De Decker wrote:
Is there still a reason to keep trying the regular mount? Are there cases
where grub-mount is expected to fail? Maybe only trying grub-mount could be
the
Hi Colin,
On Sun, May 19, 2013 at 12:11:30AM +0100, Colin Watson wrote:
When grub-mount fails, os-prober sets the device read-only and tries to
mount
it. It looks like the error reported in this bug was caused by setting the
device read-only, not by mounting it. The mount didn't change
On Sun, Mar 24, 2013 at 01:29:54PM +0100, Ivo De Decker wrote:
Is there still a reason to keep trying the regular mount? Are there cases
where grub-mount is expected to fail? Maybe only trying grub-mount could be
the default.
grub-mount is only available on architectures where GRUB has been
Hi,
On Mon, Mar 04, 2013 at 12:27:05PM +0100, Balint Reczey wrote:
os-prober uses 'mount -o ro', or grub-mount from 1.45:
commit 7ed9dec4d2c65056f211324f8e25a4d913b0f2a1
Author: Colin Watson cjwat...@debian.org
Date: Fri Apr 8 17:39:32 2011 +0100
Use grub-mount if it exists. This
Hi,
On 02/27/2013 05:28 PM, Torsten Jerzembeck wrote:
Julien Cristau wrote:
On Wed, Feb 27, 2013 at 13:41:45 +0100, Torsten Jerzembeck wrote:
Package: os-prober
Version: 1.42
Severity: grave
Justification: causes non-serious data loss
While updating the kernel on a storage server
Hi,
os-prober uses 'mount -o ro', or grub-mount from 1.45:
Please excuse me if this is trivial, but
'-o ro' does not prevent write access!
According to man:
Note that, depending on the filesystem type, state and kernel
behavior, the system may still write to the device. For example,
Ext3 or
Hi,
2013/3/4 q1we...@i.com.ua:
Hi,
os-prober uses 'mount -o ro', or grub-mount from 1.45:
Please excuse me if this is trivial, but
'-o ro' does not prevent write access!
According to man:
Note that, depending on the filesystem type, state and kernel
behavior, the system may still
7 matches
Mail list logo
