Find the answer to your Linux question:
Page 3 of 4 FirstFirst 1 2 3 4 LastLast
Results 21 to 30 of 34
Yes im serious. im on Slackware 9.0 on a full install. and i typed it letter for letter. like i showed you. if you wish i could even get a ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #21
    Linux User
    Join Date
    Jun 2003
    Location
    Minnesota, USA yes.....
    Posts
    479

    Yes im serious. im on Slackware 9.0 on a full install. and i typed it letter for letter. like i showed you. if you wish i could even get a screen shot.

  2. #22
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    Are you using "su -" or just su when you su to root?

  3. #23
    Linux User
    Join Date
    Jun 2003
    Location
    Minnesota, USA yes.....
    Posts
    479
    just su to root, im not familliar with su -

  4. #24
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    That might be the problem. "su -" actually logs you in as root, while just su only gives you a subshell that runs as root.

  5. #25
    Linux User
    Join Date
    Jun 2003
    Location
    Minnesota, USA yes.....
    Posts
    479
    hmmm in that case. when i do "su -" does it just do it for that terminal or for the whole thing.(logs me out and switches to root) if so how can i hmmm unroot?

  6. #26
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    No, that wasn't really what I meant. I just meant that it goes through the login process, ie. setting all environment variables correctly, invokes the shell as a login shell and so on. It wouldn't be able to log you out completely anyway. I mean, how would it go about to do that, after all?

  7. #27
    Linux User
    Join Date
    Jun 2003
    Location
    Minnesota, USA yes.....
    Posts
    479
    Code:
    troy@slackware:~$ su -
    Password:
    root@slackware:~# kwrite /etc/lilo.conf
    kwrite: cannot connect to X server
    hmm now what?

    Code:
    root@slackware:~# cat ~/.bash_profile
    PATH=/usr/local/sbin:/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin:/opt/kde/bin
    PATH=$PATH:/opt/kde/bin
    PATH=$PATH:/opt/kde/bin
    export PATH=$PATH:/opt/kde/bin
    thats what i get for
    Code:
    cat ~/.bash_profile

  8. #28
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    You probably don't have the xauth PAM module installed. I would have thought that slackware comes with it, but apparently that is not the case. Just to be sure, though, check if you have a line for pam_xauth in /etc/pam.d/su.
    You should install it anyway, since it is A Good Thing to have. I don't know what means of installation Slackware uses, though, so I'm afraid I can't help you get it.

  9. #29
    Linux User
    Join Date
    Jun 2003
    Location
    Minnesota, USA yes.....
    Posts
    479
    Code:
    root@slackware:~# cat /etc/pam.d/su
    cat: /etc/pam.d/su: No such file or directory
    did i do that right? or is "cat" not the right command. or is my system just goofy?

  10. #30
    Linux User
    Join Date
    Jun 2003
    Location
    Minnesota, USA yes.....
    Posts
    479
    TGZ is the package management. not sure if thats what you mean by means of installation but distrowatch tells quite a bit about Distros.

Page 3 of 4 FirstFirst 1 2 3 4 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •