On Do, 21.05.20 10:06, Tobias Hunger (tobias.hun...@gmail.com) wrote:
> CopyFiles and CopyBlocks do make sense since they are probably going to get
> used widely. I am not so shure about subvolunes and even less so about
> setting up physical LVM volumes, multi-volume btrfs filesystems,
> dm-integ
Hi Chris,
On Sat, May 30, 2020, 10:09 Chris Murphy wrote:
> Future feature for the former case:
> - Btrfs seed/sprout feature expressly supports this use case for
> replicating a seed image when destination is also Btrfs.
> # mount /dev/seed /mnt
> # btrfs device add /dev/sprout /mnt
> # mount -
On Wed, May 20, 2020 at 4:01 AM Lennart Poettering
wrote:
>
> On Mi, 20.05.20 00:12, Tobias Hunger (tobias.hun...@gmail.com) wrote:
>
> >
> > The one thing that is frustrating is to get a machine image generated
> > by my build server onto a new piece of hardware. So I wanted to see
> > how far I
On Wed, May 20, 2020, 15:21 Lennart Poettering
wrote:
> > What about things like create subvolumes on BTRFS? systemd-tmpfiles
> > does support that.
>
> If this is desirable we could probably add MakeSubvolume= or so which
> is applied before CopyFiles= is run, or so.
CopyFiles and CopyBlocks d
On Mi, 20.05.20 14:29, Arian Van Putten (ar...@wire.com) wrote:
> > gpt-auto is not enough. I will want to set up pretty complex things
> like dm/crypto/etc.
>
> Note that gpt-auto-generator will detect if the partition is a LUKS
> partition or has dm-verity, and will set up a `/dev/mapper/root` d
On Mi, 20.05.20 13:58, Tobias Hunger (tobias.hun...@gmail.com) wrote:
> > To deliver the others, I want to add Encrypt= and Format= as
> > mentioned. To cover the 2nd usecase I then also want to provide
> > CopyBlocks= and CopyFiles=.
>
> I assume CopyBlocks= will just dd and so does not need a fo
> gpt-auto is not enough. I will want to set up pretty complex things
like dm/crypto/etc.
Note that gpt-auto-generator will detect if the partition is a LUKS
partition or has dm-verity, and will set up a `/dev/mapper/root` device
automatically.
But I don't think more complex devicemapper setups ar
Hi Lennart,
On Wed, May 20, 2020 at 12:01 PM Lennart Poettering
wrote:
> On Mi, 20.05.20 00:12, Tobias Hunger (tobias.hun...@gmail.com) wrote:
> > The one thing that is frustrating is to get a machine image generated
> > by my build server onto a new piece of hardware. So I wanted to see
> > how
On Mi, 20.05.20 00:12, Tobias Hunger (tobias.hun...@gmail.com) wrote:
>
> The one thing that is frustrating is to get a machine image generated
> by my build server onto a new piece of hardware. So I wanted to see
> how far I can get with systemd-repart and co. to get this initial
> deployment to
Hi Lennart,
On Tue, May 19, 2020 at 11:26 PM Lennart Poettering
wrote:
> So, yes, "systemd-makefs" was how I intended this originally to be
> done. However, I think that's not going to suffice in the long run,
> and instead systemd-repart will soon be able to format file systems
> natively by inv
On Di, 19.05.20 23:05, Tobias Hunger (tobias.hun...@gmail.com) wrote:
> to partition the new drive. That works nicely. Now how do I format
> those partitions? Systemd-mkfs springs to mind -- so I will need to
> identify those partitions in /etc/fstab. My system is immutable, so I
> have to create
Hello!
I am experimenting with automatically partitioning, formatting and
creating files on a new drive based on configuration. Systemd comes
with all the building blocks nowadays to do this, but I am still
struggling a bit.
I have created some partition definitions and ran systemd-repart to
part
12 matches
Mail list logo