Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
I don't even see why there are so many other posts about Kermit, laplink, file transfers, PCMCIA, etc etc. Worst case is that the hard drive has a proprietary connector and you have to solder an adapter on.
Because rule #1 when trying to get data off twenty-year-old hardware is "If it's working, mess with it as little as possible."
In my experience, if you are upgrading legacy code that assumed straightforward ascii then utf8 is the
way to go. It was invented for the purpose by someone very smart (Ken Thompson). If there were a 'Neatest Hacks of All Time' competition utf8 would be my nomination.
The only real issues I've encountered are the usual ones of comparisons between equivalent characters and defining collating order. These stop being a problem (or more precisely 'your' problem) once you abandon the idea of rolling your own and use a decent utf8 string library.
Based on my experience as an executor, you should pick the best one or two photos from each significant occasion, record the date, location and the people (forename and surname) it shows in a plain text file and trash the rest. Fortunately chronological order is both the easiest and best way of organising such a collection. Don't bother keeping pictures that don't have clearly recognisable people in them because it's only these that will be of any interest in future.
Then, when you die your kids will inherit a nice collection of ca 100 family photos complete with enough information to make them interesting and give them a context.
To all of you who are sued for filesharing, you should ask the following proofs or you are not guilty or no copyright-violation has happened at all:[...]
The claimant does not have to prove anything to you they merely have to persuade a judge that, on the balance of probability, they are more likely to be telling the truth than you.
So, you're an employer who is short of skilled labour. You sign up to a scheme that requires the skilled personnel you do have, let's call her Nellie, to spend a significant fraction of her time training a school-leaver who's been told to sit next to her for three years. After three years the apprentice says 'Thanks for all the help, I've just been offered a nice job with another company.'. Only a C-level executive would think that this is going to work out well.
This sort of scheme has been tried before in the UK. For example, when there was a shortage of physics and maths teachers in schools a decade or so ago. Long story short, it was paying early career physics and maths teachers a bit more that fixed the problem.
Not really. The nice/nasty thing about Apple's walled garden, depending on your point of view, is that if just one user notices and reports your malware doing something it shouldn't Apple can revoke the relevant certificates and it's game over within a matter of hours.
Since one also has to provide proof of identity and pay a subscription to get the certificates in the first place unless the author took a lot of trouble to create a false identity they could be tracked down and prosecuted.
Now, I am sure there are flaws in this system, but it raises the bar to the point that there are easier ways for a hard-working computer-savvy crook to earn a living.