02-11-2017, 05:39 PM
This is not a bug, just a brief mention of a recent test with a dual boot (Windows 10, LL) machine. The Ubu rescue disk does not pick up the LL description entry in grub correctly. Had to enter it manually after I purposely crashed Windows 10 into BSOD by interrupting updates with a hard shutdown in order to make it necessary to reinstall Windows boot to MBR to get out of recovery mode. Don't recommend Ubu for recovery for LL lost boot on dual boot Windows 10. Also LL live disk method recovers LL boot but only reverts to BSOD boot for Windows 10. Supergrub 2 (Rescatux) recovered LL boot correctly but also sent Windows back to BSOD (pointed to stalled recovery again.) Made me chuckle at myself a little at that point, realizing immediately both had actually recovered the grub menu. In dual boot certain Windows BSOD situations, those that require restoring Windows MBR, even though grub still remains there, most users will have to enter grub entries for LL manually from the grub menu, or a terminal if they want their Windows boot to remain unchanged. Rescue disks will only muck things up. It is easier for new users to keep a copy of the LL grub config file to refer to. I have often thought that a minimal fat32 partition could be setup at installation to store grub text entries for later use by inexperienced users with dual boot situations. Even though I can edit grub from Windows 10 if necessary new users of course would not be able to. I don't think the most commonly used rescue disks are good for new users dual booting with Windows 10 when BSOD situations occur with Windows because their failure will generally cause the users to purchase unnecessary Windows repair tools in order to fix their systems. I don't think we should recommend methods that encourage more income for MS. Also since Windows 10, most of the advice about mounted partitions and flags is bunk and changing them with NTFS tools from Linux will not pull Windows 10 out of BSOD recovery mode boot, just reproduce it infinitely. BSOD mode is a post grub menu, switched MBR mode. All that is needed is a Windows 7,8, or 10 install disk to reinstall the MBR which it finds immediately, not more MS purchases, but of course that ruins the LL grub boot menu entry because Windows does not recognize ext4 partitions though it does recognize the grub menu already there in its MBR. Easiest to keep a copy of LL's grub menu entry. Also root continues to be a nuisance in Ubu recovery instances, and the no passwd root terminal does not work anymore. There is a certain insane paranoia about personal (in the room) security seizing developers these days for no good reason. Makes sense for some countries I guess, but it is an absolutely false and trivial suggestion that taking away these normal nix repair tools is an improvement to OS security. Nothing is better than encryption period. Everything else is a waste of time, and becoming a nuisance for IT people, and one that costs ordinary users more money. Desktop Linux should get off the stupid in the room security bandwagon altogether, and just advise encryption for security. What can the inexperienced user do with Ubu, but create a root user and password in advance, and of course that scares away most users because of the error messages when doing so. LL should get on its own bandwagon and eliminate this issue in its distro. It is simply NOT a security issue for Desktop Linux.
TC
TC
All opinions expressed and all advice given by Trinidad Cruz on this forum are his responsibility alone and do not necessarily reflect the views or methods of the developers of Linux Lite. He is a citizen of the United States where it is acceptable to occasionally be uninformed and inept as long as you pay your taxes.
