Re:Arch Linux adapted for Windows Subsystem for Linux
by piaste on Thursday September 15, 2016 @04:04AM
(#12504246)
Personally - this is a question of individual preference, though - I do not mind the OS boot time itself very much (to a degree). Whether the system takes ten seconds or two minutes from reset/power-on to the login screen does not make much of a difference, to me, psychologically. But once I log in, I need to open all of these programs, make sure the windows are in the right place, SSH connections to certain machines are open, etc. I admit I am kind of obsessive-compulsive about this, but this is a far greater (psychological) barrier to rebooting than the OS boot time itself.
Hibernation should solve this issue, no? It certainly does on single-OS machines. I practically only shut down my desktop when I want to tweak the hardware and/or BIOS.
It's a little more annoying for dual-OS because there is a 'hibernate' command and a 'reboot' command, but I'm not aware of a 'hibernate-then-reboot' one, so you have to manually hit the power button after hibernating instead.
Re:Arch Linux adapted for Windows Subsystem for Linux
by laurent123456 on Thursday September 15, 2016 @05:00AM
(#12504467)
Hibernation would work but then you have to make sure that the two operating systems don't share any drive (such as a data drive), because writing on a drive mounted by an hibernated system can cause all kind of weird issues.
Re:Arch Linux adapted for Windows Subsystem for Linux
by tremon on Thursday September 15, 2016 @07:49AM
(#12505234)
Boot times do not matter for hardware OSes. For containers and VMs, there is much better use-case for short boot times: on-demand scaling.
Re:Arch Linux adapted for Windows Subsystem for Linux
by kochthesecond on Thursday September 15, 2016 @06:54AM
(#12504892)
I dont care about long boot times either, it's opening chrome and all my terminals that is a pain in the ass.
Re:Arch Linux adapted for Windows Subsystem for Linux
by Wofiel on Thursday September 15, 2016 @03:10AM
(#12504020)
You can run things like VcXsrv or Xming, then you can pretty much run anything through them, including window managers. When WSL went mainline I had all sorts of fun playing with it, building Servo and VLC and running them in a tiling wm, just because I could. (Not exactly productive time though)
> Boot times are very short with SSDs so restarting is not a problem.
Personally - this is a question of individual preference, though - I do not mind the OS boot time itself very much (to a degree). Whether the system takes ten seconds or two minutes from reset/power-on to the login screen does not make much of a difference, to me, psychologically. But once I log in, I need to open all of these programs, make sure the windows are in the right place, SSH connections to certain machines are open, etc. I admit I am kind of obsessive-compulsive about this, but this is a far greater (psychological) barrier to rebooting than the OS boot time itself.
I do not use Windows at home, and my work laptop runs Windows 7 (I intend to keep it that way, too), so I have not been able to play with the Linux subsystem on Windows. But if you consider it as an alternative to Cygwin (which I do use), it sound kind of nice. Now if only Windows had a native, builtin X server... ;-)
EDIT: With Cygwin or the Linux subsystem, driver issues are not an issue, of course, because hardware is still managed by the Windows kernel and Windows drivers.