Donald Henson
I'm trying to use YaST2 (SuSE 8.2 Pro) to update kde....
Actually, updating the system was a secondary goal. I'm just trying to figure out how to properly install either updates or new software without going to the command line.
Don, for single packages (after downloading and doing rpm -v --checksig <name of pm>.rpm I use kpackge to check dependencies and then intall, but for upgrading things like glibc or KDE or xf86, where the stability of my machine is at question, i do it from the command line using: # -Uvh *.rpm and I usually add 2>&1 | tee /home/gar/text.txt so my command reads" # -Uvh *.rpm 2>&1 | tee /home/gar/text.txt this command uses standard out to catch any messages generated during the upgrade. What do you have against the command line? -- In the Beginning was the Command Line ---Neal Stephenson __________________________________________________________________ McAfee VirusScan Online from the Netscape Network. Comprehensive protection for your entire computer. Get your free trial today! http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397 Get AOL Instant Messenger 5.1 free of charge. Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promo=380455
On Thu, 2003-10-23 at 16:23, GarUlbricht7@netscape.net wrote:
Donald Henson
wrote on 10/23/2003: (text snipped) I'm trying to use YaST2 (SuSE 8.2 Pro) to update kde....
Actually, updating the system was a secondary goal. I'm just trying to figure out how to properly install either updates or new software without going to the command line.
Don,
for single packages (after downloading and doing rpm -v --checksig <name of pm>.rpm
I use kpackge to check dependencies and then intall, but for upgrading things like glibc or KDE or xf86, where the stability of my machine is at question, i do it from the command line using:
# -Uvh *.rpm
and I usually add
2>&1 | tee /home/gar/text.txt
so my command reads"
# -Uvh *.rpm 2>&1 | tee /home/gar/text.txt
this command uses standard out to catch any messages generated during the upgrade.
What do you have against the command line?
The following is pretty long but you asked. :-) A command line is extremely prone to errors. A simple typing mistake, hitting the 3 key instead of the 2 key for example, can have devastating consequences. If you started out helping Linus build the original kernal, the command line is like an old friend and you know intuitively what to do and what not to do. But, if you are transitioning from the Windows environment, as I am, then you have very little familiarity with commands and what they do. Oh, by the way, one of the format cops on one of the lists told me to put in a paragraph break once in awhile so let me do that here. (Sorry. That's a snide remark but I couldn't help myself.) Except for very simple commands, like ls, Linux commands are a mystery to me. In the Windows environment, it's been months, possibly years, since I felt the need to use the command line. In Linux, that's one of the first suggestions I got. Since I'm not that familiar with the commands, I'm reduced to copying what I've been told to do. Notice that now there are two places for typing errors to occur plus you never know the experience level of the person giving you the solution. For example, look at what you sent me. Count how many places there are for typos to occur, not to mention that you have "and I usually add" in there as well which leaves the decision to me, a newbie that knows nothing. Contrast the above with Windows. Updates, even for office productivity software and some third-party software, are handled almost automatically. Typically, I get a dialog box that says an update is read to install. Clicking the OK button is it. It's hard to make a mistake in that kind of environment. I'm not expecting nor demanding that Linux be that automatic but when I download and install some software in accordance with the instructions, and it doesn't work in accordance with the manual, and the first advice I'm given is to go to the command line and start modifying the configuation of the X server, I get a little nervous. In the case of Red Carpet, I decided that the suggested changes were way beyond my capabilities so I decided to uninstall it. That's about it. If you want a really long response, ask me what I have against the help system. Don Henson
Donald Henson wrote:
On Thu, 2003-10-23 at 16:23, GarUlbricht7@netscape.net wrote:
/Donald Henson
wrote on 10/23/2003: (text snipped) I'm trying to use YaST2 (SuSE 8.2 Pro) to update kde....
Actually, updating the system was a secondary goal. I'm just trying to figure out how to properly install either updates or new software without going to the command line.
Don,
for single packages (after downloading and doing rpm -v --checksig <name of pm>.rpm
I use kpackge to check dependencies and then intall, but for upgrading things like glibc or KDE or xf86, where the stability of my machine is at question, i do it from the command line using:
# -Uvh *.rpm
and I usually add
2>&1 | tee /home/gar/text.txt
so my command reads"
# -Uvh *.rpm 2>&1 | tee /home/gar/text.txt
this command uses standard out to catch any messages generated during the upgrade.
What do you have against the command line?/
The following is pretty long but you asked. :-)
A command line is extremely prone to errors. A simple typing mistake, hitting the 3 key instead of the 2 key for example, can have devastating consequences. If you started out helping Linus build the original kernal, the command line is like an old friend and you know intuitively what to do and what not to do. But, if you are transitioning from the Windows environment, as I am, then you have very little familiarity with commands and what they do. Oh, by the way, one of the format cops on one of the lists told me to put in a paragraph break once in awhile so let me do that here. (Sorry. That's a snide remark but I couldn't help myself.)
Except for very simple commands, like ls, Linux commands are a mystery to me. In the Windows environment, it's been months, possibly years, since I felt the need to use the command line. In Linux, that's one of the first suggestions I got. Since I'm not that familiar with the commands, I'm reduced to copying what I've been told to do. Notice that now there are two places for typing errors to occur plus you never know the experience level of the person giving you the solution. For example, look at what you sent me. Count how many places there are for typos to occur, not to mention that you have "and I usually add" in there as well which leaves the decision to me, a newbie that knows nothing.
Contrast the above with Windows. Updates, even for office productivity software and some third-party software, are handled almost automatically. Typically, I get a dialog box that says an update is read to install. Clicking the OK button is it. It's hard to make a mistake in that kind of environment.
I'm not expecting nor demanding that Linux be that automatic but when I download and install some software in accordance with the instructions, and it doesn't work in accordance with the manual, and the first advice I'm given is to go to the command line and start modifying the configuation of the X server, I get a little nervous. In the case of Red Carpet, I decided that the suggested changes were way beyond my capabilities so I decided to uninstall it.
That's about it. If you want a really long response, ask me what I have against the help system.
Don Henson
What do you have against "man"? It helps in the learning curve! and "Since I'm not that familiar" you should read the man pages on the commands you want to use. And as a regular user it's hard to break the system so just don't make any typos as root and you'll be fine' -- Micxz
participants (3)
-
Donald Henson
-
GarUlbricht7@netscape.net
-
Micxz