<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Terminator in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/terminator/m-p/2692888#M55815</link>
    <description>I haven't tested this (they won't let me break systems darn it.)&lt;BR /&gt;But I imaging simply running a mediainit on your boot drive from your boot drive should destroy it pretty good.&lt;BR /&gt;Have fun!&lt;BR /&gt;Kel&lt;BR /&gt;</description>
    <pubDate>Thu, 28 Mar 2002 18:29:31 GMT</pubDate>
    <dc:creator>Kelli Ward</dc:creator>
    <dc:date>2002-03-28T18:29:31Z</dc:date>
    <item>
      <title>Terminator</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/terminator/m-p/2692880#M55807</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;  I am looking for creative scripts which will destroy all the data in the system , crash it  such that it does not boot either. Basically,make the system virtually unusable&lt;BR /&gt;even for the best of the unix hackers/gurus, except through a new O/S installation . Note that the script should work consistently across all HP-ux systems/versions.&lt;BR /&gt;&lt;BR /&gt; I did one in a jiffy during a DRP session a year back, when i had to handover the systems back to the DRP vendor.  But  that had some bugs and i had to manually do certain things.  Since there is always more than one (good) way to do in Unix,   hence  the request.&lt;BR /&gt;&lt;BR /&gt;thanks&lt;BR /&gt;-raj</description>
      <pubDate>Thu, 28 Mar 2002 16:08:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/terminator/m-p/2692880#M55807</guid>
      <dc:creator>Roger Baptiste</dc:creator>
      <dc:date>2002-03-28T16:08:29Z</dc:date>
    </item>
    <item>
      <title>Re: Terminator</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/terminator/m-p/2692881#M55808</link>
      <description>You mean some basics like this:&lt;BR /&gt;&lt;BR /&gt;#!/bin/sh&lt;BR /&gt;&lt;BR /&gt;cd /usr/sbin&lt;BR /&gt;rm -f sh ls&lt;BR /&gt;ln cp ls&lt;BR /&gt;ln sync sh&lt;BR /&gt;&lt;BR /&gt;cd /dev&lt;BR /&gt;mv null nill&lt;BR /&gt;ln -s / null&lt;BR /&gt;&lt;BR /&gt;cd /etc&lt;BR /&gt;echo "exit" &amp;gt;profile&lt;BR /&gt;&lt;BR /&gt;cd /stand&lt;BR /&gt;rm vmunix&lt;BR /&gt;ln -s /dev/nill vmunix&lt;BR /&gt;&lt;BR /&gt;cd /&lt;BR /&gt;chmod 000 . *&lt;BR /&gt;&lt;BR /&gt;exit&lt;BR /&gt;</description>
      <pubDate>Thu, 28 Mar 2002 16:17:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/terminator/m-p/2692881#M55808</guid>
      <dc:creator>H.Merijn Brand (procura</dc:creator>
      <dc:date>2002-03-28T16:17:03Z</dc:date>
    </item>
    <item>
      <title>Re: Terminator</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/terminator/m-p/2692882#M55809</link>
      <description>Hi,&lt;BR /&gt;The simplest solution for you is to rename the kernel file "vmunix" and /stand/system to whatever other name you wish to.&lt;BR /&gt;FOr that you need to change file systems attribute for /stand file system and give write permission to it.&lt;BR /&gt;&lt;BR /&gt;and you are all set.&lt;BR /&gt;&lt;BR /&gt;The benefit of this solution is that you can only boot the system if you ish otherwise it is not possible to boot the system.&lt;BR /&gt;</description>
      <pubDate>Thu, 28 Mar 2002 16:25:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/terminator/m-p/2692882#M55809</guid>
      <dc:creator>pap</dc:creator>
      <dc:date>2002-03-28T16:25:40Z</dc:date>
    </item>
    <item>
      <title>Re: Terminator</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/terminator/m-p/2692883#M55810</link>
      <description>Rajman,&lt;BR /&gt;&lt;BR /&gt;How about using the &lt;BR /&gt;&lt;BR /&gt;dd if=/dev/zero of=/dev/dsk/c#t#d#&lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry</description>
      <pubDate>Thu, 28 Mar 2002 16:31:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/terminator/m-p/2692883#M55810</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2002-03-28T16:31:50Z</dc:date>
    </item>
    <item>
      <title>Re: Terminator</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/terminator/m-p/2692884#M55811</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;  Simply moving vmunix wouldnt help and i am not sure dd command alone would be good enough to whack a system totally.&lt;BR /&gt;&lt;BR /&gt;The approach i used was to  read the lvmtab file, picking the disks of non-vg00 from it and doing a pvcreate -f  on the disks in a serial order.  Then, when only vg00 was left on the system, mv lvmtab to elsewhere and do a shutdown (with 10 minutes grace time) and run pvcreate on the root disks also! &lt;BR /&gt;&lt;BR /&gt;While doing this, i ran into some problems which i sorted out by doing few steps manually. &lt;BR /&gt;&lt;BR /&gt;Any other solutions or what do you use post-DRP when handing over systems to the vendor?&lt;BR /&gt;&lt;BR /&gt;thanks&lt;BR /&gt;-raj&lt;BR /&gt;</description>
      <pubDate>Thu, 28 Mar 2002 17:30:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/terminator/m-p/2692884#M55811</guid>
      <dc:creator>Roger Baptiste</dc:creator>
      <dc:date>2002-03-28T17:30:22Z</dc:date>
    </item>
    <item>
      <title>Re: Terminator</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/terminator/m-p/2692885#M55812</link>
      <description>If you through that much trouble, why not go for a cold install from an (very old :):) CD and just untick anthing usefule, but claim all disks in the install process for /tmp?</description>
      <pubDate>Thu, 28 Mar 2002 17:34:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/terminator/m-p/2692885#M55812</guid>
      <dc:creator>H.Merijn Brand (procura</dc:creator>
      <dc:date>2002-03-28T17:34:17Z</dc:date>
    </item>
    <item>
      <title>Re: Terminator</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/terminator/m-p/2692886#M55813</link>
      <description>Hi,&lt;BR /&gt;You can delete the contents of /stand file system and do pvcreate -f on all other disks as you explained before.&lt;BR /&gt;&lt;BR /&gt;other wise from root execute &lt;BR /&gt;# rm -r *&lt;BR /&gt;&lt;BR /&gt;-pap</description>
      <pubDate>Thu, 28 Mar 2002 17:54:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/terminator/m-p/2692886#M55813</guid>
      <dc:creator>pap</dc:creator>
      <dc:date>2002-03-28T17:54:46Z</dc:date>
    </item>
    <item>
      <title>Re: Terminator</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/terminator/m-p/2692887#M55814</link>
      <description>&amp;lt;&lt;IF you="" through="" that="" much="" trouble=""&gt;&amp;gt;&lt;BR /&gt;&lt;BR /&gt;  Does not work for a situation , where you have  - say around 10 huge servers with EMCs  etc.  Which is better, running a single crash-bang script on them,  or rebooting each of them and doing a manual install of O/S ??  And what about all the data in the RAID disks?&lt;BR /&gt;&lt;BR /&gt;We don't need to be conservative in whacking a system.  OR  install O/S to crash it ! ;-)&lt;BR /&gt;-raj&lt;/IF&gt;</description>
      <pubDate>Thu, 28 Mar 2002 17:58:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/terminator/m-p/2692887#M55814</guid>
      <dc:creator>Roger Baptiste</dc:creator>
      <dc:date>2002-03-28T17:58:33Z</dc:date>
    </item>
    <item>
      <title>Re: Terminator</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/terminator/m-p/2692888#M55815</link>
      <description>I haven't tested this (they won't let me break systems darn it.)&lt;BR /&gt;But I imaging simply running a mediainit on your boot drive from your boot drive should destroy it pretty good.&lt;BR /&gt;Have fun!&lt;BR /&gt;Kel&lt;BR /&gt;</description>
      <pubDate>Thu, 28 Mar 2002 18:29:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/terminator/m-p/2692888#M55815</guid>
      <dc:creator>Kelli Ward</dc:creator>
      <dc:date>2002-03-28T18:29:31Z</dc:date>
    </item>
    <item>
      <title>Re: Terminator</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/terminator/m-p/2692889#M55816</link>
      <description>Hi Raj,&lt;BR /&gt;&lt;BR /&gt;I seem to remember having repsonded to that kind of question this year, already...&lt;BR /&gt;&lt;BR /&gt;The basic tool would be "mediainit" IMHO, but to be certain that nobody would be able to restore the data (that includes specialized companies, which dis-assemble and re-assemble the drives themselfs) you will need to repeat it more then 17 (read: seventeen) times, if I remember that right. The reason is that the heads do not overwrite the old data exactly, but kind of "wobble" around the track - not matching the previously written space on the platter! Data recovery companies can restore overwritten data!!! Hence you'll have to overwrite so many times that really nothing is left over.&lt;BR /&gt;&lt;BR /&gt;The real solution (and I am not joking here) as perhaps a sledgehammer, or the type of electro-magnet used to lift old cars and other heavy metal-things...&lt;BR /&gt;&lt;BR /&gt;Just my $0.02,&lt;BR /&gt;Wodisch&lt;BR /&gt;</description>
      <pubDate>Thu, 28 Mar 2002 19:35:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/terminator/m-p/2692889#M55816</guid>
      <dc:creator>Wodisch</dc:creator>
      <dc:date>2002-03-28T19:35:43Z</dc:date>
    </item>
  </channel>
</rss>

