{BBI}Nexus{BBI}

 

A typically agressive reply and I'm not going to bother responding to each point, however I do agree that to answer or not is completely your choice, like wise as artic says, if you're not going to provide the answer to the question asked, then don't respond to the thread.

That's agressive?

And you don't have any right to tell me I can't reply...

I don't need to read your reply to this.. there's this neat feature when I can block any pm's you try to send me and not have to read the bullshit ....it just tells me you posted something and I don't have to read it... how cool is that....

 

Meanwhile start reading so you can start helping the users who's systems you wreck...

LOL

 

So what if he/she ends up back here asking for advice when things have gone wrong, isn't that what this forum is all about?

 

If you're not willing to divulge the info requested, why send the user to google for the answer? That makes no sense when you already have the answer.

{BBI}Nexus{BBI}, your free to divulge the info, I'm just not doing it....

If someone googles the answer (its on this board) between now and fionding it they will find proably 50 posts and stuff telling them not to....

 

At the end of the day, if someone unknowingly logs in as root and breaks something I'l spend my time helping them, if they are told its a bad idea then actually search and do it anyway I don't see why I should help them....though nooone will stop you helping them....

 

So what if he/she ends up back here asking for advice when things have gone wrong, isn't that what this forum is all about?

I guess its many things to different people.... its about people helping others.... if that person chooses to deliberatly wreck their system then I am allowed to choose not to help them....

In a similar way I don't help anyone that uses the Mandriva network wizards because I wasted to much time and effort helping people who use it...if they choose to use them then someone else can help them but it won't be me.

 

If a user asks a question that requires mutliple quotes to answer.... I don't answer it... end of story because the board management has decided to limit the number of quotes.... not my problem.

 

If the board could be bothered to give non mods a decent upload limit for files I would answer several other questions that require diagrams BUT I'm not going to waste my time trying to explain something in 1000 words that could be explained in a simple diagram....like networking diagrams.

 

But finally at the end of the day the question is already asked and answered at least 10 times on this board....

 

If the original poster can't be bothered to find it then why should I ???

 

 

I did figure out that if I log in via console as root, then run KDE, I am then in KDE as root, so that is good enough for my occasional desire to do that.

 

I thought something might be misconfigured in my KDE since I had the capability in 2006 and didn't after upgrading to 2007.

 

I do agree that it is probably a good idea that it is restricted. At least it makes me slow down and think about what I am about to do.

 

 

 

 

 

Open a text editor (kwrite or whatever your favorite is) in root mode. If you don't have an icon for that, go to the main KDE menu button (usually at the far left end of the task bar) and select "Run Command" or equivalent. Type the name of the text editor you want to use in the "Command" box, then click the "Options" button. Select "Run as a different user" and type "root" into the Username box. Type the root password into the Password box and click "Run."

 

When the text editor appears, open the file, "/etc/kde/kdm/kdmrc" and search for the line for the command, "AllowRootLogin."

 

Change "false" to "true" and save.

 

Just logging out should be enough for the changes to take place, but if it doesn't you may have to restart the X server (ctrl-alt-backspace) or reboot.

 

You will now be permitted to login as root. ;)

 

 

It already says:

 

"AllowRootLogin=true"

 

I think I found that tip when I first discovered this, but it didn't seem to work. I left the file edited with true.

 

But I am glad to know about that trick for launching Kwrite in root mode. That will take care of many of my reasons for wanting to switch to rrot, it is to edit such restricted files using a GUI editor.

Also as I sad earlier

 

kdesu konqueror (will start konq as root) ((((BE CAREFUL)))))

kdesu kate ... yep you got it will start the kate editor as root....

also if your running konqueror as root and then you select a file and an action that action will be performed as root.

But seriously check out krusader ... it allows all of this from within a simple interface whci allows you to switch to/from root mode....

A typically agressive reply and I'm not going to bother responding to each point, however I do agree that to answer or not is completely your choice, like wise as artic says, if you're not going to provide the answer to the question asked, then don't respond to the thread.

its only 3 letters need changing in a config file and if you can't work out how to do it Im certainly not going to tell you. Its that way for a reason.... but by the time most people actually work it out most people realise its not such a great idea...

Chance is if you do this you'll be back here very soon sabving how your system is borked....unless you know what your doing and by definition you don't or you'd know how to enable it....

Sorry sounds rude.... but Ill help you (and lots of others will) to help you achive what you need...

really we will..... but when that involves the linux equivalent of juggling with knives we get squeamish....

 

If you google search kdm root login you will find the answer eventually after finding lots of forums with threads like this.... please just take a second and think WHY

Whilst I strongly agree that users logging in as root is a bad idea, everyone should have the opportuninty to find out why for themselves.

To be refused information on the basis that it's for their own good smacks of nannying.

The user has already logged in before as root using the gui.

So what if he/she ends up back here asking for advice when things have gone wrong, isn't that what this forum is all about?

If you're not willing to divulge the info requested, why send the user to google for the answer? That makes no sense when you already have the answer.

You issued the warning and outlined the reasons why using the root login is a bad idea. Nobody sets out to deliberately break their system (unless for testing purposes), but breaking, fixing and being surrounded by a font of knowledge to assist you when you fall down is one of the reasons why Linux is such a great op/sys to run.

Check if you have the lisa package installed.

Just type in a console window: rpm -q lisa if it says there's no lisa package installed type: su press enter, input your root password press enter, then type: urpmi lisa when the package is installed type: exit to leave root mode.

K3b does vcd burning.

Hello to all, can someone help me to resolve this problem and hopefully get my smart-gui to re-appear. I recently did an upgrade of a few packages (recommended by smart). Now when I try to use the smart-gui nothing appears. I type smart --gui on the commandline and i get this. error: Interface 'gtk' not available. I've checked and the package gtk is installed, I've removed smart-gui and reinstalled it, still no joy. What else do I need to do to resolve this?

=======Update======->Resolved by updating to Spring 2007<-======

Have you tried "dummy" at the /etc/X11/xorg.conf settings?

It works for me, with no keyboard/mouse/monitor being connected...

Could you please expand on the above advice? At what point in the xorg.conf file is dummy to be inserted?

I lifted this from here: http://www.cpqlinux.com/memory.html

Installing with more than 1GB of memory:

It is not wise to have the installer use more than 1GB of memory. The installer may not be configured to handle it and may get confused and abort. Limit the amount of memory that the installer sees to 960M. The following may be keyed in at the boot prompt:

mem=960M

Gaining access to more than 1GB of memory:

If your system isn't detecting more than 1GB of memory then there are several ways to get around this:

Install the Enterprise-kernel - this has support for more memory built in already (this would suggest you may need to use this kernel)

Recompile the kernel choosing either 1GB, 2GB or 4GB during configuration

Recompile the kernel enabling bigmem

This may be a little late, but usually these older boards have a jumper on them to disable the onboard video.