Am 17.02.2015 um 13:22 schrieb Tomasz Gajc:
From my POV, person who maintains kernel should also maintain all kind
of dkms modules too, just to be certain that new kernel will work with
dkms and other stuff like kernel-firmware etc.
+1 because the kernel-modules generating by/through the dkms,
because they generating ever new versions of that(by need(really need)),
dkms it's a nice facility because it save at last space also, what's not
need,
do not generating, if you see it like so.. (but this less space it's not
really
important but also n reason)
so it's better for working together with dkms as alllll let generating ..
it's may also not bad to have because the modprobe, but it's the old
times who be need that, the this modern tames can we it saves that,
because, it's more targeted .. you see :)
and therewith can be it more controlled . Also at last thou systemd ,
where i more thending to have 2 Systems, one, like Moontrake an initd
releated Distriebution
and OpenMandriva more systemd for all cover up, you know..
some oldys who loves the old style, like me..
and other, they are more techies who love more system, like me also.. *bg*
I whant get you are an Example on hand, only one Word, Debian and the
Devuan <https://devuan.org/> Project
devuan have divided just because of systemd and initd so,
why should we not offer just two types of Linux and by the way, i think,
should be possible to have in one repository/cooker both versions of
init starter
but therewith should both be maintained ..
So back to the question, all modules or not.. in my opinion, not all,
because we have at moment only one init system actually systemd
and this is targeted so, generated by need..
and i look no one on ;) really i look on the floor *bg*
best regards
Blacky
2015-02-17 11:33 GMT+01:00 Colin Close <[email protected]
<mailto:[email protected]>>:
It seems from reports from the forums indicate that the latest
kernel we have released has broken the nVidia dkms driver package
(and probably the fglrx one too). The release of packages that
break into a stable release environment that break users systems
is not something that we should be doing.
How can we ensure that this does not recur in future kernel
updates to stable releases. If no mechanism exists in ABF perhaps
we can ensure enforcement in kahinah the QA tool.
I realise that these are binary packages and that some will argue
that they are not a priority (or similar objections) but the fact
remains that if we have issued them previously for a release and
we break by some update then we should fix them as they were part
of the release. For the time being we need to fix the dkms drivers
pronto.
Colin Close
QA Team
_______________________________________________
OM-Cooker mailing list
[email protected] <mailto:[email protected]>
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
