[Pkg-raspi-maintainers] RFC: extending the root partition/file system on first boot

[Michael Stapelberg]

On Fri, Feb 17, 2017 at 12:46 PM, Dominik George <nik at naturalnet.de> wrote:

> Hi,
>
> On Thu, Feb 16, 2017 at 09:35:48AM +0100, Michael Stapelberg wrote:
> > I wrote a Perl script which can be plugged into the boot process to
> extend
> > the root partition and root file system. The result is that the user is
> > greeted with a fully extended root file system on first login (see
> > screenlog.0).
> >
> > Here’s how to install the script on top of the preview image:
> >
> > sudo dd if=2016-11-24-raspberry-pi-3-stretch-PREVIEW.img of=/dev/sdb
> bs=5M
> > pmount sdb2
> > sudo cp ~/resizerootfs /media/sdb2/usr/bin/
> >
> > […]
> >
> > Any thoughts/comments? If not, I’ll go ahead and build a new preview
> image
> > with the script included.
>
> I am *very* much against adding stuff not installed from packages in
> Debian into the image. We should really not make the same mistakes as
>

Where are you getting this from? The script would of course be packaged
either in:
• vmdebootstrap, where I thought our packaging invocation should eventually
live as an example script (much like the ones for the cubietrack or
beaglebone)
• a separate package, to be created


> Raspbian. Instead, we should make very sure that the image is 1:1
> reproducible from Debian packages with debootstrap.
>
> That said, what about cloud-initramfs-growroot, which is in Debian,
>

Thanks for the tip. I gave it a brief look and find its pages and pages of
shell script much more complicated than the 2-pager perl script I proposed.
That said, if it works sufficiently well (so that we don’t have to debug
it), can easily be integrated into our image and doesn’t increase the image
size to an overly large extent, I’m happy to re-use it instead of
introducing a custom script.


> instead of adding non-Debian code that duplicates existing
> functionality?


I assume by “non-Debian”, you mean code that is not currently packaged in a
Debian package, and that my clarification above nullifies that point. If it
doesn’t, please explain why code written by a Debian Developer for the
Debian project which is found in a (hopefully at some point) official
Debian image would not qualify as a “Debian code” :).


>
> Cheers,
> Nik
>
> --
> PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17  FD26 B79A 3C16 A0C4 F296
>
> Dominik George · Hundeshagenstr. 26 · 53225 Bonn
> Mobile: +49-1520-1981389 · https://www.dominik-george.de/
>
> Teckids e.V. · FrOSCon e.V.
> Fellowship of the FSFE · Piratenpartei Deutschland
> Opencaching Deutschland e.V. · Debian Maintainer
>
> LPIC-3 Linux Enterprise Professional (Security)
>



-- 
Best regards,
Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-raspi-maintainers/attachments/20170217/50ea9713/attachment.html>