LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-22-2007, 10:33 PM   #541
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,543

Rep: Reputation: 1206Reputation: 1206Reputation: 1206Reputation: 1206Reputation: 1206Reputation: 1206Reputation: 1206Reputation: 1206Reputation: 1206

To be honest, I'm not very familiar with swaret, so I'm certainly not a definitive source for information on it.
I've recently written a short document about third party package management on SlackWiki.org - have a look at this and see if it addresses your concerns adequately: http://slackwiki.org/Third_Party_Package_Managers
 
Old 05-22-2007, 11:12 PM   #542
Alien_Hominid
Senior Member
 
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247

Rep: Reputation: 53
There is nothing wrong with current, if you upgrade it properly. Using swaret you might mess it up.
 
Old 05-23-2007, 01:43 AM   #543
Bebo
Member
 
Registered: Jul 2003
Location: Göteborg
Distribution: Arch Linux (current)
Posts: 553

Rep: Reputation: 31
Yes, the trick is to read the changelog.
 
Old 05-23-2007, 11:32 AM   #544
Vincent_Vega
Member
 
Registered: Nov 2003
Location: South Jersey
Distribution: Slackware, Raspbian, Manjaro
Posts: 826

Rep: Reputation: 31
Agreed. Using 'current' is fine but only as long as you have first upgraded *manually* to current. Otherwise, if you install Slack 11 and just think you can change to version=current and magically get your whole system upgraded, you will soon find out that you are wrong!!

I'll check out that document, rworkman. I don't have any problems with package management or upgrades but I was confused by what was said about swaret. That's why I just wanted to clarify.

Thanks for the replies.
 
Old 08-22-2007, 05:43 PM   #545
efrixione
LQ Newbie
 
Registered: Aug 2007
Location: Indianapolis, IN
Distribution: Slackware
Posts: 2

Rep: Reputation: 0
you are a genius!
 
Old 01-25-2008, 08:34 AM   #546
K@rl`
Member
 
Registered: Feb 2004
Posts: 70

Rep: Reputation: 15
Hi guys,

I've shamefully been away from linux for a long time.

And I've completely forgotten what config file I change to change from Fluxbox to KDE.

I'm sure it'll come back to me once I see it

cheers
 
Old 01-25-2008, 11:52 AM   #547
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,438

Rep: Reputation: 7645Reputation: 7645Reputation: 7645Reputation: 7645Reputation: 7645Reputation: 7645Reputation: 7645Reputation: 7645Reputation: 7645Reputation: 7645Reputation: 7645
Run xwmconfig and select KDE

Eric
 
Old 01-27-2008, 11:48 AM   #548
swaid06
LQ Newbie
 
Registered: Dec 2006
Distribution: slackware
Posts: 1

Rep: Reputation: 0
great howto here only thing I have run into is configuring my mail, sending to my webbased mail is not working I have opened port 25 through my router and verified my dyndns address after opening and configuring httpd on 80 but cannot send mail outside of my system. Thanks for any help.

shane


sorry dropped in the wrong thread

Last edited by swaid06; 01-27-2008 at 11:49 AM.
 
Old 02-18-2008, 10:22 AM   #549
alpha_hack
Member
 
Registered: Jul 2007
Location: Sofia, Bulgaria
Distribution: Slackware 13.1x86_64
Posts: 75

Rep: Reputation: 15
Hi there,
Although I'm not a newbie, I did read all of the information written here and I think it's really useful for all of us ! I really want to thank you for sharing this with us. I strongly recommend this tutorial to all of the newbies. It will not teach you what exactly will happen when you start but it will provide you with strong information what to do




Btw I once had a pc that had that annoying "beep" sound. It was a real pain in the ass until I found myself ( after 2 days of searching ) !

Last edited by alpha_hack; 08-04-2008 at 12:24 PM.
 
Old 03-12-2008, 02:55 PM   #550
InF3sted
Member
 
Registered: Mar 2005
Location: Belgrade
Distribution: Slackware 12.2
Posts: 30

Rep: Reputation: 15
very nice
 
Old 03-20-2008, 07:50 AM   #551
yifan04
LQ Newbie
 
Registered: Nov 2007
Posts: 1

Rep: Reputation: 0
You're doing the community a great service,
and if I hadn't already run into these headaches you would've saved me WEEKS.
thanks ALOT!
 
Old 05-13-2008, 01:50 PM   #552
The GNUinator
Member
 
Registered: Oct 2006
Location: Fort Collins, CO
Distribution: Slackware 14.0, 14.1
Posts: 71

Rep: Reputation: 15
Quote:
Originally Posted by rworkman View Post
To be honest, I'm not very familiar with swaret, so I'm certainly not a definitive source for information on it.
I've recently written a short document about third party package management on SlackWiki.org - have a look at this and see if it addresses your concerns adequately: http://slackwiki.org/Third_Party_Package_Managers
Hello,

I read your Wiki page and thanks for that. I've been using
slackupdate.sh from DarkLinux for years with almost 100%
good results. The one time it didn't work correctly was
a kernel upgrade on Slackware 12.0 which upgraded kernel-2.6.21.5-smp to kernel-2.6.21.5-smp_Slack12.0 and this broke my madwifi package
so that my Dlink-DWL650 Atheros based 802.11g wireless card
would not work anymore. The error was 'can't find kernel-modules'
and the solution was to go back to the previous kernel and
reinstall the madwifi package. That said, my one experience
with swaret was bad, though in fairness I wasn't familiar enough
with it to use it correctly.

On your Wiki Page you commented about third party package
management using non-official sources. Good point. But
using slackupdate.sh from DarkLinux I notice that packages
always come from official sources though if you messed
around with it enough you could break it!

Again, thanks for the Wiki Page.

The GNUinator
 
Old 05-13-2008, 02:03 PM   #553
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,543

Rep: Reputation: 1206Reputation: 1206Reputation: 1206Reputation: 1206Reputation: 1206Reputation: 1206Reputation: 1206Reputation: 1206Reputation: 1206
Quote:
Originally Posted by The GNUinator View Post
I read your Wiki page and thanks for that. I've been using
slackupdate.sh from DarkLinux for years with almost 100%
good results. The one time it didn't work correctly was
a kernel upgrade on Slackware 12.0 which upgraded kernel-2.6.21.5-smp to kernel-2.6.21.5-smp_Slack12.0 and this broke my madwifi package
so that my Dlink-DWL650 Atheros based 802.11g wireless card
would not work anymore. The error was 'can't find kernel-modules'
and the solution was to go back to the previous kernel and
reinstall the madwifi package.

The *real* solution was to just recompile madwifi.
The kernel upgrade was to fix a local root hole, so if you've got any untrusted users on your system, you *need* that upgraded kernel package set.
 
Old 05-15-2008, 01:19 PM   #554
The GNUinator
Member
 
Registered: Oct 2006
Location: Fort Collins, CO
Distribution: Slackware 14.0, 14.1
Posts: 71

Rep: Reputation: 15
Quote:
Originally Posted by rworkman View Post
The *real* solution was to just recompile madwifi.
The kernel upgrade was to fix a local root hole, so if you've got any untrusted users on your system, you *need* that upgraded kernel package set.
Umm. Well, I'm the only person who ever uses my system and I hardly ever log in as root. I do connect at public wireless unencrypted networks like the public library. Would never cruise the Internet as the root user.

If it was important enough to patch this kernel why was it not important enough to release a kernel-modules-2.6.21.5_Slack12.0 ??? I assume that my system couldn't find its kernel-modules package because the names were slightly different. Am I correct?

Recompile madwifi? I got this as a precompiled package from a directory somewhere called alien. My track record in compiling from C sources is not wonderful. Example: programs from "Numerical Recipes in C" that compiled just fine in OS/2 with the gcc/emx C compiler and compiled just fine in Windoze98 with Borland's free command line c/c++ compiler routinely do not compile in Linux. I get tons of errors. My guess is that the compiler can't find its header files or that its C is not backwards compatible with Ansi C.

Anyway, for me the real solution is just to turn to Slackware 12.1 ... That should do it, don't you think?

The GNUinator
 
Old 05-15-2008, 01:29 PM   #555
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,543

Rep: Reputation: 1206Reputation: 1206Reputation: 1206Reputation: 1206Reputation: 1206Reputation: 1206Reputation: 1206Reputation: 1206Reputation: 1206
Quote:
Originally Posted by The GNUinator View Post
If it was important enough to patch this kernel why was it not important enough to release a kernel-modules-2.6.21.5_Slack12.0 ??? I assume that my system couldn't find its kernel-modules package because the names were slightly different. Am I correct?
No. The recompiled kernel image itself is still compatible with the in-tree modules, so there's no need to recompile them. For out-of-tree modules (like madwifi), all bets are off.

Quote:
Recompile madwifi? I got this as a precompiled package from a directory somewhere called alien.
That's Eric Hameleers -- alienBOB here on LQ, and alien at slackware.com. If he didn't push out a rebuild of the madwifi packages, then they still work with the new kernel too.

If that's the case, then I have no idea what happened on your system, but rest assured that it "just worked" for me and countless others.

Quote:
My track record in compiling from C sources is not wonderful. Example: programs from "Numerical Recipes in C" that compiled just fine in OS/2 with the gcc/emx C compiler and compiled just fine in Windoze98 with Borland's free command line c/c++ compiler routinely do not compile in Linux. I get tons of errors. My guess is that the compiler can't find its header files or that its C is not backwards compatible with Ansi C.
Without seeing the 'tons of errors' there's no good way to answer that, but I suspect you're missing part of the d/ package series.

Quote:
Anyway, for me the real solution is just to turn to Slackware 12.1 ... That should do it, don't you think?
Yep, 12.1 should work fine too.
 
  


Reply

Tags
kernel


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 11:07 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration