Javier Martín wrote:
Bit a bit, progress continues: I have some crappy UI semi-ready, to
improve on later, and I'm now battling with the INT13h handler to
perform the actual mapping - had to rescue the big old "Architecture
Programmer's Manual" in order to do PIC code without the amd64
rip-relati
Bit a bit, progress continues: I have some crappy UI semi-ready, to
improve on later, and I'm now battling with the INT13h handler to
perform the actual mapping - had to rescue the big old "Architecture
Programmer's Manual" in order to do PIC code without the amd64
rip-relative addressing. However,
On Thu, May 29, 2008 at 11:48:33PM -0400, Pavel Roskin wrote:
>
> We may still want to map a hard drive as a floppy. I can imagine that
> some floppy readers may be seen as hard drives by the BIOS.
And some BIOSes see USB drives as floppies too :-/
--
Robert Millan
I know my rights; I want
Quoting Javier Martín <[EMAIL PROTECTED]>:
Then "drivemap" it is. I've already been delving into the depths of The
Source, though I'd have preferred it to be commented a bit more
exhaustively. Some times it's difficult to guess which methods to call,
and it took me a bit to realize that I had to
Then "drivemap" it is. I've already been delving into the depths of The
Source, though I'd have preferred it to be commented a bit more
exhaustively. Some times it's difficult to guess which methods to call,
and it took me a bit to realize that I had to check with the disk
"device" to see if it was
On Wed, 2008-05-28 at 16:24 +0200, Robert Millan wrote:
> On Tue, May 27, 2008 at 11:59:22AM -0400, Pavel Roskin wrote:
> >
> > Again, I'd like to see the command name shortened, perhaps to "drivemap"
> > or "map". It's not like users will need to distinguish BIOS and
> > non-BIOS mappings.
>
>
Javier Martín wrote:
drivemap-related functionality. Is there any site/document (apart from
the sources themselves) in which I can learn more about the internals
of GRUB2 and, specifically, the "boot" command sequence?.
GRUB 2 Wiki will serve the purpose for developer documentation:
http://gru
On Tue, May 27, 2008 at 11:59:22AM -0400, Pavel Roskin wrote:
>
> Again, I'd like to see the command name shortened, perhaps to "drivemap"
> or "map". It's not like users will need to distinguish BIOS and
> non-BIOS mappings.
But then we're occupping generic namespace with arch-specific features
> The cooperation between modules is not hard, but I think
> map -first (hdx) will be more useful. Such command just swaps hd0 and hdx
> drives. This also covers the scenarios when we chainload something else
> than first sector of given partition.
>
> And maybe we can also consider following synta
Dne 27 Květen 2008, 23:47, Javier Martín napsal(a):
>>> For grub, i'd suggest
>>> map [olddrive newdrive] ... eg. map (hd1) (hd0) (hd0) (hd1)
> That was the syntax used in GRUB Legacy, it was successful and could be
> reused, but I'd prefer the "drivemap" command I suggested earlier, with
> option
> > For grub, i'd suggest
> > map [olddrive newdrive] ...
> > eg. map (hd1) (hd0) (hd0) (hd1)
That was the syntax used in GRUB Legacy, it was successful and could be
reused, but I'd prefer the "drivemap" command I suggested earlier, with
options not just to map drives, but also to show the mappings
11 matches
Mail list logo
