Date: Thu, 21 Sep 2006 08:12:39 +0200 From: Alexander Leidinger <Alexander@Leidinger.net> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-emulation@freebsd.org Subject: Re: linux cross-development (was: Re: /dev/null: No such file or directory) Message-ID: <20060921081239.golv9vl58gococko@webmail.leidinger.net> In-Reply-To: <20060920200215.GA84299@xor.obsecurity.org> 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> <20060920200215.GA84299@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Kris Kennaway <kris@obsecurity.org> (from Wed, 20 Sep 2006 =20 16:02:15 -0400): > Actually none of these seem to be critical for typical compilation > needs, except for /dev and /tmp. The former you'll have to mount > devfs to supply (in principle linux_devtools can do this > automatically, by startup script), and you can make linux_devtools > create a /compat/linux/tmp to handle that problem too (it's not ideal > to have it use a private /tmp, but not a big deal either). Try to print something in acroread while having /compat/linux/tmp. =20 Acroread will use the linux tmp while the FreeBSD native lpr command =20 (configured in acroread to be able to print something) searches in the =20 FreeBSD tmp. Currently you don't need to mount anything for a lot of linux programs =20 to work just fine. I like to keep it this way as long as possible. The common case is that people just use the linux base to run linux =20 programs, and not to cross-develop something. What's the problem to =20 tell those people which want to cross-develop something to use the =20 linux_dist ports? Maintaining linux_base as it is is not hard (if you =20 know the pitfalls and some design decissions). Maintaining linux_dist =20 is easy too (it borrows a lot of knowledge from linux_base). =20 Maintaining a linux_base and a linux_devtools port which uses the =20 linux_base port is much harder than maintaining distinct linux_base =20 and linux_dist ports. And distinct ports don't cause as much problems =20 (see the icc part below for an example) as a combination. > Kris > > P.S. I'm not sure that falling through some of the etc/ files will > DTRT, since Linux may require a different file format. Passwd seems to be compatible enough for GTK to not complain (it =20 complains when someone uses NIS but hasn't setup the corresponding =20 linux config file, I don't know if this NIS config is compatible so =20 that we could depend upon a fallthrough). The printer configuration is =20 not necessary to be compatible, we use the FreeBSD native print =20 commands. BTW: ATM we have CONFLICTS between icc and linux_devtools. Icc is a =20 linux binary which generates FreeBSD native binaries. When =20 linux_devtools is installed icc picks up linux stuff and can't =20 generate FreeBSD native binaries. Not a major problem, but a nuisance =20 for those which want to use both. Bye, Alexander. --=20 I've always made it a solemn practice to never drink anything stronger than tequila before breakfast. =09=09-- R. Nesson http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060921081239.golv9vl58gococko>