On Mon, Mar 22, 2010 at 2:47 AM, Tom Horsley <horsley1953@xxxxxxxxx> wrote: > The one thing I remember about AppArmor was that all the > pointless security restrictions were tied to a specific > executable, and if AppArmor was preventing you from running > some program, all you had to do was make a copy of > it, then you could run the copy without a peep from > AppArmor. Hah! My very first retail coding job was for Working Software in Santa Cruz, California, whose owner and president was Dave Johnson. He's a political blogger now: http://www.seeingtheforest.com/ Back in the day, he wrote the firmware for Ford's very first computerized carburetor. The development was done on a VAX using a cross-compiler. But when the boss would do a process listing (not ps - this was VMS) he would just get: adventure adventure adventure adventure engine Adventure was the original text adventure game, later sold in commercial form as Zork. All of Dave's coworkers spent most of their days playing Adventure - but Dave was always running programs with names like "engine," "carburetor," "ignition" and so on. "You're a good man, Dave," said his boss, patting him proudly on the shoulder. If He Only Knew! What Dave had done was to induce Adventure to dump core. He then renamed the core dump "engine" or "ignition" or what have you, then reanimated the core dump and played that! GNU Emacs does the very same thing; when it is first built it is called "temacs". temacs completes its initialization upon first execution, dumps core, then edits the core file to create a runnable binary called "emacs". That way one doesn't have to wait for all that initialization every time one wants to edit a file. Don Quixote -- Don Quixote de la Mancha quixote@xxxxxxxxxxxxxxxx http://www.dulcineatech.com Dulcinea Technologies Corporation: Software of Elegance and Beauty. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
