Yeah I know this sounds totally stupid, however I can't figure this one out...

I installed the linux-pack, a .tgz file from the slackware packages site and I find it in /var/log/Packages, as well as /usr/bin/ , so it looks installed, I never recieved an error, I rebooted, I can not find anything about this program anywhere else , I searched for linux-pack and tried to run each one in these directories, no luck. Anyone know how I can get it to run?

what is the package name?
If the executable (binary) file has been copied to /usr/bin. You can execute the file from anywhere in the system. Meaning, at any working directory. Just key the prog name such as:
root@s9:/#xvidtune

the file name is linux-pack
the executable file name is linux-pack
I just now tried:
root@darkstar:~# linux-pack
I got in return: "segmentation fault"
so now I'm back to: root@darkstar:~#

that means the program did execute. and "segmentation fault" is the error it generate when the program was executed. I can't help you with that.

But I would think segmentation fault has to do with the memory Just a guess, probably there is a lot of other things that is involved.

Anyway, try reboot your machine and see whether that helps. (Don't scorn me for this). Or if you don't want to reboot, just run
init 1
init 3 (after you log in from init 1)

I could give you an in-depth description of a seg fault and its possible causes, but these guys probably do a better job. It's a good doc. Ignore the title, it goes way beyond that.

I just glanced at the top of that link. Actually, in this case it probably *is* a software problem. Unofficial slackpacks aren't guaranteed and may have been put together wrong. And it may have been put together right but for a different version of Slack. I wouldn't bother with rebooting. Make sure the thing is for 9.1 first off, and maybe try compiling it yourself, either way. I forget what it was but I had a tgz do something funky but compiled it with no problems.

Is the app a root-type app? 'root@darkstar'? It's usually 'user@mybox'.

If you get segfaults regularly, it'd be different but if this was a freak thing it's probaly just the package and there's probably not a lot to do about it.

Oh yeah - and I think there's a link at the site for reporting issues with packages. Maybe drop 'em a line.

It is absoloutely no problem at all for me to reboot, so I did a couple times, same thing, I have never recieved a message like that one before, I did make sure it was for Slackware 9.1, I however have not tried to recompile, actually I was dreading that because I've only been able to get one program to actually compile and install. It was on Slackware 8.1, Since then I've tried Mandrake & Redhat, I learned a lot, the biggest thing I learned that thier is no substitute for Slackware, everything actually works the way it is supposed to, however I realize that sometimes I don't! The documentation just sucks for a beginner, But I have learned to get the documentation I need for the most part, and now as long as I spend time learning, Slackware continues impressing me more and more. Anyway I will try to rebuild this program and install. It seems to me that if I configure it , make & make install, everything should optimized for my system. Unlike any other distro out there I've never yet run into dependency of dependency of dependency hell yet!

digiot, I don't understand what you mean by root type app, It is my understanding that as root I can do anything, can root not run some apps?
I just never heard of that before, please explain.

and carboncopy, I am not advanced enough yet to have a clue as to what you are talking about when you say to login init, I just never saw that yet, Please take it easy I am only 1-year into running linux and still feel like a total newbie, in other words I feel there isn't much I do know yet!

I think what digiot meant by root type app, it that you need root permission only to run the app. Usually you don't mess around with your system with root account as it is very very dangerous. Anyway, living on the edge is fun. I always use root all the time.

As for init stuff, init 1 will bring your system to single user mode. and init 3 will bring back the system to multi user mode. When your system you bring your system down to init level 1, it will kill most of the processes and daemons and when you bring it back to init level 3 it initialises all the processes and daemons which happens during bootup. All this happen without reloading the kernel.

just skimming through the post, don't yell if i say something unrelated to this post or if it has already been stated:

just download source files for the program you're trying to install; they look scary but are normally easier to get working, though it just does not look pretty when u do make

download the source; untar, then cd into the directory in a terminal and do ./configure, then do make, then make install
(this is just the generic way of installing, check the readme or install file for more info)

Thanks Carboncopy, that is very interesting information, I'll have to play with that a bit...


Well, like I said, I'm learning all the time, I'll uninstall it then download source and try that, thanks...