On 4/14/2011 8:13 AM, Stefan Seyfried wrote:
It seems totally useless.
I seemed to remember that it was supposed to be used for virtualized
guests, but it does not even have virtio included, so that can't be it...
Anyone here who can enlighten me?
I wouldn't need virtio for LXC container guests. If there were such a
package that let me install placeholder "kernel" package without really
installing any kernel but just satisfying various other rpm dependencies
that there must be a kernel package installed, I'd love that. I don't
need any paravirt drivers for disk or net or tty or anything.
Up to now I've just been either allowing the kernel to install and just
ignoring it, or force removing it and living with the annoyance that
some updates try to reinstall it, or force remove and mark the dependent
packages/patterns as "ignore and allow this to be broken".
Same goes for all grub/bootloader related stuff.
Letting it install and ignoring it is a little dangerous because then a
guest may try to load a module or write a bootloader. They normally
shouldn't be allowed to by the container system but it's easy to
misconfigure the container system and it's sort of "dangerous by
default" rather than the other way around, so not installing that stuff
I haven't looked at this package and don't know if there is any such
package, I'm just saying there's at least one scenario where an
essentially empty kernel package would solve problems and be the
opposite of useless.
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org