Porteus

nemesis-v1.1.0-151012-x86_64.iso
- guest user with password guest works. But only at first bootup. I changed the password of guest and next bootup guest will not login.
- internet works automatically without invoking systemctl start dhcpcd
- pacman-settings.xzm is moved automatically to /nemesis/modules

Thanks.

next bootup guest will not login

Are you working with persistence/changes? To keep the changed password you will need to somehow make /etc/{shadow,gshadow} persist a reboot. Exactly the same as porteus.

francois wrote:next bootup guest will not login.

is that with, or without pacman-settings.xzm?

hi i have come back to old core in the new pman config not found so i can't use it good for the eth0 device in network config guest account not work for me i have removed the old changes so i have installed the new iso with no luck,a strange thing the software in base maybe seem activated but i have glibc for the compiler task not work i have had reinstall the graphite software and glibc for the video driver build and i can't manage jpeg picture i have it as txt file,kodi seem good to open this but ristretto not work.

@brokenman, ncm...:
with pacman-settings.xzm
and
with persistence mode.

/etc/shadow and gshadow are very interesting.

Thanks.

Beny, With the latest ISO after booting take a look in /etc/netctl/examples and modify one of these config files to put in /etc/netctl/myconfig
Then to start it just issue: netctl myconfig

Francois I believe I have fixed the problem with the pacman-settings.xzm module screwing up the services. (check latest ISO)

pacman.settings.xzm seems to work fine here.

However the subfolder approach for bootloading does not work no more. Is it possible.I like the subfolder approach, it provides a cleaner partition structure permitting to install nemesis hdd in addition to another os.

Can you tell me when it stopped working? Was it after the change of folder names to nemesis? Any output when it fails?

Correction:
The subfolder option is working. Working on too many nemesis versions, too many boxes with and without vbox.

dbus error with normal user, see:
https://github.com/systemd/systemd/issues/589

It seems to be because root and guest don't share the same dbus bus. Only one is open per user per login.Perhaps an upstream systemd bug. I think I will wait for the next version.

For the shutdown messages how is the info of journaltcl?

I found this thread which might give an explanation:
https://bbs.archlinux.org/viewtopic.php?id=200232

Edited.

yes I imagine the shutdown errors will be in there. For verbose output you can boot with this: systemd.log_level=debug log_buf_len=1M enforcing=0

I upgraded to systemd 227 and it seems the dbus error has changed. SEE first post.

See edit of my previous post.

No, the problem is that it is failing to unmount aufs cleanly.

brokenman i can confirm you aufs when unmount the live filesystem have a lot of error,please arch have a zen section for the alternative kernel ,you want take a try ....