[not4n00bs] ...Userland "tree"
Posted: 23 Aug 2016, 20:40
@ critics...
Salutations...
Howdy... Neighbors!!!
I made this thread to see how much alpha I could get away with WITHOUT breaking stuff.
Yep... I've decided to wander off the reservation and go ROGUE by... revising 001-core.xzm
Ok... I confess. I'm a NOT big fan of Gordian Knot s (nots?) which is why I like cutting them.
So let's get started...
Slackware has a minimal install @ http://www.slackwiki.com/Minimal_System.
(see also... http://www.slackware.com/~mozes/docs/aaa_elflibs.txt )
Unfortunately... Slackware: Dependency resolution is not officially **supported in accordance with it's distribution's maintenance philosophy.
**Pls Note: Arch Linux has support... it's repo was used to construct this (glibc?) tree... https://www.archlinux.org/packages/core/x86_64/glibc/ .
" Dependency hell " still however... is NOT a given (provided the following is considered in order of dependency).
With few exceptions... almost all things Linux "plug" into this (glibc?) tree which forms the foundation of "Userland" (aka... User space ).
I have recently been using this tree to enhance 001-core.xzm before adding carefully selected ( Linux From Scratch ) Slakfinder.org
packages organized using the Arch Linux package resolution structure and only then finally confirming all their solibs w/ depfinder.
https://pkgs.org/slackware-14.2/salix-x ... v.txz.html
Whether doing remastering or a build project (eg. Linux From Scratch )
the above blueprint by and large is the route of least resistance.
As a added bonus... if ANY of these key packages were deprecated in favor of more efficient
alternatives (eg. Suckless.org )... the entire system would realize major performance gains.
(also see... http://wiki.musl-libc.org/wiki/Alternative_libraries )
Posted by 73.112.18.233 via http://webwarper.net
This is added while posting a message to avoid misusing the service
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^A Tutorial is a method of transferring knowledge and may be used as a part of a learning process. More interactive and
specific than a book or a lecture, a tutorial seeks to teach by example and supply the information to complete a certain task.
Salutations...
Howdy... Neighbors!!!
I made this thread to see how much alpha I could get away with WITHOUT breaking stuff.
Yep... I've decided to wander off the reservation and go ROGUE by... revising 001-core.xzm
Ok... I confess. I'm a NOT big fan of Gordian Knot s (nots?) which is why I like cutting them.
So let's get started...
Slackware has a minimal install @ http://www.slackwiki.com/Minimal_System.
(see also... http://www.slackware.com/~mozes/docs/aaa_elflibs.txt )
Unfortunately... Slackware: Dependency resolution is not officially **supported in accordance with it's distribution's maintenance philosophy.
**Pls Note: Arch Linux has support... it's repo was used to construct this (glibc?) tree... https://www.archlinux.org/packages/core/x86_64/glibc/ .
" Dependency hell " still however... is NOT a given (provided the following is considered in order of dependency).
Code: Select all
(glibc) <--(bzip)
|
zlib
binutils
|_ _
|
(gcc)
|
ncurses
readline
|_ _
|
(bash)
|
gmp
mpfr
libmpc
pcre
|_ _
|
(glib2)
I have recently been using this tree to enhance 001-core.xzm before adding carefully selected ( Linux From Scratch ) Slakfinder.org
packages organized using the Arch Linux package resolution structure and only then finally confirming all their solibs w/ depfinder.
https://pkgs.org/slackware-14.2/salix-x ... v.txz.html
Whether doing remastering or a build project (eg. Linux From Scratch )
the above blueprint by and large is the route of least resistance.
As a added bonus... if ANY of these key packages were deprecated in favor of more efficient
alternatives (eg. Suckless.org )... the entire system would realize major performance gains.
(also see... http://wiki.musl-libc.org/wiki/Alternative_libraries )
Posted by 73.112.18.233 via http://webwarper.net
This is added while posting a message to avoid misusing the service