[bugs #486] map doesn't work in some environments

[mike padlipsky]

This mail is an automated notification from the bugs tracker
 of the project: GNU GRUB.

/**************************************************************************/
[bugs #486] Latest Modifications:

Changes by: 
                mike padlipsky <address@hidden>
'Date: 
                Mon 09/06/2004 at 20:45 (GMT)

------------------ Additional Follow-up Comments ----------------------------
"Little is known about this problem. Someone who experienced the problem
actually should address the problem. Otherwise, I cannot do anything
with the problem. "

it seems to me there's something quite fundamental you could do without any 
knowledge whatsoever of the specific problems that the map command [as opposed 
to the map person, namely me ... hey, it's my monogram and always has been]  
has caused: if you were to document exactly how grub effects the mapping, 
perhaps i -- and others -- could at least manage to get out of the tangles the 
mapping can get one into when one innocently uses it without knowing exactly 
what it's going to do, how to make it undo what it did, and perhaps most 
important of all, whether the mapping is persistent or just per-invocation 
[which would, of course, presumably be clear if the how/what information were 
furnished.

indeed, not to put too fine a point on it, how/what, undoing, and persistence 
information should have been in the manual all the long.  [but please don't 
make me wait for a new manual to find out what i need to know and am too 
retired to feel like digging into the sources to find out for myself.]

cheers, map







/**************************************************************************/
[bugs #486] Full Item Snapshot:

URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=486>
Project: GNU GRUB
Submitted by: Yoshinori K. Okuji
On: Tue 05/28/2002 at 21:26

Category:  Booting
Severity:  Ordinary
Priority:  3 - Low
Item Group:  Software Error
Resolution:  None
Privacy:  Public
Assigned to:  None
Originator Name:  
Originator Email:  
Status:  Open
Release:  0.92
Reproducibility:  Intermittent
Planned Release:  


Summary:  map doesn't work in some environments

Original Submission:  The command "map" seems not to work properly in some 
environments.
Little is known about this problem. Someone who experienced the problem
actually should address the problem. Otherwise, I cannot do anything
with the problem.

Okuji


Follow-up Comments
------------------


-------------------------------------------------------
Date: Mon 09/06/2004 at 20:45       By: mike padlipsky <map>
"Little is known about this problem. Someone who experienced the problem
actually should address the problem. Otherwise, I cannot do anything
with the problem. "

it seems to me there's something quite fundamental you could do without any 
knowledge whatsoever of the specific problems that the map command [as opposed 
to the map person, namely me ... hey, it's my monogram and always has been]  
has caused: if you were to document exactly how grub effects the mapping, 
perhaps i -- and others -- could at least manage to get out of the tangles the 
mapping can get one into when one innocently uses it without knowing exactly 
what it's going to do, how to make it undo what it did, and perhaps most 
important of all, whether the mapping is persistent or just per-invocation 
[which would, of course, presumably be clear if the how/what information were 
furnished.

indeed, not to put too fine a point on it, how/what, undoing, and persistence 
information should have been in the manual all the long.  [but please don't 
make me wait for a new manual to find out what i need to know and am too 
retired to feel like digging into the sources to find out for myself.]

cheers, map


-------------------------------------------------------
Date: Mon 08/12/2002 at 23:16       By: 0 <None>
Sorry, I forgot to add (re win98 grub cross-booting issues)
John S. Findlay - address@hidden

-------------------------------------------------------
Date: Mon 08/12/2002 at 23:11       By: 0 <None>
I have found a 'map' related issue with grub 0.90-11.

I have 2 hard drives: ide channel 1 primary master (linux)
and ide channel 1 slave (win98). 

I can use the bios (ancient ASUS P5A-B motherboard) to boot from what 
it calls 'C' (ide  channel 1 master) or 'D' (ide channel 1 slave).  Either way  
linux or win98 boot ok. 

If I use grub in the MBR on ide channel 1 master, it will not boot the win98 on 
the slave (as expected) unless I use the 'map' command in the grub.conf to 
'swap' the drives around.  

However, even though I can get grub to boot win98 this way, the resultant win98 
environment is broken. The win98 drive (Quantun CR8.4) on ide channel 1 slave 
is chopped up  into three partitions which come up normally as C: D: and E:. If 
I use grub on the MBR of the master to boot win98, it comes up with C: D: E: F: 
and G: .  C: is ok, but D: & E: and don't work at all, and the 'real' 2nd and 
3rd partitions are now mapped to F: and G:.

If instead of using grub I use lilo, this fault does not occur, i.e C: D: and 
E: come up normally. Also, when booting to the win98 disk from lilo, no screen 
messages appear that you would'nt normally see, but when using grub the 'map' 
instruction appear on the screen in between the various win98 splash screens as 
they come and go before it finally takes over properly. 






CC List
-------

CC Address                          | Comment
------------------------------------+-----------------------------
okuji                               | just in case you don't automagically see 
it anyway









For detailed info, follow this link:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=486>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/