On Tuesday, 15 May 2007 at 1:05:07 -0700, Garrett Cooper wrote:
> Tom Evans wrote:
> >On Mon, 2007-05-14 at 22:17 -0700, Garrett Cooper wrote:
> >>Ruby's nice, but it's built on Perl so I have suspicions on its overall
> >>usability / speed given my experience with Perl over the past 4 months
>
On Monday, 14 May 2007 at 21:42:18 -0700, Garrett Cooper wrote:
> Duane Whitty wrote:
[snipped]
> >
> >I wonder what the ramifications of the above are to the goal of using the
> >bdb in
> >our base system to add db smarts to the pkg_install tools in a way that
>
[snipped]
>
> > Do you know of any simple APIs that can quickly dump fields in use
> > with BDB .db files? I have a hunch given the Ruby that I've taken a
> > look at
> > with Portupgrade that something very inefficient's in play, but I want
> > to test my assumption first before jumpi
On Sunday, 13 May 2007 at 22:39:51 -0700, Garrett Cooper wrote:
> Duane Whitty wrote:
> >Garrett,
> >
> >Sounds like you're involved in a cool project. What kind of
> >community collaboration/involvement would be helpful to you?
> >
> >Once, a long, lo
On Sunday, 13 May 2007 at 17:04:20 -0400, Kris Kennaway wrote:
> On Sun, May 13, 2007 at 10:00:46PM +0100, Thomas Sparrevohn wrote:
>
> > The answer is another INDEX/storage structure
>
> Great, I look forward to your detailed proposal.
>
> Kris
I believe this is closer to what Thomas meant
On Thursday, 10 May 2007 at 20:20:42 -0700, Garrett Cooper wrote:
> David Naylor wrote:
> >Dear Jordan
> >
> >Recently I stumbled across a document you wrote in 2001, entitled "FreeBSD
> >installation and package tools, past, present and future". I find FreeBSD
> >appealing and I would like to c
Garrett,
Sounds like you're involved in a cool project. What kind of
community collaboration/involvement would be helpful to you?
Once, a long, long time ago, I wrote quite a bit of bdb 1.85
code. At that time it WAS the current version :) I might
actually remember a bit if I start working wit
On Friday, 11 May 2007 at 17:28:47 -0400, Kris Kennaway wrote:
> On Fri, May 11, 2007 at 11:02:31PM +0200, David Naylor wrote:
> > Hi,
> >
> > Thank you all for your responses, it has given me much to think about. I
> > guess there is consenses that there is room for improvement in the current
On Thursday, 10 May 2007 at 12:54:45 +, Darren Reed wrote:
> On Thu, May 10, 2007 at 01:28:16PM +0100, Robert Watson wrote:
> >
> > On Thu, 10 May 2007, Darren Reed wrote:
> >
> > >I'm using FreeBSD 7.0-CURRENT under vmware and there are a few issues.
>
> Redirecting to [EMAIL PROTECTED]
>
hing is translating from textbook type
examples to real kernel code. Anyhow, I hope this message
wasn't too long or unbearable. Please send me any comments
that you would like to, on or off list.
Thanks again!
Duane Whitty
P.S.
I think I'm just about
ready to tackle fixing
sysv sems to
On Thu, Dec 28, 2006 at 11:33:44AM +0100, Jeremie Le Hen wrote:
> Hi Duane,
>
> On Wed, Dec 20, 2006 at 12:18:43AM -0400, Duane Whitty wrote:
> > I have read the man pages describing each family of locks, John Baldwin's
> > BSDCon 2002 paper, Jeffrey Hsu's paper, th
an interesting
and detailed section in our Arch. Handbook. I regret that I am
not able to produce something more quickly; I simply haven't
learned enough yet.
Best Regards,
Duane Whitty
>
> Bye,
> Alexander.
>
> --
> I don't do it for the money.
> --
family. Does
anyone have some pointers they feel like sharing?
Does anyone have any good references they can point me to that is
relevant to fbsd given all the recent changes as a result of SMP?
Is The Design and Implementation of the FreeBSD Operating System
still current enough
t;
According to src/sys/conf/NOTES
# The INVARIANT_SUPPORT option makes us compile in support for
# verifying some of the internal structures. It is a prerequisite for
# 'INVARIANTS', as enabling 'INVARIANTS' will make these functions be
# called.
Best Regards,
Duane Whitty
___
Duane Whitty wrote:
Submitter-Id: current-users
Originator: Duane Whitty
Organization:
Confidential: no
Synopsis: lock order reversal
Severity: serious
Priority: medium
Category: kern
Class: sw-bug
Release:FreeBSD 6.2-PRERELEASE i386
Environment
>Submitter-Id: current-users
>Originator: Duane Whitty
>Organization:
>Confidential: no
>Synopsis: lock order reversal
>Severity: serious
>Priority: medium
>Category: kern
>Class: sw-bug
>Release: FreeBSD 6.2-PRERELEASE i386
dware is quite inexpensive and HP has definitely started using more
"off-the-shelf" hardware these days.
Heh, sorry I guess this belongs more on platforms@ but the thread caught my
attention and I've been thinking about this for a while...
Best Regards,
Duane Whitty
__
forget about system admin...
Sincerely
Duane Whitty
--
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
lable?
Sincerely,
Duane Whitty
--
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Greg 'groggy' Lehey wrote:
In the last month or two I've seen increasing occurrences of programs
refusing keyboard input after they've been running for a while
(between hours and days). They still respond to the mouse. At first
I thought it was hardware, but it happens on a number of different
20 matches
Mail list logo
