Nobody here had anything off topic to say, until you asked for help, bitched and moaned and never followed instructions. At least 4 different and correct answers were handed to you, free of charge, and even after your outbursts and attacks (which many people would take as personal) you were still given answers. You repeatedly chose to blame "this Volkerding guy" for your inablility to follow directions. It's too bad. You could have learned something, or at least gotten the results you were supposedly seeking. Instead you made yourself once again look "poorly". I always wonder with people like you, is anything ever your fault and does the world ever stop attacking you? Your own attitude and words have made you feel outcast, not some imaginary clique. Have a nice day. Thanks for the fish.

Hi guys, but haven't you pointed him to a 32bit version while OP says it's "Slackware v13-64"?

Where did OP say that?

Oh, post #73, wow that's a long thread.

I'm a bit lazy about pumping all those files on my system, so I converted them from rpm to tgz, removed userland, onlineupdate, gnome-integration, jre and menus except freedesktop, downloaded my language pack, unpacked all the tgz files, made a custom merged doinst and built a huge install. A dirty hack, but worked.

Try rlworkman's Ooo release (http://rlworkman.net/pkgs/). Slackware is a nice system and 13 was a *great* release. Keep an eye on next 13.x incarnation, as it'll be the finest out there...

Attached Files

doinst.sh.txt (21.2 KB, 24 views)

Better late than never: post 73.
Or maybe it's just my assumption - not very clearly stated that it really is 64bit installation.

Yeah that's a long way to give the arch. Sbopkg would have done everything on it's own, as would reading the instructions at SBo. Prebuilt packages would have failed.

First of all, it *does* appear that some misinformation was given. When I posted I read back to the first post and saw a mention of Slackware13, and no mention of x86_64. Indeed after searching it does appear that your first mention of Slackware64-13.0 (the correct title) was much later and I obviously missed it. I do apologize for pointing you to 32-bit packages, but had you posted any error that you received in a terminal to help us understand *why* it isn't working, the thread would not have derailed like it has. You failed to mention that you were using a 64-bit OS until halfway through this (long) thread, and that certainly contributed to your failure in getting OOo to work. As did the lack of any real information as to *what* was failing. If you run a 32-bit application in a 64-bit OS it will print out a very predictable error message that we could have caught.

I have never claimed to be God's gift to Linux, and in fact I think I am certainly one of the less knowledgable on this site. However, it is annoying to spend my free time writing a very detailed post with exact instructions on how to use a SlackBuild only to have it annotated with notes that confuse you and me, so no one really knows what happened. I also literally do not know what you have done, at all, since it seems you have not posted *exact* detailed instructions as to what you have done anywhere, or followed anyone's post to the letter. I am no juvenile and if you browse my many posts on these forums (note that there is a relatively large break in posts in there somewhere) I try to help and nothing more.

It's incredible that you can deduce so much about a person only by seeing their posts online. I know I tend to verbally harass people every day of my life. I shout "TROLL!" at passersby, otherwise minding their own business.

There are *so* many resources available to learn Linux and Slackware, but it seems by using other distros without getting your hands dirty you haven't learned enough to just jump in without reading. Slackware was my first distro and I read a *lot*. I never had a problem. That's not me touting my superiority, that's me suggesting that you go read the SlackBook if you really want to learn Linux principles and how they apply to Slackware in particular.

Money-hungry merchant? Did you pay for Slackware? Though it is available for sale I get the feeling that it wasn't purchased in the instance. Regardless, Slackware has its own unique philosophies, and just because *YOU* don't like it doesn't mean Slackware itself is at fault. I am running Slackware64-13 right now with currently no issues whatsoever. In fact, I recently migrated from one 64-bit PC to another. I swapped the hard drives and my LUKS-encrypted LVM is still kicking it. Slackware works -- if you know what you're doing. Slackware is incredibly 'simple' but not necessarily easy. The simplicity makes for a stable and fast distro where not much goes wrong -- if you know what you're doing.

Perhaps you should read the kernel mailing lists and see what Torvalds himself says to the Linux community. He is far harsher than any of us here. The open source community is filled with egomaniacs and is not as friendly as some would try to make it appear. However, if you view other threads here, this is a generally friendly community, as long as people give us the information we need without pulling teeth. This is entirely volunteered time, and those that seem to 'expect' help while bashing the distro and its users don't make volunteers want to work very hard, or be very nice. Despite my tone I have written multiple detailed posts here in this thread, none of which were followed properly. The information was sadly incorrect (the principles are the same but you need a 64-bit OOo package), but help from both sides makes everything easier.

2 members found this post helpful.

I apologize for the double post, but I felt it was best to separate my responses from my advice. This post has been corrected for Slackware64-13.0. Run the following commands as root:

Then do EXACTLY the following.

All as root, please. Post the output of any commands. The top two wget commands grab the actual OpenOffice package, already built for you, along with the md5sum. An md5sum is a calculated hash that allows you to verify that the download was not corrupt -- if the download was corrupt, the md5sum command will fail (and tell you so) and the package will not be installed. That complex line up there calculates the md5sum of the file (this may take a little while) and, if correct, installs the package. Otherwise it will tell you that the checksum did NOT match and it will not install the package. If this occurs, you would have to redownload the file. Do not worry about comparing the filesize of this new file to the filesize of the old file -- if the download was indeed corrupt, then it will not install anyway because the checksum will not match.

I wish you good luck and highly recommend reading the SlackBook or another Linux/Slackware resource.

1 members found this post helpful.

Most of the times it is difficult for an OP to properly describe problems in the OP. And that's why we should ask the right questions to ensure we understand the problem before trying to answer it. OTOH the OP should take care not to let frustration get in the way. Making remarks that have no bearing on the topic and blindly retaliating does nothing to get help from others, especially by those that offered constructive, helpful remarks before in the thread. Finally calling somebody a troll once should be enough for others that read the thread properly TTB to get the point. Twice or more by one or more people is excessive and does not help deal with the problem.

http://www.linuxquestions.org/questi...hreadid=798589 contains the fat that remains after performing liposuction on this thread. While making OT remarks is not a direct violation of the LQ Rules excessive use of it will impact the good atmosphere we believe is necessary. This goes of course for the OP as well as for anyone who replies. 15 percent fat is stretching it, hence the liposuction.

* This thread remains closed for the coming few hours to let things sink in a bit. After reopening it would be good to keep responses limited to helping fix the problem. The OP is also urged to post only exact commands and (error) output that help efficient troubleshooting.


TIA all for helping make and keep LQ a friendly place to be.

2 members found this post helpful.