openembedded-core.git/scripts/runqemu-export-rootfs, branch jethro Mirror of openembedded-core runqemu-export-rootfs: update location of unfsd binary 2015-10-29T07:27:41+00:00 Maxin B. John maxin.john@intel.com 2015-10-27T15:54:30+00:00 2e98b80a3a11798145f58c8ccc8b873cd713f4f2 oe-core commit: 24b80d211f3808a0ffebee426932f11b8d4d46e0 sets sbindir = "${bindir}" in the nativesdk class. So, update the location of unfsd binary from "/usr/sbin" to "/usr/bin" in runqemu-export-rootfs. Also update unfs3-native to install unfsd under "bin" directory so the binary is always in the same location. [YOCTO #8315] Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
oe-core commit: 24b80d211f3808a0ffebee426932f11b8d4d46e0 sets
sbindir = "${bindir}" in the nativesdk class.

So, update the location of unfsd binary from "/usr/sbin" to "/usr/bin" in
runqemu-export-rootfs. Also update unfs3-native to install unfsd under
"bin" directory so the binary is always in the same location.

[YOCTO #8315]

Signed-off-by: Maxin B. John <maxin.john@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Revert "runqemu-export-rootfs: update location of unfsd binary" 2015-10-24T11:42:33+00:00 Ross Burton ross.burton@intel.com 2015-10-21T21:14:49+00:00 2e065b02a3e65c8db8a26788fdc4d7f65d5a2a8f unfsd appears to be moving around and is in sbin for at least two different users, so revert the change to expect it in bin. This reverts commit e56bda210e216251c04d872211081a89ac06dde6. Signed-off-by: Ross Burton <ross.burton@intel.com> 
unfsd appears to be moving around and is in sbin for at least two different
users, so revert the change to expect it in bin.

This reverts commit e56bda210e216251c04d872211081a89ac06dde6.

Signed-off-by: Ross Burton <ross.burton@intel.com>
runqemu-export-rootfs: update location of unfsd binary 2015-09-28T10:58:32+00:00 Maxin B. John maxin.john@intel.com 2015-09-24T10:48:12+00:00 e56bda210e216251c04d872211081a89ac06dde6 Update the location of unfsd binary from "/usr/sbin" to "/usr/bin" in runqemu-export-rootfs [YOCTO #8315] Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
Update the location of unfsd binary from "/usr/sbin" to "/usr/bin" in
runqemu-export-rootfs

[YOCTO #8315]

Signed-off-by: Maxin B. John <maxin.john@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
runqemu-export-rootfs: Fix missing # in comment 2014-02-20T11:58:19+00:00 Saul Wold sgw@linux.intel.com 2014-02-20T07:08:25+00:00 38785af0ca0b020574b32b9e3b21129469a35c94 Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
runqemu-export-rootfs: update for unfs3 2014-01-28T00:48:28+00:00 Jason Wessel jason.wessel@windriver.com 2014-01-23T14:32:45+00:00 ea126a7d4a63e27755046ddd2eb0be079e20c334 The unfs3 no longer has an rpc.mountd component. There is just a single server for mountd and nfsd requests. This means changing the name of the server in the scripts that check for it. [YOCTO #5639] Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> 
The unfs3 no longer has an rpc.mountd component. There is just a
single server for mountd and nfsd requests.  This means changing
the name of the server in the scripts that check for it.

[YOCTO #5639]

Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
runqemu: Use the newer unfs3 for serving user space nfs 2014-01-28T00:48:27+00:00 Saul Wold sgw@linux.intel.com 2014-01-23T14:32:43+00:00 2a59d55f712bbd79b1edf3ccb90ccabf609c9f0d This new version correctly handles the 64bit ext3 / ext4 issues we were seeing with the older unfs-server which did not handle 64bit file systems correctly, producing the duplicate cookies. [YOCTO #5639] Signed-off-by: Saul Wold <sgw@linux.intel.com> 
This new version correctly handles the 64bit ext3 / ext4 issues we
were seeing with the older unfs-server which did not handle 64bit file
systems correctly, producing the duplicate cookies.

[YOCTO #5639]

Signed-off-by: Saul Wold <sgw@linux.intel.com>
runqemu: allow multiple unfs instances to run simultaneously 2012-10-04T13:10:40+00:00 Scott Garman scott.a.garman@intel.com 2012-10-03T22:13:53+00:00 94eef772c283170d19ba92c8de0054cd093fc487 A miscalculation in the way the port numbers of mountd and nfsd are created was causing conflicts when starting multiple instances of qemu using userspace nfs. Thanks to Rudolf Streif for proposing this fix! Fixes [YOCTO #1969] Signed-off-by: Scott Garman <scott.a.garman@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
A miscalculation in the way the port numbers of mountd and nfsd
are created was causing conflicts when starting multiple instances
of qemu using userspace nfs.

Thanks to Rudolf Streif for proposing this fix!

Fixes [YOCTO #1969]

Signed-off-by: Scott Garman <scott.a.garman@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
runqemu-export-rootfs: improve rpcbind error detection 2012-10-04T13:10:21+00:00 Scott Garman scott.a.garman@intel.com 2012-10-03T22:13:52+00:00 16d6ec51f4b976c9b86a8b6bf6251089df2d2732 mountd requires rpcbind or portmap. Check that one of these services is running before doing anything else, and report a user-friendly error when they are not found. Signed-off-by: Scott Garman <scott.a.garman@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
mountd requires rpcbind or portmap. Check that one of these
services is running before doing anything else, and report
a user-friendly error when they are not found.

Signed-off-by: Scott Garman <scott.a.garman@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
runqemu-export-rootfs: use consistent whitespace 2012-10-04T13:09:39+00:00 Scott Garman scott.a.garman@intel.com 2012-10-03T22:13:51+00:00 b05185240669e0ae811a23620913b35ca99493fb Signed-off-by: Scott Garman <scott.a.garman@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Signed-off-by: Scott Garman <scott.a.garman@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
runqemu-export-rootfs and friends: don't put pseudo db in target fs 2012-08-28T15:03:41+00:00 Peter Seebach peter.seebach@windriver.com 2012-08-27T18:32:30+00:00 aa5d6bd006d3b4eede21d8987451876ed3385ab8 In a few places, we have scripts which use <rootfs>/var/pseudo for the pseudo state directory controlling a given filesystem. This seems possibly risky because it means that stuff running under qemu or whatnot could wipe out the data being used to handle that rootfs. Move this to: <rootfs>/../$(basename_rootfs).pseudo_state to avoid problems. This also solves at least one case (not directly hit by yocto's tree) wherein you could end up trying to remove a rootfs while pseudo was using a database inside that rootfs, and thus the remove would fail. Signed-off-by: Peter Seebach <peter.seebach@windriver.com> 
In a few places, we have scripts which use <rootfs>/var/pseudo for
the pseudo state directory controlling a given filesystem. This
seems possibly risky because it means that stuff running under
qemu or whatnot could wipe out the data being used to handle that
rootfs. Move this to:
  <rootfs>/../$(basename_rootfs).pseudo_state
to avoid problems.

This also solves at least one case (not directly hit by yocto's
tree) wherein you could end up trying to remove a rootfs while
pseudo was using a database inside that rootfs, and thus the
remove would fail.

Signed-off-by: Peter Seebach <peter.seebach@windriver.com>