From: ng0 <ng0@infotropique.org>
To: Dmitry Nikolaev <cameltheman@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Enable modules in Linux configuration.
Date: Sun, 30 Jul 2017 09:33:56 +0000 [thread overview]
Message-ID: <20170730093356.psqt64per62qnnh6@abyayala> (raw)
In-Reply-To: <CAH3JXcEGXTXfQ0fy4ijGHcDZ51mB10TJ5EfPNz6V+yshbDpNFg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
Dmitry Nikolaev transcribed 2.4K bytes:
> Hi everybody.
>
> I'm trying to set up GuixSD on Reiser4 file system. I've succeeded with
> patching and compiling Linux with Reiser4 patch, but I've found that
> reiser4 module is disabled by default. Everything I did was pointless 8-]
>
…
I'm going to respond only to this part:
> will you add linux-libre-reiser4,
> libaal and reiser4progs packages to main package repository if I'll send
> you patches?
That depends mainly on the licenses, from my point of view.
I haven't looked into the sources, but from what other systems
provide:
- libaal: GPL2
- reiser4progs: GPL2
and I think the reiser4 patches were GPL2 too?
The other question is, will someone maintain this linux-libre package
variation? Are there people who would update it? We don't assign people
to packages, but knowing that there is at least one person caring for
it would help.
> Dmitry Nikolaev
--
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-07-30 9:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-29 19:33 Enable modules in Linux configuration Dmitry Nikolaev
2017-07-30 9:33 ` ng0 [this message]
2017-07-30 18:11 ` Joshua Branson
2017-07-30 18:18 ` ng0
2017-07-31 11:45 ` Mark H Weaver
2017-07-31 11:57 ` Mark H Weaver
2017-07-31 21:39 ` Marius Bakke
2017-08-02 14:37 ` Joshua Branson
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=20170730093356.psqt64per62qnnh6@abyayala \
--to=ng0@infotropique.org \
--cc=cameltheman@gmail.com \
--cc=help-guix@gnu.org \
/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.
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).