--
Regards
Vladimir 'phcoder' Serbinenko
--- Begin Message ---
David Miller wrote:
From: phcoder
Date: Sun, 22 Mar 2009 23:51:14 +0100
You could do it the way similar to how it's done on i386-pc:
jmp use_hardcoded
use_hardcoded:
And then the grub-setup tool nops out the first jump if stage
From: Robert Millan
Date: Sun, 22 Mar 2009 13:22:34 +0100
> On Sun, Mar 22, 2009 at 01:41:52AM +0100, phcoder wrote:
> > I don't see why
> > sth like
> > (/p...@1e\,60/p...@0/p...@9/p...@0/s...@1/d...@0,1)
> > is a problem.
>
> FWIW, I like this much better than replacing our comma separat
From: phcoder
Date: Sun, 22 Mar 2009 23:51:14 +0100
> You could do it the way similar to how it's done on i386-pc:
> jmp use_hardcoded
>
> use_hardcoded:
> And then the grub-setup tool nops out the first jump if stage2
> resides on a disk different than where bootblock is
Sure we could do that.
You could do it the way similar to how it's done on i386-pc:
jmp use_hardcoded
use_hardcoded:
And then the grub-setup tool nops out the first jump if stage2 resides
on a disk different than where bootblock is
David Miller wrote:
From: phcoder
Date: Sun, 22 Mar 2009 12:17:17 +0100
As for the
On Sun, Mar 22, 2009 at 01:41:52AM +0100, phcoder wrote:
> I don't see why
> sth like
> (/p...@1e\,60/p...@0/p...@9/p...@0/s...@1/d...@0,1)
> is a problem.
FWIW, I like this much better than replacing our comma separator with
something else, thereby making GRUB inconsistent among platforms.
From: phcoder
Date: Sun, 22 Mar 2009 01:48:14 +0100
> phcoder wrote:
> > Device name in boot block will anyway be written in it's complete raw OFW
> > form, no matter how the rest of the grub2 accessing the disks. Using UUIDs
> > in this place would be nice. On IRC you said that we have 120 byt
From: phcoder
Date: Sun, 22 Mar 2009 01:41:52 +0100
> Device name in boot block will anyway be written in it's complete
> raw OFW form, no matter how the rest of the grub2 accessing the
> disks. Using UUIDs in this place would be nice. On IRC you said that
> we have 120 bytes for the name. UUID i
phcoder wrote:
Device name in boot block will anyway be written in it's complete raw
OFW form, no matter how the rest of the grub2 accessing the disks. Using
UUIDs in this place would be nice. On IRC you said that we have 120
bytes for the name. UUID is 16 or 32 bytes depending on FS. Is it
po
Device name in boot block will anyway be written in it's complete raw
OFW form, no matter how the rest of the grub2 accessing the disks. Using
UUIDs in this place would be nice. On IRC you said that we have 120
bytes for the name. UUID is 16 or 32 bytes depending on FS. Is it
possible to fit so
From: David Miller
Date: Wed, 18 Mar 2009 13:55:22 -0700 (PDT)
> From: Robert Millan
> Date: Wed, 18 Mar 2009 11:18:46 +0100
>
> > On Sun, Mar 15, 2009 at 03:41:16PM -0700, David Miller wrote:
> > > From: Robert Millan
> > > Date: Sun, 15 Mar 2009 16:45:31 +0100
> > >
> > > > It's not an abso
From: Robert Millan
Date: Wed, 18 Mar 2009 11:18:46 +0100
> On Sun, Mar 15, 2009 at 03:41:16PM -0700, David Miller wrote:
> > From: Robert Millan
> > Date: Sun, 15 Mar 2009 16:45:31 +0100
> >
> > > It's not an absolute must that device names are unique. You can still
> > > identify partitions
On Sun, Mar 15, 2009 at 03:41:16PM -0700, David Miller wrote:
> From: Robert Millan
> Date: Sun, 15 Mar 2009 16:45:31 +0100
>
> > It's not an absolute must that device names are unique. You can still
> > identify partitions by their filesystem UUID or label, and in fact this
> > is what our defa
From: Vesa Jääskeläinen
Date: Sun, 15 Mar 2009 11:22:21 +0200
> David Miller wrote:
> > The problem is two fold:
> >
> > 1) "," characters can appear anywhere in an openfirmware path
> >name. For example my workstations disk is:
> >
> > /p...@1e,60/p...@0/p...@9/p...@0/s...@1/d...@
From: Robert Millan
Date: Sun, 15 Mar 2009 16:45:31 +0100
> It's not an absolute must that device names are unique. You can still
> identify partitions by their filesystem UUID or label, and in fact this
> is what our default scripts (grub-mkconfig) do anyway.
Things like UUID and labels are no
On Sat, Mar 14, 2009 at 03:14:17PM -0700, David Miller wrote:
>
> One issue I need to resolve before I can send finalized
> patches out for sparc is about device naming.
>
> Currently the PowerPC ieee1275 support allows using both device
> aliases and full openfirmware device path names with the
David Miller wrote:
> One issue I need to resolve before I can send finalized
> patches out for sparc is about device naming.
>
> Currently the PowerPC ieee1275 support allows using both device
> aliases and full openfirmware device path names with the usual GRUB
> partition specification concaten
From: phcoder
Date: Sun, 15 Mar 2009 00:44:15 +0100
> For me it looks like it's disk driver-specific (ofdisk) and not
> platform-specific. Perhaps quoting or escaping could offer a better
> solution?
Specifying partitions using "/path/to/device:partition" syntax is an
attribute of openfirmware.
For me it looks like it's disk driver-specific (ofdisk) and not
platform-specific. Perhaps quoting or escaping could offer a better
solution?
David Miller wrote:
One issue I need to resolve before I can send finalized
patches out for sparc is about device naming.
Currently the PowerPC ieee1275
One issue I need to resolve before I can send finalized
patches out for sparc is about device naming.
Currently the PowerPC ieee1275 support allows using both device
aliases and full openfirmware device path names with the usual GRUB
partition specification concatenated at the end. For the most
19 matches
Mail list logo
