Re: your mail
bar On Sun, Jan 17, 2021 at 02:56:52PM +0100, Klemens Nanni wrote: > foo
Re: your mail
On Mon, Dec 10, 2018 at 09:44:05AM +0100, Jan Stary wrote: > Currently, pcap_setdirection() is described in pcap.3 as follows: > > pcap_setdirection() is used to limit the direction > that packets must be flowing in order to be captured. > > The "direction" is not described, except in pcap.h. > Should the constants be mentioned in the manpage? > Also, the direction only seems to matter for live captures. > > Jan > fixed, thanks. jmc > > Index: pcap.3 > === > RCS file: /cvs/src/lib/libpcap/pcap.3,v > retrieving revision 1.48 > diff -u -p -r1.48 pcap.3 > --- pcap.33 Jun 2018 10:45:15 - 1.48 > +++ pcap.310 Dec 2018 07:12:53 - > @@ -535,6 +535,15 @@ datalink types. > .Fn pcap_setdirection > is used to limit the direction that packets must be flowing in order > to be captured. > +The direction is either > +.Dv PCAP_D_INOUT , > +.Dv PCAP_D_IN > +or > +.Dv PCAP_D_OUT . > +Direction is only relevant to live captures. > +When reading from a dump file, > +.Fn pcap_setdirection > +has no effect . > .Pp > .Fn pcap_list_datalinks > returns an array of the supported datalink types for an opened live capture >
Re: your mail
On 2015/09/09 11:33, James Turner wrote: > espie@openbsd, dera...@cvs.openbsd.org > Bcc: > Subject: Re: sqlite 3.8.11.1 > Reply-To: > In-Reply-To: <20150909084510.gh30...@tazenat.gentiane.org> > > On Wed, Sep 09, 2015 at 08:45:10AM +, Miod Vallat wrote: > > > Hi, > > > > > > thanks to the hard work of jturner@, here's a 650kb gzipped update to > > > sqlite 3.8.11.1, bumping shlib to 31.0. This is needed for upcoming > > > firefox 41 update, but anyone is welcome to look into the update itself. > > > > > > Not attaching the diff because of the size, available at > > > http://rhaalovely.net/~landry/stuff/sqlite-3.8.11.1.diff.gz > > > > Do we really need to import lib/libsqlite3/ext/fts5/test/ which amounts > > for half of the diff? > > > > To give a little background on why we have all these directories and > files based on my understanding... > > When espie@ imported sqlite he wanted to follow upstream so he imported > what was distrubuted with sqlite. Since then we do tagged (based on the > sqlite version) imports whenever we do an update. So when a diff is sent > out it includes all new files in that sqlite release. In this case there > is a new fts5 backend which contains a lot of tests (which we never > run). We also haven't enabled the fts5 backend at this time. > > Now we could change strategies and I could only create a diff of the > changes we actually want and then remove all these extra files from our > tree and the use commit rather then import going forward. > > I would be fine with this as it would make each update more manageable > but I'm not sure what espie@ original goals where with following > upstream. With nsd/unbound we have been removing the unused files. There are arguments in either direction of course.
Re: your mail
unrelated to this topic, I suspect your smtpd is fairly old right ? On Wed, Sep 09, 2015 at 11:33:57AM -0400, James Turner wrote: > espie@openbsd, dera...@cvs.openbsd.org > Bcc: > Subject: Re: sqlite 3.8.11.1 > Reply-To: > In-Reply-To: <20150909084510.gh30...@tazenat.gentiane.org> > > On Wed, Sep 09, 2015 at 08:45:10AM +, Miod Vallat wrote: > > > Hi, > > > > > > thanks to the hard work of jturner@, here's a 650kb gzipped update to > > > sqlite 3.8.11.1, bumping shlib to 31.0. This is needed for upcoming > > > firefox 41 update, but anyone is welcome to look into the update itself. > > > > > > Not attaching the diff because of the size, available at > > > http://rhaalovely.net/~landry/stuff/sqlite-3.8.11.1.diff.gz > > > > Do we really need to import lib/libsqlite3/ext/fts5/test/ which amounts > > for half of the diff? > > > > To give a little background on why we have all these directories and > files based on my understanding... > > When espie@ imported sqlite he wanted to follow upstream so he imported > what was distrubuted with sqlite. Since then we do tagged (based on the > sqlite version) imports whenever we do an update. So when a diff is sent > out it includes all new files in that sqlite release. In this case there > is a new fts5 backend which contains a lot of tests (which we never > run). We also haven't enabled the fts5 backend at this time. > > Now we could change strategies and I could only create a diff of the > changes we actually want and then remove all these extra files from our > tree and the use commit rather then import going forward. > > I would be fine with this as it would make each update more manageable > but I'm not sure what espie@ original goals where with following > upstream. > > -- > James Turner > -- Gilles Chehade https://www.poolp.org @poolpOrg
Re: your mail
On Wed, Sep 09, 2015 at 06:13:11PM +0200, Gilles Chehade wrote: > unrelated to this topic, I suspect your smtpd is fairly old right ? > Running a snapshot from 9/2. > On Wed, Sep 09, 2015 at 11:33:57AM -0400, James Turner wrote: > > espie@openbsd, dera...@cvs.openbsd.org > > Bcc: > > Subject: Re: sqlite 3.8.11.1 > > Reply-To: > > In-Reply-To: <20150909084510.gh30...@tazenat.gentiane.org> > > > > On Wed, Sep 09, 2015 at 08:45:10AM +, Miod Vallat wrote: > > > > Hi, > > > > > > > > thanks to the hard work of jturner@, here's a 650kb gzipped update to > > > > sqlite 3.8.11.1, bumping shlib to 31.0. This is needed for upcoming > > > > firefox 41 update, but anyone is welcome to look into the update itself. > > > > > > > > Not attaching the diff because of the size, available at > > > > http://rhaalovely.net/~landry/stuff/sqlite-3.8.11.1.diff.gz > > > > > > Do we really need to import lib/libsqlite3/ext/fts5/test/ which amounts > > > for half of the diff? > > > > > > > To give a little background on why we have all these directories and > > files based on my understanding... > > > > When espie@ imported sqlite he wanted to follow upstream so he imported > > what was distrubuted with sqlite. Since then we do tagged (based on the > > sqlite version) imports whenever we do an update. So when a diff is sent > > out it includes all new files in that sqlite release. In this case there > > is a new fts5 backend which contains a lot of tests (which we never > > run). We also haven't enabled the fts5 backend at this time. > > > > Now we could change strategies and I could only create a diff of the > > changes we actually want and then remove all these extra files from our > > tree and the use commit rather then import going forward. > > > > I would be fine with this as it would make each update more manageable > > but I'm not sure what espie@ original goals where with following > > upstream. > > > > -- > > James Turner > > > > -- > Gilles Chehade > > https://www.poolp.org @poolpOrg -- James Turner
Re: your mail
On Wed, Sep 09, 2015 at 06:13:11PM +0200, Gilles Chehade wrote: > unrelated to this topic, I suspect your smtpd is fairly old right ? > If this is about my fucked up response I think that was all on me and a failed Mutt reply. > On Wed, Sep 09, 2015 at 11:33:57AM -0400, James Turner wrote: > > espie@openbsd, dera...@cvs.openbsd.org > > Bcc: > > Subject: Re: sqlite 3.8.11.1 > > Reply-To: > > In-Reply-To: <20150909084510.gh30...@tazenat.gentiane.org> > > > > On Wed, Sep 09, 2015 at 08:45:10AM +, Miod Vallat wrote: > > > > Hi, > > > > > > > > thanks to the hard work of jturner@, here's a 650kb gzipped update to > > > > sqlite 3.8.11.1, bumping shlib to 31.0. This is needed for upcoming > > > > firefox 41 update, but anyone is welcome to look into the update itself. > > > > > > > > Not attaching the diff because of the size, available at > > > > http://rhaalovely.net/~landry/stuff/sqlite-3.8.11.1.diff.gz > > > > > > Do we really need to import lib/libsqlite3/ext/fts5/test/ which amounts > > > for half of the diff? > > > > > > > To give a little background on why we have all these directories and > > files based on my understanding... > > > > When espie@ imported sqlite he wanted to follow upstream so he imported > > what was distrubuted with sqlite. Since then we do tagged (based on the > > sqlite version) imports whenever we do an update. So when a diff is sent > > out it includes all new files in that sqlite release. In this case there > > is a new fts5 backend which contains a lot of tests (which we never > > run). We also haven't enabled the fts5 backend at this time. > > > > Now we could change strategies and I could only create a diff of the > > changes we actually want and then remove all these extra files from our > > tree and the use commit rather then import going forward. > > > > I would be fine with this as it would make each update more manageable > > but I'm not sure what espie@ original goals where with following > > upstream. > > > > -- > > James Turner > > > > -- > Gilles Chehade > > https://www.poolp.org @poolpOrg -- James Turner
Re: your mail
In OpenBSD we just write that as free(mp), the if isn't required. Will remember it ;-) Index: fuse.c === RCS file: /cvs/src/lib/libfuse/fuse.c,v retrieving revision 1.24 diff -u -p -r1.24 fuse.c --- fuse.c 20 May 2014 13:32:22 - 1.24 +++ fuse.c 2 Jan 2015 16:53:30 - @@ -493,5 +493,7 @@ fuse_main(int argc, char **argv, const s if (!fuse) return (-1); + free(mp); + return (fuse_loop(fuse)); }
Re: your mail
On Sat, Jan 25, 2014 at 11:04:21PM -0600, Shawn K. Quinn wrote: On Sat, Jan 25, 2014, at 08:53 AM, Marc Espie wrote: I agree with so-called having negative connotations. I think both those instances are using it intentionally, namely there are nasty surprises in some MBR blocks that are not covered by the so-called MBR standard. There's an actual MBR standard? If so, maintained by whom? Precisely. MBR is a dark art. We know we produce valid MBR blocks because machines don't blow up on us...
Re: your mail
On Fri, Jan 24, 2014 at 08:08:29PM -0500, Ted Unangst wrote: I generally associate negative connotations with so-called, as in the so-called free world. I wouldn't use it just to name something, as in the kernel is written in the so-called C language. so-called implies it's called this, but it's not. Two imo dubious occurrences in the install notes. It's not a so-called MBR partition; it is an MBR partition. Similarly with hppa LIF. There's one other use in loongson about initrd which seems ok. I agree with so-called having negative connotations. I think both those instances are using it intentionally, namely there are nasty surprises in some MBR blocks that are not covered by the so-called MBR standard. Probably likewise for hppa LIF...
Re: your mail
On Sat, Jan 25, 2014 at 15:53, Marc Espie wrote: On Fri, Jan 24, 2014 at 08:08:29PM -0500, Ted Unangst wrote: I generally associate negative connotations with so-called, as in the so-called free world. I wouldn't use it just to name something, as in the kernel is written in the so-called C language. so-called implies it's called this, but it's not. Two imo dubious occurrences in the install notes. It's not a so-called MBR partition; it is an MBR partition. Similarly with hppa LIF. There's one other use in loongson about initrd which seems ok. I agree with so-called having negative connotations. I think both those instances are using it intentionally, namely there are nasty surprises in some MBR blocks that are not covered by the so-called MBR standard. I'd agree if we were talking about the so-called MBR standard. But the partitions created by fdisk are as close to real as we can make them; they aren't imposters. Note also it's not about boot blocks, this text appears on several archs, including arm, which don't necessarily use MBR booting.
Re: your mail
On Sat, Jan 25, 2014, at 08:53 AM, Marc Espie wrote: I agree with so-called having negative connotations. I think both those instances are using it intentionally, namely there are nasty surprises in some MBR blocks that are not covered by the so-called MBR standard. There's an actual MBR standard? If so, maintained by whom? -- Shawn K. Quinn skqu...@rushpost.com
