Linux: Installing with YUM
-
Of course, there is always that situation where you know that you need some functionality but have no idea how to get it. This is extremely rare, but it does happen. In the real world, you just don't have very much call for installing something that you don't know what it is, even from the official repos.
So in an extreme case you need to download a file over HTTP and actually don't know that cURL and wget are the main tools for that. You could do any number of searches inside of Linux to teach yourself what tool is appropriate. But more likely you would go to Google to not find out what there "is" but to find out "how most people do it and how to use it."
If you did that, you'd find cURL was already there (and you just didn't know how to use the system as it was) and that wget is available for a less powerful, but easier experience for downloads. You'd find quickly enough data to know how to use the tools for your needs, not just acquire them.
Once you did that once, you'd know the two tools and never really need that again. Because of the repos you know that they will be there, available, all the time even if the master site moves, they will be signed, etc.
-
Now, what you will likely look up often, is exactly file names. For example, it is common to find that Python 2 packages are called python and Python 3 are called python3.
This is where
yum list | grep pythonis awesome because it will list everything called python regardless and let you see what the options are. -
@scottalanmiller said:
Now, what you will likely look up often, is exactly file names. For example, it is common to find that Python 2 packages are called python and Python 3 are called python3.
This is where
yum list | grep pythonis awesome because it will list everything called python regardless and let you see what the options are.This!
-
@scottalanmiller said:
Now, what you will likely look up often, is exactly file names. For example, it is common to find that Python 2 packages are called python and Python 3 are called python3.
This is where
yum list | grep pythonis awesome because it will list everything called python regardless and let you see what the options are.Am I the only one that uses
yum search python | moreI mean, I know 'yum list | grep python' works, I find more often it turns into
yum list | grep python | morenothing really wrong with either, just the way I tend to work.
-
I can scroll with my terminal, so using more isn't really necessary.
-
As a side note: The -y modifier assumes a yes for any interactive questions. I looked that up a little while ago and it was actually kind of hard to find. I've noticed that sometimes it doesn't actually ignore the interactive questions though. I assume this has to do with the package and what is required.
-
@wirestyle22 said:
The -y modifier assumes a yes for any interactive questions too. I looked that up a little while ago and it was actually kind of hard to find
It's right in the man page. Man is your friend, learn to love it! (uh, that might have come out wrong.)
-
@travisdh1 said:
@wirestyle22 said:
The -y modifier assumes a yes for any interactive questions too. I looked that up a little while ago and it was actually kind of hard to find
It's right in the man page. Man is your friend, learn to love it! (uh, that might have come out wrong.)
The reason I had trouble is because I was searching Yum commands not Yum modifiers
Windows ruined any potential I had. -
@travisdh1 said:
@wirestyle22 said:
The -y modifier assumes a yes for any interactive questions too. I looked that up a little while ago and it was actually kind of hard to find
It's right in the man page. Man is your friend, learn to love it! (uh, that might have come out wrong.)
It's illegal to use the man pages in Mississippi now.
-
@travisdh1 said:
@scottalanmiller said:
Now, what you will likely look up often, is exactly file names. For example, it is common to find that Python 2 packages are called python and Python 3 are called python3.
This is where
yum list | grep pythonis awesome because it will list everything called python regardless and let you see what the options are.Am I the only one that uses
yum search python | moreI mean, I know 'yum list | grep python' works, I find more often it turns into
yum list | grep python | morenothing really wrong with either, just the way I tend to work.
I do it also. After about he third time you search something while in a tmux session and you can't scroll up you learn to do that lol.
Except I've always used less, idk why I defaulted to that over more.
-
@johnhooks The difference is 6 compared to a half dozen (at least in this case.)
I used to know a reason why you would use less or more in certain cases, but it's been so long that I no longer remember what caused a difference.
-
@johnhooks said:
@travisdh1 said:
@scottalanmiller said:
Now, what you will likely look up often, is exactly file names. For example, it is common to find that Python 2 packages are called python and Python 3 are called python3.
This is where
yum list | grep pythonis awesome because it will list everything called python regardless and let you see what the options are.Am I the only one that uses
yum search python | moreI mean, I know 'yum list | grep python' works, I find more often it turns into
yum list | grep python | morenothing really wrong with either, just the way I tend to work.
I do it also. After about he third time you search something while in a tmux session and you can't scroll up you learn to do that lol.
Except I've always used less, idk why I defaulted to that over more.
That's why I don't use tmux often.
-
@travisdh1 said:
@johnhooks The difference is 6 compared to a half dozen (at least in this case.)
I used to know a reason why you would use less or more in certain cases, but it's been so long that I no longer remember what caused a difference.
I know of no case where you use more. I always used it because I learned it first, but less is the only one you would actually want to use.
