Daemon's Advocate article

[Robert Garrett]

eader.dragonflybsd.org> <200403011728.i21HSciT077091 at xxxxxxxxxxxxxxxxxxxx> <20040301181002.GG1352 at xxxxxxxxxxxxxxx> <200403012005.i21K5hFg077822 at xxxxxxxxxxxxxxxxxxxx> <m265dn71dy.fsf at xxxxxxxxxx>
In-Reply-To: <m265dn71dy.fsf at xxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 39
Message-ID: <40449f75$0$184$415eb37d at xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
NNTP-Posting-Host: 64.217.142.35
X-Trace: 1078239094 crater_reader.dragonflybsd.org 184 64.217.142.35
Xref: crater_reader.dragonflybsd.org dragonfly.kernel:4102

Dave Leimbach wrote:
> Matthew Dillon <dillon at xxxxxxxxxxxxxxxxxxxx> writes:
> 
> 
>>:Egads!  Matt, put down the painkillers!!    8-)
>>:
>>:I can just see it now...  right next to 'page faults', we've got
>>:'package faults'.  We could even have a package pager, to
>>:automatically do LRU analysis on packages, and delete them when we get
>>:tight on space (of course, weighing in the speed of the network
>>:connection).
>>:
>>:
>>:-- 
>>:Matthew Fuller     (MF4839)   |  fullermd at xxxxxxxxxxxxxxx
>>
>>   And 'pkglock' to lock a package in so it isn't deleted by the LRU.
>>
>>   Really, though, I think this might be a great idea whos time has come.
>>   Kinda like having an NFS mount over the internet, but with added security
>>   (local MD5 file for comparisons, multiple servers, load distribution, etc).
>>
>>   Perfect for a userland VFS.
>>
>>					-Matt
> 
> 
> What does this mean for the system admin who normally would have some control 
> over what gets installed on his boxes?
> 
> I think we need a way to handle that link in the chain don't we?
> 
> Ugh... I am starting to thing in terms of UML Use Cases.  
> 
> Dave
we present them with a graphical representation of all the possible 
knobs they could ever want to tweak, when they define INSANE_PKG

Rob