Here is a diff to add posix_madvise() to libc.
Mostly from NetBSD.
Index: sys/sys/mman.h
===
RCS file: /cvs/src/sys/sys/mman.h,v
retrieving revision 1.18
diff -u -p -r1.18 mman.h
--- sys/sys/mman.h 21 Jul 2003 22:52:19 -
It really is very simple --
If you get it
(a) build and then tested
(b) then tell me what the growth to the media is
then it can be commited.
I am the custodian of the extremely size-sensitive install media...
> if we are dropping bioctl then we might as well drop CRYPTO. You really
> o
if we are dropping bioctl then we might as well drop CRYPTO. You really
one with the other.
On Mon, Apr 19, 2010 at 09:05:43PM +0200, David Coppa wrote:
> On Mon, Apr 19, 2010 at 8:57 PM, Mark Kettenis
> wrote:
> >> Date: Mon, 19 Apr 2010 07:05:53 +0200
> >> From: David Coppa
> >>
> >> Hi,
> >>
ProleDno spremanje - još 7 dana sa popustom!
Odaberite bilo koja 2 ili više proizvoda iz ponude ProleDno spremanje i
osvojite 10% POPUSTA i POKLON Mini kuhinjsku vagu!
PoE>urite, napravite svoj paket još danas i oD
istite svoj dom uz minimum
napora i za upola kraDe vreme!
Neki od proizvoda
* Claudio Jeker [2010-04-19 18:40]:
> On Mon, Apr 19, 2010 at 04:35:31PM +0200, Henning Brauer wrote:
> > * Gregory Edigarov [2010-04-19 14:36]:
> > > On Mon, 19 Apr 2010 14:18:02 +0200
> > > Henning Brauer wrote:
> > >
> > > > what problem does that solve?
> > > > specifically, what problem do
On Mon, Apr 19, 2010 at 8:57 PM, Mark Kettenis
wrote:
>> Date: Mon, 19 Apr 2010 07:05:53 +0200
>> From: David Coppa
>>
>> Hi,
>> This diff adds missing bits for softraid support into sparc/sparc64
>> ramdisks.
>>
>> Tested on my Blade 150, bsd.rd didn't overflow.
>>
>> Comments? OKs?
>
> For spar
> Date: Mon, 19 Apr 2010 07:05:53 +0200
> From: David Coppa
>
> Hi,
> This diff adds missing bits for softraid support into sparc/sparc64
> ramdisks.
>
> Tested on my Blade 150, bsd.rd didn't overflow.
>
> Comments? OKs?
For sparc64, I think we shouldn't add bioctl this to ramdisk/list and
ra
On Mon, 19 Apr 2010 16:57:38 +0200 "Bret S. Lambert"
wrote:
> src/sys/
> kern/ <- generic stuffs (signals, scheduling, vnodes,
> syscalls) net/<- generic net stuffs (interface handling, pf,
> routing) netinet{,6}/ <- IPv{4,6} stuffs
> net*/ <- non-IP network stuffs
>
On Mon, Apr 19, 2010 at 04:35:31PM +0200, Henning Brauer wrote:
> * Gregory Edigarov [2010-04-19 14:36]:
> > On Mon, 19 Apr 2010 14:18:02 +0200
> > Henning Brauer wrote:
> >
> > > what problem does that solve?
> > > specifically, what problem does this solve that is not solved by
> > > interface
On Mon, Apr 19, 2010 at 8:48 AM, Adam M. Dutko wrote:
> 1) Are there areas that are easier for "relative newbies" to start in
versus
> other areas? I know this depends on a lot of things, to include
experience.
> Hypothetically, someone that has some C experience, but not a lot of
kernel
> (and
> And if you value your sanity, stay out of anything resembling filesystems.
This is a lie.
Hacking on filesystems, and the VFS layer in general is a very rewarding
experince, just ask Bob.
NFS for example, has been a source of joy for OpenBSD developers for
years!
>> 2) Is there something like
On Mon, Apr 19, 2010 at 11:48:02AM -0400, Adam M. Dutko wrote:
> On Mon, Apr 19, 2010 at 10:57 AM, Bret S. Lambert wrote:
>
> >
> > ... ...
>
>
> > Hopefully this is useful for somebody.
> >
>
> It is, thank you.
>
> With regard to the other questions I peppered everyone with... :-)
>
> 1)
On Monday, April 19, "Adam M. Dutko" wrote:
>
> 1) Are there areas that are easier for "relative newbies" to start in versus
> other areas? I know this depends on a lot of things, to include experience.
> Hypothetically, someone that has some C experience, but not a lot of kernel
> (and subsyste
On Mon, Apr 19, 2010 at 11:48:02AM -0400, Adam M. Dutko wrote:
> On Mon, Apr 19, 2010 at 10:57 AM, Bret S. Lambert wrote:
>
> >
> > ... ...
>
>
> > Hopefully this is useful for somebody.
> >
>
> It is, thank you.
>
> With regard to the other questions I peppered everyone with... :-)
>
> 1)
> Neat idea, but you do no sanity checking at all. So you could end up with
> two interfaces with the same name (very bad) or an interface with a name
> that violates the naming scheme.
> Since if_xname is used in various places to identify interfaces changing
> their name is dangerous. e.g. pf and
On Mon, Apr 19, 2010 at 10:57 AM, Bret S. Lambert wrote:
>
> ... ...
> Hopefully this is useful for somebody.
>
It is, thank you.
With regard to the other questions I peppered everyone with... :-)
1) Are there areas that are easier for "relative newbies" to start in versus
other areas? I k
On Mon, Apr 19, 2010 at 09:59:06AM -0400, Adam M. Dutko wrote:
> The obvious answer to this questions is "Just read the source..." but I
> still want to ask if someone is aware of a good overview of the OpenBSD
> source code? I've watched several presentations by Ted Unangst, Jason Dixon
> and co.
* Gregory Edigarov [2010-04-19 14:56]:
> On Mon, 19 Apr 2010 08:34:12 -0400
> Simon Perreault wrote:
>
> > On 2010-04-19 08:31, Gregory Edigarov wrote:
> > > sometimes it is better and necessary to have interfaces named under
> > > one standartized name like fether0... fetherN for example
> >
>
* Stuart Henderson [2010-04-19 14:53]:
> On 2010/04/19 08:34, Simon Perreault wrote:
> > On 2010-04-19 08:31, Gregory Edigarov wrote:
> > >sometimes it is better and necessary to have interfaces named under one
> > >standartized name like fether0... fetherN for example
> >
> > Why? And how can gr
* Gregory Edigarov [2010-04-19 14:36]:
> On Mon, 19 Apr 2010 14:18:02 +0200
> Henning Brauer wrote:
>
> > what problem does that solve?
> > specifically, what problem does this solve that is not solved by
> > interface groups?
> sometimes it is better and necessary to have interfaces named under
The obvious answer to this questions is "Just read the source..." but I
still want to ask if someone is aware of a good overview of the OpenBSD
source code? I've watched several presentations by Ted Unangst, Jason Dixon
and co. and there seems to be a good amount of information spread across the
w
On Mon, 19 Apr 2010 15:05:37 +0200
Claudio Jeker wrote:
> On Mon, Apr 19, 2010 at 03:52:52PM +0300, Gregory Edigarov wrote:
> > On Mon, 19 Apr 2010 08:34:12 -0400
> > Simon Perreault wrote:
> >
> > > On 2010-04-19 08:31, Gregory Edigarov wrote:
> > > > sometimes it is better and necessary to ha
On Mon, Apr 19, 2010 at 03:52:52PM +0300, Gregory Edigarov wrote:
> On Mon, 19 Apr 2010 08:34:12 -0400
> Simon Perreault wrote:
>
> > On 2010-04-19 08:31, Gregory Edigarov wrote:
> > > sometimes it is better and necessary to have interfaces named under
> > > one standartized name like fether0...
On Mon, 19 Apr 2010 08:34:12 -0400
Simon Perreault wrote:
> On 2010-04-19 08:31, Gregory Edigarov wrote:
> > sometimes it is better and necessary to have interfaces named under
> > one standartized name like fether0... fetherN for example
>
> Why? And how can groups not accomplish that?
>
> Sim
On 2010/04/19 08:34, Simon Perreault wrote:
> On 2010-04-19 08:31, Gregory Edigarov wrote:
> >sometimes it is better and necessary to have interfaces named under one
> >standartized name like fether0... fetherN for example
>
> Why? And how can groups not accomplish that?
There is one place I've f
On Mon, 19 Apr 2010 14:17:59 +0200
Alexander Hall wrote:
> On 04/19/10 13:34, Gregory Edigarov wrote:
> > Hello,
> >
> > This diff adds possibility for the network interfaces to have an
> > arbitrary names. this is done via ifconfig name
>
> Just curious... What is the purpose?
>
> For pf.co
On 2010-04-19 08:31, Gregory Edigarov wrote:
sometimes it is better and necessary to have interfaces named under one
standartized name like fether0... fetherN for example
Why? And how can groups not accomplish that?
Simon
--
NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca
STUN/TURN serv
PMTUD can only lower TCP MSS (either the default one or the one
advertised by the peer), not raise it. This is how it was originally but
it regressed at some point. The comments still mention the correct
behaviour, but the code doesn't do what the comments say. This diff
fixes that.
Please te
On Mon, 19 Apr 2010 14:18:02 +0200
Henning Brauer wrote:
> what problem does that solve?
> specifically, what problem does this solve that is not solved by
> interface groups?
sometimes it is better and necessary to have interfaces named under one
standartized name like fether0... fetherN for exa
On Mon, 19 Apr 2010 15:09:00 +0300
Gregory Edigarov wrote:
> On Mon, 19 Apr 2010 13:52:13 +0200
> Claudio Jeker wrote:
>
> > On Mon, Apr 19, 2010 at 02:34:55PM +0300, Gregory Edigarov wrote:
> > > Hello,
> > >
> > > This diff adds possibility for the network interfaces to have an
> > > arbitra
On 04/19/10 13:34, Gregory Edigarov wrote:
> Hello,
>
> This diff adds possibility for the network interfaces to have an arbitrary
> names.
> this is done via ifconfig name
Just curious... What is the purpose?
For pf.conf you can add an interface group name to the interface and use
that as an
> Date: Mon, 19 Apr 2010 13:50:55 +0200
> From: Otto Moerbeek
>
> On Mon, Apr 19, 2010 at 02:34:55PM +0300, Gregory Edigarov wrote:
>
> > Hello,
> >
> > This diff adds possibility for the network interfaces to have an
> > arbitrary names. this is done via ifconfig name
> >
>
> This enables
what problem does that solve?
specifically, what problem does this solve that is not solved by
interface groups?
--
Henning Brauer, h...@bsws.de, henn...@openbsd.org
BS Web Services, http://bsws.de
Full-Service ISP - Secure Hosting, Mail and DNS Services
Dedicated Servers, Rootservers, Applicatio
On Mon, 19 Apr 2010 13:52:13 +0200
Claudio Jeker wrote:
> On Mon, Apr 19, 2010 at 02:34:55PM +0300, Gregory Edigarov wrote:
> > Hello,
> >
> > This diff adds possibility for the network interfaces to have an
> > arbitrary names. this is done via ifconfig name
> >
>
> Neat idea, but you do no
On Mon, Apr 19, 2010 at 02:34:55PM +0300, Gregory Edigarov wrote:
> Hello,
>
> This diff adds possibility for the network interfaces to have an arbitrary
> names.
> this is done via ifconfig name
>
> Please test.
> Thank you.
>
>
> --- /usr/src/sys/net/if.c.origSat Apr 17 12:42:06
On Mon, Apr 19, 2010 at 02:34:55PM +0300, Gregory Edigarov wrote:
> Hello,
>
> This diff adds possibility for the network interfaces to have an arbitrary
> names.
> this is done via ifconfig name
>
Neat idea, but you do no sanity checking at all. So you could end up with
two interfaces with t
Hello,
This diff adds possibility for the network interfaces to have an arbitrary
names.
this is done via ifconfig name
Please test.
Thank you.
--- /usr/src/sys/net/if.c.orig Sat Apr 17 12:42:06 2010
+++ /usr/src/sys/net/if.c Sat Apr 17 13:27:12 2010
@@ -1416,6 +1416,17 @@
On Sun, 11 Apr 2010 18:47:45 +0100 Owain Ainsworth
wrote:
> The tarball that may be found at http://xenocara.org/intel-current.tgz
> contains an update to the intel 2.9.1 driver (the last one that
> supported userland modesetting) with a load of backports for bugfixes
> and performance improvemen
Hi,
This diff adds missing bits for softraid support into sparc/sparc64
ramdisks.
Tested on my Blade 150, bsd.rd didn't overflow.
Comments? OKs?
ciao,
David
Index: distrib/sparc64/bsd.rd/list
===
RCS file: /cvs/src/distrib/sparc6
39 matches
Mail list logo
