Search Criteria
Package Details: growpartfs 1.00-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/growpartfs.git (read-only, click to copy) |
|---|---|
| Package Base: | growpartfs |
| Description: | Extends a partition to fill available space |
| Upstream URL: | None |
| Licenses: | GPL3 |
| Replaces: | growpart |
| Submitter: | samuellittley |
| Maintainer: | samuellittley (lcastelli) |
| Last Packager: | samuellittley |
| Votes: | 5 |
| Popularity: | 0.066084 |
| First Submitted: | 2021-01-23 17:09 (UTC) |
| Last Updated: | 2021-01-23 17:09 (UTC) |
Latest Comments
samuellittley commented on 2021-01-23 17:19 (UTC)
This is currently used as part of https://github.com/GoogleCloudPlatform/compute-archlinux-image-builder to create Arch images for GCE.
I've created an updated growpartfs package, and requested for this to be merged into it
dvzrv commented on 2020-11-03 17:13 (UTC)
@lcastelli, @samuellittley: growpart is provided by cloud-utils in [community].
What is the benefit of growpartfs? If it has use on its own, please rename this package to growpartfs and depend on cloud-utils. Otherwise this package is in conflict with the AUR submission guidelines and needs to be removed.
bitfehler commented on 2019-03-17 11:53 (UTC)
TIL. Thanks a bunch, I was confused by the fact that the initramfs hook seems to be widely used, but this is indeed much easier!
lcastelli commented on 2019-03-17 04:20 (UTC)
Hi Conrad,
What is the benefit of running it from initramfs? It seems common filesystems support or require resizing while mounted, and that can be easily enabled on startup with
systemctl enable growpartfs@-.bitfehler commented on 2019-03-15 22:31 (UTC)
Thanks a lot for maintaining this!
I was wondering: how do you feel about adding mkinitcpio hooks for growpart to this package? I think many folks will want to use this tool from initramfs, and https://aur.archlinux.org/packages/mkinitcpio-growrootfs/ is unfortunately totally outdated. It also conflicts with this package because it supplies it's own /usr/bin/growpart, which gave me the idea that the hooks would actually best be kept in here. I have successfully grown an EC2 AMI's root using your package and a modified version of https://github.com/aryklein/mkinitcpio-growrootfs, so you could just use the -hook and -install file from there (the hook as an erroneous line break that needs to be removed: https://github.com/aryklein/mkinitcpio-growrootfs/blob/master/growfs-hook#L26-L27)
What do you think?