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.
I installed your list using installpkg --root /path/to/directory, then added an entry to an existing /boot/grub/menu.lst and rebooted. It failed, so I added an /etc/fstab and it worked (I guess fstab is created by the Slackware installer script). Anyway to cut a short list even shorter it will boot without pkgtools, dialog, sysklogd and logrotate. I haven't experimented further as you need pkgtools to remove the packages.
I will use the other small install that worked, as a guide. And install a new one cutting down packages as I go. to try to find out what package I need
but I havent chosen D series. Only A. So why is it there? anyway I needed that or I got an error.
I will test on a real pc tomorrow, instead of vmware and check if I get the same error.
samac: isnt installpkg,removepkg,upgradepkg and so on a part of pkgtools? so I need that package, dont I?
samac: isnt installpkg,removepkg,upgradepkg and so on a part of pkgtools? so I need that package, dont I?
Not to boot, but to add and remove packages.
You can also remove openssl-solibs. If you remove aaa-elflibs you require to add libtermcap, libcap, acl, attr (and ncurses if you absolutely want to be able to add packages).
Because these *-solibs are libraries that Patrick Volkerding has packaged up out of other packages, they are not stand alone libraries/programs. Therefore they are not found in all Linux distributions, they are part of Slackware Linux not all Linux distributions.
Incidently if you decide to do without the aaa_elflibs you can also remove aaa_terminfo as these files are provided by ncurses.
so if I remove aaa_elflibs I can install libtermcap, libcap, acl, attr ? only those 4?
and if I remove terminfo I can install ncurses? what's positive with that?
However you will have learned, as I have just done, that init requires libtermcap, and ls requires libcap, acl and attr, dialog requires ncurses which also supplies your terminfo.
No, no, the package named glibc includes everything installed by all the other glibc packages -the i18n, the development libs and headers, the locale stuff. glibc-solibs is not some pieced-together hack of a pack (while aaa_elflibs *is*).
glibc-solibs is a subset of the full glibc installation which includes just the runtime libraries. All the different parts of glibc are split into separate packages because the glibc package is *huge* and mayn users do not need or want all the different parts. If you list all the files included in all the glibc packages except the full glibc-x.x.x and run them through uniq, you'll find that the list matches the list of files in the full glibc-x.x.x package.
glibc-solibs is a subset of the full glibc installation which includes just the runtime libraries. All the different parts of glibc are split into separate packages because the glibc package is *huge* and mayn users do not need or want all the different parts. If you list all the files included in all the glibc packages except the full glibc-x.x.x and run them through uniq, you'll find that the list matches the list of files in the full glibc-x.x.x package.
I stand corrected. It seems to be an odd way of doing it, having individual parts and a complete package, I would have thought it would have made more sense to have a glibc-base, glibc-headers, glibc-i18n etc.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.