| 1 |
Hello, |
| 2 |
|
| 3 |
I'm interested in putting together a gentoo mangement node subsystem to aid in |
| 4 |
multi-gentoo administration. |
| 5 |
|
| 6 |
The immediate target is checking for security updates. |
| 7 |
|
| 8 |
For this, I've come across a problem regarding root handling which I've opened |
| 9 |
a bug for here: |
| 10 |
https://bugs.gentoo.org/show_bug.cgi?id=129054 |
| 11 |
|
| 12 |
After sorting this issue, I was able to successfully test a remote machine for |
| 13 |
glsa on the local node, by transferring its VDB to the local machine, and |
| 14 |
also find out which packages needs updating. |
| 15 |
Taken into account that the remote machines are backends which by security |
| 16 |
requirements do not have any access to the internet, this saves the manual |
| 17 |
work of downloading the packages and placing them of the servers - and this |
| 18 |
worlds quite well, since I can emerge -f for a remote machine. |
| 19 |
|
| 20 |
Another detail I need to sort out - does portage use ${ROOT}/etc/ or |
| 21 |
just /etc ? Since I would need to store the useflags and customization for |
| 22 |
each remote host, it is a requirement. |
| 23 |
|
| 24 |
I've came across another problem as well. |
| 25 |
importing portage will go through its initialization, checking VDB and sorts, |
| 26 |
so that if I'd like in to switch a VDB I'll have to re-import portage. Since |
| 27 |
I do not know of a way to re-import portage in python, I've worked around |
| 28 |
this by changing ROOT env and then call portage via os.system calls. |
| 29 |
On my humble amd 2600 machine this yields a 8 seconds average per VDB change. |
| 30 |
|
| 31 |
Is there something I can do beside replicating the init code into a function, |
| 32 |
change root and recall the init function again? |
| 33 |
|
| 34 |
Is there a better way of doing this? |
| 35 |
|
| 36 |
|
| 37 |
-- |
| 38 |
Eldad Zack <eldad@g.o> |
| 39 |
Key/Fingerprint at pgp.mit.edu, ID 0x96EA0A93 |
Archives