> -----Original Message-----
> From: Patrick Ohly [mailto:[email protected]]
> Sent: Thursday, January 29, 2015 7:28 AM
> To: LIYONG; Schaufler, Casey
> Cc: [email protected]
> Subject: Re: [Dev] Cannot generate the bootable u-disk using the .hddimg file
> - system.posix_acl_default xattr
>
> On Fri, 2015-01-23 at 16:07 +0100, Patrick Ohly wrote:
> > On Fri, 2015-01-23 at 21:22 +0800, LIYONG wrote:
> > > Hi Patrick,
> > >
> > > I am using the latest "source ./tizen-common-init-build-env" command to
> build the core minimal image.
> > > Using the mkefidisk.sh script in the yocto project to create the
> > > bootable u-disk. The host OS is Ubuntu 14.04
> >
> > Sorry, I am not familiar with mkefidisk.sh. So far, only the method of
> > manually creating an USB image as described in the Wiki page has been
> > tested.
> >
> > The strace output indicates problems with copying xattr attributes.
> > Perhaps that gives someone an idea.
>
> I tried it myself and can reproduce the issue. I used
> http://dominion.thruhere.net/koen/angstrom/minnow/mkefidisk.sh as linked
> to by http://www.elinux.org/Installing_Angstrom_on_a_Hard_Disk
>
> The image was a "Tizen on Yocto" image that I just created myself.
>
> In my case, the error is:
>
> Copying ROOTFS files...
> cp: 'mkefidisk-wKZ/hddimg_rootfs/var/volatile/log': Invalid argument
> Preparing boot partition...
> Installation complete.
>
> The version of the script that I used lacks error checking, that's why
> it continues. It also does not work with /bin/sh -> dash; I manually ran
> it under bash. Which version where you using?
>
> When comparing the /var/volatile/log in the image that gets copied from
> (rootfs in my case) and the result of "cp -a" (target here), I see:
>
> # xattr -lz /tmp/*/var/volatile/log
> /tmp/rootfs/var/volatile/log: No such xattr: system.posix_acl_default
> /tmp/rootfs/var/volatile/log: security.SMACK64: System::Log
> /tmp/rootfs/var/volatile/log: security.SMACK64TRANSMUTE: TRUE
> /tmp/target/var/volatile/log: security.SMACK64: System::Log
> /tmp/target/var/volatile/log: security.SMACK64TRANSMUTE: TRUE
>
> Casey, do you have any idea what this "No such xattr:
> system.posix_acl_default" error might be about? Is it a problem that it
> did not get copied?
Without looking to deeply into the problem,
I suspect that either the system you're running on
doesn't support POSIX ACLs, the filesystem you're
reading from doesn't support them, or the
filesystem you're writing to does not support them.
> I'm not getting it for other entries in the filesystem.
>
> The error shows up in strace as:
>
> # strace xattr -lz /tmp/rootfs/var/volatile/log
> ...
> listxattr("/tmp/rootfs/var/volatile/log", NULL, 0) = 68
> listxattr("/tmp/rootfs/var/volatile/log",
> "system.posix_acl_default\0securit"...,
> 68) = 68
> getxattr("/tmp/rootfs/var/volatile/log", "system.posix_acl_default", 0x0, 0)
> = -
> 1 EINVAL (Invalid argument)
> stat("/tmp/rootfs/var/volatile/log", {st_mode=S_IFDIR|0755, st_size=4096,
> ...})
> = 0
> write(2, "No such xattr: system.posix_acl_"..., 40No such xattr:
> system.posix_acl_default) = 40
> ...
>
> I run this on Debian Testing, Linux kernel 3.16.0-4-amd64.
>
> --
> Best Regards, Patrick Ohly
>
> The content of this message is my personal opinion only and although
> I am an employee of Intel, the statements I make here in no way
> represent Intel's position on the issue, nor am I authorized to speak
> on behalf of Intel on this matter.
>
>
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
