Bizarre path description

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








2















I have a checked out a project with file hierarchy:



REPO/project/src/multiple sub-directories here


I am reading some documentation and at a certain point I have to create a file config.properties and put it into 2 locations specified by that:



  1. project/src/config.properties

  2. project/../../config.properties

The point 1 is obvious but the 2 I didn't understand it? Is it wrong or it's me?










share|improve this question
























  • Is the documentation you're following available online?

    – roaima
    Oct 30 '15 at 23:51


















2















I have a checked out a project with file hierarchy:



REPO/project/src/multiple sub-directories here


I am reading some documentation and at a certain point I have to create a file config.properties and put it into 2 locations specified by that:



  1. project/src/config.properties

  2. project/../../config.properties

The point 1 is obvious but the 2 I didn't understand it? Is it wrong or it's me?










share|improve this question
























  • Is the documentation you're following available online?

    – roaima
    Oct 30 '15 at 23:51














2












2








2








I have a checked out a project with file hierarchy:



REPO/project/src/multiple sub-directories here


I am reading some documentation and at a certain point I have to create a file config.properties and put it into 2 locations specified by that:



  1. project/src/config.properties

  2. project/../../config.properties

The point 1 is obvious but the 2 I didn't understand it? Is it wrong or it's me?










share|improve this question
















I have a checked out a project with file hierarchy:



REPO/project/src/multiple sub-directories here


I am reading some documentation and at a certain point I have to create a file config.properties and put it into 2 locations specified by that:



  1. project/src/config.properties

  2. project/../../config.properties

The point 1 is obvious but the 2 I didn't understand it? Is it wrong or it's me?







filesystems path






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 18 at 4:03









Rui F Ribeiro

42.1k1484142




42.1k1484142










asked Oct 30 '15 at 23:40









Master MindMaster Mind

1134




1134












  • Is the documentation you're following available online?

    – roaima
    Oct 30 '15 at 23:51


















  • Is the documentation you're following available online?

    – roaima
    Oct 30 '15 at 23:51

















Is the documentation you're following available online?

– roaima
Oct 30 '15 at 23:51






Is the documentation you're following available online?

– roaima
Oct 30 '15 at 23:51











1 Answer
1






active

oldest

votes


















1














REPO/project/src/multiple sub-directories here


So these would be relative paths, not absolute paths (ie they don't start with a / to indicate the root)



project/src/config.properties


Would translate to REPO/project/src/config.properties



project/../../config.properties


would translate to REPO/config.properties because you change into project, then back two levels.



You can create symlinks to config.properties whereever you like, extra links won't mess anything up, and each one will use up one inode and no disk space.
If the real file is REPO/config.properties then this will symlink other files to that one.



ln -s REPO/config.properties REPO/project/src/





share|improve this answer























    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f239868%2fbizarre-path-description%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    REPO/project/src/multiple sub-directories here


    So these would be relative paths, not absolute paths (ie they don't start with a / to indicate the root)



    project/src/config.properties


    Would translate to REPO/project/src/config.properties



    project/../../config.properties


    would translate to REPO/config.properties because you change into project, then back two levels.



    You can create symlinks to config.properties whereever you like, extra links won't mess anything up, and each one will use up one inode and no disk space.
    If the real file is REPO/config.properties then this will symlink other files to that one.



    ln -s REPO/config.properties REPO/project/src/





    share|improve this answer



























      1














      REPO/project/src/multiple sub-directories here


      So these would be relative paths, not absolute paths (ie they don't start with a / to indicate the root)



      project/src/config.properties


      Would translate to REPO/project/src/config.properties



      project/../../config.properties


      would translate to REPO/config.properties because you change into project, then back two levels.



      You can create symlinks to config.properties whereever you like, extra links won't mess anything up, and each one will use up one inode and no disk space.
      If the real file is REPO/config.properties then this will symlink other files to that one.



      ln -s REPO/config.properties REPO/project/src/





      share|improve this answer

























        1












        1








        1







        REPO/project/src/multiple sub-directories here


        So these would be relative paths, not absolute paths (ie they don't start with a / to indicate the root)



        project/src/config.properties


        Would translate to REPO/project/src/config.properties



        project/../../config.properties


        would translate to REPO/config.properties because you change into project, then back two levels.



        You can create symlinks to config.properties whereever you like, extra links won't mess anything up, and each one will use up one inode and no disk space.
        If the real file is REPO/config.properties then this will symlink other files to that one.



        ln -s REPO/config.properties REPO/project/src/





        share|improve this answer













        REPO/project/src/multiple sub-directories here


        So these would be relative paths, not absolute paths (ie they don't start with a / to indicate the root)



        project/src/config.properties


        Would translate to REPO/project/src/config.properties



        project/../../config.properties


        would translate to REPO/config.properties because you change into project, then back two levels.



        You can create symlinks to config.properties whereever you like, extra links won't mess anything up, and each one will use up one inode and no disk space.
        If the real file is REPO/config.properties then this will symlink other files to that one.



        ln -s REPO/config.properties REPO/project/src/






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Oct 30 '15 at 23:52









        CriggieCriggie

        839513




        839513



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f239868%2fbizarre-path-description%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown






            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Displaying single band from multi-band raster using QGIS

            How many registers does an x86_64 CPU actually have?