On Thu, 20 Jun 2019 22:31:15 +0200
Ansgar Burchardt wrote:
> If _apt deserves a special solution, I would suggest assigning the
> _apt user a static uid instead of patching debootstrap.
it seems to me the simplest approach, from a technical point of view,
and it's the one I'm using since _apt us
On Thu, 20 Jun 2019 09:32:17 +0200
Ansgar Burchardt wrote:
> I don't think it is a good idea to require debootstrap to know about
> such details.
_apt user is standard to debian, but not its uid
the _apt user is created by the apt postinst, that cannot know anything
about the host system from w
as I have installed jessie with debootstrap, I cannot verify if the
swap config lines in /etc/crypttab are safe now, but reading the source
they are not
the patch I proposed 2 years ago sadly run only on linux but not on
kfreebsd nor hurd
may be that in the meanwhile we can add a warning in the R
the patch works perfectly, I hope it will be included in jessie+1
you can roughly apply the patch on debootstrap 1.0.66 with:
patch -r- /usr/sbin/debootstrap 668001.patch
patch -r- /usr/share/debootstrap/functions 668001.patch
and press enter to any question
after patching I can install a new s
Package: partman-crypto
Version: 56
Hi,
I think that using udev persistent device naming in /etc/crypttab
would be useful to prevent some dangerous situation, like the
following one.
I have a 3 disks setup with the first two in raid mode and the third as
archive. The swap partitions are encrypte
5 matches
Mail list logo
