Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
"dd if=/dev/hda2 of=/mnt/hda6/fedora.bin bs=512 count=1"
creates the file
then go in to windows edit the boot.ini
G:\ferdora.bin "Fedora"
so i boot the system, i havent deleted grub yet coz i want to be sure the it will work first. So i use grub to go to the chain loader select the fedora and nothing happens, well some error message.
i did this before using a system that all ready was setup with the same software that i didnt setup myself and it worked fine.
Can some one help me or even give a different way this can be achived.
Thank you all!
Last edited by monkey_eater; 05-13-2006 at 05:20 AM.
instead. This command only gets the first 512b from the Linux file system.
This thing worked for LILO. I never tried to use Windows boot manager when I was using GRUB. But I guess this works too. (I haven't looked into GRUB internels yet)
I dont understand what your dd command is supposed to be doing. If you wanted to copy the mbr, you would not use a partition number---you want the 1st 512 bytes of the **disk**--not of the 1st partition.
eg: "dd if=/dev/hda of=<pathtofile> etc"
Actually, note that grub is really the first 446 bytes (after that is a 64-byte partition table, and then the 2-byte "signature") Do if you just want grub, use bs=446
Distribution: Fedora (workstations), CentOS (servers), Arch, Mint, Ubuntu, and a few more.
Posts: 441
Rep:
Quote:
Originally Posted by pixellany
Actually, note that grub is really the first 446 bytes (after that is a 64-byte partition table, and then the 2-byte "signature") Do if you just want grub, use bs=446
That's why I said I haven't looked into GRUB internals. Well, here's someone who did..
Have a look at Task E4 of the last link of my signature.
I think it will work out. That you can use the existing Grub to boot to Window. In Window's NTLDR it lists itself and Linux so that you can boot to either there. Once you are happy with it you can restore Windows's MBR (Task B1 or B2 of the same link) and overwriting Grub at the same time.
Using Windows NTLRD you need to copy the file "fedora.bin", created in Linux using the dd command, into the "C" drive of your XP or Win2k.
Basically NTLRD does not support Linux and so can't (or won't) read a Linux partition to find its boot loader for chainloading. A user must round up each Linux's first 512 bytes of the Linux partition (the boot loader) and copies into the Windows partition for NTLRD to use. It is a pain in the ar?e because Linux can't write on NTFS partition and so "fedora.bin" has to be transfer into a floppy or a Dos partition first and fetched into XP or Win2k later. Editing "boot.ini" also need it to be "unhide" first and "hide" it on completion.
Personally I would stick with Grub or make a bootable Grub floppy or Grub CD to boot the PC. There is no PC system that cannot be booted by a Grub floppy so why bother with NTLRD?
Just like the Linux kernel the boot loaders like Grub or Lilo requires a fast response similar to that from a hard disk. USB devices are limited by the USB transmission rate and this causes the standard kernel to panic and the boot loader to hang if a system is booted from a USB device.
A slower bootloader is often used to boot a USB device.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.