Re: cloning a system to another partition - what to change?
On 10:37 Wed 19 Oct , SpamHog wrote:
> Thank you too Mike, but I have already tried several times with either
> GNU/Linuxspeak "/dev/hda6" or Grubspeak "(hd0,5)" so it must be
> someting else.
>
> Moreover,
>
> 1) Being the "boot" root and the "running" root one and the same, the
> second root specification should be redundant anyway.
>
On your second line, you must add "root=/dev/hdc6" in order to pass
this argument to the kernel as your new root file system.
It is a _kernel_ argument and _not_ a Grub argument.
Grub only reads the _first_ part of the second line, to find the kernel:
-->"kernel=/boot/vmlinuz-2.6.8-2-686"<--
All arguments after this part are passed only to the target kernel and
are not releated to Grub.
> 2) Funnier yet: /dev/hda5 is not mentioned at all in my grub commands.
> Why is grub grabbing it instead of e.g., /dev/hda1 or the floppy?
> Occam's razor: the initrd image was made with hda5 as root, man
> mkinitrd says one should spec the root if not the same as the current
> system root (if mkinitrd works, that is), so if not from me, the idea
> of latching onto hda5 is likely to come from it. :0
>
> So, up the stream bar paddle esp. w.r.t. why mkinitrd now refuses to
> produce any initrd image. This is a strictly fresh and standard 3.1
> install with no subsequent changes - I didn't touch any conffile!
>
> Ideas?
>
> Grateful but uncloned, I remain.
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
Reply to: