How Do you Login to Root

[Crusty]

if you have it installed, then assuming you have installed it right you should be able to edit your /etc/samba/smb.conf file to add network shares.

head on over to samba.org and read their documentation.

Come back once you have at least attempted to get a share working.

 

[0rion]

I have started to read Some Samba doc but, I think my problem is with LISa daemon, for that is what the Error says. Can you just tell me how to install that becouse it says that is not installed?

 

[Crusty]

Have you installed the kdenetwork package?

try typing smb: into konqueror

 

[0rion]

yes i have, i can transfer files to a nother box but when i go to LAN Browser (to find my other box) and type lan://mshome/ is when i get the error

 

[n0cmonkey]

mount -t smbfs

 

[0rion]

Thanx for all the help after hours of reading http://doc.mandrakelinux.com/MandrakeLinux/92/en/Starter.html/ I have fixed the problem with the LAN but I would still like to Log in to Root with KDE still have not found that. In the log in screen all I see is my User name!!!!

 

[Crusty]

Don't login to KDE as root! It is a BAD BAD BAD idea.

 

[Nothinman]

type 'su -' instead of just 'su', the dash resets your environment so the shell will use root's environment instead of your own.

 

[Crusty]

Originally posted by: Nothinman
type 'su -' instead of just 'su', the dash resets your environment so the shell will use root's environment instead of your own.

Hrmm...I didn't know that...

is it really that usefull?

 

[n0cmonkey]

Originally posted by: MCrusty

Originally posted by: Nothinman
type 'su -' instead of just 'su', the dash resets your environment so the shell will use root's environment instead of your own.

Hrmm...I didn't know that...

is it really that usefull?

Sometimes. I needed to do it for a while and just got in the habit of adding the -.

 

[Crusty]

Originally posted by: n0cmonkey

Originally posted by: MCrusty

Originally posted by: Nothinman
type 'su -' instead of just 'su', the dash resets your environment so the shell will use root's environment instead of your own.

Hrmm...I didn't know that...

is it really that usefull?

Sometimes. I needed to do it for a while and just got in the habit of adding the -.

Heh, well if something ever acts fishy after I su i'll try and remember that

 

[pitupepito2000]

Originally posted by: 0rion
Thanx, but that is not realy what I was looking for, I need to chang to Root in KDE. In the login only my user name is there.

NEVER, AND I MEAN NEVER LOG IN AS ROOT IN KDE. There's no reason to do it. You are putting the security of your system at risk when you do something like that. I would suggest you read a good book about linux, and you will understand many of use tell you not to log in as root in kde.

 

[n0cmonkey]

Forget it. Let him login to KDE as root. He's only hurting himself.

 

[pitupepito2000]

Originally posted by: Nothinman
type 'su -' instead of just 'su', the dash resets your environment so the shell will use root's environment instead of your own.

what kinds of benefits do you get by doing this? What kinds of advantages does it have?

Thanks,
pitupepito

 

[n0cmonkey]

Originally posted by: pitupepito2000

Originally posted by: Nothinman
type 'su -' instead of just 'su', the dash resets your environment so the shell will use root's environment instead of your own.

what kinds of benefits do you get by doing this? What kinds of advantages does it have?

Thanks,
pitupepito

su(1):

- Same as the -l option (deprecated).

-l Simulate a full login. The environment is discarded except for
HOME, SHELL, PATH, TERM, LOGNAME, and USER. HOME and SHELL are
modified as above. LOGNAME and USER are set to the target login.
PATH is set to the value specified by the ``path'' entry in
login.conf(5). TERM is imported from your current environment.
The invoked shell is the target login's, and su will change di-
rectory to the target login's home directory.

 

[MonstaThrilla]

Originally posted by: pitupepito2000

Originally posted by: Nothinman
type 'su -' instead of just 'su', the dash resets your environment so the shell will use root's environment instead of your own.

what kinds of benefits do you get by doing this? What kinds of advantages does it have?

Thanks,
pitupepito

I use 'su -' instead of 'su' because it puts the /sbin directory in my path (very helpful when doing admin work). On the downside, it cd's you into root's home (usually /root), so you'll have to cd back to where you were working if you found out you needed root access for a certain file/executable. This can all be changed of course by tweaking the environment variables.

 

[n0cmonkey]

Originally posted by: MonstaThrilla

Originally posted by: pitupepito2000

Originally posted by: Nothinman
type 'su -' instead of just 'su', the dash resets your environment so the shell will use root's environment instead of your own.

what kinds of benefits do you get by doing this? What kinds of advantages does it have?

Thanks,
pitupepito

I use 'su -' instead of 'su' because it puts the /sbin directory in my path (very helpful when doing admin work). On the downside, it cd's you into root's home (usually /root), so you'll have to cd back to where you were working if you found out you needed root access for a certain file/executable. This can all be changed of course by tweaking the environment variables.

I'd kill lots of things if /sbin wasn't in my $PATH.

 

[Nothinman]

what kinds of benefits do you get by doing this? What kinds of advantages does it have?

Basically it sets up your PATH and anything else set in root's shell 'dot' files (custom aliases, shell settings, etc). If you put /sbin and /usr/sbin in the global PATH via something like /etc/profile it's probably not a big deal.

 

[Barnaby W. Füi]

Originally posted by: n0cmonkey
I'd kill lots of things if /sbin wasn't in my $PATH.

Yeah, I don't really understand why people would prefer it that way. It (/sbin *not* being in $PATH) seems to generally be the default on linux, or at least debian.