| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
That can take quite a while, so let the user know why propellor has
stalled.
|
|
* DiskImage: Fix rsync crash when a mount point does not exist in the
chroot.
* Fix bug in unmountBelow that caused unmounting of nested mounts to
fail.
This commit was sponsored by Jack Hill on Patreon.
|
|
|
|
|
|
|
|
Cheap flash drives need partitions aligned to 4 MiB in order to not be slow
(and to avoid extra writes). <https://lwn.net/Articles/428584/>
And at least 1 MiB alignment is generally a good idea, and most people
seem to think 4 MiB is for all drives.
I noticed that Parted.partitioned does not do that; the first
partition started at an offset of 1 MB, and subsequent partitions
from where it ends. (The 1 MB offset came from the PartedVal PartSize
instance, and note that it was not 1 MiB.)
* Parted: Add an Alignment parameter. (API change)
A good default to use is safeAlignment, which is 4MiB,
well suited for inexpensive flash drives, and fine for other disks too.
Previously, a very non-optimial 1MB (not 1MiB) alignment had been used.
* DiskImage: Use safeAlignment. It didn't seem worth making the
alignment configurable here.
Alignment is implemented by offsetting the first partition's start
position so it's aligned (making sure to leave room for the partition
table). Each partition is then extended as needed so the next partition
will start properly aligned.
Note that parted rejects partition tables that don't fit in cylinder
bounderies. Before, propellor let parted deal with the fine details
of layout, so that was not a problem. Now it's possible to set some
wacky Alignment not divisible by 512, or use Byte sizes for partitions
and create a partition table that parted rejects. But, using
safeAlignment and MegaBytes should always be safe.
Also, this fixes a rounding bug in Parted.calcPartTable.
It was rounding up to the nearest MegaByte when allocating remaining
disk space, so returned partition table that was actually larger than
the disk size.
This commit was sponsored by an anonymous bitcoiner.
|
|
Use "fat32" for both; these are not distinguished at the partition table
level.
This commit was sponsored by Henrik Riomar on Patreon.
|
|
|
|
|
|
Avoid needing to --spin host deployed from disk image to let its propellor
access its privdata.
This commit was sponsored by Boyd Stephen Smith Jr. on Patreon.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
sbuild-overhaul
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Diskimage.imageBuiltFor: New property to build a disk image for a Host,
using partition table information configured via the new properties
hasPartitionTableType, hasPartition and adjustPartition.
This lets Machine properties include eg /boot partitions that are known to
be needed by the bootloader, and the user can adjust those partitions and
add others.
This commit was sponsored by Brock Spratlen on Patreon.
|
|
sbuild-overhaul
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Instead, provide a property to let the user tell propellor to propagate the
host's proxy into the chroot. This makes it easy to toggle on and off and lets
the user explicitly specify how they want the chroot's proxy setup to work.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Reconsidered making services never run inside chroots, that seemed too
potentially limiting.
Using Info rather than checking policy-rc.d because it will also work
outside of debian, but more because policy-rc.d has an extremely
complicated interface and I didn't want to deal with it.
This commit was sponsored by Jochen Bartl on Patreon.
|
|
|
|
|
|
Service: Changed to use invoke-rc.d rather than service for starting
services. This notably means that in chroots, services will not be started.
This seems like the right thing to do, because running services inside
a chroot is problimatic. Use a real container system for running services.
Fixes the problem that, when building a disk image, using eg,
Apt.servicesInstalledRunning caused the service to be started in the
chroot, even though a policy-rc.d was in place to prevent it, because the
"service" command does not check policy-rc.d.
This commit was sponsored by John Peloquin on Patreon.
|
|
Install dnsmasq first to avoid connfile conflict
Don't set up container when in chroot, won't work. Propellor should
perhaps prevent this..
|
|
|
