Re: cloneable tun
> My favourite "quick-and-dirty" language is Python, and I consider > myself a fairly proficient Python programmer. I've never, ever, done > ioctls from Python, and while it looks indeed as if it is possible to > do so, I'm sure it'd take me some effort to get it right. I definitely agree with your statement! I've found ioctls much easier to perform in brainf*ck than in python. Grumpy
Re: sndio cleanups
> Granted, the trend seems to be that everything excepts BSDs and Linux is > dead anyways, so if it builds there, you should be fine. ;( Does Netcraft confirm this?
Re: dd(1) human-readable output
> This is going to break atleast 3 scripts that get run periodically > on all of my development machines, while I'm happy with adjusting > them (this change would make them smaller actually) I'm unsure if > we want to throw this into the wild, since this output behaviour > is _old_. That's the point, exactly. People (well, scripts written by people) depend on the dd report output format. > Now, a -h button or similar would solve that, but thats fugly. Given dd is non-unixy in its commandline syntax, this would rather be a ``conv='' suboption. Or its own ``summary=human-readable'' option. Definitely not a dash-prefixed option. > So, while I'm all for it, I think the greybeards need to weigh > in on this :) It's not grey, you damn kid. It's ``exhausted tone''. Grumpy
Re: If you are one of the cool kids who cranks kern.bufcachepercent up..
> > @@ -350,7 +359,7 @@ > > * referencing buffers. > > */ > > toggle ^= 1; > > - if (numvnodes > 2 * maxvnodes) > > + if (numvnodes / 2 > maxvnodes) > > toggle = 0; > > + if ((numvnodes >> 1) > maxvnodes) > > slightly better? I find your lack of faith in the compiler disturbing.