| Summary: | Meet error message prompt when extracting qemu root fs | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | liping Ke <liping.ke> |
| Component: | core | Assignee: | Mark Hatle <mark.hatle> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | minor | ||
| Priority: | Medium | CC: | jessica.zhang, kevin.tian, lianhao.lu, liping.ke, mark.hatle, meta.mr.watcher, meta.watcher, sgw, susie.li |
| Version: | 0.9 | ||
| Target Milestone: | 0.9 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Program Management | Documentation change: | --- |
|
Description
liping Ke
2010-08-25 20:33:48 UTC
pseudo is supposed to handle fifos. So this should not be a problem. Can you look at /home/lke/unfs/kernels/ and tell me what filesystem that mount point is using? There are some filesystem types that do not support fifos. If you happen to be using one this could trigger that error. Confirmed with the pseudo author this is a defect in pseudo. Upstream is working on a fix.... I am unable to run the command: poky-extract-sdk tmp/deploy/images/poky-image-sdk-qemux86.tar.bz2 What is the configure, commands and steps to generate the poky-image-sdk-qemux86.tar.bz2 file? I have tried simply running bitbake poky-image-sdk, and I get a .hdimage file, not a tar.bz2. Fixed in upstream commit: e3765ee9c9c2bccaa32fbe6426d4eb1bbcd214e7 Pull request for the fix will be submitted soon. Fix has been checked in... Hi, Mark Did not see the e3765ee9c9c2bccaa32fbe6426d4eb1bbcd214e7 on the poky/master tree. Is this the commit number of contrib master? I still meet this error with poky/master last Friday tree. I will verify the latest cs on Monday. When verified, I will change status to verified. Thanks, criping Verified this bug has been fixed with latest tip of master. (cs: d1ff9aa4f, Sep 16, RP). |