On Wed, 2007-Jan-31 08:30:27 +0100, Pascal Hofstee wrote:
In a recent attempt in trying to clean up some compiler warnings in a
GNUstep related project i came upon a case where the FreeBSD datatypes
seemed to disagree with the Linux ones. Though this in itself is not
unusual i do wonder if in
Peter Jeremy wrote:
Whilst I agree that the Linux defn is the more sensible one, System V
IPC and common sense are not commonly found together. Tradionally the
definition was int. It appears that the definition changed from
int to size_t in issue 5 of the Open Group base definition but
FreeBSD
Pascal Hofstee [EMAIL PROTECTED] writes:
Any additional sugestions/objections are always greatly appreciated.
On 32-bit platforms (i386, powerpc), int is a 32-bit signed integer
while size_t is a 32-bit unsigned integer.
On 64-bit platforms (amd64, sparc64 etc), int is a 32-bit signed
integer
Daniel Rudy [EMAIL PROTECTED] writes:
I've been taking apart and analyzing the sysctl(8) program to gain a
better insight into how to use the sysctl(3) interface. [...]
It's using an oid of 0 and 2 to get something, then it comes up with 440
and then a sequence of numbers that are
On Wed, 31 Jan 2007, Dag-Erling Smørgrav wrote:
Pascal Hofstee [EMAIL PROTECTED] writes:
Any additional sugestions/objections are always greatly appreciated.
On 32-bit platforms (i386, powerpc), int is a 32-bit signed integer while
size_t is a 32-bit unsigned integer.
On 64-bit platforms
Robert Watson [EMAIL PROTECTED] wrote:
On Wed, 31 Jan 2007, Dag-Erling Smørgrav wrote:
Pascal Hofstee [EMAIL PROTECTED] writes:
Any additional sugestions/objections are always greatly appreciated.
On 32-bit platforms (i386, powerpc), int is a 32-bit signed integer while
size_t is a
Dr. Markus Waldeck wrote:
Oliver Fromme wrote:
Well, an unprivileged user can achieve the same effect by
typing while :; do :; done. There are a thousand ways
to waste CPU time, and there is no way to prevent a user
from doing it.
It is not the same effect.
You describe
Hi Folks,
A new version of the driver is up which fixes the firmware issues.
Seems the wpi-firmware-kmod port was creating corrupt modules.
Things should work much better now. Download at the same place, file:
20070131-wpi-freebsd.tar.gz
Cheers,
Benjamin
Sam Fourman Jr. wrote:
I can
Benjamin Close wrote:
Hi Folks,
A new version of the driver is up which fixes the firmware issues.
Seems the wpi-firmware-kmod port was creating corrupt modules.
Things should work much better now. Download at the same place, file:
20070131-wpi-freebsd.tar.gz
So, when is it going to HEAD
typing while :; do :; done. There are a thousand ways
No. What I write above is not a fork bomb, it's a single
process which is wasting CPU in a busy loop. It's exactly
equivalent to top(1) with zero delay, except that top
produces some output, while a busy loop does nothing useful
at
On Wed, Jan 31, 2007 at 03:42:26PM +0100 I heard the voice of
Oliver Fromme, and lo! it spake thus:
Bottom line: Disabling zero-delay in top doesn't buy you anything
at all.
Meanwhile, you still can't zero-delay unless you're root.
--
Matthew Fuller (MF4839) | [EMAIL PROTECTED]
In [EMAIL PROTECTED], Dr. Markus Waldeck [EMAIL PROTECTED] typed:
typing while :; do :; done. There are a thousand ways
No. What I write above is not a fork bomb, it's a single
process which is wasting CPU in a busy loop. It's exactly
equivalent to top(1) with zero delay, except
On Wed, 2007-Jan-31 10:52:02 +, Robert Watson wrote:
If we do decide to go ahead with the ABI change, there are a number of
other things that should be done simultaneously, such as changing the uid
and gid fields to uid_t and gid_t.
And mode to mode_t. The uid and gid fields in struct
On 1/31/07, Mike Meyer [EMAIL PROTECTED] wrote:
In [EMAIL PROTECTED], Dr. Markus Waldeck [EMAIL PROTECTED]
typed:
typing while :; do :; done. There are a thousand ways
No. What I write above is not a fork bomb, it's a single
process which is wasting CPU in a busy loop. It's exactly
Hello everyone,
I'm using 6-stable on 4 amd64 machines. One of them has FreeBSD on its
local hard drive and others are booted via network with PXE.
But I encounter that /usr/local/etc/rc.d/* are not executed during the
boot process?
Is there some kind of option to change this?
Or may be I
15 matches
Mail list logo
