Re:How Tmux Starts Up: An Adventure with Linux Tools (2014)
by davesmith1983 on Saturday July 06, 2019 @02:54PM
(#20371183)
Because you have a clean start every-time you do something. When you use a machine on a daily basis you will have lots of your own scripts, software etc that will be in your path. A lot of times issues occur between machines because your build your instructions or your build scripts whatever have something that is specific to your machine / user account whatever that someone else might not have.
If you use VM you will know that whatever the default VM is in vagrant that you tell them to use will be the same.
It isn't always necessary but tbh I am not in the habit of doing it.
Re:How Tmux Starts Up: An Adventure with Linux Tools (2014)
by jnurmine on Saturday July 06, 2019 @04:10PM
(#20371632)
But still, why VMs? A container seems even better suited for this purpose, since the only thing really required for this use-case is a certain configuration of system software as well as a separation from the rest of the system.
Lxc/lxd can do it, Docker can do it, et cetera, the actual technology does not matter.
As a plus, builds will be faster vs. a VM.
Re:How Tmux Starts Up: An Adventure with Linux Tools (2014)
by davesmith1983 on Saturday July 06, 2019 @04:20PM
(#20371688)
Containers weren't a thing back in 2014. Vagrant IIRC was fairly new and I remember sitting next to a guy that was scripting much of this up.
Re:How Tmux Starts Up: An Adventure with Linux Tools (2014)
by zokier on Saturday July 06, 2019 @04:38PM
(#20371790)
Containers were definitely a thing in 2014; Docker was getting hyped, LXC got 1.0 release after 5 years of developement, and people had been using stuff like OpenVZ long before.
May 19, 2013 Docker - Way better than a VM https://news.ycombinator.com/item?id=5731706
Re:How Tmux Starts Up: An Adventure with Linux Tools (2014)
by davesmith1983 on Saturday July 06, 2019 @04:47PM
(#20371850)
Well what is hyped up on hackernews might see the inside of corporate office in maybe another 10 years time.
Re:How Tmux Starts Up: An Adventure with Linux Tools (2014)
by ciupicri on Saturday July 06, 2019 @04:42PM
(#20371811)
But chroot was a thing back in 2014. Fedora's mock used chroot for building RPMs from source RPMs [1].
[1]: https://fedoraproject.org/wiki/Using_Mock_to_test_package_bu...
Re:How Tmux Starts Up: An Adventure with Linux Tools (2014)
by fredthomsen on Saturday July 06, 2019 @04:20PM
(#20371686)
Have to agree. This has been my main workflow for the past year and a half and the speed increase alone makes it worth it
Re:How Tmux Starts Up: An Adventure with Linux Tools (2014)
by orev on Saturday July 06, 2019 @03:13PM
(#20371294)
At least it was a local virtual machine and not the cloud. Seems like every tutorial I see these days starts with 5 minutes of explaining how to launch some cloud image, as if people have forgotten you can use a local virtual box.
Re:How Tmux Starts Up: An Adventure with Linux Tools (2014)
by asark on Saturday July 06, 2019 @02:57PM
(#20371203)
Makes it trivial to remove any build dependencies afterward, and the instructions/script are the same no matter your distro (delete the VM). Also, only one script or set of instructions needed to install the deps to begin with, if a VM's used and it's always the same distro & version.
Personally, unless I'm running Gentoo I don't like all that crap hanging around my system packages, and this is simpler than learning the best way to deal with it on whatever distro & package manager one happens to compile on, especially if you don't compile from source very often.
Re:How Tmux Starts Up: An Adventure with Linux Tools (2014)
by mav3rick on Saturday July 06, 2019 @01:34PM
(#20370724)
Doesn't want to dirty his home at all ? (Can use a chroot for this?. Maybe source is unstable and can crash machine ?
Re:How Tmux Starts Up: An Adventure with Linux Tools (2014)
by yjftsjthsd-h on Saturday July 06, 2019 @03:55PM
(#20371540)
If an unprivileged userland program (like tmux) can bring down the whole machine, we have bigger problems than an unstable user program.
What's with this need of using virtual machines for almost everything? Why would I need a virtual machine to compile tmux?