Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
|
04-22-2014, 02:45 PM
|
#1
|
Senior Member
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 4,442
Rep:
|
What if I use installpkg with .xz packages?
Hi: installpkg makes no objections when given a .xz packages. Does it manage them correctly? It would be more logical that xz understands and correctly manages .tgz packages, which is my second question.
Last edited by stf92; 04-22-2014 at 02:48 PM.
|
|
|
04-22-2014, 03:36 PM
|
#2
|
Member
Registered: Dec 2013
Location: Turin, Italy
Distribution: slackware
Posts: 328
Rep:
|
xz/lzma is the current compression for slackware packages (obviously not all, like xz pakcage itself)
take a look at /sbin/installpkg, there is a case construct to determine which compression utility should be used: tgz/gzip, tbz/bzip2, tlz/lzma, txz/xz; for other extensions, installpkg will refuse to operate on the package
|
|
|
04-22-2014, 03:48 PM
|
#3
|
LQ Addict
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,210
Rep:
|
installpkg is very versatile and can handle several package compression methods, as shows this code snippet:
Code:
case $packageext in
'tgz' )
packagecompression=gzip
;;
'tbz' )
packagecompression=bzip2
;;
'tlz' )
packagecompression=lzma
;;
'txz' )
packagecompression=xz
;;
esac
All compression utilities listed honor the " -dc" option and of course should be present.
Last edited by Didier Spaier; 04-22-2014 at 03:53 PM.
|
|
|
04-22-2014, 03:58 PM
|
#4
|
Senior Member
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 4,442
Original Poster
Rep:
|
Well,
Code:
root@local:/mnt/cd0/slackware/a# installpkg -warn lilo-23.2-i486-3.txz
#### Scanning the contents of lilo-23.2-i486-3.txz...
The following files will be overwritten when installing this package.
Be sure they aren't important before you install this package:
gzip: stdin: not in gzip format
tar-1.13: Child returned status 1
tar-1.13: Error exit delayed from previous errors
root@local:/mnt/cd0/slackware/a#
this is because this is installpg from slackware 12.0. But using that from 14.0 installpkg did not complain. And based on what Didier posted, I take it is perfectly correct to install a .txz package with the new installpkg. Am I right?
|
|
|
04-22-2014, 04:19 PM
|
#5
|
Senior Member
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 2,557
|
You can change the compression as follows:
Code:
xzdec lilo-23.2-i486-3.txz | gzip > lilo-23.2-i486-3.tgz
Assuming you use Slackware 14.0 or locally compile xzdec.
P.S. Generally it is not a great idea to install packages intended for 14.0 in an older version.
Last edited by ruario; 04-22-2014 at 04:48 PM.
Reason: added shelr.tv link
|
|
|
04-22-2014, 04:21 PM
|
#6
|
LQ Addict
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,210
Rep:
|
What I wrote in my previous post stands for Slackware 14.0. Back in 2007 when Slackware 12.0 was released installpkg only dealt with gzip.
Furthermore why would you use installpkg from 12.0 to install a package intended for a later release?
PS I didn't see ruario's answer before posting but if you aim was actually to upgrade lilo on 12.0 (maybe because old lilos can't install new kernels as too big), then you should build yourself a newer lilo package on Slackware 12.0.
In any case if you're still using Slackware 12.0 I suggest that you upgrade as this version is no more maintained, so possible security holes will remain open.
Last edited by Didier Spaier; 04-22-2014 at 04:38 PM.
|
|
|
04-22-2014, 04:40 PM
|
#7
|
Senior Member
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 2,557
|
You may well already know this but in case you don't, Slackware 12.0 has been end of lifed and does not receive security updates (since the 27th of July 2012).
|
|
|
04-22-2014, 04:46 PM
|
#8
|
Senior Member
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 2,557
|
Quote:
Originally Posted by stf92
I take it is perfectly correct to install a .txz package with the new installpkg. Am I right?
|
It is fine to install .txz packages on Modern Slackware but not on 12.0.
|
|
|
04-22-2014, 04:49 PM
|
#9
|
Moderator
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,148
|
Quote:
Originally Posted by stf92
Hi: installpkg makes no objections when given a .xz packages. Does it manage them correctly? It would be more logical that xz understands and correctly manages .tgz packages, which is my second question.
|
Not only can pkgtools handle .txz packages, since version 13.0 xz-compression is the default for Slackware packages.
|
|
|
04-22-2014, 05:18 PM
|
#10
|
Senior Member
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 4,442
Original Poster
Rep:
|
Quote:
Originally Posted by Didier Spaier
(maybe because old lilos can't install new kernels as too big)
|
That is precisely the case. When giving lilo the path to the kernel image for the Debian 7.4 kernel, he complain: ""Fatal: Setup length exceeds 31 muximum; kernel setup will overwrite boot loader" (I opened a thread about this). To solve the issue in the old lilo, I booted from the slackware 14.0 disk, and let the installer to proceed as if installing in an empty hard disk. I got the prompt, and not finding lilo (every candidate path was in $PATH but 'lilo' got 'Command not found') I went to /slackware/a/ and ran installpkg on the lilo package. However, when I ran this lilo, I got "Fatal: trying to map files from unnamed device 0x001". What I am now doing is to install 14.0. In an hour I will be running lilo under 14.0 installed on the hard and will see what happens.
|
|
|
04-23-2014, 04:03 AM
|
#11
|
Senior Member
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 2,557
|
Quote:
Originally Posted by ruario
Generally it is not a great idea to install packages intended for 14.0 in an older version.
|
To continue on from this point, if you had really wanted to stick with Slackware 12.0 for some reason (even though it no longer receives security updates). The correct thing to do would have been to rebuild a more recent Lilo on 12.0 itself. This could be achieved as follows.
Fetch and unpack the Lilo source and SlackBuild files to a suitable directory:
Code:
$ mkdir -p /tmp/staging
$ cd /tmp/staging
$ lftp -c 'open http://mirrors.slackware.com/slackware/slackware-14.1/source/a/; mirror -x ".*\.mirrorlist" lilo'
Tweak lilo.SlackBuild to produce an .tgz package instead of a .txz package:
Code:
$ sed -i '/makepkg/s/txz$/tgz/' /tmp/staging/lilo/lilo.SlackBuild
Switch to root and run the SlackBuild:
Code:
$ su -
# cd /tmp/staging/lilo
# sh lilo.SlackBuild
Upgrade Lilo:
Code:
# upgradepkg /tmp/lilo-24.0-i486-4.tgz
If you have now decided to move to a more recent Slackware instead, why not go directly to 14.1 so that support lasts as long as possible.
Last edited by ruario; 04-23-2014 at 04:13 AM.
Reason: spelling; removed redundant mirror options
|
|
|
04-23-2014, 12:26 PM
|
#12
|
Senior Member
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 4,442
Original Poster
Rep:
|
Thank you for those instructions. I've been running 14.0 for a while now. But I don't like to change the OS as if it were the shirt. I observe that the trend is towards transforming the computer into a thing not unlike the television set, or a vacuum cleaner. A thing that can be comfortably operated by everybody. Things like USB and udev find their justification in the public acceptance, ease of use. But they introduce huge amounts of complexity. And why? So that my sister can plug in her camera into the computer and organize her pictures?
What about the common people like me? They have enormously complicated my life. To Hell with USB and udev and all unnecessary "improvements" whose only aim is to increase sales. To Hell with multimedia. To Hell with color itself and graphical user interfaces. The aim is to make computers controllable by an imbecile. But that which for an imbecile can be easy is infinitely complicated for me. I don't know why but it turns up to be so. I'm very sorry if this seems extemporaneous.
|
|
|
04-24-2014, 01:19 AM
|
#13
|
Amigo developer
Registered: Dec 2003
Location: Germany
Distribution: Slackware
Posts: 4,928
|
What sort of pacakges have the .tar.xz suffix?? The only thing I can think of is that you might be trying to install packages meant for archlinux -which is not a good idea.
|
|
|
04-24-2014, 01:37 AM
|
#14
|
MLED Founder
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,453
|
Quote:
Originally Posted by stf92
What about the common people like me? They have enormously complicated my life. To Hell with USB and udev and all unnecessary "improvements" whose only aim is to increase sales. To Hell with multimedia. To Hell with color itself and graphical user interfaces. The aim is to make computers controllable by an imbecile. But that which for an imbecile can be easy is infinitely complicated for me. I don't know why but it turns up to be so. I'm very sorry if this seems extemporaneous.
|
You might want to replace your PC by an abacus.
|
|
|
04-24-2014, 02:07 AM
|
#15
|
LQ Addict
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,210
Rep:
|
Quote:
Originally Posted by kikinovak
You might want to replace your PC by an abacus.
|
This reminds me of a trip I made to China back in 1988. I went to a currency exchange office to change US $ in renminbin yuans. A first employee took the dollars, used a pocket calculator to compute how many yuans I should get, then checked the result with an abacus. She then handed over her results to a second employee who gave me the yuans. Oh, and that was the last time I traveled in a steam train. Nostalgy...
Last edited by Didier Spaier; 04-24-2014 at 02:13 AM.
|
|
|
All times are GMT -5. The time now is 06:57 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|