On Wed, 2008-07-23 at 00:08 +0200, Robert Millan wrote:
> I don't think it's that unusual. Let's take an example. We have 1 PATA
> disk and 1 SATA disk, and are installing GNU/Linux in it. We only have
> one /boot partition (or directory in /). Turns out we have no idea which
> of the two disk
On Tue, Jul 22, 2008 at 05:57:56PM -0400, Pavel Roskin wrote:
> On Tue, 2008-07-22 at 23:36 +0200, Robert Millan wrote:
> > On Mon, Jul 21, 2008 at 05:26:17PM -0400, Pavel Roskin wrote:
> > > >
> > > > This is mostly implemented already. I sent a proof of concept in a mail
> > > > titled "[PATCH]
On Tue, 2008-07-22 at 23:36 +0200, Robert Millan wrote:
> On Mon, Jul 21, 2008 at 05:26:17PM -0400, Pavel Roskin wrote:
> > >
> > > This is mostly implemented already. I sent a proof of concept in a mail
> > > titled "[PATCH] disk/fs_uuid.c".
> > >
> > > It will only search hard drives unless no
On Mon, Jul 21, 2008 at 05:26:17PM -0400, Pavel Roskin wrote:
> >
> > This is mostly implemented already. I sent a proof of concept in a mail
> > titled "[PATCH] disk/fs_uuid.c".
> >
> > It will only search hard drives unless no match is found (in that case your
> > boot is broken, so you wouldn
On Sat, 2008-07-19 at 17:14 +0200, Robert Millan wrote:
> > As I understand it, there are two cases where we have to hardcode the
> > drive number.
> >
> > 1) MBR and core.img (embedded or not) are on different drives.
>
> If embedded, then they're not different drives (core.img is put right aft
On Wed, Jul 16, 2008 at 12:08:57PM -0400, Pavel Roskin wrote:
> On Wed, 2008-07-16 at 07:11 -0700, Colin D Bennett wrote:
>
> > > That's a very advanced setup. I actually cannot imagine why anyone
> > > would use different boot and root drives. Well, maybe the boot drive
> > > has no partitions
