Just one word, really...
Why?
953 publicly visible posts • joined 6 Jun 2013
I presume the reason being that you'd have to set up an account that was capable of accepting swipe payments. I don't know how that's done, but I would hope that a certain quantity of personal information would be required (and have to be verified) before the bank would start accepting tap payments flowing into that account.
Possibly you could try and attach it to a legitimate business account as an aside, but to make it worth while you'd have to scam so many people that surely the pattern of customers phoning their bank and saying "I didn't buy this. Why is this charge on my card?" would trace back to you before you made enough money to just close down the business and leave the country.
-----BEGIN PGP MESSAGE-----
Version: GnuPG v1
jA0EBwMC4SoNhq0MkFpg0sAKAXaHo0m545FwVh2S44okpnkFWw2yLHnF4AvyxsL8
l7sJB/JYhEP/zuzgw6rBSTRwHm79RZzr+oefBy/OFvaDozqkEKSmzZKy6u7PQ870
ggnLBkqyYS85apEqkXPGOf8ZKFIrZbZROLhpxVvAJiajfFoWcXVFX1xjnmVBdLRn
ja7Tpl/qe5itScecBLHLicJlB3VeU2uLb8mdoQvvHPrAGF/AaAvkY5Cf9vWOchfg
eH5dwa+gR3FoV4qS7pRm8H0/bzJCugNNts9Isw==
=wvuo
-----END PGP MESSAGE-----
Key => title.
...that really popular torrents actually drive UP sales of the shared work because they cause it to reach an audience that wouldn't otherwise have known about it - rather like that spike in DVD sales that 'Python got when they put all their material on youtube. That being the case this wording:
(ii) knows or has reason to believe that communicating the work to the public will cause loss to the owner of the copyright, or will expose the owner of the copyright to a risk of loss.
becomes rather an interesting defence. "I don't know or have reason to believe that this will cause loss to the owner, as I chose to believe the aforementioned study that it actually does the opposite" I'm not sure what a court would make of that, but I'm sure some lawyers will enjoy finding out.
To call the result "Unsurprising" seems like an understatement.
Why use a Pi? Because it's like an order of magnitude cheaper than anything x86 and for the vast majority of people it'll be the only non x86 board they've ever heard of. Bit of a no brainer it seems to me, that.
It might work for us here - Instead of buying expensive servers full of expensive SAS RAID controllers which you have to keep populating with expensive SAS disks, and even more expensive flash caches, you could buy a cheap ethernet enclosure - basically a glorified switch with integrated drive caddies - and run something like CEPH where you just keep adding more disks as required.
The magic only works if the kinetic enclosure + disks is cheaper than the dedicated SAN server machine of course.
I'd really like to see them build these things with POE RJ45 sockets on the back so they could just be slapped straight onto an existing switch - but that's probably not actually all that useful once you're outside of a testing environment because the cable management would get annoying :/
I like to play this game with our Telecoms department. "Please call us on $NUMBER to report any problems" - um... how? My phone hasn't worked since you switched it to the NEW (not the old new, or even the old, or god forbid the analogue one we had before that) VOIP system.
...actually, I'm fine with them not fixing it. It means users have to use the ticketing system because they can't call me.
The point of these "standards" such as they are - or even the CPP Specification - is to say "We wrote this page in a way devoid of annoying bloat"
...but the site owners are the ones including all that crud in the first place. They chose to do it - no one made them - and presumably they chose to do it because they have numbers that say that forcing flash ads and "Please sign up to our newsletter" popups actually _does_ increase site revenue.
To make them change, surely the first step is going to have to be to convince them otherwise, or else to the suits who sign off on the final site design, this is going to look like a deliberate attack on their revenue streams, and why on earth would they agree to that?
I'm sort of with you. I have a work laptop that runs windows 10 and it's fine. It's just a Windows PC. It does everything I want of it. The control panel/system settings split is a massive step backwards, but everything else - meh, it's fine.
I'm still never installing Win10 at home because I don't trust Microsoft to be responsible with the data they'll gather from it, or trust them not to break my machine with some future update that I'm not allowed to opt out of.
I don't control the work machine, so I don't care about the loss of control. That's someone else's department. I'm not prepared to tolerate it on a machine that I manage personally.
I have tried bloody everything :/
It's a well defined problem at least. The nfs-kernel-server process owns the lock on the file. Since nfs-kernel-server isn't kind enough to proved a human parsable entry in /proc to let you know which instance of nfsd is actually holding a given file (and since each nfsd process doesn't map 1:1 to a particular nfs export that wouldn't help even if they did) there's no way to know which instance you can kill to get your lock back.
The only thing to do is shut down all of nfs-kernel-server and kick the 99% of your users who aren't causing problems.
Possibly we'd be better served with a user space NFS server, but they all seem to have their own problems.
Assuming you're using Linux at some point you will come across those words that make even the most hardened systems/storage admin tremble.
nfs-kernel-server.
I swear to fucking god they designed that thing just to mess with us. Anyone recognise this?
You need to delete this directory because $USER doesn't work here any more.
# umount /pool/home/$USER
umount: /pool/home/$USER: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
cannot unmount '/pool/home/$USER': umount failed
Wait... mounted? No they bloody don't. $USER has had their account deactivated. They've left the building. Their machine has been returned to the pool. No one other than the IT team could have mounted their share anyway - what gives?
Oh, wait, they turned the machine off at the wall didn't they. Well, now we're screwed, becuase nfs-fucking-kernel-server is going to sit there and await an unmount from the client and the only way to stop it is to restart the daemon - kicking everyone who actually IS using it.
(Honestly tho - if anyone has any ideas how the HELL you kick a user from a Linux NFS server in order to cause the kernel to release its lock on an exported filesystem, this is a bane-of-my-life type problem)
Sadly, not voting is NOT voting no!
This is the biggest problem in modern politics. I despise practically every "representative" that I've been offered for the last 3 parliaments. I don't trust any of them. I don't believe any of them will represent my interests in any way.
Not voting at all however achieves exactly the same, no representation. It's a nasty vicious circle. Short of running for office myself - something I consider myself entirely unfit to do - I have no idea where you even start to find a candidate that's worth the time of day.
That's what this is really about. When you're Ops that also does Dev I'm prepared to bet that 95% of the time it's because whoever you work for is too cheap to employ proper devs. I reckon that I'm "DevOps" which is to say my title is "Systems Administrator", which sounds like Ops to me, but when it comes to what I actually _do_ here, that doesn't mean a damn thing.
I'm responsible for researching things, buying them, installing them, configuring them (which all seems like Ops) but then, when inevitably someone goes "Oh, can it also do this? AndbythewayweneeditbyFriday" hacking together some code to patch in whatever awful thing we've been asked for without spending any money because we haven't got any.
Honestly, the number of places I know within a mile of me (I might occasionally spend Friday lunchtimes in the nearest pub with other distressed IT staff) that don't have version control is seriously frightening.
I've asked why before, and the answer is always the same: We don't have time to implement it because we're too busy putting out the fires caused by not having it.
I don't really know how you get out of that one.
As far as I can tell it translates roughly like this:
Nothing ever gets finished because you can never stop "developing" it to deal with the fact that it's got to keep "Operating" all the time and can't be shut down for proper testing.
Development + Operation all at the same time by the same people, see?
That's certainly what it feels like around here anyway.
...I'm actually expected to do this by work in the hope we might find out who it belongs to and return it to them. I managed to get the responsibility passed to me from the Receptionists who usually manage lost property because I at least have a bunch of disposable linux VM's to try it on.
Well, yes, but to be fair that is largely how legal advice works.
Ultimately whether or not this is legal will have to be decided by a court, at which point if lawyer N can convince the court that it is, then they were right.
That might be a crazy hard sell, which is why none of the others wanted to try it, but the law isn't some immutable thing like mathematics. If you want to make something legal, you just need to convince a court* that it is.
*or possibly many courts, assuming what you're trying is contentious and is going to result in an appeal.
Yeah. Running 5 production servers, 2 test servers over about 500Tb of total storage on it and Ubuntu 14.04. It Just Works. The only issue is having to wait for the DKMS modules to compile whenever you do a kernel upgrade and given how rarely we actually do that I could so care less about any of this nonsense.
...for this level of stupidity. Guys, it took about 5 seconds from reading the headline to realizing that this was going to be a TERRIBLE idea. How on earth did anyone manage to get from thinking it up to actually telling people about it without clocking at least one of the absolute show stoppers here?
Brought in your own kit? Well, enjoy that because unless it's either a mouse, a keyboard, or a USB flash drive the PC is your office is going to ignore it.
There are A3 multifunction copier/scanner/fax/printer things on each floor by each stairwell. Those you may use. Other scanners, printers, 1980s fax machines you will not use. We won't support them. No exceptions.
...I'm not sure it really does anything I need. Maybe it does things you need - and if so, that's great - but from where I'm sat (which incidentally is in front of a Windows 7 desktop with half a dozen PuTTY sessions open to various Linux machines) what I'd really want from this is a way to use my extensive bash experience to control Windows machines as easily as I control Linux ones.
That doesn't seem to be what Microsoft are aiming for here. They talk about "developers" but really, when I have my developer hat on I would never rely on this to test Linux code because it's not actually representative of what that code would do on a real Linux machine.
...until auto manufacturers start taking network security seriously.
I'm glad someone's doing it, but really it's pretty poor that this is required in the first place. As soon as internet connected things started going into cars there should have been requirements that they were properly isolated from anything that managed the actual driving, and those requirements should have been laid down in law as important public safety concerns.
Are you suggesting that, as is so often the case in the UK, we are in fact protected by from our government by it's own incompetence?
No I'm suggesting that catastrophic failures of the PNC to properly handle sensitive data are not only unsurprising to me, but from my experience with the thing, were inevitable.
Let me tell you a little story about a library cataloguing program called genesis. Genesis was originally implemented to use serial terminals attached to a minicomputer, but at some point in the early 80s was updated to run as a DOS program on x86 pcs. When they did this, they made some design decisions that are beyond bizarre, including reserving a few blocks of memory as a keyboard and screen buffer.
Yes, the same buffer.
The practical upshot of this was that if you were a proficient typist you could overflow the keyboard part of the buffer into the screen part and corrupt the display. The "fix" implemented for this was a keyboard combination that flushed the entire buffer and reset the system to the last saved state - effectively deleting any work you had done since the last commit.
Commits were only possible on the last page of each form, and forms couldn't scroll, so you had to fill in a page, read it carefully, tab your way to the "next" button, fill in the next page and so on until you got to the last one where you could finally save the data you'd just entered. If you cocked up by typing too fast, well, now the form was corrupted and you had to start all over again and some of these forms ran to 20 pages or so.
That is the second worst computer system I've ever used.
The PNC is the worst.
I'm right with you on that one. I loathe Android. The problem is that iOS is actually worse, and god knows how they even managed that.
I've not found a mobile OS I liked since webos went under. WinPho started well, but it's just turned into a complete train wreck the last couple of years.
I'm still holding out some forlorn hope that some form of converged Ubuntu might actually appear and be usable in the near future.
I'm certainly not going to downvote you because you're at least half right. It's a thing that happens. Sometimes tho, it's not that IT is doing things badly, it's that they're not successfully explaining why they won't do things at all.
Sometimes the reason this happens is that whatever the PHB is trying to get done is stupid and dangerous, IT have said "Not in a million years and here's precisely why", the PHB hasn't understood the "here's precisely why" bit, and then spends ages trying to circumvent the process instead of rethinking the original plan.
Our industry has a bit of a history of promising a pet bear. Sure, it sounds cool, and everyone is going to be impressed if you have one, but sooner or later it's going to bite your face off. Most PHB's don't have the technical understanding to realize that, and most IT staff aren't good at explaining complex problems to people who don't have a technical background.
"Eve must also have a bunch of domains that can serve mangled iCloud.com URLs."
If she's got herself a malicious access point that bob here is attached to, and a server capable of masquerading as one of Apples, wouldn't she be better off just hijacking all DNS requests to iCloud.com or have I missed something?
To take a break from all the smut related ones, I still think the stupidest thing I've ever been asked to do at work was remove a pair of lesbian ducks* and their duckling from a lecture theatre.
The logic, apparently, was that they had gotten into the lectern and were disrupting the ability of a lecturer to use the computer, and it was ergo an IT issue.
It turns out that ducks defending a duckling won't run away from you so as to stop you touching them, but will go absolutely fucking mental once you pick them up and try and carry them away from their charge.
*Yeah, you read that right. If you want to read up on the breeding habits of the common mallard duck, feel free, it's pretty surreal reading.