Date: Thu, 12 Apr 2007 11:58:11 +0200 From: Roman Divacky <rdivacky@FreeBSD.ORG> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: freebsd-emulation@FreeBSD.ORG, Oliver Fromme <olli@lurza.secnetix.de>, freebsd-ports@FreeBSD.ORG, bsam@FreeBSD.ORG Subject: Re: Printing with Acrobat Reader Message-ID: <20070412095811.GA87726@freebsd.org> In-Reply-To: <20070412115026.sx5tdm2aogss4kkc@webmail.leidinger.net> References: <200704120913.l3C9D5lA060207@lurza.secnetix.de> <20070412115026.sx5tdm2aogss4kkc@webmail.leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Acroread will use linux system calls to start the shell. This results > in the linux shell (/compat/linux/bin/sh) to start (linuxulator > directory prefixing). The linux shell will use the same linuxulator > directory prefixing to start /compat/linux/usr/bin/lpr. So we're in > the same situation like with Acroread. So when you play around with it > also try to not specify a path to the lpr call and tell us which one > works. this is not entirely true (or I just read it wrong). it works like this any binary (fbsd or linux) can run any binary (fbsd or linux). its just that when linux binary wants to run "xyz" it searches /compat/linux first and then falls back to / just a clarification
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070412095811.GA87726>