antiX core boot manager

[Member macondo]

Today I decided to install ANOTHER antiX core version because I wanted to test Reiserfs (which I use in Slackware), but I remembered there are only 2 options for GRUB: MBR and / .
There should be a third option during the installation: NO BOOT MANAGER INSTALLATION.

Allow me to explain: in this new SSD, I installed antiX core first with GRUB in the MBR, then I installed Slackware Current in the third partition with NO BOOT MANAGER, after the installation, I rebooted into antiX, and did ‘update-grub’ and rebooted, it brought Slackware into the antiX grub menu and that was it, no problems.

But now, if I installed a second antiX version, I would have to install GRUB again into the MBR, because there is NO Ooption to ignore the installation of GRUB again.

See my point? Otherwise, kudos to you guys!!

• This topic was modified 2 years, 9 months ago by macondo.
• This topic was modified 2 years, 9 months ago by macondo.

antiX Core 64 Bit Runit IceWM

"Sometimes a man finds his destiny on the road he took to avoid it."

[Moderator Brian Masinick]

Helpful

Up

0

::

macondo wrote:

Today I decided to install ANOTHER antiX core version because I wanted to test Reiserfs (which I use in Slackware), but I remembered there are only 2 options for GRUB: MBR and / .
There should be a third option during the installation: NO BOOT MANAGER INSTALLATION.

Allow me to explain: in this new SSD, I installed antiX core first with GRUB in the MBR, then I installed Slackware Current in the third partition with NO BOOT MANAGER, after the installation, I rebooted into antiX, and did ‘update-grub’ and rebooted, it brought Slackware into the antiX grub menu and that was it, no problems.

But now, if I installed a second antiX version, I would have to install GRUB again into the MBR, because there is NO Ooption to ignore the installation of GRUB again.

See my point? Otherwise, kudos to you guys!!

@macondo:

I see your point and I understand it, but this is not something that I have seen in previous installations.
I wonder if the specific instance you installed (which I have NOT recently installed) has a DEFECT in the current release?
I usually do the exact same thing that you do, and I usually don’t install to the MBR most of the time.
Right now in fact, I’m using MX Linux to manage the MBR in GPT formatted device partitions with UEFI, though I disable the “secure” UEFI method.
I have TWO antiX 19 instances, the Base and runit versions, and I’ve installed, if I remember correctly, at or near antiX 19, though they are all now running the equivalent of antiX 19.2 with their different scheduling programs. Neither of them “acquired” primary use of the MBR, or if they DID, I simply removed their MBR entries in /boot/efi.

If I *missed* this DEFECT during my previous testing, I apologize.

--
Brian Masinick

[Member macondo]

Helpful

Up

0

::

Thank you, Brian…

antiX Core 64 Bit Runit IceWM

"Sometimes a man finds his destiny on the road he took to avoid it."

[Member Xecure]

Helpful

Up

0

::

A very bad workaround is installing a WM, startx, installing antix minstaller and install antiX with the graphical intaller. Reboot, remove the WM and X if you don’t want it.

Not a real solution, sorry.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Moderator Brian Masinick]

Helpful

Up

0

::

If anyone else happens to install or reinstall antiX, please notice whether or not there is a choice to ignore installing a boot manager.

@macondo:

If there continue to be no other choices I suggest you install the boot loader to /

It won’t hurt anything and when you update the boot loader on another system it can correctly detect antiX.

If you don’t want the information on your disk you can manually remove either the package, the directories containing the files or both, depending on your needs and concerns.

I hope that helps.

--
Brian Masinick

[Moderator Brian Masinick]

Helpful

Up

0

::

Xecure wrote:

A very bad workaround is installing a WM, startx, installing antix minstaller and install antiX with the graphical intaller. Reboot, remove the WM and X if you don’t want it.

Not a real solution, sorry.

How will this affect the grub boot loader (boot manager)?

If we’re assuming that a full installation works as expected, that would be an alternative way.

I’m thinking that

sudo apt-get remove grub
(Or all grub packages), and also purging will completely remove the boot manager on a system when it’s not necessary.

Agreed?

--
Brian Masinick

[Forum Admin anticapitalista]

Helpful

Up

0

::

@macondo – I’ll add the option to not install grub to the cli-installer script.

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

antiX with runit - leaner and meaner.

[Moderator Brian Masinick]

Helpful

Up

0

::

anticapitalista wrote:

@macondo – I’ll add the option to not install grub to the cli-installer script.

Thanks anti! 🙂

--
Brian Masinick

[Member macondo]

Helpful

Up

0

::

Thank you, anti

antiX Core 64 Bit Runit IceWM

"Sometimes a man finds his destiny on the road he took to avoid it."

[Author]

Posts