public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dragostin Yanev <gentoo+user@netixen.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: s6 et al
Date: Thu, 3 Oct 2013 17:09:25 +0300	[thread overview]
Message-ID: <20131003170925.6671cbe9@gacer.netixen.com> (raw)
In-Reply-To: <524D69C2.20408@gmail.com>

On Thu, 03 Oct 2013 14:57:38 +0200
Alan McKinnon <alan.mckinnon@gmail.com> wrote:

> On 03/10/2013 14:55, James wrote:
> > William Hubbs <williamh <at> gentoo.org> writes:
> > 
> > 
> >> On Wed, Oct 02, 2013 at 12:04:24AM -0500, Bruce Hill wrote:
> >>> Just stumbled across some very interesting software/ideas:
> >>>
> >>> http://skarnet.org/poweredby.html
> > 
> >> Yes, I have been looking at this for a few days, and some of the
> >> other members of the OpenRC team are interested in it as well.
> > 
> > I'm not too sure about the kernel sources:
> > "is provided by Gandi and cannot be modified"
> 
> That's a GPL violation right there.

Hi,
I think you are misreading that sentence out of it's context.
The context as I read it states that the hosting server is a VPS leased
by Gandi and they don't have control over the kernel (openvz, lxc,
containers, etc..).


> 
> The developer absolutely totally cannot do that. He/she may refuse to
> provide support if the kernel image is not what is shipped, but by
> using Linux they have already bound themselves to an agreement that
> the sources must be provided and be modifiable. And, they have to
> host the sources on their own network or provide them on demand
> 
> 
> 
> > 
> > My experiences with embedded *nix is that the kernel sources
> > are tinkered with, almost constantly to infinity......
> > 
> > You'd be wise to post to the gentoo-embedded group, where
> > those learking in the shadows (memory crevaces) have
> > lots of experiences with a multitude of embedded ventures.
> > 
> > Most embedded ventures end up on the waste heap; they made
> > critical decision that leave the effort..........borked.
> > I'd research into the coding+user community, as being 
> > naked and alone on an embedded vetnure, does give rise to
> > abandonment.   
> > 
> > Another consideration is the processor architecture(s) that 
> > the codebase runs on. Most embedded and high end processor
> > efforts are looking at LOW POWER architectures, as the thrust
> > of all future efforts. This means on ARM or ARM+x86 or such.
> > 
> > 
> > That said, the project does look attractive.
> > 
> > caveat emptor.
> > hth,
> > James
> > 
> > 
> > 
> > 
> > 
> > 
> 
> 



  parent reply	other threads:[~2013-10-03 14:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-02  5:04 [gentoo-user] s6 et al Bruce Hill
2013-10-02 14:44 ` William Hubbs
2013-10-02 14:52   ` Bruce Hill
2013-10-03 14:26     ` William Hubbs
2013-10-03 14:39       ` Pandu Poluan
2013-10-03 15:19         ` William Hubbs
2013-10-03 12:55   ` [gentoo-user] " James
2013-10-03 12:57     ` Alan McKinnon
2013-10-03 13:58       ` Michael Orlitzky
2013-10-03 14:09       ` Dragostin Yanev [this message]
2013-10-03 14:15         ` Alan McKinnon
2013-10-03 15:32           ` James
2013-10-03 16:36             ` William Hubbs
2013-10-03 22:32 ` [gentoo-user] " Walter Dnes
2013-10-04  1:24   ` Volker Armin Hemmann

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=20131003170925.6671cbe9@gacer.netixen.com \
    --to=gentoo+user@netixen.com \
    --cc=gentoo-user@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