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: a07f3367d7,129433ab43bf5aef X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit X-Received: by 10.180.83.101 with SMTP id p5mr977425wiy.0.1359079703706; Thu, 24 Jan 2013 18:08:23 -0800 (PST) Path: i11ni18219wiw.0!nntp.google.com!feeder1.cambriumusenet.nl!82.197.223.103.MISMATCH!feeder3.cambriumusenet.nl!feed.tweaknews.nl!193.141.40.65.MISMATCH!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!news.bawue.net!storethat.news.telefonica.de!telefonica.de!weretis.net!feeder4.news.weretis.net!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail From: Brian Drummond Newsgroups: comp.lang.ada Subject: Re: cannot write to a file in Linux despite +rw permissions Date: Sat, 19 Jan 2013 10:11:41 +0000 (UTC) Organization: A noiseless patient Spider Message-ID: References: <1d536a59-c2e6-40d8-bf1e-fa7a0b4a923a@googlegroups.com> <9c80818c-77bf-489f-9648-7271e55f4ac7@googlegroups.com> Mime-Version: 1.0 Injection-Date: Sat, 19 Jan 2013 10:11:41 +0000 (UTC) Injection-Info: mx04.eternal-september.org; posting-host="da745e888d4a5182b5fda6212bbb0a63"; logging-data="24844"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+QxvaaYR+3nEOPnXIFiNzOtgXjJLaffkA=" User-Agent: Pan/0.139 (Sexual Chocolate; GIT bf56508 git://git.gnome.org/pan2) Cancel-Lock: sha1:CnO04SKIxUAN9qisDFxdp1ZjvZY= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Date: 2013-01-19T10:11:41+00:00 List-Id: On Fri, 18 Jan 2013 23:08:53 -0800, Ada novice wrote: > I realized that I was putting you all on the wrong track since I was > experimenting on a more complex Ada code that takes time to run than on > the very simple code that I posted here, which made you believe that it > could be a GNAT installation issue. My apologies for this. I was tempted > to believe that it was a file permissions issue! No apology needed. If "works here, mate" is just the poke you need to (try the trivial example and) look elsewhere, then it served its purpose. If there's a lesson it is that you could shorten the loop next time... - Brian