>Perhaps the missing DrakConf is not installed in my pedestrian accounts taskbar by default but >available on Roots."
>Easy enough to fix. Right-click your KDE application launcher toolbar and select Add Application to >Panel > System > Configuration > Configure Your Computer.
In fact that is exactly what I did. I was only pointing out that it was odd that it was THERE when the LiveCD was running and I was logged in as "guest" but NOT there when it was installed on my hard drive and I was logged in as the first account I had defined. Not unavailable or anything.
To be simple and usable, that just seemed to me to be an oversight. A new user would need to know the name of the utility, and how to add it.
>"/etc/sudoers is not pre-configured by the install to include my account"
>PCLOS uses su instead of sudo. Ubuntu uses sudo, as does Mint. To each his own.
SUDO was there, as it is on so many systems. It was not hard to configure it. But the main win of SUDO in this case is that it can be set up to give someone admin level access when they enter *their* password, not the root password. May seem like a minor difference, but as I noted, I like to keep root access to a minimum, and that includes using the root password for stuff. SUDO can also restrict it so that not *all* of the root commands are needed by the end user, just the ones needed to do things like configure the network or the screen or the like.
>"PCLOS ships Beryl and Compiz installed, and either can be enabled from the KDE Control Center."
>Uh, no, either can be enabled from the PCLinuxOS Control Center, otherwise known as "Configure Your >Computer", or as drakconf.
And that is why I wish all the DrakConf stuff would be rolled into KDE control center or the other way around! Two admin apps, some function duplicated, but not all. Again, new user needs to hunt around to find all this stuff.
I am not dissing PCLinuxOS speciically here either: This is true of every KDE install I have ever seen. On OpenSUSE with KDE, some stuff is in Yast, and some is in KDECC. Fedora has all the "system-config-*" commands, and of course KDECC.
You know: it is not even KDE specific, because there is also gnome-control-center and yast on OpenSUSE, and so on. Must drive new users mad trying to figure out where ewach distro hides this stuff.
Kudos to Kubuntu on this point: Last time I loaded that one up, things like the network card and wireless stuff had KDECC plugins.
linux
Posted by
ratsarts
at
2008-08-15 21:27
"Must drive new users mad trying to figure out where each distro hides this stuff."
Not at all. That is only one bit of frustration
a new user hsa to deal with. The new user is driven
back only by the "in flux" alwaways in state of change-
nature of linux- no standards- lots of work required:
on user part. Linux will never be suitable for the
desktop. Suitable for zellots only.
>Easy enough to fix. Right-click your KDE application launcher toolbar and select Add Application to >Panel > System > Configuration > Configure Your Computer.
In fact that is exactly what I did. I was only pointing out that it was odd that it was THERE when the LiveCD was running and I was logged in as "guest" but NOT there when it was installed on my hard drive and I was logged in as the first account I had defined. Not unavailable or anything.
To be simple and usable, that just seemed to me to be an oversight. A new user would need to know the name of the utility, and how to add it.
>"/etc/sudoers is not pre-configured by the install to include my account"
>PCLOS uses su instead of sudo. Ubuntu uses sudo, as does Mint. To each his own.
SUDO was there, as it is on so many systems. It was not hard to configure it. But the main win of SUDO in this case is that it can be set up to give someone admin level access when they enter *their* password, not the root password. May seem like a minor difference, but as I noted, I like to keep root access to a minimum, and that includes using the root password for stuff. SUDO can also restrict it so that not *all* of the root commands are needed by the end user, just the ones needed to do things like configure the network or the screen or the like.
>"PCLOS ships Beryl and Compiz installed, and either can be enabled from the KDE Control Center."
>Uh, no, either can be enabled from the PCLinuxOS Control Center, otherwise known as "Configure Your >Computer", or as drakconf.
And that is why I wish all the DrakConf stuff would be rolled into KDE control center or the other way around! Two admin apps, some function duplicated, but not all. Again, new user needs to hunt around to find all this stuff.
I am not dissing PCLinuxOS speciically here either: This is true of every KDE install I have ever seen. On OpenSUSE with KDE, some stuff is in Yast, and some is in KDECC. Fedora has all the "system-config-*" commands, and of course KDECC.
You know: it is not even KDE specific, because there is also gnome-control-center and yast on OpenSUSE, and so on. Must drive new users mad trying to figure out where ewach distro hides this stuff.
Kudos to Kubuntu on this point: Last time I loaded that one up, things like the network card and wireless stuff had KDECC plugins.
Not at all. That is only one bit of frustration
a new user hsa to deal with. The new user is driven
back only by the "in flux" alwaways in state of change-
nature of linux- no standards- lots of work required:
on user part. Linux will never be suitable for the
desktop. Suitable for zellots only.