From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,9dabd984ea966de9 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news2.google.com!newsread.com!newsprint.newsread.com!63.218.45.11.MISMATCH!newshosting.com!nx02.iad01.newshosting.com!38.144.126.100.MISMATCH!feed5.newsreader.com!newsreader.com!border2.nntp.dca.giganews.com!nntp.giganews.com!wns14feed!worldnet.att.net!204.71.34.3!newsfeed.cwix.com!news.binc.net!kilgallen From: Kilgallen@SpamCop.net (Larry Kilgallen) Newsgroups: comp.lang.ada Subject: Re: GNAT on a multiboot computer Date: 29 Oct 2004 11:14:38 -0500 Organization: LJK Software Message-ID: References: <417DFD3C.6080209@stochastique.net> <417e16a7$0$30703$ba620e4c@news.skynet.be> <417f57d8$0$30704$ba620e4c@news.skynet.be> <549gd.17128$Qs6.1469677@news20.bellglobal.com> <1126782.ZbbeXJgdME@linux1.krischik.com> <41820f69$0$7073$ba620e4c@news.skynet.be> NNTP-Posting-Host: eisner.encompasserve.org X-Trace: grandcanyon.binc.net 1099066394 18324 192.135.80.34 (29 Oct 2004 16:13:14 GMT) X-Complaints-To: abuse@binc.net NNTP-Posting-Date: Fri, 29 Oct 2004 16:13:14 +0000 (UTC) Xref: g2news1.google.com comp.lang.ada:5881 Date: 2004-10-29T11:14:38-05:00 List-Id: In article <41820f69$0$7073$ba620e4c@news.skynet.be>, Adrien Plisson writes: > i dream of a system which don't have any f****** conventions as "c:", nor any > f****** weird locations as "Documents and Settings" or "/opt/usr/bin", and do > not need any installation, ala Macintosh 10 years ago (copy where you want, run). Some of this certainly pertains to elaborate OS mechanisms to which application developers choose to conform. On VMS, for example, copying a program to a particular location and then using the RUN command works fine. But... If the program uses a shareable image in concert with other programs, that shareable image either must be in SYS$SHARE or must have a logical name defined. If the program uses a separate message image in order to support internationalization, that message image must be in SYS$MESSAGE or must have a logical name defined. If the program documentation supports the DCL command HELP/MESSAGE an existing logical name must be modified by the system manager. If the program is to be invoked by its own native command like LJK/SECURITY SHOW ASSESSMENT rather than RUN, the SET COMMAND command must be used to establish that command. And of course any of those steps which will affect other users of the system must be done by someone with system management privilege. You can still do the "copy-run" approach or even RUN directly from the source location of the program, but life gets more complicated when multiuser environments are involved. In fact, for the best security no user should have the right to execute any program they provided, since they might be inappropriately trusting the source of that program !