Ubuntu slow to boot after dual boot












0















I just installed Kali Linux (on /dev/sda5) in dual boot with Ubuntu (on /dev/sda2). However, now that I have Kali, Ubuntu takes a few minutes to launch, whereas Kali takes a few seconds, and I would like the contrary. How can I do that ?



Edit



Here is my /etc/fstab in Ubuntu :



# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda2 during installation
UUID=7d4d2f18-146c-4d56-b5f3-0dc605eeb9e0 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=95B2-5AED /boot/efi vfat umask=0077 0 1
# /home was on /dev/sda3 during installation
UUID=69d6623e-0bcc-4cef-8b25-e46c98210d44 /home ext4 defaults 0 2
# swap was on /dev/sda4 during installation
UUID=97913f94-1989-4c8d-b2e0-010dfb10d613 none swap sw 0 0









share|improve this question

























  • Welcome to Ask Ubuntu. I have no idea, but I'd explore what you changed in installing Kali. Did you create the sda5 partition? or was it there before (primarily did you reformat it? it was accessed before in your file-system table causing Ubuntu to try & mount a now non-existing partition until it's reaches timeout as your description implies to me). We can't know what changes you made in the installation of Kali, but I'd looked at sda5 changes if I was in your position.

    – guiverc
    Jan 24 at 23:44













  • When I installed Kali, I had already created the sda5 partition and formated it in ext4. During the installation, I removed the formating of sda5 to have 30Gb of free space, and installed Kali on it.

    – Ul Tome
    Jan 25 at 8:56











  • My point was the formatting changed the UUID (or unique-ID of the partition which is created during format), and your Ubuntu is likely to look for & wait for the UUID of the old-partition, then eventually time-out.... ie. you need to change the UUID of your old partition, with that of the newly formatted partition. You've not amended it to reflect your new layout causing the timeouts... The first place I'd look is your file-system-table (/etc/fstab)...

    – guiverc
    Jan 25 at 8:59













  • I'm not sure I understood what you told me, but I added to my post the contents of my /etc/fstab, and I tried replacing the UUID of sda2 with the one of sda5, but it didn't help

    – Ul Tome
    Jan 25 at 10:50











  • Don't just replace or change UUIDs without checking that the UUID's match your partition UUID's. If you sudo blkid |grep UUID you'll get a list of UUID's found on your system, use these [results] to check the UUIDs mentioned in your fstab are correct (I cannot as I don't know what's on your system). I don't see sda5 mentioned in comments (lines which have a # at the start are comments or documentation) but I'd still check them all. Installations (ie. kali) often re-format swap; so you may have found this has changed, and may be your problem.

    – guiverc
    Jan 25 at 11:05
















0















I just installed Kali Linux (on /dev/sda5) in dual boot with Ubuntu (on /dev/sda2). However, now that I have Kali, Ubuntu takes a few minutes to launch, whereas Kali takes a few seconds, and I would like the contrary. How can I do that ?



Edit



Here is my /etc/fstab in Ubuntu :



# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda2 during installation
UUID=7d4d2f18-146c-4d56-b5f3-0dc605eeb9e0 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=95B2-5AED /boot/efi vfat umask=0077 0 1
# /home was on /dev/sda3 during installation
UUID=69d6623e-0bcc-4cef-8b25-e46c98210d44 /home ext4 defaults 0 2
# swap was on /dev/sda4 during installation
UUID=97913f94-1989-4c8d-b2e0-010dfb10d613 none swap sw 0 0









share|improve this question

























  • Welcome to Ask Ubuntu. I have no idea, but I'd explore what you changed in installing Kali. Did you create the sda5 partition? or was it there before (primarily did you reformat it? it was accessed before in your file-system table causing Ubuntu to try & mount a now non-existing partition until it's reaches timeout as your description implies to me). We can't know what changes you made in the installation of Kali, but I'd looked at sda5 changes if I was in your position.

    – guiverc
    Jan 24 at 23:44













  • When I installed Kali, I had already created the sda5 partition and formated it in ext4. During the installation, I removed the formating of sda5 to have 30Gb of free space, and installed Kali on it.

    – Ul Tome
    Jan 25 at 8:56











  • My point was the formatting changed the UUID (or unique-ID of the partition which is created during format), and your Ubuntu is likely to look for & wait for the UUID of the old-partition, then eventually time-out.... ie. you need to change the UUID of your old partition, with that of the newly formatted partition. You've not amended it to reflect your new layout causing the timeouts... The first place I'd look is your file-system-table (/etc/fstab)...

    – guiverc
    Jan 25 at 8:59













  • I'm not sure I understood what you told me, but I added to my post the contents of my /etc/fstab, and I tried replacing the UUID of sda2 with the one of sda5, but it didn't help

    – Ul Tome
    Jan 25 at 10:50











  • Don't just replace or change UUIDs without checking that the UUID's match your partition UUID's. If you sudo blkid |grep UUID you'll get a list of UUID's found on your system, use these [results] to check the UUIDs mentioned in your fstab are correct (I cannot as I don't know what's on your system). I don't see sda5 mentioned in comments (lines which have a # at the start are comments or documentation) but I'd still check them all. Installations (ie. kali) often re-format swap; so you may have found this has changed, and may be your problem.

    – guiverc
    Jan 25 at 11:05














0












0








0








I just installed Kali Linux (on /dev/sda5) in dual boot with Ubuntu (on /dev/sda2). However, now that I have Kali, Ubuntu takes a few minutes to launch, whereas Kali takes a few seconds, and I would like the contrary. How can I do that ?



Edit



Here is my /etc/fstab in Ubuntu :



# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda2 during installation
UUID=7d4d2f18-146c-4d56-b5f3-0dc605eeb9e0 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=95B2-5AED /boot/efi vfat umask=0077 0 1
# /home was on /dev/sda3 during installation
UUID=69d6623e-0bcc-4cef-8b25-e46c98210d44 /home ext4 defaults 0 2
# swap was on /dev/sda4 during installation
UUID=97913f94-1989-4c8d-b2e0-010dfb10d613 none swap sw 0 0









share|improve this question
















I just installed Kali Linux (on /dev/sda5) in dual boot with Ubuntu (on /dev/sda2). However, now that I have Kali, Ubuntu takes a few minutes to launch, whereas Kali takes a few seconds, and I would like the contrary. How can I do that ?



Edit



Here is my /etc/fstab in Ubuntu :



# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda2 during installation
UUID=7d4d2f18-146c-4d56-b5f3-0dc605eeb9e0 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=95B2-5AED /boot/efi vfat umask=0077 0 1
# /home was on /dev/sda3 during installation
UUID=69d6623e-0bcc-4cef-8b25-e46c98210d44 /home ext4 defaults 0 2
# swap was on /dev/sda4 during installation
UUID=97913f94-1989-4c8d-b2e0-010dfb10d613 none swap sw 0 0






boot dual-boot






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 25 at 10:29







Ul Tome

















asked Jan 24 at 21:33









Ul TomeUl Tome

32




32













  • Welcome to Ask Ubuntu. I have no idea, but I'd explore what you changed in installing Kali. Did you create the sda5 partition? or was it there before (primarily did you reformat it? it was accessed before in your file-system table causing Ubuntu to try & mount a now non-existing partition until it's reaches timeout as your description implies to me). We can't know what changes you made in the installation of Kali, but I'd looked at sda5 changes if I was in your position.

    – guiverc
    Jan 24 at 23:44













  • When I installed Kali, I had already created the sda5 partition and formated it in ext4. During the installation, I removed the formating of sda5 to have 30Gb of free space, and installed Kali on it.

    – Ul Tome
    Jan 25 at 8:56











  • My point was the formatting changed the UUID (or unique-ID of the partition which is created during format), and your Ubuntu is likely to look for & wait for the UUID of the old-partition, then eventually time-out.... ie. you need to change the UUID of your old partition, with that of the newly formatted partition. You've not amended it to reflect your new layout causing the timeouts... The first place I'd look is your file-system-table (/etc/fstab)...

    – guiverc
    Jan 25 at 8:59













  • I'm not sure I understood what you told me, but I added to my post the contents of my /etc/fstab, and I tried replacing the UUID of sda2 with the one of sda5, but it didn't help

    – Ul Tome
    Jan 25 at 10:50











  • Don't just replace or change UUIDs without checking that the UUID's match your partition UUID's. If you sudo blkid |grep UUID you'll get a list of UUID's found on your system, use these [results] to check the UUIDs mentioned in your fstab are correct (I cannot as I don't know what's on your system). I don't see sda5 mentioned in comments (lines which have a # at the start are comments or documentation) but I'd still check them all. Installations (ie. kali) often re-format swap; so you may have found this has changed, and may be your problem.

    – guiverc
    Jan 25 at 11:05



















  • Welcome to Ask Ubuntu. I have no idea, but I'd explore what you changed in installing Kali. Did you create the sda5 partition? or was it there before (primarily did you reformat it? it was accessed before in your file-system table causing Ubuntu to try & mount a now non-existing partition until it's reaches timeout as your description implies to me). We can't know what changes you made in the installation of Kali, but I'd looked at sda5 changes if I was in your position.

    – guiverc
    Jan 24 at 23:44













  • When I installed Kali, I had already created the sda5 partition and formated it in ext4. During the installation, I removed the formating of sda5 to have 30Gb of free space, and installed Kali on it.

    – Ul Tome
    Jan 25 at 8:56











  • My point was the formatting changed the UUID (or unique-ID of the partition which is created during format), and your Ubuntu is likely to look for & wait for the UUID of the old-partition, then eventually time-out.... ie. you need to change the UUID of your old partition, with that of the newly formatted partition. You've not amended it to reflect your new layout causing the timeouts... The first place I'd look is your file-system-table (/etc/fstab)...

    – guiverc
    Jan 25 at 8:59













  • I'm not sure I understood what you told me, but I added to my post the contents of my /etc/fstab, and I tried replacing the UUID of sda2 with the one of sda5, but it didn't help

    – Ul Tome
    Jan 25 at 10:50











  • Don't just replace or change UUIDs without checking that the UUID's match your partition UUID's. If you sudo blkid |grep UUID you'll get a list of UUID's found on your system, use these [results] to check the UUIDs mentioned in your fstab are correct (I cannot as I don't know what's on your system). I don't see sda5 mentioned in comments (lines which have a # at the start are comments or documentation) but I'd still check them all. Installations (ie. kali) often re-format swap; so you may have found this has changed, and may be your problem.

    – guiverc
    Jan 25 at 11:05

















Welcome to Ask Ubuntu. I have no idea, but I'd explore what you changed in installing Kali. Did you create the sda5 partition? or was it there before (primarily did you reformat it? it was accessed before in your file-system table causing Ubuntu to try & mount a now non-existing partition until it's reaches timeout as your description implies to me). We can't know what changes you made in the installation of Kali, but I'd looked at sda5 changes if I was in your position.

– guiverc
Jan 24 at 23:44







Welcome to Ask Ubuntu. I have no idea, but I'd explore what you changed in installing Kali. Did you create the sda5 partition? or was it there before (primarily did you reformat it? it was accessed before in your file-system table causing Ubuntu to try & mount a now non-existing partition until it's reaches timeout as your description implies to me). We can't know what changes you made in the installation of Kali, but I'd looked at sda5 changes if I was in your position.

– guiverc
Jan 24 at 23:44















When I installed Kali, I had already created the sda5 partition and formated it in ext4. During the installation, I removed the formating of sda5 to have 30Gb of free space, and installed Kali on it.

– Ul Tome
Jan 25 at 8:56





When I installed Kali, I had already created the sda5 partition and formated it in ext4. During the installation, I removed the formating of sda5 to have 30Gb of free space, and installed Kali on it.

– Ul Tome
Jan 25 at 8:56













My point was the formatting changed the UUID (or unique-ID of the partition which is created during format), and your Ubuntu is likely to look for & wait for the UUID of the old-partition, then eventually time-out.... ie. you need to change the UUID of your old partition, with that of the newly formatted partition. You've not amended it to reflect your new layout causing the timeouts... The first place I'd look is your file-system-table (/etc/fstab)...

– guiverc
Jan 25 at 8:59







My point was the formatting changed the UUID (or unique-ID of the partition which is created during format), and your Ubuntu is likely to look for & wait for the UUID of the old-partition, then eventually time-out.... ie. you need to change the UUID of your old partition, with that of the newly formatted partition. You've not amended it to reflect your new layout causing the timeouts... The first place I'd look is your file-system-table (/etc/fstab)...

– guiverc
Jan 25 at 8:59















I'm not sure I understood what you told me, but I added to my post the contents of my /etc/fstab, and I tried replacing the UUID of sda2 with the one of sda5, but it didn't help

– Ul Tome
Jan 25 at 10:50





I'm not sure I understood what you told me, but I added to my post the contents of my /etc/fstab, and I tried replacing the UUID of sda2 with the one of sda5, but it didn't help

– Ul Tome
Jan 25 at 10:50













Don't just replace or change UUIDs without checking that the UUID's match your partition UUID's. If you sudo blkid |grep UUID you'll get a list of UUID's found on your system, use these [results] to check the UUIDs mentioned in your fstab are correct (I cannot as I don't know what's on your system). I don't see sda5 mentioned in comments (lines which have a # at the start are comments or documentation) but I'd still check them all. Installations (ie. kali) often re-format swap; so you may have found this has changed, and may be your problem.

– guiverc
Jan 25 at 11:05





Don't just replace or change UUIDs without checking that the UUID's match your partition UUID's. If you sudo blkid |grep UUID you'll get a list of UUID's found on your system, use these [results] to check the UUIDs mentioned in your fstab are correct (I cannot as I don't know what's on your system). I don't see sda5 mentioned in comments (lines which have a # at the start are comments or documentation) but I'd still check them all. Installations (ie. kali) often re-format swap; so you may have found this has changed, and may be your problem.

– guiverc
Jan 25 at 11:05










1 Answer
1






active

oldest

votes


















1














Welcome to Ask Ubuntu.



I'd suggest exploring what you changed in installing Kali. Did you create the sda5 partition? or was it there before (primarily did you reformat it? it was accessed before in your file-system table causing Ubuntu to try & mount a now non-existing partition until it's reaches timeout as your description implies to me). We can't know what changes you made in the installation of Kali, but I'd look at 'sda5' changes if I was in your position.



If you re-formatted 'sda5' you'll have changed the UUID (or unique-ID of the partition; created during format), and your Ubuntu is likely looking and waiting for the UUID of the old-partition to appear, then eventually time-out.... ie. you need to change the UUID of your old partition, to that of the newly formatted partition. You've not amended it to reflect your new layout causing the timeouts... The first place I'd look is your file-system-table (/etc/fstab)..



Don't just replace or change UUIDs without checking that the UUID's match your partition UUID's. If you sudo blkid |grep UUID you'll get a list of UUID's found on your system, use these [results] to check the UUIDs mentioned in your fstab are correct. I don't see sda5 mentioned in comments (lines which have a # at the start are comments or documentation) but I'd still check them all. Installations (ie. kali) often re-format swap; so you may have found this has changed, and this may be your issue causing slow boots.



A rebuild of initramfs is your next step; I think it has UUID's built into it (update-initramfs). If boots are still slow, next i would probably rebuild grub (update-grub but this usually uses PARTUUID, but is quick and simple to re-create).



(this answer is just copied/pasted comments with minor editing)






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    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: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    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%2faskubuntu.com%2fquestions%2f1112630%2fubuntu-slow-to-boot-after-dual-boot%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














    Welcome to Ask Ubuntu.



    I'd suggest exploring what you changed in installing Kali. Did you create the sda5 partition? or was it there before (primarily did you reformat it? it was accessed before in your file-system table causing Ubuntu to try & mount a now non-existing partition until it's reaches timeout as your description implies to me). We can't know what changes you made in the installation of Kali, but I'd look at 'sda5' changes if I was in your position.



    If you re-formatted 'sda5' you'll have changed the UUID (or unique-ID of the partition; created during format), and your Ubuntu is likely looking and waiting for the UUID of the old-partition to appear, then eventually time-out.... ie. you need to change the UUID of your old partition, to that of the newly formatted partition. You've not amended it to reflect your new layout causing the timeouts... The first place I'd look is your file-system-table (/etc/fstab)..



    Don't just replace or change UUIDs without checking that the UUID's match your partition UUID's. If you sudo blkid |grep UUID you'll get a list of UUID's found on your system, use these [results] to check the UUIDs mentioned in your fstab are correct. I don't see sda5 mentioned in comments (lines which have a # at the start are comments or documentation) but I'd still check them all. Installations (ie. kali) often re-format swap; so you may have found this has changed, and this may be your issue causing slow boots.



    A rebuild of initramfs is your next step; I think it has UUID's built into it (update-initramfs). If boots are still slow, next i would probably rebuild grub (update-grub but this usually uses PARTUUID, but is quick and simple to re-create).



    (this answer is just copied/pasted comments with minor editing)






    share|improve this answer




























      1














      Welcome to Ask Ubuntu.



      I'd suggest exploring what you changed in installing Kali. Did you create the sda5 partition? or was it there before (primarily did you reformat it? it was accessed before in your file-system table causing Ubuntu to try & mount a now non-existing partition until it's reaches timeout as your description implies to me). We can't know what changes you made in the installation of Kali, but I'd look at 'sda5' changes if I was in your position.



      If you re-formatted 'sda5' you'll have changed the UUID (or unique-ID of the partition; created during format), and your Ubuntu is likely looking and waiting for the UUID of the old-partition to appear, then eventually time-out.... ie. you need to change the UUID of your old partition, to that of the newly formatted partition. You've not amended it to reflect your new layout causing the timeouts... The first place I'd look is your file-system-table (/etc/fstab)..



      Don't just replace or change UUIDs without checking that the UUID's match your partition UUID's. If you sudo blkid |grep UUID you'll get a list of UUID's found on your system, use these [results] to check the UUIDs mentioned in your fstab are correct. I don't see sda5 mentioned in comments (lines which have a # at the start are comments or documentation) but I'd still check them all. Installations (ie. kali) often re-format swap; so you may have found this has changed, and this may be your issue causing slow boots.



      A rebuild of initramfs is your next step; I think it has UUID's built into it (update-initramfs). If boots are still slow, next i would probably rebuild grub (update-grub but this usually uses PARTUUID, but is quick and simple to re-create).



      (this answer is just copied/pasted comments with minor editing)






      share|improve this answer


























        1












        1








        1







        Welcome to Ask Ubuntu.



        I'd suggest exploring what you changed in installing Kali. Did you create the sda5 partition? or was it there before (primarily did you reformat it? it was accessed before in your file-system table causing Ubuntu to try & mount a now non-existing partition until it's reaches timeout as your description implies to me). We can't know what changes you made in the installation of Kali, but I'd look at 'sda5' changes if I was in your position.



        If you re-formatted 'sda5' you'll have changed the UUID (or unique-ID of the partition; created during format), and your Ubuntu is likely looking and waiting for the UUID of the old-partition to appear, then eventually time-out.... ie. you need to change the UUID of your old partition, to that of the newly formatted partition. You've not amended it to reflect your new layout causing the timeouts... The first place I'd look is your file-system-table (/etc/fstab)..



        Don't just replace or change UUIDs without checking that the UUID's match your partition UUID's. If you sudo blkid |grep UUID you'll get a list of UUID's found on your system, use these [results] to check the UUIDs mentioned in your fstab are correct. I don't see sda5 mentioned in comments (lines which have a # at the start are comments or documentation) but I'd still check them all. Installations (ie. kali) often re-format swap; so you may have found this has changed, and this may be your issue causing slow boots.



        A rebuild of initramfs is your next step; I think it has UUID's built into it (update-initramfs). If boots are still slow, next i would probably rebuild grub (update-grub but this usually uses PARTUUID, but is quick and simple to re-create).



        (this answer is just copied/pasted comments with minor editing)






        share|improve this answer













        Welcome to Ask Ubuntu.



        I'd suggest exploring what you changed in installing Kali. Did you create the sda5 partition? or was it there before (primarily did you reformat it? it was accessed before in your file-system table causing Ubuntu to try & mount a now non-existing partition until it's reaches timeout as your description implies to me). We can't know what changes you made in the installation of Kali, but I'd look at 'sda5' changes if I was in your position.



        If you re-formatted 'sda5' you'll have changed the UUID (or unique-ID of the partition; created during format), and your Ubuntu is likely looking and waiting for the UUID of the old-partition to appear, then eventually time-out.... ie. you need to change the UUID of your old partition, to that of the newly formatted partition. You've not amended it to reflect your new layout causing the timeouts... The first place I'd look is your file-system-table (/etc/fstab)..



        Don't just replace or change UUIDs without checking that the UUID's match your partition UUID's. If you sudo blkid |grep UUID you'll get a list of UUID's found on your system, use these [results] to check the UUIDs mentioned in your fstab are correct. I don't see sda5 mentioned in comments (lines which have a # at the start are comments or documentation) but I'd still check them all. Installations (ie. kali) often re-format swap; so you may have found this has changed, and this may be your issue causing slow boots.



        A rebuild of initramfs is your next step; I think it has UUID's built into it (update-initramfs). If boots are still slow, next i would probably rebuild grub (update-grub but this usually uses PARTUUID, but is quick and simple to re-create).



        (this answer is just copied/pasted comments with minor editing)







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 26 at 21:19









        guivercguiverc

        4,57721522




        4,57721522






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • 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%2faskubuntu.com%2fquestions%2f1112630%2fubuntu-slow-to-boot-after-dual-boot%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 make a Squid Proxy server?

            Is this a new Fibonacci Identity?

            19世紀