On Wednesday 01 October 2008, 11:25:24, Julien Cristau wrote: > On Wed, Oct 1, 2008 at 11:18:53 +0200, Marco Amadori wrote: > > Ok, but useradd should chown them when the user is created at runtime. Do > > you see wrong uid in the RUNNING system? > > I'm talking about the files in /etc, not the ones in /home. That is, > /etc itself, /etc/skel, and all the files under that on the cd have my > uid from the system where I built the cd, which is pretty weird IMO.
Ok, so there is not a bug there. > > Anyway, lh_chroot_local-includes should not change permissions IMHO, you > > should change them with a l-h's hook and not for your use case. > I'm not talking about changing permissions, I'm talking about changing > ownership, Yes, I'm sorry, I meant both. > because uids on the live system and on the host are > unrelated, so preserving ownership doesn't make any sense as far as I > can tell. You ask for a feature/bug* that all files under "chroot_local_includes" should be copied with UID/GID 0/0 ? Then anyone who needs to set UID/GID for "chroot_local_includes" files should explicit do/redo it in a live.helper hook instead of trusting "chroot_local_includes" owners? I could be fine with that, but I let Daniel and other devs choose for that question, I see both advantages and complications in changeing the mode in which files are copied in. * bug since someone (e.g. me for a couple of systems) could have a build system which exploit this beaviour. -- ESC:wq -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
