[SOLVED] ...Modularity and "Run From Ram"

Technical issues/questions of an intermediate or advanced nature.
fullmoonremix

[SOLVED] ...Modularity and "Run From Ram"

Post#1 by fullmoonremix » 23 Aug 2016, 15:33

P: _I'm in the process of stripping 001-core.xzm down to the bone (ie... Linux From Scratch ).

Q: _Which one of the following packages is needed to avoid breaking Porteus modularity and the ability to "run from ram"?

These are the candidates slated for possible 001-core.xzm deprecation (or removal to 002-xorg.xzm???)...

Code: Select all

aaa_base-14.2-x86_64-2
aaa_terminfo-5.9-x86_64-1
acpid-2.0.26-x86_64-1
bin-11.1-x86_64-1
cdrtools-3.01-x86_64-3
dcron-4.5-x86_64-5
dhcpcd-6.8.2-x86_64-2
dialog-1.3_20160424-x86_64-1
dmapi-2.2.12-x86_64-1
dmidecode-3.0-x86_64-1
dosfstools-3.0.28-x86_64-1
dvd+rw-tools-7.1-x86_64-2
etc-14.2-x86_64-8
floppy-5.5-x86_64-1
fuse-2.9.5-x86_64-1
glibc-solibs-2.24-x86_64-1
glibc-zoneinfo-2016f-noarch-1
iputils-s20140519-x86_64-1
ipw2100-fw-1.3-fw-1
ipw2200-fw-3.1-fw-1
libpcap-1.7.4-x86_64-1
libraw1394-2.1.1-x86_64-1
libusb-1.0.20-x86_64-1
lm_sensors-3.4.0-x86_64-1
lsof-4.89-x86_64-1
lvm2-2.02.161-x86_64-1
network-scripts-14.2-noarch-2
ntfs-3g-2016.2.22-x86_64-1
openssh-7.3p1-x86_64-1
pkgtools-14.2-noarch-11
ppp-2.4.7-x86_64-1
reiserfsprogs-3.6.24-x86_64-1
rpm2tgz-1.2.2-x86_64-1
screen-4.4.0-x86_64-1
sdparm-1.10-x86_64-1
sshfs-fuse-2.5-x86_64-1alien
sysfsutils-2.1.0-x86_64-1
sysvinit-functions-8.53-x86_64-2
sysvinit-scripts-2.0-noarch-33
unrar-4.2.4-x86_64-1alien
usbutils-008-x86_64-1
utempter-1.1.6-x86_64-2
wireless-tools-29-x86_64-9
xfsdump-3.1.6-x86_64-1
xfsprogs-4.3.0-x86_64-1
zd1211-firmware-1.4-fw-1
This is what I safely removed so far from 001-core.xzm without breaking anything...

Code: Select all

alsa-lib-1.1.1-x86_64-2
bridge-utils-1.5-x86_64-1
cgmanager-0.39-x86_64-1
cifs-utils-6.4-x86_64-2
curl-7.50.1-x86_64-1
dnsmasq-2.76-x86_64-1
elfutils-0.163-x86_64-1
ethtool-4.5-x86_64-1
gamin-0.1.10-x86_64-5
gptfdisk-1.0.0-x86_64-1
httpfs2-0.1.4-x86_64-1dj
icu4c-56.1-x86_64-2
infozip-6.0-x86_64-3
libaio-0.3.109-x86_64-1
libcap-ng-0.7.7-x86_64-1
libgudev-230-x86_64-1
libidn-1.33-x86_64-1
libndp-1.6-x86_64-1
libnetfilter_conntrack-1.0.5-x86_64-1
libnfnetlink-1.0.1-x86_64-1
libnih-1.0.3-x86_64-2
libsoup-2.52.2-x86_64-2
libtermcap-1.2.3-x86_64-7
libusb-compat-0.1.5-x86_64-2
libusbmuxd-1.0.10-x86_64-1
libxml2-2.9.4-x86_64-2
logrotate-3.8.9-x86_64-1
lzip-1.16-x86_64-1
lzo-2.09-x86_64-1
lzop-1.03-x86_64-1_slonly
mdadm-3.3.4-x86_64-1
mozilla-nss-3.23-x86_64-1
net-tools-1.60.20120726git-x86_64-1
newt-0.52.19-x86_64-1
nfs-utils-1.3.3-x86_64-2
openvpn-2.3.11-x86_64-1
p7zip-16.02-x86_64-1alien
parted-3.2-x86_64-2
pciutils-3.4.1-x86_64-2
popt-1.16-x86_64-2
powertop-2.8-x86_64-1
pptp-1.8.0-x86_64-1_slonly
rfkill-0.5-x86_64-1
rp-pppoe-3.12-x86_64-1
rpcbind-0.2.3-x86_64-1
rsync-3.1.2-x86_64-1
sg3_utils-1.42-x86_64-1
slocate-3.1-x86_64-4
smartmontools-6.5-x86_64-1
sqlite-3.13.0-x86_64-1
squashfs-tools-4.3-x86_64-1
strace-4.11-x86_64-1
sudo-1.8.16-x86_64-1
usb_modeswitch-2.2.6-x86_64-1
usbmuxd-1.1.0-x86_64-1
wgetpaste-2.25-noarch-2_slack
whois-5.2.12-x86_64-1
For me 001-core.xzm is all about "boot n' build".
Everything after that (> 001) is just interface (CLI/GUI).

The way I view it... when I do a build everything missing will be demanded by
the USM anyway. After I finish the build I will vet everything with "depfinder"...
http://webwarper.net/ww/~av/slakfinder. ... pkg=256437

My goal is to have a functioning stripped down 001-core.xzm based on LFS that supports ONLY... USM/MC and Connman.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Preface... :(
An Inquiry is any process that has the aim of augmenting knowledge, resolving doubt, or solving a problem.



Posted by 73.112.17.86 via http://webwarper.net
This is added while posting a message to avoid misusing the service
Last edited by fullmoonremix on 06 Sep 2016, 08:19, edited 26 times in total.

fullmoonremix

Re: Modularity and "Run From Ram"...

Post#2 by fullmoonremix » 24 Aug 2016, 15:36

I assume the file system packages in the list are keepers.
Also... the wireless... network and device packages are important.

And of course... the associated dependencies should not be removed.
Beyond that... I'm not sure which remaining packages are safe to deprecate.


Posted by 199.36.206.40 via http://webwarper.net
This is added while posting a message to avoid misusing the service

fullmoonremix

Re: Modularity and "Run From Ram"...

Post#3 by fullmoonremix » 25 Aug 2016, 19:07

The 1st post was revised...




Posted by 73.112.19.173 via http://webwarper.net
This is added while posting a message to avoid misusing the service
Last edited by fullmoonremix on 27 Aug 2016, 16:20, edited 3 times in total.

User avatar
wread
Module Guard
Module Guard
Posts: 1080
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v3.2.5-kde5-64 bits
Location: Santo Domingo
Contact:

Re: Modularity and "Run From Ram"...

Post#4 by wread » 26 Aug 2016, 15:38

We are all anxious to test your Porteus-PeckWM-rc1 8)
When are you going to share it?
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

fullmoonremix

Re: Modularity and "Run From Ram"...

Post#5 by fullmoonremix » 26 Aug 2016, 16:41

Soon of course... but it's still in the oven baking. :wink:

All I need to know is... how many of the packages from the group
slated for deprecation can I remove without breaking Porteus?

With that answer it could be ready in less than a week.
And that's only because I will need to download... assemble all the parts and test it.

For example I know I can remove alsa because I'm deprecating it in favor of OSS (which has pro audio sound).

Here's what I have so far functioning (w/ the old 001-core.xzm)...
Qingy (uses "DirectFB" however this was difficult to set up)... Fifth Browser (uses "FLTK" toolkit but it still needs symlinks)... Tint (XCB)...
PekWM (XCB)... TkDVD ("tk" toolkit)... Xfe ("Fox" toolkit)... Connman... MC... USM... plus my default configuration and "tarpit" (various packages).

The problem is I can't build anything until I can strip down 001-core.xzm.

Now this doesn't mean you can't put all the deprecated stuff back in.
It only means it has to go into 002-xorg.xzm.

Ultimately... I will still need a hardened kernel using ADEOS and grSec.

I would also like to build a streamlined dev module with
a functional src2pkg so I can compile "snackamp" (tk toolkit)...
http://snackamp.sourceforge.net/siteima ... esktop.png


Posted by 73.112.16.173 via http://webwarper.net
This is added while posting a message to avoid misusing the service
Last edited by fullmoonremix on 28 Aug 2016, 12:57, edited 8 times in total.

fullmoonremix

Re: Modularity and "Run From Ram"...

Post#6 by fullmoonremix » 26 Aug 2016, 19:47

The 1st post was revised...

Posted by 73.112.19.173 via http://webwarper.net
This is added while posting a message to avoid misusing the service
Last edited by fullmoonremix on 27 Aug 2016, 16:18, edited 1 time in total.

fullmoonremix

Re: Modularity and "Run From Ram"...

Post#7 by fullmoonremix » 27 Aug 2016, 00:00

I think one way to do the deprecation is to review previous versions of 001-core.xzm.

I will explore this avenue tonight.

Posted by 73.150.85.78 via http://webwarper.net
This is added while posting a message to avoid misusing the service

fullmoonremix

Re: Modularity and "Run From Ram"...

Post#8 by fullmoonremix » 27 Aug 2016, 05:38

The first post was revised...

Posted by 73.112.19.173 via http://webwarper.net
This is added while posting a message to avoid misusing the service
Last edited by fullmoonremix on 27 Aug 2016, 16:17, edited 6 times in total.

Jack
Contributor
Contributor
Posts: 1081
Joined: 09 Aug 2013, 14:25
Distribution: Porteus 3.2.rc5 Mate 64 bit
Location: Marysville, OHIO USA

Re: Modularity and "Run From Ram"...

Post#9 by Jack » 27 Aug 2016, 06:27

I found this I don't if it will help you or not.

Code: Select all

aaa_base-14.2-x86_64-1
aaa_elflibs-14.2-x86_64-13
aaa_terminfo-5.9-x86_64-1
bash-4.3.042-x86_64-1
bin-11.1-x86_64-1
bzip2-1.0.6-x86_64-1
coreutils-8.25-x86_64-2
dcron-4.5-x86_64-5
dhcpcd-6.8.2-x86_64-2
dialog-1.2_20130523-x86_64-1
diffutils-3.3-x86_64-1
e2fsprogs-1.42.13-x86_64-2
elvis-2.2_0-x86_64-2
etc-14.2-x86_64-6
eudev-3.1.5-x86_64-8
findutils-4.4.2-x86_64-1
gawk-4.1.3-x86_64-1
glibc-solibs-2.23-x86_64-1
gnupg-1.4.20-x86_64-1
grep-2.25-x86_64-1
gzip-1.6-x86_64-1
iputils-s20140519-x86_64-1
logrotate-3.8.9-x86_64-1
mpfr-3.1.4-x86_64-1
ncurses-5.9-x86_64-4
net-tools-1.60.20120726git-x86_64-1
network-scripts-14.2-noarch-1
openssh-7.2p2-x86_64-1
openssl-solibs-1.0.2h-x86_64-1
pkgtools-14.2-noarch-6
procps-ng-3.3.11-x86_64-1
sed-4.2.2-x86_64-1
shadow-4.2.1-x86_64-1
sharutils-4.15.2-x86_64-1
slackpkg-2.82.1-noarch-1
sysklogd-1.5.1-x86_64-1
sysvinit-2.88dsf-x86_64-4
sysvinit-functions-8.53-x86_64-2
sysvinit-scripts-2.0-noarch-31
tar-1.28-x86_64-1
util-linux-2.27.1-x86_64-1
wget-1.17.1-x86_64-2
which-2.21-x86_64-1
xz-5.2.2-x86_64-1
I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.

User avatar
wread
Module Guard
Module Guard
Posts: 1080
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v3.2.5-kde5-64 bits
Location: Santo Domingo
Contact:

Re: Modularity and "Run From Ram"...

Post#10 by wread » 27 Aug 2016, 11:21

Do it trial and error by bisection; you must test running with the bottom half of the list; if it does not comply your expectations, add the bottom half of the left out top list, repeatedly.

The second time you do it from top to bottom; the third time from bottom to top, etc., until it is clean 8)

Alternatively, you could read what each package does and decide if you want to keep that functionality, taking it out or leaving it unchanged accordingly 8)

Regards!
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

fullmoonremix

Re: Modularity and "Run From Ram"...

Post#11 by fullmoonremix » 27 Aug 2016, 16:16

Thanks... wread



Posted by 73.112.19.173 via http://webwarper.net
This is added while posting a message to avoid misusing the service

Jack
Contributor
Contributor
Posts: 1081
Joined: 09 Aug 2013, 14:25
Distribution: Porteus 3.2.rc5 Mate 64 bit
Location: Marysville, OHIO USA

Re: Modularity and "Run From Ram"...

Post#12 by Jack » 27 Aug 2016, 17:21

In your first post the 1st list is it 001-base and the 2nd list going to be 001-extra? That way the 1st will be dependency free? And when you add the 1st list and 2nd list be dependency free too? If you move 2nd list to 002 it would make 002 even bigger and right now it is 80.1MB.

I think your on the right track if you do it this way.

001-base and 001-extra (you might have this built)
002-xorg and 002-extra
003-desktop and 003-extra and in this move programs from 002 to this module but leave openbox in 002.

If I knew how that's the way I would build it. If over time packages or programs were upgraded you would only have to upgrade that module which is above.

Hope you understand this.

This is just a thought and my 0.02 cent.
I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.

fullmoonremix

Re: Modularity and "Run From Ram"...

Post#13 by fullmoonremix » 28 Aug 2016, 00:36

The 1st list is not my spin on 001-core.xzm (my spin is... glibc "tree" + " Linux From Scratch " + Arch dep resolution + USM + MC + Connman).
http://webwarper.net/ww/~av/forum.porte ... ell#p48238

The 1st list (002-xorg.xzm "candidates") is what remains after moving the 2nd list to 002-xorg.xzm.
(I actually don't use 002-xorg.xzm because I want a clean PekWM build with X11/xorg support and drivers placed in /~/porteus/modules).

When I finish sorting out the 1st list I'll merge the vetted "candidates"
into 002-xorg.xzm and what remains back into 001-core.xzm.


Posted by 73.112.16.173 via http://webwarper.net
This is added while posting a message to avoid misusing the service
Last edited by fullmoonremix on 28 Aug 2016, 13:49, edited 11 times in total.

Jack
Contributor
Contributor
Posts: 1081
Joined: 09 Aug 2013, 14:25
Distribution: Porteus 3.2.rc5 Mate 64 bit
Location: Marysville, OHIO USA

Re: Modularity and "Run From Ram"...

Post#14 by Jack » 28 Aug 2016, 01:00

I was trying to help but I guest I was wrong.
I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.

fullmoonremix

Re: Modularity and "Run From Ram"...

Post#15 by fullmoonremix » 28 Aug 2016, 01:03

You are not "wrong" Jack... you just have a different "spin" on the approach.
No worries... your input helps more than you know. You and wread give me a fresh perspective.

Posted by 73.112.16.173 via http://webwarper.net
This is added while posting a message to avoid misusing the service

Post Reply