Steve Franks wrote:
Seems there is a more appropriate list for my earlier question to
freebsd-questions:
On and on I charge porting linux engineering tools. Major pita. I
see a bunch of #ifdef __APPLE__ lines to pull in alternate headers;
what's the equiv for FreeBSD?
__FreeBSD__
but it is m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Franks wrote:
| Seems there is a more appropriate list for my earlier question to
| freebsd-questions:
|
| On and on I charge porting linux engineering tools. Major pita. I
| see a bunch of #ifdef __APPLE__ lines to pull in alternate headers;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Franks wrote:
| The manpage
(http://www.freebsd.org/cgi/man.cgi?query=clock_gettime&sektion=2&apropos=0&manpath=FreeBSD+7.0-RELEASE)
| for clock_gettime() specifies the correct header as , which I
| am using, and I don't see any errors on clock_
Seems there is a more appropriate list for my earlier question to
freebsd-questions:
On and on I charge porting linux engineering tools. Major pita. I
see a bunch of #ifdef __APPLE__ lines to pull in alternate headers;
what's the equiv for FreeBSD?
Thanks,
Steve
On Fri, May 09, 2008 at 07:54:40PM +0200, Anders Nore wrote:
> You are probably right, but how would you store the key's? Is storing the
> key as e.g., 'portname-1.2_3+CONTENT' a good solution?
I'd just use a different db file. I am not sure how much the following
applies to FreeBSD as pkg_instal
The manpage
(http://www.freebsd.org/cgi/man.cgi?query=clock_gettime&sektion=2&apropos=0&manpath=FreeBSD+7.0-RELEASE)
for clock_gettime() specifies the correct header as , which I
am using, and I don't see any errors on clock_gettime(), but the param
I need, listed in the manpage, CLOCK_REALTIME is
On Fri, 09 May 2008 19:06:33 +0200, Joerg Sonnenberger
<[EMAIL PROTECTED]> wrote:
On Fri, May 09, 2008 at 06:50:10PM +0200, Anders Nore wrote:
Yes that would probably be bad for the database, but I'm sure one can
manage to get around this problem by copying it before changing the db
and
del
According to Bruce Cran:
> I've attached a patch which implements this (the change to loginrec.c
> reverts it back to the default OpenSSH code) and was wondering if someone
> could take a look at it.
If you have not already done so, please use send-pr to record it in GNATS,
that will help not fo
According to Anders Nore:
> with the base system (/usr/src/include/db.h). BerkeleyDB is not you're
> typical relational db, and can only save key/value pairs. The way I'm
> thinking of storing information to the .db is to name the keys as the
> directory names in /var/db/pkg. And save the +* fil
On Fri, May 09, 2008 at 06:50:10PM +0200, Anders Nore wrote:
> Yes that would probably be bad for the database, but I'm sure one can
> manage to get around this problem by copying it before changing the db and
> delete the copy if it doesn't fail. At the next time executed it will check
> for a
On Fri, 09 May 2008 14:43:08 +0200, Joerg Sonnenberger
<[EMAIL PROTECTED]> wrote:
On Fri, May 09, 2008 at 01:52:46PM +0200, Anders Nore wrote:
I'm working on adding .db support to the pkg_tools( i.e. pkg_add,
pkg_info,
etc. ) as part of SoC 2008. The database api used is BerkeleyDB that
co
On Thu, May 01, 2008 at 09:16:28PM -0700, Tim Kientzle wrote:
> In all of these cases, though, adding a space between the '0' and
> the 'b' changes the meaning, so is wrong. Indent can
> change/insert whitespace, but should never do so in a way that
> changes the meaning of the program. In all of
Hi,
After upgrading to 7-stable with sources of about 2 weeks ago I'm
seeing panics about once every 2 days, see below. I've posted to
stable@ two days ago, but got no reactions. Nobody else seems to have
this issue according to google.
Any ideas?
Ruben
Fatal trap 12: page fault while in kerne
On Friday 09 May 2008 13:52:46 Anders Nore wrote:
> I'm working on adding .db support to the pkg_tools( i.e. pkg_add,
> pkg_info, etc. ) as part of SoC 2008.
Is this gonna be optional?
> One problem lies with the +* files which is scripts (e.g., +INSTALL,
> +DEINSTALL). I've gotten some input th
Hello.
For example:
pf.conf
ext_if="xl0"
ip_world="nn.nn.nn.nn"
# Filter rules
block log all
anchor in on $ext_if {
pass quick proto tcp to $ip_world port 22 keep state
# SSH
pass quick proto tcp to $ip_world port 25 keep state
# SMTP
pass
On Fri, May 09, 2008 at 01:52:46PM +0200, Anders Nore wrote:
> I'm working on adding .db support to the pkg_tools( i.e. pkg_add, pkg_info,
> etc. ) as part of SoC 2008. The database api used is BerkeleyDB that comes
> with the base system (/usr/src/include/db.h). BerkeleyDB is not you're
> typic
Hi,
I'm working on adding .db support to the pkg_tools( i.e. pkg_add,
pkg_info, etc. ) as part of SoC 2008. The database api used is BerkeleyDB
that comes with the base system (/usr/src/include/db.h). BerkeleyDB is not
you're typical relational db, and can only save key/value pairs. The way
17 matches
Mail list logo
