Re: bug in COM-port subsystem

2011-03-10 Thread Anton Maksimenkov
2011/3/11 Anton Maksimenkov : > If some process can catch COM port in a way that noone can use the > port and noone can kill that process - it is wrong situation. And here is the quick path which solves the problem: --- /usr/origsrc/sys/kern/tty.c Mon Oct 11 22:20:15 2010 +++ /usr/src/sys/kern/tt

Reflex Digitales - Últimas unidades a precios inmejorables

2011-03-10 Thread DigitalesNet
USD 920 Nikon D5000 Kit Cámara digital réflex de objetivos intercambiables / Sensor de imágen CMOS / Tamaño

Re: Incorrect exit status from which(1)/whereis(1)

2011-03-10 Thread Philip Guenther
On Mon, Feb 14, 2011 at 3:31 AM, David Julio wrote: ... > Index: which.c > === > RCS file: /cvs/src/usr.bin/which/which.c,v > retrieving revision 1.16 > diff -u -r1.16 which.c > --- which.c 31 May 2010 14:01:49 - 1.16 > +

Re: bug in COM-port subsystem

2011-03-10 Thread Anton Maksimenkov
2011/3/11 Amit Kulkarni : > I tried to do a similar thing, Ctrl + C on a fsck, kill -9 the fsck > pid. But the process is not able to be killed. Finally found out that > I/O stuff can't be killed in OpenBSD. Since you do I/O to COM port, > and try to kill it... I don't know if its a bug though. An

Re: userland PPP patch for IPv6CP + VLAN interfaces

2011-03-10 Thread Brad
On 03/03/11 2:20 PM, Claudio Jeker wrote: On Wed, Mar 02, 2011 at 06:47:40PM -0500, Brad wrote: Ethernet vlan(4) interfaces have valid Ethernet link layer addresses but use a different interface type (IFT_L2VLAN vs IFT_ETHER). Treat IFT_L2VLAN interfaces like IFT_ETHER interfaces when handling l

Your Summary of junk emails blocked - 1 Junk Emails Blocked

2011-03-10 Thread Admin Junk Summary
Junk Box Summary for: tech@openbsd.org The 1 emails listed below have been placed in your personal Junk Box since your last Junk Box Summary and will be deleted after 30 days. To retrieve any of these messages, visit your Junk Box at: Login using your standard us

Re: Support Netmos 9922 dual PCIe serial port cards

2011-03-10 Thread Mike Larkin
On Fri, Mar 11, 2011 at 12:14:43AM +0100, Mark Kettenis wrote: > > Date: Thu, 10 Mar 2011 14:48:45 -0800 > > From: Mike Larkin > > > > This diff adds support to puc(4) for NetMos 9922 dual serial > > cards. It's pretty straightforward. Tested by me on i386 and > > amd64. > > > > ok? > > Somethi

Re: Support Netmos 9922 dual PCIe serial port cards

2011-03-10 Thread Mike Larkin
On Thu, Mar 10, 2011 at 11:20:57PM +, Stuart Henderson wrote: > On 2011/03/10 14:48, Mike Larkin wrote: > > This diff adds support to puc(4) for NetMos 9922 dual serial > > cards. It's pretty straightforward. Tested by me on i386 and > > amd64. > > > + /* NetMos PCIe Peripheral Controller :D

Re: Support Netmos 9922 dual PCIe serial port cards

2011-03-10 Thread Stuart Henderson
On 2011/03/10 14:48, Mike Larkin wrote: > This diff adds support to puc(4) for NetMos 9922 dual serial > cards. It's pretty straightforward. Tested by me on i386 and > amd64. > + /* NetMos PCIe Peripheral Controller :Dual serial port */ the usual style in this file is like /* Blah blah: 2S */

Re: Support Netmos 9922 dual PCIe serial port cards

2011-03-10 Thread Mark Kettenis
> Date: Thu, 10 Mar 2011 14:48:45 -0800 > From: Mike Larkin > > This diff adds support to puc(4) for NetMos 9922 dual serial > cards. It's pretty straightforward. Tested by me on i386 and > amd64. > > ok? Something slightly smarter might be needed. Can you mail out the pcidump -vxx output for

Support Netmos 9922 dual PCIe serial port cards

2011-03-10 Thread Mike Larkin
This diff adds support to puc(4) for NetMos 9922 dual serial cards. It's pretty straightforward. Tested by me on i386 and amd64. ok? -ml Index: dev/pci/pcidevs === RCS file: /cvs/src/sys/dev/pci/pcidevs,v retrieving revision 1.1590

Missing icps_bmcastecho in netstat.

2011-03-10 Thread Christiano F. Haesbaert
Hi, the following displays rejected icmp echo requests sent to bcast/mcast. Index: inet.c === RCS file: /cvs/src/usr.bin/netstat/inet.c,v retrieving revision 1.115 diff -d -u -p -w -r1.115 inet.c --- inet.c 2 Mar 2011 21:51:14 -0

ral(4) diff

2011-03-10 Thread Tim van der Molen
I have the following ral(4): ral0 at pci0 dev 13 function 0 "Ralink RT2561S" rev 0x00: irq 5, address 00:1d:7d:49:28:92 ral0: MAC/BBP RT2561C, RF RT2527 After a commit from August 2010 (see http://marc.info/?l=openbsd-cvs&m=128095139804862) the ral stopped working: clients could not associate wi

Re: bug in COM-port subsystem

2011-03-10 Thread Amit Kulkarni
I tried to do a similar thing, Ctrl + C on a fsck, kill -9 the fsck pid. But the process is not able to be killed. Finally found out that I/O stuff can't be killed in OpenBSD. Since you do I/O to COM port, and try to kill it... I don't know if its a bug though. hope that helps you On Thu, Mar 10,

TVs LCD y LED SAMSUNG 3D

2011-03-10 Thread DigitalesNet
  TV LCD Samsung 32" Led   USD 940 TV LCD Samsung 40"   USD 1030 TV LCD Samsung 46" Led 3D   USD

Još samo danas najbolji pokloni za dame

2011-03-10 Thread Top Shop
Top Shop Top E-revija: 60, 10. mart 2011. PraktiD na rešenja i saveti za bolji E>ivot Budi fit | DomaDinstvo | Zabava i deca | Svi proizvodi Knjige | Saveti i zabava Top Shop HIT TV proizvodi! Spider Pan - set tiganja Spider pan - set tiganja Derma Seta - set za ulepšavanje Derma Seta

bug in COM-port subsystem

2011-03-10 Thread Anton Maksimenkov
Hi. It seems I catched some bug in kernel. I use some ugly program which connects to COM-port and tries to do some activity. You can see it's source here http://pastebin.com/kHLy26GD I start it and try to kill it # ./ct writing bytes 36[ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ff