Hello everybody,
yes Sam, you are right, but this bios is a little bit different, there is only
a setting regarding SATA: SATA0 legacy. with this option enabled, the kernel
detects the hard drive, but is not able to initialize it in order to be
partitioned . So i disabled this option and it is
Hi,
On Mon, 26.01.2009 at 15:39:36 +0100, Raimo Niskanen
raimo+open...@erix.ericsson.se wrote:
How can I know if I have a suspicious drive?
you won't, imho, until Seagate will deliver usable data on this issue.
Their statements so far were a long way from being trust-inspiring,
imho.
My best
Hi,
On Mon, 26.01.2009 at 17:08:51 +, Dieter open...@sopwith.solgatos.com
wrote:
It is easy to set up a slashdot account. Or you can post as anonymous
coward.
yes, but I don't want to set up a /. account right now, and posting as
AC wouldn't likely solve the problem.
that he has
Hi,
On Mon, 26.01.2009 at 17:08:51 +, Dieter open...@sopwith.solgatos.com
wrote:
Your suggestion of smartmontools is helpful, thank you.
thanks - I have just sent an email to them, esp. after seeing that
there are people from big name companies involved, who could procure
at least some of
Hi all,
First post here, so please be gentle.;-)
Let's get the
environmentals out of the way first :
-- OpenBSD 4.4 on i386 architecture
--
All errata up to and including 008 (14 Jan 2009) installed
Here's what I'm
seeing (IP addresses obfuscated to protect the innocent) :
(1) ATTEMPT 1
On 1/26/2009 1:43 PM, Nenhum_de_Nos wrote:
I have a couple of 750GB ES.2 and now I'm worried !
Why be worried, other than the nuisance of failed hardware? You've got
backups, right?
Besides, if you have a terabyte of data, chances are you have three
undetected single-bit or larger errors
BOG BOG wrote:
Hello everybody,
yes Sam, you are right, but this bios is a little bit different, there is
only a \
setting regarding SATA: SATA0 legacy. with this option enabled, the kernel
detects \
the hard drive, but is not able to initialize it in order to be partitioned .
So i \
anyone know why this situation would come up in sasyncd and/or help me
pinpoint the root cause? seems to correspond with a hiccup in traffic
flowing through the vpn. it corrects itself after a few minutes but it has
occurred on multiple occasions about the same time of day. Non-VPN traffic
still
Hello ,
cat /etc/pf.conf | grep test
table test const persist {10.0.0/24}
pfctl -T show -t test
10.0.0.0/24
a b wrote:
Hi all,
First post here, so please be gentle.;-)
Let's get the
environmentals out of the way first :
-- OpenBSD 4.4 on i386 architecture
--
All errata up to and
Hello ,
cat /etc/pf.conf | grep test
table test const persist {10.0.0/24}
pfctl -T show -t test
10.0.0.0/24
a b wrote:
Hi all,
First post here, so please be gentle.;-)
Let's get the
environmentals out of the way first :
-- OpenBSD 4.4 on i386 architecture
--
All errata up to and
I've been playing with aucat's new sound server capabilities, and it's
impressed me enough that I'd like to have it running as a system-wide
sound daemon. What is proper way to have it launch at boot? An entry in
rc.conf.local like 'aucat_flags=-l'?
Thanks,
--
Joe Gidi
j...@entropicblur.com
On Tue, Jan 27, 2009 at 02:27:59PM -0500, Joe Gidi wrote:
I've been playing with aucat's new sound server capabilities, and it's
impressed me enough that I'd like to have it running as a system-wide
sound daemon. What is proper way to have it launch at boot? An entry in
rc.conf.local like
http://www.theregister.co.uk/2009/01/27/blowfish_poisoning/
--
http://www.glumbert.com/media/shift
http://www.youtube.com/watch?v=tGvHNNOLnCk
This officer's men seem to follow him merely out of idle curiosity.
-- Sandhurst officer cadet evaluation.
Securing an environment of Windows platforms
bofh wrote:
http://www.theregister.co.uk/2009/01/27/blowfish_poisoning/
hack on the linux kernel?
;)
Dieter openbsd at sopwith.solgatos.com writes:
Recovering from Seagate's problematic 7200.11 firmware.
Most of you have read about the problems with Seagate's
7200.11 disks. For those of you that haven't, the firmware
on many of these drives is buggy, and can brick the drive
when
Nenhum_de_Nos matheus at eternamente.info writes:
where you read that from ?
I have a couple of 750GB ES.2 and now I'm worried !
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207931NewLang=en
thanks, yet OT, but I also heard of new firmwares being worse than old
hi gang,
i am at a bit of loss here. i have finally a notebook
where both the wireless (iwn0) and normal nic (lii0) get
recognized. both are dhcp clients of my home router.
consider the following scenario:
1. boot up, lii0 gets a lease
2. i disconnect the wire
3. route -n flush; dhclient iwn0
On Tue, Jan 27, 2009 at 02:27:59PM -0500, Joe Gidi wrote:
I've been playing with aucat's new sound server capabilities, and it's
impressed me enough that I'd like to have it running as a system-wide
sound daemon. What is proper way to have it launch at boot? An entry in
rc.conf.local like
frantisek holop wrote:
hi gang,
i am at a bit of loss here. i have finally a notebook
where both the wireless (iwn0) and normal nic (lii0) get
recognized. both are dhcp clients of my home router.
consider the following scenario:
1. boot up, lii0 gets a lease
2. i disconnect the wire
On Sun, Jan 25, 2009 at 09:56:50PM +, Stuart Henderson wrote:
On 2009-01-24, Mark Zimmerman markz...@frii.com wrote:
Greetings:
I am trying to get ipv6 neighbor discovery working over a wpa wireless
link between two ral interfaces. I get nothing, and no error messages
from rtadvd on
Toni writes:
If we can find out what area
this is (I assume it isn't in the normal space used for user storage)
and how to zero it (if not already zero) there is no need to update
the firmware.
I'd rather say that the (ring) buffer has some external counter, also
stored somewhere,
Hi all. I have some strange problem, i'll try to describe it.
There is HP notebook with obsd and Linux inside.
When i work in obsd screen goes to black, but notebook still work and i can
type ^C reboot if i was in terminal. One time i work two hours, another -
just 15 minutes before this
bofh wrote:
http://www.theregister.co.uk/2009/01/27/blowfish_poisoning/
Actually, they knew what the deal was since only an unlicensed
chef/restaurant would serve organ meat. Even nicking the organs can be
trouble, especially since there is seasonal and individual variation in
the strength.
A
23 matches
Mail list logo
