I know during install you should choose to install the boot loader to
the MBR of HAD.
For grub try here
http://www.gnu.org/software/grub/
this is stolen from the gentoo website"
--------------begin cut---------------------------------------
Final steps: configure GRUB
The most critical part of understanding GRUB is getting comfortable with
how GRUB refers to hard drives and partitions. Your Linux partition
/dev/hda1 is called (hd0,0) under GRUB. Notice the parenthesis around
the hd0,0 - they are required. Hard drives count from zero rather than
"a", and partitions start at zero rather than one. So, /dev/hdb3 gets
translated to (hd1,2), and /dev/hdd7 gets translated to (hd3,6). After
you've gotten the feel for that, convert your boot and root partition
names to the GRUB format and write them down. Now, it's time to install
GRUB.
The easiest way to install grub is to simply type grub at your chrooted
shell prompt:
# grub
You'll be presented with the grub> grub command-line prompt. Now, you
need to type in the right commands to install the GRUB boot record onto
your hard drive. In my example configuration, I want to install the GRUB
boot record on my hard drive's MBR (master boot record), so that the
first thing I see when I turn on the computer is the GRUB prompt. In my
case, the commands I want to type are:
Code listing 39
grub> root (hd0,0)
grub> setup (hd0)
grub> quit
Here's how the two commands work. The first root ( ) command tells GRUB
the location of your boot partition (in our example, /dev/hda1 or
(hd0,0) in GRUB terminology. Then, the second setup ( ) command tells
GRUB where to install the boot record - it will be configure to look for
its special files at the root ( ) location that you specified. In my
case, I want the boot record on the MBR of the hard drive, so I simply
specify /dev/hda (also known as (hd0)). If I were using another boot
loader and wanted to set up GRUB as a secondary boot-loader, I could
install GRUB to the boot record of a particular partition. In that case,
I'd specify a particular partition rather than the entire disk. Once the
GRUB boot record has been successfully installed, you can type quit to
quit GRUB. Gentoo Linux is installed, but we need to create the
/boot/grub/menu.lst file so that we get a nice GRUB boot menu when the
system reboots. Here's how to do it.
Now, create the menu.lst file (nano -w /boot/grub/menu.lst), and add the
following to it:
Code listing 40
default 0
timeout 30
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
title=My example Gentoo Linux
root (hd0,0)
kernel /boot/bzImage root=/dev/hda3
# Below needed only for people who dual-boot
title=Windows NT Workstation
root (hd0,5)
chainloader +1
Note: The menu.lst file should end in "lst" as in "list", not "1st" as
in "first". Also, (hd0,0) should be written without any spaces inside
the parentheses.
After saving this file, Gentoo Linux installation is complete. Selecting
the first option will tell GRUB to boot Gentoo Linux without a fuss. The
second part of the menu.lst file is optional, and shows you how to use
GRUB to boot a bootable Windows partition.
Note: Above, (hd0,0) should point to your "boot" partition (/dev/hda1 in
our example config) and /dev/hda3 should point to your root filesystem.
(hd0,5) contains the NT boot loader.
Also, if you need to pass any options to the kernel, simply add them to
the end of the kernel command. We're already passing one option
(root=/dev/hda3), but you can pass others as well. In particular, you
can turn off devfs by default (not recommended unless you know what
you're doing) by adding the gentoo=nodevfs option to the kernel command.
Note: Unlike in earlier versions of Gentoo Linux, you no longer have to
add devfs=mount to the end of the kernel line to enable devfs. In rc6
devfs is enabled by default.
------------------end cut-------------------------------
I know this is how I installed grub on mine. YMMV
Anyone else have a better link on installing a boot loader after the OS
is there?
Take care,
Seth Hollen
seth@hollen.org
727-919-1598
-----Original Message-----
From: slug@lists.nks.net [mailto:slug@lists.nks.net] On Behalf Of David
M. Vo
Sent: Friday, May 10, 2002 12:23 PM
To: slug@nks.net
Subject: RE: [SLUG] Dual boot?????
Thanks Seth,
I am using RH 7.2 and it does have both options:
Grub or lilo, but I just could not get it working.
I went on the web and try to get some how-to but it did not help.
Do you know any reference site that I can go to to get this info?
Thanks,
David
-----Original Message-----
From: slug@lists.nks.net [mailto:slug@lists.nks.net]On Behalf Of Seth
Hollen
Sent: Thursday, May 09, 2002 10:45 AM
To: slug@nks.net
Subject: RE: [SLUG] Dual boot?????
Yes you can, what Linux distro are you using.
Grub or lilo can do it
Take care,
Seth Hollen
seth@hollen.org
727-919-1598
-----Original Message-----
From: slug@lists.nks.net [mailto:slug@lists.nks.net] On Behalf Of David
M. Vo
Sent: Thursday, May 09, 2002 2:18 PM
To: slug@nks.net
Subject: [SLUG] Dual boot?????
Hi Guys,
I am trying to put win2k and linux on the same PC. I have 2k on HDA and
Linux on HDB.
I have to boot linux by floppy disk. Is it possible to have both on the
boot
loader.
If yes, how.
My win 2k is NTFS format.
Thanks
-----Original Message-----
From: slug@lists.nks.net [mailto:slug@lists.nks.net]On Behalf Of Greg
Schmidt
Sent: Thursday, May 09, 2002 7:01 AM
To: slug@nks.net
Subject: Re: [SLUG] Slow SAMBA or what?
On Wed, 8 May 2002, Chuck Hast wrote:
> I have a LINUX machine that I also use as a SAMBA box. I went to pull
a
> file over to a windows 2k machine from the SAMBA machine, the file is
a
> 74m directory, I am pulling it over a 100mb 100baseT connection 20
minutes
> seems a bit LONG for that path, do I need to tweek something in my
SAMBA
> box? (I can't see anything to tweek in the windows box but then was
there
> every anything TO tweek?)
>
>
One of the things to check for on a poorly performing Ethernet
connection
is a duplex mismatch, especially with Windows involved. The drivers
commonly autonegotiate a full-duplex link but really only run at
half-duplex. That WILL tank the performance. You say it is 100baseT,
not
100baseTX (switched). Maybe try forcing the Windows NIC to half-duplex.
If your network gear is sufficiently sophisticated to be able to show
errors on the ports check to see if your getting collisions on a
full-duplex link or some other wierdness.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 18:12:01 EDT