Announcement

Collapse
No announcement yet.

default runlevel problem

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    default runlevel problem

    First of all, i've looked everywhere for the answer to this and tried all of them;

    How do I make karmic boot to runlevel 3 instead of runlevel 2 at boot?
    As I understand it Karmic uses upstart; but I do not have an /etc/event.d/ directory!
    I've also tried making a inittab in etc/ as per previous Kubu distro's.
    modifying the boot/init/grub file or the 40_session file didn't work either.

    Please help as this should be easy!!

    #2
    Re: default runlevel problem

    Ubuntu Set Default Runlevel /etc/inittab
    Windows no longer obstructs my view.
    Using Kubuntu Linux since March 23, 2007.
    "It is a capital mistake to theorize before one has data." - Sherlock Holmes

    Comment


      #3
      Re: default runlevel problem

      Originally posted by Snowhog
      As stated above, I don't have an etc/event.d/ directory!

      Comment


        #4
        Re: default runlevel problem

        Originally posted by Snowhog
        That's a bit outdated (there's no /etc/event.d anymore).

        The file to edit on karmic is:
        /etc/init/rc-sysinit.conf
        (Edit the DEFAULT_RUNLEVEL variable)

        you can also create a /etc/inittab file or use kernel boot option to choose the runlevel, /etc/init/rc-sysinit.conf will read and use those if set

        Comment


          #5
          Re: default runlevel problem

          Originally posted by kubicle
          That's a bit outdated (there's no /etc/event.d anymore).
          "..anymore)." Still exists in Jaunty, but understand.
          Windows no longer obstructs my view.
          Using Kubuntu Linux since March 23, 2007.
          "It is a capital mistake to theorize before one has data." - Sherlock Holmes

          Comment


            #6
            Re: default runlevel problem

            Ok,

            I'd already set DEFAULT_RUNLEVEL=3 in /etc/init/rc-sysinit.conf

            but after your suggestion went back and checked; noticed a script to check for inittab within this file. Script checks for inittab and looks for DEFAULT_RUNLEVEL. so I changed my entry in inittab from id:3:initdefault: to DEFAULT_RUNLEVEL=3 and ...........no joy! still boots to kdm!

            also, entering grub on startup and editing to add 3 works - boots to RL3 ok. As this is using grub2 I can't simply edit menu.lst anymore. how do I make this permanent?

            Comment


              #7
              Re: default runlevel problem

              Originally posted by Muttley
              I'd already set DEFAULT_RUNLEVEL=3 in /etc/init/rc-sysinit.conf

              but after your suggestion went back and checked; noticed a script to check for inittab within this file. Script checks for inittab and looks for DEFAULT_RUNLEVEL. so I changed my entry in inittab from id:3:initdefault: to DEFAULT_RUNLEVEL=3 and ...........no joy! still boots to kdm!
              And have you prevented kdm from loading on runlevel 3?
              Try editing /etc/init/kdm.conf, and add:
              Code:
              and runlevel [!3]
              to the "start on ()" block

              also, entering grub on startup and editing to add 3 works - boots to RL3 ok. As this is using grub2 I can't simply edit menu.lst anymore. how do I make this permanent?
              You can set default options in /etc/default/grub (GRUB_CMDLINE_LINUX_DEFAULT) in GRUB2 (need to run 'sudo update-grub' afterwards)

              Comment


                #8
                Re: default runlevel problem

                Originally posted by kubicle

                And have you prevented kdm from loading on runlevel 3?
                Try editing /etc/init/kdm.conf, and add:
                Code:
                and runlevel [!3]
                to the "start on ()" block
                Your a star!! stupid of me! I should have checked runlevel 'who -r' shows run-level 3!
                Thanks for your time and expertise!

                Comment

                Working...
                X