SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
check the sudoers file in /etc and see if user and the proper permissions. Slack 9 seems to configure differently for everyone, also look at the package installer, and see if "sudo" is installed, mine is version 1.6.6
thanks for your replies, but I did not make myself clear.
I thought sudo was maybe what I needed to setup, but it is not the case.
I can su to root ok, but I cant start an X display for root if I log on as user. I read elsewhere that I need to use xhost + , but this was not necessary in the previous distro I was using. The example I gave was nmapfe, which has different options available as root, so I used to launch it from a console in which I had su'd to root.
I don't know the reason behind this (security?). But to allow other users to use your display you have to spell it out now in your ~/.xinitrc file (or just from command line from a termnial emulator) that your box is one of the xhosts.
in .xinitrc or command line will let you have what you want.
General rule, don't use sudo if you don't have to.
I solved the problem. When I used mandrake, I always used to add '-nolisten TCP' to the kdm Xservers file. This stopped X from listening with the port 6000 open, which I considered a potential security risk. It never prevented me from opening apps from the console as root.
I did this immediately when I got Slackware installed, but it seems to make a much bigger difference with Slack, because after removing this I was ok again.
I will just have to rely on my firewall I guess, though I liked the 'boots and braces' approach, and the first thing I do after installation is try and make my box secure.( I still use Shorewall as a firewall, which I find very good)
Thanks for all your help.
putting xhosts into .bashrc is not going to work. at least in case if you do not use any of *dm (gdm, xdm, kdm etc.). because at the moment when your bashrc and profile are sourced no X server is running and DISPLAY variable is not set.
1) it will not brake you back to type "xhost ..."
2) if you want to do it automatically you have to use X related init scripts such as .xinitrc (or probably .xsession if you use *dm)