/etc/issue
message:http://superuser.com/questions/380550/modify-login-prompt-or-header-etc-issue-to-display-ip-address-of-the-machine
/etc/issue
message:As you may have noticed, Microsoft has disabled the standard method of accessing Safe Mode in Windows 8 in favor of a new Modern UI system. In other words, you can no longer press F8 during the Windows start up sequence and access the black and white Advanced Boot Options menu system from which you can select Safe Mode. Microsoft's justification for disabling the F8 key is essentially that computers boot up so fast these days that people will have trouble pressing F8 before Windows starts.
To be able to use F8 to get to Safe Mode, in Administrator Command Prompt type the command:
bcdedit /set {default} bootmenupolicy legacyhttp://www.techrepublic.com/photos/boot-windows-8-into-safe-mode/6414603?seq=11
Welcome to Hacking. The first rule of Hacking is: you do not talk about Hacking. The second rule of Hacking is: you DO NOT talk about Hacking! Third rule of Hacking: if someone yells "stop!", goes limp, or gets arrested, the hack is NOT over. Fourth rule: only two guys to a hack. Fifth rule: one hack at a time, fellas. Sixth rule: the hacks are bare Windows PC's. No Linux, no Unix, no Macs. Seventh rule: hacks will go on as long as they have to. And the eighth and final rule: if this is your first time at hacking, you have to hack.
A very fine idea for naming and nesting unit tests:
To have a nested class for each method being tested.
Sources:
This little trick, this one simple sentence, is like a missing piece in the jigsaw. I liked it from the very start. It fits very well alongside guides for naming of testing methods, like expressed in this article:
http://blog.stevensanderson.com/2009/08/24/writing-great-unit-tests-best-and-worst-practises/
I just wonder how this practice could fit into JUnit. Will have to try.