I’ve used DokuWiki for several years now and appreciated the ease of installation and use, the speed, but I never truly felt comfortable with the wiki requiring write access to its directory structure to store its versioning information. That and moving/deleting the pages seemed required command-line access. While I was mostly ok doing that myself, I couldn’t expect contributors to be comfortable doing so.
It served its purpose though, and for that I’m grateful. Of course to be fair, I’m also moving away from it because I use MediaWiki at work and am wanting to standardize on that.
So, I’ve been migrating content from the old wiki to the new one and it’s been going pretty well so far. The new wiki isn’t running as fast as I’d like, but I blame the current server configuration for that. While I work on moving the last handful of pages, I’m redirecting old content to the new system so any existing search engine traffic will find their way to the right pages.
For someone that previously had no experience installing/configuring MediaWiki it really wasn’t that bad. I’m also new to using Git, so installing MediaWiki using Git was a good excuse to expose myself to it again. While I still prefer Subversion for all of my work, I need to get used to it for other projects I plan to interact with.
Note to self:
I started the installation on July 4th and wrapped up basic configuration on the 7th while migrating content is still an ongoing process. I hope to wrap up by this Saturday.
Note: There is a newer version of this document here.
For all steps listed, I’m working with an Ubuntu 10.04 LTS virtual machine. It consists of a single disk (/dev/sda) that I didn’t size properly when I originally created the VM.
Later I added a second disk (/dev/sdb, independent of snapshots) to hold audio files from ripping cds prior to transferring to them to a player. I did not add this disk to the existing logical volume.
Now we’re going add a third disk (/dev/sdc) to the VM and place it in the same volume group as the original disk to help alleviate the space problem as shown here:
Filesystem Size Used Avail Use% Mounted on
7.3G 6.5G 487M 94% /
none 245M 264K 244M 1% /dev
none 249M 1.1M 248M 1% /dev/shm
none 249M 92K 249M 1% /var/run
none 249M 0 249M 0% /var/lock
none 249M 0 249M 0% /lib/init/rw
/dev/sda1 236M 54M 170M 24% /boot
/dev/sdb1 30G 497M 30G 2% /media/bucket
.host:/ 79G 68G 12G 86% /mnt/hgfs
(Full disclosure: This book was provided for review at no cost to me)
What you should know
- To borrow someone else’s phrase, this is NOT a “small form linux for dummies” title, and assumes you are a fairly knowledgeable about computers.
- Even though the front cover mentions Fedora, the coverage is minimal; whether that is good or bad is up to you.
- The majority of the book covers command-line applications, although there are GUI applications mixed in the later half of the book.
- While the command-line suggestions the book gives are solid, many of the GUI applications are no longer maintained and in my opinion should not have been anything more than a footnote.
- Errata pages for this book:
After having the moderation queue slammed by comment spammers, I’ve re-enabled the requirement to create an account when leaving a comment. I thought it would be easier for visitors to forgo that requirement, but I’ll never be able to keep up with spam unless I turn the requirement back on. *sigh*
I’m reading through Linux Pocket Guide, 2nd Edition and came across this option for the shutdown command:
-k Kidding: don’t really perform a shutdown, just broadcast warning messages to all users as if the system were going down.
Who says SysAdmins don’t have a sense of humor? 😉