The views or opinions expressed on this blog are my own and do not necessarily reflect the views or opinions of my current employer. The views or opinions expressed by visitors on this blog are theirs solely and may not reflect mine.
Entries tagged as opensolaris
Related tagsadministration article backup blog btrfs community conference containers development domain event free froscon linux lvm meeting mysql oracle oss otn presentation RPM seminar site news snapshots social solaris storage sysadmin tools utility virtualization workshop zfs bzr cluster code collaborating configuration contributing databases distribution drizzle drupal encryption gallery hardware hint hosting innodb mailinglist multimedia mylvmbackup news opensource OSS packaging perl php pictures programming python rpm slides subversion suse thinkpad travel university update web webinar betatest appliance cmake compiling connector drivers engine forge gis gui installation internals opengis plugins spatial studio sun virtualbox xen codebits concert eclipse fosdem git intellij java mercurial netbeans opensqlcamp planetmysql scm vacation baby recording schwag writings award bindings bof book cms contributions deutsch errors groupware gsoc guug interview jobs languages licensing life Linux linuxtag MySQL openoffice osx patches personal porting proxy sfd streaming survey twitter usergroup video voting wiki windows work amoocon brazil camera captcha cebit doag embedded falcon fisl highavailability ioug linuxcon magazines ocfs2 openworld OS/2 oscon Personal spam trademarks ukoug flightgear simulation oow Site News email logging trackball tweak bdb sqlite lamp gardening bios hotplug review security shell VoIP boox certification documentation ebook epub manual rss
Wednesday, August 11. 2010
I tend to switch between Linux and OpenSolaris as my desktop operating system from time to time. To be more flexible in this setup, I store most of my work-related data (e.g. source trees, VirtualBox images) on an external 320GB USB disk drive, using the ZFS file system. While OpenSolaris supports ZFS natively, I can access the file system on Linux using zfs-fuse and I could even mount these file systems on a FreeBSD system, if needed. There aren't that many file systems that allow an easy exchange of data between (Open)Solaris and Linux – the other ones that I am aware of are FAT and UFS, which both don't give me the confidence and flexibility I need.
A while ago, I purchased a second external drive of the same size and now use both of them in a mirrored configuration. This gives me several benefits:
From my experience, ZFS is a very solid and reliable solution, providing impressive functionality with a very user-friendly UI (you only need use two commands, zfs and zpool).
Saturday, March 6. 2010
I recently received a question from Robin Schumacher at Calpont, the makers of the InfiniDB analytics database engine for MySQL: "How would you recommend we try and get bundled in with the various Linux distros?"
Since this question has come up several times before, I thought it might make sense to blog about my take on this.
First of all, please note that there is a difference between "being part of the core distribution" and "being available from a distributor's package repository". The latter one is relatively easy, the former can be hard, as you need to convince the distributor that your application is worth devoting engineering resources to maintain and support your application as part of their product. It's also a space issue – distributions need to make sure that the core packages still fit on the installation media (e.g. CD-ROMs or a DVD). Therefore they take a very close look at each package and if it's really needed to be part of the installation medium or if it's fine to provide it for download from a package repository instead.
Distributors prefer to keep their core product small and restricted to the "basic OS building blocks". While MySQL might still be considered to be a part of this, this probably does not apply to the various plugins and extensions that are available for it. Therefore the best approach is to invest some engineering time and start doing the packaging yourself, either by hiring an engineer capable of creating and maintaining the packages, or by finding someone in your community who has the required experiences and is willing to do it.
While it's of course possible to set up and maintain your own build and package hosting infrastructure for that, I recommend to make use of the existing services provided by the distributors.
The top tier distributors all provide means of offloading the maintenance of "non-core" packages to their community, offering various options for packages to be made available. For example, Novell/openSUSE provide the free "Build Service", which is capable of building packages for other distributions as well (e.g. Fedora, Mandriva, Debian/Ubuntu, etc.). In addition to automating the builds, the Build Service also takes care of the distribution via their download mirror network and ensures that your application can be found via their package search interface.
Ubuntu/Canonical have "Personal Package Archives (PPAs) – if your project is hosted on Launchpad already, that might be something to look into for providing Debian/Ubuntu packages. Alternatively you could join the Debian project and start building and maintaining your package there. They maintain a list of "Work-Needing and Prospective Packages", a description of the process on how to become a new maintainer is outlined here.
If you'd like to target Solaris/OpenSolaris as well, there is the OpenSolaris Source Juicer – a web service which allows OpenSolaris community developers to build packages (using RPM spec files) and publish them for review, so they will be included in an official package repository. The Software Porters Community Group coordinates, advocates, encourages and helps with the porting of Software from multiple Platforms to the OpenSolaris Platform.
Friday, October 16. 2009
With IntelliJ now being available under an Open Source license, developers have another option to choose from when it comes to Java-based IDEs/Frameworks (Eclipse and NetBeans being the other two prominent ones). Choice is always good, and being an Open Source enthusiast, I of course welcome JetBrain's move!
However, as I'm not really a heavy GUI-based IDE user myself, I can't really comment on which one is the best. These kind of discussions tend to turn into a Holy War anyway... In the end it's likely that each of them gets the job done and you have to come to your own conclusions, based on your personal preference and requirements.
I personally would be interested in seeing how their support for PHP or Python compares to the one in NetBeans. Their plugin repository lists more that 560 plugins, including many for database connectivity/modeling/navigation (incl. support for MySQL). I'm also glad to see that they have a plugin for Bazaar, something that I'm desperately missing from NetBeans!
Interestingly, they decided to keep a few parts proprietary, it's going to be interesting to see how this will turn out for them and if developers will be willing to pay for these extra features, considering that most of this is available for free from the other two projects.
Their Contributor License Agreement looks like it has been derived from the Sun Contributor Agreement (SCA), which is always nice to see. I assume this can be attributed to Roman Strobl - I was positively surprised to notice that he joined their team as a technology evangelist in June! Roman did a great job in spreading the NetBeans and OpenSolaris gospel at Sun before and I briefly met him at this year's FOSDEM conference in Brussels. Congratulations!
Friday, September 4. 2009
First off, I would like to thank all of the participants and supporters, particularly my colleagues Regina Steyer and Iris Musiol for the perfect logistics and co-sponsoring as well as Uli Graef, Thorsten Frueauf, Matthias Schmidt, Alexander Rubin and Joerg Moellenkamp for manning the Sun booth and the help on site.
Another big Thank You goes out to my team mates Giuseppe and Colin as well as to Sheeri K. Cabral, who were a big help in keeping the OpenSQL Camp on track and by supporting the event by giving talks. In addition to that, Sheeri recorded most of the OpenSQL Camp sessions on video and published them in record time!
So here's a quick summary of both events from my side, starting with the main conference.
Sun was a Gold sponsor of the event and we had a booth right at the main entrance area; it could hardly be missed. It consisted of two large and two small desks as well as a divider behind them. For demos, we had a (slightly noisy) Sun Fire X2200 M2 Server and four SunRay 2 Thin Clients (which by themselves triggered a lot of questions and curiosity by many visitors). The booth was flanked by rollup-banners on both sides as well as various posters attached to the divider. Here's a picture of our booth before the event opened:
We also had a number of talks in the main conference track (both German and English):
The comments and ratings of these sessions were generally very positive. Our booth was well attended, especially during the session breaks. In total, there were over 1.400 visitors at the conference over the two days.
I personally did not attend many sessions in the main conference tracks, as I was too occupied with the OpenSQL Camp and the booth organization. However, I managed to listen to Uli Graef's talk, which was a very technical and interesting session about ZFS features and internals. Being a big fan of ZFS myself, this was a very worthwhile session to be at and my impression was that it encouraged others to take a closer look at this truly amazing file system.
The second talk I attended was Sunday's keynote by Dries Buytaert from the Drupal project about "The Secrets of Building and Participating in Open Source
As for previous FrOSCons (is that the proper plural?), there was a social event scheduled for Saturday evening, providing barbecue (Steaks and Sausages as well as vegetarian dishes) and drinks. This event usually takes place outside and is always an excellent opportunity for networking and talking with key people from other OSS communities and projects. And there was plenty of time for talking - the queues for the grilled food were long...
Here is a list of other blogs and articles about FrOSCon that are worth a read (in no particular order and both German and English):
In addition to the main conference tracks, FrOSCon also provided a number of so-called "Developer Rooms" to OSS projects, so that they could organize sub-conferences or hackfests of their own. We applied for a room to set up a conference dubbed "OpenSQL Camp", related to the topic of Open Source databases, which was approved.
We then sent out a call for papers and invited people from the many OSS database communities to join us and talk about their projects. Every session proposal was published on the OpenSQL Camp web site and people were able to vote on the sessions they were most interested in via email or twitter:
The organization and scheduling of the talks and speakers was done via the FrOSCon conference system (Pentabarf), which made it very easy to perform this task and also made sure that the OpenSQL Camp sessions were included in the main conference program. Below is a full list of sessions at our subconference (see the FrOSCon Program page for abstracts, speaker info, links and slides). We had two cancellations by speakers on short notice, but were able to cover the gaps with ad-hoc presentations. I'd like to send a special thanks to Geert Vanderkelen, who gave a great presentation about MySQL Cluster despite the very short notice and some technical difficulties at the beginning!
Most talks attracted between 20-50 attendees and we had a great mix of topics from several different database projects (with a slight majority of MySQL-related talks). The Panel Discussion (moderated by me), called the "OSS Toolshed Shootout" went quite well and the speakers had a good time answering questions on various topics about their projects. Thanks again to all OpenSQL Camp speakers for making this event a success!
All in all I think that both FrOSCon and OpenSQL Camp were well worth supporting and attending - we were able to provide insight and trigger some interesting discussions among the OSS enthusiasts and developers in the audience. It was also a good opportunity in get in touch with many people of other OSS communities, fostering the MySQL (and other Sun OSS projects) ecosystem.
I personally look forward to next year's FrOSCon - a Big Thanks to the organizers for another great event!
Posted by Lenz Grimmer in Linux, MySQL, OSS, Solaris at 22:56 | Comments (0) | Trackbacks (0)
Wednesday, August 26. 2009
There have been several similar articles to this one, but I find it pretty amazing to see all these emerging and established Solaris/OpenSolaris distributions. It's a good sign of a healthy community!
So here is my collection - please let me know if I forgot one.
Third-party distributions (in alphabetical order):
Wednesday, June 3. 2009
My last post about Basic MySQL Security generated a number of interesting comments, thanks for all your feedback! I'd like to address a few points that were mentioned there:
While the problem seems to be a non-issue on Linux, Keith Murphy stated that the password might still be visible on other Unix operating systems (e.g. Solaris), as described in Bug#11952 in our bug database. According to the bug report, it depends on the implementation of "ps" — there seems to be a BSD variant (/usr/ucb/ps) as well as a SysV implementation (/usr/bin/ps).
However, on my tests on OpenSolaris (2008.11), both still displayed the password! So be aware of this when working on non-Linux systems and better double check the behaviour on your particular platform. The bug report provides a few more details about this issue, apparently it cannot be fixed for all platforms.
I also pointed out that the password will end up in your shell history and Jay Pipes emphasized this in his comment. As I wrote, you need to make sure that your shell history file is properly protected against access by other users! Usually, a chmod 600 ~/.bash_history will fix this. Most shells create these files with appropriate permissions automatically or can be configured to do so (check your shell's manual page with man `basename $SHELL`).
But there are more potential password leaks that I would like to mention, while we're on the topic: the mysql command line client maintains a history file of its own, that you should be aware of. The history is convenient for easily going back in your list of previous SQL statements by using the Up/Down cursor keys or searching for a particular query by using the CTRL+R shortcut. However, the MySQL client stores all your SQL statements in a file ~/.mysql_history in your home directory by default, similar to how your unix shell does it. So if you are adding new MySQL user accounts using the GRANT ... IDENTIFIED BY PASSWORD... statement, the user's password will be written to the history file in plain text, visible to everyone who has the appropriate file system privileges. Keep that in mind when performing administrative tasks on a MySQL server and make sure to restrict access to that file! By default, the client creates the file with only read and write permissions for the user (600), but if you want to be on the safe side you can of course remove it after you entered passwords on the MySQL command line. As an alternative, you can start the MySQL command line client by using the "-q / --quick" option, which skips using the history file for this particular session. If you can live without a command line history in general, you could simply replace that history file with a symbolic link to /dev/null:
$ ln -fs /dev/null ~/.mysql_historyAlternatively you can set the environment variable $MYSQL_HISTFILE to point to either a different file name or to /dev/null directly. By the way, all of this is documented in the mysql(1) man page as well as in the Reference Manual.
Another attack vector for local users to obtain MySQL passwords are the MySQL server log files — anyone with file system access to the binary log files can extract possible GRANT statements from there using the mysqlbinlog command! So you need to make sure that these files are properly secured from being accessed by regular users as well.
In general, the best approach is to not allow regular users to log into your MySQL Server system in the first place. Shell access should be restricted to the system's admin accounts, access to the MySQL server should strictly take place via the MySQL Client/Server protocol. Which, by the way, is not using encryption by default — make sure to use SSL or an SSH tunnel when accessing a MySQL server through an untrusted network. Otherwise you may also reveal confidential information like user passwords to unauthorized entities...
Monday, January 12. 2009
We've now concluded our call for papers for the MySQL Developer Room at FOSDEM 2009 in Brussels, Belgium, which will be open on Sunday, 8th of February from 09:00-17:00.
We received some excellent proposals and I am very excited about the schedule. Here's the quick summary of the talks:
See the Schedule page on the MySQL Forge for the detailed agenda, including the detailed session abstracts and speaker bios. These talks will soon appear in the general FOSDEM schedule, too. If you are interested in MySQL and any of the topics above, consider visiting us in Room AW1.126! Participation and attendance is totally free, though the organizers happily accept donations and sponsorships.
In addition to the Developer Room, MySQL will share a project desk with the OpenSolaris community. We are still looking for at least one more volunteer that would help us with manning the desk! If you are interested in helping out (2 hours at a minimum), please drop me a line!
My colleague Joerg Moellenkamp stepped up and established the HHOSUG - a local OpenSolaris User Group here in Hamburg, Germany. It has a web-home with discussion forums on Xing.com. Our first physical meetup will take place on Wednesday, 4th of February, 17:45. We will meet in the the meeting rooms at Sun's Hamburg offices (Nagelsweg 55, 20097 Hamburg). If you plan to attend, please RSVP here. We have the following topics on the agenda:
Luckily, Wednesday is usually the day that I am in the office anyway, so I'll just stick around. I look forward to meeting many fellow OpenSolaris fans there
Friday, January 9. 2009
A (slightly belated) Happy New Year to you! I just returned from my Christmas vacation two days ago, which I spent mostly at home and with my parents-in-law in St. Radegund, Austria. Now I am busy catching up with what has piled up during my absence (I managed to resist the temptation to check my work email during the time off).
Some MySQL-related news that came up in the past weeks and are worth sharing:
Quite a lot of exciting stuff going on, and more to come. This is a great start into the new year!
Saturday, December 20. 2008
While VirtualBox is available as a downloadable OpenSolaris package from the download page at virtualbox.org, I find it much more convenient to use the Package Manager GUI or pkg on the command line to install and update packages.
Sun provides a VirtualBox IPS package (and some others like Flash Player) from a separate "extras" repository. However, you need to obtain a key and SSL certificate before you can access this repository, which are available for free from https://pkg.sun.com/register/ after logging in with your Sun Online Account.
Once you obtained and installed these files in /var/pkg/ssl (detailed instructions are provided on the download page), you can add this repository as another "authority" and start looking at what packages are provided:
$ pfexec pkg set-authority \
So there is not that much to download by now - some additional Java packages and the Flash plugin for Firefox. There is no package for VirtualBox 2.1.0 yet, but I hope this will be updated soon...
Monday, December 1. 2008
FOSDEM 2009, one of the biggest European Open Source conferences, will take place on February 7-8 in Brussels, Belgium. Today I received a confirmation from the organizers: MySQL will have a developer room on Sunday, the 8th! This is very cool.
My idea was to organize some kind of MySQL mini-conference, with a focus on developers and DBAs. I am going to send out a more formal CfP soon, but if you have any ideas or suggestions for a talks/sessions already, please get in touch with me!
In addition to the devroom, I have also been invited to give a talk about MySQL High Availability solutions in the conference main track. In this talk I plan to cover some commonly used HA setups for MySQL, including the OSS components/tools (for Linux and OpenSolaris) involved. I will mention MySQL Cluster as well, explaining the relationship and architecture of MySQL Server and NDB Cluster. I hope this will be of interest to the audience.
I also submitted two lightning talk proposals: "New features in MySQL 5.1" and one about "Why you should use Bazaar for maintaining your OSS project", but I won't know if these were accepted until the end of December...
See you there!
Saturday, November 15. 2008
As noted in my previous blog posting, I manged to revive my old Logitech TrackMan Marble FX on Linux (openSuSE 11.1b4), using a Serial-to-USB dongle with a Prolific PL2303 chip. But I also use OpenSolaris on my Laptop quite frequently (currently testing the upcoming 2008.11 release), so I investigated if it would be possible to enable the trackball there as well.
Luckily, the Driver Manager listed the plugged in adapter and the correct driver (usbsprl) was loaded already. Now the real challenge was finding out which device node to use. Some research revealed that the driver actually comes with a manual page , which indicated that /dev/term/0 was the correct device name.
Lo and behold, I copied the InputDevice section from my Linux xorg.conf file into the OpenSolaris one, replaced the Device parameter with the appropriate one and restarted the X server. Immediate success! Now I can enjoy using my most favourite input device on OpenSolaris as well.
Wednesday, November 12. 2008
I recently installed the last release candidate version of OpenSolaris 2008.11 (ISO image available from here) and I am happy to note that the audiohd driver now supports the Intel soundchip (82891H) in my Lenovo Thinkpad T61 out of the box! This was one of the glitches I observed with 2008.05. In general, I am very impressed by the OpenSolaris driver support for this particular laptop - everything except for bluetooth is supported now. On the downside, suspending to RAM still fails for me, but I have not looked into this very deeply yet.
But what good is a working sound driver, if you don't have apps that produce sounds? Be default, the media players included in the distribution lack support for most codecs, e.g. MP3 or video formats. This is not much different from most Linux distributions, as these codecs are usually protected by patents or proprietary licenses which require the user to install these separately. Here are some hints on how to enable better multimedia support on OpenSolaris.
If you want full multimedia support and an choice of video players/codecs, you should add the Life With Solaris (LWS) package repository to the package manager:
$ pfexec pkg set-authority -O http://pkg.lifewithsolaris.jp:10000/ pkg.lifewithsolaris.jp
You will now be able to choose a new package repository from the dropdown list, which allows you to select players and codecs for download/installation. The packages will be installed in /opt/LWS, so you need to add /opt/LWS/bin to your $PATH, if you want to start the applications from the command line. But the packages will create menu entries for the GNOME desktop as well.
Thursday, September 11. 2008
If you are a maintainer of an Open Source project, you currently have plenty of choice when it comes to getting your project hosted for free. One criterion could be your software configuration management system (SCM) of choice.
Some of the hosting services that I am currently aware of and the choice of SCM they offer include:
As disclosed by Tim Bray some days ago, there now is another option - Kenai is open for project hosting (currently by invitation only)! In his blog post, he interviews Nick Sieger, one of the developers behind this project about their motivation and intentions:
We need to demonstrate credibility in building on top of more traditional LAMP/SAMP web stacks (not just Java EE); and we need to show viability of Sun technologies and hardware for next-generation web applications.
In a nutshell, Kenai is a platform for:
Some of the features that are currently available include:
Reading the interview with Nick and looking at some presentations slides for RailsConf from Fernando Castano (a jRuby and Database performance engineer at Sun and another member of the project team), I was able to gather a list of the tools and technologies they used to build Kenai:
I found it interesting that they decided to deploy and run the Rails application as a war file within the Glassfish application server (using Warbler). By the way, the fabolous OpenSUSE Build Service is a Rails application, too! So far, the entire site is powered by a single MySQL instance with query cache enabled.
The project is hosted on the following infrastructure:
You should check out Fernando's presentation for more technical details, tuning info and how they benchmarked the setup - it contains a number of useful tuning hints and performance graphs.
Nick also talked a bit about their future near term plans: to improve the usability and feature set, incrementally improve the site navigation and layout and adding support for hosting files/release downloads. They also consider offering Jira as an option to Bugzilla for bug tracking and Git as another SCM option.
There is an IRC channel #projectkenai on freenode.net, to get in touch with the developers directly. The mailing list for the Project Kenai site itself, is firstname.lastname@example.org - you can subscribe to this list here.
Wednesday, September 10. 2008
Tomorrow (Thursday, 11th of September) at 9:00 PST/16:00 UTC/17:00 GMT/18:00 CET, there will be an new free MySQL University Session. MySQL University started as an internal training program for MySQL engineers, to share and spread knowledge about their areas of expertise and has been available to the public for quite some time now. It covers a wide range of technical topics around the MySQL Server and usually takes place once per week.
For the first time, the presentation will not be performed by (former) MySQL employees/developers, but by two of our "Sun Classic" colleagues: Jyri Virkki (OpenSolaris Web Stack community lead) and Murthy Chintalapati (Sr Engineering Manager, Web Stack development) will talk about the OpenSolaris Web Stack:
OpenSolaris Web Stack is an OpenSolaris project and community building an integrated stack of popular open source web tier infrastructure technologies such as Apache HTTP server, MySQL, memcached, PHP and Ruby On Rails optimized for Solaris platform. This session introduces OpenSolaris Web Stack, its status and future development including addition of newer technologies such as lighttpd, Varnish etc., as well as the ease of use features for developers and deployers. We will also be discussing an experimental web stack IPS package repository and it could be leveraged to build and make available popular end user applications such as Drupal.
MySQL University sessions are free to attend - all you need is an IRC client (to post your questions and comments) and an audio player capable of playing back an OGG audio stream, so you can listen to what is being said. See the Instructions for Attendees on the MySQL University pages for more information on how to log in and attend. The audio stream will be recorded and published on the MySQL University pages for later consumption, in case you can't make it or want to listen to a previous session.
(Page 1 of 1, totaling 15 entries)
Show tagged entries
Original content in this work is licensed under a Creative Commons License