Porteus/Arch aka Sensei (Porteus w/pacman package manager)

[francois]

Great photo on your desktop.

From memory wicd is the WiFi manager. All you have to do is to find the WiFi network and assign your router password.

Volume could be managed at bottom with bootloader cheat code:
http://forum.porteus.org/viewtopic.php?f=81&t=1106
as in volume=80%

Finally, firefox and chrome add very slow on old Linux boxes. You should be better with opera or slimjet or midori.

[francois]

Here I need a little help from my friends (stifiling, ncmprhnsbl, or any arch knoledgeable person).

chromium, that is google-chrome browser on archlinux (porteus-arch) will not start. The error message is:

Code: Select all

root@porteus:~# chromium
/usr/lib/chromium/chromium: /lib/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /usr/lib/chromium/chromium)
root@porteus:~#

According to this thread the following pacman command did not do the job, or maybe I did not say yes to the good options while in the debugging process:
https://bbs.archlinux.org/viewtopic.php?id=181759

Code: Select all

pacman --debug -Syu gcc-libs

[francois]

And:

Code: Select all

root@porteus:~# pacman -Syu
:: Synchronizing package databases...
 sensei                    11.7 KiB  11.4M/s 00:00 [######################] 100%
 core is up to date
 extra is up to date
 community is up to date
 archlinuxfr is up to date
:: Starting full system upgrade...
error: duplicated database entry 'libtasn1'
error: duplicated database entry 'p11-kit'
error: duplicated database entry 'recordproto'
error: duplicated database entry 'diffutils'
warning: alsa-lib: local (1.0.28-1) is newer than extra (1.0.27.2-1)
warning: autoconf: local (2.69-2) is newer than core (2.69-1)
warning: automake: local (1.14.1-1) is newer than core (1.14-1)
warning: binutils: local (2.24-7) is newer than core (2.23.2-3)
warning: bison: local (3.0.2-1) is newer than core (3.0.1-1)
warning: cloog: local (0.18.1-3) is newer than core (0.18.1-2)
warning: diffutils: local (3.3-2) is newer than core (3.3-1)
warning: fakeroot: local (1.20.1-1) is newer than core (1.20-1)
warning: file: local (5.20-1) is newer than core (5.15-1)
warning: flac: local (1.3.0-4) is newer than extra (1.3.0-1)
warning: flex: local (2.5.39-1) is newer than core (2.5.37-1)
warning: gc: local (7.4.2-2) is newer than extra (7.2.d-2)
warning: gcc: local (4.9.1-2) is newer than core (4.8.2-5)
warning: groff: local (1.22.2-7) is newer than core (1.22.2-5)
warning: gtksourceview2: local (2.10.5-3) is newer than extra (2.10.5-2)
warning: guile: local (2.0.11-2) is newer than extra (2.0.9-1)
warning: icu: local (53.1-1) is newer than extra (52.1-1)
warning: isl: local (0.13-1) is newer than core (0.12.1-2)
warning: json-c: local (0.12-2) is newer than extra (0.11-1)
warning: libltdl: local (2.4.2-14) is newer than core (2.4.2-12)
warning: libmpc: local (1.0.2-2) is newer than core (1.0.1-2)
warning: libogg: local (1.3.2-1) is newer than extra (1.3.1-2)
warning: libpulse: local (5.0-1) is newer than extra (4.0-6)
warning: libtasn1: local (4.2-1) is newer than extra (3.4-1)
warning: libtool: local (2.4.2-14) is newer than core (2.4.2-12)
warning: libvorbis: local (1.3.4-1) is newer than extra (1.3.3-1)
warning: make: local (4.0-2) is newer than core (4.0-1)
warning: mc: local (4.8.13-1) is newer than community (4.8.11-1)
warning: mousepad: local (0.3.0-3) is newer than extra (0.3.0-2)
warning: nss: local (3.17.1-1) is newer than extra (3.15.3-1)
warning: p11-kit: local (0.22.1-1) is newer than extra (0.20.1-1)
warning: patch: local (2.7.1-3) is newer than core (2.7.1-2)
warning: pciutils: local (3.2.1-1) is newer than core (3.2.0-4)
warning: perl: local (5.20.1-1) is newer than core (5.18.1-1)
warning: pkg-config: local (0.28-2) is newer than core (0.28-1)
warning: python: local (3.4.2-1) is newer than extra (3.3.3-1)
warning: python-xdg: local (0.25-2) is newer than extra (0.25-1)
warning: recordproto: local (1.14.2-2) is newer than extra (1.14.2-1)
warning: scrnsaverproto: local (1.2.2-2) is newer than extra (1.2.2-1)
warning: speech-dispatcher: local (0.8.1-1) is newer than extra (0.8-2)
warning: sudo: local (1.8.11.p1-1) is newer than core (1.8.8-1)
warning: thunar: local (1.6.3-2) is newer than extra (1.6.3-1)
warning: ttf-bitstream-vera: local (1.10-10) is newer than extra (1.10-9)
warning: vte: local (0.28.2-5) is newer than extra (0.28.2-3)
warning: vte-common: local (0.38.1-1) is newer than extra (0.34.9-1)
warning: xdg-utils: local (1.1.0.git20141009-1) is newer than extra (1.1.0.git20130520-1)
warning: xfce4-terminal: local (0.6.3-1) is newer than extra (0.6.2-1)
warning: xorg-xrandr: local (1.4.3-1) is newer than extra (1.4.1-1)
warning: yajl: local (2.1.0-1) is newer than extra (2.0.4-2)
 there is nothing

[ncmprhnsbl]

i,m guessing , thats the latest chrome built via AUR...
still guessing, gcc-libs is kernel dependent, which means, to upgrade requires specific kernel(could be completely wrong about that)
otherwise you could look at seblu.net for when gcc-libs is the correct version, point /etc/pacman.conf at it..
or just download it directly ... then pacman -U /where /the/pkg/is.pkg.xz
high chance of breakage, being close to the end of its cycle...
for new kernel we must wait for porteus 4.0 (and if stifiling makes a new sensei)

[francois]

From what I understand, gcc should be fixed with the new kernel, and accordingly all these other dependencies for which there is conflict for the upgraded packages.

Introduction to pacman, and citation:
https://wiki.archlinux.org/index.php/Pa ... troduction
After pacman -Syu is run there is a small chance that corrections on the system will be needed in order to have it running as desired. Important corrections are advertised here: Arch Home. They are very rare (six in 2012). However, it is advisable to run pacman -Syu only when time to perform corrections is available to the user and not when the system is relied upon. It is advisable to run pacman -Syu often in order to minimize the difficulty of adjustment, whenever it arises.

However in the first page of this thread

Code: Select all

pacman -Sy

is proposed.

[ncmprhnsbl]

remember, sensei-porteus is not arch,
arch rolls, sensei-porteus does not, https://wiki.archlinux.org/index.php/Ar ... ck_Machine
so -Syu will not upgrade anything(actually, if there are changes in stifiling sourceforge repo or archlinuxfr, would be picked up)
pacman cannot upgrade the slackware kernel...

[francois]

I just reinstall anew and everything works now. Maybe, I just played to much with pacman -Sy package.

[ncmprhnsbl]

fresh is best

[francois]

@Stifiling:
This archlinux version of porteus is more responsive than the original porteus on my old Linux boxes with the packages I usually have on my porteus system. With archlinux and pacman, the choice and availability of packages is infinite, their installation is a charm.

However. The 64 bit edition of version 3.1rc does not permit persistence.

Thanks.

[ncmprhnsbl]

package list (should be)is in /var/lib/pacman/local

And I'm also trying to figure out how to get my ElanTECH touchpad set up (my ElanTECH touchscreen works great).

not sure what you mean .. touchpad not working?
try: http://forum.porteus.org/viewtopic.php? ... 386#p16544

[francois]

If your intent is to replace the xfce desktop with the porteus lxqt module, this will not work. Instead, you will have to install lxqt thru pacman and modify the login manager so that you boot into lxqt, see archlinux instructions:
https://wiki.archlinux.org/index.php/LXQt

This will need some very good familiarization with the archlinux environment. And no one will help you on the archlinux forum if you are not using archlinux directly. Personnally, I would stick with the xfce environment as this is for porteus-arch the only flavor available for 3.1.

But maybe better than that, you should turn yourself to manjaro an archlinux derivative. These people will provide help on their forum. Here is the lxqt download:
http://sourceforge.net/projects/manjaro ... T/2015.08/
Here is the forum:
https://forum.manjaro.org/index.php?board=20.0

You could build also your own minimal lxqt from what they call the manjaro net edition (600mb):
https://wiki.manjaro.org/index.php?titl ... stallation

Manjaro is one of the biggest linux distribution presently.

[Ed_P]

Here is the forum:
https://forum.manjaro.org/index.php?board=20.0

This actually might be a better link: https://forum.manjaro.org/index.php

You could build also your own minimal lxqt from what they call the manjaro net edition (600mb)

Careful francois, that could be taken as a DIY response.

[francois]

Thumbs up for the positive attitude.

However, my impression is that stifiling will not maintain that thread anymore.

[francois]

I reread your post, and I am happy to learn:
All my Arch modules are made from converted pkgs.org "pkg's" (Arch) using LxQt/Porteus. And all of them function flawlessly in Sensei.

However, as arch is a rolling release distribution and is condidered more bleeding edge than slackware, it could happen that some packages could supercede some important packages of your porteus installation. This is the case for archlinux abiword, porteus does not support the actual archlinux version. So you might get into some limitations trying to build archlinux on porteus. See last post of first thread:
viewtopic.php?f=75&t=4997

In addition, here is what beny has to say about archlinux and slackware compatibility. Stated from the chat:
i have stripped a lot of arch packages and only a few are good for slackware

Why don't you want to simplify your life with pacman? Stifiling explains how to build modules using porteus/arch on the first page of this thread. So you have the advantages of porteus: modules and the advantages of archlinux a greater pasture to work with. I would be please to test a lxqt module for porteus/arch.

Concerning factual information comparing archlinux to slackware here is a very good thread by someone who looks like a connaisseur:
https://wiki.archlinux.org/index.php/Ar ... tributions
Slackware and Arch are quite similar in that both are simple distributions focused on elegance and minimalism.
Slackware is famous for its lack of branding and completely vanilla packages, from the kernel up. Arch typically applies patching only to avoid severe breakage or to ensure packages will compile cleanly.
Slackware uses BSD-style init scripts, Arch uses systemd.
Arch supplies a package management system in pacman which, unlike Slackware's standard tools, offers automatic dependency resolution and allows for more automated system upgrades. Slackware users typically prefer their method of manual dependency resolution, citing the level of system control it grants them, as well as Slackware's excellent supply of pre-installed libraries and dependencies.
Arch is a rolling-release system. Slackware is seen as more conservative in its release cycle, preferring proven stable packages. Arch is more bleeding-edge in this respect.
Arch Linux provides many thousands of binary packages within its official repositories whereas Slackware official repositories are more modest.
Arch offers the Arch Build System, an actual ports-like system and also the AUR, a very large collection of PKGBUILDs contributed by users. Slackware offers a similar, though slimmer system at slackbuilds.org which is a semi-official repository of Slackbuilds, which are analogous to Arch PKGBUILDs. Slackware users will generally be quite comfortable with most aspects of Arch.

[francois]

Bluemeridian, I would say you are right about porteus-arch. Abiword will not be a problem as the missing dependencies on slackware are there on archlinux.

Surely stifiling could reason a lot better than me on issues tied to porteus-arch compared to arch alone. The major one being that it is a rolling release distribution and its use of forcing some packages as described on the first page. Just backup your work once and a while, just for sure.