Date: Sat, 19 Sep 2009 22:36:24 +0200 From: Alexander Leidinger <Alexander@Leidinger.net> To: Alexander Best <alexbestms@math.uni-muenster.de> Cc: freebsd-emulation@freebsd.org Subject: Re: compat.linux.osrelease behavior Message-ID: <20090919223624.00004f42@unknown> In-Reply-To: <permail-20090918130831f0889e8400005dd6-a_best01@message-id.uni-muenster.de> References: <permail-20090918130831f0889e8400005dd6-a_best01@message-id.uni-muenster.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 18 Sep 2009 15:08:31 +0200 (CEST) Alexander Best <alexbestms@math.uni-muenster.de> wrote: > hi there, > > i have a question regarding the behavior of compat.linux.osrelease. > setting it to 2.4.2 sets linuxulator into 2.4 kernel-emulation and > 2.6.16 sets it into 2.6 kernel-emulation right? Sort of. 2.6.x set's 2.6 mode, and everything else is 2.4 mode. But this is AFAIK only a semantic change of some functions. This does not disable syscalls which are in 2.6 but not in 2.4. > but what happens when compat.linux.osrelease gets set to a different > value? ports/Updating entry 20071101 e.g. advises skype users to set > compat.linux.osrelease to 2.4.20. does this trigger 2.6 > kernel-emulation because 2.4.20 > 2.4.2 or are there more than two > kernel-emulation layers inside the linuxulator?? It does not affect the kernel emulation. But the glibc will try to use new syscalls. Bye, Alexander.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090919223624.00004f42>