Some Basic Slackware Setup - Post Install
Greetings again everybody,
First off, I'd like to let everybody know that if you ever decide to install slackware, and you're using an LSI controller (shipped with some Dell PowerEdge servers), the kernel you need to load is "raid.s". Knowing that will save you hell and back. Next, I have some questions. After installing slack, I created myself a new user. I assume most of the problems that I am having are related to my persmissions or so, so you guys probably won't have a hard time answering my questions. 1. When starting X, I get the following error: Code:
There was an error setting up inter-process communcations for KDE. The message returned was : 2. When I'm logged in as my username, and SU, commands don't work properly. For example, typing "startx" as SU gives me a "command not found error". What gives there? 3. Somebody care to help me get my internet working? I thought I had everything set up right on install, but apparently I don't. It might simply be that only one network card was setup on install, and it happens to be the wrong one that I'm plugged into :-/ I'm not sure exactly what is going on there, but I have 3 network cards (2 integrated, one Intel). Let's start off with those. I may have a few more questions later. Thanks for everybody's help here. You all have been major support. |
linux is case sencitive......
i cant answer many of ur questions.. but type 'su' instead of 'SU' that will fix that one. |
I'm sorry. This is when I'm typing it already as su. I typed SU above as to not make any confusion as a spelling error or something.
It's not just that command that doesn't work, either. When I went to configure X, I couldn't get in as su, I had to log in directly as root, because typing "xf86cfg -textmode" would give me an error as su, but not as a regular user, or as root. |
when you login to root, your path is different then when your a normal user. try echo $PATH under normal user, root, and su to root from normal.. and check the differences, or post them for more info...
when you installed, did you use the kernel default of the bootdisk, or did you compile your own, run some things like lsmod lspci pnpdump and see if anything is showing for your network cards.. if you need help with those check their manpages, also check man su, for more details on why that may not be working whatever i didn't answer, please reask, with specific examples, hardware types, manpages read, and things tried... |
Alright, under root:
/usr/local/sbin /usr/sbin /sbin /usr/local/bin /usr/bin /bin /usr/X11R6/bin usr/games/opt/www/htdig/bin /usr/lib/java/bin /usr/lib/java/jre/bin /opt/kde/bin /usr/lib/qt-3.2.1/bin /usr/share/texmf/bin Under my login: /usr/local/bin /usr/bin /bin /usr/X11R6/bin /usr/games /opt/www/htdig/bin /usr/lib/java/bin /usr/lib/java/jre/bin /opt/kde/bin /usr/lib/qt-3.2.1/bin /usr/share/texmf/bin And as su under my login: /usr/local/sbin /usr/local/bin /sbin /usr/sbin /bin usr/bin As for my kernel, I used raid.s from the boot disk, but I'm going to need to recompile to take advantage of my dual processors and 2GB of RAM. After running pnpdump, I see that it seems as though my ethernet cards were recognized: Ethernet controller: Intel Corp. 82544EI Gigabit Ethernet Controller (Copper) (rev 02) Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 02) Ethernet controller: Broadcom Corporation NetXtreme BCM 5704 Gigabit Ethernet (rev 02) |
Well, there's one of your problems. startx is under /usr/X11R6/bin, which is not in your $PATH in su. One way to get around this is to run su - instead. This makes su log in and run the scripts that set up $PATH and co.
|
Thanks, rkngl!
Now I can startx under su, but I still think the permissions are messed up when I'm trying to log into X when not root or su, because I'm getting the error Code:
xauth: timeout in locking authority file //.Xauthority Ideas? Do I have to change permissions on this file or something? |
Yeah, I'm getting an "installation" error with "no write access to the /home directory".
KDE needs to write directly to the /home directory when just trying to run the program? |
OK, I'll ask the obvious question. What is wrong with your permissions? Have you been messing around with them?
|
I never changed anything. In fact, I've not used chmod once in this install.
|
look at the chown manual page,
it explains how to fix your home directory something like chown -R usrname:users userdir did you say run su - as in "su -" ??? which network card do you want to get working?? should work right away if you recompile with support.. |
As it turns out, I only have one network card configured (I'm sure I will ask more on how to get the other ones working as well later on).
However, the bigger question here is that it seems that my "home" directory for new users I create is "/", instead of "/home/userName". Maybe this is what's causing the problems? Why isn't a home directory created for new users that I add? |
Since you're running slackware, use adduser instead of useradd. adduser will create the home directory (/home/<username>), etc for new users.
|
rkngl, THAAAAAAAANK YOU!!!!!
*drool* Good man... good man (or lady). |
:) man it is. good luck
|
All times are GMT -5. The time now is 11:57 PM. |