Maybe I'm in the minority but I prefer keeping my GNU/Linux and Windows installations separate, with each OS on its own drive. My Linux setup is secure, free of proprietary software and under my full control. When I run tcpdump, I'm met with a clean log where every packet is one I recognize. I get to use my favorite window manager (awesomewm) and I don't have to worry about forced updates. My Windows install is quite…
This is pretty OT, but I feel like it is worth pointing out: > 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 onc…
Arch Linux adapted for Windows Subsystem for Linux
111–120 of 163 posts
Re: Arch Linux adapted for Windows Subsystem for Linux
#112Earlier quoted context omitted.
This is pretty OT, but I feel like it is worth pointing out: > 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 onc…
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)
Re: Arch Linux adapted for Windows Subsystem for Linux
#113Maybe I'm in the minority but I prefer keeping my GNU/Linux and Windows installations separate, with each OS on its own drive. My Linux setup is secure, free of proprietary software and under my full control. When I run tcpdump, I'm met with a clean log where every packet is one I recognize. I get to use my favorite window manager (awesomewm) and I don't have to worry about forced updates. My Windows install is quite…
Re: Arch Linux adapted for Windows Subsystem for Linux
#114Earlier quoted context omitted.
You need to run separate GPUs to achieve this though don't you?
Not necessarily. I managed to get it working with a single GPU, by unbinding it from the host and binding it to the VM. Unfortunately it does mean that you have to stop X11 and all programs, and going back doesn't work (the GPU freezes the machine when the proprietary NVIDIA driver loads), but it's still better than dual-booting because background services continue to run. It certainly is easier with separate GPUs, t…
Re: Arch Linux adapted for Windows Subsystem for Linux
#115Maybe I'm in the minority but I prefer keeping my GNU/Linux and Windows installations separate, with each OS on its own drive. My Linux setup is secure, free of proprietary software and under my full control. When I run tcpdump, I'm met with a clean log where every packet is one I recognize. I get to use my favorite window manager (awesomewm) and I don't have to worry about forced updates. My Windows install is quite…
I'm excited because everyone at my company doesn't develop on linux because "we know visual studio" and "setting up a build environment will take too much time".
With the linux subsystem for windows, we have the ability to push them to slowly start developing new systems on linux. So I'm super happy about it.
Re: Arch Linux adapted for Windows Subsystem for Linux
#116I am currently dual booting between Arch Linux and Windows 10. Moving to something like this one day makes me conflicted. On one hand I feel like I would betray open source, on the other hand I wouldn't have to restart my machine to play games...
Re: Arch Linux adapted for Windows Subsystem for Linux
#117Maybe I'm in the minority but I prefer keeping my GNU/Linux and Windows installations separate, with each OS on its own drive. My Linux setup is secure, free of proprietary software and under my full control. When I run tcpdump, I'm met with a clean log where every packet is one I recognize. I get to use my favorite window manager (awesomewm) and I don't have to worry about forced updates. My Windows install is quite…
This is pretty OT, but I feel like it is worth pointing out: > 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 onc…
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
#118Maybe I'm in the minority but I prefer keeping my GNU/Linux and Windows installations separate, with each OS on its own drive. My Linux setup is secure, free of proprietary software and under my full control. When I run tcpdump, I'm met with a clean log where every packet is one I recognize. I get to use my favorite window manager (awesomewm) and I don't have to worry about forced updates. My Windows install is quite…
(*Or a boot loader on a separate USB drive which is never plugged in while running Windows)
Re: Arch Linux adapted for Windows Subsystem for Linux
#119Earlier quoted context omitted.
This is pretty OT, but I feel like it is worth pointing out: > 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 onc…
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…