From owner-freebsd-emulation Sun Apr 22 13:53:57 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 7798937B424; Sun, 22 Apr 2001 13:53:54 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.3/8.11.3) with SMTP id f3MKsPf81871; Sun, 22 Apr 2001 16:54:25 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 22 Apr 2001 16:54:25 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: marcel@FreeBSD.org Cc: emulation@FreeBSD.org Subject: Linux-specific jail code in linuxulator Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Marcel, I'm in the process of rewriting large sections of the FreeBSD jail(8) code to improve its management capability, make it SMPng-safe, etc. The jail code includes some linuxulator-specific adaptations -- in particular, the ability to specify per-jail MIB entries: struct linux_prison { char pr_osname[LINUX_MAX_UTSNAME]; char pr_osrelease[LINUX_MAX_UTSNAME]; int pr_oss_version; }; CVS annotate on linux_mib.c indicates that these features were present in 1.1 of the file when it was originally added, so I was wondering if (a) you were the author of the code and (b) what you knew about its use. Since I'm rewriting largely from scratch (although keeping fairly close to the original implementation when it comes to most features), now appears to be the opportunity to determine if these features are used, if so whether they are useful. Apparently they weren't part of Poul-Henning's orginal implementation, so I assume they were added later. If they are used, I should make sure to include them in the revised version, and possibly clean up interactions between optional components (such as sysvipc, linuxlator, etc) and jail. If they're not used, removing them makes sense because they do introduce complexity (especially in light of fine-grained threading/protection in the kernel). Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message