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.
Seriously, I went to upgrade from good old Slackware 9.1 to this new crappy 13.1 piece of dig turd!
1) Apparently, Slackware got into the trend of copying Microsoft Windows and now will only boot on the first primary partition, if i wanted to an external hard rive to keep the OS on, i can no longer do so, because I see the stock scripts have been changed somewhat, apparently we aren't supose to have anything but sda and hda for booting .... now I donno about you, but when i like to do builds of LFS I like to use an external drive as the OS and the internal drive were LFS lives, seeing how Slackware has magically decided to only boot of the first hard drive (even tho linux itself is capable of booting of any partition) I have been forced to sadly accept I need to change flavors of linux, because this is totally unacceptable, you wanna do what windows does, thats great, but not on my machine.
2) If compiz doesn't work the way it should (IE freezing at random) on 3 of my boxes with totally different hardware configurations, they why on earth is it even supported? Do we not like having stable machines? i know it's been a dream for some time to copy Windows, but really, I have been with Linux for 12 years, so if I wanted to go back to Win98 I could have, I don't need the lock ups, if I wanted them I'd Install DOS, Install Quick basic and write a short program to randomly call any interrupt (this freezes dos solid).
3) Pick a freaking start up script style, either choose sysv already or stick with BSD, using both is both annoying and redundant
4)Get your act together! Slackware's track record for breaking things is the worst i have ever seen, if it works, dont break it by introducing new things, keep them in current, thats why current exists! The stock Slackware 13.1 X86_64 has been nothing short of a nightmare, in fact it's so bad, I am going to fork LFS and start a new distro, that does everything Slackware apparently cant do, ie: everything slack 9.1 did, apparently this is rocket science! You know to keep the things that actually matter and ditch the graphical piece of crap? if they dont work oh well? I'd rather if the basics work then some GUI and all its crap that sits on top of all the important things.
Anyways, this will be the last time I post in the Slackware area of this forum, because i feel it is a waste of my time, anything said will just create my posts on why other thing in the future don't work, the whole idea of compatibility is to keep the feature you already have, and incorporate new ones, NOT cut out features and glue new ones over top
My experience of slackware 13.x and current on four machines (2xdesktop, laptop and netbook) is very different to that of the OP - all are running very smoothly.
If you really care about discussing your issues, don't tell us "anyways, this will be the last time I post in the Slackware area of this forum". There is no sense in posting what you just did, unless your intention was to troll.
An upgrade from Slackware 9.1 to 13.1 skips 7 years of development. Things change a lot in that amount of time. Many of those changes are quite intrusive and may be incompatible with "the good old ways of working". I would not even consider an upgrade between these versions but do a "from-scratch" installation of 13.1.
Of course Slackware still boots off other partitions than those present on the first drive. Of course compiz works, but may need configuration tweaks if the kernel and/or X.Org drivers for your hardware are hiccuping. What's your gripe with BSD versus SysV boot scripts? Slackware uses a hybrid mix, it is neither of those.
Slackware-current is not what you think it to be - it is not a "rolling release" like other distros have, it is merely the upfront to the next stable release. You don't like the new KDE? Then by all means feel free do de-install those packages! There is XFCE, fluxbox, blackbox, fvwm2 which may be more to your taste? Seeing that you were trying to use compiz means that you do care for the eye candy, but get infuriated when you can not get it to work reliably.
This forum exists to address the questions like you have, however if you do not want to discuss your issues until you are red in the face and steam is coming out of your ears, you leave us little room to help you, don't you think?
Feel free to tell us what you find working on Slackware 9.1 thet no longer works in Slackware 13.1... I am really interested.
And please! Do not try to keep stuck in the past - Linux distros have evolved, and Slackware is not a big player so it has to swallow what the big guys cook up. Not all changes are meant to bring stability in the short-term, only more features. This is unfortunate, and Slackware can not change anything about it other than stick in the past like you would have us. That would push it into oblivion at some point. Let's face it, you probably planned an upgrade from Slackware 9.1 because you needed something that was not present in that old version?
Awaiting your comments.
Eric
Last edited by Alien Bob; 02-27-2011 at 08:08 AM.
Reason: Syntax.
1) Apparently, Slackware got into the trend of copying Microsoft Windows and now will only boot on the first primary partition, if i wanted to an external hard rive to keep the OS on, i can no longer do so, because I see the stock scripts have been changed somewhat, apparently we aren't supose to have anything but sda and hda for booting .... now I donno about you, but when i like to do builds of LFS I like to use an external drive as the OS and the internal drive were LFS lives, seeing how Slackware has magically decided to only boot of the first hard drive (even tho linux itself is capable of booting of any partition) I have been forced to sadly accept I need to change flavors of linux, because this is totally unacceptable, you wanna do what windows does, thats great, but not on my machine.
To Alien Bob, Thank you for such a well thought out reply. I have a hard time believing english is not your first language : )
In my experience I have had less issues with Slackware breaking things than other distros. Also if you do not like the way things are done there are many more distros to choose from. This really just seems like a troll (IMO).
No one has seemed to answer the OP, so I will, I would suggest Slackware as a host, it comes with all dependency's and has an added bonus of being completely stock for the most part, so a LFS build should have no problems being done under Slackware.
Can anyone else recommend a host OS, instead of tell the user what version he/she should be using?
Please explain the reasoning for the above and what you have posted originally in this thread? You seem to vacillate or just trolling again? To recommend and then make such a poor rant now is nothing more than a vacillating troll to me.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.