Joachim Strmbergson wrote:
http://www.cuj.com/roundup/a.htm
Fast-browsing it seems that conformance visavi STL is not the main focus
of this article. It doeas talk about a STL roundup though.
Exactly,
There isn't a list or table showing the particular issues with the various
STL (compiler
Arjan Knepper wrote:
Joachim Strmbergson wrote:
http://www.cuj.com/roundup/a.htm
Fast-browsing it seems that conformance visavi STL is not the main focus
of this article. It doeas talk about a STL roundup though.
Exactly,
There isn't a list or table showing the particular issues
Benny Prijono wrote:
As far as I notice (I only briefly browse the web version though), the
difference between the printed and the online version is, the printed
version has nice summary table of conformance level test results,
oops...
second browse to the URL reveals that the results
Hi,
Is the following possible to do with the vtund?!
I have one host running FreeBSD 4.2. On that host
I have one "real" ethernet board, rl0. I would like to create
several tap interfaces (managed to do). All packets directed
to the tap interfaces I want to be tunneled through the rl0
interfaces
Gunnar Olsson wrote:
Hi,
Is the following possible to do with the vtund?!
I have one host running FreeBSD 4.2. On that host
I have one "real" ethernet board, rl0. I would like to create
several tap interfaces (managed to do). All packets directed
to the tap interfaces I want to be
Benny Prijono wrote:
Benny Prijono wrote:
As far as I notice (I only briefly browse the web version though), the
difference between the printed and the online version is, the printed
version has nice summary table of conformance level test results,
oops...
second browse to the URL
In message [EMAIL PROTECTED]you write:
}
}--tKW2IUtsqtDRztdT
}Content-Type: text/plain; charset=us-ascii
}Content-Disposition: inline
}Content-Transfer-Encoding: quoted-printable
}
}On Thu, Mar 29, 2001 at 12:29:55PM +0200, Danny Braniss wrote:
}
} }Please post the output of env(1) when run as
On Wed, 28 Mar 2001, Dennis wrote:
At 04:22 PM 03/28/2001, Chistopher S. Weimann wrote:
On Wed, Mar 14, 2001 at 12:33:21PM -0500, Dennis wrote:
Your logic is backwards. You think that rewarding mediocre companies will
scare good companies into wanting a piece of the pie. The only
In article [EMAIL PROTECTED],
Alfred Perlstein [EMAIL PROTECTED] wrote:
I can't seem to get a crashdump, is there a way to take a
ddb crash address: "Stopped at lf_setlock+0x52"
and boot later and see what line of code that's on?
Assuming you have a corresponding kernel with debugging
On Wed, Mar 28, 2001 at 01:56:21PM -0800, Mike Smith wrote:
Anyway, I just had a quick look, and I think that your basic problem is
that MAKEDEV uses the wrong encoding for devices above 255. This is
fixed in -CURRENT, and if you bring back the unit2minor changes from
there to -STABLE you
On Wed, 28 Mar 2001, Murray Stokely wrote:
The NetBSD guys have STLport in 'pkgsrc' to facilitate the
progress they've made with OpenOffice. I haven't looked at the
changes they made but as soon as I get NetBSD on that U1 I'll take
a look at it.
Open Source Tripwire is now ported to
Sorry, away for a couple of days...but yes, I am firewalled (ipfw, I beleive
I'm running 4.2 current, although kernel says 4.3 beta...I cvsup-ed and this
is a by product). fxp0 is external if, tun0 is pppoe if pointed at fxp0 and
fxp1 is internal. I have no problem scanning to internal addrs,
On Wed, 28 Mar 2001, Dennis wrote:
it doesnt "hurt" at all. Dealing with bitter losers is part of the public
experience :-)
Thanks for the tip. i'll forward it to the customer who needs it and let
him do the work. I've got some more flames to deflect :-)
Dennis, comments like this are the
god,
thas what i am trying to say.../dev/ad0 or /dev/wd0 whatever is not working
whereas /dev/hda in Linux is workinf perfectly...
also hexdump /dev/hda ( in Linux) and hexdump /dev/ad0 (or /dev/wd0) gave me the
same results
now can anyone answer that
thanks
To Unsubscribe: send mail to
On 29-Mar-01 John Baldwin wrote:
On 29-Mar-01 Alfred Perlstein wrote:
I can't seem to get a crashdump, is there a way to take a
ddb crash address: "Stopped at lf_setlock+0x52"
and boot later and see what line of code that's on?
l *lf_setlock+0x52
For example, on one of my SMP test
At 11:01 AM 03/29/2001, you wrote:
On Wed, 28 Mar 2001, Dennis wrote:
At 04:22 PM 03/28/2001, Chistopher S. Weimann wrote:
On Wed, Mar 14, 2001 at 12:33:21PM -0500, Dennis wrote:
Your logic is backwards. You think that rewarding mediocre
companies will
scare good companies into
Sorry everybody, I have to express my opinion now.
Dennis, it seems like that you keep repeating yourself here
And you keep being wrong. As a hardware designer myself, I can
assure you that there is no connection between hardware quality
and level of documentation.
And having fought with
Hello.
I'm using FreeBSD 4.1. My kernel contains the ata driver for the IDE
controllers. I understand that the ata driver has replaced the wd driver. My
question is:-
1. Are there any / Do I need to use certain flags to enable LBA, DMA, etc.
features like for the wd driver? Or is this done
Hello.
While configuring my kernel configuration file, I notice that certain
entries have numbers after the driver and some don't. For example: -
device psm0
device da
My questions are:-
1. What's the number behind the driver?
2. Why for some entries there are no numbers?
At 07:20 PM 03/29/2001, Soren Kristensen wrote:
Sorry everybody, I have to express my opinion now.
Dennis, it seems like that you keep repeating yourself here
And you keep being wrong. As a hardware designer myself, I can
assure you that there is no connection between hardware quality
and
There is an ENABLE_ATAPI_DMA or something to that effect in the kernel config
you must set. Read /usr/src/sys/i386/conf/LINT for more info. You may also man
ata.
BSD Blood had the audacity to say:
Hello.
I'm using FreeBSD 4.1. My kernel contains the ata driver for the IDE
controllers. I
Some are legacy drivers that need space configured in the kernel for them.
Others are newer PCI devices that can auto-attach. This stuff is being
phased-out in -current.
BSD Blood had the audacity to say:
Hello.
While configuring my kernel configuration file, I notice that certain
On 30-Mar-2001 Coleman Kane wrote:
There is an ENABLE_ATAPI_DMA or something to that effect in the kernel config
you must set. Read /usr/src/sys/i386/conf/LINT for more info. You may also man
ata.
That only affects ATAPI devices (ie not hard drives).
You can enable write caching and
subscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
It seems BSD Blood wrote:
Hello.
I'm using FreeBSD 4.1. My kernel contains the ata driver for the IDE
controllers. I understand that the ata driver has replaced the wd driver. My
question is:-
1. Are there any / Do I need to use certain flags to enable LBA, DMA, etc.
features like
Hi!
I previously sent this message to the questions list but I didn't
receive an answer. That is why I'm now trying this list.
I'm gathering some performance data of some 4.1.1 kernel routines by
means of rtsc() calls. For storing the performance data, I have defined
an array of u_int64_t. For
Can someone pls tell me if it is possible to define an array of size 0.
Not in C.
GCC and most other compilers support it.
I do it all the time (see all the various netgraph structures) however it must
be the LAST item in the structure. It gives the address of the first byte
AFTER the
On Thu, Mar 29, 2001 at 09:40:05PM -0500, Dennis wrote:
3com never has,
Uh, how do you think Bill Paul wrote the xl driver?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
In message [EMAIL PROTECTED], Todd Whitesel writes:
Just put a 1-element array at the end of your header struct, and account for
it when you work out how much extra space to allocate. C memory layout rules
guarantee that this usage will have the desired effect.
Nope, not portable. The
* Peter Seebach [EMAIL PROTECTED] [010329 23:49] wrote:
In message [EMAIL PROTECTED], Todd Whitesel writes:
Just put a 1-element array at the end of your header struct, and account for
it when you work out how much extra space to allocate. C memory layout rules
guarantee that this usage will
On Thu, 29 Mar 2001, Alfred Perlstein wrote:
AP* Peter Seebach [EMAIL PROTECTED] [010329 23:49] wrote:
AP In message [EMAIL PROTECTED], Todd Whitesel writes:
AP Just put a 1-element array at the end of your header struct, and account for
AP it when you work out how much extra space to allocate.
31 matches
Mail list logo
