LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
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-20-2007, 08:04 PM   #1
dizzi
Member
 
Registered: Jun 2004
Location: Yorkshire, UK
Distribution: Slackware, Mepis LiveCD
Posts: 146

Rep: Reputation: 15
Modifying and repackaging Slackware package


Hi

I would like to install a Slack Pack which apparently was compiled for the 2.6.17.13 kernel. However I am running kernel 2.6.20. This should not normally be an issue but when I unpacked the archive to view the contents before installing, I noticed a "..../lib/modules/2.6.17.13/kernel/drivers/net/wireless" folder structure. Since I am running kernel 2.6.20 my structure would show this value rather the the 2.6.17.13. My question is, is it possible to unpack and modify the package to change the name of the 2.6.17.13 directory to 2.6.20 and have the entire archive repackaged into a genuine Slack Pack?

Cheers
 
Old 05-20-2007, 08:21 PM   #2
Eternal_Newbie
Member
 
Registered: Jun 2005
Location: The Pudding Isles
Distribution: Slackware 13.37
Posts: 573

Rep: Reputation: 59
What is the package? It sounds like a kernel module of some sort. If that is the case it will need to be recompiled for your present kernel. With any luck the package will include a slackbuild script. If it does, extract the slackbuild script, obtain the source and run the script and you should have a package built against your kernel. Full instructions for using slackbuilds are here at slackbuilds.org
 
Old 05-20-2007, 08:22 PM   #3
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,379

Rep: Reputation: Disabled
No.
A precompiled package with a kernel module inside can not be used on another kernel.
You can re-build the package using the sources however, and create a kernel module for your version of the kernel.
What package are you referring to by the way?

Eric
 
Old 05-20-2007, 08:25 PM   #4
rigelan
Member
 
Registered: Jul 2005
Location: Iowa
Distribution: Slackware
Posts: 173

Rep: Reputation: 19
Yeah, just untar it in a test directory that has nothing else in it. And then make your change, go to the base directory of your test, and as root "makepkg foo.tgz"

But If it is just a directory structure, you could also go to that directory and create a soft link from one directory to the other: ln -s 2.6.17.13 2.6.20.

But now I look at where it is installed: Kernel modules from one version do not work with kernels of a different version number, so I don't think your 2.6.17.13 module that it is placing in there will actually work.
 
Old 05-20-2007, 08:30 PM   #5
dizzi
Member
 
Registered: Jun 2004
Location: Yorkshire, UK
Distribution: Slackware, Mepis LiveCD
Posts: 146

Original Poster
Rep: Reputation: 15
Hi guys

Thanks for all the informative responses. For the record the package is: ipw3945-1.2.0_2.6.17.13-i486-1.tgz. So based on the advice here its strictly for 2.6.17.13 then.

Cheers
 
Old 05-20-2007, 08:43 PM   #6
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 1,807

Rep: Reputation: 234Reputation: 234Reputation: 234
Quote:
Originally Posted by dizzi
So based on the advice here its strictly for 2.6.17.13 then.
Yes, but Alien Bob has made it easy for you.

You can download all the files from here:

http://www.slackware.com/~alien/slac...ipw3945/build/

and run the SlackBuild script to create a new package for your kernel version.
 
Old 05-20-2007, 09:02 PM   #7
dizzi
Member
 
Registered: Jun 2004
Location: Yorkshire, UK
Distribution: Slackware, Mepis LiveCD
Posts: 146

Original Poster
Rep: Reputation: 15
Smile

Excellent, although I am completely clueless about the "SlackBuild" bit. However Eternal_Newbie has been good enough to post a link which I hope will clear things up.

Cheers

Last edited by dizzi; 05-20-2007 at 09:04 PM.
 
Old 05-20-2007, 09:35 PM   #8
slimm609
Member
 
Registered: May 2007
Location: Chas, SC
Distribution: slackware, gentoo, fedora, LFS, sidewinder G2, solaris, FreeBSD, RHEL, SUSE, Backtrack
Posts: 428

Rep: Reputation: 65
dont forget the slack tools that help with this stuff.


install slacktrack from /extra on the site.

also look at explodepkg, makepkg, etc.
 
  


Reply


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


Similar Threads
Thread Thread Starter Forum Replies Last Post
using older slackware package for newer slackware. Is it problematic? hottdogg Slackware 2 12-13-2005 04:57 AM
modifying permissions in slackware noxious Slackware 3 09-09-2004 10:45 PM
Slackware Package???? epihammer Slackware 13 07-03-2004 10:24 AM
repackaging the mandrake 9.2 isos Pete Dogg Mandriva 3 12-02-2003 08:27 PM
modifying slackware monkeymartin Slackware 4 07-15-2003 03:32 AM


All times are GMT -5. The time now is 06:39 PM.

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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration