On Monday, March 06, 2000, Zhihui Zhang wrote:
Can anyone tell me where is the code for pci_intr_establish() and
_thread_sys_read()? I could not find them under /usr/src.
I can tell you offhand that _thread_sys_anything is the _real_
syscall for `anything'. This is because a lot of
On Mon, 6 Mar 2000, Chris Costello wrote:
On Monday, March 06, 2000, Zhihui Zhang wrote:
Can anyone tell me where is the code for pci_intr_establish() and
_thread_sys_read()? I could not find them under /usr/src.
I can tell you offhand that _thread_sys_anything is the _real_
syscall for
Daniel Eischen wrote:
Some of the man pages and cancellation support came from OpenBSD
(David Leonard). The man page appears to have been written on
Jan 17, 1999 for OpenBSD. FreeBSD-current and -stable came much
later.
Ah, that's what I saw. Thanks for the clarification.
--
In article [EMAIL PROTECTED],
W Gerald Hicks [EMAIL PROTECTED] wrote:
Convince me that nothing like the following exists in the
ports framework and /usr/src and I'd be ok with a change
*after* 4.0 release (repeats himself)
# Makefile.foo
FOOVAR=
.
.
.
BARVAR=${FOOVAR}
nothing is not a word at all, so it can't be expanded, so I think
bash is corrent to complain about a syntax error.
Epsilon anyone?
I really don't care (honestly) but a null word can be considered a word too!
In yacc-like terms:
wordlist:
| wordlist WORD
;
It doesn't really
I agree that this is not the time to change it. But in the long run,
if the ports framework is misusing /bin/sh then the framework needs to
be fixed. We shouldn't let bugs there influence what we do with the
shell.
Haven't been convinced yet they are bugs :-)
Cheers,
Jerry Hicks
[EMAIL
My laptop running 3.4-RELEASE decided it doesn't want to boot.
It was uncleanly shut down via the power switch by someone
who thought they were shutting down a different machine.
Now when it boots, running fsck gives this result:
chip0: Intel 82439TX System Controller (MTXC) rev 0x01 on
I've had the same problem. Most people have told me that I have to
replace the hard drive.
I never had the problem before 3.4. Maybe that's just a coincidence,
though.
--
Chris Byrnes (CB5820)
Network Engineer, High Stability Internet Services
http://www.highstability.com
On Mon, 6 Mar
I sometimes have this problem with my pc.
Usually, a good kick will get it to boot.
Sometimes on laptops and stuff the hard drive cable gets
loose or something. Or, it's a bad hard drive.
Try giving is a shove.
--bhishan
I've had the same problem. Most people have told me that I have to
hi, there!
On Mon, 6 Mar 2000, Martin Cracauer wrote:
I just checked POSIX 1003.2.
for name [ in word ]
do
compound-list
done
"First, the list of words following 'in' shall be expanded to generate
a list of items." [...] "If no items result from the expansion, the
In [EMAIL PROTECTED], Max Khon wrote:
hi, there!
On Mon, 6 Mar 2000, Martin Cracauer wrote:
I just checked POSIX 1003.2.
for name [ in word ]
do
compound-list
done
"First, the list of words following 'in' shall be expanded to generate
a list of items." [...] "If no
On Sat, 04 Mar 2000 15:36:43 +0200, Sheldon Hearn wrote:
I seem to remember POSIX being ambiguous on this one, but my books
are at the office. If you haven't gotten a more conclusive answer by
Monday, mail me and I'll look it up.
I was wrong about POSIX being ambiguous in this regard;
Sheldon Hearn wrote:
On Sat, 04 Mar 2000 15:36:43 +0200, Sheldon Hearn wrote:
I seem to remember POSIX being ambiguous on this one, but my books
are at the office. If you haven't gotten a more conclusive answer by
Monday, mail me and I'll look it up.
I was wrong about POSIX being
On Mon, 06 Mar 2000 00:59:39 PST, Doug Barton wrote:
for name [ in word ]
do
compound-list
done
the "in word" is optional. Therefore:
Hmmm, you're right.
I must admit, though, that if the text is confusing enough to confuse
me, it's not entirely clear (even if I'm not the
In message [EMAIL PROTECTED] Sheldon Hearn writes:
: On Mon, 06 Mar 2000 00:59:39 PST, Doug Barton wrote:
:
: for name [ in word ]
: do
: compound-list
: done
:
: the "in word" is optional. Therefore:
:
: Hmmm, you're right.
:
: I must admit, though, that if the text is
Warner Losh wrote:
In message [EMAIL PROTECTED] Sheldon Hearn writes:
: On Mon, 06 Mar 2000 00:59:39 PST, Doug Barton wrote:
:
: for name [ in word ]
: do
: compound-list
: done
:
: the "in word" is optional. Therefore:
:
: Hmmm, you're right.
:
: I must admit,
On Mon, 06 Mar 2000 01:44:35 PST, Doug Barton wrote:
At the same time, I'd also like to see if POSIX has a clear definition
of "word."
Aha, that's what we should have looked at right in the beginning. My
take on POSIX.2 3.10.2 (Shell Grammar Rules) is that _word_ may not be
the empty
On Fri, 3 Mar 2000, Mike Smith wrote:
Actually, since this is copy-on-write, you do not need the block, until
you write. If you need to make a copy, it will be on a write system call
(possibly an inode update), just fail the write ENOSPC or whatever. Or am
I missing something simple
Hi,
I use two threads to do I/O for a process.
The I/O takes place either on a socket or
an I/O device (com port) file descriptor.
Apparently it is not possible to shutdown those
threads from a third thread, neither using close nor shutdown(2) for
the socket I/O if the threads are blocked
Hi,
I have not so much experience using POSIX threads, but we had in
university a project and for I/O to use threads is not so good method.
You slow down the process.
Some comments? Isn't so?
stefan
Titus von Boxberg wrote:
Hi,
I use two threads to do I/O for a process.
The I/O takes
well i bumped it to 512 and nmbclusters to 32768 on several machines that
got 5000+ (!) http requests a second... the problem is the number of maximum
open files in the system (32k in this case) and open sockets.
/k
--
The path of excess leads to the tower of wisdom. -W. Blake
Karsten W.
I use two threads to do I/O for a process.
The I/O takes place either on a socket or
an I/O device (com port) file descriptor.
Apparently it is not possible to shutdown those
threads from a third thread, neither using close nor shutdown(2) for
the socket I/O if the threads are blocked
* stefan parvu ([EMAIL PROTECTED]) [000306 09:19]:
I have not so much experience using POSIX threads, but we had in
university a project and for I/O to use threads is not so good method.
You slow down the process.
Some comments? Isn't so?
In my experience, threads are the perfect way to
On Mon, 6 Mar 2000, James FitzGibbon wrote:
Some comments? Isn't so?
In my experience, threads are the perfect way to speed up an I/O bound
application. While one thread is blocked in iowait, others can be
performing operations that do not contend for the same resource
(calculation, I/O
[...]
What's the reason for locking the file descriptors
for *all* system calls? especially those I mentioned?
Where is pthread_cancel() ?
are you using -stable (3.x)? there is no ``pthread_cancel'' in -stable.
use -current.
or
- use other threads library
- use
On Monday, March 06, 2000, Max Khon wrote:
However, under Solaris 2.6:
clone$uname -a
SunOS clone 5.6 Generic_105181-13 sun4u sparc SUNW,Ultra-1-Engine
clone$/bin/ksh
clone$for i in ; do echo $i; done
/bin/ksh: syntax error: `;' unexpected
clone$
It is likely you are running the ksh88
Max Khon [EMAIL PROTECTED] wrote:
However, under Solaris 2.6:
clone$uname -a
SunOS clone 5.6 Generic_105181-13 sun4u sparc SUNW,Ultra-1-Engine
clone$/bin/ksh
clone$for i in ; do echo $i; done
/bin/ksh: syntax error: `;' unexpected
That's an old ksh88, which probably doesn't conform to
On Thu, 02 Mar 2000 19:59:39 EST, James Howard wrote:
The problem is how do we keep up with -STABLE afterwards? Using
CVSup, out changes will get clobbered every time. Is there a facility
where you can keep up with the source but let local modifications
through?
CVS does this
I am busy to convert two lkm's to kld's and having some problem with it.
The scenario is two lkm's ( now kld's ) which are loaded dependantly ( A and B
)
I used to load them as :
/sbin/modload -o /tmp/kern.sym ./A.o
/sbin/modload -A /tmp/kern.sym ./B.o
to keep the symbols available.
The general
I am busy to convert two lkm's to kld's and having some problem with it.
The scenario is two lkm's ( now kld's ) which are loaded dependantly ( A and B
)
I used to load them as :
/sbin/modload -o /tmp/kern.sym ./A.o
/sbin/modload -A /tmp/kern.sym ./B.o
to keep the symbols available.
The general
Titus von Boxberg wrote:
Daniel Eischen wrote:
Apparently it is not possible to shutdown those
threads from a third thread, neither using close nor shutdown(2) for
the socket I/O if the threads are blocked during read.
What methods can one use to unblock such a blocked-on-read
On Mon, 21 Feb 2000 22:10:15 +0600, Max Khon wrote:
bash and ksh complain about unexpected ';'.
/bin/sh (FreeBSD) thinks it's ok and does nothing.
Which behaviour is more POSIXly correct?
Neither bash nor ksh claim to be particularly POSIX compliant.
Bash claims POSIX.2 compliance.
Even though it's my preferred shell, I certainly wouldn't say
that Bash is any sort of standard, certainly not in the POSIX
sense.
Bash implements the POSIX.2 standard, with certain well-defined
exceptions (`posix mode').
Imagine processing a possibly empty list constructed from a
'make'
Are you sure that "word" here means one or more tokens, or zero or
more tokens. If it means zero or more tokens, then 'for i in ; do '
is perfectly legal. You're not quoting what word means.
The standard says that `word' may not be the empty string.
POSIX.2, 3.10.
The reason that I ask
On 06-Mar-00 Yevmenkin, Maksim N, CSCIO wrote:
[...]
What's the reason for locking the file descriptors
for *all* system calls? especially those I mentioned?
Where is pthread_cancel() ?
are you using -stable (3.x)? there is no ``pthread_cancel'' in -stable.
use -current.
Bt!!!
On 06-Mar-00 Doug Barton wrote:
I just checked POSIX 1003.2.
for name [ in word ]
do
compound-list
done
the "in word" is optional. Therefore:
for name in ; do echo $name; done
is an error, whereas
for name ; do echo $name; done
These are two different functions. The
In message [EMAIL PROTECTED] Marc Frajola writes:
: I have written my own Perl script that reads dmesg to get the disk
: geometry and then generates a proper FreeBSD partition (disklabel)
: label, and have verified that I can get the result I want this way.
Bad idea. Too many different
On Mon, 06 Mar 2000 12:04:53 EST, Chet Ramey wrote:
Bash claims POSIX.2 compliance. If you have specific reports of
non-compliance, send them to [EMAIL PROTECTED]
I spoke out of turn. Please permit me to extract my foot from my mouth
and try to reattach it to some part of the body that'll
[...]
are you using -stable (3.x)? there is no ``pthread_cancel''
in -stable.
use -current.
Bt!!! Wrong!
uname -a
FreeBSD server.baldwin.cx 3.4-STABLE FreeBSD 3.4-STABLE #6:
Sun Feb 20 20:24:19 EST 2000
[EMAIL PROTECTED]:/usr/source/src/sys/compile/SERVER i386
man -k
On Mon, 6 Mar 2000, Yevmenkin, Maksim N, CSCIO wrote:
[...]
are you using -stable (3.x)? there is no ``pthread_cancel''
in -stable.
use -current.
Bt!!! Wrong!
uname -a
FreeBSD server.baldwin.cx 3.4-STABLE FreeBSD 3.4-STABLE #6:
Sun Feb 20 20:24:19 EST 2000
In message [EMAIL PROTECTED] Chet Ramey writes:
: The idiomatic solution for this sort of thing is changing
: your makefile recipes from
:
: for f in ${SUBDIRS} do ...
:
: to
:
: sh_subdirs=${SUBDIRS}; for f in $$sh_subdirs ; do ...
That's much better than what I've tended to do:
In message [EMAIL PROTECTED], Warner Losh writes:
: to
:
: sh_subdirs=${SUBDIRS}; for f in $$sh_subdirs ; do ...
there's lots of other workarounds, from seeing if SUBDIRS is defined,
to using make's .foreach.
Another option is:
for f in $$empty_list ${SUBDIRS}; do ...
On Mon, Mar 06, 2000 at 01:45:44PM -0500, John Baldwin wrote:
On 06-Mar-00 Doug Barton wrote:
All that said, if the ports make system depends on the current
behavior, it has to be fixed before we can contemplate any changes.
Patches accepted.
The construction
set --
Ron 'The InSaNe One' Rosson wrote:
Remember a few months back when it was mentioned that the Netgear FS-105
was on sale at CompUSA. Wel Frye's Electronics has them on sale till
tomorrow for $93.99. Just thought I would let people know there is a
second chance.
I'm very happy with mine.
In message [EMAIL PROTECTED], Warner Losh writes:
: to
:
:sh_subdirs=${SUBDIRS}; for f in $$sh_subdirs ; do ...
there's lots of other workarounds, from seeing if SUBDIRS is defined,
to using make's .foreach.
Another option is:
for f in $$empty_list ${SUBDIRS};
John Baldwin wrote:
On 06-Mar-00 Yevmenkin, Maksim N, CSCIO wrote:
[...]
What's the reason for locking the file descriptors
for *all* system calls? especially those I mentioned?
Where is pthread_cancel() ?
are you using -stable (3.x)? there is no ``pthread_cancel'' in -stable.
Can anyone tell me where is the code for pci_intr_establish() and
_thread_sys_read()? I could not find them under /usr/src.
Thanks,
-Zhihui
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Mon, 6 Mar 2000, Wes Peters wrote:
John Baldwin wrote:
On 06-Mar-00 Yevmenkin, Maksim N, CSCIO wrote:
[...]
What's the reason for locking the file descriptors
for *all* system calls? especially those I mentioned?
Where is pthread_cancel() ?
are you using -stable
Version 2 of the lock manager is ready to be released. Amitha
says that it passes all of the tests in the suite posted by Drew (thanks
Drew). A noteable exception to this is on SGI where some lock requests
are never even received from the remote host. Also DOS sharing is not
yet complete.
On
49 matches
Mail list logo
