Hello,

I got a Slackware based LiveCD with Kernel 2.6.21. Unfortuantely
this slim LiveCD does not support loading *.lzm modules
(I would like to load/use a Windows emulator like Qemu, VirtualBox or
VMWare)

Questions:
Is it easier to upgrade that Slackware based LiveCD in order to support
loading *.lzm modules

or

convert the *.lzm modules to *.mo modules ?


Any feedback is appreciated very much. Thank's a lot!

John

This is not a Slax forum, so you won't find many here who know about '*.lzm' or '*.mo' modules -only about *.o and *.ko kernel modules. LOL
Try using a different version/brand of LiveCD thta has the features you want.

Thank's for the feedback. Now it's clear to me why "my" Slackware based distro does not at all support *.lzm- and *.mo-modules (because each disto (Slackware and Slax) uses a different module-format..


John

I'm not a slax expert, but I did download the latest version recently. From what I can see, the term "modules" is used by slax to refer to additional programs or program groups that can be added or removed either on-the-fly or by performing a second burn of the CD to include these items on the live CD. The two extentions you refer to .mo and .lzm are the extension for the slax modules which appear to have changed from one to the other in one of the latest slax version changes. These do not appear to have anything to do with linux kernel modules with the .o or .ko extension - at least not directly.

Hopefully I have not butchered that too much.

Yes, Franklin, you got it right. That's what I meant, though I wasn't so explicit. Slackware uses neither .mo nor .lzm 'modules'. Slackware lets you add programs by installing *packages*.
The OP should post qiestions regarding .lzm or .mo modules on the forum for whichever distro he is using. We're not terribly unfriendly here on the Slackware forum, but questions relating to so-called 'Slackware-based' distros are only rarely Slackware questions. The problems and quirks of Slackware-based LiveCD's are the part where those differ from real Slackware, so most users here don't have a clue (or interest) as to how to solve the issues.

I knew what you meant, but the OP seemed to be walking away with the wrong idea.

Thank's a lot for the clarifications.

Yes I was.... but now I do (hopefully) understand the thing with modules and that I have to go with "packages"

John