Hi Craig,
Thanks for your recommendation but unfortunately it has not worked.  Should I use the device_table.txt file exclusively and hence remove the user home directory under target/generic/target_skeleton/home?

On 8/7/07, Craig Hughes <craig@gumstix.com> wrote:
On Aug 7, 2007, at 11:22 AM, C D wrote:

> Hello,
> I wish to automatically create user accounts (including associated
> home directories) and incorporate them into the filesystem image
> that is created by the buildroot.  I'm currently doing this by
> putting the necessary entries into the files: passwd, shadow and
> group under target/generic/target_skeleton/etc within the buildroot.
> To get the home directories, I've created user directories under
> target/generic/target_skeleton/home and set their ownership
> permissions appropriately.  The user home directories get created
> with the correct permissions under build_arm_nofpu/root/home but
> when I flash the filesystem on to the Verdex, the ownership
> permissions are set to "root:root".
> My technique is clearly nasty and flawed since it requires the same
> user accounts to exist on the host machine that is used to build
> the Verdex filesystem - is there a better way of adding users and
> their home directories?  If not, how can I get the home directories
> to retain the correct ownshership permissions (without having an
> even nastier "chown <dir> <user>:<user>" command somewhere in the
> startup scripts)?
> Any advice is much appreciated.  Thanks in advance,

Take a look at the file



This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>   http://get.splunk.com/
gumstix-users mailing list