From f6aa1fb87bea3b930c4f1d5039dc58d76f170bd8 Mon Sep 17 00:00:00 2001 From: Alexander Leidinger Date: Wed, 2 Jan 2008 15:22:26 +0000 Subject: [PATCH] Add some more infos: - textdump in 8-current in the automatic crash reporting entry - FEATURE macro in 8-current for the kernel features entry - bsdtar mtree extensions for the non-root release building entry[1] Discussed with: kientzle --- en/projects/ideas/ideas.xml | 39 ++++++++++++++++++++++++++----------- 1 file changed, 28 insertions(+), 11 deletions(-) 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" - $FreeBSD: www/en/projects/ideas/ideas.xml,v 1.31 2007/11/09 13:01:54 netchild Exp $ + $FreeBSD: www/en/projects/ideas/ideas.xml,v 1.32 2007/11/09 16:39:33 netchild Exp $ @@ -170,11 +170,14 @@ Ideas//EN" information (of course, automatic reporting has to be explicitly enabled by individual system administrators, and should have at least three options: not to send out anything at all as a default, send out after - administrator confirmation, and automatically send all necessary information)

+ administrator confirmation, and automatically send all necessary information). + The FreeBSD kernel in 8-current has the textdump feature which may + be interesting to use for this part

-

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: