|
Mark_Wallace wrote: I'm not anti-RAID, but I'm a firm believer that keeping duplicates of everything is a waste of time and space.
I keep everything personal and important in specific directories, that are backed up in a perhaps complicated, but easy to set up, pattern.
Storing multiple copies of an operating system and program files seems like a total waste, to me.
You don't have to have a RAID for your system volume. You can always create a volume that's specific for storage that's backed by a RAID.
That being said, there is a valid use case for backing up the system volume, you'd like to recover in the event of a failure sooner than later. Some people would like to get back to work rather than go through the pain of reinstalling everything, and updating patches, etc. again. To each their own, but it's a valid use case.
Anyway, RAID was designed to handle what you're doing. If you have 4 drives laying around, you could always have one for the system and 3 for the storage as a RAID 5. All your installed OSes will still have access to the volume just so long as it's a hardware RAID you're using.
Mark_Wallace wrote: Sorting out what to retain from a full system copy can take days.
Guess that all depends on how you organize your files bro.
Jeremy Falcon
|
|
|
|
|
Jeremy Falcon wrote: To each their own, but it's a valid use case Granted, but for me, installing a new system happens much more often than having to reinstall a previous system because of failure (i.e. the latter has never happened, in over thirty years of intensive computer usage), so storing a system via raid is a complete waste of everything.
That's what shadow copies and images are for, if you're really paranoid -- but just ensuring the safety of the comparatively few files that are actually of value to you is way more important (and leads to fewer compatibility problems).
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Well yeah sure, but restoring from a shadow copy of a backup isn't as *pure* as the exact state before the crash that you'd get with RAID. Anyway, to each their own. If system files ain't no important to you, then don't back them up. Just don't tell MS, they may cry. I mean, at least backup notepad. It's such a useful app.
Jeremy Falcon
|
|
|
|
|
I'm really glad we had this discussion, because it's reminded me to amend my registry-chunk-extractor script for my win tablet.
I'd have been severely cheesed off if the drive had failed, or something, and I'd been unable to restore my program settings.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Glad I could help, yay for CP.
Jeremy Falcon
|
|
|
|
|
Jeremy Falcon wrote: What do you have against using a RAID?
I'm not really after redundancy here, or looking at improving performance, so RAID doesn't offer me much in this context. I'm not going to make the mistake assuming that RAID == backup.
|
|
|
|
|
dandy72 wrote: I'm not going to make the mistake assuming that RAID == backup
But neither does keeping a spare drive around in case one crashes. Again, tomato vs tomahto. But this problem has already been solved.
Jeremy Falcon
|
|
|
|
|
|
There's some intrinsic beauty to you're plan.
I don't know what it is but I know it's there.
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
It's genius madness?!
|
|
|
|
|
We decided at work today that an ideal password is "case-insensitive".
If you l33t it a bit, it will meet any stupid requirements.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I vote for "Case-Sensitive". It's like "case-insensitive", but all the cool kids are using it.
Jeremy Falcon
|
|
|
|
|
I don't mix with the cool kids; they're just followers.
But you make a good point, so I'll go with "case-desensitised".
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I always thought of people making up password rules as insensitive in any case
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
|
|
|
|
|
|
This is one of the many reasons I wrote the article :
Destroy All Passwords: Never Memorize A Password Again[^]
Why not draw your password?
I agree with you about never remembering the password again and just requesting a new one each time.
The most secure password is known by no one.
|
|
|
|
|
|
This is lame. It's much more fun if they add rules like no more than three consecutive letters from your name (and fail to implement it correctly, because two consecutive letters already led to rejection of the password) and require you to change the password at least two times a month. People with names like Max Pax have little problems, but those with longer names and more common combinations practically could not come up with anything they could remember.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
Mister Mxyzptlk is hosed then
|
|
|
|
|
Super Lloyd wrote: On a site I am really interested in! (Xamarin forums) Curious - are you using XForms or for (like me) using C# to build for Android/iOS only?
/ravi
|
|
|
|
|
yes, I have been using Xamarin Form for a while now!
it's great!
|
|
|
|
|
Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a hieroglyph, and the blood of a virgin.
|
|
|
|
|
I like the haiku requirement!
|
|
|
|
|
Another Microsoft failure on creating a simple form!Lol I laughed a lot with your post.
|
|
|
|
|
I always had the idea that the best way to authenticate a user is to rely on their mailbox.
1) User enters email address and clicks the Login button
2) Website sends email to that account with one-time link
3) User clicks one-time link and that authenticates him into the site
Thoughts?
|
|
|
|