os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add some more infos:

Browse source 
- 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
This commit is contained in:
Alexander Leidinger 2008-01-02 15:22:26 +00:00
parent a688a3ffa4
commit f6aa1fb87b
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=31216
1 changed files with 28 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

39
en/projects/ideas/ideas.xml
View file

@ -15,7 +15,7 @@ Ideas//EN"
<ideas>
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
<cvs:keyword name="freebsd">
$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 $
</cvs:keyword>
</cvs:keywords>
@ -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)</p>
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</p>
<p>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
<p>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.</p>
<p><strong>Requirements</strong>:</p>
@ -771,11 +774,15 @@ they all need to be locked.</p>
<p>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.</p>
with COMPAT_FREEBSD5). All such optional kernel features need to
register themselves with the <a
href="http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/sys/sysctl.h.diff?r1=1.154;r2=1.155;f=h">FEATURE
macro</a> so that the userland can easily query whether a given
feature is present. So far not all kernel features are using this
infrastructure.</p>
<p>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.</p>
<p><strong>Requirements</strong>:</p>
<ul>
<li>Good knowledge of C.</li>
@ -1769,12 +1776,22 @@ SMP features.</p>
<desc>
<p><strong>Technical contact</strong>: <a
href="mailto:rwatson@FreeBSD.org">Robert Watson</a>, <a
href="mailto:cperciva@FreeBSD.org">Colin Percival</a></p>
href="mailto:cperciva@FreeBSD.org">Colin Percival</a>, <a
href="mailto:kientzle@FreeBSD.org">Tim Kientzle</a></p>
<p>Instead 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.</p>
<p>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.</p>
<p><strong>Requirements</strong>:</p>
<ul>
<li>No fear regarding our installation system.</li>