SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I don't really care about the semantics of how amazingly dangerous root is, again, I have seen enough threads hijacked about this sermon, please stop hijacking mine.
It's the way the company expects it run, so it's the way it's going to be run.
I have the same problem with the Akonadi server failing as any user, not just root. I am using Slackware current (23/06/2009) and I get the same error messages whether I login as root or login as a user.
Quote:
I was able to solve the "No resource agents found" problem!
just copy the agent directory from /usr/share/akonadi/ to /usr/local/share/
I found copying the contents of /usr/share/akonadi/agents to /usr/local/share solved the problem for non-root logins only.
I am still working on the root issue....
Cheers, bg4.
PS for what its worth I use KDE in root all the time and I don't have passwords either!!
Root login solved!!
In the file /root/.local/share/akonadi/mysql.conf add the line "user=root" below the "[mysqld]" heading and Bobs your uncle.
Cheers, bg4.
Last edited by bg4; 06-24-2009 at 05:53 PM.
Reason: Added root solution
I was able to solve the "No resource agents found" problem!
just copy the agent directory from /usr/share/akonadi/ to /usr/local/share/
An alternative solution is to edit /usr/bin/startkde and add /usr/share/akonadi to the line that sets the XDG_DATA_DIRS.
Code:
# Make sure that D-Bus is running
if test -z "$XDG_DATA_DIRS"; then
XDG_DATA_DIRS="`kde4-config --prefix`/share:/usr/share:/usr/local/share:/usr/share/akonadi"
export XDG_DATA_DIRS
fi
You do have to run as root when your companies software development tells you that you have to because their stuff is written in such a way that you must.
I wasn't however looking for a debate as to whether running as root is good or bad I was looking for a solution to my issue.
If anyone has that and has actually experienced this problem running on a non root user account as well, it would be far more appreciated to hear the solution than a lecture about running as root.
From what I'm seeing, so far, you received a lot of "shoulds" from a pack of politically correct "mustabators" telling you how to work and breathe. Nor do I see any sort of solution offered. There is no debate, since Linux is supposed to be "free", yet there are those who would determine for YOU how you manage your system. It sure wasn't like that in the "Good Ole Days". I've been using the root account since the early 90's. I've blown up my share of installs, too, by making a mistake. I am not doomed to repeat them. When I'm done with my "root" work, I have a nice user to login to.
I learned something as well. That the M$ mentality is not confined to M$. Those of you that do not see my point, I would suggest that you ask a shrink about "control fallacies". I double-dog dare you to. No one may tell another what they "should" do, in an open intelligent society, unless it is a point of law. It's mentally unhealthy for the do'er. You may however suggest.
Rigging same software to remove all KDE4 pim utilities, when you try to remove it, is also a massive "should". Use Akonadi or we remove everything else. Since Akonadi is not running, and the pim utils still function, Akonadi is NOT a legitimate depend. I resent it being forced on my installation. We're really starting to look too much like M$ folks. Way too much. Ric
From what I'm seeing, so far, you received a lot of "shoulds" from a pack of politically correct "mustabators" telling you how to work and breathe.
I suspect they were just trying to help, just like someone who might say, "if you're going to jump out of this plane, you should take a parachute!" when they see you heading for the door without one.
The running as root issue is no different.
Attacking them for showing concern for someone else's well-being seems a little churlish to me.
Akonadi is not needed, at least for now, but should (?) be in future. It's safe if you remove it. To stop the migration you can try 'kwriteconfig --file kres-migratorrc --group Migration --key Enabled --type bool false'. And yes, it gave me a bad taste too...
Root login solved!!
In the file /root/.local/share/akonadi/mysql.conf add the line "user=root" below the "[mysqld]" heading and Bobs your uncle.
Thank you much for this simple solution. That simple fix finally got akonadi to initialize and shut up.
[soap box]I'm testing Current/13.0 on a non-networked box, which eventually will become an HTPC. I simply do not have time to fiddle with 'su root' all day long and I run the box as root. I too get weary of the "don't run as root" religiosity. I'm a big boy and I accept responsibility for my actions. Bad enough I have to continually avoid all the self-appointed nannies in this world who think they know how I should live my life, and then have to endure that same attitude with free software. I wish people would just let each person live and let live.[/soap box]
I've had root accounts on machines since there was a Linux to install... and yes, I blew off a harddrive one time. But only once. I blew the smackers out of a perfectly good and, at the time, very expensive Multisync monitor using xvidtune. It just went EEEK! and smoke came out of the flyback. But, xvidtune did what I told it to do, so I could only blame myself.
We all have war stories. But, it should be left to MY discretion when to use the root account and when not to. Not only do I not need a nanny I despise a nanny. Actually it's a little bit past despise. Maybe LOATHE?? Good Boundaries are what I talking about. It's my machine. It's mine to administer and mine to break. Don't put a "should" on me, as it's mentally unhealthy for the "should"er. Period. My two cents, Ric
[soap box]I'm testing Current/13.0 on a non-networked box, which eventually will become an HTPC. I simply do not have time to fiddle with 'su root' all day long and I run the box as root. I too get weary of the "don't run as root" religiosity. I'm a big boy and I accept responsibility for my actions. Bad enough I have to continually avoid all the self-appointed nannies in this world who think they know how I should live my life, and then have to endure that same attitude with free software. I wish people would just let each person live and let live.[/soap box]
Man...
And I get sick of people trying to be heroes by trivialising the importance of not running as root. Painting it like it makes you some kind of special and encouraging others to do the same is just irresponsible IMHO.
Yes it's your box and you can do with it whatever you want. If you understand the risks and are prepared to take them then go ahead.
You should never run kde as root.
If you run it as user then you kan open an terminal in kde and 'su -' to become root in that shell/session.
you only have some of roots privileges with su
you can prove this for your self try to su halt
NO you need to be root to set up and configure the system
IF you hose the system on a fresh install no big deal you won't lose much
just reinstall
it should run for root without errors KDE 4.2 is at least a year from being as good as KDE 3.5
slackware for all intents and purposes no longer has a working version of KDE
I've had root accounts on machines since there was a Linux to install... and yes, I blew off a harddrive one time. But only once. I blew the smackers out of a perfectly good and, at the time, very expensive Multisync monitor using xvidtune. It just went EEEK! and smoke came out of the flyback. But, xvidtune did what I told it to do, so I could only blame myself.
We all have war stories. But, it should be left to MY discretion when to use the root account and when not to. Not only do I not need a nanny I despise a nanny. Actually it's a little bit past despise. Maybe LOATHE?? Good Boundaries are what I talking about. It's my machine. It's mine to administer and mine to break. Don't put a "should" on me, as it's mentally unhealthy for the "should"er. Period. My two cents, Ric
one of the biggest things I hate about windoze is that it tries to protect me from myself
yes I did delete the /usr directory once for 3 years on that computer the only user account was root with only one problem
as root I am the unquestioned owner of the computer NOT a less than welcome guest who needs to be watched over
IF I need to work on the system I login as root
Man...
And I get sick of people trying to be heroes by trivialising the importance of not running as root. Painting it like it makes you some kind of special and encouraging others to do the same is just irresponsible IMHO.
Who is trying to be a hero? Who is trivializing? Where did I write I was special? Where did I encourage anybody else into any specific action?
Quote:
Yes it's your box and you can do with it whatever you want. If you understand the risks and are prepared to take them then go ahead.
If the root account was not meant to be used then it wouldn't exist.
No-one is saying it's not ok to log in as root or use root to do system administration.
Creating and using a non-root user for day-to-day activities is a good practice and should be encouraged.
Of course there are systems that this is not possible/practical/convenient.
No-one is stopping you from doing whatever you want with your computer... it's not like they are taking the root password away from you.
@ rob.rice
"su -" (as suggested by Nille_kungen) will actually give you full root privs and environment.
Personally getting pretty tired of your anti KDE4 spam... It will be part of Slackware-13.0 so if you don't like it just stay with 12.2 or use another DE.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.