Porteus

I noticed many people are excited to go ahead and work on 002-xorg while I am still working out bugs in 001. I will list here all the stuff that I need help with in the hope that some people will focus attention on the 001 module. Without a rock solid base the higher stages will certainly fall.

1.0)
The module produced by setup-pman causes a systemd failure on next boot when placed in modules folder.
FIXED

2.0)
During shutdown, systemd doesn't unmount aufs correctly giving ugly red messages.

3.0)
When guest issues su command a dbus error message is reported.

After upgrading from systemd226 to systemd227 the problem has changed.
When logged in as guest and issuing su the error message is:

Failed to connect to bus: Operation not permitted

When logged in as root and trying to su to guest: su guest the error message is:

Failed to connect to bus: Permission denied.

Looks like a permission issue now. I have to assume the problem doesn't exist in arch, so what could it be?

1.0 I have not experienced any failure in vbox
2.0 There is a lot of red messages for me too in vbox.
3.0 There are some red messages at bootup.

3.0 There are some red messages at bootup.

Can you please post what they are? You can get them in two ways:

1) after boot run: systemctl --failed
2) In vbox go to settings/system/processor and move the % slide bar down to about 8. Now you will have a processor running at 8% capacity which should slow down the boot enough to see what's happening.

I'm not interested in network-setup failure as I am rewriting the network procedure to be more reliable and robust. Thanks.

systemctl --failed:
systemd-networkd.service loaded failed failed
systemd-resolved.service loaded failed failed
systemd-timesyncd.service loaded failed failed
systemd-networkd.socket loaded failed failed

With slow processor other than above:
Failed start login service

...

The rest is hard to catch. I will try tomorrow with better eyes.

Good nite.

systemd-networkd.service loaded failed failed
systemd-resolved.service loaded failed failed
systemd-timesyncd.service loaded failed failed
systemd-networkd.socket loaded failed failed

These are the fails I was talking about in point 1) of my original post when you have a pacman-settings.xzm module in the modules folder. Is this the case?

at this point, i can confirm theres a problem with pacman-settings.xzm..
theres not much in it...

i see the unmount fail messages(breifly) at poweroff but have no ideas..
ahve seen this? https://aur.archlinux.org/packages/linux-aufs_friendly/

Same here. I have pacman-settings.

If you stop it with "halt", you can read the lines at closing:
I get in red,
Failed to unmount /mnt/sdb2
Falied to unmount /mnt/live/memory/changes
Failed to unmouint /mnt/live/memory/images/001-core.xzm
Failed to unmount /mnt/live/memory/images/000-kernel.xzm
Failed to unmount /mnt/live/dev
--------------------------here one line ok-----------
Failed to unmount /mnt/live

I tested running Midnight Commander: text-mode mouse does not work, only F1 responds correctly, all other F's fail.
I tried "systemctl start dhcpcd"; response was "systemd.service" was not loaded.

I don't quite understand the use of nemesis. Only because of systemd? or because of pcman? then switch to Archlinux...

Guys, I am aware of the error messages in red. That's why I created this section. This section is for people to help find out the cause of the error messages before I get time to investigate. The outstanding problems are things that I have noted but not yet attended to.

i don't quite understand the use of nemesis. Only because of systemd? or because of pcman?

It is an attempt at having a system for people to help develop the OS. A community developed OS. It uses systemd which is a good chance to get to know how it works if that's your end goal.
So far many people are reporting bugs which is great. Until today nobody has registered a bitbucket account to actually help with development. Writing code. This is what I am hoping will happen. We are using git so don't be scared of breaking anything. We can create branches, and revert changes no problem. When someone joins, and is prepared to modify the source code, I will create a video tutorial on how to commit changes. They are first reviewed by me and then merged with the master trunk if approved.

Wread, pman is simply a wrapper around pacman that converts the installed packages to modules.
I understand there is Sensei, and Stiffiling does a great job with it. I am hoping he will join in with developing Nemesis as he understands arch better than me. Sensei gives users a base to work off in order to create desktop environments. Nemesis intends to offer a fully finished desktop environment. Of course, this can only be realized if we get more people actually helping develop. If it is just me coding then things will grind to a screeching halt very soon. I simply don't have the time to devote to running it by myself. If it remains only me then I will release the final 002 stage and then leave it available but not maintained.

My priority is the standard Porteus, and my time could better be used there.

hi wread you have to modify the network config in config directory ip-link give you a number you have to change this in config.

hi thanks brokenman i have done video driver with your crippled kernel source and header, only one thing arch not want the 32 bit compatibility libs when xfce4 start give an elf error for libGL,so only the 64 bit is installed i am into the system now.activate into X seem not work in the console: activate /root/xz/libisofs-1.4.0-1-x86_64.pkg.xzm
/usr/local/bin/activate: line 85: /usr/local/bin/xactivate: No such file or directory
btw good work, only the guest account left as issue now

The last update I pushed 30 minutes ago changed the predictable naming of network cards. The default now is back to eth0 and wlan0.
xactivate will be added when I reach stage 002.

only the guest account left as issue now

Please check with latest update and report if it is still an issue.

and wread i think you can test the plasma 64 bit more easily in archeus with pman,i think

@brokenman
I must apologize, then I didn't want to offend you, Jay.
And I understand the situation. They want to eliminate the little distros from the market; they want to get Slackware out of sight, they invented systemd, giving some inexcusable excuse...Even KDE is looking at it (systemd). With systemd you can say goodby to portable distros, Porteus will die....
All systemd-distros are big, must be big, or ask Tom what he thinks.

If the train cannot be stopped, we can still survive going BSD instead Linux and making Portmacos a live distribution.

To nemesis or not to nemesis, that is the problem!

Regards

You didn't offend me Wread. You just asked a simple question.

All systemd-distros are big, must be big, or ask Tom what he thinks.

What makes you think that? And what makes you think that a portable distro can't use systemd?
Nemesis will be a portable distro that is under 300Mb and uses systemd. I don't particularly like systemd very much so far. It does make some simple things a little difficult to achieve. I'm not sure if Mr Poettering has an alternate agenda to take over the linux world or not. I don't particularly care either way. Linux means freedom and diversity. All I can say is, until I have tried it and understand it fully, I can't really make an informed decision about it.

They want to eliminate the little distros from the market; they want to get Slackware out of sight, they invented systemd

Who exactly is they? Why would they want to eliminate little distros? Little embedded distros are the future. If slackware dies it won't be because of systemd. Not any time soon as I see it.

Anyway, the above are just rhetorical questions. No need to answer them and start yet another systemd thread. Leave that for the can of worms thread that I started.