SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I use a lot of the programs avaialble via SlackBuilds and not sure what would break if I started building with the 13.37 scripts, or even how to go about doing so.
Do I just install Slackware current and pull the 13.37 scripts?
Yeah, this is something to consider I'll grant you. I recently upgraded from Slackware 13.137 to Slackware64 14RC4. Since I also changed architecture I couldn't reuse my non-official packages and everything had to be recompiled. For the most part it all went smoothly. The vast majority of things still compiled with the 13.37 scripts. Also some things didn't need to be compiled again anyway because there are now official packages that ship with Slackware. However I did have a few problems with a handful of packages. Some I could just tweak the build script slightly but I am still missing a few things. For example I haven't yet got gtksourceview to compile and I have other stuff that depends on that. I have been meaning to checkout the git master branch of SlackBuilds.org as I believe it has some updates in preparation for 14 but I just haven't got around to it and the stuff I am missing is not that important to me that I can't live without it.
If you don't have many third party packages you will probably be OK but it might be best to test building your favourite stuff in a virtual machine running current before you commit to the upgrade.
EDIT: Ok, I checked out master:
git clone git://slackbuilds.org/slackbuilds.git
and the updated gtksourceview SlackBuild compiles just fine! Hats off to the SBo admins, you are clearly doing a great job getting everything ready for Slackware 14!
Most SlackBuilds will work out of the box in -current. Some of those that don't work, will do if you upgrade the version of the package.
We have a list of untested or problematic builds here: http://www.slackbuilds.org/Checklist.txt . Everything that is not on that list will work in -current right now or will do in the very near future (unless it has been dropped or something). If you test or manage to make some of the software of the list work on Slackware RC, I guess the build maintainers will like to hear about how did you do it.
Last edited by BlackRider; 09-13-2012 at 09:22 AM.
@ruario: thank you, I will download and install 10.0.7esr when I can find it.
More information of Firefox ESR releases here. You can download the latest Firefox 10.0.X ESR binary here. You can either use this directly or repack it. One nice thing about the binary packages that Mozilla provide is that they are PGO. The binaries provided by most (all?) distros are not PGO, nor is this something a regular user is likely to do, or at least do well. As such the Mozilla provided binary versions are almost certainly faster.
I don't use Firefox for day to day browsing but it is handy for the occasional comparative test with Opera and so I wrote a script that I use for doing a binary repack of Firefox into Slackware format. Whilst my script is designed to fetch and install the latest stable (regular) release it can repack ESR releases as well by simply setting $VERSION to the version you want, e.g.
I am everyday Java developer and still keep my self far away from Java 7 - too buggy for my enterprise setups. Java 6 works very well and reccmmend it for desktops as well.
*Sigh* Wish I could, but there are always some programs that are so "up to date" that they refuse to play with anything but Oracle Java 7...
BTW, why do some developers feel compelled to use every latest dang feature. Now it's java, but I unfortunately am old enough to remember FORTRAN code breaking because someone had to use Watfor extensions, then Fortran 77 then 90.. and usually, as far as I can tell, the generic code that would still have worked on Fortran 66 would've have worked just as well. Keep your code generic if at all possible*, it makes it so much easier to migrate/port.
*exceptions to the rule noted
... and I suppose there are security concerns with keeping with the old java as well as going with the new java.
well about releasing slackware 14.0 I don't mind wait for some more months.
To get an stable and some what less buggy slackware dvd from slackstore.
If this get rushed slackware would become like debian.
not that debian is an bad distribution but much different from slackware.
slackware should be like it always have been. stable from the start,
until you fuck it up. not the other way around