On Sun, Apr 3, 2016, at 05:35 AM, Daniel J Walsh wrote:
> Colin is that right? Do you intend to make this available via atomic
> command line?
https://github.com/projectatomic/atomic/pull/335
On 03/31/2016 08:16 PM, Dusty Mabe wrote:
On 03/31/2016 12:21 PM, Matthew Miller wrote:
On Thu, Mar 31, 2016 at 12:09:16PM -0400, Daniel J Walsh wrote:
On 03/31/2016 11:58 AM, Dusty Mabe wrote:
I'm down to write a blog post for this. You will have to fight over
where it gets posted (project
On 03/31/2016 06:00 PM, Matthew Miller wrote:
> The more we talk about it, the more people we'll get onto this list!
+1
Also, I wouldn't even assume that everyone subscribed to atomic-devel
noticed this thread. We're all drinking from the firehose, and it takes
*a lot* of work to evenly communica
On 03/31/2016 12:21 PM, Matthew Miller wrote:
> On Thu, Mar 31, 2016 at 12:09:16PM -0400, Daniel J Walsh wrote:
>> On 03/31/2016 11:58 AM, Dusty Mabe wrote:
>>> I'm down to write a blog post for this. You will have to fight over
>>> where it gets posted (projectatomic or fedmag) :)
>>>
>>> Fight!
On 03/31/2016 12:09 PM, Daniel J Walsh wrote:
>
>
> On 03/31/2016 11:58 AM, Dusty Mabe wrote:
>>
>> On 03/30/2016 07:14 PM, Josh Berkus wrote:
>>> On 03/30/2016 01:06 PM, Matthew Miller wrote:
On Mon, Mar 28, 2016 at 07:59:04PM -0400, Jonathan Lebon wrote:
>> Any solution for testing t
On Thu, Mar 31, 2016 at 02:16:12PM -0400, Colin Walters wrote:
> On Wed, Mar 30, 2016, at 07:14 PM, Josh Berkus wrote:
> > On 03/30/2016 01:06 PM, Matthew Miller wrote:
> > So, can somebody blog this?
> I have no opposition to this but on the other hand the reason I
> didn't write one from the star
On Wed, Mar 30, 2016, at 07:14 PM, Josh Berkus wrote:
> On 03/30/2016 01:06 PM, Matthew Miller wrote:
> So, can somebody blog this?
I have no opposition to this but on the other hand the reason I didn't
write one from the start is I think the vast majority of the target audience is
on
(or should
On 03/31/2016 11:58 AM, Dusty Mabe wrote:
On 03/30/2016 07:14 PM, Josh Berkus wrote:
On 03/30/2016 01:06 PM, Matthew Miller wrote:
On Mon, Mar 28, 2016 at 07:59:04PM -0400, Jonathan Lebon wrote:
Any solution for testing that needs to involve a reboot?
Check out `unlock --hotfix`! It will m
On Thu, Mar 31, 2016 at 12:09:16PM -0400, Daniel J Walsh wrote:
> On 03/31/2016 11:58 AM, Dusty Mabe wrote:
> >I'm down to write a blog post for this. You will have to fight over
> >where it gets posted (projectatomic or fedmag) :)
> >
> >Fight!
> >
> Do we want to wait until we have something peop
On 03/30/2016 07:14 PM, Josh Berkus wrote:
> On 03/30/2016 01:06 PM, Matthew Miller wrote:
>> On Mon, Mar 28, 2016 at 07:59:04PM -0400, Jonathan Lebon wrote:
Any solution for testing that needs to involve a reboot?
>>> Check out `unlock --hotfix`! It will make the overlayfs
>>> persistent ac
On Wed, Mar 30, 2016 at 04:14:54PM -0700, Josh Berkus wrote:
> >>> Any solution for testing that needs to involve a reboot?
> >> Check out `unlock --hotfix`! It will make the overlayfs
> >> persistent across reboots.
> > This is really, really cool stuff, y'all!
> So, can somebody blog this?
This
On 03/30/2016 01:06 PM, Matthew Miller wrote:
> On Mon, Mar 28, 2016 at 07:59:04PM -0400, Jonathan Lebon wrote:
>>> Any solution for testing that needs to involve a reboot?
>> Check out `unlock --hotfix`! It will make the overlayfs
>> persistent across reboots.
>
> This is really, really cool stuf
On Mon, Mar 28, 2016 at 07:59:04PM -0400, Jonathan Lebon wrote:
> > Any solution for testing that needs to involve a reboot?
> Check out `unlock --hotfix`! It will make the overlayfs
> persistent across reboots.
This is really, really cool stuff, y'all!
--
Matthew Miller
Fedora Project Leader
On 28/03/16, Jonathan Lebon wrote:
> > Any solution for testing that needs to involve a reboot?
>
> Check out `unlock --hotfix`! It will make the overlayfs
> persistent across reboots.
>
> https://github.com/ostreedev/ostree/blob/master/man/ostree-admin-unlock.xml#L74
Awesome features :)
Kushal
On 03/28/2016 10:39 AM, Colin Walters wrote:
> I think with the new "ostree admin unlock" verb in OSTree v2016.4 that has
> changed:
> https://mail.gnome.org/archives/ostree-list/2016-March/msg9.html
This is very cool. We should probably blog about this too.
--
Joe Brockmeier | Community Te
> Any solution for testing that needs to involve a reboot?
Check out `unlock --hotfix`! It will make the overlayfs
persistent across reboots.
https://github.com/ostreedev/ostree/blob/master/man/ostree-admin-unlock.xml#L74
On 03/28/2016 10:39 AM, Colin Walters wrote:
> One of the goals I have for Atomic Host is that we are doing more integration
> testing work than the traditional client-side package assembly model.
>
> However, in order to achieve that goal, we need to enable developers to
> quickly and rapidly
One of the goals I have for Atomic Host is that we are doing more integration
testing work than the traditional client-side package assembly model.
However, in order to achieve that goal, we need to enable developers to quickly
and rapidly test combinations of packages and code. Until now, actu
18 matches
Mail list logo
