Logo Usage Request
Hello All, I've been referred here to ask for permission to use the DragonFly BSD logo. Background- I'm with the BSD Certification Group. We are putting together the BSD Professional exam and we will be using the AQEMU program for managing virtualized sessions for the lab exam. AQEMU can display icons of the operating systems it manages. Unfortunately there is no icon for DragonFly BSD. I've managed to make a logo and integrate it with our own distribution of AQEMU that we will be using for the lab exam. See the following URL for a screen capture: http://sixshooter.v6.thrupoint.net/dfly/aqemu.png It is this use of the logo that I'm requesting permission to use. Please let me know if this use meets your approval. Best Regards, Jim Brown BSD Certification Group PS- The BSDP lab exam will be available sometime in Q1 of 2011. We will announce the exam when it becomes available. URLs if you are interested: AQEMU: http://sourceforge.net/projects/aqemu/ BSDCG: http://www.bsdcertification.org BSDP: http://bsdwiki.reedmedia.net/wiki/BSDP.html
Re: Logo Usage Request
On Tue, August 24, 2010 4:35 pm, Jim Brown wrote: I've managed to make a logo and integrate it with our own distribution of AQEMU that we will be using for the lab exam. See the following URL for a screen capture: http://sixshooter.v6.thrupoint.net/dfly/aqemu.png It isn't really a permissions thing as much as it is just a way for us to know where the logo's floating around. I don't see any problems with this. There's vector versions of the logo linked at the first item on the images page: http://www.dragonflybsd.org/images/ Specifically: http://www.dragonflybsd.org/images/DragonFly_BSD.eps http://www.dragonflybsd.org/images/DragonFly_BSD.svg http://www.dragonflybsd.org/images/DragonFly_BSD.ai You can create a 'clean' image from those files at any scale, if that helps.
Heads up: Binary packages updated
The 'stable' links for binary packages on avalon now point at pkgsrc-2010Q2. This means pkg_radd will pull from a newer batch of packages. Watch out - some of the newer packages will have newer dependencies, so you may be in for some number of upgrades to use these newer binary packages. If you keep a /usr/pkgsrc to match those binary packages (and you should if you are using them), you'll want to update it to match pkgsrc-2010Q2, also. Change /usr/pkgsrc/CVS/Tag to have 2010Q2 in it and 'cvs update -dP' is one way to do it.
