On 10/06/2018 07:04 AM, George from the tribe wrote:
On 10/05/2018 06:18 PM, David C. Rankin wrote:
On 10/04/2018 05:58 PM, George from the tribe wrote:
Of course running everything in the vm is slower than running things directly, but this will enable me to do what I want to do when I have to be in windows.
Move everything to SSD and as long as you aren't trying to run something like Plasma or Gnome3, you won't notice any difference at all. I have Win7 and 15 virtualized on a 42.3 install on SSD, and both boot within 12 seconds and the desktops are instantaneous. I wouldn't have believed it until I tried it. The 42.3 host will boot from cold-start to full KDE3 desktop in 11 seconds and change.
Cost wise you pay a bit more for less storage, but I'll gladly give up my old 1T platters for 512G (or 256G) nand-3d SSD any day.
That's a good idea. I have put in an SSD on my small laptop (that I labeled laptop 2 below) and had that experience until I installed Leap 15. Something about the install of Leap 15 made the startup and shutdown process much slower. It sort of hangs for awhile, but I haven't had time to troubleshoot it yet. I hope to get to that problem soon.
I know they moved things from /etc/sysconfig/network/config around, but in 42.3, setting: WAIT_FOR_INTERFACES="1" eliminated 30+ seconds from boot.
I might also note that I just saw on Amazon that you can purchase a 1TB internal laptop SSD for around $150. So this looks like a really good option. It could be a complete game changer. I saw that the windows people are having trouble with the latest microsoft update - some people have had it erase all their data from anything that wasn't in onedrive. The only reason I ever boot into windows is only for this one program that I just can't get to run well on the linux side, out of slowness. If the SSD made the difference there, I could forego windows completely.
Yes, I was laughing about the 1809 screw-up of Intel Audio drivers, every feature update release rains terror down on the normal computing public. Not to mention your computer is disabled and held hostage for 2-10 hours while the update tries to figure out how to install without bricking your system. Really makes you appreciate the Linux problems of worrying about shaving a few more seconds off boot, but knowing either way it will be your same old rock solid desktop when it comes up -- even if you have time for a few more sips of coffee in between. I learned long ago with win10 to stay on the corporate track, 1703 with updates set to "Windows Updates for Business" and feature updates deferred for 365 days (disabled). I've tried 1709 and 1803, but ended up rolling back the updates. Nothing new I wanted from them, but plenty of headache I didn't. Always glad to just get the updates done and then "Restart", set the hwclock to UTC in the BIOS, and press F9 to boot from Drive 2 and have Leap fire back up... so I cold go on with getting work done. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org