On Fri, 10 Feb 2017 09:57:32 -0500,
Dave Reisner wrote:
> > + LC_ALL=C btrfs subvolume show "$1" | sed -n 's/^\tSubvolume ID:\s*//p'
>
> This looks like you're parsing human readable output to get the subvol
> ID. Is this really the only way to get this information?
As far as I can tell, yes.
From: Luke Shumaker
Motivation:
tmpfiles.d(5) has directives to create btrfs subvolumes. This means
that systemd-tmpfiles (which may be called by an ALPM hook) might
create subvolumes. For instance, systemd's systemd-nspawn.conf
creates a subvolume at
On Fri, Feb 10, 2017 at 9:46 AM wrote:
> From: Luke Shumaker
>
> Motivation:
>
> When installing the necessaryssary dependencies in the chroot, the
> ALPM hooks run; and if 'systemd' is a dependency, then one of the
> hooks is to run
> Some packages end up creating subvolumes through systemd-tmpfiles, (e.g.
> systemd-nspawn,) so we need to delete those as well, but there's no way
> to reliably list subvolumes under a certain subvolume relative to the
> filesystem, so we need a hard-coded list.
Actually there is, it just turns
From: Luke Shumaker
Motivation:
When installing the necessaryssary dependencies in the chroot, the
ALPM hooks run; and if 'systemd' is a dependency, then one of the
hooks is to run systemd-tmpfiles. There are several tmpfiles.d(5)
commands that instruct it to
On Fri, Feb 10, 2017 at 03:46:08AM -0500, luke...@lukeshu.com wrote:
> From: Luke Shumaker
>
> Motivation:
>
> When installing the necessaryssary dependencies in the chroot, the
> ALPM hooks run; and if 'systemd' is a dependency, then one of the
> hooks is to run