| 1 |
Couple things, |
| 2 |
|
| 3 |
1) I forgot to mention that currently baselayout cannot be packaged, it |
| 4 |
must be "built" on each server. Annoying but not a huge deal, since the |
| 5 |
ebuild is mostly file swaping. |
| 6 |
|
| 7 |
2) Not running 'emerge sync' from each server is actually harmful to the |
| 8 |
server. You might be able to use 'emerge regen' to mitigate most of |
| 9 |
this, but I haven't investigated it that fully (since I switched from |
| 10 |
NFS /usr/portage to a BINHOST). |
| 11 |
|
| 12 |
3) The .keep file prevents an emerge clean from deleting an empty directory. |
| 13 |
|
| 14 |
Trust me the BINHOST method works much better than /usr/portage shared |
| 15 |
over NFS. |
| 16 |
|
| 17 |
jbw |
| 18 |
|
| 19 |
Sancho2k.net Lists wrote: |
| 20 |
|
| 21 |
>>Sancho2k.net Lists wrote: |
| 22 |
>> |
| 23 |
>> |
| 24 |
>>>Joby Walker said: |
| 25 |
>>> |
| 26 |
>>> |
| 27 |
>>> |
| 28 |
>>>>>A Pentium3 live CD should work just fine on a Pentium4, if I understand |
| 29 |
>>>>>your question. |
| 30 |
>>>> |
| 31 |
>>>>I agree. And I would recommend installing the stage2 .tbz2 instead of |
| 32 |
>>>>stage1 and bootstrapping. You can always do a deep emerge from your |
| 33 |
>>>>package base to replace the Live CD software with your standardized |
| 34 |
>>>>packages. |
| 35 |
> |
| 36 |
> |
| 37 |
> One thing that we've ran into is that at least one package so far won't |
| 38 |
> emerge/update under our plan. Our "plan" was to NFS export /usr/portage |
| 39 |
> out from our master server which would then be mounted on all other Gentoo |
| 40 |
> servers. The mount is read only to ensure that another admin doesn't for |
| 41 |
> example delete /usr/portage, or emerge sync before we determine it should |
| 42 |
> be done, or whatever. |
| 43 |
> |
| 44 |
> Now we are at the point with our first test installation using this plan |
| 45 |
> that we are running an emerge system to build the system after a stage2 |
| 46 |
> tarball has been used to create another server. The update is getting to |
| 47 |
> sys-apps/baselayout and bailing out because the file /usr/portage/.keep |
| 48 |
> cannot be written (read-only filesystem). |
| 49 |
> |
| 50 |
> Have we run into an inherent flaw in our system by assuming that packages |
| 51 |
> should never need to write to /usr/portage? Is baselayout the only one |
| 52 |
> that does this? What is the purpose of the .keep file? The version in |
| 53 |
> question is baselayout-1.8.6.13. |
| 54 |
> |
| 55 |
> TIA, |
| 56 |
> |
| 57 |
> DS |
Archives