1 INFO-VAX	Fri, 12 Nov 2004	Volume 2004 : Issue 628       Contents:4 Re: An interesting link about CPU families over time Re: ANN: VMS Mosaic 3.8  Re: ANN: VMS Mosaic 3.8  Re: ANN: VMS Mosaic 3.8  Re: ANN: VMS Mosaic 3.8 ' Re: COBOL PAK for the Hobbyist License? ' Re: COBOL PAK for the Hobbyist License? % Re: Dynamic FTP site and file locking % Re: Dynamic FTP site and file locking % Re: Dynamic FTP site and file locking   hardware training - storageWorks- Re: how to implement an append only log file? - Re: how to implement an append only log file? - Re: how to implement an append only log file? - Re: how to implement an append only log file? " Re: Need help with a PeeCee again." Re: Need help with a PeeCee again." Re: Need help with a PeeCee again. Re: NFS weirdness % OT: Dell posts 25% Q3 profit increase  Re: Problem to Partition a disk  Re: Problem to Partition a disk ! Re: V/A SMB client product source + VMS NFS Client to Windows Services for Unix / Re: VMS NFS Client to Windows Services for Unix   F ----------------------------------------------------------------------   Date: 12 Nov 2004 04:37:14 GMT! From: Lee Witten <lw99@yahoo.com> = Subject: Re: An interesting link about CPU families over time / Message-ID: <Xns959F765EEA1C1nn48@199.125.85.9>   7 "Fred Kleinsorge" <fred.nospam@nospam.dec.com> wrote in + news:rmTjd.2575$Xi7.1361@news.cpqcorp.net:  E > While there may have been some amount of resentment in terms of the E > resources expended on one versus the other, and disagreements about ? > company strategy -- there was never any hostility between VMS G > engineering and UNIX engineering.  We have worked together frequently C > on many levels, and there are many ex-VMS engineers who over time   > moved to various UNIX groups.   L But it's very interesting to me to see that given the path Tru64 has taken, J that those VMS folks who moved to UNIX may have made a poor career choice.  K No, VMS and UEG got along just fine.  They shared a common enemy - storage  J engineering :-)  In fact the alpha systems folks also got along well with ! us - they had the same enemy too!   I Sorry Fred if you can't share that opinion [publically] but I don't have   that restriction these days.   --lw--   ------------------------------   Date: 11 Nov 04 14:19:29 EST) From: cook@wvnvms.wvnet.edu (George Cook)   Subject: Re: ANN: VMS Mosaic 3.8! Message-ID: <92TpgUwiA5kJ@wvnvms>   \ In article <4192D85A.EB1DF960@teksavvy.com>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes: > ! > Now, onto the next problem.....  >  > Library libvms.olb built. > > EDIT/TPU/NOSECTION/NODISPLAY/COMMAND=CVTHELP.TPU MOSAIC.HELP+ > %DCL-S-SPAWNED, process JFMEZEI_6 spawned % > RUNOFF /OUTPUT=[-]MOSAIC MOSAIC.RNH 3 > %RUNOFF-F-COI, Can't open input file "MOSAIC.RNH"  > %RMS-E-FNF, file not foundP > %MMS-F-ABORT, For target [-]MOSAIC.HLP, CLI returned abort status: %X10000004.I > %MMS-F-ABORT, For target LIBVMS, CLI returned abort status: %X10EE8034.  >  > P > now, a dir [...]mosaic.rnh yields nothing. Turns out that since I have "ed*it"? > symbol defined be default, it messed up the EDIT/TPU command.  > P > As a suggestion, you may wish to either DELET/SYMBOL/ALL/GLOBAl when you start] > the installation process, or use EDITX instead of EDIT (which bypasses EDIT redefinitions).   H A problematic issue.  Deleting all global symbols would break stuff likeF MMK which is normally executed via a global symbol, so Mosaic manuallyD deletes individual symbols which are likely to cause problems.  EDIT will now be one of those.      George Cook  WVNET    ------------------------------  % Date: Thu, 11 Nov 2004 19:58:00 -0500 - From: "John E. Malmberg" <wb8tyw@qsl.network>   Subject: Re: ANN: VMS Mosaic 3.81 Message-ID: <zIudnQElO5gFlwncRVn-iA@adelphia.com>    Richard Brodie wrote: J > "Bob Koehler" <koehler@eisner.nospam.encompasserve.org> wrote in message/ > news:A15q7dnZ4tEj@eisner.encompasserve.org...  >  >  >>>default : >>>}  <- end of switch >>>  >>/ >>   That's perfectly valid in C, C++, or Java.  >  > A > Current versions of DECC, CXX and gcc give warnings if pressed. H > A statement is required, even if a null one. It's a bit harsh, though,7 > to call it a major bug when it often passes silently.   F Of course the presence of the default : label is optional in a switch I statement, so if there is no action to be taken on default, why not just  
 leave it off?    -John  wb8tyw@qsl.network Personal Opinon Only   ------------------------------  % Date: Thu, 11 Nov 2004 20:19:03 -0600 2 From: David J Dachtera <djesys.nospam@comcast.net>  Subject: Re: ANN: VMS Mosaic 3.8+ Message-ID: <41941D97.936148E2@comcast.net>    George Cook wrote: > ^ > In article <4192D85A.EB1DF960@teksavvy.com>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes: > > # > > Now, onto the next problem.....  > >  > > Library libvms.olb built. @ > > EDIT/TPU/NOSECTION/NODISPLAY/COMMAND=CVTHELP.TPU MOSAIC.HELP- > > %DCL-S-SPAWNED, process JFMEZEI_6 spawned ' > > RUNOFF /OUTPUT=[-]MOSAIC MOSAIC.RNH 5 > > %RUNOFF-F-COI, Can't open input file "MOSAIC.RNH"  > > %RMS-E-FNF, file not foundR > > %MMS-F-ABORT, For target [-]MOSAIC.HLP, CLI returned abort status: %X10000004.K > > %MMS-F-ABORT, For target LIBVMS, CLI returned abort status: %X10EE8034.  > >  > > R > > now, a dir [...]mosaic.rnh yields nothing. Turns out that since I have "ed*it"A > > symbol defined be default, it messed up the EDIT/TPU command.  > > R > > As a suggestion, you may wish to either DELET/SYMBOL/ALL/GLOBAl when you start_ > > the installation process, or use EDITX instead of EDIT (which bypasses EDIT redefinitions).  > J > A problematic issue.  Deleting all global symbols would break stuff likeH > MMK which is normally executed via a global symbol, so Mosaic manuallyF > deletes individual symbols which are likely to cause problems.  EDIT > will now be one of those.   , Well, yeah, I guess that's one way to do it.  6 Like JF suggests, though, EDITX is a good work-around.  B Ideally, of course, you *NEVER* want to "symbolize" the verb EDIT, unless you do it like so:    $ ED*T :== EDIT/EDT   E ...or whatever your favorite default editor might be. EDT as a symbol F name does not "break" EDIT/EDT or EDIT/TPU as badly as using EDIT as a1 symbol name which really messes up both of those.    --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  % Date: Fri, 12 Nov 2004 07:03:04 +0200 * From: Mike Rechtman <rechtman@tzora.co.il>  Subject: Re: ANN: VMS Mosaic 3.8+ Message-ID: <2viug8F2kkcnmU1@uni-berlin.de>    David J Dachtera wrote:  > George Cook wrote: > ^ >>In article <4192D85A.EB1DF960@teksavvy.com>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes: >>" >>>Now, onto the next problem..... >>>  >>>Library libvms.olb built.? >>>EDIT/TPU/NOSECTION/NODISPLAY/COMMAND=CVTHELP.TPU MOSAIC.HELP , >>>%DCL-S-SPAWNED, process JFMEZEI_6 spawned& >>>RUNOFF /OUTPUT=[-]MOSAIC MOSAIC.RNH4 >>>%RUNOFF-F-COI, Can't open input file "MOSAIC.RNH" >>>%RMS-E-FNF, file not found Q >>>%MMS-F-ABORT, For target [-]MOSAIC.HLP, CLI returned abort status: %X10000004. J >>>%MMS-F-ABORT, For target LIBVMS, CLI returned abort status: %X10EE8034. >>>  >>> Q >>>now, a dir [...]mosaic.rnh yields nothing. Turns out that since I have "ed*it" @ >>>symbol defined be default, it messed up the EDIT/TPU command. >>> Q >>>As a suggestion, you may wish to either DELET/SYMBOL/ALL/GLOBAl when you start ^ >>>the installation process, or use EDITX instead of EDIT (which bypasses EDIT redefinitions). >>J >>A problematic issue.  Deleting all global symbols would break stuff likeH >>MMK which is normally executed via a global symbol, so Mosaic manuallyF >>deletes individual symbols which are likely to cause problems.  EDIT >>will now be one of those.  >  > . > Well, yeah, I guess that's one way to do it. > 8 > Like JF suggests, though, EDITX is a good work-around. > D > Ideally, of course, you *NEVER* want to "symbolize" the verb EDIT, > unless you do it like so:  >  > $ ED*T :== EDIT/EDT  > G > ...or whatever your favorite default editor might be. EDT as a symbol H > name does not "break" EDIT/EDT or EDIT/TPU as badly as using EDIT as a3 > symbol name which really messes up both of those.  >  ... and EDIT/ACL ...   Mike   --  J New to Usenet? read http://eisner.encompasserve.org/~rechtman/post_hlp.htmE --------------------------------------------------------------------- E Usual disclaimer: All opinions are mine alone, perhaps not even that. D Mike Rechtman                                 *rechtman@tzora.co.il*C    "20% of a job takes 80% of the time, the rest takes another 80%" E ---------------------------------------------------------------------    ------------------------------    Date: 11 Nov 2004 16:08:33 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) 0 Subject: Re: COBOL PAK for the Hobbyist License?3 Message-ID: <iTGS0BR2vpCv@eisner.encompasserve.org>   N In article <opshaz23k4zgicya@hyrrokkin>, "Tom Linden" <tom@kednos.com> writes:J > On 11 Nov 2004 13:22:51 +0100, Andreas Davour <ante@update.uu.se> wrote: > I >> I booted by simh/VAX yesterday and since my licenses had expired I got = >> the new ones from Montagar and registered and loaded them. J >> Now I notice that I no longer have any COBOL license anymore. Do anyoneI >> know why it have dissapeared, and if somehow HP could be smooth-talked < >> into letting us have a COBOL PAK as hobbyists once again?4 >> I actually had fun learning some COBOL on my VAX. > 5 > Cobol fun? Try PL/I if you really want to have fun.   %    BLISS and TECO for fun and profit.    ------------------------------  # Date: Thu, 11 Nov 2004 23:35:36 GMT % From: Roger Ivie <rivie@ridgenet.net> 0 Subject: Re: COBOL PAK for the Hobbyist License?3 Message-ID: <slrncp7tq6.7pb.rivie@Stench.no.domain>   K On 2004-11-11, Bob Koehler <koehler@eisner.nospam.encompasserve.org> wrote: P > In article <opshaz23k4zgicya@hyrrokkin>, "Tom Linden" <tom@kednos.com> writes:K >> On 11 Nov 2004 13:22:51 +0100, Andreas Davour <ante@update.uu.se> wrote:  >>  J >>> I booted by simh/VAX yesterday and since my licenses had expired I got> >>> the new ones from Montagar and registered and loaded them.K >>> Now I notice that I no longer have any COBOL license anymore. Do anyone J >>> know why it have dissapeared, and if somehow HP could be smooth-talked= >>> into letting us have a COBOL PAK as hobbyists once again? 5 >>> I actually had fun learning some COBOL on my VAX.  >>  6 >> Cobol fun? Try PL/I if you really want to have fun. > ' >    BLISS and TECO for fun and profit. &                                 ^^^^^^    Not with the hobbyist license... --  
 Roger Ivie rivie@ridgenet.net http://anachronda.webhop.org/  -----BEGIN GEEK CODE BLOCK----- 
 Version: 3.12 H GCS/P d- s:+++ a+ C++ UB--(++++) !P L- !E W++ N++ o-- K w O- M+ V+++ PS+? PE++ Y+ PGP t+ 5+ X-- R tv++ b++ DI+++ D+ G e++ h--- r+++ z+++   ------END GEEK CODE BLOCK------    ------------------------------    Date: 11 Nov 2004 16:12:17 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) . Subject: Re: Dynamic FTP site and file locking3 Message-ID: <43roNiBLiCdF@eisner.encompasserve.org>   f In article <cc5619f2.0411111016.5c3cb6f2@posting.google.com>, jordan@ccs4vms.com (Rich Jordan) writes: > @ > One obvious fix is to have the data sources FTP to a differentD > directory or directory tree and use a process on the VMS system toF > watch for and move the data files to the outbound FTP directory; theE > interlock time would be reduced to a second or two per file.  Or we H > could move the file into the anonymous FTP directory under a differentE > name, then do a rename, which should reduce the interlock time to a ! > fraction of a second (I think).  > = > That will work, but is there a better solution available?     F    Copying, whether from another location on the disk or from a remote    host, takes time.  A    Renaming, whether to a different name in the same directory or >    to a different directory on the same disk is much closer toA    instantaneous.  I don't know if it's atomic (I think not), but C    I also don't know any way that you can see it and not access it.   H    I still wish VMS engineering would give us a documented event to tellA    us when a directory was updated so we could wait on that event $    instead of polling the directory.   ------------------------------  % Date: Thu, 11 Nov 2004 18:14:10 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> . Subject: Re: Dynamic FTP site and file locking, Message-ID: <4193F240.12B09F03@teksavvy.com>   Rich Jordan wrote:F > From some testing with a network camera that FTPs files to a VMS FTPE > server, we've noted that if a request to d/l a file comes in during H > the period a data source is creating a new one, the downloading client > will get an access error.   M Download to a subdirectory, and after download, rename the file to the parent 3 directory where the customers can now download it.    M If the Cameras don't have enough smarts to issue the rename command after the L send command, then you'll have to have a process on VMS that regularly scansL the downalod directory to rename the files to the directory where the public can access the images.   ------------------------------  % Date: Thu, 11 Nov 2004 23:01:46 -0500 ( From: David Froble <davef@tsoft-inc.com>. Subject: Re: Dynamic FTP site and file locking, Message-ID: <419435AA.4050504@tsoft-inc.com>   Rich Jordan wrote:  C > We're going to be setting up an FTP site, hopefully on an OpenVMS H > Alpha system.  The site will hold data files placed there by dozens ofH > sources, updated every 20-30 minutes, via authenticated FTP sessions. @ > The connection the data sources use is low bandwidth, and eachC > transfer will take about 45-60 seconds; access by the downloading F > clients (using anonymous FTP) will be much faster.  Older (VMS file)E > versions of the data files will be retained, but users coming in to E > get the files should normally only retrieve the most 'current' one.  > H > The system will be running VMS V7.3-2, TCPIP V5.4 ECO2, and _might_ be, > running Hunter's FTP server package (TBD). > F > From some testing with a network camera that FTPs files to a VMS FTPE > server, we've noted that if a request to d/l a file comes in during H > the period a data source is creating a new one, the downloading clientC > will get an access error.  Given the 45-60 second potential delay 8 > before a retry works, that isn't going to work for us. > @ > One obvious fix is to have the data sources FTP to a differentD > directory or directory tree and use a process on the VMS system toF > watch for and move the data files to the outbound FTP directory; theE > interlock time would be reduced to a second or two per file.  Or we H > could move the file into the anonymous FTP directory under a differentE > name, then do a rename, which should reduce the interlock time to a ! > fraction of a second (I think).  > = > That will work, but is there a better solution available?    >  > Thanks >  > Rich > CCS  >   = Ok, just the way I see things, (usually called opinion).  :-)   K Until a file is fully transfered to the FTP server, as far as users (those  Q wanting to download the file) are concerned, the new file doesn't yet exist.  It  = cannot be considered to exist until it is entirely available.   Q Both your solutions are valid.  The first, to have seperate IN and OUT locations  T appeals to me.  It seems to potentially give you more control over what's happening.  P The second solution may be easier to implement, and as you mention, a very fast N operation.  Actually, from a user perspective, the rename is an instantaneous K action, since the file is complete, but not 'there' until the directory is  = updated.  From that perspective, #2 would be a better choice.    Dave   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------    Date: 11 Nov 2004 14:17:59 -0800, From: JimStrehlow@data911.com (Jim Strehlow)) Subject: hardware training - storageWorks = Message-ID: <4b6ec350.0411111417.483b1b6f@posting.google.com>   ? Other than the "school of hard knocks" or purchasing a hardware > support contract, are there some hardware training courses for= AlphaServers (in the future Integrity servers) regarding RAID 	 products?   @ We are planning to upgrade the firmware and o/s soon at a remote! location for an AlphaServer DS10.   ? Its RA3000  36 GB hardware RAID array failed years ago which we ( rebuilt; but did we rebuild it properly?; Did I properly configure the battery backup (UPS) properly? D We read the manuals. It has been running fine for a couple of years;	 but ... .   > Is there a way to backup the RAID storage block and controller configuration information?  D Is there software (along the lines of the old SWXCR*.COM procedures)E that checks the integrity for a "device type 4 Member RAID 5" RA3000?     0 Or you could help me by answering the following.$  - what is your RAID hardware array?  E  - did you configure it strictly on OpenVMS or did you need to set it A up via a laptop with some software that ran on Microsoft Windows?   2  - how difficult was it to configure and maintain?    - would you recommend it?     Thanks in advance.  5 Jim Strehlow, OpenVMS Administrator, Alameda, CA, USA    ------------------------------    Date: 11 Nov 2004 13:04:52 -06004 From: kaplow_r@encompasserve.org.TRABoD (Bob Kaplow)6 Subject: Re: how to implement an append only log file?3 Message-ID: <FNxLLJs+94PK@eisner.encompasserve.org>   J Everyone seems to be missing the obvious answer. The only way to prevent aL priv user from modifying a file is to place that device on write once media:+ WORM CDrom, line printer, or paper tape :-)   1 	Bob Kaplow	NAR # 18L	TRA # "Impeach the TRA BoD" & 		>>> To reply, remove the TRABoD! <<<K Kaplow Klips & Baffle:	http://nira-rocketry.org/LeadingEdge/Phantom4000.pdf L     www.encompasserve.org/~kaplow_r/    www.nira-rocketry.org    www.nar.org  K         "For as adamant as my country has been about civil liberties during I         peacetime, it has a long history ... of failing to preserve civil J         liberties when it perceived its national security threatened." -- 4         former Supreme Court Justice William Brennan   ------------------------------    Date: 11 Nov 2004 13:42:23 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) 6 Subject: Re: how to implement an append only log file?3 Message-ID: <426m165j8gUl@eisner.encompasserve.org>   j In article <FNxLLJs+94PK@eisner.encompasserve.org>, kaplow_r@encompasserve.org.TRABoD (Bob Kaplow) writes:L > Everyone seems to be missing the obvious answer. The only way to prevent aN > priv user from modifying a file is to place that device on write once media:- > WORM CDrom, line printer, or paper tape :-)   F WORM disks are good, but they do not address the risk of modifications# being made to the operating system.    ------------------------------  % Date: Thu, 11 Nov 2004 21:40:35 +0200 * From: Mike Rechtman <rechtman@tzora.co.il>6 Subject: Re: how to implement an append only log file?+ Message-ID: <2vhthkF2mr622U1@uni-berlin.de>    Roy Omond wrote: > Tom Linden wrote:  >  >> [...snip...]  >>F >> Came across this other day when googling on watchdog, to emphasize = >> the  point    http://www.wordserf.co.uk/mh/vaxhackpro.html  >  > < > Ah, the days of the Cuckoo's Egg, July 1987, and the Chaos > Computer Club. > > > I was the whistleblower ... it was an "interesting" exercise@ > in reverse enginnering to see what they had done, and how they > had done it.  F Notice on the web site there's "a program that should be in every VMS H hacker's toolbox"; Minor detail: "Ok one small note, you require CMKRNL 0 privilege to execute this file ..." yeah, right.   Mike   --  J New to Usenet? read http://eisner.encompasserve.org/~rechtman/post_hlp.htmE --------------------------------------------------------------------- E Usual disclaimer: All opinions are mine alone, perhaps not even that. D Mike Rechtman                                 *rechtman@tzora.co.il*C    "20% of a job takes 80% of the time, the rest takes another 80%" E ---------------------------------------------------------------------    ------------------------------    Date: 11 Nov 2004 16:07:36 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) 6 Subject: Re: how to implement an append only log file?3 Message-ID: <cqvMOvRT0rGv@eisner.encompasserve.org>   j In article <FNxLLJs+94PK@eisner.encompasserve.org>, kaplow_r@encompasserve.org.TRABoD (Bob Kaplow) writes:L > Everyone seems to be missing the obvious answer. The only way to prevent aN > priv user from modifying a file is to place that device on write once media:- > WORM CDrom, line printer, or paper tape :-)  >   @    Then you have to trust the software that's doing the writing.   ------------------------------  % Date: Thu, 11 Nov 2004 20:15:47 -0600 2 From: David J Dachtera <djesys.nospam@comcast.net>+ Subject: Re: Need help with a PeeCee again. + Message-ID: <41941CD3.23380D08@comcast.net>    Chris Scheers wrote: >  > JF Mezei wrote:  > > Chris Scheers wrote: > > E > >>It appears that your CD burning software is using the short names J > >>instead of the long names.  It may have an option to specify which set > >>of names to use. > >  > > J > > Nop. Joliet extension has a similar encoding thing. It stores both 8.3Q > > filenames in the standard  ISO 9660 place, and stored the complete file names 5 > > in a different place used by the Joliet software.  > > R > > So when you mount a CD that is Joliet encoded on a non Joliet machine, you seeQ > > the 8.3 names. Mount the same CD on a Joliet equipped machine and you see the  > > full names.  > I > If I understand this correctly, the ISO9660 standard defines 8.3 names, 8 > and then an extension is used to support longer names. > ) > What extension(s) are supported by VMS?   F I think it may depend which VERSION of ISO-9660. I believe you need at7 least V3 to support lowercase or mixed case file names.    --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------    Date: 11 Nov 2004 21:52:52 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) + Subject: Re: Need help with a PeeCee again. 3 Message-ID: <VsDgwdbU2lDQ@eisner.encompasserve.org>   ` In article <41941CD3.23380D08@comcast.net>, David J Dachtera <djesys.nospam@comcast.net> writes: > Chris Scheers wrote:  J >> If I understand this correctly, the ISO9660 standard defines 8.3 names,9 >> and then an extension is used to support longer names.  >>  * >> What extension(s) are supported by VMS? > H > I think it may depend which VERSION of ISO-9660. I believe you need at9 > least V3 to support lowercase or mixed case file names.   @ V3 is not a version.  When VMS support for ISO-9660 was written,E it was based on the first edition of the standard, dated 15-Apr-1988.   D The next edition to the best of my knowledge is the one that allowedE the option of supporting no-file-extension names, which was important & for Japanese language directory names.  F To the best of my knowledge, no version of ISO-9660 has ever permittedG the "Joliet" extensions specified by Microsoft.  While well-intentioned E (from a Microsoft perspective) double-byte characters in the metadata   are _not_ permitted by ISO-9660.  E The Rock Ridge (and subsequent IEEE) extensions _are_ fully compliant : with ISO 9660 in the way they provide additional metadata.  F The VMS extension to support full RMS file charactersitics _are_ fullyD compliant with ISO 9660 in the way they provide additional metadata.  ; ISO 9660 section 10 specifies three "Levels of interchange"    	Level 1 		No multi-section files5 		8.3 character filenames (uppercase alphabetic only) 9 		8 character directory names (uppercase alphabetic only)    	Level 2 		No multi-section files   	Level 34 		No restrictions on the full ISO 9660 specification  B Level 3 is required to have files that exceed the size of a singleC volume.  I know of no operating system other than VMS that supports  Interchange Level 3.  B For that matter, I know of no operating system other than VMS thatA supports section 6.10 Record Structures.  Section 13.2 appears to E contain weasel words to allow receiving systems to omit that support.   C I know of no operating system other than VMS that supports Extended  Attribute Records.   ------------------------------  # Date: Fri, 12 Nov 2004 05:44:32 GMT + From: LESLIE@JRLVAX.HOUSTON.RR.COM (leslie) + Subject: Re: Need help with a PeeCee again. 4 Message-ID: <45Ykd.12993$SS3.10054@fe2.texas.rr.com>  8 Michael Moroney (moroney@world.std.spaamtrap.com) wrote: : I : Unpatched M$ systems often get infected with a virus within minutes of  H : being connected to the internet.  (that includes brand-new ones fresh I : from the store whose windows version is usually many patches too old)    :   + Average time between attacks: 16 minutes...   *   http://isc.sans.org//survivalhistory.phpA   SANS - Internet Storm Center - Cooperative Cyber Threat Monitor 6   And Alert System - Current Infosec News and Analysis    5   http://www.sans.org/rr/whitepapers/windows/1298.php %   Windows XP: Surviving the First Day   &  "SANS Institute Internet Storm Center  E   Since its release, a number of severe security vulnerabilities have B   been discovered in Windows XP. These vulnerabilities are used byB   worms and viruses, making it impossible to connect an unsecured,A   unpatched system to the Internet for any amount of time without B   risking exposure and infection. Users of new computers are facedE   with the dilemma of being infected by these worms before being able $   to download the necessary patches.  B   This guide will show how to install Windows XP securely, without?   being infected by these worms during the patching process..."        --Jerry Leslie9   Note: leslie@jrlvax.houston.rr.com is invalid for email    ------------------------------  + Date: Fri, 12 Nov 2004 02:07:26 +0000 (UTC) , From: lewis@PROBE.MITRE.ORG (Keith A. Lewis) Subject: Re: NFS weirdness. Message-ID: <cn15su$22i$1@newslocal.mitre.org>  { huber@NOBODY-mppmu.mpg.de (Joseph Huber) writes in article <jLOUAFqBRhlM@vms.mppmu.mpg.de> dated 9 Nov 2004 09:32:10 +0100:   >Check Your TCPIP MOUNT options: > /ADF=CREATE or /NOADF L > /STRUCTURE=2 or 5  i.e. treat the volume like a VMS ODS-2 or ODS-5 volume.  F /ADF does not matter here because VMS is reading data which was mostlyL created on Unix/Linux.  There aren't any .ADF files and there won't be.  But for the record I use /NOADF.  D >The filename-translation is different for ODS-2 vs. ODS-5 volumes, 0 >also influenced by several DECC$ logicals like 6 > DECC$FILENAME_UNIX_REPORT, DECC$FILENAME_UNIX_ONLY, 5 > DECC$EFS_CASE_PRESERVE, DECC$READDIR_DROPDOTNOTYPE,   >(Java uses these DECC rules !), > ' >and also by SET PROCESS /PARSE_STYLE .   J I have problems with both parse styles, although the filename given in theI error message is different.  I went to a lot of trouble to put mixed-case K into my filenames (several thousand) and don't want to erase that work just ) because a new VMS version chokes on it.     J My latest test was re-installing TCPIP 5.3 on top of VMS 7.3-2.  It didn'tJ help.  The next logical step would be to re-install VMS 7.3-1, but I thinkK I'll give those DECC$* logicals a crack first, as my key app in all this is 7 CSWS 1.2 which I'm pretty sure was built using DEC C.     J Thanks for the hint on those logicals; I had no idea DEC C had its own set? of parameters for this stuff.  I found some documentation here: < http://h71000.www7.hp.com/DOC/731FINAL/5763/5763pro_001.html< http://h71000.www7.hp.com/doc/731FINAL/5763/5763pro_005.html  0 --Keith Lewis              klewis {at} mitre.org> The above may not (yet) represent the opinions of my employer.   ------------------------------  % Date: Thu, 11 Nov 2004 16:52:45 -0500 # From: "John Smith" <a@nonymous.com> . Subject: OT: Dell posts 25% Q3 profit increase, Message-ID: <Y9ydnWtJV9epQg7cRVn-uw@igs.net>  = http://online.wsj.com/article/0,,SB110011049104870259,00.html        Dell's Profit Climbs 25% With Strength Abroad  ) A WALL STREET JOURNAL ONLINE NEWS ROUNDUP  November 11, 2004 4:27 p.m.   H Dell Inc.'s profit climbed 25% amid a solid surge in revenue, boosted byD strength abroad and a pickup in spending by U.S. business customers.  J The Round Rock, Texas, computer maker reported net income of $846 million,K or 33 a share, for its fiscal third quarter ended Oct. 29. That compares to I net income of $677 million, or 26 cents a share, in the same quarter last  year.   I Revenue rose 18% to $12.5 billion from $10.62 billion in the year-earlier  period.   I In August, Dell predicted third-quarter earnings of 33 cents a share with L revenue of about $12.5 billion. Analysts surveyed by Thomson First Call wereE expecting Dell to earn 33 cents a share on revenue of $12.54 billion.   L The company cited a 27% sales jump in Europe, the Middle East and Africa andK 25% growth in Asia-Pacific and Japan. It said a 20% increase in spending by 6 business customers boosted its performance in the U.S.  L Dell said it sold a combined eight million standards-based servers, notebookL computers and desktop computers world-wide in the quarter. Notebook computer volumes rose 35%.   L Dell, which is continually battling for world's top PC maker spot with rivalL Hewlett-Packard Co., has so far managed to avoid the downturn plaguing otherK technology companies as sales of its higher-margin servers and notebook PCs ! outpace lower-margin desktop PCs.   F Looking ahead, Dell said Thursday its fourth-quarter product shipmentsH should be about 20% higher than in the same year-ago period, putting itsI revenue at about $13.5 billion and earnings at 36 cents a share, about in G line with First Call's forecast. Analysts were expecting earnings of 36 - cents a share with revenue of $13.54 billion.   J Dell reported results after the close of trading Thursday. Shares added 40= cents to $37.25 in 4 p.m. trading on the Nasdaq Stock Market.    ------------------------------  # Date: Thu, 11 Nov 2004 20:17:09 GMT % From: Rob Brown <mylastname@gmcl.com> ( Subject: Re: Problem to Partition a diskE Message-ID: <Pine.LNX.4.61.0411111312360.28837@localhost.localdomain>   * On Thu, 11 Nov 2004, Rudolf Wingert wrote:   > Hello, > C > I would like to patition a 146GB disk with the LDdriver into four E > partitions. The first problem (under OpenVMS 7.3-1 AXP) was, that I I > could not initialyze this disk with clustersize = 1. With clustersize = C > 4 there was no problem. I did also set the /INDEX to BEGIN. After @ > mounting I created a directory ([LD]) and tried to create fourI > contiguous files of the size = 71000000  with the LDdriver. But I could B > create only three of them. The last one did not have enaugh freeG > contiguous disk space. The DEFRAG shows, that the disk was fragmented I > into a few extends (four). I don't understand why. What's wrong with my " > initalyzation und file creation?  8 Do a dir/size=all [000000].  Does that explain anything?  @ When you initialize the disk, you will probably want to specify G /HEADERS and /INDEX to help maximize the amount of contiguous space on   the initialized volume.    - Rob      --    B Rob Brown                        b r o w n a t g m c l d o t c o mA G. Michaels Consulting Ltd.      (866)438-2101 (voice) toll free! 6 Edmonton                         (780)438-9343 (voice)5                                   (780)437-3367 (FAX) 2                                   http://gmcl.com/   ------------------------------  % Date: Thu, 11 Nov 2004 20:22:09 -0600 2 From: David J Dachtera <djesys.nospam@comcast.net>( Subject: Re: Problem to Partition a disk+ Message-ID: <41941E51.734D048D@comcast.net>    Rudolf Wingert wrote:  >  > Hello, > C > I would like to patition a 146GB disk with the LDdriver into four E > partitions. The first problem (under OpenVMS 7.3-1 AXP) was, that I I > could not initialyze this disk with clustersize = 1. With clustersize = C > 4 there was no problem. I did also set the /INDEX to BEGIN. After @ > mounting I created a directory ([LD]) and tried to create fourI > contiguous files of the size = 71000000  with the LDdriver. But I couldeB > create only three of them. The last one did not have enaugh freeG > contiguous disk space. The DEFRAG shows, that the disk was fragmented I > into a few extends (four). I don't understand why. What's wrong with mye" > initalyzation und file creation?  G Last time I played seriously with LD (V6.2), containers did not need tol8 be contiguous, they just couldn't have multiple headers.   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page:e" http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/i   ------------------------------  % Date: Thu, 11 Nov 2004 15:09:47 -0700e. From: "Michael D. Ober" <mdo.@.wakeassoc..com>* Subject: Re: V/A SMB client product source. Message-ID: <LqRkd.39$g1.3733@news.uswest.net>  D You have two options - Samba for VMS and HP Advanced Server for VMS.  
 Mike Ober.  8 "Rodman S. Regier" <rsr@hfx.andara.com> wrote in message2 news:gc3jo0d1h8c4nk1p61sgv2o79f38r52chk@4ax.com...6 > My organization is performing a zero-based review ofF > how we're performing file sharing access in a heterogenous operatingF > system environment.  Server nodes I need to support onsite that haveH > file repositories include Windows Server 2003 and OpenVMS/Alpha nodes. >nG > One of the options I am investigating is an SMB client product optionrG > for OpenVMS/Alpha  that would map a Windows Server 2003 file share asi= > something that looks like a disk drive on the OpenVMS node.t >v: > Could you point me to an "industrial grade" product that" > would deliver such a capability? >t9 > n.b. I have seen the first-level info on Vector NetworkE? >      LANutil32  product which appears to be Jun/2000 vintage.n, >      http://www.vector-networks.com/luvms/< >      I have concerns that it would not support current SMB; >      protocol password encryption defaults that have beenu7 >      added with the production release of Windows XP.  >- > Thanks >- >- >- >-B > ................................................................< >        Posted via TITANnews - Uncensored Newsgroups Access4 >              >>>> at http://www.TitanNews.com <<<<B > -=Every Newsgroup - Anonymous, UNCENSORED, BROADBAND Downloads=- >, >t   ------------------------------  % Date: Thu, 11 Nov 2004 14:28:22 -0700C. From: "Michael D. Ober" <mdo.@.wakeassoc..com>4 Subject: VMS NFS Client to Windows Services for Unix. Message-ID: <YPQkd.31$g1.3649@news.uswest.net>  L Has anyone gotten the VMS 7.3 NFS client to mount shares on a Windows ServerE running "Services for Unix 3.5"?  I am using the PCNFS server option.   , The VMS Command Line and response are below:   SYSTEM>TCPIP MOUNT DNFS0D /HOST="10.96.253.255"/PATH="/LOGS"/NOADF/STRUCTURE=5/UID=101/GID=100, %TCPIP$DNFSMOUNT-E-MOUNTFAIL, error mounting  _DNFS300:[SYS0.][000000]DNFS0.;1& -TCPIP-E-NOTAFILE, /LOGS is not a file  K I have verified that the UID/GID pair are correct on the Windows Server andr! also in the TCPIP PROXY database.y     Thanks,e
 Mike Ober.   ------------------------------  # Date: Fri, 12 Nov 2004 00:31:24 GMT 0 From: "Matt Muggeridge" <Matt.Muggeridge@hp.com>8 Subject: Re: VMS NFS Client to Windows Services for Unix= Message-ID: <wvTkd.32922$K7.28169@news-server.bigpond.net.au>e   Check your syntax...  9 The DNFS0 must end with a colon.  i.e. try the following:0         TCPIP MOUNT DNFS0:  etc etc   Matt.<     -- l= -------------------------------------------------------------n OpenVMS TCP/IP Engineering Enterprise Computing Group Hewlett-Packard Companyl Gold Coast, AUSTRALIAa= -------------------------------------------------------------a    : "Michael D. Ober" <mdo.@.wakeassoc..com> wrote in message ( news:YPQkd.31$g1.3649@news.uswest.net...H > Has anyone gotten the VMS 7.3 NFS client to mount shares on a Windows  > ServerG > running "Services for Unix 3.5"?  I am using the PCNFS server option.t >g. > The VMS Command Line and response are below: >i > SYSTEM>TCPIP MOUNT DNFS0F > /HOST="10.96.253.255"/PATH="/LOGS"/NOADF/STRUCTURE=5/UID=101/GID=100. > %TCPIP$DNFSMOUNT-E-MOUNTFAIL, error mounting" > _DNFS300:[SYS0.][000000]DNFS0.;1( > -TCPIP-E-NOTAFILE, /LOGS is not a file > J > I have verified that the UID/GID pair are correct on the Windows Server  > andi# > also in the TCPIP PROXY database.e >  >j	 > Thanks,N > Mike Ober. >  >    ------------------------------   End of INFO-VAX 2004.628 ************************