whoops. double post
|
If distros = cars
-> Ubuntu, RedHat, Mandriva, and their derivatives = GM, Ford, Toyota, ...etc. Designed and built by committee. -> Slackware = kit car. Final assembly is left up to the end user. -> Gentoo = Auto parts mega warehouse. Has everything you need to build a car. -> LFS = Machine Shop. |
Quote:
Quote:
Quote:
Quote:
|
Quote:
Quote:
Quote:
--EDIT-- With optimized 2.6.27.7 kernel performance is similar to what I had with optimized 2.6.25.7. No other troubles so far. |
Quote:
On the other hand, I'll think about posting something generic that others could modify to their needs. That would help me improve the script for my own needs too. :) Quote:
|
Quote:
Quote:
Of course, that can be a pain for people with more selective installations like yours. Your next point makes a lot of sense: Quote:
Regards, -Drew |
Darn, double post.
|
I will restate a point that has been made in this forum many times before. The only supported Slackware system is the full install. When you start selectively dropping packages you are on your own. There can be unexpected consequences.
As an example, to try to create space on an old system running reiserfs, I tried deleting packages to do with ext3. Then I lost the output from the mount command, as the required library is part of the e2fsprogs package. |
Quote:
I remember also being able to use slackpkg to update from 12.1 to 12.2 (full ;) and everything was just fine. Quote:
I understood what you wanted it to do, install everything new except those packages that were already present on a default installation but wasn't in yours. It would be great if something like this was possible but the point here is: the tool does what is supposed to do. If we had some lists like a guy said back in posts would be just wonderful. |
Linux.com's 12.2 review is very positive.
|
Hi,
Quote:
|
Quote:
I, for one, am leaving Slackware after 3 years of using it and NEVER imagining me using something else. But it turns out I am sick of it. |
Quote:
Quote:
Quote:
|
My cautionary advice was given due to the fact that modern computer systems routinely have hard disk drives with excess capacity when compared to the size of the full Slackware install. If you have the disk space, then a full install will give you assured functionality. It is unrealistic to expect the Slackware maintainers to support anything other than a full install. They can make no assumptions about a users hardware, needs and level of experience.
For people running older systems, (including me!), then it can be advantageous to remove packages that are not required. I know that not loading KDE can save an enormous amount of space if you can conduct all necessary operations without that desktop environment, as I do with some lightweight gateway/fileservers. Further space can be be reclaimed by removing other functionality, such as development tools, editors, alternate web browsers and hardware specific packages. But each removal makes the setup less general and if taken too far can lead to a consequence like I described. Perhaps it is a bad example, but it is certainly a real example from my own experience. |
Quote:
|
All times are GMT -5. The time now is 12:02 AM. |