Ubuntu 18.04 update-rc.d doesn't do the right thing












1















I have a newly installed 18.04 system and I am installing VirtualBox on it, with the autostart startup scripts.



The autostart startup scripts correctly list the VirtualBox kernel module as a dependency in the LSB section of the /etc/init.d/ scripts as follows:



/etc/init.d/virtualbox:



### BEGIN INIT INFO
# Provides: vboxdrv virtualbox
# Required-Start: $remote_fs $network
# Required-Stop: $remote_fs
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: VirtualBox Linux kernel module
### END INIT INFO


/etc/init.d/vboxautostart-service:



### BEGIN INIT INFO
# Provides: vboxautostart-service
# Required-Start: vboxdrv
# Required-Stop: vboxdrv
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Description: VirtualBox autostart service
### END INIT INFO


However, after I run;



sudo update-rc.d vboxautostart-service defaults


the /etc/rc*.d/ directories list vboxautostart-service as S01* and K01*. This causes the dependency between the two to not be honored, and my VirtualBox VMs do not get auto started because the kernel module is not loaded on startup.



For example, here is the dir listing of /etc/rc5.d:



S01acpid             S01dbus         S01saned
S01anacron S01gdm3 S01speech-dispatcher
S01apport S01grub-common S01spice-vdagent
S01avahi-daemon S01irqbalance S01ssh
S01bluetooth S01kerneloops S01unattended-upgrades
S01console-setup.sh S01ntp S01uuidd
S01cron S01plymouth S01vboxautostart-service
S01cups S01rsync S01virtualbox
S01cups-browsed S01rsyslog S01whoopsie


This works fine on 16.04. Here's the listing of /etc/rc5.d on 16.04:



README            S01rsyslog              S02dbus                   S03grub-common
S01apport S01unattended-upgrades S02irqbalance S03ondemand
S01lvm2-lvmetad S01uuidd S02mdadm S03plymouth
S01lvm2-lvmpolld S01virtualbox S02ntp S03rc.local
S01lxcfs S02acpid S02rsync
S01lxd S02atd S02ssh
S01open-vm-tools S02cron S02vboxautostart-service


Is this broken in 18.04?










share|improve this question





























    1















    I have a newly installed 18.04 system and I am installing VirtualBox on it, with the autostart startup scripts.



    The autostart startup scripts correctly list the VirtualBox kernel module as a dependency in the LSB section of the /etc/init.d/ scripts as follows:



    /etc/init.d/virtualbox:



    ### BEGIN INIT INFO
    # Provides: vboxdrv virtualbox
    # Required-Start: $remote_fs $network
    # Required-Stop: $remote_fs
    # Default-Start: 2 3 4 5
    # Default-Stop: 0 1 6
    # Short-Description: VirtualBox Linux kernel module
    ### END INIT INFO


    /etc/init.d/vboxautostart-service:



    ### BEGIN INIT INFO
    # Provides: vboxautostart-service
    # Required-Start: vboxdrv
    # Required-Stop: vboxdrv
    # Default-Start: 2 3 4 5
    # Default-Stop: 0 1 6
    # Description: VirtualBox autostart service
    ### END INIT INFO


    However, after I run;



    sudo update-rc.d vboxautostart-service defaults


    the /etc/rc*.d/ directories list vboxautostart-service as S01* and K01*. This causes the dependency between the two to not be honored, and my VirtualBox VMs do not get auto started because the kernel module is not loaded on startup.



    For example, here is the dir listing of /etc/rc5.d:



    S01acpid             S01dbus         S01saned
    S01anacron S01gdm3 S01speech-dispatcher
    S01apport S01grub-common S01spice-vdagent
    S01avahi-daemon S01irqbalance S01ssh
    S01bluetooth S01kerneloops S01unattended-upgrades
    S01console-setup.sh S01ntp S01uuidd
    S01cron S01plymouth S01vboxautostart-service
    S01cups S01rsync S01virtualbox
    S01cups-browsed S01rsyslog S01whoopsie


    This works fine on 16.04. Here's the listing of /etc/rc5.d on 16.04:



    README            S01rsyslog              S02dbus                   S03grub-common
    S01apport S01unattended-upgrades S02irqbalance S03ondemand
    S01lvm2-lvmetad S01uuidd S02mdadm S03plymouth
    S01lvm2-lvmpolld S01virtualbox S02ntp S03rc.local
    S01lxcfs S02acpid S02rsync
    S01lxd S02atd S02ssh
    S01open-vm-tools S02cron S02vboxautostart-service


    Is this broken in 18.04?










    share|improve this question



























      1












      1








      1








      I have a newly installed 18.04 system and I am installing VirtualBox on it, with the autostart startup scripts.



      The autostart startup scripts correctly list the VirtualBox kernel module as a dependency in the LSB section of the /etc/init.d/ scripts as follows:



      /etc/init.d/virtualbox:



      ### BEGIN INIT INFO
      # Provides: vboxdrv virtualbox
      # Required-Start: $remote_fs $network
      # Required-Stop: $remote_fs
      # Default-Start: 2 3 4 5
      # Default-Stop: 0 1 6
      # Short-Description: VirtualBox Linux kernel module
      ### END INIT INFO


      /etc/init.d/vboxautostart-service:



      ### BEGIN INIT INFO
      # Provides: vboxautostart-service
      # Required-Start: vboxdrv
      # Required-Stop: vboxdrv
      # Default-Start: 2 3 4 5
      # Default-Stop: 0 1 6
      # Description: VirtualBox autostart service
      ### END INIT INFO


      However, after I run;



      sudo update-rc.d vboxautostart-service defaults


      the /etc/rc*.d/ directories list vboxautostart-service as S01* and K01*. This causes the dependency between the two to not be honored, and my VirtualBox VMs do not get auto started because the kernel module is not loaded on startup.



      For example, here is the dir listing of /etc/rc5.d:



      S01acpid             S01dbus         S01saned
      S01anacron S01gdm3 S01speech-dispatcher
      S01apport S01grub-common S01spice-vdagent
      S01avahi-daemon S01irqbalance S01ssh
      S01bluetooth S01kerneloops S01unattended-upgrades
      S01console-setup.sh S01ntp S01uuidd
      S01cron S01plymouth S01vboxautostart-service
      S01cups S01rsync S01virtualbox
      S01cups-browsed S01rsyslog S01whoopsie


      This works fine on 16.04. Here's the listing of /etc/rc5.d on 16.04:



      README            S01rsyslog              S02dbus                   S03grub-common
      S01apport S01unattended-upgrades S02irqbalance S03ondemand
      S01lvm2-lvmetad S01uuidd S02mdadm S03plymouth
      S01lvm2-lvmpolld S01virtualbox S02ntp S03rc.local
      S01lxcfs S02acpid S02rsync
      S01lxd S02atd S02ssh
      S01open-vm-tools S02cron S02vboxautostart-service


      Is this broken in 18.04?










      share|improve this question
















      I have a newly installed 18.04 system and I am installing VirtualBox on it, with the autostart startup scripts.



      The autostart startup scripts correctly list the VirtualBox kernel module as a dependency in the LSB section of the /etc/init.d/ scripts as follows:



      /etc/init.d/virtualbox:



      ### BEGIN INIT INFO
      # Provides: vboxdrv virtualbox
      # Required-Start: $remote_fs $network
      # Required-Stop: $remote_fs
      # Default-Start: 2 3 4 5
      # Default-Stop: 0 1 6
      # Short-Description: VirtualBox Linux kernel module
      ### END INIT INFO


      /etc/init.d/vboxautostart-service:



      ### BEGIN INIT INFO
      # Provides: vboxautostart-service
      # Required-Start: vboxdrv
      # Required-Stop: vboxdrv
      # Default-Start: 2 3 4 5
      # Default-Stop: 0 1 6
      # Description: VirtualBox autostart service
      ### END INIT INFO


      However, after I run;



      sudo update-rc.d vboxautostart-service defaults


      the /etc/rc*.d/ directories list vboxautostart-service as S01* and K01*. This causes the dependency between the two to not be honored, and my VirtualBox VMs do not get auto started because the kernel module is not loaded on startup.



      For example, here is the dir listing of /etc/rc5.d:



      S01acpid             S01dbus         S01saned
      S01anacron S01gdm3 S01speech-dispatcher
      S01apport S01grub-common S01spice-vdagent
      S01avahi-daemon S01irqbalance S01ssh
      S01bluetooth S01kerneloops S01unattended-upgrades
      S01console-setup.sh S01ntp S01uuidd
      S01cron S01plymouth S01vboxautostart-service
      S01cups S01rsync S01virtualbox
      S01cups-browsed S01rsyslog S01whoopsie


      This works fine on 16.04. Here's the listing of /etc/rc5.d on 16.04:



      README            S01rsyslog              S02dbus                   S03grub-common
      S01apport S01unattended-upgrades S02irqbalance S03ondemand
      S01lvm2-lvmetad S01uuidd S02mdadm S03plymouth
      S01lvm2-lvmpolld S01virtualbox S02ntp S03rc.local
      S01lxcfs S02acpid S02rsync
      S01lxd S02atd S02ssh
      S01open-vm-tools S02cron S02vboxautostart-service


      Is this broken in 18.04?







      scripts virtualbox startup autostart






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 30 at 16:25







      George Kyriazis

















      asked Jan 29 at 23:47









      George KyriazisGeorge Kyriazis

      63




      63






















          0






          active

          oldest

          votes











          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%2f1113965%2fubuntu-18-04-update-rc-d-doesnt-do-the-right-thing%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          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%2f1113965%2fubuntu-18-04-update-rc-d-doesnt-do-the-right-thing%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

          Human spaceflight

          Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?

          張江高科駅