Hot answers tagged upgrade
Recommended updates are, well, recommended. You can read the stable release updates policy. They fall into three categories: Critical bugs such as data loss, impossibility to install, etc. Updates to data files which become necessary over time, such as the timezone database, antivirus signatures, hardware support lists, etc. Some of these may be code ...
I solve the problem by using Amrish instructions at Ask Ubuntu Stack Exchange, i.e. by using the following code: sudo rm /etc/resolv.conf sudo ln -s ../run/resolvconf/resolv.conf /etc/resolv.conf sudo resolvconf -u
The problem is caused because you moved eclipse to a location outside the directory where you installed it. Instead of moving eclipse to a directory in your path, create soft link to the executable. Assuming Eclipse is extracted within your home directory: sudo ln -s /home/masi/eclipse/eclipse /usr/local/bin/eclipse You can then run eclipse without ...
I forgot to run update-initramfs -u after fixing the swap in .../resume and and /etc/fstab
Short of upgrading your Mint installation, the easiest way to upgrade to Java 8 is as you found out to install Oracle's JDK. The correct way to do this though is to use java-package. Start by downloading the appropriate JDK from Oracle, then sudo apt-get install java-package make-jpkg jdk-8u92-linux-x64.tar.gz sudo dpkg -i oracle-java8-jdk_8u92_amd64.deb ...
It may depend on which distribution you are using, but in Fedora (and therefore in most or all Fedora-derived distributions including Red Hat Enterprise Linux and CentOS) the selinux-policy-targeted package includes a postinstall script with restorecon and fixfiles commands, so it should not be necessary.
Well it is always best to do a fresh install on empty partitions or otherwise you'll keep lots of unneeded files all over the place. There is no magic solution to know where you saved your files. They may be in /home but you could have saved then all over the place. It may be a good idea to also backup the list of installed packages for future ...
First of all moving eclipse binary to /usr/local/bin/ was a bad move. Many executables need to to link to dynamic link libraries - usually called shared objects or .so - to work properly. When you moved eclipse to /usr/local/bin you might have forgotten to move its corresponding shared objects to the same location and that is why you got : The Eclipse ...
Originally, the tool worked when we were at the GA release of RHEL 7 (7.0). At this point, it does not. It is absolutely not recommended. You are better off doing a clean installation at all times. This involves taking a backup of what's necessary (such as static web content, etc), installing the system, and restoring from backup. Their tools are broken ...
Only top voted, non community-wiki answers of a minimum length are eligible