From 5d97d31c8372ab7c87c8b42fe11f29bdc3576bd8 Mon Sep 17 00:00:00 2001
From: Tom Rhodes
The extension that was added is that instead of a single table it's @@ -430,7 +430,7 @@ its easier to build from there.
Benno : The other note that I will - make is that I'm only targetting PowerPC similar to 700.
+ make is that I'm only targeting PowerPC similar to 700.Warner : I was going to comment that NetBSD has done well with little tiny ports to different @@ -486,7 +486,7 @@
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 haven't tested it much. It is a hosted tool chain. Runs on Sparc64, generates Sparc64 binaries, but it's not the full usual @@ -655,7 +655,7 @@
PoulHK : On the subject of 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 - tinderbox like system it will require buy in by the commiters.
+ tinderbox like system it will require buy in by the committers.Nik C : I think the Mozilla team do it more with a web page status.
@@ -672,7 +672,7 @@Robert : If we're going to commit to having multiple platforms we need to solve this.
-Nik C : Thre are also issues of +
Nik C : There are also issues of regression testing.
David : I don't know what could be @@ -703,7 +703,7 @@
PoulHK : The performance is an 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?
Matt : Two comments on the FS @@ -863,7 +863,7 @@ downwards going command?
PoulHK : 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 safely.
@@ -1000,7 +1000,7 @@ active.PoulHK : 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.
Robert : Action item is to query @@ -1116,7 +1116,7 @@ thing .
Jonathan L : I have code that does - that. I've replaced all the queueing calls with a single call.
+ that. I've replaced all the queuing calls with a single call.Robert : Bring this to an end.
@@ -1145,7 +1145,7 @@This stuff interacts with other subsystems including the network.
-Mandatory policies. Discretionary rights are you proteting your +
Mandatory policies. Discretionary rights are you protecting your own data. This is very hard to manage. MAC addresses this by defining policies for users in the system. Where you have many users on the same machine. There are a couple of traditional @@ -1173,7 +1173,7 @@ get this.
What happens with the framework a module can declare at boot time or - you can do an lkm on it.
+ you can do an LKM on it.Right now these API calls are in a perforce branch. They are pervasive. They don't touch every part of the system, only the @@ -1182,7 +1182,7 @@
There isn't a generic label structure. To add new labels you must recompile the kernel. Real key is to keep the costs low.
-We don't allow for garbage collection on lables. Binary block that +
We don't allow for garbage collection on labels. Binary block that gets carried around.
This is not really integrated into userland.
@@ -1238,7 +1238,7 @@ of the list stuffTerry : You said something about - the NSA linux code. Independant? Licensing?
+ the NSA linux code. Independent? Licensing?Robert : Interesting issue. All TrustedBSD work is under BSD license. The NSA stuff will not be @@ -1258,7 +1258,7 @@ contract was to release as open source.
Alfred : About compatability. How - compatable are we with others?
+ compatible are we with others?Robert : We've tried to follow the specs.
@@ -1267,7 +1267,7 @@ extended attribute stuff?Robert : 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).
@@ -1391,7 +1391,7 @@ Doing the basic stuff is the right answer.Julian : 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.
Matt : We can always change the @@ -1525,7 +1525,7 @@
We don't generate code on the fly.
-John : Current Status con't. +
John : Current Status cont. 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 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.
Anon : 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?
John : 2nd question (schedule) is @@ -1599,7 +1599,7 @@
Luigi : Do we care about performance on uniprocessors on 5.0?
-John : One thign that SMPng may +
John : One thing that SMPng may help buy is that if you have two network interfaces then you can handle more stuff.
@@ -1639,7 +1639,7 @@Got a bit of a feature list for 5.0 final. SMPng is broken down into several sections. UFS2. KSE. PAM overhaul. TrustedBSD etc.
-I'd like some feeback on this.
+I'd like some feedback on this.
David : Feature freeze is a code - slush. Will I as a commiter see a freeze?
+ slush. Will I as a committer see a freeze?Murray : You will not have to worry about bug fixes but you must act rationally.
@@ -1686,7 +1686,7 @@Doug : I don't know how tied you 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 - 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.
Murray : The way we have it set up @@ -1795,7 +1795,7 @@ ALTERNATE
Julian : Breaking the build is not 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 patches etc. A list of things you should do etc.
@@ -1860,7 +1860,7 @@ ALTERNATEDoug : One is that in regards to 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 stress wasn't present.