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.
i used useradd (the one which asks the series of questions...forgot whether it was useradd or adduser. i think it was useradd.
and while i'm on the subject, which file do i need to copy from /etc to get the dir colours and aliases that root has? i copied DIR-COLORS but didn't know quite what to do with it. i guess if i put a .xsession in /etc/skel, that'll handle the default wm's but what else?
(and is there a way to extend the inactive timeout thing?...for the forum)
Originally posted by abs and while i'm on the subject, which file do i need to copy from /etc to get the dir colours and aliases that root has?
This is handled by the /etc/profile file... check it out. On all my Slack installations (and there are tens of em), users always have dircolors. I think there might be a profile sourcing problem with your user accounts, or that there's something in your skel dir that's overriding the default profile.
Maybe you can try clearing all things in your /etc/skel dir except for the .screenrc file. And then try to create another user.
(I never have timeout issues with the forum, I'm the only user of this PC so I let it remember my login permanently)
and woah, i must've been real sleepy when i posted those contents. that was of /etc/profile.d/ and not /etc/profile. the latter has stuff like
# /etc/profile: This file contains system-wide defaults used by
# all Bourne (and related) shells.
# Set the values for some environment variables:
export MINICOM="-c on"
export HOSTNAME="`cat /etc/HOSTNAME`"
export LESSOPEN="|lesspipe.sh %s"
what else should i check up on? (for startx)
ps: /etc/skel/ has a .screenrc in it (only) since i'd mentioned it was empty in post #5
You can choose with the script xwmconfig (it is in /usr/X11R6/bin in Slackware 9.1, forgot the place of previous Slackware versions) which (installed :-) WindowManager to start with the startx command. Run it, highlight your WM (with up-down arrow),choose that WM with the Space Bar and give return.
Now issue startx and the chosen WM will be started in X. Some hidden dirs should be present in the users home-dir. Read the xwmconfig bash-script about that. It is not very difficult. And you can modify it to add a downloaded WM you want to try. (e.g. ratpoison). Be aware that xwmconfig is specific for the Slackware distro.
arrggh!!! i have no idea what's going on with my system.
when i did '$ /usr/X11R6/bin/startx' (as u said) it was available to normal users.
then i did '$ echo $PATH' and '/usr/X11R6/bin/' was part of it.
i was wondering what else could be causing the problem since the path and the whole command were available to the normal user. then i tried doing '$ start[TAB]' and it worked! it gave 'startx' as an option. i got the X is already running message...coz this session was on. so i know i works now.
i haven't changed anything! dunno how or why it's working now. i am glad it is but if it should happen again, i won't know how to fix it. i'll probably just post here, again!
anyways, thanks a ton skog and Shade.
@Douwe: choosing a window manager is not the problem. 'startx' itself was not available for normal users. fixed now though.