SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Ok I have pulled off a minimal install in a that i have only installed the /slackware/a series of packages on the slack disk 1 also installed /slackware/ap series, which is fine and i have a system up and running well.
Ok so now i would like to install fluxbox of any one of the window managers, the thing is these packages are dependant on other packages, so how do i go about finding out what lib's and packages to install before i install say fluxbox.
I tried doing this before with a failed result and would like to find out some more before I mess with a fully running system.
Is there a way to find what dependancies a pkg has ??
when I install Slackware, I just install the base system without X and so on. After that, I download:
- swaret using lynx
- newest Xorg using swaret
- windows manager using swaret and so on ...
swaret tries to find out which libraries does the specific application need. it does that by using "ldd" command. you can also run it by hand.
but, if you install fluxbox, and if it doesn't want to start, you'll see the error on the command line and you'll see which libraries are needed.
finding dependencies i usually do what malo_umoran mentioned. I run the application at the command line, and it would spit back a missing dependency. This could take a while, because it usually does it one missing dependency at a time.
For X you need to install the base X package plus fonts-misc. You also need tcp-ip installed since X uses it to communicate with linux. for fluxbox the only other thing you need is cxxx-libs since fluxbox is a c++ prog.
You can have a small install with fluxbox with about 130MB of software installed.
I personally prefer to use the slack sources (x and xap are on disk 4) and it comes with build scripts and make the packages. You can edit these to use the optimization tags for your processor, and it will make .tgz's that you can save and use every time you choose to reload.
I think the c libs part is what im looking for thanks
Hope this works out at the moment im getting the x server to start but having a few problems trying to get serial mouse to work , also seem to be getting 3 errors before x startx
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/zaind-pt00c:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
Havent got a clue as to whats happening there though.
Internet Protocol 6 is not compiled in by default, but this creates no problem.
* Most 'errors' reported by the kernel and programs are really not serious and mostly mean 'I looked for this but didn't find it.' The message fails to follow up and tell you ',but that's alright, we can run anyway...'.
If a program runs the error is not fatal. Of course many of these can be done away with by re-compiling the kernel just for your hardware and disabling a few items in the init scripts.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.