never mind, that bug is fixed now, or should be.

You can tell easily, simply start svmi, then look in the options:



You should see there listed your running version, numerically, that's the same data that the addons section uses, if that is null, it's still not fixed, if you see your version listed, it's fixed.
Back to top

actually, that should not have failed at all, can you also show me this data:

apt-cache search ^virtualbox-[2-9]\.[0-9] | awk '{print $1}' | cut -d '-' -f 2

that should show 3.0
Back to top

Hi,
I am not sure whether this feature is already in smxi and I am just too blind to find it.

I am using sidux and used until now i used siduxcc to remove the older sidux-kernels.
Now I have started to try the liquorix kernels and found that I have to remove the older ones manually as siduxcc seems only to take care of the sidux-kernels.
I can get around with that but would rather be able to remove older kernels together with their modules and headers completely from within smxi.

For the case that this already implemented, please give me a hint how I can find/access this function.

regards

Reiner
Back to top

Not fixed. Same error with svmi, option 10.


Back to top

I think I have found the problem. I had this repo enabled in my sources.list.

I removed it, removed VB and installed non-ose via svmi and the guest additions.

So I guess if the repo is enabled, svmi will not install guest additions, but will install VB.
Back to top

hmm, the problem is in identifying which version is in place, in theory, it shouldn't matter, but can you re-enable those repos, then do apt update, then show this:

apt-cache search ^virtualbox-[2-9]\.[0-9] | awk '{print $1}' | cut -d '-' -f 2

paste in that information, then show:

dpkg -l | grep -i virtualbox

then show: apt-cache policy virtualbox OR apt-cache policy virtualbox-<the results of step 1>
Back to top

h2 here you are.








Back to top

There's a problem in d-u with libuniconf4.6 and wvdial. According to sidux forums, and my own experience, you need to purge libuniconf4.4 first, then install 4.6.
I was wondering if smxi can, in some way, handle this situation? I mean, not hard to do without smxi if you know what you are doing, but the purge needs to be done with dpkg, not apt. Thanks.
Back to top

that fix is already in smxi, though I used apt to purge.
Back to top

Hi techadmin, I was wondering if you would be able to add lxviewer to smxi, as it is not available in debian repos though it seems to be available pre-compiled for rpm distros.
lx-viewer.sourceforge.net/ to the home page.
Here is a lx-viewer.sourceforge.net/faq.php to their faqs page, which goes a bit over my head:

Cad support is very sketchy in linux and it would be great to be able to install this easily through smxi

Thanks, Mike
Back to top