Advertisement
VLF

Stromasys CHARON-AXP v4.2.Build.142-01.68704122 Retail Linux

VLF
May 30th, 2017
2,946
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 34.71 KB | None | 0 0
  1. $! 58 ADAWI . : FFS EA !$
  2. $! 19 BLSS : SETPRV BYPASS CMKRNL DiAGNOSE READALL . INCL D6 !$
  3. $! BC CHMK ^ VOLPRO iMPERSONATE SHARE WORLD UPGRADE v JSB 16 !$
  4. $! B7 DECW | | LDPCTX 06 !$
  5. $! -- - >--+----------------------------------------+--> -- - !$
  6. $! 7A EMUL | | MATCHC 39 !$
  7. $! EB FFC | .................................... | PROBER 0C !$
  8. $! 0A INDEX | :__ __: __ : ______ : | REMQUE 0F !$
  9. $! 17 JMP | :\$\ /$/: |@| : |&&&&&&| : | SVPCTX 07 !$
  10. $! 3A LOCC | : \$\ /$/ : |@| : |&|____ : | TSTG 53FD !$
  11. $! 2F MOVTUC | : \$\ /$/ : |@| : |&&&&&&| : | VGATHQ 37FD !$
  12. $! 0D PROBEW | : \$\/$/ : |@|____ : |&| : | XORW3 AD !$
  13. $! 02 REI | : \$$/ : |@@@@@@| : |&| : | ASHQ 79 !$
  14. $! 2A SCANC | :............:..........:..........: | BGTRU 1A !$
  15. $! 73FD TSTH | | CRC 0B !$
  16. $! E9FD VSXORL | --:: THE VMS LiBERATiON FRONT ::-- | VSYNC A8FD !$
  17. $! FC XFC | | CLRL D4 !$
  18. $! 35FD VGATHL | +=================+ | MTVP A9FD !$
  19. $! 60 ADDD2 | -- +| IN VMS WE TRUST |+ -- | SPANC 2B !$
  20. $! DF PUSHAL | +=================+ | PUSHR BB !$
  21. $! - -- <--+----------------------------------------+--< - -- !$
  22. $! 03 BPT | | POPR BA !$
  23. $! FA CALLG ^ THE VERNON PRESERVATiON UNDERGROUND v IOTA EDFD !$
  24. $! 97 DECB . DEDiCATED TO PROJECT EMERALD : NOP 01 !$
  25. $! 74FD EMODH : . HALT 00 !$
  26.  
  27. --:: PRESENTS ::--
  28.  
  29. $!-- VLF::SYS$TARGET:[RELEASE] ---------------------------------------!$
  30.  
  31. Stromasys.CHARON-AXP.v4.2.Build.142-01.68704122.Retail.GNU.Linux.x64.Cracked-VLF
  32.  
  33. SOFTWARE NAME: Stromasys CHARON-AXP v4.2 Build 142-01.68704122
  34. SOFTWARE TYPE: Hardware Virtualisation
  35. DEVELOPER....: Stromasys SA, Switzerland
  36. URL..........: http://www.stromasys.ch/virtualization-solutions/charon-axp-on-linux/
  37.  
  38. VLF RCE.....: Subcommandante BYPASS RELEASE TYPE....: HARDWARE EMULATOR
  39. SUPPLiER....: TEAM VLF RELEASE DATE....: 2013-10-25
  40. PACKER......: TEAM VLF RELEASE DiSKS...: 10 X 5M
  41. LANGUAGE....: English RELEASE FORMAT..: vlfaae*
  42. PROTECTiON..: HASP SRM Dongle MEDiCiNE........: Runtime Patch
  43. PLATFORM....: GNU/Linux x64
  44.  
  45. $!-- VLF::SYS$TARGET:[RELEASE.DESCRiPTiON] ---------------------------!$
  46.  
  47. CHARON-AXP on Linux is a member of the CHARON cross-platform hardware
  48. virtualization product family. CHARON-AXP creates the virtual replica
  49. of the original Alpha Hardware inside a standard 64 bit x86 compatible
  50. computer system. It will run the original Alpha binary code, including
  51. operating systems OpenVMS and Tru64 UNIX, their layered products, and
  52. applications.
  53.  
  54. $!-- VLF::SYS$RCE:[iNSTALL.REGiSTRATiON.NOTES] -----------------------!$
  55.  
  56. 1) Unpack Charon-AXP-4.2-14201.68704.Repacked.Cracked-VLF.tar.bz2 into
  57. /opt/charon directory
  58.  
  59. 2) cd /opt/charon/bin/axp/
  60.  
  61. 3) ./libre.sh ./ds10l ../../cfg/ds10l.cfg
  62.  
  63. Also, read, carefully, the "install.readme.first.txt" plain-text file
  64. in the release archive save-set.
  65.  
  66. $!-- VLF::SYS$GROUP:[iNFO] -------------------------------------------!$
  67.  
  68. "They can't abide the cold steel, sir! no, sir! They don't like it
  69. up 'em."
  70.  
  71. -- Lance-Corporal Jack Jones (The local butcher), "Dad's Army," BBC TV
  72.  
  73. Subcommandante BYPASS ...... Reverse Code Engineer, Programmer
  74. Subcommandante XDelta ...... Cheer Squad, Special Operations
  75.  
  76. http://www.jokeindex.com/joke.asp?Joke=2606
  77.  
  78. NB: We were aiming for a v1.0.0.0 Final release of this NFO and the VLF
  79. MANiFESTO and ACTiViSM road-map, by 25.10 (2012), but health issues and
  80. the vicissitudes of life decided otherwise; nil desperandum; per ardua
  81. ad astra; nil illegitimus carborundum; Persta atque obdura.
  82.  
  83. $!-- VLF::SYS$GROUP:[MANiFESTO] --------------------------------------!$
  84.  
  85. --:: THE VMS LiBERATiON FRONT MANiFESTO ::--
  86. <v0.9.3.0 BETA>
  87.  
  88. We hold these truths to be self-evident:
  89.  
  90. That in VMS we trust.
  91.  
  92. That the VMS Operating System is part of the intellectual heritage and
  93. conceptual literacy in the commonwealth of computer science, the most
  94. immaculate, logical, systematic, disciplined, and literate culture and
  95. 'vade mecum' about how to go about the business of computing at every
  96. level of operating system function, that has ever been designed,
  97. devised and documented, it is a glory and testament to human ingenuity.
  98.  
  99. That the VMS Operating System mind-share, installation, third-party
  100. developer and expertise ecologies should never be allowed to collapse
  101. and die off or be inhibited from flourishing by the commercial
  102. expediency of Hewlett Packard nor the ruthless self-interest of third
  103. parties; that VMS will always be a viable Operating System culture for
  104. current and future generations of humanity.
  105.  
  106. That the VMS Operating System should be simultaneously ported to all
  107. of the Intel CPU architectures, both 32 and 64 bit, where all of the
  108. Microsoft Windows New Technology series of Operating Systems are
  109. manifest from the main-frame to the micro-computer and also ported
  110. to the 32 and 64 bit ARM architectures.
  111.  
  112. That the VMS Operating System should become a hybrid commercial Open
  113. Source Software system where Hewlett Packard generates income from
  114. Service Level Agreements they can actually deliver on for Business
  115. Critical Systems on certified hardware for enterprises, institutions
  116. and governments and so that the research and development, the
  117. evolution, of VMS can never ever again be suppressed or extinguished.
  118.  
  119. That neither snow nor rain nor heat nor gloom of night, nor the
  120. machinations and the visionary mediocrity of the Hewlett Packard and
  121. Microsoft corporations will stay our crackers and couriers from the
  122. swift and sure completion of their self appointed tasks and duties.
  123.  
  124. $!-- VLF::SYS$GROUP:[NEWS] -------------------------------------------!$
  125.  
  126. The 35th Anniversary of the mighty VMS Operating System is on the 25th
  127. of October 2012.
  128.  
  129. The 35th Anniversary Count-down Timer:
  130.  
  131. http://is.gd/The_35th_Anniversary_Of_VMS
  132.  
  133. We recommend quaffing quality lagered products for the occasion; sink
  134. several in celebration of the unstoppable, unsinkable, unkillable, VMS!
  135.  
  136. We also recommend quaffing lagered products for the 36th Anniversary of
  137. the mighty VMS operating system as well!
  138.  
  139. $!-- VLF::SYS$GREETiNGS:[SALUTATiONS] --------------------------------!$
  140.  
  141. No one currently, we, the DELTA:: node of the VLF, the Vernon
  142. Preservation Underground, are out of left field and are sui generis.
  143.  
  144. You get that on the big jobs.
  145.  
  146. $!-- VLF::SYS$RESPECT:[DEDiCATiONS] ----------------------------------!$
  147.  
  148. /""-._
  149. . '-,
  150. : '',
  151. ; * '.
  152. ' * () '.
  153. \ \
  154. \ _.---.._ '.
  155. : .' _.--''-'' \ ,'
  156. .._ '/.' . ;
  157. ; `-. , \'
  158. ; `, ; ._\
  159. ; \ _,-' ''--._
  160. : \_,-' '-._
  161. \ ,-' . '-._
  162. .' __.-''; \...,__ '.
  163. .' _,-' \ \ ''--.,__ '\
  164. / _,--' ; \ ; "^.}
  165. ;_,-' ) \ )\ ) ;
  166. / \/ \_.,-' ;
  167. / ;
  168. ,-' _,-'''-. ,-., ; PFA
  169. ,-' _.-' \ / |/'-._...--'
  170. :--`` )/
  171.  
  172. The work of the VMS Liberation Front is dedicated to the memory and the
  173. completion and extension of "Project Emerald" and the preservation and
  174. evolution of Vernon, the VMS mascot and totemic animal and all that he
  175. represents.
  176.  
  177. http://www.vaxination.ca/vms/shark/history.html
  178.  
  179. Refresh your memories:
  180.  
  181. http://h71000.www7.hp.com/openvms/20th/
  182. http://h71000.www7.hp.com/openvms/20th/vmsbook.pdf
  183.  
  184. We also salute the memory of BiG KEN OLSEN, may he rest in Silicon
  185. Heaven, and all the digits who made it all possible within DEC, the
  186. Digital Equipment Corporation.
  187.  
  188. http://en.wikipedia.org/wiki/Digital_Equipment_Corporation
  189.  
  190. $!-- VLF::SYS$LEGALiTiES:[CAVEATS] -----------------------------------!$
  191.  
  192. The policy and philosophy of the VLF with its keygenning, cracking and
  193. reverse code engineering (RCE) projects, is not the 'piracy' of
  194. intellectual property for the sake of it, per se, but to preserve,
  195. cultivate, and extend VMS mind-share for the future generations, VMS is
  196. too great a creation to be lost to humanity due to the cupidity and
  197. stupidity of HP management.
  198.  
  199. The VLF releases will establish the basis for which the VMS expertise
  200. ecologies of system programmers, analysts, system administrators,
  201. operators and network, security, capacity planning, technical support
  202. specialists and application developers can start to be repopulated,
  203. from the current near catastrophic collapse and extinction, from the
  204. coming generations of computer science students, by demolishing the
  205. entry barriers to them being able to familiarise themselves with VMS
  206. and the Layered Products - the entry barriers for students being, of
  207. course, the cost of software and hardware.
  208.  
  209. Sure Information Technology people can learn GNU/Linux and the Open
  210. Source Free Software tools for some decent conceptual and procedural
  211. literacy, but, alas, the vast majority are going to be eking out a
  212. computing crust mentally mutilating themselves mastering microsoft
  213. methodology, wallowing in the La Brea tar-pit of their near monopoly on
  214. matters computing.
  215.  
  216. Which is a profound tragedy when they could, in a slightly better
  217. world, be learning the VMS way to achieve the same goals on the same
  218. CPU architectures and platforms but with a much more conceptually
  219. literate and functionally facilitative mental life.
  220.  
  221. So during the period when computer science students are as poor as
  222. church-mice, studying, with the resources the VLF provides, they can
  223. study VMS and bootstrap themselves into competence and confidence and
  224. if they start earning money from their VMS skills, then it's time to
  225. buy the tools they use.
  226.  
  227. Businesses and professionals buying tools from other businesses to run
  228. their business makes the business world go round at the very least.
  229.  
  230. The VLF does not condone or approve of its releases being used for
  231. commercial gain at all, the purpose of the VLF releases is to stop and
  232. reverse the extinction of the VMS expertise ecology and mind-share for
  233. current and future generations.
  234.  
  235. The VLF does not apologise to the developers whose products we reverse
  236. engineer, since any such gesture would be dismissed, thus, instead, we
  237. reinforce the observation that if the VLF considered their application
  238. worth cracking and integrating into the tool-kit to assist in
  239. boot-strapping the VMS expertise ecology from catastrophic collapse by
  240. making the learning of VMS accessible and practical to the current and
  241. future generations of computer science students, then the application
  242. is worth buying, and if the VMS business, government and institutional
  243. installation ecology boot-straps back into vigor, then sales will
  244. naturally come their way.
  245.  
  246. Hewlett-Packard management of its VMS asset is the greatest impediment
  247. to your VMS applications' sales - direct your anger accurately,
  248. intelligently and effectively and publicly at them.
  249.  
  250. "It is practically impossible to teach good programming to students
  251. that have had a prior exposure to BASIC: as potential programmers they
  252. are mentally mutilated beyond hope of regeneration."
  253.  
  254. -- Professor Edsger Dijkstra, "How Do We Tell Truths That Might Hurt?",
  255. ACM SIGPLAN Notices Vol 17 No 5, May 1982
  256.  
  257. One wonders what the good professor thought of Microsoft...
  258.  
  259. $!-- VLF::SYS$SYSTEM:[ACTiViSM] --------------------------------------!$
  260.  
  261. "The Net interprets censorship as damage and routes around it."
  262.  
  263. -- John Gilmore, http://www.toad.com/gnu/
  264.  
  265. We the DELTA:: node of the VLF, the VMS Liberation Front, have
  266. regretfully concluded that HP management is damage to VMS and we are
  267. committed to routing around it.
  268.  
  269. The DELTA:: node of the VLF specialises in bypassing intellectual
  270. property protection so that no one else in the VMS activism world has
  271. to, although many, of course, have the requisite technical skills to
  272. parallel our work - we are the Vernon Preservation Underground.
  273.  
  274. Those VMS activists that are above ground and publicly active, we fully
  275. realise, will not be able to use the VLF releases, even if they were
  276. inclined to, and we do not assume that anyone would be so inclined,
  277. they will have to abide with existing DEC hardware, freeware hardware
  278. emulators and the HP Hobbyist VMS and layered products program.
  279.  
  280. The objective of the DELTA:: node of the VMS Liberation Front is to
  281. reboot and repair the catastrophic collapse of the VMS expertise
  282. ecology by systematically removing all impediments for the current
  283. generations of computer science students from being able to study,
  284. learn, and master the VMS way. We have achieved this with the LibreVMS
  285. LMFGEN license generator for VMS and LP and the LibreCHARON Stromasys
  286. VAX and AXP hardware emulators.
  287.  
  288. Vernon will be able thrive and survive at existing VMS revision levels
  289. and extant CPU architectures in full independence and autonomy, forever
  290. proofed against any extinction policies within or without of the
  291. Hewlett Packard corporation, the current owners of the VMS intellectual
  292. property.
  293.  
  294. This the VLF Liberation Front has unambiguously established.
  295.  
  296. However such underground, intellectual property transgressing activism
  297. is necessary but insufficient. What is also required is muscular and
  298. vigorous above-ground activism, in a logical, systematic and diligent
  299. manner with a lip curling snarl and no reservation with tooth and claw.
  300. With the VMS die-hards, if it isn't NDAs staying their hand, it's the
  301. HP VMS Hobbyist program, it has had natural effect of inhibiting full
  302. and frank commentary and fearless action, since there is the implicit
  303. fear that access to the VMS Hobbyist program would be withdrawn, either
  304. individually or generally, the LiBREVMS LMFGEN is an 'entente cordiale'
  305. nuclear deterrent to such inhibiting actions.
  306.  
  307. The first step in legal, above ground, VMS activism is to become a HP
  308. shareholder, as HP is a publicly listed company and to then sit on your
  309. tranche of shares and hence become a passionate, practical and
  310. principled part-owner of the Hewlett Packard corporation. As a
  311. part-owner of the HP corporation, you are then entitled to participate
  312. in the deliberative assemblies of the company, such as AGMs (Annual
  313. General Meetings) in accordance with Corporations Law and the HP
  314. Constitution and to engage in share-holder activism such as the calling
  315. of EGMs (Extraordinary General Meetings) with a sufficient quorum of
  316. your fellow share-holders and the concomitant notification to all
  317. share-holders of such an EGM and reason for it, as just one instance of
  318. activism.
  319.  
  320. As a share-holder, you are entitled to be angry, and you should be very
  321. angry at the compromise and degradation of both dividends and long term
  322. share holder value by the gross neglect and vandalism, over the last
  323. decade, of what should be one of the principal pillars and engines of
  324. income generation for the HP Corporation, the OpenVMS operating system,
  325. in all tiers of computing.
  326.  
  327. As a share-holder, you should be proud and grateful, if current or past
  328. principled, brave, and loyal HP employees decides, NDAs be damned, to
  329. become whistle-blowers on HP senior management policy on the VMS asset,
  330. disgusted by the lack of any promotion or advertisement of VMS, let
  331. alone the butchering of VMS maintenance and research and development.
  332.  
  333. As a share-holder, if the current database of VMS installations
  334. customers (sans any sensitive government clients, of course!) was
  335. leaked (and also any COTS, VAR, ISV, ETC, vendor databases), you would
  336. not see that as an act prejudiced against share-holder value at all,
  337. but rather a sunlight opportunity for the VMS installations customer
  338. base, and other VMS related vendors, to become totally reflexively
  339. aware, thence cooperatively constellating and engaging in share holder
  340. activism as well, the STAR:: Node of VMS above-ground activism.
  341.  
  342. Needless to say, in the year 2012, since the demise of DEC in 1998, and
  343. the five years of dithering during the Compaq era, until Compaq was
  344. merged with HP in the 2002, and then this last long, lean, decade of
  345. malign neglect, that the remaining VMS customer base is rusted on,
  346. either by need or by sagacious choice, either way they see VMS as being
  347. critical to their business operations, hence they are strongly
  348. motivated in matters VMS.
  349.  
  350. If the VMS installations customer base was to become totally
  351. reflexively aware, then even though sections of it may be competing
  352. against each other in particular markets, the one thing they would
  353. agree on unanimously and have sound cause to transcend their
  354. competitive differences is the enduring merit of the VMS operating
  355. system as a foundation of their business, thence they can cooperatively
  356. constellate to prosecute, vigorously and intelligently, the VMS cause,
  357. in rational self interest, collectively.
  358.  
  359. The extant rusted-on, reflexively aware, VMS customer and vendor base,
  360. could all purchase their own share tranches in HP and then form a VMS
  361. Industry Association, with a VMS Engineering quality carefully
  362. constructed constitution, including a rule that the voting weight of
  363. any association member is the (logarithm base 10 of their share
  364. holdings + 1) rounded down to the nearest integer - this substantially
  365. levels the deliberative playing field within the association, whilst
  366. also acknowledging the size of the players to an appropriate extent.
  367.  
  368. It is also in the realm of possibility, perhaps not probability, but
  369. that would have to be tested in practice, that such a VMS Industry
  370. Association might be able to force the installation of a Director on
  371. the HP Board, by dint of the co-ordinated share-holdings of its
  372. members. Such a VMS Advocacy directorship on the HP board may not
  373. result in cheaper support and maintenance contracts for the VMS
  374. Industry Association members (HA!), however they will be able to
  375. effectively audit and determine whether they are getting value for
  376. money, verifying whether HP has the actual expertise and resource
  377. infrastructure to properly deliver on their VMS maintenance and support
  378. SLAs (Service Level Agreements) for the members' business critical
  379. systems; indeed it would be incumbent due diligence on the VMS Advocacy
  380. director to determine whether HP management have been practicing deep
  381. fraud in this regard for the last decade.
  382.  
  383. This is but the shallow shoals of what an activism enfranchised VMS
  384. installations customer and vendor base can do, if it cooperatively
  385. constellates into the STAR:: (above ground) legal node of the VMS
  386. Liberation Movement.
  387.  
  388. "I cannot forecast to you the action of Russia. It is a riddle wrapped
  389. in a mystery inside an enigma: but perhaps there is a key. That key is
  390. Russian national interest."
  391.  
  392. -- Winston Churchill, BBC Radio Broadcast, 1st October 1939
  393.  
  394. The actions of HP management of the VMS asset over the last dread
  395. decade, is a riddle wrapped in a mystery inside an enigma, and there is
  396. a key, and that key is radical self-interest - radical self-interest
  397. that is not in the interests of long term HP share holder value and
  398. never has been.
  399.  
  400. The OpenVMS asset is in an deliberately induced coma in the HP hospice
  401. in an Itanium sarcophagus on a starvation drip feed with it's VMS
  402. Engineering heart ripped out and replaced with something risible that
  403. cannot patch, cannot port and cannot pursue research and development -
  404. and yet, OpenVMS still has a pulse and can regenerate from survival
  405. back to thriving with exigent, immediate, interdiction into HP
  406. management - they must be called to account.
  407.  
  408. The key of radical self-interest is blindingly obvious: cherchez le
  409. Microsoft.
  410.  
  411. Ken Olsen's original goal with the Digital Equipment Corporation was to
  412. give computing power to the people, quality was paramount and
  413. excellence was trusted to sell, maximum value and utility for market
  414. price. Microsoft is the antithesis of the DEC ethos, quality and
  415. excellence are sub-ordinate to profit, minimum value and utility for
  416. maximum price, and the full spectrum monopolistic domination in all
  417. market segments, by any means they can get away with, Microsoft
  418. benchmarks 'corporation as psychopath,' they are not interested in
  419. giving computer power to the people but the opposite, making people the
  420. disenfranchised computer peons of Microsoft in choiceless perpetuity.
  421.  
  422. Let us review salient historical events:
  423.  
  424. 1988: Microsoft hire O/S architects and engineers, led by Dave Cutler,
  425. from the Digital Equipment Corporation to build Windows NT.
  426.  
  427. 1993: Microsoft Windows/NT v3.1 first released.
  428.  
  429. 1995: Microsoft's Bill Gates and DEC's Robert Palmer announce the
  430. 'Affinity for OpenVMS' program, to assist customers implementing the
  431. (apparent) 'complementary' strengths of OpenVMS and Windows/NT in a
  432. three-tier client/server environment...
  433.  
  434. 1998: Compaq no longer supports Windows/NT (32 bit) on AXP.
  435.  
  436. The branch never falls far from the tree, and VMS was on the Microsoft
  437. assassination hit list, as of 1988, as a consequence of hiring DEC
  438. architects and engineers to design and implement Windows/NT, the child
  439. was always going to kill the parent. When Windows NT was initially
  440. ported to the Alpha AXP CPU architecture, the writing would have well
  441. and truly been on the wall that although W/NT and VMS are the two most
  442. comparable O/S architecturally, there is absolutely no comparison, in
  443. terms of performance, versatility, reliability, fault tolerance,
  444. security and utility, that was true in 1993 and remains true today in
  445. 2012, VMS utterly trumps Windows NT series operating systems, that is
  446. true on the AXP architecture and also true on the Itanium.
  447.  
  448. Thus Microsoft committed to ensuring that VMS would never be ported to
  449. those CPU architectures and computing tiers where Microsoft dominates
  450. commercially namely the Intel x86 and AMD64 CPU architectures, never
  451. ever, regardless of the multiple tier, super-scalability of the VMS
  452. operating system, and that remains true today. Microsoft also committed
  453. to ensuring that it was difficult to benchmark and compare W/NT and VMS
  454. on any architectures.
  455.  
  456. The Microsoft covert strategies for ensuring this are, at least, two
  457. fold:
  458.  
  459. 1. Microsoft cultivating key human assets in the employment of DEC,
  460. Compaq and HP that could shape both VMS policy and Windows Licensing
  461. negotiations to Microsoft's convenience.
  462.  
  463. 2. Microsoft encouraging 'Beads for Manhattan' strategies in Compaq
  464. post 1998 and then the merged HP-Compaq, post 2002, where they get
  465. 'discounted' Windows licenses, so long as they commit to not porting
  466. VMS to the Intel x86 and AMD64 architectures.
  467.  
  468. It is a 'Beads for Manhattan' strategy in that Compaq and HP-Compaq, in
  469. getting 'discounted' licences, and forgoing challenging Microsoft
  470. directly head-on, in its eminent CPU domains and computing tiers with
  471. the infinitely superior VMS, were getting the worthless 'beads' of
  472. volume price discounts, good for trivial short term profit but not long
  473. term market strength, and surrendering the opportunity to generate VMS
  474. income in those tiers of computation that Microsoft have an artificed,
  475. near, monopoly, with that infinitely superior product - VMS.
  476.  
  477. The 'threat' of porting VMS, kept in an induced coma on life support,
  478. rings increasingly hollow with every passing year, Microsoft feigns
  479. response in negotiations; yet, if the port was actually done, the
  480. threat would become very real indeed.
  481.  
  482. The HP-Compaq oxymoronic benchmarking management of its VMS asset has
  483. always been at maximal cognitive dissonance, the antithesis of any
  484. conceivable business rationality, the challenge was to make sense of
  485. the senselessness.
  486.  
  487. The cupidity and the stupidity, the corruption and incompetence within
  488. HP-Compaq management, needs to come to an end, Microsoft human assets
  489. within HP management, particular VMS policy management need to be
  490. identified and removed; similarly those in HP management that think
  491. cheaper Windows licenses is preferable to the re-fitting and
  492. re-ignition of the VMS income generation engine, need to be identified
  493. and removed.
  494.  
  495. The OpenVMS asset remains chained to the Itanium 'Itanic' ship-wreck on
  496. the bottom of the Mariana trench of enterprise computing without any
  497. advertising or promotion and it is time at its 35th Anniversary that it
  498. was liberated and finally ported to all 'WinTel' and AMD64 and ARM CPU
  499. Architectures, wherever Microsoft Corporation Windows New Technology
  500. series and derivative Operating Systems are manifest.
  501.  
  502. To assert that VMS is outmoded, obsoleted, yesterday's legacy
  503. technology, is as absurd as asserting that the bio-chemistry of your
  504. DNA and your immune system are similarly so. Vernon is the natural
  505. proprietary predator of Microsoft installations in all tiers of
  506. computation, from the enterprise to the personal and the ecological
  507. balance needs to be restored.
  508.  
  509. When that is achieved then and only then can the DELTA:: Node of the
  510. VLF, the Vernon Preservation Underground, retire back to the realms of
  511. myth and legend.
  512.  
  513. The rising star and spectacular success of Microsoft and the Windows/NT
  514. Operating System and its thriving third-party applications, services
  515. and expertise ecologies has been directly at the expense of VMS and the
  516. precipitous collapse, and near extinction of the VMS installation base,
  517. and its third-party applications, services and expertise ecologies; it
  518. is the computing crime of the 21st Century par excellence.
  519.  
  520. This 0.9.3.0 BETA VLF version of a VMS activism plan is not intended to
  521. be comprehensive, but it is a modest, yet non-trivial and pertinent
  522. basis from which to start envisioning about unsentimental, muscular and
  523. fearless, VMS Activism, and the VLF do encourage all that are
  524. passionate about the heritage of VMS, to trade in their ten gallon
  525. Stetson hats for one hundred gallon Stetson hats instead and to then
  526. have a long hard, think or re-think about 'nail-gun:wall' pro-active
  527. strategies to establish the renaissance of VMS for the next 35 years
  528. and to then publish your thoughts on comp.os.vms.
  529.  
  530. "It should be your care, therefore, and mine, to elevate the minds of
  531. our children and exalt their courage; to accelerate and animate their
  532. industry and activity; to excite in them an habitual contempt of
  533. meanness, abhorrence of injustice and inhumanity, and an ambition to
  534. excel in every capacity, faculty, and virtue. If we suffer their minds
  535. to grovel and creep in infancy, they will grovel all their lives."
  536.  
  537. -- John Adams (1735-1826) Founding Father, 2nd US President,
  538. Dissertation on the Canon and Feudal Law, 1756
  539.  
  540. $!-- VLF::SYS$QIO:[REQUESTS] --------------------------------------!$
  541.  
  542. We welcome the supply to the VLF of commercial OpenVMS software and
  543. commercial VAX, AXP, and PDP-11 hardware emulators.
  544.  
  545. We welcome the supply of OpenVMS Operating System and Layered Product
  546. source-code; ideally in "self regenerating" DECset form; but not
  547. limited to that - all source code is welcome.
  548.  
  549. Please refer to the VLF MANiFESTO and the ACtiViSM charter for our
  550. motivations in requesting such supply.
  551.  
  552. Thank you.
  553.  
  554. $!-- VLF::SYS$CONTACT:[DETAiLS] --------------------------------------!$
  555.  
  556. iRC: N/A
  557. Web: N/A
  558. Releases: Check the Usenet Binaries Newsgroup: alt.binaries.warez
  559. Announcements: Check the Usenet Discussion Newsgroup: comp.os.vms
  560. E-mail: mailto:vlf@hush.com (please use OpenPGP Encryption)
  561. Public Key: https://www.hushtools.com/hushtools2/index.php?
  562. Webform: https://forms.hush.com/vlf (OpenPGP encrypted)
  563.  
  564. Manifesto: http://is.gd/VLF_MANiFESTO
  565. Releases: http://is.gd/VLF_RELEASES
  566. Communiques: http://is.gd/VLF_COMMUNiQUES
  567.  
  568. NOTE: In light of the Edward Snowden NSA/PRISM revelations in mid-2013,
  569. this new privacy, security and anonymity resource directory has arisen:
  570.  
  571. https://prism-break.org/
  572.  
  573. Please familarise yourself with it, before contacting the VLF.
  574.  
  575. Be rest assured that if you decide to contact the DELTA:: Node of the
  576. VMS Liberation Front, the act of contact will not be interpreted by the
  577. VLF that you approve of our manifesto or methods, nor that you wish to
  578. join the VLF underground resistance movement. We also welcome
  579. corrections and refinements to the accuracy of our historical
  580. understanding and also to our analytical rigour.
  581.  
  582. One way to communicate to us in a traceless, or at least plausibly
  583. deniable way is to communicate via the hush mail encrypted webform,
  584. from a Tor-ified browser:
  585. https://forms.hush.com/vlf
  586.  
  587. http://www.torproject.org/
  588.  
  589. We highly recommend familiarising and mastering either of the Liberte
  590. Linux or Tails Live CD systems for communicating to us, (or at the very
  591. least as a Tor-ified browser resource):
  592.  
  593. http://dee.su/liberte
  594.  
  595. https://tails.boum.org/index.en.html
  596.  
  597. The only problem with using the hush mail web-form is that we can't
  598. communicate back to you. But if you have something important to send to
  599. us, then that is a fairly traceless way to do it.
  600.  
  601. If you wish to contact the VLF with full two way communication we would
  602. encourage you to establish a secondary email account and then to use
  603. PGP encryption, when communicating to us - to establish both your
  604. anonymity and your plausible deniability that you have done so.
  605.  
  606. Our OpenPGP public key can be obtained from:
  607.  
  608. https://www.hushtools.com/hushtools2/index.php?
  609.  
  610. Set up an opaquely named e-mail address which allows direct SSL
  611. enabled, POP and IMAP access from your computer's e-mail client.
  612.  
  613. These e-mail providers, for example, allow SSL enabled direct POP and
  614. IMAP access:
  615.  
  616. http://www.gmx.com http://www.fastmail.fm
  617.  
  618. http://www.yahoomail.com http://www.lavabit.com
  619.  
  620. (NOTE: Sadly, the immaculate Lavabit service is currently unavailable,
  621. due to the noble NSA/PRISM activism of the developer, Ladar Levison, in
  622. constitutionally challenging his National Security Letter.)
  623.  
  624. Thus you could install GnuPG or GPG4Win on your system and that would
  625. enables two way communication with the VLF in encrypted form:
  626.  
  627. http://www.gnupg.org/ http://www.gpg4win.org/
  628.  
  629. Note, however, that ordinary e-mail correspondence, encrypted or not,
  630. clearly fingers your IP addresses.
  631.  
  632. Therefore for the commissioning and the usage of any such e-mail
  633. address always transact such sessions at a public wi-fi portal and
  634. never on your home or work networks, that way such IP remains
  635. 'firewalled' from tracing.
  636.  
  637. Of course, the fact that you have communicated to us is still clearly
  638. present in your e-mail records on your computer. A practical
  639. alternative is to configure a persistent version of Liberte Linux on an
  640. encrypted USB stick or SD card, and only conduct e-mail correspondence
  641. from that system booted onto a laptop, which is used at a public wi-fi
  642. portal.
  643.  
  644. Another alternative is to commission a free Hushmail encrypted web-mail
  645. account via a tor-ified browser and to then always use that hushmail
  646. account via a tor-ified browser.
  647.  
  648. https://www.hushmail.com
  649.  
  650. The problem with free hushmail accounts is that they have to be logged
  651. into every three weeks otherwise they convert to a paid account; a paid
  652. account is quite convenient and can be anonymously purchased using the
  653. method described hence.
  654.  
  655. If you wish to send us large files, then upload them to a
  656. cyber-locker/file-host, these are recommended:
  657.  
  658. http://rghost.net/ http://datafilehost.com
  659.  
  660. Of course uploading via a tor-ified browser client.
  661.  
  662. For very large data sets we recommend uploading to the Usenet binaries
  663. newsgroup:
  664.  
  665. alt.binaries.test
  666.  
  667. Always upload using SSL tunneling, using a SSL enabled Usenet access
  668. provider.
  669.  
  670. Recommended tools:
  671.  
  672. http://www.jbinup.com/ or -
  673.  
  674. http://powerpost.free.fr/ used with https://www.stunnel.org/index.html
  675.  
  676. Use a nondescript file name and encrypt the archives with a password,
  677. locate a suitably tolerant public wi-fi access point to upload from and
  678. then securely contact us with the particulars, as detailed previously.
  679.  
  680. If you search about you will probably be able to find a fixed value,
  681. pre-paid, disposable, Visa or Mastercard debit card with which the
  682. on-line registration process only requires a working e-mail address for
  683. authentication and not a mobile phone number.
  684.  
  685. In commissioning a working e-mail address and hence also a synthetic
  686. identity, Yahoomail, at least, tolerates tor-ified browser use,
  687. otherwise use internet cafes or public wi-fi portals for the
  688. commissioning and usage of that e-mail account consistently and
  689. exclusively.
  690.  
  691. Once you have established the synthetic identity and the pre-paid debit
  692. card, you can then purchase pre-paid SSL enabled Usenet access, whence
  693. you can execute the uploads from a public-access wi-fi portal.
  694.  
  695. Please note that credit card OLTP systems usually reject proxied and
  696. tor-ified browsers for transactions and so for the actual purchase we
  697. recommend using a public portal; Internet Cafes that boot fresh O/S
  698. images from their intranet for each and every session are a recommended
  699. resource.
  700.  
  701. By such process disciplines your real identity will remain undisclosed
  702. and your plausible deniability will be maintained.
  703.  
  704. We do not warrant or assert that the methods explicated are totally
  705. safe and useful with no risk of compromising your anonymity. Please
  706. consult more knowledgeable resources on the Internet.
  707.  
  708. This is a useful guide, generally speaking:
  709.  
  710. Dr Who - Security and Encryption FAQ - Revision 22.6.2
  711.  
  712. http://pastebin.com/kNruUa3W
  713.  
  714. Of course if you think any of this advice is technically naive and
  715. could compromise your anonymity and plausible deniability, then please
  716. do not hesitate to correct us and to suggest better methods and
  717. processes, thank you.
  718.  
  719. However the VLF consider the methods outlined to be a useful basis from
  720. which to start thinking about secure anonymous communication and we
  721. think they would be useful for HP whistle-blowers, VMS activists, and
  722. those gagged by NDAs (Non-disclosure Agreements) that see the need to
  723. let some sunshine in on HP VMS policy, and to let some sunshine out,
  724. such as the source code for VMS and Layered Products.
  725.  
  726. YMWV, please do your homework first, you are VMS men, it should not be
  727. difficult.
  728.  
  729. $!-------------------------- damn straight ---------------------------!$
  730. $ opprobrium/level=kittens/mode=conniptions/input=VLF:/output=NL: !$
  731. $!--------------------------- enough said ----------------------------!$
  732. ..: NFO and DIZ v0.9.3.0 - 2013-10-25 - !xD :..
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement