I installed Cygwin on Windows 7 and it installed properly.
I selected various packages; including curl and wget.
Yet, my anti-virus (AVG 2011) detected it as malware, with 4 red bars and put it into the Virus Vault!
I then sent the suspected file to Kaspersky's filescanner online but it came back as clean from their online scan
I then proceeded to uninstall Cygwin and restart Windows; now it's left me a bit wary of using it on Windows 7 again for fear of a virus.
Is wget always detected as a virus, and should I always be this cautious with cygwin?
Is there much difference between the Windows versions of wget and the Linux/unix ones?
Some sources I read suggested I download the older wget versions to reduce the risk of virus; the Wget version in question that was detected as a virus was the latest one.
What's the best way to deal with this issue?
If you downloaded wget from an official Cygwin repository, there's nearly no chance of a virus.
I think AVG is a little bit overzealous, and since wget is used to download data from the internet, it is recognized as a malware.
Nothing to be afraid about, you can ignore the problem I think.
You should maybe just contact the AVG team to make them aware of the situation.
Related
I have a RHEL system which by default was running Python2.7 and Python3.4
I needed Python3.6 for a project I wanted to work on and so I downloaded it and built it from source. I ran make and make install which hindsight may have been the wrong decision.
Now I do not seem to have any internet connectivity. Does anyone know what I may have over written to cause this or at least where specifically I can look to track this issue down?
Note: I can Putty into the Linux machine but it doesn't seem to have any other connectivity, specifically HTTPS
It's a bit weird that this would break network connectivity. One possible explanation is that the system has networking scripts or a network manager that relies on Python, and it got broken after make install replaced your default Python installation. It may be possible to fix this by reinstalling your RHEL Python packages (sorry, cannot offer more detailed help there, as I don't have access to a RHEL box).
I guess the lesson is "be careful about running make install as superuser". To easily install and manage different Python versions (separate from the system Python), the Anaconda Python distribution would be a good solution.
I suggest to undo that 3.6 installation and use the Software Collections version of python 3.6. See here for python 3.6 installation. Software Collections install "along side" the original versions so as to not affect the OS - and they are included in the subscription.
So after a lot of time slamming my head against the wall I got it worked out. My best guess is that the system (RHEL 7) relied on something from its default Python2.7 installation to handle SSL negotiations. Installing 3.6 alongside must have overwritten some pointer. Had I done this correctly, with altinstall all would have likely been fine.
The most frustrating part of this is that there were no error messages, connections just timed out.
To fix this, I had to uninstall all Python versions and then reinstalled Python2.7 - Once Python2 was back in the system it all seemed to work well.
To the kind people of SO,
I am having trouble finding any resources for installing NodeJS (current or earlier version) onto a RHEL4 box. I am starting to doubt if this is even possible as the OS dates back 10 years now. The machine has Python 2.3.4 and GCC 3.4.6, if that's of any help.
I am hoping someone here could maybe point me in the right direction, I feel I may be grasping for straws at this point.
There is only a handful of possibility, since from comment, you said upgrading the box is not a option. (I d like you to know there is security implications too, you should have a up-to-date OS):
Install the official way, which need yum and sudo rights.
Compile from source, which in theory doesn't need sudo rights nor yum.
Note that, even if compiling from source should be easy:
wget https://nodejs.org/dist/latest-v4.x/node-v4.4.7-linux-x86.tar.gz
tar -xzf node-v4.4.7-linux-x86.tar.gz
cd ./node-v4.4.7-linux-x86
./configure #Options
make
make install
You will almost always run into issues because of not installed or outdated dependencies. At this step, you may want to track down a previously supported version of node.js for RHEL4 (0.10.x?), or try to make a case about upgrading the box.
I must admit i'm not much of a coder or computer scientist, but in the past a friend installed Weechat on my windows computer using Cygwin (via the Cygwin terminal of course). I have a new computer now thats running windows 8.1 and have installed Cygwin with all of the necessary packages, and downloaded the latest stable version of Weechat (1.2). I am stuck from there though and don't really know which direction to move in, the only thing I have done with Cygwin so far is moved the home terminal folder to a more easier accessible location. Would it be possible to get a step by step walkthrough of how the installation progresses after downloading both the Cygwin component and the Weechat files and scripts?
Before we you can start using WeeChat, there are a few other pieces of software you need to install with CygWin. WeeChat relies on them for its functionality, which is why they are called dependencies.
You can find a detailed list of dependencies and further instructions on this link:
Weechat on Windows
Feel free to ask for further help if the above guide wouldn't suffice.
EDIT
WeeChat is currently available via the CygWin native repositories.
Simply search for weechat in the CygWin package manager.
I already have CygWin installed, what now?
No worries, simply rerun the setup-x86-64.exe* you've downloaded. This process won't remove any of your previously installed packages. At the end of the installation process you'll be able to look for and install WeeChat.
* (on 32-bit systems, the installer would be named setup-x86.exe)
I need to get node.js for a program I'm installing in Cygwin, and I'm wondering if the Linux download at nodejs.org is going to work, or does something like this for Cygwin need to be built from source? I tried downloading the linux tarball and incorporating into the installation script for Oppia (the program I'm installing) and it doesn't work, but I don't know enough about this to know what's wrong.
I suppose node.js on cygwin is not really supported. I worked with node.js under cygwin, installed with Windows installer. There are some problems, especially when there are dependencies on paths (/cygdrive/c/...). I haven't tried to build from source, but asked the guys on the node.js google group a similar question, but they just said: not supported.
So probably it's better to write those unbelievable ugly .bat/.cmd scripts and use the DOS shell commands when working with Windows (which I hate so much). I tried to use PowerShell, but it was no improvement, it's odd compared to bash.
Been trying to upgrade my subversion installation, but due to (what I believe) are limited rights (I'm using hosted Linux account), I'm not able to properly "./configure" and compile the source code (see posts Post1 and Post2 if very interested)
So, I'm thinking if I could just download pre-compiled binaries, the just might solve my problems. If you have better ideas - I'd love to hear that too!
NB: I'm not able to call aptitude or apt-get install subversion as suggested by subversion.tigris.com
I'm also interested in knowing how I would go about installing those pre-compiled binaries :)
You can extract the binaries from the deb package for your architecture (which you can download from here) using dpkg-deb -x.
So for example you can do this if you're on i386:
wget ftp://ftp.debian.org/debian/pool/main/s/subversion/subversion_1.5.4dfsg1-1_i386.deb
dpkg -x subversion_1.5.4dfsg1-1_i386.deb subversion
Of course you might have to do some tweaking to make it work. Extracting a package is not the same thing as installing it.
Look at the Debian list of SVN packages, I would assume the etch (stable) is the one you need.
Also see this thread on the same topic.