On Wed, Jan 24, 2018 at 4:22 AM, Bill Maidment <[email protected]> wrote: > All sorted. > The second USB stick worked OK before doing the chroot.
Good. I was wondering why the first stick didn't have network enabled when it booted. Not all drivers work perfectly from some USB sticks and the minimal kernel present on them, but I've certainly used them myself to do recovery work. I'm trying to figure out why you're doing dual boot. Does the Windows box not have enough resources to run VirtualBox, and run your working Linux in a VM ? I've found that very useful for development work, since Steam doesn't work as well on Linux boxes to give access to games I might like to play with all resources available. > -----Original message----- >> From:Bill Maidment <[email protected]> >> Sent: Wednesday 24th January 2018 17:17 >> To: R P Herrold <[email protected]> >> Cc: [email protected] >> Subject: RE: Problem recreating grub2 menu in SL7 dual boot with Win10 >> >> Thanks for your response >> >> > Packages are partitioned into a main and sub-packages, so that >> > the bloat of un-needed matter is avoided. UEFI is relatively >> > new, and until Windows 10, not really mandated by Microsoft >> > installations. Also the needed hardware (a TPM chip) was not >> > universally present, and so that sub-package would seem to be >> > bloat to most people >> >> Understood. >> >> > As to how to get a copy, using an second machine to retrieve >> > the needed package, and placing it on a data stick comes to >> > mind. >> >> But how to get it into the system that can only be booted in rescue mode >> from my USB stick? >> I will try using a second USB stick >> >> Cheers >> Bill >> >>
