[PKG-Openstack-devel] Bug#784334: Bug#784334: Bug#784334: Inaccessible emergency shell on serial console

[Thomas Goirand]

Gaudenz,

first thanks a lot. This is very constructive, and I appreciate a lot 
this kind of contribution, which I'm sure, everyone will enjoy a lot.

About the quiet mode of the kernel, I'm really not sure. I've been 
thinking about it for a long time, and I still can't make up my mind 
about if we need the non-quiet output or not. Let me share what I have 
in mind.

All that kernel log is a lot of text wont be very useful. There's no 
advantage, in the cloud use case to see it, as we don't expect any 
kernel failures. More likely, if there's a problem, it will be because 
of something else (cloud-init, networking, etc.).

Why do you think kernel logs is useful?

On 05/18/2015 04:39 PM, Gaudenz Steinlin wrote:
> BTW, why are you using extlinux instead of grub2 which is the standard
> bootloader in Debian?

The only advantage of Grub is to provide an interactive boot menu, which 
IMO doesn't fit in the cloud use case. So I found that syslinux is much 
better because more lightweight. However, I may revisit this so that the 
image could work better for Xen.

> And one more thing. Why is the string "7.0.0-3" hardcoded into the image
> filename?

This has been fixed in the last version in Sid. The only thing which I 
didn't do is fix the minor version.

> I would suggest to either just use debian-${RELEASE}-amd64 or
> read the version number from /etc/debian_version (after debootstrap of
> course and read from ${MOUNT_DIR}/etc/debian_version, we don't want the
> version of the build host in the filename).

Sure. But this means renaming the output file after the facts, which we 
may not want to do. Best would be to find a way to know what the is the 
current point release number out of a wget / curl command (or something 
like this...). I'm opened to any suggestion for this.

Also, I'd like to add a --output-file option: it's trivial to implement, 
and may be useful.

Thanks a lot for the patch. I'll try to have a look at it asap. I'm not 
sure if the release team will accept it in Jessie, but I will try. They 
already accepted fixing all 4 bugs which were submitted against the 
openstack-debian-images package, which is great. Maybe they will only 
accept a subset of the fixes. We'll see! Maybe sending separate bugs and 
patches would help... Suggestions on how to make the acceptance by the 
release team more likely is also welcome.

Cheers,

Thomas Goirand (zigo)