Re: [Nix-dev] Nix 1.4 released
Hi,
On 26/02/13 21:25, Vladimír Čunát wrote:
On 02/26/2013 02:46 PM, Eelco Dolstra wrote:
* Language change: The expression ${./path} ... now evaluates to a
string
instead of a path.
That means the such a file isn't copied into the store, and is included as a
plain ./path string, etc. Right?
It *is* copied, so an expression ${./file.sh} foo will evaluate to
/nix/store/...-file.sh foo. Previously it would try to copy ./file.sh foo,
which presumably doesn't exist.
BTW, I believe the hardlink concept is one of worst original UNIX features.
COW copy would make sense, but hardlinks are usually more trouble than worth.
Well, the main problem is that you can make hard links to files you don't own.
We should enable the kernel's hard link restrictions feature in NixOS...
--
Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Nix 1.4 released
On 02/27/2013 12:00 PM, Eelco Dolstra wrote:
On 26/02/13 21:25, Vladimír Čunát wrote:
On 02/26/2013 02:46 PM, Eelco Dolstra wrote:
* Language change: The expression ${./path} ... now evaluates to a string
instead of a path.
That means the such a file isn't copied into the store, and is included as a
plain ./path string, etc. Right?
It *is* copied, so an expression ${./file.sh} foo will evaluate to
/nix/store/...-file.sh foo. Previously it would try to copy ./file.sh foo,
which presumably doesn't exist.
Ah :-) thanks for explaining.
BTW, I believe the hardlink concept is one of worst original UNIX features. COW
copy would make sense, but hardlinks are usually more trouble than worth.
Well, the main problem is that you can make hard links to files you don't own.
We should enable the kernel's hard link restrictions feature in NixOS...
I certainly won't mind it. The option seems to be in-tree since around 3.6.
Vlada
smime.p7s
Description: S/MIME Cryptographic Signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] Oddity with Charon and AWS
Hi all, Today I noticed some strange behavior with the project we're deploying using Charon. When I create a new deployment and run `charon deploy` for the first time, I get a 403 Forbidden error from Amazon as it tries to create the instances: error: EC2ResponseError: 403 Forbidden ?xml version=1.0 encoding=UTF-8? ResponseErrorsErrorCodeUnauthorizedOperation/CodeMessageYou are not authorized to perform this operation./Message/Error/ErrorsRequestID473fc28f-b05d-4de7-be24-4e383dbabf8f/RequestID/Res ponse The really odd thing is that if I run the exactly same `charon deploy` again, it works. My deployment includes an IAM role... I'm wondering if it's trying to create resources using the new IAM role before the role is created, and after the role is created it works the second time. That's just a hypothesis, though; if someone with more knowledge of how Charon works could chime in, I'd appreciate it. Thanks! -Luke ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
