Porteus

hello !
Environment :
boot porteusv1.2-349 in vesa-mode as root
ctrl+alt+f1
login as root
Command executed :
activate crippled..v1.2-update..xzm
Results :
Updating shared library links: /sbin/ldconfig
Updating KDE menu: kbuildsycoca
Loading /usr/share/kbd/keymaps/i386/azerty/fr-latin1.map
[kbuildsycoca] Warning: kbuildsycoca is unable to register with DCOP.
[kbuildsycoca] kbuildsycoca running...
[tdeinit] Aborting. $DISPLAY is not set.
There was an error setting up inter-process communications for TDE. The message returned by the system was:
Could not read network connection list.
/root/.DCOPserver_je_xp70_NODISPLAY
Please check that the "dcopserver" program is running!
[kbuildsycoca] Reusing existing ksycoca.
Questions
seems ok, but
may I consider as only warning ?
same errors with other modules activating on the fly.
Blind methods ?
activate crippled... 2>null
deactivate crippled... 2>null
command only on X

bour59, the crippled kernel source module, you can put it on the base folder or modules folder and at every boot you have this software available for the building task,check if module is corrupted.

tx beny
I know that.
but is-it necessary to activate thousand of modules in case of.
what is the impact of activating thousand modules on memory size used! or other performance!
for now it'a mistery for me.

i don't remeber the max modules activation numbe,r fanthom can help you better,but if you have a30 0r 40 modules i don't think you have trouble with aufs,but i can be wrong of course

@bour59
activation of modules in cli while you have a GUI opened on vt7 is not a good idea as activation scripts needs to regenerate all the caches.
kbuildsycoca can't run in cli: so your GUI desktop may get broken.

there is no solution for this problem so please:
a) activate modules in GUI only
b) activate modules in cli but then restart GUI immediately
just to mention that this problem does not exist if you activate module in cli and then start GUI as kbuildsycoca is run at the start of each KDE session.

regarding aufs performance: i have seen a slowdown when ran 'slackyd -d' while have 512 modules activated (whole official repo).
this is rather rare scenario so aufs impact shouldn't affect average porteus user.

max number of aufs branches is set to 512 in the kernel config. i can raise it to 1024 or even 32k but really see no point for it.

Cheers

thx fanthom
I've written a small shell that avoid ac(dea)ctivate in cli
and explain the reason why

you say also : restart the gui
how to do this
I don't really understand why adding some folders from a module
needs the intervention of ksyscoca
linux tend to the opacity of another os
but this is not the place to discuss that indeed
Porteus is the best one!! like you , your team and all user's