A full-featured XFCE desktop for net surfing with 2.6GB installed size, aka: How to install the Eric's XFCE LiveSlak on your hard drive
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.
Eric, I for one I will trade the 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.
TigerVNC is something I use all the time - like other tools that connect to remote servers. So it will not go. The libwebp is something I forgot about , I indended for it to be added.
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.
For the most part, I do. I will provide one caveat though... If a 3rd-party program is compiled against one of those libraries unbeknownst to you, then you could still be vulnerable (and this could be a pre-compiled 3rd-party package or one you build yourself -- assuming you have enough development libraries to build it).
As I said, this was not intended as a reason to tell people to do a full install, just giving people the knowledge to ensure their systems are secure
I agree with you, BUT I do not see what one would want to reasonable add to a net-surfing box like the described one, other maybe than flash-player and Chromium...
Maybe Eric could enlighten us if Chromium is self-composed enough to successfully work in this (installed) mini-system.
Last edited by Darth Vader; 10-03-2017 at 03:33 PM.
I agree with you, BUT I do not see what one would want to reasonable add to a net-surfing box like the described one, other maybe than flash-player and Chromium...
And my post wasn't directed at the minimal install in this thread, but all minimal installs. You might not run into this issue if you don't install KDE, but I'm too lazy to cross-check all the libs in aaa_elflibs with the ones provided by KDE and friends to verify that.
I agree with you, BUT I do not see what one would want to reasonable add to a net-surfing box like the described one, other maybe than flash-player and Chromium...
Maybe Eric could enlighten us if Chromium is self-composed enough to successfully work in this (installed) mini-system.
I am not even remotely interested in finding out. Use a fscking full install if you want to use Chromium, Flash and stuff is my advice.
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.
this is one if the reasons I created sbbdep, to get all packages that use a certain library, depending on the so version and the library search path.
so it is not that hard to find out what programs depend on files found in aaa_elflibs, its in sbbdep.cache just a SQL statment away from you
(the command line interface is in the latest version not totally correct any more with the --who-need option and might miss the one or the other dep, but since no on complained.... it had no priority since for me it works anyway ;-)
that a program will always use what is provided via a symlinc can, but must not be like that, it depends against what it has been linked and what it is looking for exactly.
symlinks are also used to be able to have 2 versions of a library available.
however, if any program relies on libraries from aaa_elflibs that have been updated in the actual packages, this can be considered as a bug, but maybe one of the sort Slackware does not care to much about? I don't konw
I think that the basic idea is to have a small but full featured XFCE desktop for net surfing.
For example, I have a netbook with a flash drive of 8GB, where's impractical to install fully the Slackware, as the people around here recommends, because there's no room for it. Hence, I installed this XFCE liveslak which consumes less than 4GB.
But of course it is very limited, for example you cannot compile C++ programs and lacks many other packages.
If you intend to install whatever program you want, I think is better a traditional full installation of Slackware, because it has no dependencies resolution, then you will need good experience to find and add just the required dependencies.
dude ... then later ( after the supposed install ) can i install whatever package i want ? ? ?
or
am i limited just to xfce ?
tia !
After reading the documentation (http://docs.slackware.com/slackware:liveslak) and Darth's instructions, the answer is not yet clear to you?
Perhaps I should emphasize in the documentation that the result of a harddisk install of liveslak using the "setup2hd" script is: a Slackware system which is indistinguishable from a regular installation.
Well, except for the XFCE variant which does not have a "setup2hd" because it would only install a crippled OS, but by following Darth's instructions you will eventually end up with a proper Slackware install.
Which means, you can install anything you want, because the harddisk installation no longer has any relation to Slackware Live.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
