Re: boot from softraid, backspace in passphrase prompt

Since people are typing blind, can you add support for ^U as well? > I want correct typing mistakes when booting from softraid crypto disks. > Can we handle at least the backspace key, plz^Hease? :) > > diff --git sys/arch/amd64/stand/libsa/softraid.c > sys/arch/amd64/stand/libsa/softraid.c >

Re: WAPBL implementation

On Wed, Oct 28, 2015 at 09:06:54AM -0200, Walter Neto wrote: > Adding WAPBL support for dumpfs(8) > > next diffs: > - tunefs(8) showing log information and setting log size > - fsck_ffs(8) WAPBL support > > ok jasper@ Correction: I only pointed out that we should have the option to somehow get

Re: WAPBL implementation

Adding WAPBL support for dumpfs(8) next diffs: - tunefs(8) showing log information and setting log size - fsck_ffs(8) WAPBL support ok jasper@ Index: sbin/dumpfs/dumpfs.c === RCS file: /Volumes/CSP/cvs/src/sbin/dumpfs/dumpfs.c,v

boot from softraid, backspace in passphrase prompt

I want correct typing mistakes when booting from softraid crypto disks. Can we handle at least the backspace key, plz^Hease? :) diff --git sys/arch/amd64/stand/libsa/softraid.c sys/arch/amd64/stand/libsa/softraid.c index 336865a..801cec4 100644 --- sys/arch/amd64/stand/libsa/softraid.c +++

Re: (patch) tcpdump cleanup stats format

Kevin Reay writes: > Correct printf format for received/dropped packet counts in cleanup(). Committed, thanks. > ps_recv and ps_drop (struct pcap_stat) are both type u_int. > Index: tcpdump.c > === >

[PATCH] Add a simple roundrobin load balancing feature to rebound(8)

Hi, I thought it would be cool for rebound(8) to load balance on a number of DNS servers. While I was working on this, I did not manage to convince myself as to whether this should be the default behaviour. An alternative default would be to use the master server provided. If requests started

(patch) tcpdump cleanup stats format

Correct printf format for received/dropped packet counts in cleanup(). ps_recv and ps_drop (struct pcap_stat) are both type u_int. Index: tcpdump.c === RCS file: /cvs/src/usr.sbin/tcpdump/tcpdump.c,v retrieving revision 1.75 diff -u

pledge(2) and spamd(8)

Hi I was just trying to pledge(2) spamd(8), nevertheless came across 2 priviliges kern_pledge.c is missing for this to work. First spamd(8) needs to read sysctl kern.maxfiles in order to see if it can launch with that value or not, and second if the multicast options are passed as

Re: [PATCH] Use rbtree for looking up the client in rebound(8)

On Tue, Oct 27, 2015 at 05:20:31PM -0400, Ted Unangst wrote: > Dimitris Papastamos wrote: > > There was a comment in the code that indicated that it might be worth > > investigating the use of trees. I have not currently done any kind of > > serious benchmarking on this but I am looking into it.

calloc -> malloc in get_data() and get_string()

Relayd, httpd, and ntpd define the functions get_data() and get_string(). Both call calloc and then immediately memcpy. Calloc's zeroing isn't optimized out. These functions are called in network data paths in at least a couple places, so all this extra writing could have a meaningful performance

Re: pledge(2) and spamd(8)

> I was just trying to pledge(2) spamd(8), nevertheless came across 2 > priviliges kern_pledge.c is missing for this to work. > > First spamd(8) needs to read sysctl kern.maxfiles in order to see if it > can launch with that value or not, and second if the multicast options > are passed as

Patch 1/3 - make DIOCRADDADDRS to accept on IP address per ioctl() call

Hello, this is the first patch in series of three. All patches modify PF radix table API such the ioctl() functions accept one IP address per call. The idea has been proposed by Claudio at Varazdin. I still have to untangle pfr_commit_ktable() and DIOCRSETADDRS ioctl. Both seem to be more

Patch 2/3 - make DIOCRDELADDRS to accept on IP address per ioctl() call

Hello, this is the second patch in 3-patch series. Patch changes DIOCRDELADDRS ioctl to DIOCRDELADDR, which accepts one IP address only per ioctl(2) call. Patch updates kernel and pfctl(8) only. Other components, which happen to use DIOCRDELADDRS will be updated by extra patch. thanks and

Patch 3/3 - update userland to reflect DIOCRADDADDRS/DIOCRDELADDRS changes

Hello, this is the third patch in the first PF radix changes batch. Patch requires earlier patches to be in place, otherwise compilation will fail. Patch updates various user land tools by new PF radix table changes: s/DIOCRADDADDRS/DIOCRADDADDR s/DIOCRDELADDRS/DIOCRDELADDR it's also

Re: pledge(2) and spamd(8)

On 2015-10-28 17:47, Theo de Raadt wrote: >> I was just trying to pledge(2) spamd(8), nevertheless came across 2 >> priviliges kern_pledge.c is missing for this to work. >> >> First spamd(8) needs to read sysctl kern.maxfiles in order to see if it >> can launch with that value or not, and second

Re: preparing pfi_kif to MP world

Hello Mike, just a quick question: are you going to commit your pfi_kif_find() et. al.? or more work is needed there? thanks a lot regards sasha > > Turns out this is a rather simple issue that got slightly > complicated by the code diverging quite a bit since the > inception.

Re: calloc -> malloc in get_data() and get_string()

> Am 28.10.2015 um 17:05 schrieb Michael McConville : > > Relayd, httpd, and ntpd define the functions get_data() and > get_string(). Both call calloc and then immediately memcpy. Calloc's > zeroing isn't optimized out. These functions are called in network data > paths in at

Re: Patch 2/3 - make DIOCRDELADDRS to accept on IP address per ioctl() call

Hello, > > Index: sbin/pfctl/pfctl_radix.c > > + io.pfrio_size = 1; > > in 1/3 you have annotated like this > > + io.pfrio_size = 1; /* TODO: check .pfrio_size is needed */ > sorry this has leaked out from my internal repo. The .pfrio_size member will be dropped as soon as I'll be

patch saves some cycles by extending pfr_walktree() a bit

Hello, This is yet another patch, which 'scratches surface', this time in pf_table.c. As briefly discussed in Varazdin the plan is to clean up pf_table.c a bit, to make implementation of reference handling and further MP stuff bit easier. I've noticed sub-optimal implementation table entries at

Re: pledge(2) and spamd(8)

> Also, I wonder what the point of having a sanity check against > kern.maxfiles at all is, especially with the arbitrary-feeling > additional rule of "maxcon may not exceed kern.maxfiles - 200". It feels > redundant to me, and it sort of makes a promise of protection it can't > uphold. That code

Re: preparing pfi_kif to MP world

On 28 October 2015 at 18:41, Alexandr Nedvedicky wrote: > Hello Mike, > > just a quick question: > > are you going to commit your pfi_kif_find() et. al.? > or more work is needed there? > I need OKs > thanks a lot > regards > sasha > >> >> Turns

Re: calloc -> malloc in get_data() and get_string()

Joerg Jung wrote: > > > > Am 28.10.2015 um 17:05 schrieb Michael McConville : > > > > Relayd, httpd, and ntpd define the functions get_data() and > > get_string(). Both call calloc and then immediately memcpy. Calloc's > > zeroing isn't optimized out. These functions are

cron: get rid of strcmp_until

It was only used in env_set(). I've also removed the useless FACILITY define and fixed a sizeof(). - todd Index: usr.sbin/cron/env.c === RCS file: /cvs/src/usr.sbin/cron/env.c,v retrieving revision 1.29 diff -u -p -u -r1.29 env.c