I'm forwarding this from the GTK development list. According to Owen
their is something wrong with the threads implementation
Is that true? or is it a "It's not the way Linux works, so it must be
wrong"-pigheadedness? =)
DocWilco
"ROGIER MULHUIJZEN" [EMAIL PROTECTED] writes:
Quick question,
Does anyone on here know what the equivelant macro for
PTHREAD_RECURSIVE_MUTEX_INITALIZER_NP is under freebsd? I cant find
anything like this in pthread.h, and Im wondering without it what do I use
to initialize a recursive mutex.
Any advice would be appreciated
Many thanks
On Thu, Jan 13, 2000 at 10:27:23AM +0100, ROGIER MULHUIJZEN wrote:
I'm forwarding this from the GTK development list. According to Owen
their is something wrong with the threads implementation
Is that true? or is it a "It's not the way Linux works, so it must be
wrong"-pigheadedness? =)
I'm forwarding this from the GTK development list. According to Owen
their is something wrong with the threads implementation
Is that true? or is it a "It's not the way Linux works, so it must be
wrong"-pigheadedness? =)
What version of FreeBSD are you using?
Dan Eischen
[EMAIL
I'm running 3.4-RELEASE.
DocWilco
Daniel Eischen [EMAIL PROTECTED] 01/13 12:57 PM
I'm forwarding this from the GTK development list. According to Owen
their is something wrong with the threads implementation
Is that true? or is it a "It's not the way Linux works, so it
Quick question,
Does anyone on here know what the equivelant macro for
PTHREAD_RECURSIVE_MUTEX_INITALIZER_NP is under freebsd? I cant find
anything like this in pthread.h, and Im wondering without it what do I use
to initialize a recursive mutex.
Any advice would be appreciated
Well,
Consider as an example that open() is a thread cancellation point according
to POSIX. If libpthread overrides the libc open() with its own version of
open(), then by extension, every function that calls open() can potentially
cause thread cancellation. This propagation of cancellation
I'm running 3.4-RELEASE.
Try upgrading to -stable and see if that helps. There were
some changes recently merged from -current. If the application
uses signals to wakeup threads, then perhaps the -stable version
may fix the problems your seeing.
Dan Eischen
[EMAIL PROTECTED]
To
On 12/01 17:09, Michael Lucas wrote:
Minesweeper can only fill so many hours in a day, after all.
Must be a long day in your part of the world, then, because it's an
NP-complete problem! (http://www.mat.bham.ac.uk/R.W.Kaye/minesw.htm)
Heh :-)
obSources: try
On Wed, 12 Jan 2000, Luoqi Chen wrote:
It's almost a regular fork(), we lose all the advantages of a single
address space. A rfork(RFMEM) wrapper can achieve the same level of
usability without sacrificing the performance, and IMO is a preferred
solution.
I don't see this at all. You get
In message [EMAIL PROTECTED], "Kenneth D. Merry" writes:
On Tue, Jan 11, 2000 at 13:49:59 -0600, Jonathan Lemon wrote:
The RCC is probably this one:
pci: unknown ATA vendor = 0x1166, device = 0x0211
I wonder why it flags it as a ATA device, I'm pretty sure this is the
RCC chip --
"Ronald G. Minnich" wrote:
On Wed, 12 Jan 2000, Luoqi Chen wrote:
It's almost a regular fork(), we lose all the advantages of a single
address space. A rfork(RFMEM) wrapper can achieve the same level of
usability without sacrificing the performance, and IMO is a preferred
solution.
On Thu, Jan 13, 2000 at 07:18:12AM -0500, Daniel Eischen wrote:
Use _open internally within libc and libpthread. Have one "open"
entry point that is the cancellation version of open.
This is what it appears Solaris 7 does.
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to
On Thu, 13 Jan 2000, David O'Brien wrote:
On Thu, Jan 13, 2000 at 07:18:12AM -0500, Daniel Eischen wrote:
Use _open internally within libc and libpthread. Have one "open"
entry point that is the cancellation version of open.
This is what it appears Solaris 7 does.
Yeah, I've noticed
I am new in this mail list, so I do not have so much experience about the
questions I should ask, If I am in the worng place let me know, please.
Well my question is related with Solaris 2.6, the story is like this:
I have a Solaris 2.5 server which has configured all the printers so I can
On Thu, Jan 13, 2000, Ramiro Amaya wrote:
I am new in this mail list, so I do not have so much experience about the
questions I should ask, If I am in the worng place let me know, please.
Well my question is related with Solaris 2.6, the story is like this:
What does this have to do with
Wes Peters wrote:
Michael Lucas wrote:
I find myself in a contract where I sit for eight hours a day and wait
for something to break. It pays obscenely well, so I'm putting up
with the tedium.
So, if I was to sit down and start reading /usr/src/sys, where's the
logical place to
On Thu, 13 Jan 2000, Michael Lucas wrote:
PS: Anyone know the status of zp0 in -current?
It was a hack and it was put to sleep by someone wielding an axe.
--
- bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp -
- ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED]
On Thu, Jan 13, 2000 at 07:18:12AM -0500, Daniel Eischen wrote:
Consider as an example that open() is a thread cancellation point according
to POSIX. If libpthread overrides the libc open() with its own version of
open(), then by extension, every function that calls open() can potentially
On Thu, 13 Jan 2000, Ramiro Amaya wrote:
I am new in this mail list, so I do not have so much experience about the
questions I should ask, If I am in the worng place let me know, please.
Well my question is related with Solaris 2.6, the story is like this:
I have a Solaris 2.5 server
This list is for FreeBSD, not Solaris.
*==*
*Gene Harris http://www.tetronsoftware.com*
*FreeBSD Novice*
*All ORBS.org SMTP connections are denied! *
*==*
On Thu, 13
On Thu, 13 Jan 2000, Jason Evans wrote:
On Thu, Jan 13, 2000 at 07:18:12AM -0500, Daniel Eischen wrote:
Consider as an example that open() is a thread cancellation point according
to POSIX. If libpthread overrides the libc open() with its own version of
open(), then by extension,
Matthew Dillon wrote:
The last two paragraphs are the most relevant to us.
http://www.nytimes.com/reuters/technology/tech-tech-encryption.html
Have we had an opportunity to have the Walnut Creek (or other) legal staff
review the actual rules for gotchas?
--
"Where
Oliver Fromme wrote:
Basically, does this mean something like
tar cf - /usr/src/crypto | mail [EMAIL PROTECTED]
? :-)
No. Mail to "[EMAIL PROTECTED]", Hilary is handling the database.
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters
Have we had an opportunity to have the Walnut Creek (or other) legal staff
review the actual rules for gotchas?
No, this is something I hope to sit down with our corporate counsel
over very shortly. It's an annoying drive to San Jose from here, but
I'm prepared to make that sacrifice. :)
-
"Christopher R. Bowman" wrote:
The last paragraph would be a step in the right direction but still seems
silly. What are they going to do with it? I would really like to see people
educate them on the stupidity of sending code to Washington. I think it would
be neat if there was one of
I have been looking at UDF ( the filesystem used on CD-RW and DVD's ). I
was wondering if anybody was working on it. I'm thinking about trying to
implement it for CD-RW's and would like to avoid duplication of effort and
the anoyance of getting half way through the effort and having somebody
On Wed, 12 Jan 2000 17:09:29 -0500 (EST), Michael Lucas [EMAIL PROTECTED]
wrote:
I find myself in a contract where I sit for eight hours a day and wait
for something to break. It pays obscenely well, so I'm putting up
with the tedium.
How does one go about getting such contracts?
So, if I was
In message [EMAIL PROTECTED] NOKUBI Hirotaka writes:
: I also want to know a URL.
:
: My NEC PC98 (using x86 CPU, but not PC-AT compatible) uses
: RCC Champion as it's chipset. (Sorry not Champion II/III, it's slightly
: old machine.) I'll attach dmesg from it.
:
: RCC Champion is attached like
Michael Lucas wrote:
Wes Peters wrote:
Michael Lucas wrote:
I find myself in a contract where I sit for eight hours a day and wait
for something to break. It pays obscenely well, so I'm putting up
with the tedium.
So, if I was to sit down and start reading /usr/src/sys,
In message [EMAIL PROTECTED] Wes Peters writes:
: Modern flash chips support on the order of 1,000,000 write cycles, so this
: is not such a concern anymore. There is no reason why we shouldn't put
: a filesystem on a flash card.
We weren't talking about modern flash cards :-). These flash
31 matches
Mail list logo
