On Wed, Jun 3, 2015 at 2:36 PM, Kay Sievers <kay@xxxxxxxx> wrote: > On Wed, Jun 3, 2015 at 7:30 PM, Lucas De Marchi > <lucas.de.marchi@xxxxxxxxx> wrote: >> On Mon, Jun 1, 2015 at 3:26 AM, Rusty Russell <rusty@xxxxxxxxxxxxxxx> wrote: >>> Andreas Mohr <andi@xxxxxxxx> writes: >>>> Hi, >>>> >>>> I just had a not so nice experience >>>> when finally upgrading to a new 4.1-rc5 >>>> with CONFIG_MODULE_COMPRESS newly enabled - >>>> userspace binary parts (kmod 18 or 20 in my case) >>>> did not have compression enabled >>>> (at least on Debian 8pre, vs. encountering it enabled on FC21) >>>> since it does not seem to be >>>> the default build configuration of kmod (yet?). >>> >>> Sure. Let's get the maintainers to insert the actual version required >>> in the help text though. >> >> kmod supports gz since the first version and xz since version 3. So both >> of them can be safely fall into "it's supported since the beginning of >> kmod IMO". >> >> Regarding the "default configuration", there's no such thing. Each distribution >> uses a different one. > > You could add something similar to this: > > $ /usr/lib/systemd/systemd --version > systemd 220 > +PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP > +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS > +KMOD +IDN Indeed. I'm planning to do a release very soon and add something like this to it. If anyone is interested in contributing such patch it's very welcome, too :-) -- Lucas De Marchi -- To unsubscribe from this list: send the line "unsubscribe linux-modules" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
