I use a pseudonym and anon-ish e-mail for the exact same reasons you use your real name. Go figure.
I particularly don't want my on-line persona to easily match my IRL name.
That said I also keep three pseudos with this one being most likely to link to me as a person, and the one I would hand an employer if they really had a need to know about anything. -nB
not at all. While NAT is not a be-all end-all security measure, it certainly helps, as my router provides a (stupid-basic) blank face at port-scan attempts. Layers of defense. My router is the drawbridge of my castle. -nB
Like so many others, I have a project I want to do. The project involves doing X, but alas I can not do X myself. Have any other/.ers done this and have some sample code I can look at and learn how to do this myself?
I too agree, but my home system is just that, a simple mirror on a single controller. It is more fault resistant, as I am unfettered by a single disk failure, and frankly that is good enough. Should the drives be corrupted then I would lose approx 1 week of data from the mirror as that is the backup cycle I'm on.
"Anyone who says they've never lost data simply hasn't looked for the data they've already lost yet." -me -nB
there ya go. That was the country I was looking for. That assembly line was responsible for at least 99% of our failed drives not directly attributable to another cause (devs dropping drives doesn't count against the drive vendor IMHO).
How many were made in Hungary? I'm betting very few to none. We had a huge lot of 20 gig drives die on us, all from Singapore (or something?) but none of the Hungarian ones died. To me this means it was not a design issue, but rather a quality in production issue. -nB
CPUs (uCode patches) Chipsets (FWUpdates, ROM code patches) GPU (We all agree here I think)
I was just commenting that the GGGP post was accurate in that releasing driver source gives insight into your hardware. Obviously in some cases more than others.
In addition is should be noted that almost by definition, the smart ones aren't caught. Thus making the assumption that most criminals are !smart, it would follow that they do not alter the exif field to create false MD5 sigs.
On a flip side, would it be possible to get the known "bad" MD5's then using a rainbow table, create innocuous files that equate to the "bad" hash, similar to the self recursive web page that pretends to host madonna.mp3 to trap RIAA spiders? -nB
You know you are one of the more "noticeable" nicks on/. and normally I love your comments. but today made me wonder if you might have a touch of aspergers? And yet I still love the commentary.
True, it does protect from disk failure. The false sense I was referring to was the inherent "I'll do that later, the RAID will cover me for a few days" bit that none of want to admit, but we are all susceptible to.
As to the previous poster: Yes it's crappy when your volume goes off-line or read-only. Unfortunately such is the case when you have no budget and are on under performing hardware, but that's all you can afford.
Note that my application is *not* enterprise, or even departmental (though it should be treated as such). It is managing a non-trivial collection of data-sets for a masters thesis in social sciences. (not mine, I'm just the data mule).
you know the other solution is to not use RAID5 with these big drives, or to go to RAID1, or to actually back up the data you want to save to DVD and accept a disk failure will cost you the rest.
Now, while 1TB onto DVDs seems like quite a chore (and I'll admit it's not trivial), some level of data staging can help out immensely, as well as incrementally backing up files, not trying to actually get a full drive snapshot.
Say you backup like this: my pictures as of 21oct2008 my documents (except pictures and videos) as of 22 oct2008 etc. while you will still lose data in a disk failure, your loss can be mitigated, especially if you only try to backup what is important. With digital cameras I would argue that home movies and pictures are the two biggest data consumers that people couldn't backup to a single dvd and that they would be genuinely distressed to lose. -nB
True. Also FWIW I only run RAID 1 and JBOD. For things that must be on-line, or are destined for JBOD but not yet archived to backup media, they are located on one of the RAID volumes. For everything else it's off to JBOD, where things are better than RAID5
Why?
I have 6 TB of JBOD storage and 600(2x300 volumes) GB of RAID 1. If I striped the JBOD into 6TB (7 drives) and one drive failed all the near-line data would be virtually off-line (and certainly read-only) while the array re-built. With JBOD, should a disk fail, I pop in a replacement, grab the stack of DVDs from the local backup, and plug the data back in. Now all the other near-line is still available and honestly takes about the same amount of effort and time as re-building a stripe set w/ parity. Never mind that I've had a read error on rebuilds before and had to re-do the entire array from scratch anyway.
While my system would not work in an environment where the files on the JBOD change often, they are basically.archive anyway, so handling them by way of staging on RAID1 pending copy to DVD and storing on JBOD works fine.
Naturally this system also really gives an incentive to keep up on the backups, with no false sense of security of having files on a RAID5... -nB
Slashdot Mirror
I use a pseudonym and anon-ish e-mail for the exact same reasons you use your real name. Go figure.
I particularly don't want my on-line persona to easily match my IRL name.
That said I also keep three pseudos with this one being most likely to link to me as a person, and the one I would hand an employer if they really had a need to know about anything.
-nB
I'm going to go with crook.
My evidence is this windows 1.0 sales video:
http://www.youtube.com/watch?v=tGvHNNOLnCk
-nB
not at all.
While NAT is not a be-all end-all security measure, it certainly helps, as my router provides a (stupid-basic) blank face at port-scan attempts.
Layers of defense. My router is the drawbridge of my castle.
-nB
?!?
What advertisements? Seriously, haven't seen one.
Sometimes I forget what I'm not missing with FF ABP and NS installed.
-nB
Fortunately my Gmail spam filter hides these e-mails for me.
-ML
Dear /.
Like so many others, I have a project I want to do. The project involves doing X, but alas I can not do X myself. Have any other /.ers done this and have some sample code I can look at and learn how to do this myself?
regards,
someGuyWhoWantsToBeABetterGeek
I too agree, but my home system is just that, a simple mirror on a single controller. It is more fault resistant, as I am unfettered by a single disk failure, and frankly that is good enough. Should the drives be corrupted then I would lose approx 1 week of data from the mirror as that is the backup cycle I'm on.
"Anyone who says they've never lost data simply hasn't looked for the data they've already lost yet." -me
-nB
there ya go.
That was the country I was looking for.
That assembly line was responsible for at least 99% of our failed drives not directly attributable to another cause (devs dropping drives doesn't count against the drive vendor IMHO).
How many were made in Hungary? I'm betting very few to none. We had a huge lot of 20 gig drives die on us, all from Singapore (or something?) but none of the Hungarian ones died. To me this means it was not a design issue, but rather a quality in production issue.
-nB
I had an account, but forgot the UID/password and the e-mail address it was attached to is now someone else's domain...
I'm sorry, your meme has been rejected as inappropriate to your user name.
Please restate Soviet Russia meme in the form of you.
I fail it
Touché
OT, I know, but...
Isn't it about time to replace Borg Bill with Balmer pitching a chair or something?
CPUs (uCode patches)
Chipsets (FWUpdates, ROM code patches)
GPU (We all agree here I think)
I was just commenting that the GGGP post was accurate in that releasing driver source gives insight into your hardware. Obviously in some cases more than others.
I'm fairly sure this search isn't very useful.
-nB
or contractions?
I'll vouch he's right, based on my experience in the semiconductor industry.
Still I think Creative made the right choice.
-nB
While it may be reduced, there still would be convection as the boundaries of the water lose heat to the container.
-nB
+1 lovely (though, the GP does largely make valid points)
In addition is should be noted that almost by definition, the smart ones aren't caught. Thus making the assumption that most criminals are !smart, it would follow that they do not alter the exif field to create false MD5 sigs.
On a flip side, would it be possible to get the known "bad" MD5's then using a rainbow table, create innocuous files that equate to the "bad" hash, similar to the self recursive web page that pretends to host madonna.mp3 to trap RIAA spiders?
-nB
touche...
You know you are one of the more "noticeable" nicks on /. and normally I love your comments.
but today made me wonder if you might have a touch of aspergers?
And yet I still love the commentary.
True, it does protect from disk failure. The false sense I was referring to was the inherent "I'll do that later, the RAID will cover me for a few days" bit that none of want to admit, but we are all susceptible to.
As to the previous poster: Yes it's crappy when your volume goes off-line or read-only. Unfortunately such is the case when you have no budget and are on under performing hardware, but that's all you can afford.
Note that my application is *not* enterprise, or even departmental (though it should be treated as such). It is managing a non-trivial collection of data-sets for a masters thesis in social sciences. (not mine, I'm just the data mule).
you know the other solution is to not use RAID5 with these big drives, or to go to RAID1, or to actually back up the data you want to save to DVD and accept a disk failure will cost you the rest.
Now, while 1TB onto DVDs seems like quite a chore (and I'll admit it's not trivial), some level of data staging can help out immensely, as well as incrementally backing up files, not trying to actually get a full drive snapshot.
Say you backup like this:
my pictures as of 21oct2008
my documents (except pictures and videos) as of 22 oct2008
etc.
while you will still lose data in a disk failure, your loss can be mitigated, especially if you only try to backup what is important. With digital cameras I would argue that home movies and pictures are the two biggest data consumers that people couldn't backup to a single dvd and that they would be genuinely distressed to lose.
-nB
True.
Also FWIW I only run RAID 1 and JBOD.
For things that must be on-line, or are destined for JBOD but not yet archived to backup media, they are located on one of the RAID volumes. For everything else it's off to JBOD, where things are better than RAID5
Why?
I have 6 TB of JBOD storage and 600(2x300 volumes) GB of RAID 1. If I striped the JBOD into 6TB (7 drives) and one drive failed all the near-line data would be virtually off-line (and certainly read-only) while the array re-built. With JBOD, should a disk fail, I pop in a replacement, grab the stack of DVDs from the local backup, and plug the data back in. Now all the other near-line is still available and honestly takes about the same amount of effort and time as re-building a stripe set w/ parity. Never mind that I've had a read error on rebuilds before and had to re-do the entire array from scratch anyway.
While my system would not work in an environment where the files on the JBOD change often, they are basically .archive anyway, so handling them by way of staging on RAID1 pending copy to DVD and storing on JBOD works fine.
Naturally this system also really gives an incentive to keep up on the backups, with no false sense of security of having files on a RAID5...
-nB