I have Slackware 12.2 on a webserver and I need to install TCPD, but I don't know what package it's in. Does anyone know? I've tried searching online but that hasn't worked out too well.
We are pleased to present one of our new creations: pkgbuild, a tool written in standard C++, using libCURL, ZLib, BZip2 and libLZMA (part of XZ). It is a modern Slackware packages builder, network-transparent, multi-architecture, designed to greatly simplify the creation of a package, automatically executing the required post processing.
What does it do? Recognize and build packages for the following architectures: i386, i486, i586, i686, x86_64, IA64, IA32e, s390, s390x, sparc and sparc64.
I downloaded from http://ftp.nluug.nl/os/Linux/distr/s...ce/n/net-snmp/ source and I build new package and works ok no errors. If I change net-snmp.SlackBuild and add CFLAGS --with-mib-modules=ucd-snmp/lmSensors --with-ldflags=-lsensors while I need lmsensors support in net-snmp. But the package compiling ends with error:
I am very happy to announce that today I succeeded to install full Slackware ARM on the pandaboard: URL...I did the following:
* sd with 2 partitions, one (vfat) for bootloaders (MLO, u-boot.bin) and uImage and the other one (ext2) for minirootfs * copy xloader (MLO), uboot and uImage from Angstrom distro on the first partition * copy Slackware ARM minirootfs on the second partition with Angstrom modules in the usual path (/lib/modules/...) * boot in ARMedslack * install all the others packages via NFS
I had to make some changes to configuration files as indicated here:URL...The next step is to build a kernel and modules for omap4 by myself and use them instead of the Angstrom ones.One question: is there any kind of package manager, such as slap-get, sbopkg, etc. for Slackware ARM? If not, can I use the SlackBuilds from slackbuilds.org? How to modify them?
I found the source, but it's missing a few header files.I tried downloading a few but it wasn't working correctly.I'd rather install this package properly.
I'm elated when I see software download pages that include a binary Slackware package.wrt KVIrc, their Slackware package is at the top of their list of binaries.They've got an rpm too, but it's SuSE, not Redhat - I found that to be pretty kewl too.I wonder if they're Slackers... hm...Well, that having been said, there's also a SlackBuild for it at the repository.I'm going to give this client a spin and see how I like it.Here's the URL: http://www.kvirc.net/?id=releases&pl...=4.0.2&lang=enUPDATE: The mirrors I checked are reporting 404 errors... bummer.
I have slackware64-13.0 & xfce. I installed somebody's openoffice package ( a repackaging of the rpms), openoffice.org-3.2.0_en_US-x86_64-1_rlw.txz and ran into crazy keyboard issues, double inserts of random keys when I type faster than a snail's pace liikee tthiis. I had errors from xkbcomp rolling off the screen.
> Using last definition > Warning: Duplicate shape name "" > Using last definition > Warning: Duplicate shape name "" > Using last definition > Warning: Multiple doodads named ""
Theres a package I'm going to install that is available only in 32-bit, but I have its dependencies installed as regular 64-bit. Since I'm multilib, will the 32-bit package be able to work with the 64-bit deps? If not, can 32-bit versions of the deps be installed side by side with the 64 bit?
Running against a situation here, for which I have solutions in mind, but for some reason or another they don't really strike me as "good" solutions.
I am making a customized for myself (eg with postgreSQL support) php package. Configure and make run fine; but upon make install the make tries to access httpd.conf in the $DESTDIR/etc/httpd
My first thought is: prior to 'make install' copy the file from /etc/httpd to the target dir;
after hours of searching and trying, I could not determine which kde package contains the kde system-settings gui. I'm under Xfce and would like to make some changes for my remaining KDE apps.
I am a long-time Debian user (I use it since Woody) and yesterday, due to an unexpected problem on my hard drive and an inexplicable lack of a current Debian cd or a possibility to perform a net install, I had to choose between either stay without computer at home or install one of the two other operating systems I happened to have on cds: Free-BDS or Slackware 13.0. Since I do not have time to learn something that I consider to be more radically different from Debian, I went for Slack.
So, first impressions:
1. Quick and smooth installation, though I got a bit over-enthusiastic when it came to select packages to install and unselected many libraries that I later realised that were necessary for various packages and I had to install them anyway.
2. Configure my wifi was surprisingly easy. I had braced myself for overly-complicated configurations to be done while I'd not have access to google, however rc.inet1.conf was very straight-forward and it provided plenty of examples to illustrate basically every possible configuration. All I had to do was to copy my wpa_supplicant.conf from my Debian backup and it worked.
3.X: For some reason I expected I'd have trouble to properly install and configure X, however my window manager was up and running in a few minutes. I copied my ~/GNUstep folder from my backup gave me the exact same X environment I had in Debian.
4. Package managing and dependencies: (I think I am correct to presume that that has to be the main complaint of most Debian users). pkgtool is very easy to use but, yeah, it does not resolve dependencies.
However, and while I installed a system way more minimalistic than any Debian system I had, I was surprised to find out that:
-Firefox had only ONE dependency
-vlc had none
-xfe, on the other hand, has some obscure dependency that I cannot figure out where to get it (libGLU).
So, a question for more experienced Slackware users: How do you get around the dependencies? Is there a quick way to find out what additional packages you will need on beforehand, or you install the package and try to run it, so to see what libs you need when it fails to start?
I think there is a problem with the sox package that comes with Slackware 13.1.I would appreciate any advice. I'm using the same file, 1.wav, in both cases. The output of file 1.wav is1.wav: RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, stereo 44100 HzOn 12.1, I can runsox 1.wav -e stat 2> /tmp/stat.txt
I compiled php 5.2.17 from the source with php-fpm and I have the compiled package /tmp as you know the version of php is slackware 13.1 is the same (5.2.17 without php-fpm) . How could I update from from compiled package?
I mean like, what does it do differently from just installing something from source? Check to make sure you have the required dependencies before compiling the .tgz package? something else?
I have just made a clean installation of slackware 13.1 (Full installation from DVD)..At the time of installation , it prompted to create a bootable USB stick and I am able to boot using that
1.My BIOS is quite old and has the Cylinder 1024 problem..It just recognises 137 GB in a 160 GB drive...Most distros are able to read beyond the 137 GB ...Currently I am booting using GRUB 2 which was installed during Ububtu 10.10 install. As you are aware GRUB2 recognises all the OS in the drive automatically and adds them to the menu on "update-grub"...The slackware entry appears...However on selection I get the error - "error: out of Disk"...How to deal with this?
2. What is the default Package Manager for Slack? I read that Pkginstall is the default but doesnt update dependencies. I have salix (slack derivative) in another comp and I use "slapt-get"..Is it available in slackware?I want to install wireless driver ipw2100 (Intel pro wireless 2100 chipset) and get wireless up.. I can chroot from say Ubuntu and do the needful.
A slacky.eu user Spina, I did notice a bug in calculating the size of the package when the directory contains a space in the name. Example:
Code: /tmp/prova dir# LANG=en installpkg abook-0.6.0pre2-i686-4cf.txz /bin/du: cannot access `/tmp/prova': No such file or directory /bin/du: cannot access `dir/abook-0.6.0pre2-i686-4cf.txz': No such file or directory Verifying package abook-0.6.0pre2-i686-4cf.txz. Installing package abook-0.6.0pre2-i686-4cf.txz:
PACKAGE DESCRIPTION: # abook # Abook is a text-based addressbook program designed to use with mutt # mail client. Abook runs on Linux, FreeBSD and some other UNIXes. # Home: [URL] # Package abook-0.6.0pre2-i686-4cf.txz installed.
This error is caused by 'readlink -f' COMPRESSED="$(/bin/du -sh $(readlink -f $package) | cut -f 1)" instead with Code: COMPRESSED="$(/bin/du -sh "$(readlink -f $package)" | cut -f 1)" it's ok
Kernel 2.6.21.5, slackware 12.0I downloaded the file fasm-1.69.31.tgz from http://flatassembler.net. Just in case it was a slack binary package, I did 'installpkg fasm-1.69.31.tgz'. Then I found I now had /var/log/packages/fasm-1.69.31.
Want to install slackware current on BTX 915G, SouthLake2, 800mhz FSB, P4 3.20Ghz, GeForce 6600 for dedicated Desktop Publishing box as part of LAN. Is Slackware Network Package required or just a part of it to connect to LAN, scp, and Internet. Have servers in LAN don't want to waste 250gb HDD space. I'm thinking dhcpcd is client, inetd-1, openshh,ftp. What else? What does your experiences say?
I thought I knew what I was doing, just a minimal install of slackware 13.1 for a game server (minecraft), but it seems I missed java or something - I get the "command not found" error. gcc-java is installed. What package did I miss/what series is it in? Does it have any dependencies?
I upgraded to the latest -current just like always. I do the kernel packages last. This time, the machine failed to boot, telling me that it could not find the kernel modules. Well, rats.
I booted with a slackware dvd, passed the huge.s kernel, and booted into /dev/sda7, which is my main partition. I mounted /dev/sda7, and installed the kernel-modules-2.6.35.11 pkg. Rebooted, and got the same error?
I booted again with the dvd, mounted the partition, and navigated to /lib/modules - no 2.6.35.11 in there!