From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-cluster@lists.gentoo.org
Subject: Re: [gentoo-cluster] examples of (large) Gentoo clusters
Date: Mon, 04 Dec 2006 19:55:08 -0800 [thread overview]
Message-ID: <4574ED9C.10007@gentoo.org> (raw)
In-Reply-To: <8a0c7af10612041555i196d81f3u849c8419b15e171a@mail.gmail.com>
Daniel van Ham Colchete wrote:
> I studied Lustre last week a little bit and, talking about MDSs and
> OSSs, I came with one reason for them not to make Lustre to support
> Gentoo: Lustre uses a lot of kernel features that if not enabled will
> cause the kernel to crash.
>
> I didn't find any documentation explaning those features but I could
> make a list of the orbivious ones: LVM, DM, ext3, ...
>
> I think that even they can't make a list of all those features, that
> is why they have to make Lustre available mainly on pre-compiled /
> pre-configured kernels. And, thank God, Gentoo doesn't have a
> predefined kernel. Although that would make easy for them to change
> and distribute it.
>
> What do you think about my ideia?
It really shouldn't be that difficult to add in features until it stops
crashing, then specify those features as dependencies in the kernel
build system.
> But that leads to a more generic question: if Linux is always Linux
> (the kernel), and the distro is only a way to organize packages, files
> and init scripts, why would anyone need restrict an open source
> software to a distro? If my first assumption is right, the quicky (but
> not necessarily well thought) answer would be: lack of knowledge.
Sure. If they offer to support Lustre on a distribution, they need to be
able to fix problems on that distribution. That means being aware of
possible distribution-specific interactions that could cause issues and
also knowing how to deal with them as well as reproduce them locally.
Thanks,
Donnie
--
gentoo-cluster@gentoo.org mailing list
next prev parent reply other threads:[~2006-12-05 3:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 23:16 [gentoo-cluster] examples of (large) Gentoo clusters Bryan Green
2006-12-02 3:48 ` Donnie Berkholz
2006-12-02 13:54 ` Hanni Ali
2006-12-02 18:12 ` Bryan Green
2006-12-02 17:57 ` Bryan Green
2006-12-02 19:51 ` Philipp Riegger
2006-12-03 3:49 ` Donnie Berkholz
2006-12-04 18:15 ` Bryan Green
2006-12-04 20:53 ` Donnie Berkholz
2006-12-04 22:35 ` Hanni Ali
2006-12-04 23:00 ` Bryan Green
2006-12-04 23:55 ` Daniel van Ham Colchete
2006-12-05 3:55 ` Donnie Berkholz [this message]
2006-12-05 13:18 ` John R. Dunning
2006-12-05 16:25 ` Bryan Green
2006-12-05 21:15 ` Daniel van Ham Colchete
2006-12-05 21:22 ` Bryan Green
2006-12-05 21:28 ` John R. Dunning
2006-12-07 0:33 ` Bryan Green
2006-12-07 13:12 ` John R. Dunning
2006-12-08 3:56 ` Bryan Green
2006-12-08 14:18 ` John R. Dunning
2006-12-08 17:15 ` Bryan Green
2006-12-11 13:38 ` John R. Dunning
2006-12-08 18:29 ` Donnie Berkholz
2006-12-08 18:52 ` Bryan Green
2006-12-08 19:10 ` John R. Dunning
2006-12-11 19:44 ` Bryan Green
2006-12-02 14:40 ` Nick Anderson
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=4574ED9C.10007@gentoo.org \
--to=dberkholz@gentoo.org \
--cc=gentoo-cluster@lists.gentoo.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