Wols Lists wrote:
On 25/04/17 20:32, L A Walsh wrote:
Anyway... need to figure out why vmbox isn't working. Might have something to do with it deleting all it's run-config scripts... Nah... why would it do that?
Because, on Tumbleweed, it isn't supported?
VirtualBox isn't supported? ACK!
VBox *WILL* *BREAK* on any kernel upgrade, unless it is itself updated at the same time (closed kernel modules, don' cha no).
Already did that, and BTW, terminology detail: Open-source, out-of-tree modules != closed kernel module. (like Nvidia driver).
On any rolling release, VBox is a pain.
--- Depends on how often you update or whether dkms is provided.
It's forever breaking on my gentoo (except that I haven't updated it in ages because I'm expecting loads of grief when I do :-)
That's what dkms was invented for. It's on many distros, but not opensuse, because opensuse doesn't support users recompiling or updating their kernel. Suse _could_ facilitate this with a util similar to wicked, that toggles needed modules in a kernel-config file 'on' (instead of included as modules), rebuilding and reinstalling a local-HW specific version of the SuSE kernel that would boot without the need for an initrd. It might not be for everyone, but many unix vendors provided a script to do that: memory was less plentiful and disks were slower, so the less you transfered the faster your boot. Then, instead of people using 20-30MB per kernel(+initrd) in /boot, they could use as little as 6-7MB/kernel (which is why I lean toward smaller boot partitions) FWIW, in my current kernel I have 590 modules config'd with 48 built-in and 542 left for dynamic loading. Since boot, an additional 38 have loaded leaving 510 still on disk. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org