I get a lot of email, and about once a quarter I sit down and go through my email, archiving the stuff I no longer need (I haven't thrown away an email in 20 years) and deleting everything else. I also take the opportunity to sort out my auto-filing rules. Every email from a known source goes into an appropriate folder, anything else gets lumped into a folder so that I can check its content and move it to the Spam reporting folder, delete it, or manually move it into the right place. If I've got a new client, or subscribed to some new mailing lists then I'll add them to the rules.
Documentation formats
We were discussing documentation formats today within the team, and I have to admit that personally I don’t have a preferred format. I find I use the HTML (online) formats often when I'm looking for something specific, and the PDF when I want to read something in more detail. As I spend most of my day in emacs when programming, I use either HTML or the Info format.
Documentation formats
We were discussing documentation formats today within the team, and I have to admit that personally I don’t have a preferred format. I find I use the HTML (online) formats often when I'm looking for something specific, and the PDF when I want to read something in more detail. As I spend most of my day in emacs when programming, I use either HTML or the Info format.
Obviously, with access to the source files, I can also look more closely at certain elements - for example, I like to look across the various chapters when I'm looking for a command or other text, when sometimes accessing the raw source can give me the exact info I want.
We're already working on some ways to improve the way the documentation generated - my work last work was part of that. We're experimenting with better linking on the HTML and PDF documents, improved searching, and thinking of ways in which we can provide more specific (and less weighty) manuals.
As a reminder, we already provide HTML (online and download), CHM (download), man pages and, through product releases, Info format (for use in emacs and other tools).
I'd be interested to hear what formats people prefer - do you use the Mysql .info manual within emacs? Is there a format you use that we don't support? Any other improvements you'd like to see ?
Deep in the Docs
This week, and specifically today, marks a minor milestone in my employment at MySQL—I’m finally a full time employee, no longer on probation. It has also been probably the busiest week since I started at MySQL, except for the week spent at the developers’ conference in Sorrento.
Deep in the Docs
This week, and, specifically, today, marks a minor milestone in my employment at MySQL - I'm finally a full time employee no longer on probation. It has also been probably the busiest week since I started at MySQL, except for the week spent at the developers conference in Sorrento.
ZFS, a new breed of filesystem
One of the key features of Solaris 10 is the new ZFS (Zettabyte File System). The new Solaris 10 06/06 update 2 (release notes is the first of the open releases to support a stable version of ZFS.
ZFS itself covers two aspects of data storage, first it treats all physical volumes logically (which means you gain the potential for features like redundancy, or aggregation of multiple devices into a larger resource) and then it treats all filesystems as virtual (which means you can create a filesystem to the size you want, across all available logical volumes).
ZFS, a new breed of filesystem
One of the key features of Solaris 10 is the new ZFS (Zettabyte File System). The new Solaris 10 06/06 update 2 (release notes is the first of the open releases to support a stable version of ZFS.
ZFS itself covers two aspects of data storage, first it treats all physical volumes logically (which means you gain the potential for features like redundancy, or aggregation of multiple devices into a larger resource) and then it treats all filesystems as virtual (which means you can create a filesystem to the size you want, across all available logical volumes).
ZFS, a new breed of filesystem
One of the key features of Solaris 10 is the new ZFS (Zettabyte File System). The new Solaris 10 06/06 update 2 (release notes is the first of the open releases to support a stable version of ZFS.
ZFS itself covers two aspects of data storage, first it treats all physical volumes logically (which means you gain the potential for features like redundancy, or aggregation of multiple devices into a larger resource) and then it treats all filesystems as virtual (which means you can create a filesystem to the size you want, across all available logical volumes).
Getting physical with security
I've just been reading yet another rundown of data breaches and it continues to amaze me that so many are actually based around some sort of physical, rather than technical, issue.
I learned long ago that all computer security starts with the physical side – after all, there is no point having secure logins, firewalls and other electronic security if somebody can walk in off the street and take your servers and equipment from unlocked and insecure server rooms and desks.
Getting physical with security
I've just been reading yet another rundown of data breaches and it continues to amaze me that so many are actually based around some sort of physical, rather than technical, issue.
I learned long ago that all computer security starts with the physical side – after all, there is no point having secure logins, firewalls and other electronic security if somebody can walk in off the street and take your servers and equipment from unlocked and insecure server rooms and desks.