Re: Problematic interpretion of paths starting with double slashes

2018-06-13 Thread Sven Eden
> Gesendet: Mittwoch, 13. Juni 2018 um 10:09 Uhr > Von: "Corinna Vinschen" > On Jun 12 22:01, Achim Gratz wrote: > > Sven Eden writes: > > > Doing a simple stat on / if (and only if) the UNC lookup > > > fails, does not endanger anything. It wouldn&#x

Aw: Re: Re: Problematic interpretion of paths starting with double slashes

2018-06-13 Thread Sven Eden
> Gesendet: Dienstag, 12. Juni 2018 um 20:02 Uhr > Von: Lee > On 6/12/18, Sven Eden wrote: > > Good style is to guarantee, that > > not more than one slash is issued. > > Why don't you submit a patch to guarantee that not more than one slash > is issued? Alrea

Re: Problematic interpretion of paths starting with double slashes

2018-06-13 Thread Sven Eden
> Gesendet: Dienstag, 12. Juni 2018 um 19:56 Uhr > Von: "Eric Blake" > On 06/12/2018 08:14 AM, Sven Eden wrote: > > Good style is nice, but in my book, it is trumped by correct code. Yeah. Point taken. :-D > Hey, let's all assume good intent here. I did not

Aw: Re: Problematic interpretion of paths starting with double slashes

2018-06-13 Thread Sven Eden
> Gesendet: Dienstag, 12. Juni 2018 um 18:28 Uhr > Von: "Brian Inglis" > On 2018-06-12 07:14, Sven Eden wrote: > >> Gesendet: Dienstag, 12. Juni 2018 um 13:52 Uhr > >> Von: "Eric Blake" > >> Then fix your script to provide 3 slashes inst

Aw: Re: Problematic interpretion of paths starting with double slashes

2018-06-12 Thread Sven Eden
> Gesendet: Dienstag, 12. Juni 2018 um 13:52 Uhr > Von: "Eric Blake" > Then fix your script to provide 3 slashes instead of 2. Only 2 slashes > has the magic UNC behavior. It is not my script. *my* scripts are portable by all means. > That is, if you have a script that is concatenating: > > ${

Problematic interpretion of paths starting with double slashes

2018-06-12 Thread Sven Eden
Hello everybody,   I have a problem with a script that wants to copy a file, which has a variable paths build from various variables. The first variable is a possible prefix, the second an absolute path. If no prefix is needed, the first consists of just a slash. What I now see is the following: