On 5/24/2015 5:21 AM, Rickard von Essen wrote:
> Hi,
>
> The documentation on how to create a bootable usb stick, https://clearlinux.org/documentation/creating-bootable-usb-stick, reference non existing ext4 images,
> http://download.clearlinux.org/releases/[release_number]-ext4.img.xz .
>
> Is this a transient error? Otherwise it would be good to add a note in the docs that this is WIP.
>
I'll check with our release team
(but tomorrow is a US holiday so it'll be Tuesday)
also there is a small mistake in the docs, the latest images should be at http://download.clearlinux.org/image/ always
instead of having you go through all releases to find one with an image (we don't make images for every release, only about weekly)
On 5/22/2015 9:21 AM, Patrick Reilly wrote:
> I agree. I talked to Arjan (in person) yesterday about a proper
> mirror. So we should be good to mirror the internal one soon... I
> hope.
yeah I just need to talk to the right people on the logistics side of things;
with Monday being a holiday that may be Tuesday
+1 this is awesome.
— Patrick
> On Fri, May 22, 2015 at 6:27 AM, Arjan van de Ven <arjan(a)linux.intel.com> wrote:
>> On 5/21/2015 10:12 PM, Dietmar Maurer wrote:
>>>
>>> Seems Paolo wants to show that qemu can also boot fast:
>>>
>>> https://github.com/bonzini/qboot
>>>
>>> Looks promising to me.
>>
>>
>> to be honest: I love it.
>>
>> if this gets close enough to what we need, we will use it as well, or even
>> instead of kvmtool.
>>
>>
>> _______________________________________________
>> Dev mailing list
>> Dev(a)lists.clearlinux.org
>> https://lists.clearlinux.org/mailman/listinfo/dev
I agree. I talked to Arjan (in person) yesterday about a proper
mirror. So we should be good to mirror the internal one soon... I
hope.
— Patrick
>
> On Fri, May 22, 2015 at 3:51 AM, Sven Dowideit <SvenDowideit(a)home.org.au> wrote:
>> Awesome - That'll make playing much easier :)
>>
>> If you guys also add the docs to that repo - and then import any changes
>> into your Drupal, then we can have way more fun!
>>
>> Sven
>>
>>
>> On 22/05/15 18:24, Dimitri John Ledkov wrote:
>>>
>>> Heya,
>>>
>>> On 21 May 2015 at 19:59, Richard McKinley <rich(a)kismatic.io> wrote:
>>>>
>>>> Dimitri, thanks for the information. I'm working with Patrick to track
>>>> Clear Linux development in a git repository. I will get the grain as fine as
>>>> your releases. I will setup a git tag for each of your releases. I think
>>>> this will be a convenient way to follow the changes over time and have all
>>>> of the tools git provides. The repo is here, FYI:
>>>>
>>>> https://github.com/kismatic/clearlinux
>>>>
>>>
>>> Whilst this is good, i think it would be best if we can mirror
>>> internal git repositories publicly at the same time we release the
>>> snapshot, as really there is nothing interesting in them, nor need to
>>> reconstruct that. Let me talk to Arjan about it.
>>>
>>> Regards,
>>>
>>> Dimitri.
>>>
>>>
>>>> Thanks,
>>>>
>>>> Rich McKinley
>>>>
>>>>
>>>> On Thu, May 21, 2015, Dimitri John Ledkov <dimitri.j.ledkov(a)intel.com>
>>>> wrote:
>>>>>
>>>>>
>>>>> Hello Patrick,
>>>>>
>>>>> On 20 May 2015 at 17:33, Patrick Reilly <patrick(a)kismatic.io> wrote:
>>>>>>
>>>>>> Hello Dimitri,
>>>>>>
>>>>>> Could you point me towards the Clear Linux source repository?
>>>>>
>>>>> Our development mailing list is at dev(a)lists.clearlinux.org. Questions
>>>>> like these are best to be addressed there, such that next person can
>>>>> look them up.
>>>>>
>>>>> We aim to cut a release twice a day, and create snapshot archive of
>>>>> all source rpms & binary rpms. Then delta updates & images generated
>>>>> from snapshot and published.
>>>>>
>>>>
>>>> _______________________________________________
>>>> Dev mailing list
>>>> Dev(a)lists.clearlinux.org
>>>> https://lists.clearlinux.org/mailman/listinfo/dev
>>>>
>>>
>>>
>>
>> _______________________________________________
>> Dev mailing list
>> Dev(a)lists.clearlinux.org
>> https://lists.clearlinux.org/mailman/listinfo/dev
Awesome - That'll make playing much easier :)
If you guys also add the docs to that repo - and then import any changes
into your Drupal, then we can have way more fun!
Sven
On 22/05/15 18:24, Dimitri John Ledkov wrote:
> Heya,
>
> On 21 May 2015 at 19:59, Richard McKinley <rich(a)kismatic.io> wrote:
>> Dimitri, thanks for the information. I'm working with Patrick to track Clear Linux development in a git repository. I will get the grain as fine as your releases. I will setup a git tag for each of your releases. I think this will be a convenient way to follow the changes over time and have all of the tools git provides. The repo is here, FYI:
>>
>> https://github.com/kismatic/clearlinux
>>
>
> Whilst this is good, i think it would be best if we can mirror
> internal git repositories publicly at the same time we release the
> snapshot, as really there is nothing interesting in them, nor need to
> reconstruct that. Let me talk to Arjan about it.
>
> Regards,
>
> Dimitri.
>
>
>> Thanks,
>>
>> Rich McKinley
>>
>>
>> On Thu, May 21, 2015, Dimitri John Ledkov <dimitri.j.ledkov(a)intel.com> wrote:
>>>
>>> Hello Patrick,
>>>
>>> On 20 May 2015 at 17:33, Patrick Reilly <patrick(a)kismatic.io> wrote:
>>>> Hello Dimitri,
>>>>
>>>> Could you point me towards the Clear Linux source repository?
>>> Our development mailing list is at dev(a)lists.clearlinux.org. Questions
>>> like these are best to be addressed there, such that next person can
>>> look them up.
>>>
>>> We aim to cut a release twice a day, and create snapshot archive of
>>> all source rpms & binary rpms. Then delta updates & images generated
>>> from snapshot and published.
>>>
>>
>> _______________________________________________
>> Dev mailing list
>> Dev(a)lists.clearlinux.org
>> https://lists.clearlinux.org/mailman/listinfo/dev
>>
>
>
Heya,
On 21 May 2015 at 19:59, Richard McKinley <rich(a)kismatic.io> wrote:
>
> Dimitri, thanks for the information. I'm working with Patrick to track Clear Linux development in a git repository. I will get the grain as fine as your releases. I will setup a git tag for each of your releases. I think this will be a convenient way to follow the changes over time and have all of the tools git provides. The repo is here, FYI:
>
> https://github.com/kismatic/clearlinux
>
Whilst this is good, i think it would be best if we can mirror
internal git repositories publicly at the same time we release the
snapshot, as really there is nothing interesting in them, nor need to
reconstruct that. Let me talk to Arjan about it.
Regards,
Dimitri.
> Thanks,
>
> Rich McKinley
>
>
> On Thu, May 21, 2015, Dimitri John Ledkov <dimitri.j.ledkov(a)intel.com> wrote:
>>
>>
>> Hello Patrick,
>>
>> On 20 May 2015 at 17:33, Patrick Reilly <patrick(a)kismatic.io> wrote:
>> > Hello Dimitri,
>> >
>> > Could you point me towards the Clear Linux source repository?
>>
>> Our development mailing list is at dev(a)lists.clearlinux.org. Questions
>> like these are best to be addressed there, such that next person can
>> look them up.
>>
>> We aim to cut a release twice a day, and create snapshot archive of
>> all source rpms & binary rpms. Then delta updates & images generated
>> from snapshot and published.
>>
>
>
> _______________________________________________
> Dev mailing list
> Dev(a)lists.clearlinux.org
> https://lists.clearlinux.org/mailman/listinfo/dev
>
--
Regards,
Dimitri.
Pura Vida!
https://clearlinux.org
Open Source Technology Center
Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ.
Dimitri, thanks for the information. I'm working with Patrick to track
Clear Linux development in a git repository. I will get the grain as fine
as your releases. I will setup a git tag for each of your releases. I think
this will be a convenient way to follow the changes over time and have all
of the tools git provides. The repo is here, FYI:
https://github.com/kismatic/clearlinux
Thanks,
Rich McKinley
On Thu, May 21, 2015, Dimitri John Ledkov <dimitri.j.ledkov(a)intel.com
> wrote:
>
> Hello Patrick,
>
> On 20 May 2015 at 17:33, Patrick Reilly <patrick(a)kismatic.io> wrote:
> > Hello Dimitri,
> >
> > Could you point me towards the Clear Linux source repository?
>
> Our development mailing list is at dev(a)lists.clearlinux.org. Questions
> like these are best to be addressed there, such that next person can
> look them up.
>
> We aim to cut a release twice a day, and create snapshot archive of
> all source rpms & binary rpms. Then delta updates & images generated
> from snapshot and published.
>
>
Hello Patrick,
On 20 May 2015 at 17:33, Patrick Reilly <patrick(a)kismatic.io> wrote:
> Hello Dimitri,
>
> Could you point me towards the Clear Linux source repository?
Our development mailing list is at dev(a)lists.clearlinux.org. Questions
like these are best to be addressed there, such that next person can
look them up.
We aim to cut a release twice a day, and create snapshot archive of
all source rpms & binary rpms. Then delta updates & images generated
from snapshot and published.
Under: https://download.clearlinux.org/current/
Are always the most recent source rpms & binary rpms.
Under: https://download.clearlinux.org/releases/
You will find all snapshot archives, and those that were withdrawn
from update server. Inside there, there are release notes for given
snapshot + all source & binary rpms.
Under: https://download.clearlinux.org/update/
Is the delta updates and manifests for the updater.
We only use srpms as a way to build packages and generate rpms, from
which we then assemble images and update server. Directly installig
rpms or using something like yum is not supported. Thus you will find
most srpm packaging is generated with only like patches applied here
and there. But all patches are present in srpms, broken out logically.
Our swupd_update tool is the updater which gives one a transactional
update to the next release snapshot. More about it at
https://clearlinux.org/features/software-update. In general
"traditional" yum/dfn/zypper don't bring us much benefit, as we are
stateless (empty /etc by default, reserved for admin modification
only) and we have no maintainer scriplets at all (we have
update-triggers.target defined in systemd that runs all the usual
hooks post-update).
One interesting thing you might like is adding "containers-basic"
bundle, it already has `rkt' available with a heavily modified stage1,
that spawns a new Clear Container KVM and launches the workload inside
it. I am working on making that stage1 highly portable, such that one
can use it on any host that can run rkt binary.
--
Regards,
Dimitri.
Pura Vida!
https://clearlinux.org
Open Source Technology Center
Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ.