avsm changed the topic of #mirage to: Good news everyone! Mirage 3.0 released!
AltGr has joined #mirage
mort___ has joined #mirage
mort___ has quit [Quit: Leaving.]
mort___ has joined #mirage
argent_smith has joined #mirage
mort___ has quit [Quit: Leaving.]
mort___ has joined #mirage
mort___ has quit [Ping timeout: 248 seconds]
copy_ has joined #mirage
copy[m] is now known as copy[m]1
copy[m]1 is now known as copy__
copy_ has quit [Quit: Connection closed for inactivity]
mort___ has joined #mirage
<raboof> "Announcing Amazon EC2 per second billing" sounds neat. Any experience? Do mirage instances on AWS start/stop quickly or is there noticable overhead in the AWS infrastructure that interferes?
<hannes> raboof: i've no experience with ec2, you may have more luck asking on the mailing list mirageos-devel@lists.xenproject.org
<raboof> oh - 'with a minimum of 60 seconds' - still a step in the right direction :) https://aws.amazon.com/about-aws/whats-new/2017/10/announcing-amazon-ec2-per-second-billing/
mort___1 has joined #mirage
mort___ has quit [Read error: Connection reset by peer]
pagurus has quit [Ping timeout: 240 seconds]
pagurus has joined #mirage
AltGr has left #mirage [#mirage]
mort___1 has quit [Quit: Leaving.]
miragebot has joined #mirage
<miragebot> [mirage] hannesm pushed 2 new commits to master: https://git.io/vdwDI
<miragebot> mirage/master 2586c64 Hannes Mehnert: Merge pull request #860 from hannesm/cleanup...
<miragebot> mirage/master ba33f7a Hannes Mehnert: remove MacOSX < yosemite support
miragebot has left #mirage [#mirage]
argent_smith has quit [Quit: Leaving.]