Have you actually tested any of these proposed changes before you come
barging in, or even looked for history as to why they're like that?

In reality you should send this, with them all separate, with
reasons/justification why you believe they should be changed  to the
kernel list.

> Just checked what is in kernel configuration and seems ATA driver IS
> compiled statically into the kernel =:-o
> Why? Most of the used HW more likely will be using SATA.
> It would be really good to change this by:

SATA is ATA, there's Parallel and Serial ATA.... part of the same
stack within the kernel.

> Fedora on mounting initrd is using from maaaany years ramfs (not ext fs).
> If you want to debug what happens on mounting even rootfs fs driver
> you can use all tools which you may need packing them into initrd.
> With grubby now adding such additional tools is incredibly easy thing
> to do, and you don't need to have ext compiled into the kernel to
> prepare such debug tooling.
> You cannot use on recovery ext driver if your crashed hardware
> resources does not provide any block device formatted as ext fs vol.
> IPv4 support is not modularised in Linux kernel source code at all so
> for now it is not an option to have or not to have IP stack in main
> kernel binary like it is on for example Solaris. And yes, it would be
> good to have modularise IPv4 support (like it is with IPv6) to handle
> scenarios where someone is using only IPv6 but it is matter of some
> serious work which needs to be done with rearchitecting few things in
> Linux kernel .. not a choosing something in kernel source code
> configuration only.
> I've asked about reasons because I'm trying to use everywhere btrfs as
> rootfs and for the people using xfs only in similar situations this
> ext driver compiled into the kernel is like 1kg lead weight dangling
> between the legs .. (especially on some ARM systems with only 256MB
> RAM)
> IMO looks like only reasons why ext still is compiled into the kernel
> are related to the fact that for quite long time no one have been
> trying to update kernel source code configuration files and now mamy
> drivers are not even enabled as loadable modules.
> Many staging drivers and especially USB HID drivers are not enabled as
> well. IRDA, FPGA support is not at all enabled (even as module).
> There is many things which can be now provided as module instead be
> compiled in to the kernel.
> Few examples after quick review:
> 1) gzip support in initrd is enough as grubby is using only gzip.
> +# CONFIG_RD_BZIP2 is not set
> +# CONFIG_RD_LZMA is not set
> +# CONFIG_RD_XZ is not set
> +# CONFIG_RD_LZO is not set
> +# CONFIG_RD_LZ4 is not set
> 2)
> -CONFIG_=y
> 3)
> 4) I don't think that PCMCIA needs to be hardcoded in to the kernel

Historically there's actually reasons why it did actually, have you
tested this on older hardware?

> 5) especially on x86* or on guest systems working inside VM

There's supported HW that needs it built in, again have you looked at
list/git history as to why it's like that.

> 6) if someone is using only SCSI this will be useful
> 7)

There's hard dependencies why i2c needs to be built in.

> 8) If someone is using Linux working in VM or headless HW ..

Actually a lot of VMs have mice mapped by default.

> (this is useless in case guest system in VM)

The AGP is likely legitimate, it's been disabled on most non x86
arches for some time (I think some old ppc64 systems being the other
hold out), although those systems then won't get graphics until much
later in the boot process....

> Some SCSI support can be more modularised as well

What about all the VMs you keep going on about? The SCSI_VIRTIO driver
is used by most modern linux virt platforms for storage and is a
dependency. It could possibly be modularised but would slow boot down.

> 9) I think that this could be modularised as well

I bet it actually can't be as I suspect it's probably used quite early
in the boot process for some systems booting to get system information
by other drivers.

> 10) Definitelly this can stay as module
> 11) Mentioned already ext support:

Why, it's used by the vast majority of systems, makes things easier to
debug and faster to boot, also allows to boot without a initrd in some

> 12) Not everyone is using quota
> This is not probably all ..

No, it's not, but it also doesn't take into account the reasons, some
may be historical why things are the way they are, and it's mostly
you're opinion which may or may not be close to reality. Ultimately a
lot of things like EXT4, ATA, SCSI and other things being built in
come down to boot speed, ease of support and debugging. Throwing this
out to devel in one massive big suggestion isn't really helpful. If
you want to get involved in the kernel by all means, the more the
merrier but do some research first and find out why things are the way
they are before wading in. In some cases I doubt you've even tested a
kernel build to see if it works, I can see one option I know has other
dependencies which would cause it to fail to even build!

devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Reply via email to