Can't find `a2dissite` and `a2ensite` after building `apache2` from source on Mint17












0














After building apache2 http server from source (2.4.23)
I don't have the a2dissite and a2ensite commands.



Configure was:



./configure --with-included-apr --prefix=/usr/local/apache2


When I run:



whereis apache2



I get:



apache2: /etc/apache2 /usr/local/apache2


But which apache2 shows nothing, maybe there needs to be some symlinking to /usr/bin? http://localhost is working fine.



Version info for source:



/usr/local/apache2/bin/apachectl -v
Server version: Apache/2.4.23 (Unix)
Server built: Nov 1 2016 22:52:26



Linux version:



linux mint 17
3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64









share|improve this question
























  • Why 1) are you building it from source? 2) not making an effort to create a deb minimally compatible with Debian/Mint?
    – Rui F Ribeiro
    Nov 1 '16 at 22:30










  • @Zachary Brady - theres no such commands out there. Stephen Kitt gave excellent answer to this case.
    – d2048
    Nov 1 '16 at 22:45












  • @ Rui F Ribeiro 1)wanted to try out such a thing by myself. 2) this will be the next thing to try.
    – d2048
    Nov 1 '16 at 22:51
















0














After building apache2 http server from source (2.4.23)
I don't have the a2dissite and a2ensite commands.



Configure was:



./configure --with-included-apr --prefix=/usr/local/apache2


When I run:



whereis apache2



I get:



apache2: /etc/apache2 /usr/local/apache2


But which apache2 shows nothing, maybe there needs to be some symlinking to /usr/bin? http://localhost is working fine.



Version info for source:



/usr/local/apache2/bin/apachectl -v
Server version: Apache/2.4.23 (Unix)
Server built: Nov 1 2016 22:52:26



Linux version:



linux mint 17
3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64









share|improve this question
























  • Why 1) are you building it from source? 2) not making an effort to create a deb minimally compatible with Debian/Mint?
    – Rui F Ribeiro
    Nov 1 '16 at 22:30










  • @Zachary Brady - theres no such commands out there. Stephen Kitt gave excellent answer to this case.
    – d2048
    Nov 1 '16 at 22:45












  • @ Rui F Ribeiro 1)wanted to try out such a thing by myself. 2) this will be the next thing to try.
    – d2048
    Nov 1 '16 at 22:51














0












0








0







After building apache2 http server from source (2.4.23)
I don't have the a2dissite and a2ensite commands.



Configure was:



./configure --with-included-apr --prefix=/usr/local/apache2


When I run:



whereis apache2



I get:



apache2: /etc/apache2 /usr/local/apache2


But which apache2 shows nothing, maybe there needs to be some symlinking to /usr/bin? http://localhost is working fine.



Version info for source:



/usr/local/apache2/bin/apachectl -v
Server version: Apache/2.4.23 (Unix)
Server built: Nov 1 2016 22:52:26



Linux version:



linux mint 17
3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64









share|improve this question















After building apache2 http server from source (2.4.23)
I don't have the a2dissite and a2ensite commands.



Configure was:



./configure --with-included-apr --prefix=/usr/local/apache2


When I run:



whereis apache2



I get:



apache2: /etc/apache2 /usr/local/apache2


But which apache2 shows nothing, maybe there needs to be some symlinking to /usr/bin? http://localhost is working fine.



Version info for source:



/usr/local/apache2/bin/apachectl -v
Server version: Apache/2.4.23 (Unix)
Server built: Nov 1 2016 22:52:26



Linux version:



linux mint 17
3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64






linux linux-mint apache-httpd compiling






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 1 '16 at 21:53









agc

4,43811036




4,43811036










asked Nov 1 '16 at 21:18









d2048d2048

12




12












  • Why 1) are you building it from source? 2) not making an effort to create a deb minimally compatible with Debian/Mint?
    – Rui F Ribeiro
    Nov 1 '16 at 22:30










  • @Zachary Brady - theres no such commands out there. Stephen Kitt gave excellent answer to this case.
    – d2048
    Nov 1 '16 at 22:45












  • @ Rui F Ribeiro 1)wanted to try out such a thing by myself. 2) this will be the next thing to try.
    – d2048
    Nov 1 '16 at 22:51


















  • Why 1) are you building it from source? 2) not making an effort to create a deb minimally compatible with Debian/Mint?
    – Rui F Ribeiro
    Nov 1 '16 at 22:30










  • @Zachary Brady - theres no such commands out there. Stephen Kitt gave excellent answer to this case.
    – d2048
    Nov 1 '16 at 22:45












  • @ Rui F Ribeiro 1)wanted to try out such a thing by myself. 2) this will be the next thing to try.
    – d2048
    Nov 1 '16 at 22:51
















Why 1) are you building it from source? 2) not making an effort to create a deb minimally compatible with Debian/Mint?
– Rui F Ribeiro
Nov 1 '16 at 22:30




Why 1) are you building it from source? 2) not making an effort to create a deb minimally compatible with Debian/Mint?
– Rui F Ribeiro
Nov 1 '16 at 22:30












@Zachary Brady - theres no such commands out there. Stephen Kitt gave excellent answer to this case.
– d2048
Nov 1 '16 at 22:45






@Zachary Brady - theres no such commands out there. Stephen Kitt gave excellent answer to this case.
– d2048
Nov 1 '16 at 22:45














@ Rui F Ribeiro 1)wanted to try out such a thing by myself. 2) this will be the next thing to try.
– d2048
Nov 1 '16 at 22:51




@ Rui F Ribeiro 1)wanted to try out such a thing by myself. 2) this will be the next thing to try.
– d2048
Nov 1 '16 at 22:51










2 Answers
2






active

oldest

votes


















3














I'm guessing you built from the source available from the Apache Software Foundation. The a2en... scripts (and the supporting configuration) are Debian-specific; you'll find the source code in the corresponding Debian repository.



Your best bet to build the httpd server from source and still be able to use a2ensite etc. is to use the Debian source package:



sudo apt-get install devscripts dpkg-dev build-essential
sudo apt-get build-dep apache2
dget http://httpredir.debian.org/debian/pool/main/a/apache2/apache2_2.4.23-5.dsc
cd apache2-2.4.23
dpkg-buildpackage -us -uc


The first two commands install the packages necessary to build apache2; then dget downloads and extracts the source package, and dpkg-buildpackage builds it and produces a series of .deb packages you can install manually using dpkg as usual.



If the build-dep line doesn't work, the following is equivalent for apache2:



sudo apt-get install debhelper lsb-release libaprutil1-dev libapr1-dev libpcre3-dev zlib1g-dev libnghttp2-dev libssl-dev perl liblua5.2-dev libxml2-dev autotools-dev gawk dh-systemd





share|improve this answer























  • first command was end succesfully. after running second command sudo apt-get build-dep apache2 i've got Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to find a source package for apache2
    – d2048
    Nov 2 '16 at 12:27












  • @d2048 that means you don't have a deb-src entry in your sources.list (/etc/apt/sources.list and any .list file in /etc/apt/sources.list.d). I'll add a variant...
    – Stephen Kitt
    Nov 2 '16 at 12:54










  • @d2048 there, try the last apt-get install command instead of the apt-get build-dep one. (Then continue with dget etc.)
    – Stephen Kitt
    Nov 2 '16 at 12:58



















0














Don't symlink things to /usr/bin. That is an extremely bad idea and you should not do it.



Why? Because most of /usr, including /usr/bin, is reserved for the package manager. Anything that is not a package manager, including you, shouldn't be touching things in there.



/usr/local exists to provide a place to install locally-compiled software. Normally, you would provide /usr/local as a prefix, instead of /usr/local/apache2. (A prefix, by the way, is what's prefixed to the bin path, the library path, etc. So e.g. Apache's commandline tools would go in $PREFIX/bin, its libraries would go in $PREFIX/lib/apache2, etc.)



The solution to your problem is to add /usr/local/apache2/bin to the list of paths your shell uses to find binaries. This is usually referred to as $PATH or simply "your path", and can be changed with a command like:



export PATH="/usr/local/apache2/bin:$PATH"


You can put that in one of your shell's startup files to make it permanent.



That all being said, I suspect you still won't find a2ensite or a2dissite. If I recall correctly, both of these commands were added by Debian developers and then inherited from there by Mint. Therefore, they aren't included in upstream Apache source code. Stephen Kitt's excellent answer will tell you how to get these commands.






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%2f320414%2fcant-find-a2dissite-and-a2ensite-after-building-apache2-from-source-on-mi%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    3














    I'm guessing you built from the source available from the Apache Software Foundation. The a2en... scripts (and the supporting configuration) are Debian-specific; you'll find the source code in the corresponding Debian repository.



    Your best bet to build the httpd server from source and still be able to use a2ensite etc. is to use the Debian source package:



    sudo apt-get install devscripts dpkg-dev build-essential
    sudo apt-get build-dep apache2
    dget http://httpredir.debian.org/debian/pool/main/a/apache2/apache2_2.4.23-5.dsc
    cd apache2-2.4.23
    dpkg-buildpackage -us -uc


    The first two commands install the packages necessary to build apache2; then dget downloads and extracts the source package, and dpkg-buildpackage builds it and produces a series of .deb packages you can install manually using dpkg as usual.



    If the build-dep line doesn't work, the following is equivalent for apache2:



    sudo apt-get install debhelper lsb-release libaprutil1-dev libapr1-dev libpcre3-dev zlib1g-dev libnghttp2-dev libssl-dev perl liblua5.2-dev libxml2-dev autotools-dev gawk dh-systemd





    share|improve this answer























    • first command was end succesfully. after running second command sudo apt-get build-dep apache2 i've got Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to find a source package for apache2
      – d2048
      Nov 2 '16 at 12:27












    • @d2048 that means you don't have a deb-src entry in your sources.list (/etc/apt/sources.list and any .list file in /etc/apt/sources.list.d). I'll add a variant...
      – Stephen Kitt
      Nov 2 '16 at 12:54










    • @d2048 there, try the last apt-get install command instead of the apt-get build-dep one. (Then continue with dget etc.)
      – Stephen Kitt
      Nov 2 '16 at 12:58
















    3














    I'm guessing you built from the source available from the Apache Software Foundation. The a2en... scripts (and the supporting configuration) are Debian-specific; you'll find the source code in the corresponding Debian repository.



    Your best bet to build the httpd server from source and still be able to use a2ensite etc. is to use the Debian source package:



    sudo apt-get install devscripts dpkg-dev build-essential
    sudo apt-get build-dep apache2
    dget http://httpredir.debian.org/debian/pool/main/a/apache2/apache2_2.4.23-5.dsc
    cd apache2-2.4.23
    dpkg-buildpackage -us -uc


    The first two commands install the packages necessary to build apache2; then dget downloads and extracts the source package, and dpkg-buildpackage builds it and produces a series of .deb packages you can install manually using dpkg as usual.



    If the build-dep line doesn't work, the following is equivalent for apache2:



    sudo apt-get install debhelper lsb-release libaprutil1-dev libapr1-dev libpcre3-dev zlib1g-dev libnghttp2-dev libssl-dev perl liblua5.2-dev libxml2-dev autotools-dev gawk dh-systemd





    share|improve this answer























    • first command was end succesfully. after running second command sudo apt-get build-dep apache2 i've got Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to find a source package for apache2
      – d2048
      Nov 2 '16 at 12:27












    • @d2048 that means you don't have a deb-src entry in your sources.list (/etc/apt/sources.list and any .list file in /etc/apt/sources.list.d). I'll add a variant...
      – Stephen Kitt
      Nov 2 '16 at 12:54










    • @d2048 there, try the last apt-get install command instead of the apt-get build-dep one. (Then continue with dget etc.)
      – Stephen Kitt
      Nov 2 '16 at 12:58














    3












    3








    3






    I'm guessing you built from the source available from the Apache Software Foundation. The a2en... scripts (and the supporting configuration) are Debian-specific; you'll find the source code in the corresponding Debian repository.



    Your best bet to build the httpd server from source and still be able to use a2ensite etc. is to use the Debian source package:



    sudo apt-get install devscripts dpkg-dev build-essential
    sudo apt-get build-dep apache2
    dget http://httpredir.debian.org/debian/pool/main/a/apache2/apache2_2.4.23-5.dsc
    cd apache2-2.4.23
    dpkg-buildpackage -us -uc


    The first two commands install the packages necessary to build apache2; then dget downloads and extracts the source package, and dpkg-buildpackage builds it and produces a series of .deb packages you can install manually using dpkg as usual.



    If the build-dep line doesn't work, the following is equivalent for apache2:



    sudo apt-get install debhelper lsb-release libaprutil1-dev libapr1-dev libpcre3-dev zlib1g-dev libnghttp2-dev libssl-dev perl liblua5.2-dev libxml2-dev autotools-dev gawk dh-systemd





    share|improve this answer














    I'm guessing you built from the source available from the Apache Software Foundation. The a2en... scripts (and the supporting configuration) are Debian-specific; you'll find the source code in the corresponding Debian repository.



    Your best bet to build the httpd server from source and still be able to use a2ensite etc. is to use the Debian source package:



    sudo apt-get install devscripts dpkg-dev build-essential
    sudo apt-get build-dep apache2
    dget http://httpredir.debian.org/debian/pool/main/a/apache2/apache2_2.4.23-5.dsc
    cd apache2-2.4.23
    dpkg-buildpackage -us -uc


    The first two commands install the packages necessary to build apache2; then dget downloads and extracts the source package, and dpkg-buildpackage builds it and produces a series of .deb packages you can install manually using dpkg as usual.



    If the build-dep line doesn't work, the following is equivalent for apache2:



    sudo apt-get install debhelper lsb-release libaprutil1-dev libapr1-dev libpcre3-dev zlib1g-dev libnghttp2-dev libssl-dev perl liblua5.2-dev libxml2-dev autotools-dev gawk dh-systemd






    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited 27 mins ago

























    answered Nov 1 '16 at 22:27









    Stephen KittStephen Kitt

    165k24366446




    165k24366446












    • first command was end succesfully. after running second command sudo apt-get build-dep apache2 i've got Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to find a source package for apache2
      – d2048
      Nov 2 '16 at 12:27












    • @d2048 that means you don't have a deb-src entry in your sources.list (/etc/apt/sources.list and any .list file in /etc/apt/sources.list.d). I'll add a variant...
      – Stephen Kitt
      Nov 2 '16 at 12:54










    • @d2048 there, try the last apt-get install command instead of the apt-get build-dep one. (Then continue with dget etc.)
      – Stephen Kitt
      Nov 2 '16 at 12:58


















    • first command was end succesfully. after running second command sudo apt-get build-dep apache2 i've got Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to find a source package for apache2
      – d2048
      Nov 2 '16 at 12:27












    • @d2048 that means you don't have a deb-src entry in your sources.list (/etc/apt/sources.list and any .list file in /etc/apt/sources.list.d). I'll add a variant...
      – Stephen Kitt
      Nov 2 '16 at 12:54










    • @d2048 there, try the last apt-get install command instead of the apt-get build-dep one. (Then continue with dget etc.)
      – Stephen Kitt
      Nov 2 '16 at 12:58
















    first command was end succesfully. after running second command sudo apt-get build-dep apache2 i've got Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to find a source package for apache2
    – d2048
    Nov 2 '16 at 12:27






    first command was end succesfully. after running second command sudo apt-get build-dep apache2 i've got Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to find a source package for apache2
    – d2048
    Nov 2 '16 at 12:27














    @d2048 that means you don't have a deb-src entry in your sources.list (/etc/apt/sources.list and any .list file in /etc/apt/sources.list.d). I'll add a variant...
    – Stephen Kitt
    Nov 2 '16 at 12:54




    @d2048 that means you don't have a deb-src entry in your sources.list (/etc/apt/sources.list and any .list file in /etc/apt/sources.list.d). I'll add a variant...
    – Stephen Kitt
    Nov 2 '16 at 12:54












    @d2048 there, try the last apt-get install command instead of the apt-get build-dep one. (Then continue with dget etc.)
    – Stephen Kitt
    Nov 2 '16 at 12:58




    @d2048 there, try the last apt-get install command instead of the apt-get build-dep one. (Then continue with dget etc.)
    – Stephen Kitt
    Nov 2 '16 at 12:58













    0














    Don't symlink things to /usr/bin. That is an extremely bad idea and you should not do it.



    Why? Because most of /usr, including /usr/bin, is reserved for the package manager. Anything that is not a package manager, including you, shouldn't be touching things in there.



    /usr/local exists to provide a place to install locally-compiled software. Normally, you would provide /usr/local as a prefix, instead of /usr/local/apache2. (A prefix, by the way, is what's prefixed to the bin path, the library path, etc. So e.g. Apache's commandline tools would go in $PREFIX/bin, its libraries would go in $PREFIX/lib/apache2, etc.)



    The solution to your problem is to add /usr/local/apache2/bin to the list of paths your shell uses to find binaries. This is usually referred to as $PATH or simply "your path", and can be changed with a command like:



    export PATH="/usr/local/apache2/bin:$PATH"


    You can put that in one of your shell's startup files to make it permanent.



    That all being said, I suspect you still won't find a2ensite or a2dissite. If I recall correctly, both of these commands were added by Debian developers and then inherited from there by Mint. Therefore, they aren't included in upstream Apache source code. Stephen Kitt's excellent answer will tell you how to get these commands.






    share|improve this answer




























      0














      Don't symlink things to /usr/bin. That is an extremely bad idea and you should not do it.



      Why? Because most of /usr, including /usr/bin, is reserved for the package manager. Anything that is not a package manager, including you, shouldn't be touching things in there.



      /usr/local exists to provide a place to install locally-compiled software. Normally, you would provide /usr/local as a prefix, instead of /usr/local/apache2. (A prefix, by the way, is what's prefixed to the bin path, the library path, etc. So e.g. Apache's commandline tools would go in $PREFIX/bin, its libraries would go in $PREFIX/lib/apache2, etc.)



      The solution to your problem is to add /usr/local/apache2/bin to the list of paths your shell uses to find binaries. This is usually referred to as $PATH or simply "your path", and can be changed with a command like:



      export PATH="/usr/local/apache2/bin:$PATH"


      You can put that in one of your shell's startup files to make it permanent.



      That all being said, I suspect you still won't find a2ensite or a2dissite. If I recall correctly, both of these commands were added by Debian developers and then inherited from there by Mint. Therefore, they aren't included in upstream Apache source code. Stephen Kitt's excellent answer will tell you how to get these commands.






      share|improve this answer


























        0












        0








        0






        Don't symlink things to /usr/bin. That is an extremely bad idea and you should not do it.



        Why? Because most of /usr, including /usr/bin, is reserved for the package manager. Anything that is not a package manager, including you, shouldn't be touching things in there.



        /usr/local exists to provide a place to install locally-compiled software. Normally, you would provide /usr/local as a prefix, instead of /usr/local/apache2. (A prefix, by the way, is what's prefixed to the bin path, the library path, etc. So e.g. Apache's commandline tools would go in $PREFIX/bin, its libraries would go in $PREFIX/lib/apache2, etc.)



        The solution to your problem is to add /usr/local/apache2/bin to the list of paths your shell uses to find binaries. This is usually referred to as $PATH or simply "your path", and can be changed with a command like:



        export PATH="/usr/local/apache2/bin:$PATH"


        You can put that in one of your shell's startup files to make it permanent.



        That all being said, I suspect you still won't find a2ensite or a2dissite. If I recall correctly, both of these commands were added by Debian developers and then inherited from there by Mint. Therefore, they aren't included in upstream Apache source code. Stephen Kitt's excellent answer will tell you how to get these commands.






        share|improve this answer














        Don't symlink things to /usr/bin. That is an extremely bad idea and you should not do it.



        Why? Because most of /usr, including /usr/bin, is reserved for the package manager. Anything that is not a package manager, including you, shouldn't be touching things in there.



        /usr/local exists to provide a place to install locally-compiled software. Normally, you would provide /usr/local as a prefix, instead of /usr/local/apache2. (A prefix, by the way, is what's prefixed to the bin path, the library path, etc. So e.g. Apache's commandline tools would go in $PREFIX/bin, its libraries would go in $PREFIX/lib/apache2, etc.)



        The solution to your problem is to add /usr/local/apache2/bin to the list of paths your shell uses to find binaries. This is usually referred to as $PATH or simply "your path", and can be changed with a command like:



        export PATH="/usr/local/apache2/bin:$PATH"


        You can put that in one of your shell's startup files to make it permanent.



        That all being said, I suspect you still won't find a2ensite or a2dissite. If I recall correctly, both of these commands were added by Debian developers and then inherited from there by Mint. Therefore, they aren't included in upstream Apache source code. Stephen Kitt's excellent answer will tell you how to get these commands.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Apr 13 '17 at 12:36









        Community

        1




        1










        answered Nov 1 '16 at 22:28









        strugeestrugee

        8,1691254102




        8,1691254102






























            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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2f320414%2fcant-find-a2dissite-and-a2ensite-after-building-apache2-from-source-on-mi%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

            CARDNET

            Boot-repair Failure: Unable to locate package grub-common:i386

            濃尾地震