This stuff is awkward to consume at the moment. We're working on
fixing that. I _really_ want to get this update code blessed such that
the git repo could just be on github or where ever on the internet,
mailing list, docu, etc. Compilable sources does not make a sustainable
open source collaboration, which is definitely where I want this to be.
But there's paperwork to be done...
So in the meantime, sources flow out at, eg:
which contains swupd-client-2.55.tar.gz, which has a swupd-client-2.55/ as
you'd expect. In there the bsdiff/swupd_bs*.c and include/swupd_bsdiff.h
are the intersting bits.
General things we've done to the bsdiff:
- some micro optim's in the bsdiff header format(s)
- extended set of block encodings: raw, bzip2, gzip, lzma2, and a simple 0 RLE
- various bits of debug (the original bsdiff code is a tad obtuse)
- adding error checking and handling
- remove errx (quite unfriendly to do as library code)
- fix some mem leaks and buffer overruns and hangs
- breaking out some helper functions so things aren't so monolithic and naively
assumed to succeed
- adding comments on things we struggle to understand
- add a crude check to notice that xattrs changed on the file being diff'd
Colin: Feel free to ping me with questions on any of it and fingers
crossed git history will be out there eventually here and our updater
development will all simply be out in the open in addition to the source
Tim Pepper -- Linux OS Engineering
Intel Open Source Technology Center
I was talking with Arjan at ContainerCon, and he mentioned that as
part of the Clearlinux updater, you guys had forked bsdiff (again)
and made a number of bugfixes.
Where does that code live? And actually, can the website
be updated to more clearly link to the code repositories?
^ zero hits
I did eventually find:
But I'm guessing that's only used for forks from projects
that were already on github?
BTW, I am the upstream for OSTree
which is also active in the host update system space.
As part of that we investigated bsdiff and ended
up contributing to:
So it'd be great if we can try to de-bundle and share work
On 8/6/2015 6:51 AM, Vladimir Stackov wrote:
> As fair as I understand Clear Linux is aiming to be a containerized applications management system that was using KVM instead of namespaces/cgroups.
> So I'm curious: what about guest memory reclaiming?
> Memory reclaiming from virtualized OS is a pain and causes resource wasting, KSM/ballooning had their own overhead.
> I don't have to manage all of that things with namespaces/cgroups where I have single running kernel that was managing available address space itself.
> Does Clear Linux relies on KSM/ballooning or it did have their own tricks?
today we rely on sharing upfront (in the container setup, not VM setup yet),
but we have a plan to also do guest memory reclaiming... it just needs implementing.
(thanks for the poke; reminds me that I just need to code it ;-) )
As fair as I understand Clear Linux is aiming to be a containerized
applications management system that was using KVM instead of
So I'm curious: what about guest memory reclaiming?
Memory reclaiming from virtualized OS is a pain and causes resource
wasting, KSM/ballooning had their own overhead.
I don't have to manage all of that things with namespaces/cgroups where I
have single running kernel that was managing available address space itself.
Does Clear Linux relies on KSM/ballooning or it did have their own tricks?
> Could you please help me to figure out whats default username and
> password for same.
At the first boot on Clear Linux, you can use “root” user and then it
will ask you to type a new password for it.
Miguel Bernal Marin Open Source Technology Center
https://clearlinux.org Intel Corporation
I just installed Clear Linux using USB Installation.
Its been installed successfully and asking for *clr login and password.*
Could you please help me to figure out whats default username and password