xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Niall Fleming <niall.fleming@webanywhere.co.uk>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	"keir.xen@gmail.com" <keir.xen@gmail.com>,
	Jan Beulich <JBeulich@suse.com>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>,
	Konrad Rzeszutek Wilk <konrad@darnok.org>
Subject: Re: Time Change Issue Xen 4.1
Date: Thu, 01 Dec 2011 18:16:04 +0000	[thread overview]
Message-ID: <4ED7C464.6040609@webanywhere.co.uk> (raw)
In-Reply-To: <4ED756BE.3070309@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 2880 bytes --]

I wasn't expecting anyone to speed up and fix the issue, I just hoped 
that one or more of
people who were involved in the original ticket could respond to a 
request for an update,
I only asked for an update about once a week, even with busy schedules I 
would have
thought that that was possible.

I would look into the problem myself, but kernel hacking and hardcore 
XEN development is
not my thing, I did not intend to put anyone's back up about the issue. 
I'd love to fix the
problem myself, and am quite willing to test and debug stuff.

For reference the issue is not a massive deal-breaker for me, but it 
will be when the hardware
clock drifts next, particularly on the production machines which may 
have up to 100 instances
on, it becomes a massive ball-ache to down the server and reboot it just 
to get the instances to
boot with the correct time.

*Niall Fleming BSc. (Hons)*
Systems Administrator
Webanywhere Limited

Phone: 0800 862 0131 Ext: 203
Web: http://www.webanywhere.co.uk

Aire Valley Business Centre, Lawkholme Lane, Keighley, BD21 3BB
Registered in England with company number 4881346

On 01/12/2011 10:28, Laszlo Ersek wrote:
> Hello Niall,
>
> On 12/01/11 10:53, Ian Campbell wrote:
>> On Thu, 2011-12-01 at 08:55 +0000, Niall Fleming wrote:
>>> Cheers, at least I know that someone is still looking at it!
>>>
>>> If someone could give me a general timeframe, like it'll be a month,
>>> before we fix it, or two weeks or whatever, I just need to give my
>>> line manager something so he gets off my case about it!
>>
>> I'm afraid OSS software doesn't generally work like that. If you (or
>> your boss) wants something fixed on a specific time scale or priority
>> you'll have to role your sleeves up and scratch the itch. Otherwise I'm
>> sorry but you will just have to wait until someone has the cycles to
>> look into this issue.
>
> I shouldn't comment on this, because
> - it'll be off-topic, and
> - (more importantly) personally I'm not knowledgeable enough to fix 
> the problem,
>
> but I feel compelled to point out that *in general* it's not about the 
> various rights accompanying the bits (ie. proprietary / open source / 
> free software). It's about who gets to allocate whose resources. Under 
> this aspect it's irrelevant under what rights the end product will be 
> released, the question is instead who backs the effort & costs of the 
> end product being hammered into existence.
>
> Users of FLOSS tend to mix up these two things ("what rights do I have 
> to the code?" vs. "work on this for my sake!"). For the second 
> concept, commercial relationships are (and have always been) the 
> default, even if extremely forthcoming FLOSS developers used to evoke 
> a different impression.
>
> (To make it abundantly clear, this is not an advertisment, and I'm 
> speaking *strictly* personally, for myself alone.)
>
> Laszlo

[-- Attachment #1.2: Type: text/html, Size: 4071 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2011-12-01 18:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-11 17:25 Time Change Issue Xen 4.1 Niall Fleming
2011-11-11 18:39 ` Konrad Rzeszutek Wilk
2011-11-14  9:48   ` Jan Beulich
2011-11-14 18:00     ` Konrad Rzeszutek Wilk
2011-11-14 19:31       ` Jeremy Fitzhardinge
2011-11-16 14:26         ` Konrad Rzeszutek Wilk
2011-11-17 12:47           ` Niall Fleming
2011-11-22 10:23           ` Niall Fleming
2011-11-30 17:06           ` Niall Fleming
2011-11-30 22:26             ` Konrad Rzeszutek Wilk
2011-12-01  8:55               ` Niall Fleming
2011-12-01  9:53                 ` Ian Campbell
2011-12-01 10:28                   ` Laszlo Ersek
2011-12-01 18:16                     ` Niall Fleming [this message]
2011-11-14 10:15   ` Laszlo Ersek

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=4ED7C464.6040609@webanywhere.co.uk \
    --to=niall.fleming@webanywhere.co.uk \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=jeremy@goop.org \
    --cc=keir.xen@gmail.com \
    --cc=konrad.wilk@oracle.com \
    --cc=konrad@darnok.org \
    --cc=lersek@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=xen-devel@lists.xensource.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.
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 NNTP newsgroup(s).