[opensuse] Simple stupid yast question
Hello SuSE people, Should I not be able to run Yast in the rescue system? I logon as root type yast (or yast2) and I get a bash -command not found. Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2008-09-04 at 23:15 -0400, Bob S wrote:
Hello SuSE people,
Should I not be able to run Yast in the rescue system? I logon as root type yast (or yast2) and I get a bash -command not found.
Bob S
Maybe use the exact path? I'm not sure if the $PATH var is set in Rescue -- Michael S. Dunsavage -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob S a écrit :
Hello SuSE people,
Should I not be able to run Yast in the rescue system? I logon as root type yast (or yast2) and I get a bash -command not found.
Bob S of course not :-)
you have only a minimal system and your hard drive is not even mounted. search the wiki, all is explained there (you have to mount all the file system to have yast working) jdd -- Jean-Daniel Dodin Président du CULTe www.culte.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob S wrote:
Hello SuSE people,
Should I not be able to run Yast in the rescue system? I logon as root type yast (or yast2) and I get a bash -command not found.
Bob S
Bob, After having been through something similar with updates that rendered a system unbootable and needing to use the rescue function on the dvd, here is the short version for gaining full access, including yast, to the broken system: (1) boot from the install DVD (2) choose "Rescue System", login as "root" (no password needed) (3) look at "cat /proc/partitions" to determine which partitions need to be mounted under /mnt to create a chroot environment of your full original system. (the default install will require '/' and '/home' to be mounted). You should be able to tell by the relative sizes of the partitions which partition is / and which is /home. You may also need to look at "ls -l /dev/disk/by-id" for disk by-id mappings if you run into any trouble. (4) "mount" the partitions under /mnt, then "bind" dev/, proc/ and sys/ and chroot /mnt. (your '/' partition will be '/mnt' after you complete all mounts and before you chroot /mnt) **Note: mount the / partition first otherwise the mount point for /home will not exist yet. _Example_ with '/'=/dev/sda6 and '/home'=/dev/sda7: mount /dev/sda6 /mnt [** Note: at this point you can check /mnt/etc/fstab for the original devices and mount points used and unmount/adjust if necessary] continuing: mount /dev/sda7 /mnt/home mount -o bind /dev /mnt/dev mount -o bind /proc /mnt/proc mount -o bind /sys /mnt/sys cd /mnt chroot /mnt (5) Now you can run yast and everything else you need to fix your system (6) After you are done, type "exit" to exit the chroot environment and then "reboot". If all went well, you are done. If not, repeat steps 1-6 above and take another stab at it. This was all Greek to me until Joe Morris lent a hand to help explain the process of creating the chroot environment. It all works just the way it is supposed to. As always BACKUP what you can't afford to lose. Good luck! -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin a écrit :
original system. (the default install will require '/' and '/home' to be
you don't need /home to restore the system, better not mount it IMHO because there are sensible data there. mount / (root is on it), bind what is necessary (this is the problematic part, hard to remember), chroot and fix the system then reboot jdd -- Jean-Daniel Dodin Président du CULTe www.culte.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
jdd sur free wrote:
David C. Rankin a écrit :
original system. (the default install will require '/' and '/home' to be
you don't need /home to restore the system, better not mount it IMHO because there are sensible data there.
mount / (root is on it), bind what is necessary (this is the problematic part, hard to remember), chroot and fix the system then reboot
jdd
Right you are, But, having a majority of my recovery notes under /home, I did it anyway. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
the dvd, here is the short version for gaining full access, including yast, to the broken system:
(1) boot from the install DVD
(2) choose "Rescue System", login as "root" (no password needed)
(3) look at "cat /proc/partitions" to determine which partitions need to be mounted under /mnt to create a chroot environment of your full original system. (the default install will require '/' and '/home' to be This is funny. I have just been through a similar exercise with Solaris. When I booted with the Solaris DVD, it gave a message that said the system was detected and asked if I wanted to mount it, which I did. The funny part is that after three years of trying to learn something about Solaris, I have concluded that Solaris is a lot more difficult
David C. Rankin wrote: that SuSE Linux so it is funny that something with Solaris is much easier. Yes, I know the steps you listed aren't that hard. Damon Register -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 05 September 2008 12:29:20 David C. Rankin wrote:
Bob S wrote:
Hello SuSE people,
Should I not be able to run Yast in the rescue system? I logon as root type yast (or yast2) and I get a bash -command not found.
Bob S
Bob,
After having been through something similar with updates that rendered a system unbootable and needing to use the rescue function on the dvd, here is the short version for gaining full access, including yast, to the broken system:
(1) boot from the install DVD
(2) choose "Rescue System", login as "root" (no password needed)
(3) look at "cat /proc/partitions" to determine which partitions need to be mounted under /mnt to create a chroot environment of your full original system. (the default install will require '/' and '/home' to be mounted). You should be able to tell by the relative sizes of the partitions which partition is / and which is /home. You may also need to look at "ls -l /dev/disk/by-id" for disk by-id mappings if you run into any trouble.
(4) "mount" the partitions under /mnt, then "bind" dev/, proc/ and sys/ and chroot /mnt. (your '/' partition will be '/mnt' after you complete all mounts and before you chroot /mnt) **Note: mount the / partition first otherwise the mount point for /home will not exist yet. _Example_ with '/'=/dev/sda6 and '/home'=/dev/sda7:
mount /dev/sda6 /mnt
[** Note: at this point you can check /mnt/etc/fstab for the original devices and mount points used and unmount/adjust if necessary] continuing:
mount /dev/sda7 /mnt/home mount -o bind /dev /mnt/dev mount -o bind /proc /mnt/proc mount -o bind /sys /mnt/sys cd /mnt chroot /mnt
(5) Now you can run yast and everything else you need to fix your system
(6) After you are done, type "exit" to exit the chroot environment and then "reboot". If all went well, you are done. If not, repeat steps 1-6 above and take another stab at it.
This was all Greek to me until Joe Morris lent a hand to help explain the process of creating the chroot environment. It all works just the way it is supposed to. As always BACKUP what you can't afford to lose.
David, Thank You for the detailed explanation. It will be very helpful if it will let me do what I want to do. Not sure I understand the chroot environment though. It means that you are creating a "separate" filesystem which allows you to do whatever you want to the "regular" filesystem? even those portions that you have emulated in the chroot environment? Hope I am making myself clear here. Ex: suppose I wanted to rename a mount point to something else. eg. / to /11.0 ? and then /10.3 to / . Sounds crazy I know but I am desperate to get my 10.3 booting again. I need to have both systems unmounted to do that. Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 05 September 2008 10:13:12 pm Bob S wrote:
On Friday 05 September 2008 12:29:20 David C. Rankin wrote:
Bob S wrote:
Hello SuSE people,
Should I not be able to run Yast in the rescue system? I logon as root type yast (or yast2) and I get a bash -command not found.
Bob S
Bob,
After having been through something similar with updates that rendered a system unbootable and needing to use the rescue function on the dvd, here is the short version for gaining full access, including yast, to the broken system:
(1) boot from the install DVD
(2) choose "Rescue System", login as "root" (no password needed)
(3) look at "cat /proc/partitions" to determine which partitions need to be mounted under /mnt to create a chroot environment of your full original system. (the default install will require '/' and '/home' to be mounted). You should be able to tell by the relative sizes of the partitions which partition is / and which is /home. You may also need to look at "ls -l /dev/disk/by-id" for disk by-id mappings if you run into any trouble.
(4) "mount" the partitions under /mnt, then "bind" dev/, proc/ and sys/ and chroot /mnt. (your '/' partition will be '/mnt' after you complete all mounts and before you chroot /mnt) **Note: mount the / partition first otherwise the mount point for /home will not exist yet. _Example_ with '/'=/dev/sda6 and '/home'=/dev/sda7:
mount /dev/sda6 /mnt
[** Note: at this point you can check /mnt/etc/fstab for the original devices and mount points used and unmount/adjust if necessary] continuing:
mount /dev/sda7 /mnt/home mount -o bind /dev /mnt/dev mount -o bind /proc /mnt/proc mount -o bind /sys /mnt/sys cd /mnt chroot /mnt
(5) Now you can run yast and everything else you need to fix your system
(6) After you are done, type "exit" to exit the chroot environment and then "reboot". If all went well, you are done. If not, repeat steps 1-6 above and take another stab at it.
This was all Greek to me until Joe Morris lent a hand to help explain the process of creating the chroot environment. It all works just the way it is supposed to. As always BACKUP what you can't afford to lose.
David,
Thank You for the detailed explanation. It will be very helpful if it will let me do what I want to do. Not sure I understand the chroot environment though. It means that you are creating a "separate" filesystem which allows you to do whatever you want to the "regular" filesystem? even those portions that you have emulated in the chroot environment? Hope I am making myself clear here.
Ex: suppose I wanted to rename a mount point to something else. eg. / to /11.0 ? and then /10.3 to / . Sounds crazy I know but I am desperate to get my 10.3 booting again. I need to have both systems unmounted to do that.
Bob S
The chroot (command and environment) is used too boot in a bootable, ie. rescue system, than switch to system that has a problem. The /mnt of rescue system is used to mount on it partition that has a problem. There is no need to create special mount point, as once you execute chroot /mnt all you can see is your 10.3 system directory tree, every command will be executed from 10.3 directory tree, and every change is done to your 10.3. The only things that belong to rescue are kernel related directories /proc, /sys and /dev. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Bob S -
Damon Register -
David C. Rankin -
jdd sur free -
Michael S. Dunsavage -
Rajko M.