From owner-freebsd-emulation@FreeBSD.ORG Wed Feb 11 02:12:44 2015 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 43081306 for ; Wed, 11 Feb 2015 02:12:44 +0000 (UTC) Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0C06FD4D for ; Wed, 11 Feb 2015 02:12:44 +0000 (UTC) Received: by mail-pa0-f48.google.com with SMTP id eu11so938241pac.7 for ; Tue, 10 Feb 2015 18:12:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=m8L010MvAFKt7i285lcaP5IxS1LBcC2jq0Qmsk1gNR8=; b=Lpz35U612MFcRqlmR+Fo6uaq+KfMK0TyWj42RPuZAhLlLdt7YKe0DNL7G3RW7lhej9 /OhvamPFvFhOj4ObRLrf3xcUrLE1jPFK6Gn7CaAzttmBKAqFzuO/i2TpafzhOZb2N0aC +maoBYCnWBw88pHZvejse1kf92DCcPNDgSDDpjeZJXD9/2mu1zYmd/hULUwoDinNsfCI YWNiWB1n4tlxGFS0C91Isfki9nf8k1sbDswvk78UV+Q7U1e88EQZF9UVh9gW5PdNLHa8 /kxylbfja/Wkb7joIZrK1rtq5EGi8oCnAPXuV1B/wvPVYkwbzp9PNpVeaoAaNhc5Rl/i j49A== MIME-Version: 1.0 X-Received: by 10.70.45.9 with SMTP id i9mr43136738pdm.132.1423620763600; Tue, 10 Feb 2015 18:12:43 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.67.22.231 with HTTP; Tue, 10 Feb 2015 18:12:43 -0800 (PST) In-Reply-To: References: <54D4EF23.7050604@astart.com> <20150208111022.4094218f@ernst.home> <54DA6B4B.6080708@astart.com> Date: Tue, 10 Feb 2015 18:12:43 -0800 X-Google-Sender-Auth: 6UxKVNkXbv2XQXhyJxzdA-0_OOI Message-ID: Subject: Re: /compat/linux and /usr/compat/linux From: Kevin Oberman To: Chris H Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: gljennjohn@gmail.com, "freebsd-emulation@freebsd.org" X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2015 02:12:44 -0000 On Tue, Feb 10, 2015 at 2:54 PM, Chris H wrote: > On Tue, 10 Feb 2015 12:34:19 -0800 Patrick Powell > wrote > > > On 02/08/15 02:10, Gary Jennejohn wrote: > > > On Fri, 06 Feb 2015 08:43:15 -0800 > > > Patrick Powell wrote: > > > > > >> The latest linux-base appears to install into /compat, rather than > > >> /usr/compat > > >> > > >> However, some FreeBSD FAQ and other documents appear to refer to > > >> /usr/compat. > > >> > > >> Question: when did the move from using /usr/compat to /compat take > > >> place (just out of curiosity)? > > >> > > >> Question: can linproc be in /compat/linux/proc or > /usr/compat/linux/proc? > > >> Question: if you have a /usr/compat/linux/lib directory will this be > > >> added to the > > >> libraries for linux emulation? > > >> > > > /compat has historically always been a symbolic link to /usr/compat: > > > > > > lrwxr-xr-x 1 root wheel 10 Nov 25 2011 /compat -> usr/compat > > > > > > linprocfs on /usr/compat/linux/proc (linprocfs, local) > > > but in my /etc/fstab I have > > > linproc /compat/linux/proc linprocfs rw 0 > 0 > > > > > > Since /compat is a symbolic link it resolves to /usr/compat when it's > > > used. > > > > > # uname -a > > FreeBSD astart2.astart.com 9.3-RELEASE-p9 FreeBSD 9.3-RELEASE-p9 #0: Tue > > Jan 27 10:43:40 UTC 2015 > > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > > > # ls -l / |grep compat > > > > drwxr-xr-x 3 root wheel 512 Dec 3 14:41 compat > > > > # ls -l /usr |grep compat > > drwxr-xr-x 3 root wheel 512 Nov 21 21:06 compat > > > > Note that neither /compat or /usr/compat are symbolic links. > Interesting. On a RELENG_9 (9.3-STABLE); I only return > /compat > no linux, or compat available in /usr > So what's the *real* story behind all this? > > > ls -ld /compat lrwxr-xr-x 1 root wheel 11 Feb 8 09:18 /compat@ -> /usr/compat It is NOT created by the OS or any port, as far as I know. By default the installation of an emulators/linux_base-* port will create /compat. Because it can become fairly large and is in root, it was recommended some time ago that /usr/compat be created and the contents of /compat be moved there, /compat be deleted, and a symlink be created. Unless something was changed, his is up to the user. If you have both and neither is a symlink, something was not done right at some point. Once the symlink is in place, neither an upgrade or install of a linux_base-* port will affect it at all. It can significantly reduce the space required in root. I suppose it is possible that some linux ports may be installing stuff in /usr/compat/linux instead of /compat/linux so that both show up if /compat/linux is still in use. I hope this is not the case. -- Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com