Hi Philip,
On Sun, Nov 22, 2009 at 09:11:14PM -0800, Philip Guenther wrote:
> On Sat, Nov 21, 2009 at 9:21 PM, patrick keshishian
> wrote:
> > On Sat, Nov 21, 2009 at 09:15:17PM -0800, patrick keshishian wrote:
> >> I wonder if included patch is a correct fix for the following
> >> "glitch" I'm s
On Mon, Nov 23, 2009 at 12:11 AM, Philip Guenther wrote:
> On Sat, Nov 21, 2009 at 9:21 PM, patrick keshishian
> wrote:
>> On Sat, Nov 21, 2009 at 09:15:17PM -0800, patrick keshishian wrote:
>>> I wonder if included patch is a correct fix for the following
>>> "glitch" I'm seeing with ksh in `set
On Sun, Nov 22, 2009 at 08:51:55PM -0500, Brad Tilley wrote:
> On Sun, Nov 22, 2009 at 7:21 PM, Stuart Henderson
> wrote:
>
> > This should be supported as of 2009/11/17, try a snapshot.
> > Yes, the usbdevs output you included was useful - but in future
> > please send a complete dmesg rather t
On Sat, Nov 21, 2009 at 9:21 PM, patrick keshishian
wrote:
> On Sat, Nov 21, 2009 at 09:15:17PM -0800, patrick keshishian wrote:
>> I wonder if included patch is a correct fix for the following
>> "glitch" I'm seeing with ksh in `set -o vi' mode:
>>
>> Demonstration of "glitch":
>> $ touch a
The interrupt handling in ral(4) for RT2661 has a couple of problems,
which causes the interface to get stuck under heavy load with OACTIVE
set (the problems are likely especially severe on slow systems such as
my 600MHz VIA system); bouncing the interface down and back up fixes
things. As I descr
By the way, I forgot to mention that even with this patch applied, I
do have one odd problem with ral on my system -- after some time
(hours it appears), the ral interface stops being able to send
multicasts/broadcasts. All other traffic works fine, including
receiving multicasts, but no multicast
On Sun, Nov 22, 2009 at 7:21 PM, Stuart Henderson wrote:
> This should be supported as of 2009/11/17, try a snapshot.
> Yes, the usbdevs output you included was useful - but in future
> please send a complete dmesg rather than an exert.
Thanks. I did a bsd.rd install from the latest i386 snapsho
On 2009/11/22 18:35, Brad Tilley wrote:
> Anyone working on the Asus USB-N13 802.11 adapter? I have one and
> would be glad to test. It's listed as a ugen device right now (on an
> almost current box). I thought the run0 driver might support it. I
> think it has the Ralink 3070 chipset:
>
> dmesg:
Anyone working on the Asus USB-N13 802.11 adapter? I have one and
would be glad to test. It's listed as a ugen device right now (on an
almost current box). I thought the run0 driver might support it. I
think it has the Ralink 3070 chipset:
dmesg:
ugen0 at uhub0 port 1 "Ralink 802.11 n WLAN" rev 2.
On 2009/11/22 12:43, Lars Nooden wrote:
> Excellent! At the risk of disturbing things, would there be a way to
> harmonize the arguments for ssh and sftp clients, in this case for
> designating the remote user?
u...@host works everywhere.
Damien Miller wrote:
> On Tue, 17 Nov 2009, lars wrote:
>
>> Adding the -l argument to assign user name on sftp is done on ssh and makes
>> the two more similar to use. The diff below is an illustraion of what might
>> be done.
>
> No, -l is reserved for bandwidth limiting like scp's -l option.
11 matches
Mail list logo
