[ext2resize] ext3, lilo?

[<ei...@th...>]

I'm writing up documentation for "how to turn a Martian NetDrive into
an OpenAFS server", and one of the steps is, simply,

 boot to single user mode
 ext2resize / 4G
 reboot

Now, this *worked* for me, but on looking at some of the docs, I have
a couple of questions.

1) / is actually an ext3 partion, not ext2.  However, having been
   unmounted cleanly, the journal should be empty, so it should be
   identical in that regard.  Is this actually true, or did I just get
   lucky, and should I tell people to delete the journal, remount as
   ext2, resize, then tune2fs -j and make it ext3 again?

2) I didn't rerun lilo.  I suspect that since the partition in
   question had around 1G of data on it, that there was simply nothing
   beyond the cut-off point, so nothing had to be moved.  

   a) is that true, that in that case nothing would move?
   b) would -v be enough to find out if it moved something, namely the kernel?
   c) should I tell people to re-run lilo anyway?

Thanks.  (I'd be happy if some better hints about this made it into
the man page, but I don't see anything in the docs under debian
ext2resize 1.1.17-3.)

			_Mark_ <ei...@th...>
			The Herd Of Kittens