I am having various problems with net-misc/pxes-0.7 . With userpriv specified in /etc/make.conf FEATURES, the devices which are needed for pxes's source for the initrd cannot be created. Removing the userpriv option fixes this. Another error, regardless of userpriv, is that while installing, a ton of "unable to preserve permissions for" errors fly by. Here is an example: cp: failed to preserve ownership for /var/tmp/portage/pxes-0.7/image///opt/px es-0.7/stock/dist/bin/tr: No such file or directory The third error, which I am not sure is related to the ebuild or not, is that the config files for pxes point to the initrd of pxes-0.6.initrd , which is not created when you run pxesconfig. I had to manually edit pxelinux.cfg/default to correct this. A fourth, which again I'm not sure is related to the ebuild, is that when the client boots, /dev/ram which is mounted at / is mounted read only. Checking the fstab which gets sent to the initrd shows that the option ro is passed. I changed this, created a new initrd, tried again, and / was again mounted ro. I checked the fstab after the client booted, and my changes were there. I am not passing the ro option to the kernel, either. Because of this, the entire thin client is rendered useless, as it cannot create any of its temp files, cannot create /proc , etc, etc. I tried to go to the pxes mailing lists, but SF is down for maintenance. There may be more information there when it comes back. Please see the attached log for full details.
Created attachment 21324 [details] portage error log
Update: The problems with / being mounted were normal. The problems where it could not write were not. However, after clearing out everything manually and reinstalling pxes, I did not have this problem. All of the other problems stand, though.
Changint Severity to Normal due to being able to use pxes now.
If you look into the ebuild, RESTRICT=nouserpriv is set. Portage should be turning off userpriv automatically when you emerge pxes, if it isn't, it is a portage bug. The "failed to preserve permissions" errors are actually warnings, and make no difference to the end result. I could pass a --no-preserve-permissions to the unpacking process, but I had that on a previous version and it caused problems, so it was removed. I will post the pxelinux.cfg/default initrd problem to the mailing list as it is an upstream problem. I'm resolving this with UPSTREAM to show that the only standing issue is an upstream problem.
