Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sun 05 Jul 2020, 14:24
All times are UTC - 4
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Network
AnyDesk 'portable' packages - 32- or 64-bit....
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 2 [22 Posts]   Goto page: 1, 2 Next
Author Message
Mike Walsh


Joined: 28 Jun 2014
Posts: 6376
Location: King's Lynn, UK.

PostPosted: Wed 11 Mar 2020, 10:53    Post subject:  AnyDesk 'portable' packages - 32- or 64-bit....
Subject description: Available as AppImage or self-extracting script
 

Afternoon, all.

With AnyDesk now looking to be the favoured TeamViewer replacement for Puppy - due to the latter's insistence on Qt5, and all the older packages having been disabled by TeamViewer themselves - here are some 'portable', run-anywhere Puppy packages for the current release, v5.5.4.

I've packed these as either AppImages, or a self-extracting script, thanks to Fred's extremely useful portable-packaging scripts. In both cases, you just click on them, and they run.

64-bitzers have been tested in Phil B's Bionicpup64 8.0, Xenialpup64 7.5 & Tahrpup64 6.0.5/6. The 32-bitzers have only been tested in radky's sublime DPup 'Stretch', this being the sole 32-bit Puppy I use nowadays.

Downloads here:-

32-bit:-

AppImage

Self-extracting script

64-bit:-

AppImage

Self-extracting script

I will endeavour to keep these up-to-date for y'all. Help yourselves to the one you want. Enjoy.


Mike. Wink

_________________
MY 'PUPPY' PACKAGES

Back to top
View user's profile Send private message 
fjd


Joined: 03 Mar 2020
Posts: 57
Location: Sydney, Australia

PostPosted: Thu 19 Mar 2020, 16:32    Post subject:  

Mike,
I downloaded 32-bit to try. I'm uncomfortable with keeping Anydesk off the computer to lose, misplace, etc. Can it be installed?

_________________
2011 ASUS Eee PC, 1011PX, 32-bit, Atom N455, 1667MHz, 2Gb RAM, 240Gb SSD - BionicPup 32-bit frugal + USB stick install
Back to top
View user's profile Send private message 
mikeslr


Joined: 16 Jun 2008
Posts: 3893
Location: 500 seconds from Sol

PostPosted: Thu 19 Mar 2020, 16:58    Post subject:  

fjd wrote:
Mike,
I downloaded 32-bit to try. I'm uncomfortable with keeping Anydesk off the computer to lose, misplace, etc. Can it be installed?


Not sure what you mean. Accidentally delete from /mnt/home?

I didn't try Mike's self-extracting script. But AppImages can be located anyplace including /opt and, hence, withing a SaveFile/Folder.
Back to top
View user's profile Send private message 
Mike Walsh


Joined: 28 Jun 2014
Posts: 6376
Location: King's Lynn, UK.

PostPosted: Thu 19 Mar 2020, 19:58    Post subject:  

@ fjd:-

I would think the easiest way to do this would be to stick the AppImage in /opt, as t'other Mike says. Or, if you like, you could do what I've done.

In /root, I've created a 'hidden' directory - ~/.AnyDesk. (Note the use of the dot (.); this denotes a hidden directory.

Inside that 'hidden' directory, I've placed the 'AnyDesk' portable. Use the 'eye' icon in ROX's 'menu-bar' to show hidden directories/files; makes working with them easier. From there, I've simply dragged it to the desktop (ROX's 'pinboard').

This way, it's on the desktop to use, yet the real 'portable' is hidden away out of sight in /root. Doesn't hurt, cos the whole thing is tiny, really.

Up to you where you put it, TBH. You could leave it out of sight, and build a MenuEntry to start it from Menu->Network....and that's quite easy to do as well.


Mike. Wink

_________________
MY 'PUPPY' PACKAGES

Back to top
View user's profile Send private message 
davids45


Joined: 26 Nov 2006
Posts: 1325
Location: Chatswood, NSW

PostPosted: Thu 19 Mar 2020, 20:53    Post subject: ScPup - missing libs list  

G'day Mike,

No longer being a worker with a desk (or 'team'), I was curious to know what all the fuss about 'Teamviewer' (and so 'AnyDesk') is.

Starting today in an SCPup32, I downloaded your two 32-bit files. When I found which one looked like it could run, I copied it to my data partition's 32bit-Portables directory and after making the file executable, ran it in a terminal to see why it was not running.
The usual issue between Slackware and Ubuntu Pups Rolling Eyes was confirmed with some missing libs in this ScPup (version 20.01, k-4.14.160-lxpup-32-pae).

I added the libs indicated in the terminal messages from my LibraryFiles archive or by temporarily mounting a bionicpup sfs and copying the needed lib file from bionic to SCPup's /usr/lib/.

Here's the terminal output for this:
Quote:
# cd /mnt/sda5/Puppy_Archive/32Portables/AnyDesk554-Portable/
# ls
AnyDesk-554-portable32
# ./AnyDesk-554-portable32
Verifying archive integrity... All good.
Uncompressing AnyDesk-554-portable32 100%
anydesk: error while loading shared libraries: libpangox-1.0.so.0: cannot open shared object file: No such file or directory
Checking anydesk for missing libraries...
libpangox-1.0.so.0 => not found
libsystemd.so.0 => not found
libpangox-1.0.so.0 => not found
Adding these depencencies will probably fix if the program doesn't run.
# ./AnyDesk-554-portable32
Verifying archive integrity... All good.
Uncompressing AnyDesk-554-portable32 100%
anydesk: error while loading shared libraries: libsystemd.so.0: cannot open shared object file: No such file or directory
Checking anydesk for missing libraries...
libsystemd.so.0 => not found
Adding these depencencies will probably fix if the program doesn't run.
# ./AnyDesk-554-portable32
Verifying archive integrity... All good.
Uncompressing AnyDesk-554-portable32 100%
anydesk: error while loading shared libraries: liblz4.so.1: cannot open shared object file: No such file or directory
Checking anydesk for missing libraries...
liblz4.so.1 => not found
Adding these depencencies will probably fix if the program doesn't run.
# ./AnyDesk-554-portable32
Verifying archive integrity... All good.
Uncompressing AnyDesk-554-portable32 100%

(program now runs!!!)


So ScPup users could need:

libpangox-1.0.so.0
libsystemd.so.0
liblz4.so.1


to run the AnyDesk Portable.

Looks basically like a file-transfer application so not much use to an isolating (self or otherwise) user?

Eye-candy mode:
Is there an included 'AnyDesk' icon to set for the 'AnyDesk' script on the pinboard?

Thanks again for your Portables - Audacity is very nice.

David S.
AnyDeskPortable-ScPup.jpg
 Description   With extra libs needed for ScPup
 Filesize   86.15 KB
 Viewed   643 Time(s)

AnyDeskPortable-ScPup.jpg

Back to top
View user's profile Send private message 
Mike Walsh


Joined: 28 Jun 2014
Posts: 6376
Location: King's Lynn, UK.

PostPosted: Fri 20 Mar 2020, 08:09    Post subject:  

@ David:-

There's a lot more to AnyDesk than meets the eye. Like TeamViewer, the initial interface gives absolutely no hint of what the app offers, because many windows don't appear until you actually start using it.....

But, er, nice one for being persistent with the 'lib-chase'; it's always the case with Slackware-based Pups, 'cos Slackware are so conservative with what they supply by default.

From what I can glean, you can connect to multiple other machines/desktops with AnyDesk; TeamViewer is usually one at a time, unless and until you start paying for the 'Enterprise' a/c.....which then 'unlocks' more features. However many desktops you're connected to, you get a row of 'thumbnails' along the bottom in that grey band, showing those desktops.

Icon attached.


Mike. Wink
anydesk.png
 Description   AnyDesk icon
 Filesize   4.95 KB
 Viewed   615 Time(s)

anydesk.png


_________________
MY 'PUPPY' PACKAGES

Back to top
View user's profile Send private message 
ozsouth

Joined: 01 Jan 2010
Posts: 855
Location: S.E Australia

PostPosted: Mon 23 Mar 2020, 02:23    Post subject:  

Have just started using this - much better than vnc. Using the free download .deb from here: https://anydesk.com/ ,
ScPup64 & LxPupSc64 missing 3 libs, which I've packaged in attached .pet
anydesk-s64-libs.pet
Description 
pet

 Download 
Filename  anydesk-s64-libs.pet 
Filesize  108.01 KB 
Downloaded  108 Time(s) 
Back to top
View user's profile Send private message 
backi

Joined: 27 Feb 2011
Posts: 2004
Location: GERMANY

PostPosted: Fri 27 Mar 2020, 06:55    Post subject:  

Wow ......cool .....
Thanks a lot Mike !
Back to top
View user's profile Send private message 
Max Headroom


Joined: 28 Jun 2006
Posts: 423
Location: GodZone Kiwi

PostPosted: Fri 27 Mar 2020, 19:05    Post subject:
Subject description: Thanx Mike 4 Suggesting this
 

I Will Try it, the Reason I was asking about VNC was because I Wtd a X Platform Solution ie. Linux, MacOS & M$ Virus Bait Windows.

According 2 sum sauces MacOS & AnyDesk aRen't compatible, Others say OK, I'm Confused!

Thanx 4 Appimages!...

WinkK

_________________
PC is Not Political Correctness Razz , it's a Personal Computer! Boycott the Evil M$ & Google!
Back to top
View user's profile Send private message Yahoo Messenger 
Mike Walsh


Joined: 28 Jun 2014
Posts: 6376
Location: King's Lynn, UK.

PostPosted: Fri 27 Mar 2020, 23:34    Post subject:
Subject description: Thanx Mike 4 Suggesting this
 

Max Headroom wrote:
I Will Try it, the Reason I was asking about VNC was because I Wtd a X Platform Solution ie. Linux, MacOS & M$ Virus Bait Windows.

According 2 sum sauces MacOS & AnyDesk aRen't compatible, Others say OK, I'm Confused!

Thanx 4 Appimages!...

WinkK


Ermm....Windoze, MacOs, Android, iOS, Linux, FreeBSD, Raspberry Pi, ChromeOS......is that enough cross-compatibility for you? Laughing

From the 'horse's mouth'...


Mike. Wink

_________________
MY 'PUPPY' PACKAGES

Back to top
View user's profile Send private message 
soniabu


Joined: 01 Feb 2018
Posts: 162
Location: Paris

PostPosted: Thu 21 May 2020, 12:59    Post subject:  

Mike, I downloaded in my Bionicpup64 Anydesk Appimage
(the .deb file from the official website is installed without error but does not start)
and I can start, but I have difficulty in reading, for example, the description of the components in the setting; that is, on a white background the letters are a gray color, soft and smooth.

Any suggestions?
Back to top
View user's profile Send private message 
tallboy


Joined: 21 Sep 2010
Posts: 1751
Location: Drøbak, Norway

PostPosted: Sun 31 May 2020, 11:07    Post subject:  

Hi Mike. I cannot make either version work in my tahr64_6.0.6. I placed the portable in /opt, set the permissions to exec, restarted X, and clicked the app. Nothing happens! Do you have a md5sum for both 64-bit versions?

Oh, a thought came from the other brain cell: Is my VPN preventing things from happening? Will play some more...
Edit: Nope
Edit once more: Moved the potable app to /root/my-applications/bin, and tried to run it from a terminal window.
Code:
root# AnyDesk-5.5.4-portable64
anydesk: error while loading shared libraries: libsystemd.so.0: cannot open shared object file: No such file or directory
Checking anydesk for missing libraries...
   libsystemd.so.0 => not found
Adding these depencencies will probably fix if the program doesn't run.

I have no frigging systemd!

_________________
True freedom is a live Puppy on a multisession CD/DVD.
Back to top
View user's profile Send private message 
Mike Walsh


Joined: 28 Jun 2014
Posts: 6376
Location: King's Lynn, UK.

PostPosted: Sun 31 May 2020, 16:12    Post subject:  

@ Olaf:-

Now then; here's a .pet package just for you.

https://drive.google.com/file/d/1gphN9K3RWuByOeZ0juosoKT-6yHbjjJW/view?usp=sharing

This fires up, OOTB, in a pristine install of Tahrpu64 6.0.6. Just d/l, install, then Menu->Network->Anydesk. Bob's yr mother's brother, it runs straight away.

It does have a few systemd-related deps, I'll grant you that; I guess that's a function of whatever distro this was compiled in. If it was mainstream, and fairly new, it'll have systemd. They all do now. But it's possible to have systemd-related items on the system without having the monstrosity itself.

(They're only there so that Anydesk catches sight of them, says "Yep; I can see you...!", and then it'll do its thing....)

It's entirely up to you. Your choice.


Mike. Wink

_________________
MY 'PUPPY' PACKAGES

Back to top
View user's profile Send private message 
tallboy


Joined: 21 Sep 2010
Posts: 1751
Location: Drøbak, Norway

PostPosted: Mon 01 Jun 2020, 16:59    Post subject:  

Thanks, mate. Sent you a pm.
_________________
True freedom is a live Puppy on a multisession CD/DVD.
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 2064
Location: not Bulgaria

PostPosted: Tue 02 Jun 2020, 04:36    Post subject:  

Mike Walsh wrote:
But it's possible to have systemd-related items on the system without having the monstrosity itself.


Mike, you are misinformed. This forum is full of such misinformation, which is a tragic falsehood. Your comment was out-of-topic, hence so is my reply to it, apologies. However, these nonsense claims against systemd are technically misleading less-informed forum members so I can't let that comment pass silently, though of course you are welcome to have your own negative feelings, however misinformed they may be in this case... Wink

https://opensource.com/article/20/4/systemd
Quote:
Final thoughts
Even before getting very deep into systemd, it's obvious that it is both powerful and complex. It is also apparent that systemd is not a single, huge, monolithic, and unknowable binary file. Rather, it is composed of a number of smaller components and subcommands that are designed to perform specific tasks.


Arch Linux is an example of a very flexible OS for users that uses systemd, and one that I am becoming familiar with because I use upstream Arch system as the basis for one of my WeeDogLinux build script creations.

Arch used to use SysVinit. Here is what an ex primary maintainer of the init systems for Arch Linux had to say about adopting systemd in preference to the mess that was SysVinit (and I have personally worked with SysVinit since the early 1990's, but have to say that now that I've finally learned a bit of how to use systemd, it is much easier to use from a sysadmin point of view, and like a breath of fresh air. Runit, as used in Void Linux is nice too as it happens, but certainly not that SysVinit Puppy hangs on to!):

https://www.reddit.com/r/archlinux/comments/4lzxs3/why_did_archlinux_embrace_systemd/
brainz - ex-Arch Linux init systems primary maintainer wrote:

I was the primary maintainer for Arch's init scripts for a while and I can share a couple of thoughts.

Arch's initscripts were incredibly stupid. In their first phase, there was a static set of steps that would be performed on every boot. There was almost no way to adjust the behaviour here. In their second phase, the configured daemons were started in order, which only meant that a init scripts were called one after another.

In the early 2000s, that seemed like a good idea and has worked for a while. But with more complex setups, the shortcomings of that system become apparent.

With hardware becoming more dynamic and asynchronous initialization of drivers in the kernel, it was impossible to say when a certain piece of hardware would be available. For a long time, this was solved by first triggering uevents, then waiting for udev to "settle". This often took a very long time and still gave no guarantee that all required hardware was available. Working around this in shell code would be very complex, slow and error-prone: You'd have to retry all kinds of operations in a loop until they succeed. Solution: An system that can perform actions based on events - this is one of the major features of systemd.

Initscripts had no dependency handling for daemons. In times where only a few services depended on dbus and nothing else, that was easy to handle. Nowadays, we have daemons with far more complex dependencies, which would make configuration in the old initscripts-style way hard for every user. Handling dependencies is a complex topic and you don't want to deal with it in shell code. Systemd has it built-in (and with socket-activation, a much better mechanism to deal with dependencies).

Complex tasks in shell scripts require launching external helper program A LOT. This makes things very slow. Systemd handles most of those tasks with builtin fast C code, or via the right libraries. It won't call many external programs to perform its tasks.

The whole startup process was serialized. Also very slow. Systemd can parallelize it and does so quite well.

No indication of whether a certain daemon was already started. Each init script had to implement some sort of PID file handling or similar. Most init scripts didn't. Systemd has a 100% reliable solution for this based on Linux cgroups.

Race conditions between daemons started via udev rules, dbus activation and manual configuration. It could happen that a daemon was started multiple times (maybe even simultaneously), which lead to unexpected results (this was a real problem with bluez). Systemd provides a single instance where all daemons are handled. Udev or dbus don't start daemons anymore, they tell systemd that they need a specific daemon and systemd takes care of it.

Lack of configurability. It was impossible to change the behaviour of initscripts in a way that would survive system updates. Systemd provides good mechanisms with machine-specific overrides, drop-ins and unit masking.

Burden of maintenance: In addition to the aforementioned design problems, initscripts also had a large number of bugs. Fixing those bugs was always complicated and took time, which we often did not have. Delegating this task to a larger community (in this case, the systemd community) made things much easier for us.

I realize that many of these problems could be solved with some work, and some were already solved by other SysV-based init systems. There was no system that solved all of these problems and did so in a realiable manner, as systemd does.

So, for me personally, when systemd came along, it solved all the problems I ever had with system initialization. What most systemd critics consider "bloat", I consider necessary complexity to solve a complex problem generically. You can say what you want about Poettering, but he actually realized what the problems with system initialization were and provided a working solution.

I could go on for hours, but this should be a good summary.


Whether you believe it or not, most of the above init-related comments also apply to Puppy Linux since it uses SysVinit (though in very simplified form since it isn't a true multi-user system, which is fine for its focus and purpose). No wish to use systemd - fine... but let us hope that those who call themselves the Puppy stewards one day modernise Puppy, somewhat, by throwing out SysVinit and at least replace it with something like runit as a considerably better alternative.

Sorry for the thread interruption - but like I say, it wasn't me who out-of-topic chose to spread false news about systemd. The problem with such bold nonsense inaccurate or wholly untrue statements about something like systemd is that it keeps people ignorant, who themselves, go on to spread that same false information they have trusted as part of their learning more about Linux via forum mentoring help.

Yes, there are some experienced Linux users/developers and so on here who hate systemd, but frankly I cannot understand where half of their prejudice comes from - most of the anti-systemd 'monstrosity, and so on' claims certainly do not at all match my own practical experience of using/configuring these various init systems on a daily basis over many decades.

wiak

_________________
WeeDogLinux forum: https://weedoglinux.rockedge.org/viewforum.php?f=4
Tiny Linux Blog: https://www.tinylinux.info/
Check Firmware: http://murga-linux.com/puppy/viewtopic.php?p=1022797
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 2 [22 Posts]   Goto page: 1, 2 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Network
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0863s ][ Queries: 13 (0.0196s) ][ GZIP on ]