4 ms·

Apparently there is company switching from using Gentoo to NixOS. Gentoo seems a bit of a weird fit for production, unless you can compile packages on another s

Apparently there is company switching from using Gentoo to NixOS. Gentoo seems a bit of a weird fit for production, unless you can compile packages on another server and deploy them (last time I used it was 10 years ago so I don't know if that's a thing).

kragniz 10y ago
Gentoo's not such a weird choice if you want to have a lot of control. CoreOS is getting pretty popular these days, and that's gentoo based.
- deadbunny 10y ago
  CoreOS isn't what I would call a general purpose server OS though, it has to do one thing and do it well.
  - deleted 10y ago
    [deleted]
Slackwise 10y ago
They could be using Portage to build static images of variously configured systems like Google does for Chrome OS[1]. Portage is a very powerful and versatile build tool. [1]: https://www.chromium.org/chromium-os/how-tos-and-troubleshooting/portage-build-faq https://www.chromium.org/chromium-os/how-tos-and-troubleshoo...
hawski 10y ago
You can build binary packages after successful compilation/installation (every time if you want) or only build binary package. Then you can share binary packages between all hosts or have one host that is building packages for all others. You can restrict portage to only install binary packages. Doing all this can be a bit tedious, but with current computer's power it is quite fast process. You will get lean system that can be like no other - that's a curse and a blessing. Nevertheless I speak from the position of a desktop Gentoo user from the past, that recently used Gentoo for personal R&D project. It certainly is better experience than few years ago. You can install only run-time needed packages on your host or even to different directory (for chroot). One thing that I don't know how to get over is to not have development files inside binary packages. Like include files. Also I had to manually copy gcc libraries to such a chroot, because I didn't want to install whole gcc there.
drvdevd 10y ago
I feel that any system that can benefit from a high level of control (e.g. any production system) can also benefit from a source based distribution model. Of course the sysadmins using it need to know how to take advantage of that control (and e.g. maybe write some C). And of course, you can get the same thing with any modern package manager but then you have to be intimately familiar with the way packaging is built from source on that distro and how to build and run your own package hosts. Nix is quite unique (and elegant IMO), in that it: 1) forces you to learn at least a bit of a DSL to use and understand it and 2) seems to put you somewhere in between these two "extremes" of control. I don't know how easy it is to run a hydra build server (it didn't look very easy last time I checked), but I do know the nix DSL gave me a clean place to specify almost exactly how my system had differed from a base install.

kragniz 10y ago

Gentoo's not such a weird choice if you want to have a lot of control. CoreOS is getting pretty popular these days, and that's gentoo based.

deadbunny 10y ago
CoreOS isn't what I would call a general purpose server OS though, it has to do one thing and do it well.
- deleted 10y ago
  [deleted]

Slackwise 10y ago

They could be using Portage to build static images of variously configured systems like Google does for Chrome OS[1]. Portage is a very powerful and versatile build tool. [1]: https://www.chromium.org/chromium-os/how-tos-and-troubleshooting/portage-build-faq https://www.chromium.org/chromium-os/how-tos-and-troubleshoo...

hawski 10y ago

You can build binary packages after successful compilation/installation (every time if you want) or only build binary package. Then you can share binary packages between all hosts or have one host that is building packages for all others. You can restrict portage to only install binary packages. Doing all this can be a bit tedious, but with current computer's power it is quite fast process. You will get lean system that can be like no other - that's a curse and a blessing. Nevertheless I speak from the position of a desktop Gentoo user from the past, that recently used Gentoo for personal R&D project. It certainly is better experience than few years ago. You can install only run-time needed packages on your host or even to different directory (for chroot). One thing that I don't know how to get over is to not have development files inside binary packages. Like include files. Also I had to manually copy gcc libraries to such a chroot, because I didn't want to install whole gcc there.

drvdevd 10y ago

I feel that any system that can benefit from a high level of control (e.g. any production system) can also benefit from a source based distribution model. Of course the sysadmins using it need to know how to take advantage of that control (and e.g. maybe write some C). And of course, you can get the same thing with any modern package manager but then you have to be intimately familiar with the way packaging is built from source on that distro and how to build and run your own package hosts. Nix is quite unique (and elegant IMO), in that it: 1) forces you to learn at least a bit of a DSL to use and understand it and 2) seems to put you somewhere in between these two "extremes" of control. I don't know how easy it is to run a hydra build server (it didn't look very easy last time I checked), but I do know the nix DSL gave me a clean place to specify almost exactly how my system had differed from a base install.