Posted by: Anonymous
[ip: 71.98.14.163]
on December 19, 2008 10:08 PM
Yes, that is what the article refers to. I am not sure whether or not you are saying this makes it correct. Susan was mistaken when she said the sudo has replaced the root account. It caught me off guard to with 11.0, though it was in the release notes. openSUSE's team rightly realized that having two different passwords on a home desktop is really overkill. For a home user, the only benefit of a root account at all is to avoid accidental damage to the system (rm -rf /* for example). That purpose is perfectly well served by requiring a user to provide his own password as the root account. Similar in philosophy to Ubuntu's use of sudo, however you are still given a true root account, and you are perfectly free to choose not to use your own password as the root password during the installation (or afterwards). Susan, like many of us, didn't pay close enough attention to the installer's instructions. But the fact is, the installer made it very clear what was going on.
I have never had Yast's configuration "botch" anything on my systems. I find it to be a tremendous time saver. Sure, I could go through CUPs web interface and type in the always changing ips of my network printers. Or I can let Yast do it for me. I can hand edit smb.conf and set a my samba shares on my own. Or I can let Yast do it for me. I can modprobe my wifi drivers and run iwconfig on my own, or I can let yast do it for me. Since, in my opinion, the computer is here to do things for me, Yast fits my bill perfectly. If I wish to have me work for the computer, I can do that too! It's called choice.
I won't say Yast's perfect (it's not) but what does do it does well. Sure pico won't complain when you change things. For instance, if I try to remove a mount point in fstab, and accidentally fudge my root mount line, Yast will complain. If that bothers me, I can shut down Yast, fire up pico, make my change, mess uo my system, and reinstall (or do some other recovery work). The fact is, pico only works as well as you do. I happen to be a human, and if there's one thing humans do best, it's make mistakes (denying them would place a close second). So for me, having a tried and true tool is a great thing.
Learn about Linux
Download Linux
Get Linux help
Re(2): Hmmmmm...
Posted by: Anonymous [ip: 71.98.14.163] on December 19, 2008 10:08 PMI have never had Yast's configuration "botch" anything on my systems. I find it to be a tremendous time saver. Sure, I could go through CUPs web interface and type in the always changing ips of my network printers. Or I can let Yast do it for me. I can hand edit smb.conf and set a my samba shares on my own. Or I can let Yast do it for me. I can modprobe my wifi drivers and run iwconfig on my own, or I can let yast do it for me. Since, in my opinion, the computer is here to do things for me, Yast fits my bill perfectly. If I wish to have me work for the computer, I can do that too! It's called choice.
I won't say Yast's perfect (it's not) but what does do it does well. Sure pico won't complain when you change things. For instance, if I try to remove a mount point in fstab, and accidentally fudge my root mount line, Yast will complain. If that bothers me, I can shut down Yast, fire up pico, make my change, mess uo my system, and reinstall (or do some other recovery work). The fact is, pico only works as well as you do. I happen to be a human, and if there's one thing humans do best, it's make mistakes (denying them would place a close second). So for me, having a tried and true tool is a great thing.
#