From: rohit yadav <rohityadav@utexas.edu>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: [Non-root Guix]: Unable to build guix
Date: Thu, 2 May 2019 17:13:36 -0500 [thread overview]
Message-ID: <CAGKZdmZxSi_sj85Lsu3dGvzkH4zaQjjPzPNgRYvNUc6NDSgHRg@mail.gmail.com> (raw)
In-Reply-To: <87bm0kwnag.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 2033 bytes --]
On Thu, May 2, 2019 at 4:37 PM Ricardo Wurmus <rekado@elephly.net> wrote:
>
> Hi Rohit,
>
> > Unfortunately, I am stuck at Centos6 which uses old
> > kernel 2.6.32-696.el6.x86_64. I am able to install nix on this system at
> > non-root location. It works fine but NIx community has decided to use 2.0
> > which only works on newer kernel. Therefore, I have to now backport
> several
> > packages. Making it really hard because lot of packages are broken. Its
> > manageable but not ideal. Whereas the guix seems to be independent of
> > kernel (atleast that is my assumption so far).
>
> I feel your pain. I still need to sometimes touch CentOS 6 systems.
> Guix is largely kernel-independent but the GNU C library is not. It has
> a minimum kernel requirement of 3.x (I don’t know the exact version).
>
> We have patched it to accept the heavily patched RHEL 6 kernel, because
> it does seem to provide backports of all the features the GNU C library
> depends on. You may run into some problems with some packages, though.
> (I think there were problems with JDK and Qt, and I’m not sure if we
> managed to completely work around them.)
>
The JDK is easy to get around so I am fine there. I rarely using any
graphical softwares, so I may be fine here. Its mostly for the purpose of
computing software which I want on the HPC, other personal software I can
work on my machine. But thanks for pointing this out. Learning about lower
level details about the kernel and its dependency has been on my list but
never been able to find time.
>
> > I would also like to suggest an alternative to a root-less installation.
> >> At the HPC cluster where I work we run the guix-daemon as root on a
> >> virtual machine where /gnu/store is a writable NFS share. Every machine
> >> that uses Guix only needs to mount this share as read-only.
> >>
> >
> > This option is not available as I stated earlier, I do not have the root
> permission.
>
> That’s a pity!
> --
> Ricardo
>
>
[-- Attachment #2: Type: text/html, Size: 3365 bytes --]
next prev parent reply other threads:[~2019-05-02 22:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 20:15 [Non-root Guix]: Unable to build guix rohit yadav
2019-05-02 20:33 ` Ricardo Wurmus
2019-05-02 21:14 ` rohit yadav
2019-05-02 21:37 ` Ricardo Wurmus
2019-05-02 22:13 ` rohit yadav [this message]
2019-05-02 21:46 ` Ricardo Wurmus
2019-05-02 22:17 ` rohit yadav
2019-05-04 6:14 ` Chris Marusich
2019-05-05 0:39 ` Mark H Weaver
2019-05-05 8:03 ` Ricardo Wurmus
2019-05-02 20:34 ` Ricardo Wurmus
2019-05-02 21:17 ` rohit yadav
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGKZdmZxSi_sj85Lsu3dGvzkH4zaQjjPzPNgRYvNUc6NDSgHRg@mail.gmail.com \
--to=rohityadav@utexas.edu \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).