On 20. 1. 2015 at 08:40:30, Colin Walters wrote:
> On Tue, Jan 20, 2015, at 06:27 AM, Jan Zelený wrote:
> > You are probably right, I might have misunderstood what you actually
> > propose. Does it mean that you actually don't require this part to be
> > implemented at all and you can go with what'
On Tue, Jan 20, 2015, at 06:27 AM, Jan Zelený wrote:
> You are probably right, I might have misunderstood what you actually propose.
> Does it mean that you actually don't require this part to be implemented at
> all and you can go with what's in /var without any distribution-wide changes?
Fed
On 19. 1. 2015 at 11:30:22, Colin Walters wrote:
> On Mon, Jan 19, 2015, at 07:02 AM, Jan Zelený wrote:
> > I have hard time figuring out what exactly is the purpose of including the
> > factory reset feature in your proposal. No offense but unless I'm missing
> > something, it seems to me that you
On Mon, Jan 19, 2015, at 07:02 AM, Jan Zelený wrote:
> I have hard time figuring out what exactly is the purpose of including the
> factory reset feature in your proposal. No offense but unless I'm missing
> something, it seems to me that you are trying to solve some of ostree
> problems
> in
On 13. 1. 2015 at 16:41:46, Colin Walters wrote:
> On Tue, Jan 13, 2015, at 04:06 PM, Miloslav Trmač wrote:
> > > == Scope ==
> > > * Other developers:
> > > *** Use systemd-tmpfiles instead of placing content in /var (TODO:
> > > better docs for this)
> >
> > Is this a strict dependency or a nic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 15 Jan 2015 20:49:49 -0500
Colin Walters wrote:
>
> Bear in mind that a dynamic Workstation scenario as you appear to
> have primarily in mind is about the last targeted use case. Beyond
> the Atomic Host for Docker scenario, I am aiming
> On Tue, Jan 13, 2015, at 04:41 PM, Colin Walters wrote:
>
> > If it's installing a regular file, then it won't work - the package
> > (daemon) needs to create it on start.
>
> I filed a bug about this:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1182785
>
> Though I wonder if this should
On Thu, 15 Jan 2015 20:49:49 -0500
Colin Walters wrote:
> Hi Kevin,
>
> On Thu, Jan 15, 2015, at 05:20 PM, Kevin Kofler wrote:
...snip...
> > * get new updates (including security fixes) as soon as they hit the
> > mirrors, without waiting for a new OS tree compose (every extra
> > step in t
Hi Kevin,
On Thu, Jan 15, 2015, at 05:20 PM, Kevin Kofler wrote:
>
> * customize your installation by adding/removing packages (and if it were
> not prevented, the customizations would not persist across updates),
First of course, while that's accurate for the rpm-ostree technology
today, the F
Hi
On Thu, Jan 15, 2015 at 5:20 PM, Kevin Kofler wrote:
> You gain… nothing!
>
Kevin,
If you are unaware of the gains, ask for it. Image based upgrades are very
common in cloud environments I work with. It is used as alternative to
configuration management in some places and it is incredibly
Jaroslav Reznik wrote:
> = Proposed System Wide Change: RpmOstree - Server side composes and atomic
> upgrades =
> https://fedoraproject.org/wiki/Changes/RpmOstree
>
> Change owner(s): Colin Walters
I don't see the advantage of supporting this primitive "take it or leave it"
approach to installi
On Tue, Jan 13, 2015, at 04:41 PM, Colin Walters wrote:
> If it's installing a regular file, then it won't work - the package (daemon)
> needs to create it on start.
I filed a bug about this:
https://bugzilla.redhat.com/show_bug.cgi?id=1182785
Though I wonder if this should be a Change in itse
On Tue, Jan 13, 2015, at 04:06 PM, Miloslav Trmač wrote:
> > == Scope ==
> > * Other developers:
> > *** Use systemd-tmpfiles instead of placing content in /var (TODO: better
> > docs
> > for this)
> Is this a strict dependency or a nice-to-have item? That is, are we talking
> about having to
> == Scope ==
> * Other developers:
> *** Use systemd-tmpfiles instead of placing content in /var (TODO: better
> docs
> for this)
Is this a strict dependency or a nice-to-have item? That is, are we talking
about having to change all such packages in Fedora (or some specific subset)
within the
On Tue, Jan 13, 2015 at 3:27 PM, Miloslav Trmač wrote:
>> Jaroslav, there is a lot more information on the actual wiki page.
>> Like the fact that this is only for particular opt-in new installs and
>> that yum/dnf/RPM can only operate in read-only mode on such installs.
>> Could you resend this w
> Jaroslav, there is a lot more information on the actual wiki page.
> Like the fact that this is only for particular opt-in new installs and
> that yum/dnf/RPM can only operate in read-only mode on such installs.
> Could you resend this with the entirety of the text? It might lead to
> fewer ques
On Tue, Jan 13, 2015 at 7:32 AM, Jaroslav Reznik wrote:
> = Proposed System Wide Change: RpmOstree - Server side composes and atomic
> upgrades =
> https://fedoraproject.org/wiki/Changes/RpmOstree
>
> Change owner(s): Colin Walters
>
> The rpm-ostree [1] tool provides a new way to deploy and mana
= Proposed System Wide Change: RpmOstree - Server side composes and atomic
upgrades =
https://fedoraproject.org/wiki/Changes/RpmOstree
Change owner(s): Colin Walters
The rpm-ostree [1] tool provides a new way to deploy and manage RPM-based
operating systems. Instead of performing a package-by-
18 matches
Mail list logo
