INFO-VAX Tue, 25 Dec 2007 Volume 2007 : Issue 706 Contents: Re: OT: Merry Christmas to c.o.v. ! Re: Volume label. Re: Volume label. Re: Volume label. Re: Volume label. Re: Volume label. Re: ZKO to close Re: ZKO to close ---------------------------------------------------------------------- Date: Tue, 25 Dec 2007 10:42:45 +0000 (UTC) From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) Subject: Re: OT: Merry Christmas to c.o.v. ! Message-ID: In article <4770893A.DBDD6C96@spam.comcast.net>, David J Dachtera writes: > The "Santa Claus" character, as we in the U.S. know it, was the central > figure in an advertising campaign run by the Coca Cola company back > about a 100 years or so ago. Not quite 100, but almost. > It has since become part of Americana, > indeed, part of the "world" of Christmas, following onto Father > Christmas, the "real" Story of Saint Nicholas, and so on. Yes. However, contrary to popular belief, Coca-Cola did not INVENT this incarnation of Santa, although Coca-Cola did USE it and this use DID contribute to its popularity: http://www.snopes.com/cokelore/santa.asp > "Rudolph" > followed some time later, as I understand. Yes, and this was created ex nihilo: http://www.snopes.com/holidays/christmas/rudolph.asp The Santa character which Coca-Cola made popular was already well established (at least in the U.S.) a few decades previously. As are all similar figures in various countries, he was an amalgamation of various figures, traditions etc. ------------------------------ Date: Tue, 25 Dec 2007 10:34:51 +0000 (UTC) From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) Subject: Re: Volume label. Message-ID: In article <3f212454-ab83-4d30-8d8d-f3064dbce599@j64g2000hsj.googlegroups.com>, AEF writes: > Also, run a command like > > $ SHOW LOGICAL/FULL */TABLE=* > > and check out logical names like > > "LNM$STARTUP_TABLE" [exec,table] = "" [terminal] > > Since you can't reDEFINE "", I suppose this would support the saving- > CPU-cycles theory. Also, I think it's just a precaution against a user > or system mangler from redefining the device or logical name portions > of equivalence names of important logical names. > > So I think it's both: saving CPU cycles and preventing the define-a- > device-name-as-a-logical-name quick-and-dirty "fix" trick. OK, I agree, but I admit I don't see the point of defining LNM$STARTUP_TABLE to "". ------------------------------ Date: Tue, 25 Dec 2007 10:36:24 +0000 (UTC) From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) Subject: Re: Volume label. Message-ID: In article <477012e2$0$25359$c3e8da3@news.astraweb.com>, JF Mezei writes: > AEF wrote: > > > So I think it's both: saving CPU cycles and preventing the define-a- > > device-name-as-a-logical-name quick-and-dirty "fix" trick. > > consider the following: > > $DEFINE/qualifiers SYSUAF $11$DQA0:[shared]sysuaf.dat > > without a trans=terminal, someone could define a logical name $11$dqa0 > to point to another drive (or one they created with the LDdriver). True, but in this case they can't do any damage or, rather, if they can define the logical name so that it is dangerous, they have enough privileges to wreak havoc in other ways as well. ------------------------------ Date: Tue, 25 Dec 2007 05:05:43 -0800 (PST) From: FrankS Subject: Re: Volume label. Message-ID: On Dec 24, 3:12=A0pm, JF Mezei wrote: > consider the following: > > $DEFINE/qualifiers =A0SYSUAF $11$DQA0:[shared]sysuaf.dat > > without a trans=3Dterminal, someone could define a logical name $11$dqa0 > to point to another drive (or one they created with the LDdriver). In addition to the other comments about how a malicious user would need SYSNAM to really have an impact, and how /TRANS=3DTERMINAL doesn't necessarily stop iterative translation, this definition would be a sign of a bad systems manager. Using a physical device name like this is just bad style and can make transitioning to other disk interfaces a nightmare. Given the $MOUNT syntax of $ MOUNT /SYSTEM _$11$DQA0: volume_label logical_name then the worst-case reference to this drive should be either through the "logical_name" on the $MOUNT command line or the DISK$volume_label logical that gets created by OpenVMS. I'll give you the benefit of the doubt, though, that this was just an example from you and not something you really do on a production system. If a physical device name is really what one wants (despite all the valid reasons to avoid doing that), then the more appropriate syntax would be: $ DEFINE /qualifiers SYSUAF _$11$DQA0:[SHARED]SYSUAF.DAT That would preclude a redefinition from interfering with the system managers intention. I'll leave the "/qualifiers" open since that's how you show it. ------------------------------ Date: Tue, 25 Dec 2007 06:46:16 -0800 (PST) From: AEF Subject: Re: Volume label. Message-ID: <7db33f6a-f0c0-4c77-90a2-261c02187346@c49g2000hsc.googlegroups.com> On Dec 25, 5:34 am, hel...@astro.multiCLOTHESvax.de (Phillip Helbig--- remove CLOTHES to reply) wrote: > In article > <3f212454-ab83-4d30-8d8d-f3064dbce...@j64g2000hsj.googlegroups.com>, AEF > > > > writes: > > Also, run a command like > > > $ SHOW LOGICAL/FULL */TABLE=* > > > and check out logical names like > > > "LNM$STARTUP_TABLE" [exec,table] = "" [terminal] > > > Since you can't reDEFINE "", I suppose this would support the saving- > > CPU-cycles theory. Also, I think it's just a precaution against a user > > or system mangler from redefining the device or logical name portions > > of equivalence names of important logical names. > > > So I think it's both: saving CPU cycles and preventing the define-a- > > device-name-as-a-logical-name quick-and-dirty "fix" trick. > > OK, I agree, but I admit I don't see the point of defining > LNM$STARTUP_TABLE to "". Because that's how logical name tables work. Example: $ CREATE/NAME AEF $ SHOW LOG AEF/TABLE=*DIR*/FUL "AEF" [super,table] = "" [terminal] (LNM$PROCESS_DIRECTORY) $ DEFINE LNM EQV /TABLE=AEF $ SHOW LOG /FULL /TABLE=AEF (AEF) [super] [no protection information] "LNM" [super] = "EQV" $ Also, you can't explicitly define a logical name to be null. Being null apparently means it's really a logical name table: $ DEFINE NULL "" %SYSTEM-F-IVLOGNAM, invalid logical name AEF ------------------------------ Date: Tue, 25 Dec 2007 09:22:00 -0600 From: David J Dachtera Subject: Re: Volume label. Message-ID: <47712018.3963E831@spam.comcast.net> Phillip Helbig---remove CLOTHES to reply wrote: > > In article > <3f212454-ab83-4d30-8d8d-f3064dbce599@j64g2000hsj.googlegroups.com>, AEF > writes: > > > Also, run a command like > > > > $ SHOW LOGICAL/FULL */TABLE=* > > > > and check out logical names like > > > > "LNM$STARTUP_TABLE" [exec,table] = "" [terminal] > > > > Since you can't reDEFINE "", I suppose this would support the saving- > > CPU-cycles theory. Also, I think it's just a precaution against a user > > or system mangler from redefining the device or logical name portions > > of equivalence names of important logical names. > > > > So I think it's both: saving CPU cycles and preventing the define-a- > > device-name-as-a-logical-name quick-and-dirty "fix" trick. > > OK, I agree, but I admit I don't see the point of defining > LNM$STARTUP_TABLE to "". What, in your thoughts, would be an appropriate value, if not ""? (Hint: Note "[exec,table]".) David J Dachtera DJE Systems ------------------------------ Date: Tue, 25 Dec 2007 00:45:31 -0800 (PST) From: "ddp@electric-loft.org" Subject: Re: ZKO to close Message-ID: <88e0dbd6-1c60-4265-b87e-d2e7ad05155e@s12g2000prg.googlegroups.com> As far as I'm concerned, ZKO closed the day they replaced "digital softwa reengineering" with "customerswinwhenwedeliver". Oh, but for a KO turkey... Happy holidays everyone! ------------------------------ Date: Tue, 25 Dec 2007 00:45:44 -0800 (PST) From: "ddp@electric-loft.org" Subject: Re: ZKO to close Message-ID: <1a886d26-80c5-4b04-b399-a2a023a0a635@s19g2000prg.googlegroups.com> As far as I'm concerned, ZKO closed the day they replaced "digital softwa reengineering" with "customerswinwhenwedeliver". Oh, but for a KO turkey... Happy holidays everyone! ------------------------------ End of INFO-VAX 2007.706 ************************