sync hd-media FLOPPY_SIZE with debian

[Carl Karsten]

please bump to 976560 (same as debian)

 https://git.launchpad.net/ubuntu/+source/debian-installer/tree/build/config/amd64/hd-media.cfg?h=ubuntu/disco
 FLOPPY_SIZE = 801792

https://salsa.debian.org/installer-team/debian-installer/blob/master/build/config/amd64/hd-media.cfg#L7
FLOPPY_SIZE = 976560

"large enough to put an Ubuntu iso in"

No it is not, and I would like it to be.

881M Oct 17 18:39 ubuntu-18.10-live-server-amd64.iso

[Dimitri John Ledkov (xnox)]

Why are you trying to put live-server-amd64.iso there? instead of the classic .iso?

I don't believe, putting live-server iso there will do anything good at all.

ubuntu-18.10-server-amd64.iso 2018-10-17 22:20 717M

What do you want to put an Ubuntu iso there for?

[Carl Karsten (carlfk)]

why this?
  ubuntu-18.10-server-amd64.iso
It isn't listed on
http://releases.ubuntu.com/cosmic/
I did find it on:
http://cdimage.ubuntu.com/releases/18.10/release/

717M does fit so good.

What for?
hd-media installer needs it
https://launchpad.net/iso-scan
"""
debian-installer component to scan hard drives for an installer ISO image.
This is used in installer builds for removable USB drives.
"""

higher level goal: hd-media/boot.img is an fs I can mount, cp a replacement boot loader syslinux.cfg file, done.
.iso is a read only fs, so not as easy to replace the file.

[Carl Karsten (carlfk)]

ubuntu-18.10-server-amd64.iso 2018-10-17 22:20 717M (that fit)

ubuntu-18.04.2-server-amd64.iso 2019-02-10 00:19 883M (this does not)
http://cdimage.ubuntu.com/releases/18.04.2/release/

+ zcat cache/bionic/hd-media/boot.img.gz
sudo dcfldd of=/dev/sda
24832 blocks (776Mb) written.
25056+0 records in
25056+0 records out
+ pmount /dev/sda
+ cp cache/bionic/ubuntu-18.04.2-server-amd64.iso cache/bionic/ubuntu-18.04.2-server-amd64.iso.SHA256SUM /media/sda
cp: error writing '/media/sda/ubuntu-18.04.2-server-amd64.iso': No space left on device

[Carl Karsten (carlfk)]

some fit, some don't:

FLOPPY_SIZE = 801792

ubuntu-18.10-server-amd64.iso 717M

ubuntu-16.04.5-server-amd64.iso 870M
ubuntu-18.04.2-server-amd64.iso 883M

prerelease:
 http://cdimage.ubuntu.com/ubuntu-server/daily/pending/
disco-server-amd64.iso 752M

[Carl Karsten (carlfk)]

I should have tested, the iso doesn't fit in the resulting free space.

set -ex

wget -N http://archive.ubuntu.com/ubuntu/dists/disco/main/installer-amd64/current/images/hd-media/boot.img.gz
wget -N http://cdimage.ubuntu.com/releases/19.04/release/ubuntu-19.04-server-amd64.iso

gunzip --keep --force boot.img.gz

mkdir -p mnt
sudo mount boot.img mnt

df mnt
ls -l ubuntu-19.04-server-amd64.iso

sudo cp ubuntu-19.04-server-amd64.iso mnt/

++ df mnt
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/loop1 800208 28612 771596 4% /home/carl/temp/disco/mnt
++ ls -l ubuntu-19.04-server-amd64.iso
-rw-rw-r-- 1 carl carl 790626304 May 10 01:44 ubuntu-19.04-server-amd64.iso
++ sudo cp ubuntu-19.04-server-amd64.iso mnt/
cp: error writing 'mnt/ubuntu-19.04-server-amd64.iso': No space left on device

[Carl Karsten (carlfk)]

This does not fit:

http://cdimage.ubuntu.com/ubuntu-server/daily/pending/
 eoan-server-amd64.iso.zsync 2019-06-24 06:53 754M

just to be sure:
wget.. unzip... like above
cp: error writing 'mnt/eoan-server-amd64.iso': No space left on device

Can we please bump FLOPPY_SIZE
or should I file a bug against the iso for being too big? ;)

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "debian-installer_hd-media-floppysize.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

[Dimitri John Ledkov (xnox)]

Our d-i is different / forked to the one from debian, and we don't merge all the changes they do. And vice versa. We do cherrypick things from time to time, which are useful.

I'm not convinced the proposed change is universally useful. And we do not want the size to grow arbitrarily large.

Setting to won't fix.