Re: A 2025 NewYear present: make dpkg --force-unsafe-io the default?
On Fri, Dec 27, 2024 at 03:19:12PM +0300, Hakan Bayındır wrote:
> On 12/27/24 11:18 AM, Julian Andres Klode wrote:
> > On Tue, Dec 24, 2024 at 11:10:27PM +0900, Simon Richter wrote:
> > > ....
> > >
> > > So no, we cannot drop the fsync(). :\
> >
> > I do have a plan, namely merge the btrfs snapshot integration into apt,
> > if we took a snapshot, we run dpkg with --force-unsafe-io.
> >
> > The cool solution would be to take the snapshot, run dpkg inside it,
> > and then switch it but one step after the other, that's still very
> > much WIP.
> >
> Hi Julian,
Hello All,
> How would that work for non-BTRFS systems, and if not, will that make Debian
> a BTRFS-only system?
>
> I'm personally fine with "This works faster in BTRFS, because we implemented
> X", but not with "Debian only works on BTRFS".
Yeah, it feels wrong that dpkg gets file system code, gets code for one
particular file system.
Most likely I don't understand the proposal of Julian
and hope for further information.
> Cheers,
> Hakan
@Hakan, please made reading in the discussion order possible.
Groeten
Geert Stappers
--
Silence is hard to parse
Reply to: