So... I've been diagnosing this problem with IPSEC on FreeBSD
interoperating against both a Cisco ASA and a set of FreeS/WAN
clients. The configuration is that dozens of FreeS/WAN clients
connect to the FreeBSD IPSEC gateway --- FreeBSD uses Racoon to
authenticate and exchange keys with them.
Is there a particular reason that nasm comes standard with
FreeBSD and not fasm?
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09/30/11 10:52, Colin Barnabas wrote:
Is there a particular reason that nasm comes standard with FreeBSD
and not fasm?
I think FreeBSD doesn't come standard with nasm either (the base
system uses GNU as).
If you're looking for fasm port it's
Hi,
On Mon, Sep 26, 2011 at 2:23 PM, Arnaud Lacombe lacom...@gmail.com wrote:
Hi,
On Thu, Sep 22, 2011 at 5:26 PM, Ulrich Spörlein u...@spoerlein.net wrote:
On Thu, 2011-09-22 at 15:52:43 -0400, Arnaud Lacombe wrote:
Hi,
On Thu, Sep 22, 2011 at 3:05 PM, Ulrich Spörlein u...@spoerlein.net
Hello, Hackers.
I was surprised, when I discover that size_t are 32-bit wide on
32-bit (i386) system. Which semantic type should I use, for
example, for storing GEOM size in bytes in system-independent way? I
could use uint64_t, of course, but I don't like this solution, as
it very
On 30.09.2011 23:30, Lev Serebryakov wrote:
I was surprised, when I discover that size_t are 32-bit wide on
32-bit (i386) system. Which semantic type should I use, for
example, for storing GEOM size in bytes in system-independent way? I
could use uint64_t, of course, but I don't like this
Hello, Alexander.
You wrote 1 октября 2011 г., 0:51:00:
GEOM uses 64bit off_t for media size and many other things.
off_t is signed! It is ``not accurate enough'' (if you know this
Russian joke) :)))
--
// Black Lion AKA Lev Serebryakov l...@freebsd.org
On 30.09.2011 23:53, Lev Serebryakov wrote:
Hello, Alexander.
You wrote 1 октября 2011 г., 0:51:00:
GEOM uses 64bit off_t for media size and many other things.
off_t is signed! It is ``not accurate enough'' (if you know this
Russian joke) :)))
Let's say negative values reserved for 2^63
2011/9/30 Lev Serebryakov l...@freebsd.org:
Hello, Hackers.
I was surprised, when I discover that size_t are 32-bit wide on
32-bit (i386) system. Which semantic type should I use, for
example, for storing GEOM size in bytes in system-independent way? I
could use uint64_t, of course, but
2011/9/30 Lev Serebryakov l...@freebsd.org:
Hello, Alexander.
You wrote 1 октября 2011 г., 0:51:00:
GEOM uses 64bit off_t for media size and many other things.
off_t is signed! It is ``not accurate enough'' (if you know this
Russian joke) :)))
No, but I now want to know the Russian joke.
Lev Serebryakov l...@freebsd.org wrote:
GEOM uses 64bit off_t for media size and many other things.
off_t is signed! It is ``not accurate enough'' (if you know
this Russian joke) :)))
g_cache and g_nop use uintmax_t (and no, I don't know the joke).
Hi,
What happens if this occurs:
* cpu_idle() is entered
* you enter critical_enter() and call cpu_idleclock()
* an interrupt occurs, scheduling an immediate callout
* .. but you've already set the clock register, so it won't be
serviced until the wait returns.
Perhaps interrupts have to be
12 matches
Mail list logo