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.
Every Linux distribution has a GNU OS at it's core, called GNU/Linux.
Just like every other distribution, a distribution is characterized by it's packages, support vectors, and management systems.
Regardless of distribution, GNU/Linux is always there.
Doesn't matter if it's LFS, Red Hat, Slackware, Gentoo, SuSE, Debian, or Mandriva. GNU/Linux is the heart and soul of every Linux distribution.
Regardless of the contributions of GNU, I found the demand to call it GNU/Linux to be pompous. I mean, probably most people using Linux spend the majority of their time in X. Lots of tools and networking code came from BSD. There are many other important contributions that support the finished operating system. Shouldn't it be GNU/BSD/X/KDE/Xfce/Mozilla/Linux? I don't see Linus telling RMS what to call GNU Hurd. When you put together the finished package, you get naming rights.
Also, this is WAY off topic. When a thread turns into a GNU/Linux debate, it's the open source equivalent of Godwin's Rule.
Can mc (Midnight Commander) get an update at this late stage? I've been using mc-4.8.10 for some time and found some of the problems I have in 4.8.9 fixed.
current: cups complain "missing filter hpgltops" in its log, but cups prints fine, is it intentional to left out hpgltops because its security concerns?
Will Vim 7.4 still make it into 14.1?
I would just build Vim myself but whenever I checked out the buildscripts on the isos in the past, not all patches always made it in, so I wonder if Pat (or whoever maintains it) has some special criteria and I have more faith in the Slackware team than in myself when it comes to those things :P
Pat, may I suggest bumping GNU sed -- unless you're aware of a good reason not to. A while back I was building shadow (when the Slackware one was still back-level) and I found that the make got stuck with a sed process in a 100% CPU busy loop. After I updated to sed-4.2.2 and tried again the build completed successfully. I've not encountered any other instances of this happening (and it doesn't happen with the current shadow.Slackbuild either) so I'm assuming that I managed to hit some weird-ass corner case but it may be worth bumping on the off-chance that something is still lurking in 4.2.1.
Will Vim 7.4 still make it into 14.1?
I would just build Vim myself but whenever I checked out the buildscripts on the isos in the past, not all patches always made it in, so I wonder if Pat (or whoever maintains it) has some special criteria and I have more faith in the Slackware team than in myself when it comes to those things :P
Just upgraded to 7.4, seems to run without a problem. Upgrading is fairly easy:
- Obtain a copy of the directory /sources/ap/vim from your -current repository
- Remove the directory patches and the file vim-runtime-syntax-20110328.diff.gz from that directory
- Download and copy the Vim 7.4 tarball into that directory
- Edit the files vim.Slackbuild and vim-gvim.Slackbuild, change the version in line 23 to 7.4 and the version in line 26 to 74 (line-numbers are the same in both scripts)
- Save the scripts and run them, install the packages, done.
Last edited by TobiSGD; 10-03-2013 at 08:58 AM.
Reason: fixed nonsensical instruction
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.