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.
Distribution: Slackware each x86 + ARM and Porteus
I feel that having an ancient program doing its job just well is one of key elements of Slackware, take ls or sed as an example, or vi (elvis).
I also find cool that there are few other X related programs that fit this category - xclac, oclock etc... Bumping only a version up, or reinventing the wheel is what bothered me most on other distros.
And I just get bored of "yet another" software project that end up in mediocrity.
The mc is an shining example of an ancient program doing it's job right. And again the revival of development brought key improvements (just about right time) while didn't bloat it or made it mediocre.
I couldn't get either your 0.7.2 slackbuilds.org build or the 0.8.1 source to build on my current64 + system.
linking binary 'emelfm2'
/usr/lib64/gcc/x86_64-slackware-linux/4.7.1/../../../../x86_64-slackware-linux/bin/ld: objs/src/dialogs/e2_file_info_dialog.o: undefined reference to symbol 'dlclose@@GLIBC_2.2.5'
/usr/lib64/gcc/x86_64-slackware-linux/4.7.1/../../../../x86_64-slackware-linux/bin/ld: note: 'dlclose@@GLIBC_2.2.5' is defined in DSO /lib64/libdl.so.2 so try adding it to the linker command line
/lib64/libdl.so.2: could not read symbols: Invalid operation
And the 0.8.1 complains about undeclared dbus references, though as far as I can see pkg-config returns the correct flags and the header file that defines the missing reference is there. At this point I'm not prepared to spend any more time trying to get this to build.
Although it doesnt group files together in an intelligent way, so instead of grouping all the video files (.avi, .mkv, .mp4, etc) together, you get them separated by other file types (which also arnt grouped together), so you have to go hunting for a particular filetype. I might suggest that on the mailing list actually.
Other than than that, I like it.
Last edited by clifford227; 06-28-2012 at 06:55 PM.
I'm a long-time Slackware user (since 3.0) but sometimes slow to adopt new technologies. Can someone explain, please, the advantages of using a file-manager application (compared to the traditional ls, find, grep, mv, cp, rm, less, etc)?