1 INFO-VAX	Mon, 02 Jun 2003	Volume 2003 : Issue 303       Contents:  Re: read "generic PC CD" on VMS?  Re: read "generic PC CD" on VMS?< SEC:U MIT-MAGIC-COOKIE-1, Motif 1.3 and HP TCP/IP XDM (long)  Re: [OT] best HTML code cleaner?  Re: [OT] best HTML code cleaner?  Re: [OT] best HTML code cleaner?  Re: [OT] best HTML code cleaner?  F ----------------------------------------------------------------------   Date: 1 Jun 2003 12:49:58 -0500 - From: Kilgallen@SpamCop.net (Larry Kilgallen) ) Subject: Re: read "generic PC CD" on VMS? 3 Message-ID: <I6AAISXAec9J@eisner.encompasserve.org>   [ In article <3EDA2863.6F0E6798@fsi.net>, "David J. Dachtera" <djesys.nospam@fsi.net> writes:   H > "Generic PC CD" implies Joliet, not ISO-9660. I don't have a sample ofJ > the data/media he mentions, but I'd expect that MOUNT command to puke on > a Joliet CD.  E If the Primary Descriptor of a CD-ROM is in Joliet format, the CD-ROM E is not compliant with the Joliet specification.  By default, VMS will & mount based on the Primary Descriptor.  I > The newest VMS I have running here at home is V7.2 VAX. It just did the @ > MOUNT of a Joliet CD I wrote with EasyCD Creator V3.5a (130S): > 7 > DJMV01::DDACHTERA$ mount/noassi/med=cd dkb500/over=id , > %MOUNT-I-WRITELOCK, volume is write lockedI > %MOUNT-I-CDROM_ISO, FULLBKP_CD2: (1 of 1) , mounted on  _DJMV01$DKB500:   G If VMS emitted that, then I would say your CD-ROM has a normal ISO-9660  Primary Descriptor.   J > ... but I cannot explicitly specify a directory name such as [PROGRA~1]: > , > DJMV01::DDACHTERA$ dir dkb500:[progra~1]  < > %DIRECT-E-OPENIN, error opening DKB500:[PROGRA~1] as input- > -RMS-F-SYN, file specification syntax error   @ The character "~" is not valid in an ISO-9660 primary hierarchy.    > ...although wildcards do work: > - > DJMV01::DDACHTERA$ dir dkb500:[pro*]/noprot  >  > Directory DKB500:[PROGRA~1]  > ? > MICROS~1.DIR;1             4/4        13-JAN-2002 12:36:21.00    <snip>  ? > PGP.DIR;1                  4/4        13-JAN-2002 12:36:20.00 ? > PHOTOD~1$0.DIR;1           8/8        13-JAN-2002 12:36:23.00 ? > PLUS!.DIR;1                4/4        13-JAN-2002 12:36:17.00 ? > REAL.DIR;1                 4/4        13-JAN-2002 12:36:25.00 ? > REFLEC~1.DIR;1            20/20       13-JAN-2002 12:36:18.00 ? > SCANSOFT.DIR;1             4/4        13-JAN-2002 12:36:26.00    <snip>  ? > WINDOW~2.DIR;1             4/4        13-JAN-2002 12:36:26.00  > " > Total of 19 files, 96/96 blocks.  D So the tool that wrote that CD-ROM filled the Primary Hierarchy with" (mostly) illegal directory names !  A For anyone who wants to investigate the legality of such CD-ROMs, @ including whether or not they comply with Microsoft's own Joliet@ format, I suggest the free LJK/CDROM VERIFY capability described at http://www.ljk.com/ .  H > Depending on the CD content, he may or may not be able to retrieve any > meaningful data.  E The data in any files you find (and it looks like at least 2 of those H directories are not empty) is whatever is appropriate for an applicationG on the intended target machine.  This may limit what you can do on VMS, 8 which is unable, for instance, to run Microsoft viruses.   ------------------------------  % Date: Sun, 01 Jun 2003 14:49:52 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net> ) Subject: Re: read "generic PC CD" on VMS? ' Message-ID: <3EDA58E0.79FEBD5A@fsi.net>    Larry Kilgallen wrote: > ] > In article <3EDA2863.6F0E6798@fsi.net>, "David J. Dachtera" <djesys.nospam@fsi.net> writes:  > [snip]J > > Depending on the CD content, he may or may not be able to retrieve any > > meaningful data. > G > The data in any files you find (and it looks like at least 2 of those J > directories are not empty) is whatever is appropriate for an applicationI > on the intended target machine.  This may limit what you can do on VMS, : > which is unable, for instance, to run Microsoft viruses.   What about Soft-PC? ;-)    --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  % Date: Mon, 02 Jun 2003 13:58:33 +0930 / From: Mark Daniel <Mark.Daniel@wasd.vsm.com.au> E Subject: SEC:U MIT-MAGIC-COOKIE-1, Motif 1.3 and HP TCP/IP XDM (long) . Message-ID: <3EDAD271.3040302@wasd.vsm.com.au>  J I am not really wishing to start a "this is typical of DEC/CPQ/HP OpenVMS K Management ..." thread.  Please restrain the impulse to do so if this post  I just reinforces your experience over the years.  If there are others out  G there in this same situation it just might be an opportunity to inform  J those OpenVMS Engineering Project Managers who frequent and now are often H active in these newgroups, of what (I feel is) a very basic requirement.  K This relates to my day-job (DSTO), not the proprietory company represented  J by my email address (VSM).  That really dosn't change anything of course. L Small organizations as well as large are equally dependent the ubiquitous X  Window System environment.  L We are in the process of replacing a large number of older X-terminals that G provide only 8 bit colour with those supporting 24 bits (amongst other  K reasons).  In so doing we discovered that a candidate solution (which best  L goes unspecified in this forum) requires the support of MIT-MAGIC-COOKIE-1. A   Now, I don't want to debate the efficacy of the this method of  A "authentication" or privacy insurance.  Suffice to say it *is* a  L requirement.  It is also a "policy" that such such an authentication scheme K be used with X-terminals to reduce the possibility of unauthorized clients  H accessing sensitive information, including displays, entered passwords, I etc.  In other words, all the stuff that the standard X Window System so  K promiscuously allows.  Up until now we have not been able to implement the  C "policy" on our VMS systems because we use TCP/IP extensively as a  @ transport and DECwindows 1.0->1.2 has only supported user-based K authentication for DECnet, or the XDM-AUTHENTICATION-1 which is cumbersome  6 and was not practicable (at least in our environment).  J Motif 1.3 has changed this.  It supports MIT magic and works well.  (Many K thanks to the specialist handling the call at our national CSC for chasing  L this down and obtaining a copy for us well before we would have received it I on the Q2 distribution.)  OK, all is well.  Hmmm, not quite.  After time  J and effort was expended getting the XDM to support the MIT_MAGIC-COOKIE-1 H authentication it still didn't.  And won't!  You see, apparently all of L OpenVMS' X Display System (DECwindows) has received a major overhaul EXCEPT H THE XDMCP tool!  Yes, the XDM was "overlooked" (?) and does not provide   what the rest of the suite does.  L When I pressed my contact at the CSC he relayed his impression from OpenVMS L Engineering over this issue.  I quote (with permission) my reply here (with J only some private detail removed) so as not to have to recompose the same E sentiments.  He understood the remarks and is forwarding them to the  ) "whomever". Thanks for your reading time.   9 > From: Daniel, Mark Sent: Monday, June 02, 2003 11:17 AM  > Subject: RE: magic cookies >  > Hi [name], > E >> Sigh... I thought we were well past "yes/no", you can't do it with 8 >> XDM. We've been trying to raise this as a "please fix > I > My mistake.  I thought we were still in the "get the folks back home to  > tell us how" stage :^) > I >> this ASAP", but getting lots of "yeah, sure, after Itanium ships" type  >> noises. :-( > B > Never thought I'd be so exasperated.  I know I'm not telling youH > anything new [name], just expressing myself out loud.  Perhaps you can+ > return this reply verbatim to "whomever".  > J > Not wishing to again express any opinion over the essential value of MITC > magic cookie style authentication, it is so fundamental a part of I > heterogenous environments (which we all live in these days) that for it H > to be absent is tantamount to illuminating a neon sign over VMS sayingF > "DOES NOT FIT IN".  VMS does not need to draw attention to itself inH > *this* way.  Now, MIT magic in Motif 1.3 is an *excellent* move.  BUT,J > it's only half done if the XDMCP tool does not support it!!  Thin-clientJ > environments just cannot be supported without an effective XDM.  I wouldA > have thought this would have been obvious to blind-Freddy.  I'm H > surprised that someone in the DECwindows Motif 1.3 enhancement projectH > did not notice this, or did not state long and loud that the XDM is anJ > essential component of the VMS X Display System environment.  Perhaps itE > should be wrested from the TCP/IP team, or some better coordination I > between them and DECwindows project management.  Perhaps it is just Too  > Hard.  > I >> Can you give me a rough dollar value on what we could sell you guys if I >> we delivered this capability? If not dollars, then some number of DS?? % >> systems? As they say, money talks.  > J > Ignoring the issue of future Itanium sales :^)  Perhaps you might remindH > the bean counters that new systems aside, my Division retains hardwareG > and software maintenance on the existing systems.  I just enquired of W > our IT Manager and for this Division alone it's in the order of [considerable number] F > Australian beans per annum, the majority of which is for VMS systems? > (perhaps not major customer status, but significant, I'd say, J > "money-for-jam").  Considering the reported disparity in margins betweenI > sales of new iron and that for "services", I would suggest that OpenVMS G > first strive to retain this income stream before asking how much more F > we'll spend next year.  In fact it is probably from this source thatE > ports to Itanium are being funded.  Nobody is debating that now the 5 > Alpha platform has been declared obsolescent that a J > Itanium/Opteron/whatever port is necessary and inevitable but not to the+ > exclusion of much else that is necessary.  > M >> Or would we be giving sales to [platform]? XP workstations give heaps more E >> than 8 bit colour depth. DS10 or DS15 instead maybe? Wouldn't need  >> magic cookies at all... > C > Still would.  It has now come to the attention (after the need to K > explain why we can't support VMS sessions on [platform] - at least before D > Motif 1.3) of our IT Security Officer that those using VMS have no9 > connection authentication enabled on their X-Terminals. 0 > Needless-to-say, "this needs to be addressed". >  >> [signature] >  > Hope this is of some value.  > 
 > Regards, >  > Mark Daniel.   ------------------------------  % Date: Sun, 01 Jun 2003 19:01:26 +0200 2 From: martin@radiogaga.harz.de (Martin Vorlaender)) Subject: Re: [OT] best HTML code cleaner? ; Message-ID: <3eda3166.524144494f47414741@radiogaga.harz.de>   4 Russell Wallace (wallacethinmintr@eircom.net) wrote:5 > martin@radiogaga.harz.de (Martin Vorlaender) wrote:  > < > >#           De-moron-ise Text from Microsoft Applications >  > Looks good, but a question:  > D > >#   Eliminate idiot MS-DOS carriage returns from line terminator. > >s/\s+$/\n/g;  > A > Of course I don't disagree that CR+LF as opposed to plain LF is B > idiotic, but I remember reading somewhere that the HTTP standardC > actually required it; is that incorrect? Or is it just that it is G > required by the standard but web browsers will also accept pages that  > don't have it?  C In the body of an HTTP message (read: the HTML page) it's up to the D browser to cope with whatever the server spits out, be it CR, LF, or CRLF.   I There is a requirement for CRLF as a line terminator in the HTTP standard $ for the header lines of the message.  H BTW: The above removes multiples whitespaces (including newlines) at the end of each line.    cu,    Martin --  G So long, and thanks        | Martin Vorlaender  |  VMS & WNT programmer 4 for all the books...       | work: mv@pdv-systeme.deK In Memoriam Douglas Adams  |       http://www.pdv-systeme.de/users/martinv/ ;             1952-2001      | home: martin@radiogaga.harz.de    ------------------------------  % Date: Sun, 01 Jun 2003 19:11:15 +0200 2 From: martin@radiogaga.harz.de (Martin Vorlaender)) Subject: Re: [OT] best HTML code cleaner? ; Message-ID: <3eda33b3.524144494f47414741@radiogaga.harz.de>   # Didier Morandi (no@spam.com) wrote:  > Martin Vorlaender wrote:C > > This runs by the name of "demoronizing" in the perl newsgroups.  >  > Sounds good. Thanks.  G > Now, I'm not very familiar with Perl, except OpenVMS ones... should I J > rewrite  this script in DCL or is there a Perl/VMS HOWTO somewhere? (No,* > I did not look  at the Freeware CDs yet)  G Get your Perl for Win32 from www.activestate.com (comes as an MSI kit). F Or just let the script run under the latest VMS Perl - it should work.  B Supply the name of the file to clean up as the only parameter. TheG scripts writes the demoronized version to stdout, err... SYS$OUTPUT, so E redirect that to the output file. Alternatively, you can use the "-i" & option to edit the file in-place, like  #   perl -i_bak demoronize <filename>   F (The "_bak" is an extension added to the filename to save the original> file. IIRC, you have to supply it under VMS as well as Win32.)   cu,    Martin --  F   OpenVMS:                | Martin Vorlaender  |  VMS & WNT programmer3    The operating system   | work: mv@pdv-systeme.de F    God runs the           |   http://www.pdv-systeme.de/users/martinv/:    earth simulation on.   | home: martin@radiogaga.harz.de   ------------------------------   Date: 1 Jun 2003 12:44:01 -0700 ) From: daniel@mimer.se (Daniel Gustafsson) ) Subject: Re: [OT] best HTML code cleaner? < Message-ID: <de4cfd03.0306011144.a81021d@posting.google.com>  k wallacethinmintr@eircom.net (Russell Wallace) wrote in message news:<3ed9db08.125674723@news.eircom.net>... F > On Sun, 01 Jun 2003 04:22:03 +0200, martin@radiogaga.harz.de (Martin > Vorlaender) wrote: > < > >#           De-moron-ise Text from Microsoft Applications >  > Looks good, but a question:  > D > >#   Eliminate idiot MS-DOS carriage returns from line terminator. > >s/\s+$/\n/g;  > A > Of course I don't disagree that CR+LF as opposed to plain LF is B > idiotic, but I remember reading somewhere that the HTTP standardC > actually required it; is that incorrect? Or is it just that it is G > required by the standard but web browsers will also accept pages that  > don't have it?  > Yes, the HTTP and HTML standards actually require CRLF in manyB contexts. In some cases they specifically tolerate CR or LF, but I@ guess many applications always tolerate CRLF, CR or LF. XML (and> XHTML) is more relaxed and accept CRLF, CR, LF, and "different systems' line end codes".    -- Daniel Gustafsson > http://www.mimer.se - DBMS with optimistic concurrency control   ------------------------------  # Date: Sun, 01 Jun 2003 22:28:57 GMT 4 From: Craig A. Berry <craigberry@mac.com.spamfooler>) Subject: Re: [OT] best HTML code cleaner? @ Message-ID: <0979605ee24b9479fe2c64a7aef9bdf0@free.teranews.com>  3 In <3ED9B21F.10400@spam.com> Didier Morandi  wrote:  > Martin Vorlaender wrote: >>  B >> This runs by the name of "demoronizing" in the perl newsgroups. >  > Sounds good. Thanks. > H > Now, I'm not very familiar with Perl, except OpenVMS ones... should I G > rewrite  this script in DCL or is there a Perl/VMS HOWTO somewhere? ( . > No, I did not look  at the Freeware CDs yet)  I If the script does what it sounds like and just applies substitutions to  F each line of input and writes it out again, it's unlikely to make any $ difference which OS you run it on.    F The easiest place to learn about obtaining and running Perl on VMS is  the OpenVMS FAQ:  = <http://h71000.www7.hp.com/wizard/faq/vmsfaq_014.html#soft12>   E Since that section of the FAQ was last updated, OVMS Engineering has  ! released its own version of Perl:   D <http://h71000.www7.hp.com/openvms/products/ips/apache/csws_modperl. html>   H If you want to read the documentation on building your own copy of Perl I before downloading a kit, that information is available in the following  
 locations:  2 <http://www.perldoc.com/perl5.8.0/README.vms.html>  3 <http://www.perldoc.com/perl5.8.0/pod/perlvms.html>    ------------------------------   End of INFO-VAX 2003.303 ************************