Hi, I am new to Fedora and Linux, and I try to install Anaconda on Fedora 38 by using this tutorial: How To Install Anaconda on Fedora 37/36/35 – TecAdmin but when I come to Step 2 " 02. Type “yes” to accept the Anaconda license agreement to continue." I dont get this quiestions or option to type “yes”. Is it because I am not logged in as a “root”? I have “Elitebook i5 7th Gen”, from my university.
Are you trying to do fresh installation of F38 workstation using the graphical installation program (Anaconda), or want to install data science packages using Anaconda (same name but different) on your laptop installed with F38 workstation?
From the external article you cited, I assume that you need packages for data science installed on your local machine. It is worth checking the upstream docs on conda.
Fedora already provides a Python conda installer, so you may not need Anaconda Python. Anaconda Python can be installed by a user without root privileges. Fedora conda can be used to install packages in conda environments without root privileges.
Did you verify the download using the SHA256 checksum?
If you plan to work with command-line tools in linux you will find that spending some time to learn command-line basics will pay dividends later.
3 Likes
Thank you Hank, I try to get the packages for data science installed on my local machine. I tried the link, and tried to use the RedHat code “yum install libXcomposite libXcursor libXi libXtst libXrandr alsa-lib mesa-libEGL libXdamage mesa-libGL libXScrnSaver” but it was to challenging to find out how to “# Replace /PATH/FILENAME with your installation’s path and filename.”
Thank you George. Can I use the Fedora conda to install the “Anaconda Navigator” without root privileges? I tried to veryfy the SHA256 checksum, but it was to difficult for me to understand. Thank you for the tips for command-line basic, I have to learn that anyway, so I start with that.
I assume you are referring to this example from Anaconda Linux Installation:
shasum -a 256 /PATH/FILENAME
# Replace /PATH/FILENAME with your installation's path and filename.
Note that Fedora uses dnf (yum is the old tool). The “installation’s” path is the directory where you downloaded the Anaconda package, “filename” is the name of the
anaconda .rpm package.
All this is will be much clearer after you are comfortable with command-line usage. Many linux users do most of their work with the command-line because it saves time over menus and mouse clicking, and when something isn’t working right the command line may be needed to sort out problems. The command line also makes it much easier to discuss issues in forums or using email.
Ok, I was surprised to see the yum, because I had seen dnf other places. I understand the installation path now, and I will try to find the name of the anaconda.rpm pagage. I have ordered the printed version of the book you recommended, and I am reading in the web version now. I feel it is very helpful.
1 Like
Workflow to get the data analysis set up can vary by personal preference and previous tools you’re comfortable with. Alternatively, I would go for Jupyter Notebook or Spyder IDE.
No, “Anaconda Navigator” (AN) is a feature of the Anaconda Python Distribution directed at people who don’t want to use conda (or mamba, which is usually faster). AN provides 1-stop GUI shopping for many data science tools. In Fedora, many of the tools are available as distro packages and can be installed using dnf (requires root privileges), while others can be installed without root privileges in a conda environment. Some may require manual installation from a third party site. Most people only learn and use a couple tools at a time, but will need to move to newly emerging tools over time. AN has the advantage that the same versions of the tools are widely available, but often lags behind the most recent version of tools.
You might want to view the AN Troubleshooting page. Note that troubleshooting often requires using the command line. While I can see the attraction of GUI tools for people whose previous experience has been with pure GUI environments (tablets and smart phones), I find they hinder communications with distant users and force you to command-line when something breaks.
1 Like