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 don't know if this question is dumb or not, but is it safe to install dropline on slack 11? On their site it says that Dropline Gnome is made for slackware 10.2. What is the correct way to get gnome on my system?
I'm running 2.14 Freerock Gnome on Slack 11 and so far, so good. It's only been a couple of hours, though. Not a thorough test. I talked to him tonight and 2.16 is in unstable and was built with Slack-current about a week ago.
Doesn't answer your question directly, but maybe helps you decide whether or not to try it.
If I were you I would just wait for a little bit, maybe a week or two. There will be out packages from all the third-party gnome distributors for slackware 11. We've waited for over a year for slackware 11. Can't you just wait for a week for gnome?
I wouldn't use Dropline gnome for 10.2 on a 11.0 system, because in slackware 11 many things have changed and Dropline gnome has the tendency to change a lot of the default packages.
I would be carefull installing Dropline Gnome on a slackware machine. Dropline has a bit of a habbit replacing a whole bunch of packages, including some major ones like X.
You might want to have a look at either Gware or freerock who are lighter on replacing slackware core stuff
I have used Dropline with Slackware for years with great results. I get real tired of folks talking about Dropline replacing slack packages like it is a mortal sin. Read the real explanation on the Dropline website at http://forums.droplinegnome.org/viewtopic.php?t=4739
I guess I will wait. I get nervous with Dropline because last time I used it it patched up my rc.inet1 script. After that happened I had a lot of command errors when it executes at boot. I might try freerock when they make a skack 11 package. Thanks for the advice
I guess I will wait. I get nervous with Dropline because last time I used it it patched up my rc.inet1 script. After that happened I had a lot of command errors when it executes at boot. I might try freerock when they make a skack 11 package. Thanks for the advice
This was a bug in a GNOME componenet that ships in all GNOME versions for Slackware (Dropline, Freerock, Gware). It isn't exclusively a Dropline problem, but is rather an issue with GNOME itself. As far as I know, we are the only ones who have patched around it (as of 2.16.0) to stop it from misconfiguring rc.inet1. We intended to patch it out with a previous release, but it slipped through the cracks.
We currently have a pre-beta version of 2.16.0, and we are putting on the final touches. As rje_NC mentions, we no longer include X11 in Dropline GNOME, since we feel that Slackware's 6.9.0 build is very nice and does everything that we need it to do. At least 12% of the total packages have been dropped with this release. This goes for replacement packs and things that Slackware is now including but hadn't previously. I think I did a quick count and we now replace about 10 packs more than Freerock's last release, but virtually all of them are GNOME components with a few exceptions to make things like Network Manager and PAM support (now required by some GNOME components) work properly.
Though it's technically "pre-beta" status, things are very stable right now and we should have all of the rest of the kinks worked out this weekend.
So that people don't have to do what you've just said. Fetching the source and compiling might not be as easy of a task as you make it appear.
On a side-note, I find the greated problem with Gnome+Slackware [I love Slackware, I love Gnome.. but I don't run Gnome on Slackware] the thing that you can't stay -current *and* have one of the 3rd party GNOME kits. They all seem to need the -release.
It isn't exclusively a Dropline problem, but is rather an issue with GNOME itself. As far as I know, we are the only ones who have patched around it (as of 2.16.0) to stop it from misconfiguring rc.inet1.
Just curious - what the heck has some even generic GNOME tool/component to touch some initscript ? For configuration purposes there is long time ago extracted rc.inet1.conf.
Just curious - what the heck has some even generic GNOME tool/component to touch some initscript ? For configuration purposes there is long time ago extracted rc.inet1.conf.
You're totally asking the wrong guy.
We wonder the same thing. What do the system-tools-backends authors know? They don't likely use Slackware, and some random Slackware user probably suggested it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.