Date: Wed, 20 Sep 2006 13:48:48 -0600 From: John E Hein <jhein@timing.com> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: freebsd-emulation@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: linux cross-development (was: Re: /dev/null: No such file or directory) Message-ID: <17681.39712.119019.147240@gromit.timing.com> In-Reply-To: <20060920212442.41c9ed0f@Magellan.Leidinger.net> References: <20060918230348.I1031@ganymede.hub.org> <20060919022530.GA44301@lor.one-eyed-alien.net> <20060919092117.8asq42ers44w4wgg@webmail.leidinger.net> <20060920014127.GA52449@xor.obsecurity.org> <20060920102554.mxditjplogkscw44@webmail.leidinger.net> <20060920182156.GA83026@xor.obsecurity.org> <20060920212442.41c9ed0f@Magellan.Leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Alexander Leidinger wrote at 21:24 +0200 on Sep 20, 2006: > Any ideas how to provide a chroot while not losing the fallthrough if > not chrooted (and we try to identify other files/dirs where we want a > fallthrough)? That smells a little like unionfs. FWIW, I'd like to see a resurrection of linux_devtools or some equivalent. >From a system building perspective, it seems difficult to build a system in an automated way (as in a product) that needs to build apps compiled for linux. We build packages in a FreeBSD chroot and pkg_add -p them into an image hierarchy (which is then copied to the target media, typically a Compact Flash). So, if we wanted to deploy a system that has linux_base and some linux-compiled apps, we'd have to build the linux_base .tgz package in our build chroot, pkg_delete it, then install linux_dist in order to compile linux apps (there are some closed linux libs we need to link with otherwise we'd just compile the apps as freebsd). Maybe there's an easier way, but if not, it would require changes to our build infrastructure here. This is one reason I haven't updated to the latest linux ports infrastructure for our products yet. It's getting more difficult to stay that course, however, as ports/Mk, et. al., diverges from our snapshot.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17681.39712.119019.147240>