Date: Tue, 6 Dec 2011 04:54:18 -0600 From: Zhihao Yuan <lichray@gmail.com> To: Thomas Mueller <mueller6727@bellsouth.net> Cc: Alexander Leidinger <Alexander@leidinger.net>, freebsd-ports@freebsd.org Subject: Re: Linux compatibility with more than one Linux installed? Message-ID: <CAGsORuAa2-b2xrwttEfwei9VJB4GonKM_Evn4RxopGO=i%2BiryA@mail.gmail.com> In-Reply-To: <20111206095325.66342106566C@hub.freebsd.org> References: <eer12xrotnbwco8ti8cfbwy3.1323091614336@email.android.com> <20111206095325.66342106566C@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 6, 2011 at 3:53 AM, Thomas Mueller <mueller6727@bellsouth.net> wrote: >> The X server has a unix socket somewhere in /tmp. Normally this is used = instead of a TCP connection to the localhost. You need to change the DISPLA= Y >> env-variable to use a TCP connection, or you need o make the unix socket= available to the chrooted linux-env. > >> The linuxulator in FreeBSD is nearly linux 2.6.16 compatible. We lack in= otify and epoll support which the 2.6.16 kernel normally supports. If your = system does >> not depend upon inotify, epoll and anything newer than 2.6.16, it should= work. If you give it a try, please report success or failure to >> emulation@FreeBSD.org. > >> Bye, >> Alexander. > > Now I might have something to try, but it is very unlikely that I would b= uild a Linux kernel <=3D 2.6.16, especially with new hardware that might ne= ed the latest drivers. =C2=A0I will primarily want to run Linux natively ra= ther than under FreeBSD. > > I think emulators/linux_dist-gentoo-stage3 and emulators/linux_base-gento= o-stage3 must use kernel far beyond 2.6.16. > > But I think, when chrooting into Linux from FreeBSD, FreeBSD kernel is th= e one in effect. > Not really. The actual thing is, linuxulator is a Linux kernel running as a FreeBSD kernel module. The only thing FreeBSD kernel do is to identify the Linux program and to pass it to the Linux kernel. To the Linux programs inside a GNU chroot enviroment, they think they are running inside a Linux box and actually they are running inside a Linux box. To the Linux programs running under a FreeBSD base, they may identify that the base is not GNU by invoking some external programs like `uname`. However, we can replace their sh with /compat/linux/bin/sh, so that they are blind again. > Tom > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" --=20 Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___________________________________________________ 4BSD -- http://4bsd.biz/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGsORuAa2-b2xrwttEfwei9VJB4GonKM_Evn4RxopGO=i%2BiryA>