On Sun, Jan 26, 2014 at 5:07 PM, Philip Guenther guent...@gmail.com wrote:
On Sun, Jan 26, 2014 at 11:40 AM, emigrant emig...@gmail.com wrote:
My Master machine is dead, exactly HDD(thank you God for CARP+pfsync) :).
root@master[/etc]wd0(pciide0:0:0): timeout
type: ata
On Mon, Jan 27, 2014 at 10:57:59AM +, Zé Loff wrote:
On Thu, Jan 23, 2014 at 10:47:05AM +, Zé Loff wrote:
Sorry if it's a dumb question, but I'm stuck...
I have two machines (yesterday's current, one i386, one amd64) and I can
properly setup a serial console on the i386 and
On 28/01/2014, at 4:19 AM, Simon Perreault wrote:
Le 2014-01-25 14:40, Richard Procter a écrit :
I'm not saying the calculation is bad. I'm saying it's being
calculated from the wrong copy of the data and by the wrong
device. And it's not just me saying it: I'm quoting the guys
who designed
On Tue, Jan 28, 2014 at 12:27 AM, Andres Perera andre...@zoho.com wrote:
On Sun, Jan 26, 2014 at 5:07 PM, Philip Guenther guent...@gmail.com wrote:
On Sun, Jan 26, 2014 at 11:40 AM, emigrant emig...@gmail.com wrote:
My Master machine is dead, exactly HDD(thank you God for CARP+pfsync) :).
On Tue, Jan 28, 2014 at 4:55 AM, Philip Guenther guent...@gmail.com wrote:
On Tue, Jan 28, 2014 at 12:27 AM, Andres Perera andre...@zoho.com wrote:
On Sun, Jan 26, 2014 at 5:07 PM, Philip Guenther guent...@gmail.com wrote:
On Sun, Jan 26, 2014 at 11:40 AM, emigrant emig...@gmail.com wrote:
My
On Tue, Jan 28, 2014 at 2:03 AM, Andres Perera andre...@zoho.com wrote:
On Tue, Jan 28, 2014 at 4:55 AM, Philip Guenther guent...@gmail.com wrote:
...
I'm no expert on softdeps, so maybe you have a better explanation for
why Kirk made the choice he did to have it panic in some cases?
well,
On Tue, Jan 28, 2014 at 03:27:55AM -0500, Hugo Villeneuve wrote:
On Mon, Jan 27, 2014 at 10:57:59AM +, Zé Loff wrote:
On Thu, Jan 23, 2014 at 10:47:05AM +, Zé Loff wrote:
Sorry if it's a dumb question, but I'm stuck...
I have two machines (yesterday's current, one i386, one
On Wed, Jan 15, 2014 at 9:41 AM, Martin Pieuchot mpieuc...@nolizard.org wrote:
On 15/01/14(Wed) 15:27, Stefan Sperling wrote:
It seems the bwi driver lacks support for PIO mode which the
linux b43 driver falls back to in case of DMA errors such as
this one.
Two related linux commits:
On Tue, Jan 28, 2014 at 6:12 AM, Philip Guenther guent...@gmail.com wrote:
On Tue, Jan 28, 2014 at 2:03 AM, Andres Perera andre...@zoho.com wrote:
On Tue, Jan 28, 2014 at 4:55 AM, Philip Guenther guent...@gmail.com wrote:
...
I'm no expert on softdeps, so maybe you have a better explanation
Le 2014-01-27 21:21, Geoff Steckel a écrit :
It would be good if when data protected by a checksum is modified,
the current checksum is validated and some appropriate? action is done
(drop? produce invalid new checksum?) when proceeding.
This is exactly what's being done. Don't you listen
Le 2014-01-28 03:39, Richard Procter a écrit :
In order to hide payload corruption the update code would
have to modify the checksum to exactly account for it. But
that would have to happen by accident, as it never considers
the payload. It's not impossible, but, on the other hand,
checksum
On Thu, Jan 23, 2014 at 01:39:33PM +0100, Jan Stary wrote:
Time for today's silly diff yet?
The following augments the worm(6) manpage to
answer the burning question what happens if
I make the worm too long initially?
Jan
i've just committed a fix from paul janzen that answers your
On Mon, Jan 27, 2014 at 01:57:48PM +0100, Jan Stary wrote:
The diff below moves the journal volume
reference into the .Rs block and adds pages.
Jan
as discussed with jan, the diff below got committed.
jmc
Index: yacc.1
On Tue, Jan 28, 2014 at 05:33, Andres Perera wrote:
do you understand that disks have write caches that don't give a hoot
about posix mkdir() rename() and so on?
can bit rot change a inode type from directory to file, and vice versa?
do you want the kernel to figure these out after the
On 2014-01-28, Simon Perreault sperrea...@openbsd.org wrote:
Le 2014-01-28 03:39, Richard Procter a écrit :
In order to hide payload corruption the update code would
have to modify the checksum to exactly account for it. But
that would have to happen by accident, as it never considers
the
Em 28-01-2014 15:45, Stuart Henderson escreveu:
On 2014-01-28, Simon Perreault sperrea...@openbsd.org wrote:
Le 2014-01-28 03:39, Richard Procter a écrit :
In order to hide payload corruption the update code would
have to modify the checksum to exactly account for it. But
that would have to
Le 2014-01-28 12:45, Stuart Henderson a écrit :
This analysis is bullshit. You need to take into account the fact that
checksums are verified before regenerating them. That is, you need to
compare a) verifying + regenerating vs b) updating. If there's an
undetectable error, you're going to
Hello,
since updating to the latest snapshot on sparc64 from 22nd january ntpd
switches back and forth between synced and unsynced clock every few
minutes. Does anyone notice similar behavior?
my ntpd.conf:
servers de.pool.ntp.org
Regards,
Markus
On Tue, 28 Jan 2014 23:32:30 +0100,
Markus Lude markus.l...@gmx.de wrote:
Hello,
since updating to the latest snapshot on sparc64 from 22nd january
ntpd switches back and forth between synced and unsynced clock every
few minutes. Does anyone notice similar behavior?
I have the same on
On Tue, Jan 21, 2014 at 03:51:23PM -0800, Gabriel Kuri wrote:
I am running obsd 5.4 as my NAT router. I decided to setup a second obsd
box and run carp between the two for the external NATed interface (facing
the ISP). After I setup everything and switched pf to NAT using the address
on the
20 matches
Mail list logo
