So, the ideal thing to do is a full install which is about 9 GB, then gradually remove 5.5 GB to get 3.5 GB? As oppose to starting with 2.5/3.5 GB and gradually adding only what you need? If that ain't the most bent logic I ever read, we'll all be going to hell in a hand basket. Man.... I'm about to teach my 2yr old son drugs are bad for you.

I dare to say 11GB on slackware-current, then after/when glorious Plasma 5 will be adopted, I safely bet to be 12GB if not even more.

---------------------------------------------------

Regarding of previous post, of @bamunds, what I want to gain is something which cannot be obtained with removing KDE and KDEI series via PKGTOOL.

Again, what I intend is simply just to continue to use KDE4, which I prefer, after/when the glorious Plasma 5 will be adopted.

For this, I will need to "sacrifice" any Plasma 5 dependencies which eventually will arrive in our L series (i.e. Qt5, KDE Frameworks, and so on) because I strongly suspect them to conflict with those of KDE4, it is nothing personal.

That's WHY I try to find a solution for others to not be affected, also myself to NOT WORK hundred times more, to hunt down those Plasma 5 dependencies.

And I have also the solution: a separate package series for them, called KDEL or QT or whatever, selected by default in installed, for the lazy guys.

BUT, those like who does NOT want to install and use Plasma 5 but something else (XFCE, KDE4, even FVWM95), will know well what they have to do.

---------------------------------------------------

In other hand, I completely disagree with idea that customizing your Slackware installation (i.e. removing KDE and any of its own dependencies) you obtain a derivative distribution and it is NOT Slackware anymore...

Then, in this case, what is the sense to use binary packages in Slackware?

How about Patrick Volkerding to ship instead a huge tarball containing everything? This way will be FULL INSTALL FOREVER!

4 members found this post helpful.

Every time I click on "View Latest Posts",

Oooops, sorry, I accidentally released my 'mute' button!!!
I'll press it immediately, and delete:wink: this post. Bye.

Edit: p.s.: yes, I do need to: go learn the 98% Idk, before I mumblespeak to ZRT!!!
Pls upload SlackVdi to osboxes. I've only 8minutes&9mouseclicks to test this thread

1 members found this post helpful.

Amen Darth. I wonder what my windows become since it's all modded up? Watch the agenda being push here. No matter what you say, it's all about a full installl regardless if that's not even the scope of your findings.

1 members found this post helpful.

If you gathered that from my posts, then I think there is some comprehension issues.

3 members found this post helpful.

I wasn't talking about you bass. Fallback and enjoy the show. I comprehend well btw.

No matter how many times the parent explains to a teenager why they shouldn't follow the crowd off the bridge or down the dark path they insist on still trying what their peers keep telling them is OK. Then latter in life, or sometimes as soon as they get in trouble as a result of following the crowd, they realize that the parents were correct and they wonder when the parent became so smart.

4 members found this post helpful.

I know, that time has come ...

Attached Thumbnails

 

LXDE is a bit lighter on resources than XFCE. I've got it on my eeepc 1001ha (removable HDD, replaced with an SSD),and it's a bit faster, but not much. There's not a lot you can do with those little critters to improve them.

U TALK 2much OP ! ! !

make a livecd ( no more than 700mb ) with installer , and we will talk later . . .

I was bored today and reread the Managing the aaa_elflibs package sticky thread. It brought up a point I had forgotten about with partial installs. This won't be a post to tell people why they should install a full system (although, reading below will show another benefit of a full install).

The aaa_elflibs package is one of the first things installed on the system. It contains a number of libraries, both duplicates of ones from packages, as well as older libraries that were required for continued functioning of some programs. Most of the libraries are actually duplicates of the files within packages already installed on Slackware, so if there are any security updates, those files will be replaced, or at a minimum, the symlink will be changed to point to the newer file. If a full install was not accomplished, there is a chance that older, vulnerable files might exist on your system. This would occur if you don't install a package that has a library in aaa_elflibs and that package had a security update related to that library.

Now, how do you know if you're in this situation? The obvious way would be to track down what packages those files come from and if you don't have it installed, check and see if there were any patches for it. However, that is an ugly solution, since it takes a lot of work. Pat has actually provided a tool to compare our aaa_elflibs contents with packages installed on the system. It is called display_orphans.sh and can be found in the source/a/aaa_elflibs/ folder on your favorite mirror (here's the link to it on the SBo mirror). If you download and run this, it will show you any files that are in the aaa_elflibs package that do not have corresponding packages installed that contain those files. It doesn't remove all the work, but it does simplify it a bit.

Now, a caveat, there are likely going to be some false positives. They will likely fall into one of two categories. The first is the library provided in aaa_elflibs is an older version that is still needed to make some programs work properly. This is usually the result of a library getting updated and the newer version is incompatible with some programs and those programs haven't been updated. These files are normal and are expected on a new, fresh, and full installation of Slackware. The second category is versioned files. Many libraries will have their versions at the end of the filename like file extensions. If a patch was released that provided a newer version, pkgtool is unable to remove the older version since it still belongs to aaa_elflibs. However, the new package will update the symlink, so as long as any programs that rely on that library don't reference the versioned filename (and they shouldn't be), then those programs will use the updated symlink and won't be vulnerable to any issues the older versions has.

So, for any of you running partial installs, if you're serious about security, I urge you to check your aaa_elflibs contents to make sure you don't have vulnerable libraries sitting in there unknown. To remove any vulnerabilities, there are three options. One, remove the file from the system. Two, install the patched package. Or three, extract the lib and place it in the system, either overwriting the one in aaa_elflibs if they're the same name or updating the symlinks if they're different.

4 members found this post helpful.

@bassmadrigal

Good point!

In other hand, IF the dependencies ring is fully satisfied in the named partial installation, is enough to proper update the installed packages to stay away of security issue.

Sure, they would be present some libraries shipped by aaa_elflibs, which would have security issues, but they would NOT affect the system if no one of packages use them.

I hope there we will agree.

-----------------------------------------------------

Also, for those afraid that SBo packages would yell for non-installed dependencies, to note that in Eric's XFCE Live is present only the GCC (aka the C compiler), but not the autotools or other things.

So, in this installed system one could compile a new Kernel, but almost nothing else.

Long story short, like this thread title say: the installed XFCE Live is literally for net-surfing and watching videos, not for compiling packages from SBo.

Please stop posting until you have something relevant to add to a discussion. Your posts are like farts.

3 members found this post helpful.

Again, if you want to have a meaningful Slackware experience, install the full distro. The XFCE Live ISO is meant for things like hardware tests and other activities that do not require updating the Live OS.

And as a comment to the one whose posts are like farts, adding the harddisk installer would require addition of the huge kernel as well (because that is what the Slackware setup needs). The 9 MB of storage on the ISO required by that kernel must be reclaimed by removing 9 MB of other packages (to stay below 700 MB). And at this point, there are not really any more packages I would want to let go from XFCE Live.

1 members found this post helpful.

Eric, I for one I will trade things like TigerVNC for the huge kernel, in a heartbeat. Also, there maybe is a bit of room for sysvinit-functions.

But that's just me...

BTW, maybe you want to add libwebp to live, as MPlayer does not work because its lack.