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.
Don't put it in .bashrc. Put it in /etc/profile.d/local.sh and make that file executable.
If you just boot into runlevel 4, go straight to your graphical environment and launch Chrome, then your .bashrc will not have been loaded. The files in profile.d, however, will have been.
Well, I boot into runlevel 3 and I had sourced my .bashrc explicitly after the changes, but it did not work (I also restarted qwit but I don't think that matters). Now that I've created the simlink to google-chrome it works (as expected) but I can not check the other settings.
I've also, some days ago, started kde and configured for chrome in the system-settings. And whithin kde I had really chrome as the default, also with qwit. But in fvwm the kde-settings work only for kde-programs.
Thanks for the info, dugan. I, too, boot into runlevel 3, but it always helps to know this stuff, just in case....
Glad to see you got it working, markush, but I'm a bit curious as to why the .bashrc thing didn't work for you.
Not that it *should* make any difference, but when I initially tried it out with qwit, I ran the export cmd from the cli, after I had logged in (hence, after .bashrc had been sourced.) I'm wondering if it would work if you created a script that set the BROWSER path before executing qwit.
Regardless, since it just *works* now, why fuss with it...?