Control: tags -1 + patch
I figured out the grub-probe problem. It was really just grub being
outdated because I was building a stable Debian system instead of the
unstable one I believed I was building.
Using testing or unstable, grub was able to find the correct device,
but thanks to the fact t
I managed to trick update-grub to find the device by changing
vmdebootstrap making sure to use mount to place the btrfs subvolume in
the file system, thus making sure /proc/mounts have information about
it. But with that in place, another problem show up:
Configuring grub2
command failed: ['c
I had another look at setting up a root file system on a btrfs subvolume
now that vmdebootstrap support grub, and freshed up the patch to give it
another go.
Unfortunately, grub is not able to find / when it is a btrfs subvolume:
# vmdebootstrap --roottype btrfs --image=test.img --verbose --grub
[Petter Reinholdtsen]
> I had a look at how to implement this, and came up with the attached
> patch. It is able to set up btrfs, but the resulting image do not
> boot. I do not understand why, so I thought it was time to ask for
> feedback. :)
I managed to get the resulting image booting by rem
Hi.
I had a look at how to implement this, and came up with the attached
patch. It is able to set up btrfs, but the resulting image do not
boot. I do not understand why, so I thought it was time to ask for
feedback. :)
--
Happy hacking
Petter Reinholdtsen
diff --git a/vmdebootstrap b/vmdeboots
Package: vmdebootstrap
Version: 0.2-1
Severity: wishlist
At the moment, the file system type of the root created by vmdebootstrap
is ext4. Please extend vmdebootstrap to make root on btrfs an option.
This would provide block based consistency check and the ability to
extend the root file system
6 matches
Mail list logo
