diff --git a/en/projects/ideas/ideas.xml b/en/projects/ideas/ideas.xml
index c9df53b4d3..837bdc3d71 100644
--- a/en/projects/ideas/ideas.xml
+++ b/en/projects/ideas/ideas.xml
@@ -15,7 +15,7 @@ Ideas//EN"
Another part is the server side one, which will keep a database of backtraces - where similar (call stack minus addresses) reports are kept together and be - considered as a "vote", to make it possible for developers and release engineers +
Another part after the first one is finished is the server side one, + which will keep a database of backtraces where similar (call stack + minus addresses) reports are kept together and be considered as a + "vote", to make it possible for developers and release engineers to focus on the most commonly triggered issues.
Requirements:
@@ -771,11 +774,15 @@ they all need to be locked.Currently there is no way for e.g., a port makefile to tell whether things like FreeBSD 5.x compatibility are present on the system (just installing the compat5x port is not enough, you need a kernel built - with COMPAT_FREEBSD5). All such optional kernel features should - register themselves in a common location (e.g. sysctl MIB) so that - the userland can easily query whether a given feature is present. There - needs also to be a way to spoof those values, e.g., when the ports build - cluster is building for older FreeBSD versions in a jail.
+ with COMPAT_FREEBSD5). All such optional kernel features need to + register themselves with the FEATURE + macro so that the userland can easily query whether a given + feature is present. So far not all kernel features are using this + infrastructure. +There needs also to be a way to spoof those values, e.g., when the + ports build cluster is building for older FreeBSD versions in a jail. + Suport for this is not available in the FEATURE macro.
Requirements:
Technical contact: Robert Watson, Colin Percival
+ href="mailto:cperciva@FreeBSD.org">Colin Percival, Tim KientzleInstead of installing using install, mkdir, mtree, etc, directly construct a tarball. This would allow creating install distributions without root access, as setuid etc would never hit the local disk. This would require some retrofitting of our installation mechanisms.
+Bsdtar now (8-current, 20080101) has a feature that allows it to create + a tar archive from a description provided in the form of an mtree file. + This description can specify owner, permissions, and + contents for each entry and does not require the files + on disk to already have correct ownership. This should + make it possible to build a FreeBSD distribution as a + non-root user. Talk to Tim Kientzle for details of the new bsdtar + features and look at NetBSD, which has a similar facility, for + ideas about how to proceed.
Requirements: