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.
Just curious-- why do you need/want one? I'm running kernel 2.6.3 on 9.1 (as do you), I've installed KDE 3.2 (as have you) and Dropline Gnome is running 2.4.2. If I want to try GNOME 2.5, I can compile GARNOME, and all my "general" packages are updated to slackware-current.
So what's the use of a new version? As I said, I'm just curious.
I've been eyeing a new system and thinking about getting a bare bones dual Opteron64 system. Does anyone know what the time frame is for a 64 bit version of Slackware? Currently Gentoo, Suse, Mandrake and Red Hat have 64 bit versions.
I am very concern with the new release of Slackware because I don't have high speed internet connection. That's means I can't download hundreds of megabytes packages. I just upgrade my kernel and download security patch. That's all. I want to be in bleeding edge too. I want to upgrade my gnome and kde too just like you but bandwitch in my country is expensive. When the new Slackware is release, I can buy the cd and be in bleeding edge without internet connection. If I have a high speed internet connection, I don't care with the release of new Slackware. Just like you.
Last edited by melinda_sayang; 03-03-2004 at 09:07 AM.
If you have Broadband, download a Current-Iso and swaret, suscribe to
To receive notification of changes to the Slackware -Current ChangeLog via email, send an email to "firstname.lastname@example.org" with the subject "subscribe slacklog" and your email address in the body of the message
and if you think that the upgrade is worst, go for it =).. And you will be up-to-date.
I consider that's the best way to be "updated", if you don't have Broadband, ok, it's time to SlackDevBoys to get a 9.2 (with kernel2.4.25), because, Slack10 deserves the kernel2.6.x as default
i'm happy enough with the current slack. the last thing i want to do is put pressure on Patrick V. to keep pumping out "new" versions just because that's what red hat and mandrake do every few months. i'm sure a new release will be out when there's enough good reasons for it and when it's ready.
Work is being done on Slack on a continual basis, but as motub points out, if you're already on 2.6.3 and you're using KDE 3.2, then you are already ahead of the curve. Assuming that you continue to install the latest and greatest kernels, I would expect that whenever the next release of Slack comes out, the kernel version may be a step backwards for you - you would probably already be using a newer one than the one that gets included in the release. Similarly that would also probably hold true for the various other packages in the release.
If there are specific packages that you want to upgrade, then www.linuxpackages.net is an excellent resource to stay on that leading edge. -- J.W,
melinda, I feel for you, but there might be alternatives to waiting for a new version.
Do you know anyone with high-speed access and a CD burner? Buy them a blank CD-R or two and make them some cookies (or dinner, or do something nice for them) and ask them to download the kernel, and whatever packages you want and burn them to disk for you.
Is it possible to download the packages and burn a CD at an Internet cafe? (I don't know since I've never been in one, but surely they give you some way to save a file). Or at a library?
Do you or someone you know go to school at or work at a place with such access? If you don't have access to a CD burner, it might be worth it to invest in a USB pen drive. Slackpacks are pretty small-- you can fit a lot of them on. This would also work at the Internet cafe, I would think.
Just a couple of ideas, hope they help.
As for Nigel and the Opteron system-- does anything need to be 64-bit other than the kernel? Aside from the fact that both the Mandrake and SuSE offerings are server products (at least I don't see any ISO's for the AMD Opteron version of Mandrake 9.0 announced last year), I'm not sure what the benefits would be of a "64-bit Slackware release" (as opposed to using a kernel that supports 64-bit processors, which you can already do), if the applications were not themselves 64-bit (which they are not, and which is not under Patrick's control in any case).
I suppose that you could recompile everything with 64-bit optimizations turned on (if that would actually help anything), but in that case you might just as well be running LFS or Gentoo anyway.
Am I simply missing the point of having such a system at this time? (Quite possible).
Originally posted by motub Just curious-- why do you need/want one? I'm running kernel 2.6.3 on 9.1 (as do you), I've installed KDE 3.2 (as have you) and Dropline Gnome is running 2.4.2. If I want to try GNOME 2.5, I can compile GARNOME, and all my "general" packages are updated to slackware-current.
So what's the use of a new version? As I said, I'm just curious.
I have all the updated packegse running as well and i am current, i was just curious to see if anyone knew if they were really rushing the new version or are they developing more for alote better version(not that i think it needs to get better) , say instead of 9.2 they hit ver 10 , i should have been more specific with my Question sorry.
I've been looking forward to a new release as well. Some people, like myself, are not ready for manual kernel upgrades. I've tried a couple of times with SuSE and failed so far. Besides, having that most recent version on CD is very handy...each time you install on a new system, having to go through the update process is annoying when compared with simply installing a few additional tools, particularly when you don't have broadband in your area.
Originally posted by mikshaw I've been looking forward to a new release as well. Some people, like myself, are not ready for manual kernel upgrades. I've tried a couple of times with SuSE and failed so far.
so it's a good time to compile your first kernel, while you wait for the new release.
For the moment I can't figure out wut advandtage 64 micros will bring to OS/Linux if u don't do many intensive numeric calculation, oh yeah maybe for heating the room temperature on winter. , their price is also skying .., might not be of mayor interest of freaks..
I'd prefer seeing customization perfection rather than support for 64 bit, maybe bzip2 oriented packages(bzip2 CL-options seemed too compatible with gzip so far I know ?), and better services managements??
I figured out that "rpc.portmap" started twice in /etc/rc.d/rc.inet2 when there is any keyword "nfs" in /etc/fstab. When "/etc/rc.d/rc.nfsd stop" is executed there are still few processed which was started by him not terminated "..quota .. lock ..".
I'm missing kinda elegant way to manage config file for saying which services to start or not at boot time rather than chmod 644 or 755 of rc.xyz .. Say "for service in <<read from services-file.in>> do $service start, if that is possible ..
Inetd-stuff can be slowly drop into /pasture, stand alone services mode will reduce security holes and make slack slimer, perhaps some old applications COULD also go into pasture without reducing the workability. Pasture + kde + gnome <<go into the 2nd CD>>, open-motif can into xap
Yea, I can't wait for a new version as well. I upgrade everything and recompile CVS kernels every 2 weeks or so. I just want to send Slack some cash is all. Already bought t-shirts hats and books from the store. Man, I'm such a geek..... I do like the hat tho..... If I had a car, I would buy a bumpersticker for it....