Hello Debian kernel team.
I am an IBM mainframe systems programmer. I support
and maintain the z/VM operating system at my
installation which provides the virtualization that
allows multiple virtual Linux servers to share the
same LPAR (mainframe partition). I would like to make
an appeal for the default Linux kernel configuration
in Debian for the s390- and s390x-based kernels to
specify "CONFIG_DASD_DIAG=m" instead of "#
CONFIG_DASD_DIAG is not set". If you are using "MAKE
MENUCONFIG", you can find this option listed under
"Block Devices" as "Support for DIAG access to disks".
I could probably use a stock Linux kernel image if it
weren't for that one setting. Since I need it, I have
to re-fetch the kernel source code and re-compile a
custom kernel every time a security vulnerability fix
causes a kernel update. I don't see how this change
could HARM anybody. If the module isn't needed, it
WON'T be loaded. But if the module isn't there, it
CAN'T be loaded! This module (dasd_diag_mod) won't be
loaded unless loaded explicitly or unless it is
implicitly requested via an option provided to the
dasd_mod module when it is loaded. This change should
not affect anyone who may be running Linux natively
(i.e. running directly in an LPAR and not under z/VM).
I would also like to see this change made in the
kernels used by the Debian installer. This would
improve the installer's usefulness, both for initial
installs and also for use as a "rescue floppy".
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
