Package: fai-client
Version: 3.1.8
Severity: wishlist

I like using fcopy for maintaining tarballs of configuration files for a
bunch of hosts.  The "file-modes" file permits me to own/edit/maintain
my repository of configuration files as a non-privileged user because
fcopy, when given a list of classes and run recursively using my
repository as the source, produces a target tree of files with exactly
the right owners, groups, and permissions.

Unfortunately, the owner of the *directories* of the resulting tree is
the un-privileged user and the directory modes are all 755.  This means
that I cannot simply copy the resulting tree to the target machine.
This could be fixed if the "file-modes" file applied to directories as
well as files.

In the meantime, I manage the situation by carefully maintaining the
configuration repository as root with each directory given the right
owner, group, and perms (usually root,root,0755), but I prefer not
depending on root access.

Somebody else already made this request back in November 2004, but not
to the BTS as far as I can see.  Here is the thread:

        https://lists.uni-koeln.de/pipermail/linux-fai/2004-November/002568.html

Thanks in advance for considering this feature request.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (991, 'stable'), (33, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.18-6-vserver-686
Locale: LANG=en_US, LC_CTYPE=fr_CH (charmap=ISO-8859-1)

Versions of packages fai-client depends on:
ii  cfengine2                   2.1.20-1     Tool for configuring and maintaini
ii  file                        4.17-5etch3  Determines file type using "magic"
ii  libapt-pkg-perl             0.1.20       Perl interface to libapt-pkg
ii  perl                        5.8.8-7etch3 Larry Wall's Practical Extraction 

fai-client recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to