On 2023-01-26, Cyril Brulebois wrote:
> Vagrant Cascadian (2023-01-25):
>> Though a larger image would take a bit longer and burn a few extra
>> write cycles for those who did not need to actually use the space.
>
> I have no idea how much people care how much time is spent copying things
> around
Hi Vagrant,
Thanks for your feedback!
Vagrant Cascadian (2023-01-25):
> Well, empty space does compress quite well, at least!
:D
> Though a larger image would take a bit longer and burn a few extra
> write cycles for those who did not need to actually use the space.
I have no idea how much pe
On 2023-01-25, Cyril Brulebois wrote:
> Cyril Brulebois (2023-01-24):
...
> # SD card images (might also be applicable to the upcoming ChromeOS images)
>
> Looking at how those images are built, it seems we have a predefined,
> per-arch image size (150M or 200M), and gen-hd-image that's called in
On Wednesday, 25 January 2023 23:01:01 CET Diederik de Haas wrote:
> This sounds like a nice solution for the SD card images.
> I myself always use a wired connection, but I saw yesterday that someone
> tried to use d-i for RockPro64 but didn't get any output on screen and then
> tried again using
On Wednesday, 25 January 2023 20:22:33 CET Cyril Brulebois wrote:
> # SD card images (might also be applicable to the upcoming ChromeOS images)
> ...
> All of this assuming that the end results can be appended as the third
> part of the + + combination!
This sounds like a nice solution for the
Hi,
Cyril Brulebois (2023-01-24):
> I'm also not sure what our plan for e.g. ARM images (concatenateable
> images) would be; I don't think we'll pull any firmware packages during a
> d-i build, so they wouldn't end up under [2], but maybe it'd be feasible
> to just concatenate some file/image con
6 matches
Mail list logo
