I have a little issue with the sys/socket.h file under 4.0. I myself do
not have access to 4.0 myself but am using output others have given me.
Under 3.3 The program source at the bottom compiles fine. Under 4.0 the
problem is that in sys/socket.h the macro CMSG_DATA() uses another macro
Doug Rabson wrote:
On Thu, 1 Jun 2000, Jordan K. Hubbard wrote:
Does this mean we won't get the SMP stuff done next week?
I'm back on the 15th (you gain 10 hours coming back) and the SMP
meeting isn't until the 16th and 17th. Of course it will. :)
So you are running this right
In message [EMAIL PROTECTED], [EMAIL PROTECTED] wri
tes:
[EMAIL PROTECTED]
it hard to compile it under FreeBSD (however I can
compile it under Linux).I get "Buss error" and coredump
It's a simple programming error - you're not initialising the pointer
'q' in main(), so your code is overwriting
-On [2603 08:10], Arnar Mar Hrafnkelsson ([EMAIL PROTECTED]) wrote:
#ifdef HACK
#include machine/param.h
#endif
#include sys/types.h
sys/param.h would be a better solution in this case. FAIK.
--
Jeroen Ruigrok van der Werven Network- and systemadministrator
[EMAIL PROTECTED
Having just read Konstantin Boldyshev's introduction to FreeBSD assembly
programming, I have a couple of questions.
When I looked through some code in the source tree (and with a little
background from the article), I noticed that INT 80 interface appears to
be newer than an older interface,
Running a Dlink quad card (570TX) in 100Mb/s full dup mode the driver
complains about underruns for awhile and then ultimately sets
store_and_forward which seems to make it work.
Is there a way to force this easily? It seems that it should certainly be
the default if full dup 100 mode is
On Fri, 26 May 2000, Andrey A. Chernov wrote:
Yes, #define was a quick solution.
We need either to add a stub or to import ncurses author fix (removing
all trace function from production library).
Latest is better IMHO, but I left to choose best way to Peter.
However you do it, please fix
I was thinking: it seems that Linux will have an IA-64 port
ready when Itanium rolls out, as well as Windows, Solaris, etc.
Is there any effort(or at least, any thought) on making an
IA-64 port of FreeBSD? It seems Intel is trying to push IA-64
to be 'the platform' for servers and
* James Howard [EMAIL PROTECTED] [000603 08:21] wrote:
Having just read Konstantin Boldyshev's introduction to FreeBSD assembly
programming, I have a couple of questions.
When I looked through some code in the source tree (and with a little
background from the article), I noticed that INT
On Sun, Jun 04, 2000 at 01:18:39AM +0800, Belldandy wrote:
I was thinking: it seems that Linux will have an IA-64 port
ready when Itanium rolls out, as well as Windows, Solaris, etc.
Is there any effort(or at least, any thought) on making an
IA-64 port of FreeBSD? It seems Intel is
On Sat, Jun 03, 2000 at 07:10:56PM +0200, Gerald Pfeifer wrote:
On Fri, 26 May 2000, Andrey A. Chernov wrote:
Yes, #define was a quick solution.
We need either to add a stub or to import ncurses author fix (removing
all trace function from production library).
Latest is better IMHO,
Belldandy wrote:
I was thinking: it seems that Linux will have an IA-64 port
ready when Itanium rolls out, as well as Windows, Solaris, etc.
Is there any effort(or at least, any thought) on making an
IA-64 port of FreeBSD?
Please check the mail archives before asking
Is there any effort(or at least, any thought) on making an
IA-64 port of FreeBSD? It seems Intel is trying to push IA-64
to be 'the platform' for servers and workstations, and I think
FreeBSD definitely can't be left out
Intel has furnished us with IA-64 hardware and a porting effort
James Howard wrote:
Having just read Konstantin Boldyshev's introduction to FreeBSD assembly
programming, I have a couple of questions.
When I looked through some code in the source tree (and with a little
background from the article), I noticed that INT 80 interface appears to
be newer
: interface, does this simplfy Linux emulation? Hinder it?
:
: Also, this is more general, what does "CALL 7:0" do?
:
: Sorry for the silly question, I got curious.
:
:I could be totally off base, but I'm pretty sure (from memory) that
:the lcall interface is the ICBS interface (some standard
WHAT IS AN BSD?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
+[ [EMAIL PROTECTED] ]-
| WHAT IS AN BSD?
Automatic Nonsensical Buzzword Service Dispenser
You can identify ANBSDs by their overfrequent use of the words
'Linux' and 'Open Source'. Commonly found in large, slow-moving old economy
companies whose
On Sat, 3 Jun 2000, Jordan K. Hubbard wrote:
Intel has furnished us with IA-64 hardware and a porting effort is
already underway. Contact [EMAIL PROTECTED] if you would like to
help out in some way with the process.
What can those of us just out here do?
To Unsubscribe: send mail to
In muc.lists.freebsd.hackers, you wrote:
On Sat, 3 Jun 2000, Jordan K. Hubbard wrote:
Intel has furnished us with IA-64 hardware and a porting effort is
already underway. Contact [EMAIL PROTECTED] if you would like to
help out in some way with the process.
What can those of us just
At 20:50 03-06-2000 -0400, Thomas M. Sommers wrote:
It isn't the same as Linux's. Linux passes arguments to syscalls in
registers, while FreeBSD puts them on the stack.
It is often possible to write asm code that works on both: You put the
values in the registers and then you push the
20 matches
Mail list logo
