Porteus

^ Need to get all dependencies for sane via USM I don't think so, that's the point! I think dependencies for sofware included in base modules should be available in base modules (better if present in its own base module, i.e. if kolourpaint comes in 003-kde and requires libsane.so.1 then that libra...

there's no libsane.so.1 but this is a base module, any idea? root@porteus:/home/guest# usm -s libsane.so.1 ----------------------------- Are you searching for a library file? libsane.so.1, it seems a library. Would you like to find the package for it? [y/n] libsane.so.1 was found in sane-1.0.25-x86...

there's no libsane.so.1 Try KDE5 with 07-printing-i586-03.02.2017.xzm or 07-printing-x86_64-03.02.2017.xzm but only for your architecture . I'm using 07-printing-x86_64-02.12.2016.xzm downloaded from http://mirrors.dotsrc.org/porteus/x86_64/Porteus-v3.2.2/modules/07-printing-x86_64-02.12.2016.xzm o...

I have a bug in 3.2.2 kde with kolourpaint, when I execute it I get this error:

kolourpaint: error while loading shared libraries: libsane.so.1: cannot open shared object file: No such file or directory

and that's true, there's no libsane.so.1 but this is a base module, any idea?

yes but p7zip included in porteus (at least in 3.1 kde version) only includes 7zr which is a lite version supporting only 7z, LZMA, BCJ and BCJ2

my module includes 7zr, 7za, 7z with full support of compression algorithms and 7zCon.sfx to create binary self extracting archives

Here you are a module packaging a 7z port for linux 64 bits:

https://app.box.com/s/2etzgqddp6s4cgf5yipwkxdhjb52v2g0

any problem, please let me know

I also want to wish you all a happy new year and also I'm glad to say I feel this forum like a family. Thanks guys!

What I do, periodically, is copy my porteussave.dat file to another folder, rename it porteussave.dat.xzm and load it as a module either when I boot or when I want via an activate. assuming porteussave.dat is your changes file I don't think it were a good practice neither a solution for upgrading p...

Is there any proper Porteus application data backup solution? I've been researching since I don't wanna keep making a new dat container and personalizing all the applications over and over again each update. I've found that folders with . prefix in guest directory have the stuff. But I thought I as...

Use boot parameter (cheatcode) cliexec= activate~/mnt/sdXy/porteus/optional/initialization_module.xzm if you always wish to start off with these settings (module placed in optional folder). what's the difference of doing that (save module in optional folder and run activate via cliexec kernel param...

Los errores que me aparecen en amule con el Firewall en on 2016-11-26 21:45:02: Intento de conexión con GrupoTS Server (46.105.126.71:4661) tiempo agotado. 2016-11-26 21:45:02: Error al conectar a todos los servidores. 2016-11-26 21:45:03: Fallo al conectar a todo los servidores ofuscados listados....

parece que tu problema es con el dirver SIS, ejecuta este comando y pon aquí el resultado: # lspci | grep VGA luego este comando y de nuevo pon el resultado: # lsmod | grep -i sis también dime si tienes algún fichero en el directorio /etc/X11/xorg.conf.d/ especialmente alguno que contenga sis en el ...

Aprovecho tenía esto pendiente tb pues según lo que has publicado, el firewall te funciona perfectamente, aceptas tráfico de los puertos que hemos añadido y permites establecer conexiones, de hecho tienes algunas establecidas: 0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp spt:20 state ESTABLISHED 0...

Thanks. Updated in tree. you're welcome, I'm happy helping to test porteus and make it better, the more I look at porteus internals the more I appreciate your hard & pretty work. brokenman , I suppose using rc.FireWall makes unuseful the file S-firewall.sh so you can avoid the code to create it whe...

However, for now # Enable firewall: # [ -x /etc/rc.d/rc.FireWall ] && sh /etc/rc.d/rc.FireWall start & in /etc/rc.d/rc.services should make it work. yes and also the more slacky-way command: # chmod a-x /etc/rc.d/rc.FireWall get slack! ;-) But the real question here is why it is done this way, and ...