[CentOS-devel] ostree as a delivery model
Colin Walters
walters at verbum.orgFri Apr 4 19:59:30 UTC 2014
- Previous message: [CentOS-devel] ostree as a delivery model
- Next message: [CentOS-devel] ostree as a delivery model
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Apr 4, 2014 at 3:24 PM, Les Mikesell <lesmikesell at gmail.com> wrote: > I think I'm missing the point of what it does - at least for your > first system. Where does the baremetal hardware > detection/configuration happen? Anaconda is what installs: https://www.redhat.com/archives/anaconda-devel-list/2014-March/msg00028.html I did the patches against an older branch of Anaconda, I'm working on porting them to rawhide. However on the "compose server" side, the trees are not "installs". It's quite close to just "rpm2cpio"ing all of the RPMs into an unpacked root, running the %post, and committing that. A key difference though is that ostree demands that the trees can be updated without %post on the client. This lack of %post requires some design changes in the OS content. See for example: /usr/lib/passwd: https://sourceware.org/bugzilla/show_bug.cgi?id=16142 SELinux: http://marc.info/?l=selinux&m=139571299908156&w=2 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20140404/3657b0aa/attachment-0001.html>
- Previous message: [CentOS-devel] ostree as a delivery model
- Next message: [CentOS-devel] ostree as a delivery model
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS-devel mailing list