antiX19core: which file to edit to set the default kernel?

Forum Forums General Software antiX19core: which file to edit to set the default kernel?

  • This topic has 4 replies, 3 voices, and was last updated Dec 12-11:32 pm by mikey777.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #30524
    Member
    mikey777

      I’m having a go at building a system up from antix19core.
      I’m using Dolphin’s 2014 youtube videos as a guide.

      In one of the 2014 videos, Dolphin edited the /boot/grub/menu.lst file,
      using the nano text editor, to set the default kernel.

      However, I can’t find /boot/grub/menu.lst in antiX19 32-bit.
      Has this file name changed since 2014, or am I looking in the
      wrong place?

      Many thanks in advance for your help.

      • This topic was modified 4 years, 7 months ago by mikey777.

      ▪ 32-bit antix19.4-core (SysV init)+LXDE legacy install on :
      - (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
      ▪ 64-bit antix21-base (SysV init)+LXDE legacy install on:
      - (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Intel Mobile 4 Series, integrated graphics
      - (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. SiS Graphics

      #30526
      Anonymous

        This file was responsible for the Grub Legacy (Grub1).

        antiX has been working with Grub2 for a long time now.
        Responsible for this is the file (/etc/default/grub)

        #30537
        Member
        mikey777

          Many thanks for pointing this out male.
          I’m afraid my efforts to make a minimal build from antix19-core failed, as Dolphin’s video on how
          to do this is now 5 years old and sometimes it’s not always clear what the updated packages I should
          use in the build are. I’ve returned to antiX19-full …

          ▪ 32-bit antix19.4-core (SysV init)+LXDE legacy install on :
          - (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
          ▪ 64-bit antix21-base (SysV init)+LXDE legacy install on:
          - (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Intel Mobile 4 Series, integrated graphics
          - (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. SiS Graphics

          #30540
          Forum Admin
          anticapitalista

            Maybe you should let us know exactly how it failed.
            What did you do exactly and what were the results (the devil is in the details)
            Simply saying it failed helps no one, including you.

            Philosophers have interpreted the world in many ways; the point is to change it.

            antiX with runit - leaner and meaner.

            #30588
            Member
            mikey777

              @anticapitalista
              You’re right – simply saying it failed is not helpful at all.
              The new thread I’ve opened, detailing my difficulty in getting
              antiX-core to start up, will be posted here when done:

              https://www.antixforum.com/forums/topic/antix-core-failure-of-desktop-to-boot/

              • This reply was modified 4 years, 7 months ago by mikey777.
              • This reply was modified 4 years, 7 months ago by mikey777.
              • This reply was modified 4 years, 7 months ago by mikey777.

              ▪ 32-bit antix19.4-core (SysV init)+LXDE legacy install on :
              - (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
              ▪ 64-bit antix21-base (SysV init)+LXDE legacy install on:
              - (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Intel Mobile 4 Series, integrated graphics
              - (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. SiS Graphics

            Viewing 5 posts - 1 through 5 (of 5 total)
            • You must be logged in to reply to this topic.