[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[p2-dev] Provisioning p2 with p2?
- From: Fredrik Alströmer <roe@xxxxxxx>
- Date: Wed, 25 Feb 2009 14:38:01 +0100
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; b=Mz8Mb/y0zS3PKMAtpWqfVn+BCwwZuqRDoeZt4MLVEbO7jxY1E06qNgaI1hMNeuqN4P zD9Xt5SHvWCzt81+/85Fwd67Lx12S6bUZ4lczG/rumTx87c0rI+0IVIOauo6dXFOmbJ2 pmdSuFYrTVIWyIlyTJef+DoEJ55eV9G7U43fk=
I think I read somewhere that, whatever is managed by p2 you shouldn't
touch, and whatever you manage p2 won't touch. This makes perfect
sense, however there's one thing that's not completely clear to me. Is
it one of the purposes of p2 to be able to create a new profile (using
p2, that is, like with the p2 agent), install p2 into that profile,
and then let it manage itself?