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.
I use Citrix receiver almost daily on my Slackware64-current box (for work). I never cared for Google Earth but the SlackBuilds.org page has extensive instructions on the required actions for Slackware: http://slackbuilds.org/repository/14.../google-earth/
Thanks - I couldn't find that info when I was looking. I can't see the website right now (work thinks slackbuilds.org is a threat to their network), so I'll have to take a look later.
Quote:
Everything is possible on Slackware like on other (major) distros - it just takes more reading, more knowledge and more tinkering sometimes. People who do not have that time and need a working environment for their day-to-day jobb, might be better off with one of the major players like Kubuntu. Glad to read you're still using Slackware for the server though!
Yep, I know it is possible (since I can get it working under Kubuntu), and that's the part that bugged me. But you hit the nail on the head: I just don't have the time to deal with it any more. I want to say I was trying to do this under 13.37, but I'm not certain.
For me, and maybe this is a personal failure, but whatever - the rpm2tgz program has only ever successfully produced one or two packages that I could install. I never quite got the hang of slackbuilds, either - I thought I was following the directions, but they just didn't seem to work for me most of the time. I have no idea why - different versions of the source package or something, probably.
It was hard to switch from Slackware, but I'm glad I made the switch for my desktop machine. It does a great job of letting me know when security updates are required, too. Of course, it follows closer to the bleeding edge, so updates are necessary more frequently. I had to reset my thinking on that after using Slackware.
Are you the Alien Bob of the alien Slackware packages? If so, thank you for your hard work - I've used quite a few of those over the years.
The bad thing I've found from using the *buntus is that they try to incorporate so many optional dependencies into packages pulling lots of extras. Plus the fact they break down packages into dev, bin, lib, src, and meta packages and very little built actually from source, and the fact that while yes, it does keep you informed about updates, you can easily do the same via Slackware but in a less formal way.
It was hard to switch from Slackware, but I'm glad I made the switch for my desktop machine. It does a great job of letting me know when security updates are required, too.
Thanks - I couldn't find that info when I was looking. I can't see the website right now (work thinks slackbuilds.org is a threat to their network), so I'll have to take a look later.
Distribution: Slackware64 current multilib, Gentoo
Posts: 43
Rep:
I work with gentoo and slackware, and in gentoo there is no new release, it's continuously updated, like slackware current.
So you can just stay on current, and will automatically go with the flow... and to the new release.
I'd like the next version of Slackware to be a sphere, roughly one quarter the size of Mars.
The entire mass would be composed of nanorobots capable of assuming virtually any form,
including separable, discrete vessels. The bridge, (generally located at the center of the
sphere) could adapt to become any captain's preferred environment.
The propulsion system would amount to an omnidirectional micro-singularity.
This singularity would pull the entire mass towards its heading.
Not concerned about the release date :^)
I'm fine with Slackware sticking with XFCE 4.10 for Slackware 14.2. OpenBSD 5.7 is sticking with 4.10 on May 1st. As always, I would like to see a stable, battle-tested version of Slackware. XFCE 4.12 will show up in -current when it has been thoroughly vetted by the team.
I'd like the next version of Slackware to be a sphere, roughly one quarter the size of Mars.
The entire mass would be composed of nanorobots capable of assuming virtually any form,
including separable, discrete vessels. The bridge, (generally located at the center of the
sphere) could adapt to become any captain's preferred environment.
The propulsion system would amount to an omnidirectional micro-singularity.
This singularity would pull the entire mass towards its heading.
Not concerned about the release date :^)
I'd like the next version of Slackware to be a sphere, roughly one quarter the size of Mars.
The entire mass would be composed of nanorobots capable of assuming virtually any form,
including separable, discrete vessels. The bridge, (generally located at the center of the
sphere) could adapt to become any captain's preferred environment.
The propulsion system would amount to an omnidirectional micro-singularity.
This singularity would pull the entire mass towards its heading.
Not concerned about the release date :^)
If you're an emacs user you can get something similar with 'M-x skynet-nanobot-deathstar-minor-mode'
All taken care of with a queuefile, the bar is installed fully stocked:
Code:
sbopkg -i barandlapdancers.sqf
At least you won't need an initrd.
Make sure you resolve the optional beer-1.0-x86_64-1.txz package dependencies for jack-daniels-07-x86_64-1.txz, jose-cuervo-1.0-x86_64-1.txz, and cute-bartender-40d.24.26-x86_64-1.txz
That version causes segmentation faults with my version of libcutestats.so.
Reverting to cute-bartender-36b.24.36-x86_64-1.txz works for me. I do not compile libcutestats.so with injection enhancement patches.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
