Mailinglist Archive: opensuse-factory (279 mails)

< Previous Next >
Re: [opensuse-factory] How to dis/enable a bootloader?
  • From: "Rajko M." <rmatov101@xxxxxxxxxxx>
  • Date: Fri, 20 Mar 2009 19:12:25 -0500
  • Message-id: <200903201912.25334.rmatov101@xxxxxxxxxxx>
On Friday 20 March 2009 12:30:06 pm Oddball wrote:
Rajko M. schreef:
On Friday 20 March 2009 10:27:53 am Oddball wrote:
...

2) Where should grub be installed for the least trouble?

In boot sector of Linux partition, which is default.
Partition must be primary and marked active, in other words bootable.

So if asked the question were to install grub, i should answer default...

If asked, but default configuration doesn't ask anything.

After XP recovery from Ghost image, you can use recovery mode of openSUSE
installation DVD to mark linux partition bootable again, if that
information is lost, and all should work like before.

so i won't have to touch grub at all, only mark the partition bootable...

If recreation of Windows changed anything.
I remember some 2 years ago recreating windows didn't change partitioning,
like it was regular case some 5-6 years ago, when ghost image would cleanup
whole disk.

BTW, Ghost should not have a problem with generic bootloader that is
installed by default.

What generic bootloader? Grub isn't the generic bootloader?

You already have answers on that. Here is just sample in my MBR.
I guess it is from FreeDOS, installed by YaST Bootloader. When you install
openSUSE it will be installed in MBR, if don't change anything in Bootloader
section of Installation Proposal.

# dd if=/dev/sda of=mbrcode bs=512 count=1
# hexdump -C mbrcode

00000000 31 c0 8e d0 bc 00 7c 8e c0 8e d8 bf 1e 06 be 1e |1.....|.........|
...<skipped>
000000b0 7c 00 00 00 00 00 00 00 00 00 00 45 72 72 6f 72 ||..........Error|
000000c0 20 00 0d 0a 00 4e 6f 20 61 63 74 69 76 65 20 70 | ....No active p|
000000d0 61 72 74 69 74 69 6f 6e 00 44 69 73 6b 20 72 65 |artition.Disk re|
000000e0 61 64 20 65 72 72 6f 72 00 4e 6f 20 6f 70 65 72 |ad error.No oper|
000000f0 61 74 69 6e 67 20 73 79 73 74 65 6d 00 49 6e 76 |ating system.Inv|
00000100 61 6c 69 64 20 43 48 53 20 72 65 61 64 00 e8 03 |alid CHS read...|
...<skipped>

GRUB boot record code will mention GRUB in strings. I don't have sample.
Difference, when you use comand 'dd', is between /dev/sda that will give you
MBR (master boot record) and /dev/sda1 that will give you partition boot
record of first partition, and so on.

In ghost manual explicitly explained: does not work with grub...
I contacted symantec about that this afternoon in a live chat: no
bootloader supported, they give me a refund for the programm, because i
cannot use it with dual, triple or quadruple boot.

I guess the current schema is the most compatible with different tools
available on the market. It gives sometimes strange result that you have to
hop trough 2 boot screens, but it is using whatever is in boot records, which
is usually native boot loader, so you can boot whatever is installed (have
you tried BSDs).

--
Regards, Rajko
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups
References