Faheem Mitha <[EMAIL PROTECTED]> writes: > Let me just clarify something. When I saw the error I reported, I was > able to 'fix' it, and then proceed; however the process shortly after > bombed at the 'vos create' step.
> It is entirely possible that my 'fix' was not actually a fix and > introduced other errors. In any case, it would be good if you could tell > me how I need to patch the Debian afs config scripts to fix the problem > with CellServDB, because then I can test the modified version and report > if I run into any further problems. Note I'm using the sarge version, > though I can, of course, use a more recent version if you prefer. I think the right thing to do is for afs-newcell to just write out the CellServDB file directly. It knows how to do so, a new cell shouldn't have any existing entry where overwriting it is a problem, and there seem to be some oddities with bos addhost (although I want to also track those down and fix them upstream). The first rework of this will just write out the CellServDB directly, and then later I'll see if I can get bos addhost to work. > In regard to the guide below, it seems reasonably clear, however, I > think it would still be nice to provide an explicit transcript, to the > extent practicable, so people have something to compare to. I realise > you can't cover all the options, but perhaps just the basic ones? Oh, I'm planning on leaving the existing transcript, certainly. I think it's very useful. I mostly wrote this guide following the transcript and explaining all of the other options and possibilities. The transcript is from a somewhat older version of the packages, so I may go through the excercise of regenerating it at some point, but it's still basically accurate. >> 1. If you do not already have a Kerberos KDC configured, do so. You > It would be nice to say what a KDC is here, or at least spell out the > acronym. Done. >> 7. Create some space to use for AFS volumes. You can set up a separate >> AFS file server on a different system from the Kerberos KDC and AFS >> db server, and for a larger cell you will want to do so, but when >> getting started you can make the db server a file server as well. >> For a production cell, you will want to create a separate partition >> devoted to AFS and mount it as /vicepa (and may want to make >> multiple partitions mounted as /vicepb, /vicepc, etc.), but for >> testing purposes, you can use the commands below to create a >> zero-filled file, create a file system in it, and then mount it: >> >> dd if=/dev/zero of=/var/lib/openafs/vicepa bs=1024k count=32 >> mke2fs /var/lib/openafs/vicepa > [snip] > Minor point, but wouldn't it be better to make an ext3 partition here? The reason why I didn't is that ext3 is still an optional file system in the kernel, and if someone is running a kernel they built themselves, they may not have ext3. Certainly, for a production file server, you'd probably want to use ext3. But this loopback trick is explicitly not for production use and I figure it was best to err on the side of safety. > I'll provide more comments once I actually work through this. But I'll > wait on your fix before I do that. I'm testing new scripts incorporating fixes to work with dynroot right now, and if they work for me, I'll send you copies of the current ones. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
