Date: Thu, 21 Sep 2006 08:15:22 +0200 From: Alexander Leidinger <Alexander@Leidinger.net> To: "Marc G. Fournier" <scrappy@freebsd.org>, gkovesdan@t-hosting.hu 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: <20060921081522.zbnr13vhu88wws84@webmail.leidinger.net> In-Reply-To: <20060920184438.I1031@ganymede.hub.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> <20060920184438.I1031@ganymede.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting "Marc G. Fournier" <scrappy@freebsd.org> (from Wed, 20 Sep =20 2006 18:45:09 -0300 (ADT)): > On Wed, 20 Sep 2006, Alexander Leidinger wrote: > >> Quoting Kris Kennaway <kris@obsecurity.org> (from Tue, 19 Sep 2006 =20 >> 21:41:27 -0400): >> >>> What happened to the linux_devtools port (which is supposed to take >>> care of this) - was it never updated to parity with linux_base? >> >> No. There are several reasons. >> >> The current devtools port is a mess and interfered with the old =20 >> linux_base port in undesirable ways (can't remember exactly how, I =20 >> would have to have a look at it again). Bringing it into shape =20 >> would be a lot of work (nobody stepped up so far, but I didn't =20 >> asked for help for this because of the next reason). >> >> To cross-develop you need a full system, the linux_base port is a =20 >> lean and mean system. The current linux_base port is designed to =20 >> extend the FreeBSD system and to provide a good user experience for =20 >> those ports which are available in the ports collection (and most =20 >> probably for a lot of other applications). We rely on the =20 >> fallthrough to the native stuff in various places (e.g. we have =20 >> symlinks to the corresponding FreeBSD configs where it applies). =20 >> Doing a chroot into /compat/linux may work for some use cases, but =20 >> not for all (and you need to do a chroot for cross-compiling, else =20 >> you may pickup FreeBSD native stuff and get a lot of trouble) and =20 >> it is not advised to to a chroot into it (I should add a note about =20 >> this to the port...). >> >> The linux_dist ports are full linux systems. You can chroot into =20 >> them and you already have all you need (and you can use the gentoo =20 >> package-stuff to add additional stuff). > > Just curious, but why are the linux_dist ports trying to create devices > in the dev directory? shouldn't one be using devfs to mount devices? Good question. I agree with the devfs part. Let's as the maintainer (CCed). Bye, Alexander. --=20 (1)=09If it's green or it wiggles, it's biology. (2)=09If it stinks, it's chemistry. (3)=09If it doesn't work, it's physics. 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?20060921081522.zbnr13vhu88wws84>