SlackwareThis 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.
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.
Slackware isn't your everyday Linux distro and does things in a different way. Like JokerBoy said, use the SlackBuild script and it'll work. If you don't know how the SlackBuild scripts work then read the HowTo on the site SlackBuilds HowTo.
If it's just for one user you can also just put the .so file you have extracted in ~/.mozilla/plugins (create the folder if it's not there already)
I created .mozilla/plugins within /usr/lib and copied libflashplayer.so into /usr/lib/mozilla/plugins then restarted firefox and still nothing.
Apart from that it seems version 13 is a vast change to when I last used Slackware i think it was version 10 or 11. At that time I would just unzip then untar and run the script within the resulting folder.
I could even use repositories from slacky.eu then run it with slackpkg.
I wonder if the slack book is updated to these changes.?
Another thing i don't like about version 13 is the fact that the terminal prompt does not show the users current directory. No matter what directory i change in it keeps showing "bash-3.1$"
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Quote:
Another thing i don't like about version 13 is the fact that the terminal prompt does not show the users current directory. No matter what directory i change in it keeps showing "bash-3.1$"
I'm not sure what you mean here. If running bash in a console (from init 3) then the prompt should show user@host:current_directory. This is set in /etc/profile and will be operative for all bash login shells.
If you are talking about from an X session then konsole should act as a login shell and display the prompt as above. If you mean from Terminal in X then simply goto Edit->Preferences and check "Run command as login shell" and all Terminal sessions will honour the profile setting.
I created .mozilla/plugins within /usr/lib and copied libflashplayer.so into /usr/lib/mozilla/plugins then restarted firefox and still nothing.
I wasn't saying about putting anything in /usr/lib, I meant to put the file in your home directory, (so "/home/[your user name]/.mozilla/plugins", that's what "~/" means). Apologies for any confusion. The slackbuild is the "better" option anyway I guess.
@siawash: do you have a terminal window automatically loading when you login to your window manager/desktop environment? This has happened to me before in kde, if you open a new terminal (konsole in my case) it restores the normal behaviour
Another thing i don't like about version 13 is the fact that the terminal prompt does not show the users current directory. No matter what directory i change in it keeps showing "bash-3.1$"
Thank bgeddy, I just checked "Run as command as login shell" under terminal preferences and now am getting the typical terminal promt I am used to with other distros.
I now am left with three more important tasks. Namely learn about and use slack build to install
Flash player
Real player
And how to configure KDE to display a mounted CD Rom under the "Places" menu as was the case with earlier versions of KDE. My keyboard is also staying on the US configuration which means shift 2 is giving me an @ symbols as apposed ". I will leave these for a separate post.
Going back to the flash issue I have downloaded the slack.build which according to the tutorial, when extracted is supposed to show a tree thus:
Nowhere have i seen the file chemtools. Can anyone tell me if I am on the right track? Has the slackbook a comprehensive tutorial on slackbuild? If so, I will try to obtain it.
Can anyone confirm?
The method for using a slackbuild is as follows:
1) download the slackbuild .tar.gz
2) download the source tarball
3) extract the slackbuild
4) move the source tarball into the newly created directory
5) review the slackbuild
6) execute the slackbuild and install the created package with installpkg
So, in the case of the flash plugin go onto http://slackbuilds.org/repository/13...player-plugin/
1) download flash-player-plugin.tar.gz
2) download either the 32- or 64-bit package, depending on which one you are using
3) extract flash-player-plugin.tar.gz
4) put the package from step 2) in the new directory along with the extracted files
5) edit the slackbuild to your preferences - just change the ARCH variable to "x86_64" if you want to install the 64 bit plugin, everything else should be fine
6) run the slackbuild script and installpkg /tmp/"package name"
Thanks for that last tutorial. I think I followed your instructions as intended as you can see below. Maybe the my misunderstanding was that I did not extract
"libflashplayer-10.0.45.2.linux-x86_64.so.tar.gz" before placing it into the extracted slack.build. But this was not clear in your insturctions. Accordingly I amended the
executable "flash-player-plugin.SlackBuild" ARCH variable. I still don't have flash working.
siawacsh@slackware:~/Downloads/slack.build/flash-player-plugin$ ./flash-player-plugin.SlackBuild
libflashplayer.so
Slackware package maker, version 3.14159.
Searching for symbolic links:
No symbolic links were found, so we won't make an installation script.
You can make your own later in ./install/doinst.sh and rebuild the
package if you like.
This next step is optional - you can set the directories in your package
to some sane permissions. If any of the directories in your package have
special permissions, then DO NOT reset them here!
Would you like to reset all directory permissions to 755 (drwxr-xr-x) and
directory ownerships to root.root ([y]es, [n]o)? n
Creating Slackware package: /tmp/flash-player-plugin-10.0_r45-x86_64-1_SBo.tgz
./
install/
install/slack-desc
usr/
usr/lib64/
usr/lib64/mozilla/
usr/lib64/mozilla/plugins/
usr/lib64/mozilla/plugins/libflashplayer.so
usr/doc/
usr/doc/flash-player-plugin-10.0_r45/
usr/doc/flash-player-plugin-10.0_r45/flash-player-plugin.SlackBuild
Slackware package /tmp/flash-player-plugin-10.0_r45-x86_64-1_SBo.tgz created.
siawacsh@slackware:~/Downloads/slack.build/flash-player-plugin$
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.