all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: unbounded variable from `FATAL: kernel too old` ?
Date: Thu, 31 May 2018 13:57:07 +0200	[thread overview]
Message-ID: <87bmcwox64.fsf@elephly.net> (raw)
In-Reply-To: <CAJ3okZ1-y2tq-w9Y=2e1sRTGSv1zA3cOtL4Due8Z6fv1rCu2Jw@mail.gmail.com>


Hi again,

>>> I am installing the rnaseq Pigx pipeline from
>>> https://github.com/BIMSBbioinfo/pigx/tree/master/pipelines/rnaseq
>>
>> Oh, nice!
>
> Thank you to share !!
> And nice paper ! :-)

Thanks :)

> Do you plan to implement a version with the GWL ?

I’m thinking about it.  There is no current plan to switch to something
else from Snakemake, but once the pipelines have stabilised I’d like to
explore ways to simplify them.  One of the changes might be to remove
extraneous dependencies (e.g. fastqc –> fastq to cut out Java), or to
explore if we can simplify the workflow rules, maybe even to cut out
Snakemake completely.

Currently, Snakemake makes a couple of annoying workarounds necessary
(like linking Rscript to ./pigx_temp/bin and putting that on the PATH,
or to copy scripts to a writable location, or to use “shell” instead of
the more convenient “script” rules…), which I’d love to get rid of.

The GWL may need to acquire a few more changes before I can propose it
as a viable alternative for the team.

>> These variables are defined in Guix since quite some time, so you are
>> probably using a rather old version of Guix.  (The first two are defined
>> in (gnu packages bioinformatics), the latter two in (gnu packages
>> haskell).)
>
> `guix --version` reports 0.14.0.

We haven’t made a new release in a while.  I hope we can make a new
one soon.  In general you should be running “guix pull” on a regular
basis.

> But if the kernel is too old, then somehow the install is not really
> complete. Right ?

Unfortunately, this is a wart in software management with the kernel
Linux.  The big kernel binary is not part of the software dependency
graph.  We assume that it is available (and compatible) at runtime.
Usually this is fine.  Unfortunately, there are some old kernels that
are no longer supported by the kernel developers and thus no longer
supported by the glibc developers, who provide the interface that almost
all applications use to talk to the kernel.

You cannot upgrade the kernel with just Guix; you’d have to boot a
system with that kernel.

The kernel interface is pretty large, so it is very unfortunate that we
cannot treat the kernel like any other dependency.  I would think that
this would be a smaller problem in a system like the Hurd.

>> 3.0 is just a tad too old for the C library.  What system is this?  Is
>> this SLES from mid 2013?  Are you able to upgrade to at least Linux 3.10
>> or install the RHEL 6 kernel, which is known to work?
>
> Yes, it is an old Suse.
> My ideas was to be able to fetch up-to-date softwares without
> modifying the current configuration (lazy sysadmin's work ;-)

Unfortunately, you’ll need a supported kernel version.  3.10 is the
minimum for the current glibc.  Installing a recent variant of the GNU
system (e.g. with a recent Debian or GuixSD) would be a good idea.

--
Ricardo

  reply	other threads:[~2018-05-31 11:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30 18:47 unbounded variable from `FATAL: kernel too old` ? zimoun
2018-05-30 20:09 ` Ricardo Wurmus
2018-05-31  9:59   ` zimoun
2018-05-31 11:57     ` Ricardo Wurmus [this message]
2018-05-31 16:39       ` zimoun
2018-05-31 17:30         ` Ricardo Wurmus

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bmcwox64.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=help-guix@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.