Using USM to create porteus modules from a folder

[jmurrinux]

Hello forum,
Working hands on to learn Porteus, I would like to ask for clarification or verification of a procedure I'm doing to create modules with USM and questions related to how I'm doing it.


Here is my step by step list:

Trying to install Teamviewer 9 on Porteus:
Session on root

✫ Downloaded program: teamviewer_linux.tar.gz
✫ Created a folder as [unpacked_applications]
✫ Extracted the downloaded program into [unpacked_applications]
✫ Ran USM
✫ Used tools > Porteus > create a Porteus module from a folder
✫ Selected folder [unpacked_applications/Teamviewer9] module created
✫ Moved module to the Porteus/modules folder
✫ Selected module, right click, then activate module

☯ Will that be sufficient to get a program running or do I need more conventions as recommended on the FAQs for creating Porteus/Slax module guidelines?
☯ If I delete the folder [unpacked_applications/Teamviewer9] will that affect the module operation? I understand that when I create a module, what I'm doing is compressing the application files into a compression language that translate the program to Porteus-Guese language.


See you later

[brokenman]

Files that end with tar.gz are probably source code. Converting these into a module is not the correct method. Generally you unpack the file, move into the directory and build the program using the make && make install commands. I downloaded and unpacked this source code and the is a script inside called tv-setup. You should run this and then try to run ./teamviewer. When I did this it failed and the logs contained errors about not having wine.

If you have a look around the forum there is ready made module for teamviewer. In any case if your venture was solely to learn how to make modules then the file you chose is not a good example.

[jmurrinux]

Thanks brokenman for your reply.

Yes, I would like to have Teamviewer9 on Porteus. The have some files for other linux distros. I'm not sure if I can just select one of those, extract to a folder then make them porteus module for use on porteus. Here is their download page: Teamviewer9 made for different distros. I selected the unsupported option package because, I don't know if I can just pick either the debian or ubuntu files

It seems there is more side work with the make && make install commands. Which I'm not familiar with. I need to learn that process hands on it.
See you later

[brokenman]

Yes it is enough to convert this file to a porteus module: deb2xzm teamviewer.deb

You will still need wine installed. I suggest you search the forum for a ready made teamviewer with all deps.

[Slaxmax]

@jmurrinux
I make teamviewer9 (for porteus x86_64 you need too http://ponce.cc/porteus/x86_64/current/ ... 64-1sl.xzm)
http://forum.porteus.org/viewtopic.php?f=51&t=3234

@brokenman
Teamviewer included wine now.

[jmurrinux]

@Slaxmax @brokenman @ forum
*
You guys rock! Thanks a lot.
I will download it and play with it, J

[jmurrinux]

@Slaxmax

Added the two modules to the Porteus/modules folder, activated them, rebooted the computer.
Searched and found the application icon on the KDE launcher
Isn't opening, it tries to open, but nothing happen.

See you later

[Slaxmax]

For me works fine in kde i486.
Perhaps there is some problem with libraries 32bit
So try as post brokenman.

sorry

[jmurrinux]

Hello forum,

Thanks @Slaxmax
@Brokenman: I tried the module you pointed out ▲ and it gives me this message
How can I fix that in Porteus?

[jmurrinux]

hey forum and community,

I got TeamViewer 9 working on my pc after several tests, this is what I found out after the tests, I think is important to share the experience and someone else can relate to this:

• ☯ Keep TeamViewer module on a separate folder like: Porteus/Optional
  ☯ Load TeamViewer on Root account. Is the account that let me run it after Activation*
  ☯ Keep other modules that could create a conflict with TeamViewer for another session and just activate TeamViewer module when needed
  ☯ These are the modules that created a conflict for TeamViewer to run on my PC: [wine-1.7.9-x86_64-1alien.xzm] [compat32-libraries-3.0-x86_64-1sl.xzm] Because the TeamViewer version I got was built with all dependencies and wine, by Contributor PaulBy

* Maybe this is off topic, but what would be the vulnerability of Porteus by running TeamViewer 9 with root account for a remote control session?
I think there would be some or none: If I'm accessing a remote computer with TeamViewer 9 from Porteus, then I have control over that pc (no changes to mine), unless I grant the access to a remote computer to control mine. 8)

Comments, suggestions, ideas, please let me know,

jmurrinux

[brokenman]

Running Teamviewer as root is like giving someone the key to your house and you going out for the day. Be sure you require a password (key) or some kind of permission to connect. Your decision.