Thanks, folks, for the interesting contributions. I really should
have marked the subject OT but there spring up a lot
of interesting ideas.
On Fri, Jan 13, 2006 at 08:13:00AM +1100, Peter Jeremy wrote:
On Thu, 2006-Jan-12 10:48:38 +0100, Christoph Kukulies wrote:
dd if=/dev/ad2 of=/dev/ad3
Priority need not be propagated to readers as they will not block other
readers.
Most likely, you only need to propagate to the writer to avoid priority
inversron.
regards
-kamal
On 1/13/06, prime [EMAIL PROTECTED] wrote:
Hi hackers,
I have a question about how priority propagation works
On 1/13/06, Kamal R. Prasad [EMAIL PROTECTED] wrote:
Priority need not be propagated to readers as they will not block other
readers.
Most likely, you only need to propagate to the writer to avoid priority
inversron.
regards
-kamal
On 1/13/06, prime [EMAIL PROTECTED] wrote:
Hi
On Fri, 13 Jan 2006, Peter Jeremy wrote:
PJ The process is running now since yesterday evening and it is at 53 MB
PJ at a transfer rate of about 1.1 MB/s.
PJ
PJ In case the the result being unusable I would like to find a way to make
this
PJ copying faster.
PJ
PJ Note that whilst increasing
On Thu, Jan 12, 2006 at 02:23:37PM -0700, Kenneth D. Merry wrote:
written by phk) that is designed to do disk-to-disk recovery - it
copys data in big slabs until it gets an error and then works around
the faulty area block by block.
It's called 'recoverdisk', and is in
Am 13.01.2006 um 14:29 schrieb Christoph P. Kukulies:
Just for the record: Before I wanted to give back in my faulty disk
to my computer supplier as a case for warranty, I zeroed out the
faulty
disk.
dd if=/dev/zero of=/dev/ad2 bs=1m
It took half an hour to zero out the 80GB. Transferrate
Hello.
I wrote two isa device drivers A and B for FreeBSD4.11.
Both are kld-loaded and have identify() entries.
Here is the pseudo code for the identify() routines:
A_identify() /* 2 units */
{
for (i = 0; i =1; ++ i)
{
dev = BUS_ADD_CHILD(parent, ISA-ORDER_SPECULATIVE, a, 0);
If
On Friday 13 January 2006 08:29 am, Christoph P. Kukulies wrote:
On Thu, Jan 12, 2006 at 02:23:37PM -0700, Kenneth D. Merry wrote:
written by phk) that is designed to do disk-to-disk recovery - it
copys data in big slabs until it gets an error and then works around
the faulty area block
On Fri, 13 Jan 2006, Norbert Koch wrote:
4. A_probe(unit 1)
-- fails with ENXIO because hardware is not present
Your IDENTIFY method allows device enumeration. You should not create
devices in IDENTIFY that do not exist.
Consider use /boot/device.hints add ISA devices. An IDENTIFY method
All,
no big news since 6.0, but in the background there are many interesting
projects: Just now the new malloc has hit current, we hear promising numbers
from the network performance crew, the first batch of security advisories is
out and I'm sure some of you spent the holidays doing exiting
On Friday 13 January 2006 05:20 am, prime wrote:
On 1/13/06, Kamal R. Prasad [EMAIL PROTECTED] wrote:
Priority need not be propagated to readers as they will not block other
readers.
Most likely, you only need to propagate to the writer to avoid priority
inversron.
regards
-kamal
I wrote two isa device drivers A and B for FreeBSD4.11.
Both are kld-loaded and have identify() entries.
Here is the pseudo code for the identify() routines:
A_identify() /* 2 units */
{
for (i = 0; i =1; ++ i)
{
dev = BUS_ADD_CHILD(parent, ISA-ORDER_SPECULATIVE, a, 0);
If
My machine been hacked. The message file was modified. Old dated backup files
are deleted. The last log was truncated. You are gurus. Would you please tell
me where I can find out other trace file or logfiles to figure out where the
hacker come from?
Thanks a lot.
--
View this message in
anchor (sent by Nabble.com) wrote:
My machine been hacked. The message file was modified. Old dated backup files
are deleted. The last log was truncated. You are gurus. Would you please tell
me where I can find out other trace file or logfiles to figure out where the
hacker come from?
14 matches
Mail list logo
