Dual boot

[Joshua Judson Rosen]

David accidentally sent this to me instead of the list;
bringing it back listward...:

David Rose <DRose at Proviss.com> writes:
>
>  Josh, thanx for the feedback.  When I do the steps you suggest, grub
> (v 0.97) gives me:
>     Possible disks are:  hd0 hd1
> 
> Based on that, how would I configure my grub conf file?

What does it do/say when you try tab-completing on "root (hd0,"
and "root (hd1,"?

You can also actually run through a whole series of commands
(all the way to boot) from GRUB's command-line interface--
should be quicker than `edit the grub.conf and see if it works',
especially since you can verify things one command at a time.

> By the way, I currently have a work-around by disabling the primary
> drive in the BIOS, but that's hokey.  I'd still like to get this
> working for convenience and my edification.

That actually sounds like exactly the sort of thing I was talking about,
as having potential to mess-up GRUB's notion of which drives have
which number....

> On 10/13/2010 11:10 AM, Joshua Judson Rosen wrote:
> > John Abreau<jabr at blu.org>  writes:
> >> On Fri, Oct 8, 2010 at 5:58 PM, David Rose<DRose at proviss.com>  wrote:
> >>> I ran the "fdisk -l sdb" and it told me that there was an NTFS file system
> >>> with the correct amount of space so it appears that it recognizes the drive.
> >>>
> >>> I tried (hd1,1) and it gives me an "Error 22: No such partition".
> >>
> >>
> >> Grub's (hd1,1) corresponds to /dev/sdb2. Is the NTFS filesystem on /dev/sdb2?
> >> If it's actually on /dev/sdb1, then the grub equivalent would be (hd1,0)
> > I don't think that's exactly true: if I recall correctly, GRUB (version 0.x)
> > just counts the drives starting from zero, regardless of which controller
> > or channel the drives are attached to. If Linux is calling it `sdb' because
> > it's attached to the second controller, but there's no `sda' actually attached
> > (or powered-on), then `sdb' in Linux may well be `hd0' in GRUB.
> >
> > Also, partition-numbers start at 1 only in GRUB 0.x (now called "GRUB Legacy");
> > in `GRUB 2' (version 1.x, which used to be called "PUPA"), partition-numbers
> > start at *zero*. I didn't see it specified what version of GRUB is in use,
> > though I guess it's GRUB 0.x (Legacy) from the `grub.conf' syntax used.
> >
> > And, David: are you just doing this by `brute force', rebooting every time
> > to see if a change is viable? Or have you tried tab-completion in GRUB's
> > command-shell? From the manual:
> >
> >      To help you find out which number specifies a
> >      partition you want, the GRUB command-line (*note Command-line
> >      interface::) options have argument completion. This means that, for
> >      example, you only need to type
> >
> >           root (
> >
> >         followed by a<TAB>, and GRUB will display the list of drives,
> >      partitions, or file names. So it should be quite easy to determine the
> >      name of your target partition, even with minimal knowledge of the
> >      syntax.

-- 
"Don't be afraid to ask (λf.((λx.xx) (λr.f(rr))))."