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.
The system is a remaster of Ubuntu 13.10 – codenamed Saucy Salamander, released 20131017. The original system includes the Desktop Environment Unity 7.1 (Ubuntu). I have replaced Unity with KDE 4.11.2, Gnome 3.8.4, Gnome Fallback (Classic) 3.8.4 (which makes Cinnamon expendable) and Razor-qt 0.5.2.
Run your Slackware 64 bit system with the latest kernel – 3.11.2!
I have compiled a very useful (as I think) 64 bit kernel for Slackware 12.0 – 14.0 and/or all Slackware derivatives. For example Slax, Zenwalk, SlackEX and Exton|Defender.
I’ve made a third version of exGENT 2013. Now with LXDE and kernel 3.9.2-gentoo-exton. Version 130521 is for the 64 bit architecture. I’ve kept my two previous versions 20130423 and 20130415 on Sourceforge.net. The old versions are for the 32 bit architecture.
exGENT 64 bit version 130521 is in very good shape. Yesterday I could run the following commands without problems:
When XWindows was ported to 64 bit architectures, the decision was made (probably for legacy compatibility) not to add a 64 bit data format to routines that return overloaded pointers, specifically XGetWindowProperties. Pointers, which are 64 bits, are returned in 64 bit elements that are claimed to be 32 bits. There is no way to cope with this in user code, except to check which architecture you are running on. The compiler define "__x86_64" is set on Intel 64 bit compilers. wmctrl (not...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
