e "*.iso" -o -name "*.ISO" 2>/dev/null)
The patch is attached. I have been hit by this today and have spent hours
trying to understand what was going on.
--
Modestas Vainius >From 650fb20f67028f92c0a36acd2a95fc45bc8ae361 Mon Sep 17 00:00:00 2001
From: Modestas Vainius
D
put "force-unsafe-io" in that file as well.
Great. Thanks for this info.
--
Modestas Vainius
signature.asc
Description: This is a digitally signed message part.
Hello,
On trečiadienis 20 Spalis 2010 22:33:34 Julien Cristau wrote:
> On Wed, Oct 20, 2010 at 22:20:31 +0300, Modestas Vainius wrote:
> > Btw, how will I be able to enable --force-unsafe-io for dpkg when it's
> > run under apt/aptitude? Maybe environment variable and/or
&g
well and slow the
whole process down. I think you need to expand --force-unsafe-io scope.
Btw, how will I be able to enable --force-unsafe-io for dpkg when it's run
under apt/aptitude? Maybe environment variable and/or /etc/dpkg/dpkg.cfg
option is a better solution then?
--
Modestas Va
Hello,
On sekmadienis 10 Spalis 2010 01:06:41 Otavio Salvador wrote:
> On Fri, Oct 8, 2010 at 8:55 PM, Modestas Vainius wrote:
> ...
>
> > It does not make much sense for dpkg to be in this uber-paranoid mode at
> > debian-installer time. If power fails, install proce
stall process will probably have to
be started from scratch anyway. What's more, obviously I have no choice to use
libeatmydata or similar to fight this dpkg behaviour at debian installer time.
In my opinion, dpkg should provide a way to turn off those offensive *sync()
calls and deb
6 matches
Mail list logo
