On Mon, Aug 14, 2006 at 11:11:46PM +0300, Panu Matilainen wrote:
On Mon, 2006-08-14 at 15:58 -0400, Jack Neely wrote:
> Again, show me how kmdl scales. A university/enterprise environment is
> not a 3rd party extras repository.
I pointed out earlier in this thread that we've used a scheme similar to
kmdl at work (speaking of thousands of systems here) rather successfully
for several years. And like I stated previously as well, this is just
for the record, I'm not arguing for either scheme.
It's not kmdl or kmod that scales, it's the processes for releasing
kernel modules and the depsolver+plugin to handle them which need to
"scale": a plugin can be smart enough to skip the kernel update if no
corresponding kernel module for the new version can be found, or abort
the entire update. But you'll need plugins for both schemes to catch the
situation where somehow a new kernel slipped out without having kernel
modules for it available, otherwise you can end up with unbootable
system.
- Panu -
--
Fedora-packaging mailing list
Fedora-packaging(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-packaging
Panu,
I can agree with this. Can you point out some working code?
Jack
--
Jack Neely <jjneely(a)ncsu.edu>
Campus Linux Services Project Lead
Information Technology Division, NC State University
GPG Fingerprint: 1917 5AC1 E828 9337 7AA4 EA6B 213B 765F 3B6A 5B89