Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
I'm running aterm 0.4.2, KDE 3.2, and fluxbox 0.1.14
For some reason
works in KDE but not in Fluxbox.
In fluxbox, it returns
aterm: bad option "-bl"
But in KDE, it works fine--pops up a borderless aterm with no complaints. Anyone know why this might be? I'm thinking "-bl" might be a KDE specific option rather than an aterm option. If this is the case, does anyone know how to run programs without borders in flux?
I'm using Fluxbox 0.1.14. The main reason I haven't switched to a devel version yet is because I don't know if I could live without external tabs. They're soooo handy. I can't even use KDE or gnome anymore...I can't use anything buy flux now. I wish they'd make it an option to place the tabs externally rather than in the title bar in the devel versions.
Anyway, I don't have an apps file in either /usr/X11R6/share/fluxbox or in ~/.fluxbox, so I doubt that it will work with 0.1.14. Maybe I'll try creating an apps file and see what happens. Thanks for the info, Hangdog.
Don't bother with the apps file. That was introduced well after 0.1.14. In fact if I remember correctly, fluxbox didn't add the ability to run without borders until later as well. I might be wrong about that, but 0.1.14 is a couple of years old. However you still may want to give the devel version a try. The lack of the tabs really isn't as bad as you think.
I think I will give a devel version a try. Is it possible to install another version side by side with my current version? I'm afraid the location of the configuration files may cause a problem.
Also, I'm kind of surprised that Slack 10 comes with such an old version of Flux....I wonder what the reasoning is.
edit: Ok, so 0.1.14 is the last "stable" version...although 2 years old.
I highly doubt that the stable and devel versions will co-exist nicely. I think it is one or the other. The good news is that Slack DOES come with the devel version, it is just in the extra folder along with a few other goodies.
Originally posted by kersten78 I think I will give a devel version a try. Is it possible to install another version side by side with my current version? I'm afraid the location of the configuration files may cause a problem.
You can run both side by side without trouble if you use a different rc file for fluxbox devel.
You'll need to install from source in order to prevent overwriting the stable files, and you'll probably need to start flux stable with a full path from now on, or rename the devel binary.
Before starting Fluxbox devel:
Create a new init file for fluxbox devel. Easiest way would probably be
cp init dev-init
Edit $HOME/.fluxbox/dev-init, changing paths to something other than the configs listed (I used "dev-filename" for everything).
Start Fluxbox devel with "/path/to/fluxbox -rc $HOME/.fluxbox/dev-init".
Keep in mind that if you start flux devel without the -rc option, it will use the configs from flux stable, and things might not look and behave exactly right.
mikshaw, thanks for the info. I have the source downloaded and ready to ./configure, but I'm not sure if I need to change the path to prevent it from installing over my current fluxbox installation. Do I need to use the options
--prefix=PREFIX install architecture-independent files in PREFIX
--exec-prefix=EPREFIX install architecture-dependent files in EPREFIX
It looks like if I change the prefix, the exec-prefix will change automatically. Is this the case? I just really don't want to screw up my current install in case I can't stand the new tabs.
Hangdog, is the devel version installed with the full Slack 10 install? or is it something I need to pull off the extra CD's that come with it? If it is installed with the full version, where might I find it?
EDIT: I just looked around a bit, and I'm wondering what to do about all the flux files in /usr/X11R6/share/fluxbox and also the /usr/X11R6/bin/fluxbox and /usr/X11R6/bin/fluxbox-generate_menu binaries? Will installing the devel version mess with those?
I think that the development fluxbox is on one of the extra CDs. Of course you can also download it from your favorite Slackware mirror.
I would assume that using the Slackware package would indeed mess with those X11 files. However, most of the files you've modified are likely to be in your ~/.fluxbox directory and the Slacware package shouldn't mess with those.
I got some help from #fluxbox on freenode. I ran configure, make, and then
make DESTDIR=/my/devel/path install
and it worked without a hitch. I did have to edit the new init file to use the right menu file, etc. but it's working right now. The new tabs are not at all what I imagined them to be. I guess I was thinking of the old tabs just moved down into the title bar. It's more like a split title bar rather than tabs in the old sense. Pretty awesome. I'm going to play with it for a while, but I'm already impressed. I'm sure it will take over soon enough. Thanks for the help everybody.