PureDyne
CC Attribution - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Mansoux, Aymeric
Puredyne is the USB-bootable GNU/Linux operating system for creative media. It is a live distribution, you don’t need to install anything – simply boot your computer using a USB key or CD/DVD and you’re ready to start using software such as Pure Data, Supercollider, Icecast, Csound, Fluxus, Processing, Arduino, Gimp, Inkscape and much more.
 Okay. Hi, my name is Emre and I'm going to try to talk to you very quickly about Pure Dyn. So what's Pure Dyn? Pure Dyn is a live distribution which is basically an operating system that can run either on any medium, so hard drive, CD, DVD, USB key. And we wanted to be some kind of same-based system for media artists and designers, something very basic, simple, on which people can build on. The Pure Dyn is quite peculiar in the sense that it's all made by artists and designers and musicians and none of us are, let's say, proper programmer or computer scientist. We learned it the hard way. So we use Pure Dyn to make steps. That's how it started. It's really, really practical. It's a tool. It's not meant to be a demo as in, oh, look, I've got this DVD full of awesome application that you can check. No, it's something that we actually really use. The way it has been developed was exactly through our own practice. So there have been several iterations, for example, workshops. So at the beginning Pure Dyn started because we need to have some kind of an environment on which the people who were teaching too could go back home with the whole toolkit and don't have to worry about installing Linux from scratch or this kind of things. Also because a lot of documentation or the material of the workshop or what was done during the workshop could be found back at home in an almost similar context. And then because at home, yeah, it's also meant in our home, we started to use it as our default installation, as default system, which gave quite a big boost in the project because we were able to fix things quickly because we had direct interest in having it working correctly. And then we started to use that for our own gigs, for our project, for installation. And again, it boosted the project and pushed the project in new directions. So far, the original version of Pure Dyn was sketched on another live CD project called Dinabolik. And then for various reasons, we moved on to Dbian and we released two versions with Dbian, Miso and Likenn Potato. Yeah, we use a sub name because, yeah, I will explain it. And then recently we switched to Ubuntu and the latest table is based on Ubuntu with Dbian live script and it's called Current and Coriander. We moved to Ubuntu very quickly because it was getting extremely difficult for us to invest time in maintaining our own P-Builder, back porting, packaging and things like this. It was much more easier for us to work with the Ubuntu snapshots, but we kept the Dbian as a live system environment. So inside Pure Dyn, what you have is we develop everything based for a Pentium 3. So it might sound a bit surreal, but we think it's quite good to have a good multimedia environment that can run on rather old hardware. And also because all the optimization that you will see, all the problem, bottleneck that you will see on a Pentium 3 will pay off if you run the same system later on on a faster machine, obviously. We have a real time kernel. The Windows Manager desktop is XFCE because it's a good compromise between something that is user friendly and that brings up the usual meta-force that people are used to. But we slowly push them to use EvolWM or R-SOM when they start to use Pure Dyn, especially because EvolWM, for example, is perfect when you have to run installation or make performances. The applications on the systems are mixed of, so, Dbian live for all the bootings system, Ubuntu, the different repository from Ubuntu for the application, and then midi-buntu mostly for the Alza firmware. And then the Pure Dyn PPA, which is, if you know a bit about Launchpad and Ubuntu, you know what the PPA is. So it's our own package repository where we put everything there that we find that we think is either not packaged well enough or missing or for various reasons. So, very quickly, a small demo. So this, yeah, that's Pure Dyn. So when you put Pure Dyn, you get something like that. You've got a six Linux booter. And then, so this one is quite simple. In the next release, we will have options to boot in your different languages. And then you start Pure Dyn and it boots. And that's the usual, I can't see much, but, well, you know, it's booting. While it's booting, we're going to check the MacGyver flowchart. So the MacGyver flowchart is basically what makes Pure Dyn quite interesting for artists, midi-artists who need to basically have a system that can adapt to all kinds of different situations like MacGyver. So you have the system itself is stored as read-only either on a live CD or DVD, a live USB or a live HD. So anything that you can boot off. And then everything that you see after is completely optional. So then you can enable persistence for the changes that will be made on the system because you run live CD. If you change the wallpaper, if you install a new program, then you will lose it next time that you reboot, obviously, because everything is happening in the realm of your computer. So with persistence, you can store your changes either on a partition or on a disk image. A partition means all kind of different Linux, supported Linux file system or image can be stored also on a Windows or HFS partition. And the type of persistence that you can have is either for the full system. So even if you change it something in slash ETC or you screw up user folder or whatever, it will be remembered. Or only the home user, which is practical for a workshop or for small media lab because you can quickly only migrate the home folder from the users or custom and custom, then you can go crazy because you can just having only one file persistent and change or a set of files. It's a very fine grained system. Still booting? Yeah. Sorry. So how do we build this stuff? It's built from scratch and it's very, very important because a lot of live CD or multi-matter CD that are around are usually sort of converged. Yeah, not confession. Yeah, you just take your full installation, your full system, you install stuff manually, you change the wallpaper, you make your menu pretty and it's all nice. And then you got this magic tool that turns your full system into live CD. That's very nice if you want to have a snapshot of your system to show to your friends. But it's not very viable in the long run because you can't update. The packages are limited to what the person wanted you to have. So we built from scratch, which means that everything in pure dine is packaged, which also means that you can just have your own Ubuntu and to some extent even Dbian and just get our packages and integrate that with your own super. Then we try to avoid all kinds of bloats. So for example, we don't use all the recommends features of the package manager. If we need something from a package, we know why we need it and we enable it manually. So we don't have to pull half of a whole distribution when we want to install a particular software. We don't assume that our user are stupid. So what we provide is basically access to Internet, basic good system and as little background crap as possible. So if someone wants to have Bluetooth because it needs to be working for his remote or whatever, then it's just one line to type to pull it from the package repository and that's it. It's very, so we don't deal with specific case. We don't want to please anyone. That's what we call the command denominator. We don't want to please anyone. We don't want to say it's the multimedia distribution of the future and everyone will be pleased. No, we just want to see who uses it and we'll check for the common denominator. I think, yeah, when I switch window, it must freeze the thing. Well, anyway, it's the demo effect, so it could not work. So we use Launchpad to develop PureDyn and it's okay for, I would not recommend Launchpad for all kinds of software projects, but in our case, it's quite good because for the obvious integration with Ubuntu, at the moment, we have 11 developers working on the project and we have a so-called horizontal organization. So what we mean with that is that we don't have fine-grained permissions in this PureDyn team if you are in, which is usually not too hard to get in as you start to contribute a few things. Then you have access to all the repositories, to all, well, you are admin basically on everything. And we decided to do that and it's working for us because people take initiatives and don't feel they have to ask for something in particular to someone. We don't waste time in discussion. And because we all have quite, it's quite focused distribution, there's not much to be, it's quite rare when there is really a strong fundamental disagreement between us. The way we develop it is with, yeah, this stuff is really not working, is with code sprint. I will try it one last time. So code sprint, we probably know what it is and it was the best system we found for us. So we just meet every now and then and all together we work for a week nonstop and we try to clean as much bug as possible. And because it's an art media project, we have our code sprint hosted by usually media art festival or art organization which is quite, quite weird peculiar interesting mix. Then make your own soup. Make your own soup that means that we have developed a small, simple SDK to build the distribution. And it's very easy to use, it's documented, it's a sort of high level wrapper for live helper which is the lower tool that we use. And people can use it quickly to replicate exactly puredine and make some time customization that from changing the wallpaper to putting your own name on the splash screen or to just change the default applications. So we already have people using it. So, yeah, we have puredine craftivism where it was a special version developed for the art gallery in Bristol. CD-Straw is a Greek security thingy, this throw that is using puredine as basis. Bogotrax is a Colombian distribution that was used for a lot, lot of projects recently in Colombia. And then everyone, it's very easy to branch and fork the script to make your own stuff. So tomorrow, what do we want to do? We want to close, to work closer to art and design communities. What does that mean? That means that usually the puredine team is broken down is people who are interested in more specific things. For example, we have supercollider developers working with us and they know how to package correctly and to run supercollider on puredine. So every time there is something new for supercollider, they have access to everything so they can make the changes and they can push the changes to us. We don't have to do it ourselves. Same for flexors. That's the way we want to do it. People who are good at something, they can still do it on their own but because of Launchpad, it's very easy to propagate the changes and push updates to us. For the documentation, we started to work on Wikibooks and we are trying to follow a model of user case studies and not only how to use all tutorials. So we tried to look at artists who are using puredine or designers who are using puredine and what is their setup, what do they use and how is it done. So it brings some kind of context to documentation which is for us very, very useful and very inspiring. And your idea here, yes, we listen to our users, our beloved users. A lot of changes in puredine has been made because of discussion happening on the list. We have around 300 people on the list and it's quite high quality list in the sense that it's very, very focused and very specialist questions. That's it. Thank you. You can go on puredine.org if you want to get more information and try it out for yourself. Thank you. Thank you.
 Okay. Hi, my name is Emre and I'm going to try to talk to you very quickly about Pure  Dyn. So what's Pure Dyn? Pure Dyn is a live distribution which is basically an operating  system that can run either on any medium, so hard drive, CD, DVD, USB key. And we wanted  to be some kind of same-based system for media artists and designers, something very basic,  simple, on which people can build on. The Pure Dyn is quite peculiar in the sense that  it's all made by artists and designers and musicians and none of us are, let's say, proper  programmer or computer scientist. We learned it the hard way. So we use Pure Dyn to make  steps. That's how it started. It's really, really practical. It's a tool. It's not meant  to be a demo as in, oh, look, I've got this DVD full of awesome application that you can  check. No, it's something that we actually really use. The way it has been developed  was exactly through our own practice. So there have been several iterations, for example,  workshops. So at the beginning Pure Dyn started because we need to have some kind of an environment  on which the people who were teaching too could go back home with the whole toolkit and don't  have to worry about installing Linux from scratch or this kind of things. Also because  a lot of documentation or the material of the workshop or what was done during the workshop  could be found back at home in an almost similar context. And then because at home, yeah, it's  also meant in our home, we started to use it as our default installation, as default  system, which gave quite a big boost in the project because we were able to fix things  quickly because we had direct interest in having it working correctly. And then we started  to use that for our own gigs, for our project, for installation. And again, it boosted the  project and pushed the project in new directions. So far, the original version of Pure Dyn was  sketched on another live CD project called Dinabolik. And then for various reasons, we  moved on to Dbian and we released two versions with Dbian, Miso and Likenn Potato. Yeah,  we use a sub name because, yeah, I will explain it. And then recently we switched to Ubuntu  and the latest table is based on Ubuntu with Dbian live script and it's called Current  and Coriander. We moved to Ubuntu very quickly because it was getting extremely difficult  for us to invest time in maintaining our own P-Builder, back porting, packaging and things  like this. It was much more easier for us to work with the Ubuntu snapshots, but we kept  the Dbian as a live system environment. So inside Pure Dyn, what you have is we develop  everything based for a Pentium 3. So it might sound a bit surreal, but we think it's quite  good to have a good multimedia environment that can run on rather old hardware. And also  because all the optimization that you will see, all the problem, bottleneck that you  will see on a Pentium 3 will pay off if you run the same system later on on a faster machine,  obviously. We have a real time kernel. The Windows Manager desktop is XFCE because it's  a good compromise between something that is user friendly and that brings up the usual  meta-force that people are used to. But we slowly push them to use EvolWM or R-SOM when  they start to use Pure Dyn, especially because EvolWM, for example, is perfect when you have  to run installation or make performances. The applications on the systems are mixed  of, so, Dbian live for all the bootings system, Ubuntu, the different repository from Ubuntu  for the application, and then midi-buntu mostly for the Alza firmware. And then the Pure Dyn  PPA, which is, if you know a bit about Launchpad and Ubuntu, you know what the PPA is. So it's  our own package repository where we put everything there that we find that we think is either  not packaged well enough or missing or for various reasons. So, very quickly, a small  demo. So this, yeah, that's Pure Dyn. So when you put Pure Dyn, you get something  like that. You've got a six Linux booter. And then, so this one is quite simple. In the  next release, we will have options to boot in your different languages. And then you  start Pure Dyn and it boots. And that's the usual, I can't see much, but, well, you know,  it's booting. While it's booting, we're going to check the MacGyver flowchart. So the MacGyver  flowchart is basically what makes Pure Dyn quite interesting for artists, midi-artists  who need to basically have a system that can adapt to all kinds of different situations  like MacGyver. So you have the system itself is stored as read-only either on a live CD  or DVD, a live USB or a live HD. So anything that you can boot off. And then everything  that you see after is completely optional. So then you can enable persistence for the  changes that will be made on the system because you run live CD. If you change the wallpaper,  if you install a new program, then you will lose it next time that you reboot, obviously,  because everything is happening in the realm of your computer. So with persistence, you  can store your changes either on a partition or on a disk image. A partition means all  kind of different Linux, supported Linux file system or image can be stored also on a Windows  or HFS partition. And the type of persistence that you can have is either for the full system.  So even if you change it something in slash ETC or you screw up user folder or whatever,  it will be remembered. Or only the home user, which is practical for a workshop or for small  media lab because you can quickly only migrate the home folder from the users or custom and  custom, then you can go crazy because you can just having only one file persistent and  change or a set of files. It's a very fine grained system. Still booting? Yeah. Sorry.  So how do we build this stuff? It's built from scratch and it's very, very important because  a lot of live CD or multi-matter CD that are around are usually sort of converged. Yeah,  not confession. Yeah, you just take your full installation, your full system, you install  stuff manually, you change the wallpaper, you make your menu pretty and it's all nice.  And then you got this magic tool that turns your full system into live CD. That's very  nice if you want to have a snapshot of your system to show to your friends. But it's not  very viable in the long run because you can't update. The packages are limited to what the  person wanted you to have. So we built from scratch, which means that everything in pure  dine is packaged, which also means that you can just have your own Ubuntu and to some  extent even Dbian and just get our packages and integrate that with your own super. Then  we try to avoid all kinds of bloats. So for example, we don't use all the recommends features  of the package manager. If we need something from a package, we know why we need it and  we enable it manually. So we don't have to pull half of a whole distribution when we  want to install a particular software. We don't assume that our user are stupid. So  what we provide is basically access to Internet, basic good system and as little background  crap as possible. So if someone wants to have Bluetooth because it needs to be working for  his remote or whatever, then it's just one line to type to pull it from the package repository  and that's it. It's very, so we don't deal with specific case. We don't want to please  anyone. That's what we call the command denominator. We don't want to please anyone. We don't want  to say it's the multimedia distribution of the future and everyone will be pleased. No,  we just want to see who uses it and we'll check for the common denominator. I think,  yeah, when I switch window, it must freeze the thing. Well, anyway, it's the demo effect,  so it could not work. So we use Launchpad to develop PureDyn and it's okay for, I would  not recommend Launchpad for all kinds of software projects, but in our case, it's quite good  because for the obvious integration with Ubuntu, at the moment, we have 11 developers working  on the project and we have a so-called horizontal organization. So what we mean with that is  that we don't have fine-grained permissions in this PureDyn team if you are in, which  is usually not too hard to get in as you start to contribute a few things. Then you have  access to all the repositories, to all, well, you are admin basically on everything. And  we decided to do that and it's working for us because people take initiatives and don't  feel they have to ask for something in particular to someone. We don't waste time in discussion.  And because we all have quite, it's quite focused distribution, there's not much to  be, it's quite rare when there is really a strong fundamental disagreement between us.  The way we develop it is with, yeah, this stuff is really not working, is with code  sprint. I will try it one last time. So code sprint, we probably know what it is and it  was the best system we found for us. So we just meet every now and then and all together  we work for a week nonstop and we try to clean as much bug as possible. And because it's  an art media project, we have our code sprint hosted by usually media art festival or art  organization which is quite, quite weird peculiar interesting mix. Then make your own soup.  Make your own soup that means that we have developed a small, simple SDK to build the  distribution. And it's very easy to use, it's documented, it's a sort of high level wrapper  for live helper which is the lower tool that we use. And people can use it quickly to replicate  exactly puredine and make some time customization that from changing the wallpaper to putting  your own name on the splash screen or to just change the default applications. So we already  have people using it. So, yeah, we have puredine craftivism where it was a special version  developed for the art gallery in Bristol. CD-Straw is a Greek security thingy, this throw that  is using puredine as basis. Bogotrax is a Colombian distribution that was used for a  lot, lot of projects recently in Colombia. And then everyone, it's very easy to branch  and fork the script to make your own stuff. So tomorrow, what do we want to do? We want  to close, to work closer to art and design communities. What does that mean? That means  that usually the puredine team is broken down is people who are interested in more specific  things. For example, we have supercollider developers working with us and they know how  to package correctly and to run supercollider on puredine. So every time there is something  new for supercollider, they have access to everything so they can make the changes and  they can push the changes to us. We don't have to do it ourselves. Same for flexors.  That's the way we want to do it. People who are good at something, they can still do it  on their own but because of Launchpad, it's very easy to propagate the changes and push  updates to us. For the documentation, we started to work on Wikibooks and we are trying to  follow a model of user case studies and not only how to use all tutorials. So we tried  to look at artists who are using puredine or designers who are using puredine and what  is their setup, what do they use and how is it done. So it brings some kind of context  to documentation which is for us very, very useful and very inspiring. And your idea here,  yes, we listen to our users, our beloved users. A lot of changes in puredine has been made  because of discussion happening on the list. We have around 300 people on the list and  it's quite high quality list in the sense that it's very, very focused and very specialist  questions. That's it. Thank you. You can go on puredine.org if you want to get more information  and try it out for yourself.  Thank you.  Thank you.
PureDyne_0_59.png PureDyne_60_227.png PureDyne_228_7127.png PureDyne_7128_7187.png PureDyne_7188_7343.png PureDyne_7344_7403.png PureDyne_7404_7463.png PureDyne_7464_7523.png PureDyne_7524_8075.png PureDyne_8076_8315.png PureDyne_8316_8411.png PureDyne_8412_11027.png PureDyne_11028_11099.png PureDyne_11100_11171.png PureDyne_11172_16607.png PureDyne_16608_16931.png PureDyne_16932_16979.png PureDyne_16980_17687.png PureDyne_17688_19355.png PureDyne_19356_21995.png PureDyne_21996_22134.png