Re: Question about wscons/wsksymdef.h
On Sat, May 19, 2012 at 01:27:53AM +0200, Juan Francisco Cantero Hurtado wrote: Hi!. This afternoon I was thinking about to change my vim config for to remap the capslock key to control or escape keys. I was searching some of information and I did remember the option nocaps of Xorg. For Xorg /usr/X11R6/share/X11/xkb/rules/base.lst has the list of all possible values for XkbModel, XkbLayout and XkbOptions Also, I've read the man page of wsconsctl and I saw the option swapctrlcaps. So, I decided to look the code of wscons related to this option. I am not a C programmer but I can understand sometimes the simple code. In short. Can someone say me what are these values?. I don't want a master class, just a link or a bit of documentation is sufficient. #define KB_NODEAD 0x01 /* disable dead accents */ #define KB_DECLK0x02 /* DEC LKnnn layout */ #define KB_LK4010x04 /* DEC LK401 instead LK201 */ #define KB_SWAPCTRLCAPS 0x08 /* swap Left-Control and Caps-Lock */ #define KB_DVORAK 0x10 /* Dvorak layout */ #define KB_METAESC 0x20 /* generate ESC prefix on ALT-key */ #define KB_IOPENER 0x40 /* f1-f12 - ESC,f1-f11 */ #define KB_MACHDEP 0x80 /* machine dependent */ #define KB_APPLE0x01 /* Apple specific layout */ Those are arbritrary values corresponding to various flags that can be set with the kbd(8) command, as keymap variant (their names are at the end of wsksymdef.h). Unfortunatly wscons is one of the worse areas of OpenBSD for documentation. To figure out exactly what they do, you need to read the source. For PC style keyboard you can see how keymaps are built from their symbolic names in /sys/dev/pckbc/wskbdmap_mfii.c And if en route you feel like writing some the missing bits of documentation, you're of course welcome ! -- Matthieu Herrb
Re: Using MCLGETI for sk(4)
On Fri, May 18, 2012 at 5:16 AM, Brad Smith b...@comstyle.com wrote: On Mon, May 07, 2012 at 10:24:37AM +0100, Stuart Henderson wrote: On 2012/05/06 21:34, Brad Smith wrote: I have resurrected the old jumbo allocator to MCLGETI conversion diff that was reverted with rev 1.152. The commit did not indicate why that was so. I updated it to -current and have tested it a fair bit on amd64 with a SysKonnect GEnesis board using jumbos and have not found any issues so far. Theo or Stuart can you comment on why this was reverted? Forwarded you some mails offlist, TL;DR version is it dies under heavy packet load. Would be nice to have this back as the jumbo allocator uses a huge wodge of kvm. Not sure if I have a good machine for testing it any more. Ya, so I've heard but cannot reproduce any issues so far. Also test with a Yukon board with multiple ping -f's in both directions. Up to 53 jumbo mbuf clusters allocated so far. skc0 at pci1 dev 7 function 0 Schneider Koch SK-98xx v2.0 rev 0x20, Yukon (0x1): apic 2 int 16 sk0 at skc0 port A: address 00:00:5a:9f:31:32 eephy0 at sk0 phy 0: 88E1011 Gigabit PHY, rev. 3 It appears that MCLGETI() is affected by different chipset revisions . Testing all the revisions is difficult to do. That's why my MCLGETI diffs still sleep in my local tree :-) -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- Brightest day, Blackest night, No bug shall escape my sight, And those who worship evil's mind, be wary of my powers, puffy lantern's light !
Re: Using MCLGETI for sk(4)
On 2012/05/19 19:09, Loganaden Velvindron wrote: On Fri, May 18, 2012 at 5:16 AM, Brad Smith b...@comstyle.com wrote: On Mon, May 07, 2012 at 10:24:37AM +0100, Stuart Henderson wrote: On 2012/05/06 21:34, Brad Smith wrote: I have resurrected the old jumbo allocator to MCLGETI conversion diff that was reverted with rev 1.152. The commit did not indicate why that was so. I updated it to -current and have tested it a fair bit on amd64 with a SysKonnect GEnesis board using jumbos and have not found any issues so far. Theo or Stuart can you comment on why this was reverted? Forwarded you some mails offlist, TL;DR version is it dies under heavy packet load. Would be nice to have this back as the jumbo allocator uses a huge wodge of kvm. Not sure if I have a good machine for testing it any more. Ya, so I've heard but cannot reproduce any issues so far. Also test with a Yukon board with multiple ping -f's in both directions. Up to 53 jumbo mbuf clusters allocated so far. skc0 at pci1 dev 7 function 0 Schneider Koch SK-98xx v2.0 rev 0x20, Yukon (0x1): apic 2 int 16 sk0 at skc0 port A: address 00:00:5a:9f:31:32 eephy0 at sk0 phy 0: 88E1011 Gigabit PHY, rev. 3 It appears that MCLGETI() is affected by different chipset revisions . Testing all the revisions is difficult to do. That's why my MCLGETI diffs still sleep in my local tree :-) Looking at old dmesg, mine would have been this one, skc0 at pci1 dev 6 function 0 3Com 3c940 rev 0x10, Yukon (0x1): apic 2 int 3 (irq 3) sk0 at skc0 port A: address 00:0a:5e:1a:a3:00 eephy0 at sk0 phy 0: Marvell 88E1011 Gigabit PHY, rev. 3 Not sure what card gollo@ was using.
Re: Question about wscons/wsksymdef.h
On Fri, May 18, 2012 at 07:07:17PM -0700, Matthew Dempsky wrote: On Fri, May 18, 2012 at 4:27 PM, Juan Francisco Cantero Hurtado i...@juanfra.info wrote: In short. Can someone say me what are these values?. I don't want a master class, just a link or a bit of documentation is sufficient. Are you just trying to swap caps and ctrl at the console? If so, just put us.swapctrlcaps (or whatever) in /etc/kbdtype and reboot. (Or run kbd us.swapctrlcaps as root to do it instantly.) I know. No, I'm playing with wscons for add a nocaps option. Just for curiosity. -- Juan Francisco Cantero Hurtado http://juanfra.info
Re: Question about wscons/wsksymdef.h
On Sat, May 19, 2012 at 08:45:48AM +0200, Matthieu Herrb wrote: On Sat, May 19, 2012 at 01:27:53AM +0200, Juan Francisco Cantero Hurtado wrote: Hi!. This afternoon I was thinking about to change my vim config for to remap the capslock key to control or escape keys. I was searching some of information and I did remember the option nocaps of Xorg. For Xorg /usr/X11R6/share/X11/xkb/rules/base.lst has the list of all possible values for XkbModel, XkbLayout and XkbOptions Thanks. Good to know. Also, I've read the man page of wsconsctl and I saw the option swapctrlcaps. So, I decided to look the code of wscons related to this option. I am not a C programmer but I can understand sometimes the simple code. In short. Can someone say me what are these values?. I don't want a master class, just a link or a bit of documentation is sufficient. #define KB_NODEAD 0x01 /* disable dead accents */ #define KB_DECLK0x02 /* DEC LKnnn layout */ #define KB_LK4010x04 /* DEC LK401 instead LK201 */ #define KB_SWAPCTRLCAPS 0x08 /* swap Left-Control and Caps-Lock */ #define KB_DVORAK 0x10 /* Dvorak layout */ #define KB_METAESC 0x20 /* generate ESC prefix on ALT-key */ #define KB_IOPENER 0x40 /* f1-f12 - ESC,f1-f11 */ #define KB_MACHDEP 0x80 /* machine dependent */ #define KB_APPLE0x01 /* Apple specific layout */ Those are arbritrary values corresponding to various flags that can be set with the kbd(8) command, as keymap variant (their names are at the end of wsksymdef.h). I assumed the numbers are random but I wanted to be sure. Perfect. Unfortunatly wscons is one of the worse areas of OpenBSD for documentation. To figure out exactly what they do, you need to read the source. For PC style keyboard you can see how keymaps are built from their symbolic names in /sys/dev/pckbc/wskbdmap_mfii.c Yep, I've modified wskbdmap_mfii.c, ukbdmap.c and wsksymdef.h. Fortunately, add a new option is easy for a newbie like me. And if en route you feel like writing some the missing bits of documentation, you're of course welcome ! I know :P . The OpenBSD devs are very open a new contributions. Thanks for all the info. -- Juan Francisco Cantero Hurtado http://juanfra.info
Re: Future of PF
On Sat, May 19, 2012 at 10:51:31PM +0300, wishmaster wrote: Hi. I use PF in both OS'es: Free and OpenBSD. This is great firewall. But today statefull firewalling and inspecting packet headers only, traffic classification and prioritization by port number only - it is not enough for complex firewalling/shaping/prioritization/etc. Outside window - XXIst century and today it is necessary to have more advanced tool. I am about DIFFUSE. http://www.caia.swin.edu.au/urp/diffuse/intro.html In future (maybe in 10.X) it will be in the base FreeBSD system as part of IPFW. It is available for Linux and OpenWRT as well. My suggestion is to integrate DIFFUSE into PF as well. We need keep pace with time and only this way will let PF to be one of the best firewall solution. You can suggest whatevery you want, words are for free : jirib
