Dear Maintainer,
* What led up to the situation?
=> I'm SystemImager developper, and my dracut module requires i18n (same mobule across all linux distro flavors,
usefull when an emergency shell is triggered)
* What exactly did you do (or not do) that was effective (or
ineffective)?
=> Trying to port my module to debian raised an error: can't install my module because it depends on i18n one.
=> The primitive 09-console-setup is a regression as it doesn't allow end user to configure console via cmdline
parameters. The primitive module provides no hook to parse some specific parameters like rd.vconsole.keymap (or
font or any other parameters)
=> the primitive 09-console-setup doesn't install the following binaries (stty, setfont, loadkeys, kbd_mode) that
can be very usefull to end user when an emergency shell is triggered
* What was the outcome of this action?
=> Can't build systemimager initrd.img imager. Need to add a specific module-setup.sh for my module when built on
debian, also need to add some conditions in many hooks to handle this regression and do stuffs myself.
* What outcome did you expect instead?
=> At least SOMETHING STANDARD: an i18n module that would be optional (present in dracut debian package thus, but
that wouldn't interfere with debianisms), that would require and usedebian PROPRIETARY WITH NO VALUE ADDED
09-console-setup primitive module, that would provides the cmdline parser hook and that would install the
common i18n binaries (stty, setfont, loadkeys, kbd_mode)
Why by help do you cut down dracut while you could just add you 09-console-setup and have i18n module being made optional and use your module for concistency while keeping ability to take some parameters from cmdline and provide some tools to the user using emergency shell?
Sorry fort this somewhat unfriendly report, but as a developper, Debian is the only distro that trigger specific case to handle for no visible benefit. this report is an exaple between many others.
Even reporting a bug is far more difficult on this distro as there is no web bugzilla or equivalent. When developping in docker container in a company exchange based with no available SMTP gateway it's just horrible. what's the benefit over a standard web based bug reporting tool?