Run the developers summit file through ispell
Submitted by: Hiten Panyda <hiten@uk.FreeBSD.org>
This commit is contained in:
Tom Rhodes
parent
fd2307e27e
commit
5d97d31c83
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=12918
1 changed files with 25 additions and 25 deletions
|
|
@ -1,6 +1,6 @@
|
||||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
|
||||||
<!ENTITY base CDATA "../..">
|
<!ENTITY base CDATA "../..">
|
||||||
<!ENTITY date "$FreeBSD: www/en/events/2002/bsdcon-devsummit.sgml,v 1.4 2002/03/18 17:46:50 rwatson Exp $">
|
<!ENTITY date "$FreeBSD: www/en/events/2002/bsdcon-devsummit.sgml,v 1.5 2002/04/13 14:32:46 rwatson Exp $">
|
||||||
<!ENTITY email 'hackers'>
|
<!ENTITY email 'hackers'>
|
||||||
<!ENTITY title "BSDCon 2002 FreeBSD Developer Summit">
|
<!ENTITY title "BSDCon 2002 FreeBSD Developer Summit">
|
||||||
<!ENTITY stylesheet "&base;/events/events.css">
|
<!ENTITY stylesheet "&base;/events/events.css">
|
||||||
|
|
@ -155,7 +155,7 @@
|
||||||
with symbols renamed. Newbus is an OO type framework was and was
|
with symbols renamed. Newbus is an OO type framework was and was
|
||||||
half way there. KOBJ and Newbus work today with a table of methods.
|
half way there. KOBJ and Newbus work today with a table of methods.
|
||||||
To invoke a method an indirection is done to a lookup. This makes
|
To invoke a method an indirection is done to a lookup. This makes
|
||||||
it so that the nvoker doest not need to know where the invoked
|
it so that the invoker doest not need to know where the invoked
|
||||||
method is.</p>
|
method is.</p>
|
||||||
|
|
||||||
<p>The extension that was added is that instead of a single table it's
|
<p>The extension that was added is that instead of a single table it's
|
||||||
|
|
@ -430,7 +430,7 @@
|
||||||
its easier to build from there.</p>
|
its easier to build from there.</p>
|
||||||
|
|
||||||
<p><strong class="speaker">Benno</strong> : The other note that I will
|
<p><strong class="speaker">Benno</strong> : The other note that I will
|
||||||
make is that I'm only targetting PowerPC similar to 700.</p>
|
make is that I'm only targeting PowerPC similar to 700.</p>
|
||||||
|
|
||||||
<p><strong class="speaker">Warner</strong> : I was going to comment
|
<p><strong class="speaker">Warner</strong> : I was going to comment
|
||||||
that NetBSD has done well with little tiny ports to different
|
that NetBSD has done well with little tiny ports to different
|
||||||
|
|
@ -486,7 +486,7 @@
|
||||||
<h3>Sparc64 - Jake Burk Burkholder</h3>
|
<h3>Sparc64 - Jake Burk Burkholder</h3>
|
||||||
|
|
||||||
<p>Basic status is we boot multi-user on real hardware. Looking at
|
<p>Basic status is we boot multi-user on real hardware. Looking at
|
||||||
targetting Ultra 2, 5, 10 and Blade 100. Something for 5.0 but it
|
targeting Ultra 2, 5, 10 and Blade 100. Something for 5.0 but it
|
||||||
may be a very manual install procedure. Toolchain is native but we
|
may be a very manual install procedure. Toolchain is native but we
|
||||||
haven't tested it much. It is a hosted tool chain. Runs on
|
haven't tested it much. It is a hosted tool chain. Runs on
|
||||||
Sparc64, generates Sparc64 binaries, but it's not the full usual
|
Sparc64, generates Sparc64 binaries, but it's not the full usual
|
||||||
|
|
@ -655,7 +655,7 @@
|
||||||
<p><strong class="speaker">PoulHK</strong> : On the subject of
|
<p><strong class="speaker">PoulHK</strong> : On the subject of
|
||||||
tinderbox. About 2 years ago I set up a machine to test this kind
|
tinderbox. About 2 years ago I set up a machine to test this kind
|
||||||
of thing but got a lot of negative feedback. If we want to do a
|
of thing but got a lot of negative feedback. If we want to do a
|
||||||
tinderbox like system it will require buy in by the commiters.</p>
|
tinderbox like system it will require buy in by the committers.</p>
|
||||||
|
|
||||||
<p><strong class="speaker">Nik C</strong> : I think the Mozilla team
|
<p><strong class="speaker">Nik C</strong> : I think the Mozilla team
|
||||||
do it more with a web page status.</p>
|
do it more with a web page status.</p>
|
||||||
|
|
@ -672,7 +672,7 @@
|
||||||
<p><strong class="speaker">Robert</strong> : If we're going to commit
|
<p><strong class="speaker">Robert</strong> : If we're going to commit
|
||||||
to having multiple platforms we need to solve this.</p>
|
to having multiple platforms we need to solve this.</p>
|
||||||
|
|
||||||
<p><strong class="speaker">Nik C</strong> : Thre are also issues of
|
<p><strong class="speaker">Nik C</strong> : There are also issues of
|
||||||
regression testing.</p>
|
regression testing.</p>
|
||||||
|
|
||||||
<p><strong class="speaker">David</strong> : I don't know what could be
|
<p><strong class="speaker">David</strong> : I don't know what could be
|
||||||
|
|
@ -703,7 +703,7 @@
|
||||||
|
|
||||||
<p><strong class="speaker">PoulHK</strong> : The performance is an
|
<p><strong class="speaker">PoulHK</strong> : The performance is an
|
||||||
issue but not as big as the code intrusion. Should we do it as two
|
issue but not as big as the code intrusion. Should we do it as two
|
||||||
seperate file systems or should we put this functionality directly
|
separate file systems or should we put this functionality directly
|
||||||
into UFS2?</p>
|
into UFS2?</p>
|
||||||
|
|
||||||
<p><strong class="speaker">Matt</strong> : Two comments on the FS
|
<p><strong class="speaker">Matt</strong> : Two comments on the FS
|
||||||
|
|
@ -863,7 +863,7 @@
|
||||||
downwards going command?</p>
|
downwards going command?</p>
|
||||||
|
|
||||||
<p><strong class="speaker">PoulHK</strong> : There's two things to it.
|
<p><strong class="speaker">PoulHK</strong> : There's two things to it.
|
||||||
A struct bio travelling down will either be in the consumer or the
|
A struct bio traveling down will either be in the consumer or the
|
||||||
provider and that's where the lock is. Modules can also be shut off
|
provider and that's where the lock is. Modules can also be shut off
|
||||||
safely.</p>
|
safely.</p>
|
||||||
|
|
||||||
|
|
@ -1000,7 +1000,7 @@
|
||||||
active.</p>
|
active.</p>
|
||||||
|
|
||||||
<p><strong class="speaker">PoulHK</strong> : There are two stacks one
|
<p><strong class="speaker">PoulHK</strong> : There are two stacks one
|
||||||
that is used by the Japanese and one that does a bunch of wierd
|
that is used by the Japanese and one that does a bunch of weird
|
||||||
stuff that no one uses.</p>
|
stuff that no one uses.</p>
|
||||||
|
|
||||||
<p><strong class="speaker">Robert</strong> : Action item is to query
|
<p><strong class="speaker">Robert</strong> : Action item is to query
|
||||||
|
|
@ -1116,7 +1116,7 @@
|
||||||
thing .</p>
|
thing .</p>
|
||||||
|
|
||||||
<p><strong class="speaker">Jonathan L</strong> : I have code that does
|
<p><strong class="speaker">Jonathan L</strong> : I have code that does
|
||||||
that. I've replaced all the queueing calls with a single call.</p>
|
that. I've replaced all the queuing calls with a single call.</p>
|
||||||
|
|
||||||
<p><strong class="speaker">Robert</strong> : Bring this to an end.</p>
|
<p><strong class="speaker">Robert</strong> : Bring this to an end.</p>
|
||||||
</div>
|
</div>
|
||||||
|
|
@ -1145,7 +1145,7 @@
|
||||||
|
|
||||||
<p>This stuff interacts with other subsystems including the network.</p>
|
<p>This stuff interacts with other subsystems including the network.</p>
|
||||||
|
|
||||||
<p>Mandatory policies. Discretionary rights are you proteting your
|
<p>Mandatory policies. Discretionary rights are you protecting your
|
||||||
own data. This is very hard to manage. MAC addresses this by
|
own data. This is very hard to manage. MAC addresses this by
|
||||||
defining policies for users in the system. Where you have many
|
defining policies for users in the system. Where you have many
|
||||||
users on the same machine. There are a couple of traditional
|
users on the same machine. There are a couple of traditional
|
||||||
|
|
@ -1173,7 +1173,7 @@
|
||||||
get this.</p>
|
get this.</p>
|
||||||
|
|
||||||
<p>What happens with the framework a module can declare at boot time or
|
<p>What happens with the framework a module can declare at boot time or
|
||||||
you can do an lkm on it.</p>
|
you can do an LKM on it.</p>
|
||||||
|
|
||||||
<p>Right now these API calls are in a perforce branch. They are
|
<p>Right now these API calls are in a perforce branch. They are
|
||||||
pervasive. They don't touch every part of the system, only the
|
pervasive. They don't touch every part of the system, only the
|
||||||
|
|
@ -1182,7 +1182,7 @@
|
||||||
<p>There isn't a generic label structure. To add new labels you must
|
<p>There isn't a generic label structure. To add new labels you must
|
||||||
recompile the kernel. Real key is to keep the costs low.</p>
|
recompile the kernel. Real key is to keep the costs low.</p>
|
||||||
|
|
||||||
<p>We don't allow for garbage collection on lables. Binary block that
|
<p>We don't allow for garbage collection on labels. Binary block that
|
||||||
gets carried around.</p>
|
gets carried around.</p>
|
||||||
|
|
||||||
<p>This is not really integrated into userland.</p>
|
<p>This is not really integrated into userland.</p>
|
||||||
|
|
@ -1238,7 +1238,7 @@
|
||||||
of the list stuff</p>
|
of the list stuff</p>
|
||||||
|
|
||||||
<p><strong class="speaker">Terry</strong> : You said something about
|
<p><strong class="speaker">Terry</strong> : You said something about
|
||||||
the NSA linux code. Independant? Licensing?</p>
|
the NSA linux code. Independent? Licensing?</p>
|
||||||
|
|
||||||
<p><strong class="speaker">Robert</strong> : Interesting issue. All
|
<p><strong class="speaker">Robert</strong> : Interesting issue. All
|
||||||
TrustedBSD work is under BSD license. The NSA stuff will not be
|
TrustedBSD work is under BSD license. The NSA stuff will not be
|
||||||
|
|
@ -1258,7 +1258,7 @@
|
||||||
contract was to release as open source.</p>
|
contract was to release as open source.</p>
|
||||||
|
|
||||||
<p><strong class="speaker">Alfred</strong> : About compatability. How
|
<p><strong class="speaker">Alfred</strong> : About compatability. How
|
||||||
compatable are we with others?</p>
|
compatible are we with others?</p>
|
||||||
|
|
||||||
<p><strong class="speaker">Robert</strong> : We've tried to follow the
|
<p><strong class="speaker">Robert</strong> : We've tried to follow the
|
||||||
specs.</p>
|
specs.</p>
|
||||||
|
|
@ -1267,7 +1267,7 @@
|
||||||
extended attribute stuff?</p>
|
extended attribute stuff?</p>
|
||||||
|
|
||||||
<p><strong class="speaker">Robert</strong> : Right now everyone does
|
<p><strong class="speaker">Robert</strong> : Right now everyone does
|
||||||
RPCs for ACLs and they're incompatbile. Not in Posix 1e. We tried
|
RPCs for ACLs and they're incompatible. Not in Posix 1e. We tried
|
||||||
to work with others but some are not tracking (Linux).</p>
|
to work with others but some are not tracking (Linux).</p>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
|
@ -1391,7 +1391,7 @@
|
||||||
Doing the basic stuff is the right answer.</p>
|
Doing the basic stuff is the right answer.</p>
|
||||||
|
|
||||||
<p><strong class="speaker">Julian</strong> : My theory is in fact that
|
<p><strong class="speaker">Julian</strong> : My theory is in fact that
|
||||||
nwe'll keep the current code and provide a new library. I don't want
|
we'll keep the current code and provide a new library. I don't want
|
||||||
to be responsible for the entire threading system.</p>
|
to be responsible for the entire threading system.</p>
|
||||||
|
|
||||||
<p><strong class="speaker">Matt</strong> : We can always change the
|
<p><strong class="speaker">Matt</strong> : We can always change the
|
||||||
|
|
@ -1525,7 +1525,7 @@
|
||||||
|
|
||||||
<p>We don't generate code on the fly.</p>
|
<p>We don't generate code on the fly.</p>
|
||||||
|
|
||||||
<p><strong class="speaker">John</strong> : Current Status con't.
|
<p><strong class="speaker">John</strong> : Current Status cont.
|
||||||
We've taken more time to get it right. We've added common things
|
We've taken more time to get it right. We've added common things
|
||||||
like semaphores, reader writer locks. I've been making the kernel
|
like semaphores, reader writer locks. I've been making the kernel
|
||||||
fully pre-emptible. I've commited half of this to current now. The
|
fully pre-emptible. I've commited half of this to current now. The
|
||||||
|
|
@ -1550,7 +1550,7 @@
|
||||||
fine grain the others in 5.0 oh well.</p>
|
fine grain the others in 5.0 oh well.</p>
|
||||||
|
|
||||||
<p><strong class="speaker">Anon</strong> : What specifically are you
|
<p><strong class="speaker">Anon</strong> : What specifically are you
|
||||||
planning in terms of performance gains before the relase? Do we
|
planning in terms of performance gains before the release? Do we
|
||||||
have any more firm of a schedule?</p>
|
have any more firm of a schedule?</p>
|
||||||
|
|
||||||
<p><strong class="speaker">John</strong> : 2nd question (schedule) is
|
<p><strong class="speaker">John</strong> : 2nd question (schedule) is
|
||||||
|
|
@ -1599,7 +1599,7 @@
|
||||||
<p><strong class="speaker">Luigi</strong> : Do we care about
|
<p><strong class="speaker">Luigi</strong> : Do we care about
|
||||||
performance on uniprocessors on 5.0?</p>
|
performance on uniprocessors on 5.0?</p>
|
||||||
|
|
||||||
<p><strong class="speaker">John</strong> : One thign that SMPng may
|
<p><strong class="speaker">John</strong> : One thing that SMPng may
|
||||||
help buy is that if you have two network interfaces then you can
|
help buy is that if you have two network interfaces then you can
|
||||||
handle more stuff.</p>
|
handle more stuff.</p>
|
||||||
|
|
||||||
|
|
@ -1639,7 +1639,7 @@
|
||||||
<p>Got a bit of a feature list for 5.0 final. SMPng is broken down
|
<p>Got a bit of a feature list for 5.0 final. SMPng is broken down
|
||||||
into several sections. UFS2. KSE. PAM overhaul. TrustedBSD etc.</p>
|
into several sections. UFS2. KSE. PAM overhaul. TrustedBSD etc.</p>
|
||||||
|
|
||||||
<p>I'd like some feeback on this.</p>
|
<p>I'd like some feedback on this.</p>
|
||||||
|
|
||||||
<h3>Discussion</h3>
|
<h3>Discussion</h3>
|
||||||
|
|
||||||
|
|
@ -1655,7 +1655,7 @@
|
||||||
bit? (Laughter)</p>
|
bit? (Laughter)</p>
|
||||||
|
|
||||||
<p><strong class="speaker">David</strong> : Feature freeze is a code
|
<p><strong class="speaker">David</strong> : Feature freeze is a code
|
||||||
slush. Will I as a commiter see a freeze?</p>
|
slush. Will I as a committer see a freeze?</p>
|
||||||
|
|
||||||
<p><strong class="speaker">Murray</strong> : You will not have to
|
<p><strong class="speaker">Murray</strong> : You will not have to
|
||||||
worry about bug fixes but you must act rationally.</p>
|
worry about bug fixes but you must act rationally.</p>
|
||||||
|
|
@ -1686,7 +1686,7 @@
|
||||||
<p><strong class="speaker">Doug</strong> : I don't know how tied you
|
<p><strong class="speaker">Doug</strong> : I don't know how tied you
|
||||||
are to the release schedule. If you want to spend all of October
|
are to the release schedule. If you want to spend all of October
|
||||||
polishing. If we go backwards from October we can do Release 1 on
|
polishing. If we go backwards from October we can do Release 1 on
|
||||||
May 15. April 1st is too soon and puts you in wierd catagories
|
May 15. April 1st is too soon and puts you in weird catagories
|
||||||
relative to Usenix.</p>
|
relative to Usenix.</p>
|
||||||
|
|
||||||
<p><strong class="speaker">Murray</strong> : The way we have it set up
|
<p><strong class="speaker">Murray</strong> : The way we have it set up
|
||||||
|
|
@ -1795,7 +1795,7 @@ ALTERNATE
|
||||||
|
|
||||||
<p><strong class="speaker">Julian</strong> : Breaking the build is not
|
<p><strong class="speaker">Julian</strong> : Breaking the build is not
|
||||||
as bad as breaking the kernel. What's harder is committing a
|
as bad as breaking the kernel. What's harder is committing a
|
||||||
subsystem that affects another subsystem. In terms of the proecess
|
subsystem that affects another subsystem. In terms of the process
|
||||||
I'd like to see a best practices document. On how people develop
|
I'd like to see a best practices document. On how people develop
|
||||||
patches etc. A list of things you should do etc.</p>
|
patches etc. A list of things you should do etc.</p>
|
||||||
|
|
||||||
|
|
@ -1860,7 +1860,7 @@ ALTERNATE
|
||||||
|
|
||||||
<p><strong class="speaker">Doug</strong> : One is that in regards to
|
<p><strong class="speaker">Doug</strong> : One is that in regards to
|
||||||
PoulHK said in addition to the potential cost of disciplining a
|
PoulHK said in addition to the potential cost of disciplining a
|
||||||
commiter you have to measure the cost against the others who want
|
committer you have to measure the cost against the others who want
|
||||||
that person gone. How many more people could we attract if that
|
that person gone. How many more people could we attract if that
|
||||||
stress wasn't present.</p>
|
stress wasn't present.</p>
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue