[Nix-dev] configurations repository

Tue Nov 4 22:16:03 CET 2014

On 11/04/2014 09:13 PM, Arseniy Seroka wrote:
> That's awesome idea. But I think we have to add lots of comments to this 
> examples (that help a lot while using live code). Or maybe just provide 
> some ideal configs with comments and other without them.

It's impossible to tell what you're replying to, especially as you ar
top-posting.

> 
> On 4 November 2014 23:07:04 nix-dev-request at lists.science.uu.nl wrote:
> 
>> Send nix-dev mailing list submissions to
>> 	nix-dev at lists.science.uu.nl
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> 	http://lists.science.uu.nl/mailman/listinfo/nix-dev
>> or, via email, send a message with subject or body 'help' to
>> 	nix-dev-request at lists.science.uu.nl
>>
>> You can reach the person managing the list at
>> 	nix-dev-owner at lists.science.uu.nl
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of nix-dev digest..."
>>
>>
>> Today's Topics:
>>
>>    1. Hydra failure types and Nix support (Michael Raskin)
>>    2. [***SPAM***] configurations repository (Michael Raskin)
>>    3. Fwd: Re:  NixOS Live CD (Graphic) Boot Failure (J. Brian Kelley)
>>    4. Re: Fwd: Re:  NixOS Live CD (Graphic) Boot Failure
>>       (Vladim?r ?un?t)
>>    5. Re: NixOS Live CD (Graphic) Boot Failure (J. Brian Kelley)
>>    6. Re: NixOS Live CD (Graphic) Boot Failure (Wout Mertens)
>>    7. Re: deploying nix-built software to non-nix linux systems
>>       (Paul Colomiets)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Tue, 04 Nov 2014 18:35:06 +0300
>> From: Michael Raskin <7c6f434c at mail.ru>
>> Subject: [Nix-dev] Hydra failure types and Nix support
>> To: nix-dev at lists.science.uu.nl
>> Message-ID: <E1Xlg1e-0004dP-8T.7c6f434c-mail-ru at smtp26.mail.ru>
>> Content-Type: text/plain; charset="UTF-8"
>>
>> 16596922		mda_lv2.i686-linux	
>> 16591197		mongodb.x86_64-linux	
>> 16599836		qbittorrent.i686-linux	
>> 16599870		qbittorrent.x86_64-linux	
>> 16590792		syslogng_incubator.i686-linux	
>> 16604362		syslogng_incubator.x86_64-linux	
>>
>> Of these I think that all failures except mongo are transient, and mongo
>> has just declared that 10GiB /tmp/ is too small ? rebuilding with
>> a larger /tmp/ to check.
>>
>> 1. Hydra seems to merge ?new failures? and ?still failing? in the same
>> tab. It may be what we want, but is it intended to call the tab ?still
>> failing??
>>
>> 2. Apparently real failures end with ?builder failed with code ??.
>> Should the failures without that line be marked in a different way?
>>
>> And yes, mda_lv2, qbittorrent and syslogng_incubator can be restarted?
>>
>>
>>
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Tue, 04 Nov 2014 19:00:31 +0300
>> From: Michael Raskin <7c6f434c at mail.ru>
>> Subject: [Nix-dev] [***SPAM***] configurations repository
>> To: nix-dev at lists.science.uu.nl
>> Message-ID: <E1XlgQF-0004Cc-QS.7c6f434c-mail-ru at smtp45.i.mail.ru>
>> Content-Type: text/plain; charset="UTF-8"
>>
>> Previously we had configurations repository in SVN. I even continued to
>> update my configuration there long after Git migration. Its useful
>> function was that I could easily give a link like ?see viric's
>> configuration?.
>>
>> I don't think comprehensiveness is that important for such a repository,
>> but as we currently have >50 committers, if half of use commits some
>> of our configurations, it would again be a useful collection of examples
>> of live Nix use.
>>
>> Should we create it (with the same permissions as NixPkgs, probably)?
>> I always consider such live documentation a good thing for initial
>> evaluation of a language?
>>
>>
>>
>>
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Tue, 04 Nov 2014 12:26:32 -0500
>> From: "J. Brian Kelley" <jbk at teksavvy.com>
>> Subject: [Nix-dev] Fwd: Re:  NixOS Live CD (Graphic) Boot Failure
>> To: Wout Mertens <wout.mertens at gmail.com>
>> Cc: nix-dev <nix-dev at lists.science.uu.nl>
>> Message-ID: <54590C48.1000004 at teksavvy.com>
>> Content-Type: text/plain; charset=utf-8; format=flowed
>>
>> Well, I reinstalled Linux Mint 17 (went smoothly) and sadly there is no
>> /proc/config.gz .
>>
>> Is there any means to direct the screen output to my usb flash drive? Or
>> at least stop it scrolling until I have had a chance to read things? Is
>> there possibly a "debug" option that can be invoked?
>>
>>
>>
>>
>>
>> ------------------------------
>>
>> Message: 4
>> Date: Tue, 04 Nov 2014 18:35:16 +0100
>> From: Vladim?r ?un?t <vcunat at gmail.com>
>> Subject: Re: [Nix-dev] Fwd: Re:  NixOS Live CD (Graphic) Boot Failure
>> To: nix-dev at lists.science.uu.nl
>> Message-ID: <54590E54.5020107 at gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> On 11/04/2014 06:26 PM, J. Brian Kelley wrote:
>>> Well, I reinstalled Linux Mint 17 (went smoothly) and sadly there is no
>>> /proc/config.gz .
>>
>> sudo modprobe configs
>> may be needed to access that file.
>>
>> Vladimir
>>
>>
>> -------------- next part --------------
>> A non-text attachment was scrubbed...
>> Name: smime.p7s
>> Type: application/pkcs7-signature
>> Size: 3251 bytes
>> Desc: S/MIME Cryptographic Signature
>> Url : 
>> http://lists.science.uu.nl/pipermail/nix-dev/attachments/20141104/731f46a5/attachment-0001.bin
>>
>> ------------------------------
>>
>> Message: 5
>> Date: Tue, 04 Nov 2014 14:17:41 -0500
>> From: "J. Brian Kelley" <jbk at teksavvy.com>
>> Subject: Re: [Nix-dev] NixOS Live CD (Graphic) Boot Failure
>> To: Wout Mertens <wout.mertens at gmail.com>
>> Cc: nix-dev <nix-dev at lists.science.uu.nl>
>> Message-ID: <54592655.3070702 at teksavvy.com>
>> Content-Type: text/plain; charset=utf-8; format=flowed
>>
>> As a last attempt, I burned the minimal ISO and tried booting it.
>>
>> Exactly the same result - goes nicely until it shows the login prompt
>> whereupon the error message triplets start (doesn't even newline down
>> from the prompt so the first error message is offset somewhat).
>>
>> Seems a bit strange that they start at the point that a keyboard input
>> is required - could the fact that the keyboard is PS/2 connected be a
>> factor?
>>
>> I'm really grasping at straws - do I submit a bug report that simply
>> says install iso(s) don't work?
>>
>>
>>
>>
>> ------------------------------
>>
>> Message: 6
>> Date: Tue, 04 Nov 2014 19:25:09 +0000
>> From: Wout Mertens <wout.mertens at gmail.com>
>> Subject: Re: [Nix-dev] NixOS Live CD (Graphic) Boot Failure
>> To: "J. Brian Kelley" <jbk at teksavvy.com>
>> Cc: nix-dev <nix-dev at lists.science.uu.nl>
>> Message-ID:
>> 	<CAO3V83JWq3mOj5p2mKDZcbuFEnwE2SRNeeVM4xsDnCKM2CykEw at mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Can you try the modprobe configs that was suggested?
>>
>> Opening an issue won't help, we can't reproduce and we're the same guys :-)
>>
>> On Tue, Nov 4, 2014, 20:17 J. Brian Kelley <jbk at teksavvy.com> wrote:
>>
>>> As a last attempt, I burned the minimal ISO and tried booting it.
>>>
>>> Exactly the same result - goes nicely until it shows the login prompt
>>> whereupon the error message triplets start (doesn't even newline down
>>> from the prompt so the first error message is offset somewhat).
>>>
>>> Seems a bit strange that they start at the point that a keyboard input
>>> is required - could the fact that the keyboard is PS/2 connected be a
>>> factor?
>>>
>>> I'm really grasping at straws - do I submit a bug report that simply
>>> says install iso(s) don't work?
>>>
>>>
>>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: 
>> http://lists.science.uu.nl/pipermail/nix-dev/attachments/20141104/a4568912/attachment-0001.html
>>
>> ------------------------------
>>
>> Message: 7
>> Date: Tue, 4 Nov 2014 22:06:34 +0200
>> From: Paul Colomiets <paul at colomiets.name>
>> Subject: Re: [Nix-dev] deploying nix-built software to non-nix linux
>> 	systems
>> To: Anders Papitto <anderspapitto at gmail.com>
>> Cc: nix-dev <nix-dev at lists.science.uu.nl>
>> Message-ID:
>> 	<CAA0gF6rb8bsChF3a9Z_ksSaYKvZq9LhJ1g_Gi4uVp=BiVAdDrA at mail.gmail.com>
>> Content-Type: text/plain; charset=UTF-8
>>
>> Hi Anders,
>>
>> On Tue, Nov 4, 2014 at 1:36 AM, Anders Papitto <anderspapitto at gmail.com> wrote:
>>> Hello,
>>>
>>> I'm interested in using nix/nixos to build an application with its
>>> full set of dependencies, and then deploy it to non-nixos machines as
>>> a self-contained package (up to and including the system libraries),
>>> without root privileges. Ideally I would like to not require that any
>>> nix tools be available on the target system. The perfect workflow
>>> would be something like
>>>
>>> # on any linux system
>>> $ wget https://some/path/to/my-app.tar.gz
>>> $ tar -xf my-app.tar.gz
>>> $ ./my-app/bin/my-app # run the application -> it should not try to
>>> access anything outside ./my-app
>>>
>>> Is this possible? I haven't been able to find any resources on
>>> deploying to a non-nix systems.
>>>
>>
>> Not easily but you can do that in two cases:
>>
>> 1. If you haven't root privileges, but can ask admin to make /nix owned by you
>>
>> 2. If you have recent kernel (>=3.8) with CONFIG_USER_NS enabled
>> (which is by default),
>>
>>
>> --
>> Paul
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> nix-dev mailing list
>> nix-dev at lists.science.uu.nl
>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>>
>>
>> End of nix-dev Digest, Vol 113, Issue 9
>> ***************************************
> 
> 
> _______________________________________________
> nix-dev mailing list
> nix-dev at lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
> 

-- 
Mateusz K.