Please send the dump my way.
On Sep 3, 2012, at 8:14 PM, Claudio Jeker wrote:
> I never got any negative test results back about this change. I assume
> that either nobody is interested or that it just works.
I've been using this in semi-production with announce restart yes without
issues.
> Date: Wed, 5 Sep 2012 04:01:56 +0400
> From: Alexander Polakov
>
> * Alexander Polakov [120903 21:41]:
> > Now back to "underlying issues": x86emu executes some code which causes
> > parity check NMI (bit 7 set in port 0x61) to be generated, which causes
> > drop to the debugger (I mistook it
On Mon, Sep 10, 2012 at 12:26:09PM +0200, Mark Kettenis wrote:
> > Date: Wed, 5 Sep 2012 04:01:56 +0400
> > From: Alexander Polakov
> >
> > * Alexander Polakov [120903 21:41]:
> > > Now back to "underlying issues": x86emu executes some code which causes
> > > parity check NMI (bit 7 set in port
> Date: Mon, 10 Sep 2012 13:34:56 +0300
> From: Paul Irofti
>
> On Mon, Sep 10, 2012 at 12:26:09PM +0200, Mark Kettenis wrote:
> > > Date: Wed, 5 Sep 2012 04:01:56 +0400
> > > From: Alexander Polakov
> > >
> > > * Alexander Polakov [120903 21:41]:
> > > > Now back to "underlying issues": x86em
Hi,
first of all: Thanks for your reply!
On Sat, Sep 08, 2012 at 04:04:41PM +0200, Mark Kettenis wrote:
> > most modern x86 hardware includes more than one PCI root segement.
> > E.g. a hardware that I have here has three PCI root segemnts with bus
> > numbers 0, 0x7f, 0x80 and 0xff respectively.
i dont have this hardware, so i can only test that it hasnt broken
this chip:
bge0 at pci3 dev 4 function 0 "Broadcom BCM5714" rev 0xa3, BCM5715 A3 (0x9003):
ivec 0x795, address 00:14:4f:a9:34:90
brgphy0 at bge0 phy 1: BCM5714 10/100/1000baseT/SX PHY, rev. 0
i need tests from any bge users willi
On 2012/09/10 22:57, David Gwynne wrote:
> i dont have this hardware, so i can only test that it hasnt broken
> this chip:
>
> bge0 at pci3 dev 4 function 0 "Broadcom BCM5714" rev 0xa3, BCM5715 A3
> (0x9003): ivec 0x795, address 00:14:4f:a9:34:90
> brgphy0 at bge0 phy 1: BCM5714 10/100/1000baseT/
Hi.
This diff adds 2 new options to usermod(8):
-U to unlock a user's password
-Z to lock a user's password
In effect locking/unlocking the password means to add a '!' in front of
the encrypted entry in master.passwd.
Note that this disable the _password_ not the account of course (you
could stil
Hi list@,
is there any plans to expand 'tagged' keyword in PF into list?
Example of usage:
match in ... tag ABC
match in ... tag BCD
pass in on egress tagged { ABC, BCD }
If yes, is anyone already working on that? Any diff for testing?
Yes, I started to look at this, but it will take time for
On Aug 18 10:40:23, Mark Kettenis wrote:
> Finally got annoyed enough that my MacBook running OS X (don't ask)
> didn't work too well on my OpenBSD AP at home. The reason is the
> following caveat listed in the athn(4) man page:
>
> Host AP mode doesn't support power saving. Clients attempt
On Sun, Sep 9, 2012 at 8:32 PM, Aaron Bieber wrote:
> On Sat, Sep 08, 2012 at 04:47:45PM +0200, Raphael Graf wrote:
>> This adds support for the FT2232H and FT4232H serial adapters.
>> (FT2232H found on the BeagleBone).
>>
>> These devices have a 120MHz base clock for the baud rate generator
>> an
2012/9/10 Antoine Jacoutot
> Hi.
>
> This diff adds 2 new options to usermod(8):
> -U to unlock a user's password
> -Z to lock a user's password
>
> In effect locking/unlocking the password means to add a '!' in front of
> the encrypted entry in master.passwd.
> Note that this disable the _passwo
On 09/10/12 15:24, sven falempin wrote:
2012/9/10 Antoine Jacoutot
In effect locking/unlocking the password means to add a '!' in front of
the encrypted entry in master.passwd.
Note that this disable the _password_ not the account of course (you
could still connect using ssh+key for e.g.).
Hi,
the following patch adds a new flag to iostat(8) to show the read and
write transfers per second, similiar to the iostat view of systat(1).
Though I had a hard time formulating the man page bits. This is how it
looks like:
$ iostat -x -w1 wd0
wd0
KB/t rt/s wt/s MB/s
It's working reasonably well here, but there's glitches with Android
devices. After a while they either say the AP is 'out of range' or 'saved'
with the non functional option to connect. That's with both an Androided
ICS HP Touchpad and a Sony Ericcson Xperia Pro with latest official ICS.
Sadly th
Cómo Elaborar Folletos, Catálogos, Revistas, Boletines, Prensa, Anuncios y
Mucho Más...
SEMINARIO ONLINE EN VIVO este 19 de Septiembre de 2012.
¡Aprenda las habilidades esenciales del diseño gráfico que harán que cada uno
de los proyectos que diseñe sean visualmente más efectivos y poderosos!
Ning
This is a diff that should fix a few issues I've encountered with sftp's
tab-complete, and a few others that I found in the process.
1) In makeargs: Lack of bounds checking for the argument pointer
table, causing a buffer overflow when entering too many arguments.
2)Improper handling of absolute
On 10 September 2012 18:01, Antoine Jacoutot wrote:
> Hi.
>
> This diff adds 2 new options to usermod(8):
> -U to unlock a user's password
> -Z to lock a user's password
>
> In effect locking/unlocking the password means to add a '!' in front of
> the encrypted entry in master.passwd.
> Note that
On Tue, Sep 11, 2012 at 09:33:56AM +0300, Eugene Yunak wrote:
> On 10 September 2012 18:01, Antoine Jacoutot wrote:
> > Hi.
> >
> > This diff adds 2 new options to usermod(8):
> > -U to unlock a user's password
> > -Z to lock a user's password
> >
> > In effect locking/unlocking the password means
20 matches
Mail list logo