Yeah, you're "free" to have to do 365.25/365.25 on call. While needing the money more than your boss needing the help. Because if you go, there's 50 more lined up to take your position.
But you dont't have 50 more potential bosses to work for, and the few "opportunities" that do exist would impose similar conditions...
Meanwhile, being on call 24/7, 365.25 (this includes every fucking weekend, and every fucking holiday, and every fucking vacation -- no matter how remote) is a recipe for employees (me) finding ways to avoid it.
That's why in the free world, the law says that one given person can't be on call all the time. You are supposed to rotate this duty within the team, so that every week it's somebody else. And the one who's on call gets extra compensation for it (just for being "ready", even if during his period, there happens to be no call).
I personally would probably get one of those signal shielding bags and drop it in there when I wasn't to be on-call. Then you could carry it with you even. Then it also appears just as if it lost power for a while, so it would be hard to get in trouble over it...
I used to have a phone with the problem described in TFA, along with me allegedly being "on-call" at all hours.
Does "loss of signal" mean only "loss of GPS signal" or "loss of all signal". Indeed, if it's a phone, if it has no signal at all, and if you're on call, I can see where the employer might have a problem with this. And if you're not on call, go with the other posters more low-tech suggestions, and leave it at your desk...
In theory this says "unless you are arresting me, this is a voluntary interaction which I am ending".
... but actually your are not ending it, but rather continuing it by keeping on filming...
Legally, he could claim that because you voluntarily stick around, you are voluntarily consenting to any abuse that he's subjecting you to after you've got your chance to leave or stop all interactions with him.
Speaking of high-school pranks. One funny MBR-related thing we did back in the day was creating a loop in the chain of logical partitions (the MBR can only define 4 primary partitions. If you want more than 4 partitions, you created an extended partition which contains a linked list of logical partitions. And we made this linked list loop back to its beginning).
Windows (or DOS) versions back in the day were so buggy that they didn't notice the loop, and kept scanning, and scanning, and scanning until they reached the end of the list (which happened never, because it was a loop).
Result: unbootable machine. Even from a floppy. Because the DOS on the floppy was also doing the inventory of all storage media attached to the machine and stumbled upon the same partition loop. And if you removed the (internal) hard disk, well, then you couldn't obviously reinstall Windows on it.
The only fix was to boot Linux from a floppy, and remove the loop from there. However, back in the day Linux was still obscure enough that the "powers that be" didn't know about this fix...
The MBR also contains information about the disk partitions. The altered MBR overwrites the bytes for these partitions with Null bytes, making it even more difficult to recover data from the sabotaged hard drive.
Nowadays, most drives only contain a single partition (especially those of unsophisticated users), so even that is easy to recover. Or else, look for signatures of partition boot sector in the likely places (aligned on a cylinder start).
So, if popular culture approves of and encourages it, can't blame the cops too much for doing it despite it being merely illegal...
Yes, we can.
Indeed, we can, but unfortunately "we" don't. And that's the problem.
The "we" here is not the Slashdot readers (or other people well-informed about civil rights), but the population at large. And this population doesn't get any special training about their rights, but picks it up from movies and similarly unreliable sources.
So, even though police's training tells them that they shouldn't behave in such a way, they are confident that there will be very little backlash against such behavior (except from the "weirdos", which are a tiny tiny minority), and so they'll do it despite their training.
In summary: yes, we can blame police for this behavior. But we (the better informed people) should blame the movies as well.
Indeed, disk mirroring is not a replacement for backup. Disk mirroring only protects against (some...) hardware failures, but not against human error (such as accidentally removing the wrong file). Backups protect against human errors too (... and natural disasters, if kept offsite, and plenty of other error conditions which mirroring doesn't protect against).
(Guess one could go creative in dice designs but.. it really is the standard.)
Even by going "creative", you won't be able to create 10 sided dice... it's a mathematical impossibility as there are only five possible convex regular polyhedra, and none of them have 10 sides.
The way a D10 is usually made is by using a 20-sided Icosahedron, and have each number occur twice (i.e. there will be 2 faces labeled 3).
He has basically invented a scenario I've never seen anyone have trouble with.
I did take getting used to it. I remember, I had the same issue (accidental scrolling when trying to middle click) the first couple of days that I used a scroll-wheel mouse.
Ok, so for me this was only an issue while getting used to it, but I can imagine that other people might indeed have some (longer lasting...) motor skill issues with this. However, theoretically, it should be possible to configure X to ignore scroll events, solving this issue?
Misses files such as.a.b. and.a.b.
Try the following instead: ls -a | egrep '^\.([^.]|\..)'
(a string starting with a dot, then either a non-dot or a dot followed by any character)
Slashdot Mirror
But you dont't have 50 more potential bosses to work for, and the few "opportunities" that do exist would impose similar conditions...
Meanwhile, being on call 24/7, 365.25 (this includes every fucking weekend, and every fucking holiday, and every fucking vacation -- no matter how remote) is a recipe for employees (me) finding ways to avoid it.
That's why in the free world, the law says that one given person can't be on call all the time. You are supposed to rotate this duty within the team, so that every week it's somebody else. And the one who's on call gets extra compensation for it (just for being "ready", even if during his period, there happens to be no call).
We should name the diseases after politicians. Preferably members of the US Congress. They want the recognition.
They already do, in a way. It seems that santorum is named after a politician...
I personally would probably get one of those signal shielding bags and drop it in there when I wasn't to be on-call. Then you could carry it with you even. Then it also appears just as if it lost power for a while, so it would be hard to get in trouble over it...
I used to have a phone with the problem described in TFA, along with me allegedly being "on-call" at all hours.
Does "loss of signal" mean only "loss of GPS signal" or "loss of all signal". Indeed, if it's a phone, if it has no signal at all, and if you're on call, I can see where the employer might have a problem with this. And if you're not on call, go with the other posters more low-tech suggestions, and leave it at your desk...
Or go back to BBS days with 80x24 text resolution. ;)
Wouldn't that be unreadably small on that tiny watch face?
Yes, but in that case the "hacker" can kill the computer but, could not use that computer to kill you.
He could drop it on you...
In theory this says "unless you are arresting me, this is a voluntary interaction which I am ending".
... but actually your are not ending it, but rather continuing it by keeping on filming...
Legally, he could claim that because you voluntarily stick around, you are voluntarily consenting to any abuse that he's subjecting you to after you've got your chance to leave or stop all interactions with him.
... but it's still bizarre if you ask for permission to go, and then just continue to hang around at that exact spot...
There's still the risk of being charged with "wasting police time" though...
Couldn't you patch the VM software to hide the VM API's which make it recognizable as such?
This sounds like some high school student prank.
Speaking of high-school pranks. One funny MBR-related thing we did back in the day was creating a loop in the chain of logical partitions (the MBR can only define 4 primary partitions. If you want more than 4 partitions, you created an extended partition which contains a linked list of logical partitions. And we made this linked list loop back to its beginning).
Windows (or DOS) versions back in the day were so buggy that they didn't notice the loop, and kept scanning, and scanning, and scanning until they reached the end of the list (which happened never, because it was a loop).
Result: unbootable machine. Even from a floppy. Because the DOS on the floppy was also doing the inventory of all storage media attached to the machine and stumbled upon the same partition loop. And if you removed the (internal) hard disk, well, then you couldn't obviously reinstall Windows on it.
The only fix was to boot Linux from a floppy, and remove the loop from there. However, back in the day Linux was still obscure enough that the "powers that be" didn't know about this fix...
We used to have a receptionist who put so much crap on her PC
Damn, that receptionist must have been seriously hot
Yeah, he was.
:-)
Apart from that, female sysadmins (or company owners) do exist...
The MBR also contains information about the disk partitions. The altered MBR overwrites the bytes for these partitions with Null bytes, making it even more difficult to recover data from the sabotaged hard drive.
Nowadays, most drives only contain a single partition (especially those of unsophisticated users), so even that is easy to recover. Or else, look for signatures of partition boot sector in the likely places (aligned on a cylinder start).
A computer is not "destroyed" if you have to repair the MBR or reinstall Windows.
Not to mention, you don't have to re-install Windows. You can install a proper OS instead.
... or why those stupid horse blinkers?
Laws that need to be made in secret are bad laws.
... and not only bad, but also unconstitutional in many places. For example, in Luxembourg, the Constitution says that secret treaties are "abolished". Art. 37 subparagraph 3.
http://www.legilux.public.lu/leg/textescoordonnes/recueils/Constitution/Constitution.pdf
"Les traités secrets sont abolis."
Short and to the point.
(I know, Lux will not be party to this treaty, but it might be party to the similarly secret TTIP treaty)
So, if popular culture approves of and encourages it, can't blame the cops too much for doing it despite it being merely illegal...
Yes, we can.
Indeed, we can, but unfortunately "we" don't. And that's the problem.
The "we" here is not the Slashdot readers (or other people well-informed about civil rights), but the population at large. And this population doesn't get any special training about their rights, but picks it up from movies and similarly unreliable sources.
So, even though police's training tells them that they shouldn't behave in such a way, they are confident that there will be very little backlash against such behavior (except from the "weirdos", which are a tiny tiny minority), and so they'll do it despite their training.
In summary: yes, we can blame police for this behavior. But we (the better informed people) should blame the movies as well.
Yes. I mean't disk mirroring...
So, there's still another mistake then.
Indeed, disk mirroring is not a replacement for backup. Disk mirroring only protects against (some...) hardware failures, but not against human error (such as accidentally removing the wrong file). Backups protect against human errors too (... and natural disasters, if kept offsite, and plenty of other error conditions which mirroring doesn't protect against).
Your welcome. You can have it. Just make sure you don't allow them to reach port 25 on non Canadian IPs...
And not that he's the only such either...
Because now I know it's 151 digits. Had no idea before.
... but it's 153 digits, not 151. Or at least that's what grep -P -o '\d' | wc says when I paste the number into it...
lenses do have a resolving limit
true, but it is not expressed in Megapixels...
(Guess one could go creative in dice designs but .. it really is the standard.)
Even by going "creative", you won't be able to create 10 sided dice... it's a mathematical impossibility as there are only five possible convex regular polyhedra, and none of them have 10 sides.
The way a D10 is usually made is by using a 20-sided Icosahedron, and have each number occur twice (i.e. there will be 2 faces labeled 3).
He has basically invented a scenario I've never seen anyone have trouble with.
I did take getting used to it. I remember, I had the same issue (accidental scrolling when trying to middle click) the first couple of days that I used a scroll-wheel mouse.
Ok, so for me this was only an issue while getting used to it, but I can imagine that other people might indeed have some (longer lasting...) motor skill issues with this. However, theoretically, it should be possible to configure X to ignore scroll events, solving this issue?
ls -a | grep '^\..*[^.][^.]*$'
Misses files such as .a.b.
ls -a | egrep '^\.+[^.]+$'
Misses files such as .a.b. and .a.b.
Try the following instead:
ls -a | egrep '^\.([^.]|\..)' (a string starting with a dot, then either a non-dot or a dot followed by any character)