Re: hotplug(4) r1.10 ignoring hotplug_put_event() prior to hotplugopen() [Was: hotplugd(8) ignoring devices attached before boot]

2010-12-13 Thread MERIGHI Marcus
ted.unan...@gmail.com (Ted Unangst), 2010.12.12 (Sun) 19:10 (CET): On Sun, Dec 12, 2010 at 6:36 AM, MERIGHI Marcus mcmer-open...@tor.at wrote: The behaviour change in hotplug(4)/hotplugd(8) after your commit makes it more ``hot plug'', actually. What bothers me (but not many others,

Re: hotplug(4) r1.10 ignoring hotplug_put_event() prior to hotplugopen() [Was: hotplugd(8) ignoring devices attached before boot]

2010-12-13 Thread Mark Kettenis
Date: Mon, 13 Dec 2010 12:48:55 +0100 From: MERIGHI Marcus mcmer-open...@tor.at That sounds good. I was aware of the change, but didn't think anybody would notice. :) A bit late to the game, but I don't really agree with Tedu that the changed behaviour is an improvement. Say I have

Re: hotplug(4) r1.10 ignoring hotplug_put_event() prior to hotplugopen() [Was: hotplugd(8) ignoring devices attached before boot]

2010-12-13 Thread MERIGHI Marcus
mark.kette...@xs4all.nl (Mark Kettenis), 2010.12.13 (Mon) 13:41 (CET): Date: Mon, 13 Dec 2010 12:48:55 +0100 From: MERIGHI Marcus mcmer-open...@tor.at That sounds good. I was aware of the change, but didn't think anybody would notice. :) A bit late to the game, but I don't really

Re: hotplug(4) r1.10 ignoring hotplug_put_event() prior to hotplugopen() [Was: hotplugd(8) ignoring devices attached before boot]

2010-12-13 Thread Jonathan Armani
On Mon, 13 Dec 2010 14:28:42 +0100, MERIGHI Marcus mcmer-open...@tor.at wrote: mark.kette...@xs4all.nl (Mark Kettenis), 2010.12.13 (Mon) 13:41 (CET): Date: Mon, 13 Dec 2010 12:48:55 +0100 From: MERIGHI Marcus mcmer-open...@tor.at That sounds good. I was aware of the change, but didn't

pf: ugly error message when probability value out of range.

2010-12-13 Thread Thomas Pfaff
When specifying a probability attribute on a rule and the value is out of range, pfctl reports the problem using the internal probability value, an unsigned greater than UINT_MAX, rather than what you actually specified. The accepted range is either a number between 0 and 1 or between 0 and 100

Re: hotplug(4) r1.10 ignoring hotplug_put_event() prior to hotplugopen() [Was: hotplugd(8) ignoring devices attached before boot]

2010-12-13 Thread Ted Unangst
On Mon, Dec 13, 2010 at 7:41 AM, Mark Kettenis mark.kette...@xs4all.nl wrote: A bit late to the game, but I don't really agree with Tedu that the changed behaviour is an improvement. Say I have configured hotplugd(8) such that it automatically mounts things when I plug in my camera. Now I

MCLGETI for dc(4)

2010-12-13 Thread Loganaden Velvindron
First of all, big thanks to Christian `naddy` who sent me a dc(4). I also managed to get my hands on a PNIC. This diff add mclgeti support plus 2 bug fixes that suppress idle timeouts, and autonegocation which is broken on the PNIC. As usual, you know who to complain to. Index:

Re: MCLGETI for dc(4)

2010-12-13 Thread Mark Kettenis
Whoa there. Please stop for a moment. We have converted a small number to MCLGETI, and in almost all cases we've run into bugs. Subtle driver bugs, hardware bugs that need workarounds, etc. etc. If a driver is used a lot or if the number of chip variants is very limited, we eventaully find

Re: hotplug(4) r1.10 ignoring hotplug_put_event() prior to hotplugopen() [Was: hotplugd(8) ignoring devices attached before boot]

2010-12-13 Thread Todd T. Fries
definately prefer the prior behavior. Thanks, Penned by Mark Kettenis on 20101213 6:41.17, we have: | Date: Mon, 13 Dec 2010 12:48:55 +0100 | From: MERIGHI Marcus mcmer-open...@tor.at | | That sounds good. I was aware of the change, but didn't think anybody | would notice. :) | | A bit

Re: hotplug(4) r1.10 ignoring hotplug_put_event() prior to hotplugopen() [Was: hotplugd(8) ignoring devices attached before boot]

2010-12-13 Thread Ted Unangst
On Mon, Dec 13, 2010 at 2:48 PM, Todd T. Fries t...@fries.net wrote: I echo Mark's sentiments, though for a different reason. Softraid crypto volumes take time to fsck, yet are useful to use. In my case I can wait 20+min for my personal laptop to be useful, or I can wait 5min and let the

Re: hotplug(4) r1.10 ignoring hotplug_put_event() prior to hotplugopen() [Was: hotplugd(8) ignoring devices attached before boot]

2010-12-13 Thread Chris Kuethe
On Mon, Dec 13, 2010 at 11:48 AM, Todd T. Fries t...@fries.net wrote: I echo Mark's sentiments, though for a different reason. And hot-pluggable serial devices, like GPS receivers. Some of them do have usb serial numbers I can key on.

Re: hotplug(4) r1.10 ignoring hotplug_put_event() prior to hotplugopen() [Was: hotplugd(8) ignoring devices attached before boot]

2010-12-13 Thread Mark Kettenis
Date: Mon, 13 Dec 2010 13:17:26 -0500 From: Ted Unangst ted.unan...@gmail.com On Mon, Dec 13, 2010 at 7:41 AM, Mark Kettenis mark.kette...@xs4all.nl wrote: A bit late to the game, but I don't really agree with Tedu that the changed behaviour is an improvement. Say I have configured

Re: hotplug(4) r1.10 ignoring hotplug_put_event() prior to hotplugopen() [Was: hotplugd(8) ignoring devices attached before boot]

2010-12-13 Thread Ted Unangst
OK, if you can wait a few more hours, I will make a diff to go back the way things came.

Re: hotplug(4) r1.10 ignoring hotplug_put_event() prior to hotplugopen() [Was: hotplugd(8) ignoring devices attached before boot]

2010-12-13 Thread Ted Unangst
On Mon, Dec 13, 2010 at 3:27 PM, Mark Kettenis mark.kette...@xs4all.nl wrote: I think the solution to that is to make adding the duid to fstab work. At boot, if the duid exists, it's mounted. If it doesn't, it doesn't mount but also doesn't error out. This may already work even, I haven't

Re: MCLGETI for dc(4)

2010-12-13 Thread Stuart Henderson
On 2010/12/13 13:51, Loganaden Velvindron wrote: First of all, big thanks to Christian `naddy` who sent me a dc(4). I also managed to get my hands on a PNIC. This diff add mclgeti support plus 2 bug fixes that suppress idle timeouts, and autonegocation which is broken on the PNIC. As usual,

Re: hotplug(4) r1.10 ignoring hotplug_put_event() prior to hotplugopen() [Was: hotplugd(8) ignoring devices attached before boot]

2010-12-13 Thread Todd T. Fries
, but it still is pleanty enough space for this. Penned by Mark Kettenis on 20101213 14:27.51, we have: | Date: Mon, 13 Dec 2010 13:17:26 -0500 | From: Ted Unangst ted.unan...@gmail.com | | On Mon, Dec 13, 2010 at 7:41 AM, Mark Kettenis mark.kette...@xs4all.nl wrote: | A bit late to the game

Re: hotplug(4) r1.10 ignoring hotplug_put_event() prior to hotplugopen() [Was: hotplugd(8) ignoring devices attached before boot]

2010-12-13 Thread Paul de Weerd
On Mon, Dec 13, 2010 at 03:04:13PM -0500, Ted Unangst wrote: | I can agree there's a problem here, but the fact that you're using | hotplug to mount disks that aren't hotplugged indicates the problem is | elsewhere. :) I don't think hotplug was supposed to be the do random | stuff a little bit

Re: usb_{bulk,interrupt}_transfer() and PCATCH

2010-12-13 Thread Jacob Meuser
any further thoughts on this? On Sun, Dec 12, 2010 at 01:02:41PM +, Jacob Meuser wrote: On Sat, Dec 11, 2010 at 08:56:38PM +, Jacob Meuser wrote: On Sat, Dec 11, 2010 at 08:35:00PM +, Jacob Meuser wrote: On Sat, Dec 11, 2010 at 08:14:24PM +0100, Mark Kettenis wrote: Date:

revert hotplug malloc change

2010-12-13 Thread Ted Unangst
keeping a little bit of the change, i'm leaving the element expansion in there. that's what i was really after the first time anyway. Index: hotplug.c === RCS file: /home/tedu/cvs/src/sys/dev/hotplug.c,v retrieving revision 1.10

bugfixes for dc(4)

2010-12-13 Thread Loganaden Velvindron
Hi, I separated the mclgeti part from the bugfixes for PNIC. Give it a try. Thanks Index: src/sys/dev/ic/dc.c === RCS file: /cvs/src/sys/dev/ic/dc.c,v retrieving revision 1.121 diff -u -p -r1.121 dc.c --- src/sys/dev/ic/dc.c 7 Sep