LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Linux Mint
User Name
Password
Linux Mint This forum is for the discussion of Linux Mint.

Notices


Reply
  Search this Thread
Old 09-04-2015, 11:33 AM   #1
notadoc
Member
 
Registered: Jan 2015
Posts: 113

Rep: Reputation: Disabled
Grub Boot: Old vs New


New install of 17.1 Cinnamon. Other distro is Slack 14. GRUB2 installed by choice into the root device of Mint. MBR contains Old Grub. There are 2 ways I can boot into Mint:

1. Point the old grub on MBR to /boot/vmlinuz-3.13.0-37-generic and initrd.img-3.13.0-37-generic in the Mint root partition. Works fine.

2. Point the old grub to /boot/grub/i386-pc/core.img in the Mint root partition. Also works, though it takes a few secs longer.

Question: Is there any functional difference between these two boot methods? I don't see any obviously different behavior, but I still wonder.
 
Old 09-04-2015, 11:51 AM   #2
Keruskerfuerst
Senior Member
 
Registered: Oct 2005
Location: Horgau, Germany
Distribution: Manjaro KDE, Win 10
Posts: 2,199

Rep: Reputation: 164Reputation: 164
Your installation of Mint 17.1 seems not successful.
 
Old 09-04-2015, 12:03 PM   #3
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: Slackware, Ubuntu, PCLinux,
Posts: 10,510

Rep: Reputation: 2491Reputation: 2491Reputation: 2491Reputation: 2491Reputation: 2491Reputation: 2491Reputation: 2491Reputation: 2491Reputation: 2491Reputation: 2491Reputation: 2491
Quote:
Your installation of Mint 17.1 seems not successful.
I think you mis-read his post. He said both options do boot.

Quote:
Is there any functional difference between these two boot methods?
No. Have the same thing with Grub Legacy booting Ubuntu. The first option directly boots, the second option is more like a chainload entry and when I select it, I get the Ubuntu boot menu with various options.
 
1 members found this post helpful.
Old 09-05-2015, 02:46 AM   #4
Keruskerfuerst
Senior Member
 
Registered: Oct 2005
Location: Horgau, Germany
Distribution: Manjaro KDE, Win 10
Posts: 2,199

Rep: Reputation: 164Reputation: 164
I have read the first post.

But it makes no sense to me installing two bootloaders in two places.

If it is a actual computer, UEFI is the best way.
 
Old 09-05-2015, 07:48 AM   #5
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 7,350

Rep: Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590
Quote:
If it is a actual computer, UEFI is the best way.
It might not be a uefi computer.
Quote:
But it makes no sense to me installing two bootloaders in two places.
Makes perfect since IMO. I have a similar setup and allows for a distro to update it's own grub menu during updates without having to go and update grub in the distro with the bootloader in the mbr, which I tend to forget to do from time to time.

Last edited by colorpurple21859; 09-05-2015 at 07:51 AM.
 
Old 09-05-2015, 08:10 AM   #6
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: Slackware, Ubuntu, PCLinux,
Posts: 10,510

Rep: Reputation: 2491Reputation: 2491Reputation: 2491Reputation: 2491Reputation: 2491Reputation: 2491Reputation: 2491Reputation: 2491Reputation: 2491Reputation: 2491Reputation: 2491
If you have multiple operating systems as is the case here, installing a bootloader to the root partition of the second system allows you to chainload it. The OP has two entries to boot Mint in his Grub Legacy. There is no need to do it, probably just to test. The first method will boot a few seconds faster as it doesn't go to the menu of the second OS as the second option does.
 
Old 09-05-2015, 03:11 PM   #7
Keruskerfuerst
Senior Member
 
Registered: Oct 2005
Location: Horgau, Germany
Distribution: Manjaro KDE, Win 10
Posts: 2,199

Rep: Reputation: 164Reputation: 164
Hardwareinfo?
 
Old 09-07-2015, 01:54 PM   #8
notadoc
Member
 
Registered: Jan 2015
Posts: 113

Original Poster
Rep: Reputation: Disabled
Just to be clear, this isn't a UEFI box. The two boot loaders are an "accident of history." Original distro (Slack 14) installed legacy grub in MBR. Some time later I installed Mint 17.1 in unused space on the same physical drive. During the Mint install I selected the Mint root partition for grub2, because I didn't want to screw up my working MBR. Simple as that.

I'm marking this thread as SOLVED, because I believe my original question has been answered.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] How come I can't edit /boot/grub/grub.conf or /boot/grub/menu.lst in Fedora 14? trien27 Fedora 4 01-22-2011 04:02 PM
Grub menu doesnt load at startup : dual boot : grub in the /boot partition jayesh.bhoot Linux - General 7 10-23-2010 03:58 AM
Why /boot/grub/grub.conf is symlinked to /boot/grub/menu.lst raj_hcl1986@rediffma Linux - Newbie 2 10-19-2008 02:19 AM
gentoo : grub: The file /boot/boot/grub/stage1 not read correctly Boudewijn Linux - Software 3 05-21-2008 03:13 AM
need to access /boot/grub/menu.lst and /boot/grub/device.map neouto Linux - Newbie 8 09-04-2005 11:45 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Linux Mint

All times are GMT -5. The time now is 12:12 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration