Matthew Cooke

This is how I managed to resize a VMware image for Fedora 8.

I started with a VMware Fedora 8 from thoughtpolice and a copy of VMWare Fusion.

Step 1 Resize the virtual disk

Under OS X run:
/Applications/VMware Fusion.app/Contents/MacOSdiskTool -X 40Gb fedora-8-i386.vmdk

(where fedora-8-i386.vmdk is the VMWare disk image file)

Step 2 Create an Ext3 partition in the free space.

Download the latest GParted ISO.Connect it to Vmware Fusion (VirtualMachine | CD/DVD | Choose Disk Image)

Restart Vmware but during the initial boot go into the virtual bios settings and change the boot order to make CD boot before hard disk.

Restart VMware to boot up GParted. (You can not resize the partition as it shows as unknown - but do not cry at this point!)
Select the free space and turn it into an ext3 partition.

Shutdown and disconnect the Virtual GParted CD Image.

Step 3 Adding the new partition into the Logical Volume.

I booted up into fedora to change the Logical Volume size - this may not be the best way to do it but it worked for me. then as root i executed the following.

pvcreate /dev/sda3

vgextend VolGroup00 /dev/sda3
vgdisplay -v VolGroup00

Somewhere it will display a number for Free PE on /dev/sda3

Now enter
lvextend -l xxxx /dev/VolGroup00/LogVol00

where xxxx is the Free PE number.

Finally the last step is a bit scary it resizes the partition to make use of the larger volume whilst the filesystem is mounted. But it did seem to work for me!

resize2fs /dev/VolGroup00/LogVol00

After a while the result should show something like:

resize2fs 1.40.2 (12-Jul-2007)
Filesystem at /dev/VolGroup00/LogVol00 is mounted on /; on-line resizing required
old desc_blocks = 1, new_desc_blocks = 2
Performing an on-line resize of /dev/VolGroup00/LogVol00 to 8380416 (4k) blocks.
The filesystem on /dev/VolGroup00/LogVol00 is now 8380416 blocks long.

And bingo my disk size has gone up from 7gig to 30Gig

[root@localhost dev]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
31G 3.1G 27G 11% /
/dev/sda1 190M 13M 169M 7% /boot
tmpfs 125M 12K 125M 1% /dev/shm

“In the middle of difficulty lies opportunity.”

Let’s start off with the basic principals of a wiki. The original C2 wiki covers the basics of why wikis work pretty well. Of particular note is the following:

“Wiki is not WysiWyg. It’s an intelligence test of sorts to be able to edit a wiki page. It’s not rocket science, but it doesn’t appeal to the VideoAddicts. If it doesn’t appeal, they don’t participate, which leaves those of us who read and write to get on with rational discourse.”

So when I tell you that jotspot is a so called WYSIWYG wiki you would be right to be suspicious! After all ,we all know the kind of crap that WYSIWYG generators generally produce (see MS Frontpage!). But I was willing to give Jotspot a go. Well, here are some of the improvements jotspot has made to the concept of the wiki:

• Quick and simple to create new page.
• Jotspot improves this experience by assuming you perhaps want to create a spreadsheet every time you try to create a new page.

• Wiki-syntax is not WYSIWYG
• Jotspot improves on this experience by defaulting you to WYSIWYG rather than wiki syntax this enables lazy users to mess up your wiki markup very quickly.
• Better still, using the default WYSIWYG often actually breaks the pages so they can no longer be edited in normal markup mode. Ever. Genius.

• Original wikis used a simple textarea for input.
• Jotspot improves on this with Web2.0 goodies such as pages that keep refreshing for no reason and sucking all your CPU.
• Jotspot also uses a javascript pulldown menu instead of a button, just to edit in markup mode! This is both annoying and broken in some browsers.
• The usual form page doesn’t appear in the history, so no navigating back and fore. Instead when you click back you get an annoying javascript popup telling you maybe you didn’t want to move off the page because you will lose everything. Which indeed you will.

Finally I’d just like to share some of my favourite random jotspot errors:
Additional information:
com.s3.script.lib.JotLibException: function filterBadHTML: parameter html: no value specified.

After which jotspot becomes unuseable.

Additional information: javascript evaluation exceeded threshhold