-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2014-05-20 16:47, Anton Aylward wrote:
On 05/20/2014 10:20 AM, Carlos E. R. wrote:
If you run "mkinitrd" it should do it. However, you have to do it after migration and before booting.
I was hoping you'd talk about the config and parameters needed. *sigh*
Well, you see, I make them on the go. I know the goal, the tools, and I look up the exact syntax in the man pages. I make mistakes, so I go back and correct them, on the go. I have done it several times, successfully, and helped others correct their problems. But I don't have a precise writeup with detailed instructions that ensure success.
As I understand it, mkinitrd is on the way out in favour of some other, easier to configure and manage, tool.
So I heard... I'll wait. You people try it, then you tell me. I'll listen and take notes. >:-))
"Chroot"? Chroot to where?
You can't, in my experience, simply chroot to anywhere except / without having to make provision for /dev, /proc and /sys.
Then, do :-) Those a are menial details to be filled up later :-) Yes, you have to mount the target root somewhere, and the new usr partition in the correct place under that somewhere. And the separate boot partition if it exists, and var if it is separate, etc. And yes, you need bind mount sys, proc, dev - but you find that out if you forget from the error messages you get.
At the very least initrd needs to know what modules to include and where to write to. If you've chroot'd this may be all upset unless you either make a few mounts and symlinks and supply an argument list.
Well, initrd should know already about the needed modules, the hardware has not changed, nor disk driver, and probably not the filesystems used.
Now to be fail, I've booted form the rescue disk to do many operations and then mounted the hard drive I've been modifying/repairing on /mnt/disk and chroot'd there so that I'm running on the 'real' system and not the rescue disk. Perhaps that's what you were thinking of but didn't mention or perhaps edited out when revision.
Yes, that's exactly what I meant.
If, however, you are doing this change in single user mode without booting from the rescue disk, then the chroot isn't needed.
Yes, but I'm not sure that you can rename usr and mount the new one in place in that mode, because it is in use...
However ....
Migrating /usr/share to its own partition frees up space on /usr and maybe on /, and you don't need to run mkinited :-)
True. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlN7blQACgkQja8UbcUWM1w88AD/ewyiv3acni3fvL7AwjDAkaz3 A128TVkkfx1M5NVBj9MA/RIMrVFAeuPuNd+rabIu64XiQnqlBo/PQjSrW5rAPd5P =L8GH -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org