Hi Azul,

This scenario is not NixOS so there's no need to rollback anything.
I'm simply using the nix package manager.

But yes, if the filestorage goes down, the nix store will not be
accessible. This is something we'll have to live with if it happens.

R

On 01/07/16 22:38, Azul wrote:
> how would you rollback a broken system if the /nix store was remote and
> the box wouldnt boot or have no network ?
> 
> On 1 July 2016 at 21:34, Layus <layus...@gmail.com
> <mailto:layus...@gmail.com>> wrote:
> 
>     I never sait it was a good idea, just soemthing worth investigating.
> 
>     Now, this has been discussed on the ML already
> 
>     See for example
>     [Nix-dev] Sharing the Nix store between systems
>     <http://lists.science.uu.nl/pipermail/nix-dev/2011-December/007381.html> 
>     /Rickard Nilsson
>     /[Nix-dev] nix on compute cluster?
>     <http://lists.science.uu.nl/pipermail/nix-dev/2014-October/014584.html> 
> //Andreas
>     Herrmann
> 
>     //And more generally Google search on
>     site:http://lists.science.uu.nl/pipermail/nix-dev/ :-).
> 
>     -- Layus.
> 
> 
>     On 01/07/16 21:55, Renato Alves wrote:
>>     I never tried it with sockets, only tcp ports.
>>
>>     I need to move the socket to a different location. Currently it also
>>     sits on NFS. I can play with symlinks making it point to a local disk.
>>
>>     The entire setup sounds terribly hackish though.
>>
>>     If anyone has better alternatives I'd love to hear them.
>>
>>     Thanks,
>>     R
>>
>>     On 01/07/16 20:51, Layus wrote:
>>>     Just one idea off the top of my head: Would it be possible to forward
>>>     the unix socket of the daemon ?
>>>
>>>     -- Layus ?
>>>
>>>     On 01/07/16 15:10, Renato Alves wrote:
>>>>     Hi everyone,
>>>>
>>>>
>>>>     Recently I've been trying to setup nix on a multiple-machine shared
>>>>     environment. At the moment I have one machine setup with nix-daemon
>>>>     running from a store in a custom location (/shared/myuser/nix). This
>>>>     location is shared via NFS with several other machines. This is all
>>>>     still pretty new to me as I've only recently started using nix and
>>>>     haven't used nixos yet.
>>>>
>>>>     Before setting up nix-daemon I ran into some problems with database
>>>>     corruption (sqlite) due to concurrent processes. With nix-daemon these
>>>>     have gone away.
>>>>
>>>>     One limitation that I identified recently is that on any of the other
>>>>     machines that do not have nix-daemon running (but have read access to
>>>>     the store) I can run commands from the store without problems but
>>>>     cannot, for instance, use nix-shell.
>>>>     So I thought of spawning a nix-daemon instance on those machines but 
>>>> I'm
>>>>     not sure what is the best way to set it up without risking DB 
>>>> corruption
>>>>     again.
>>>>
>>>>     These are the requirements I'd like to meet:
>>>>      * /shared/myuser/nix is shared across multiple machines with the same
>>>>     architecture (x86_64-linux).
>>>>      * All machines should be able to use nix-shell or any nix related
>>>>     command, including requesting installation of packages.
>>>>      * Only some machines are allowed to compile. Machines that are not
>>>>     allowed should rely on something like remote-systems.conf to distribute
>>>>     work.
>>>>
>>>>     Is this kind of setup currently possible with nix? If so, can someone
>>>>     provide some guidance?
>>>>
>>>>
>>>>     Thanks,
>>>>     Renato
>>>>
>>>>
>>>>
>>>>     _______________________________________________
>>>>     nix-dev mailing list
>>>>     nix-dev@lists.science.uu.nl <mailto:nix-dev@lists.science.uu.nl>
>>>>     http://lists.science.uu.nl/mailman/listinfo/nix-dev
>>>
>>>
>>>     _______________________________________________
>>>     nix-dev mailing list
>>>     nix-dev@lists.science.uu.nl <mailto:nix-dev@lists.science.uu.nl>
>>>     http://lists.science.uu.nl/mailman/listinfo/nix-dev
>>>
>>
>>
>>     _______________________________________________
>>     nix-dev mailing list
>>     nix-dev@lists.science.uu.nl <mailto:nix-dev@lists.science.uu.nl>
>>     http://lists.science.uu.nl/mailman/listinfo/nix-dev
> 
> 
> 
>     _______________________________________________
>     nix-dev mailing list
>     nix-dev@lists.science.uu.nl <mailto:nix-dev@lists.science.uu.nl>
>     http://lists.science.uu.nl/mailman/listinfo/nix-dev
> 
> 
> 
> 
> _______________________________________________
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
> 

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Reply via email to