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 tried out a lot of distributions... mostly working with SuSe in the past... now I switched to Slackware 10.0 for testing... and I love it!!!
But there are some little things that won't work the way I would like them working... and I have been surfing this forum for a while ... but there are stil lsome little things I need help with!
1) I can't access my windows (NTFS) partition as a user ... don't know muc habout this stuff,... other distributions worked from the beginning, so I never got in tuch with that. It seems like a permissions-problem to me. This is what "ls -l "looks like
dr-x------ 1 root root 8.0K date time windows/
When I simply try to "chmod 555 windwos" or "chmod +r windows" I only get a message
chmod: changing permissions of "windows/": Read-only file system
and an errorcode "1"
And from /etc/fstab is that:
/dev/hda1 /windows ntfs ro 1 0
So... I think I have to change something in /etc/fstab ... but, as I said ... I don't know anything for sure :-)
My Second question is:
2) Is there something like YaST or similar in Slackware? Because there are some litttle things I could tune in YaST within seconds... and of course I do not know where and how to do this without it.
For example.... where can I turn on ACPI in some way? How can I change the mouse I am using, to get the wheel working? ... In SuSE I knew how to do this... thanks to YaST ... but how is it going on Slackware.... ?
On to the next:
3) If I place the .bashrc or .exrc in my home... they should overwrite the ones from the system... but in fact they are totally unrecognized ... nothnig happens! NOTHING ... wherther in my personal nor in the root's home they have any effect...
Do I have to turn that on or something like this???
I put some stuff in /etc/profile.d/myscript.sh ... but that seems to be not exactly what I want... because this won't work for root ....
4) Now, the last one is juts some bonus-stuff... I know,... this is not very important ... but I don't like to curses-look of Lilo ... is there a simple way to turn on a graphical Lilo? And may an splashscreen instead of vga-consolse at bootup?
Ok now, I hope it's ok, that I posted all in one thread ... if not, please let me know... I'll fix that.
Away from that I hope some of you guys can help me.... since this forum helped me a lot today and I just could not find out this stuff myself... :-)
Dude, sorry nothing like YaST in Slack. You have to tune the config files on your own. But the advantages to slack are enormous. You get the packages as their maintainers/developers intended. The system stays out of your way. Another good reference site is www.insyte.uni.cc. Moving on to your mouse... go to the cli and type: su. Enter the root password. type: pico /etc/X11/xorg.conf. Go to the section in their called "Input pointer Device (or something like that). At the end of the Options Section you see a line #End of Section. Go just above this line and type: Option "ZaxisMapping" "4 5". Also make sure that your mouse is set to IMPS/2 instead of just PS/2. Search in these slack forums for answers to your questions. Good luck
from "man bash"
When bash is invoked as an interactive login shell, or as a non-interactive shell with the --login option, it first reads and executes commands from the file /etc/profile, if that file exists. After reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and reads and executes commands from the first one that exists and is readable. The --noprofile option may be used when the shell is started to inhibit this behavior.
When a login shell exits, bash reads and executes commands from the file ~/.bash_logout, if it exists.
When an interactive shell that is not a login shell is started, bash reads and executes commands from ~/.bashrc, if that file exists. This may be inhibited by using the --norc option. The --rcfile file option will force bash to read and execute commands from file instead of ~/.bashrc.
I completely forgot the .bash_profile etc... now, that works for me.
But this all is ... errr ... I don't know .. .confusing?
Because... .bashrc won't work for any user... don't know why ... so I have to use .bash_profile ... but suddenly .bashrc works for root .... damn!
Well,... I got what I wanted to far.... and I can't tell you how thankful I am!
You guy really did some for me! ... there are some other things I have to figure out... but that will be another thread !