Motivation:
As you all know, telnet and ssh allow you to login into remote systems. This is nice to do some stuff there, you perhaps do complex calculation on that remote system from your local box without loosing any CPU time used by the remotely executed complex calculations.
What if you now want to act on your server, but need to save as much CPU time as possible?

Imagine this case, you have two Gentoo boxes, one acting as your server, and one beeing your desktop box, both are reachable from your LAN, your server is your broadband to the internet.

While you definitely feel free to update your desktop box nearly every day without caring about cpu usage nor about availability, it isn't recommented to do so on your server, too. gcc, invoked by emerge, is eating to much CPU on a running server system wich should still stay to serve as before.

Okay, what did we do? We just got our server system into our local machine, our desktop. Now we have exactly the server environemnt on our desktop, except the hardware. The hardware has changed, to hopefully the better one, but compatible. This increases compilation and other administrative task's speed. That means, we have a locial reversed telnet session on our desktop to the server we talk about.

Now you can do any administrative tasks you like, most often used will probably indefinite be emerge -bu system ;)

To exit the virtual server environment, you must care about the instructions below:

I am not that up to date with utilizing ssh yet, but I feel this might come in handy. Now to clarify the creation and mounting of /mnt/server locally, Is this like using the Samba share??? or just tricking the session into a remote mount?

Okay, what did we do? We just got our server system into our local machine, our desktop. Now we have exactly the server environemnt on our desktop, except the hardware. The hardware has changed, to hopefully the better one, but compatible. This increases compilation and other administrative task's speed. That means, we have a locial reversed telnet session on our desktop to the server we talk about.

You didn't establish a reverse telnet session, you simply mounted a remote filesystem and are performing operations on it locally. It's not anything like reverse telnet.

A normal telnet connection works like this: a client connects to a server, logs in, and gets a shell prompt where they can type commands. A reverse telnet connection (by standard definitions) works like this: a server connects to a client and provides a shell prompt. Trojans sometimes do this to "phone home" and give their creator a root prompt so the person can do whatever they like on their system.

So, to clarify, that's not what you just did, therefore your post is mis-named. _________________I don't believe in witty sigs.

So, to clarify, that's not what you just did, therefore your post is mis-named. ;)

So, okay, thanks, I understand. But, as you probably have seen, English can't be my native language, even if I would like so :( All I wanna say is, sorry for that kindly bad named subject, how would you name it? (How to save cpu on remote systems for administration)? Sorry, I really can't bring it up in a short sentence to clarify what I intend to offer in this article :( But this hopefully doesn't make the content helpless..... thanks ;)

I am not that up to date with utilizing ssh yet, but I feel this might come in handy. Now to clarify the creation and mounting of /mnt/server locally, Is this like using the Samba share??? or just tricking the session into a remote mount?

What kind of python are you using? (because I didn't find the fcntl.py as mentioned in your dump, check whether you've /usr/lib/python2.2/lib-dynload/fcntl.so instead)

Why emerge breaks down in building less may have different reasons. One could be, that you have splitted up your remote system in different partitions but didn't import them correctly. Another could be that the routine searching for these files is also defined in pything language and generates an probably an implicit error here.

Did you try NFS?
I can't try samba right now, I it seems that I am going to.

Okay, according to your posting change, "rm -f include/asm" really can't work, because it is a directory, try removing it recursively using "rm -rf include/asm".
But, sorry, why do you want to delete it?

Opps, just check, the "DeprecationWarning" error happen on this host (cyrix m2) system as well. Re emerging the 2.2.1 right now to see what happen. slow... and done 2.2.1-r5 still no good. Still the same warning everytime I use emerge.

The portage version is 2.0.43. re-emerge portage didn't help either.

/usr/lib/python2.2/lib-dynload/fcntl.so is there

I did not issue "rm -f include/asm" it was part of (kickoff by) "make menuconfig". I think this error might not be related to the above warning.

I was trying to see if I could use the P4 to make a new kernel for the old cyrix m2. I have only samba network setup for the environment. On the host cyrix m2, emerge and compile kernel both OK even eith the warning.

Assuming that Cyrix M2 is compatible to the P4 it shouldn't be the problem. However, it may be probably a portage bug?
What about emerging less locally? Does this work?
Furthermore, you can use the tool strace to trace the system calls for emerge. dump the output into a log file, than search for the error message and what functions actually was invoked. This may help to find the error and probably fix.

I guess tracing the problem is not what I could do at this stage of my Linux skill . Maybe I will try the NFS route if I could find some time to set it up and build the right kernel this weekend. On the Cyris M2 is kind of slow.

just for those still or now interested in. Since I need it some more frequently I wrote little script that automatically does the setup for you each time you want to fake a foreigns environment.

What does the script:
When you're logged in to a machine X-host (with better hardware) and want to do some stuff on machine Z-host (wich allows nfs exporting of root dir /) you may surely want to call this script as follows:

Code:

fakehost.sh Z-host

This script does automatically mount the remote directories needed as well as binds the the local required into, too. Afterthen fakehost.sh provides you a already initialized environment using chroot shell (we all know this already). Already initialized means the standard procedure you would do every chroot (env-update, source /etc/profile ATM).

Once you've done your things in that virtual environment just type exit to exit it. fakehost.sh also does an automatic cleanup, but remember once this script terminated unexpected to call fakehost.sh Z-host cleanup by hand.

# /home is exported to jupiter's /home so, just binding our own
# saves net traffic and though speeds up further work
# NOTE: THIS MUST NOT BE THE CASE FOR YOU, SO COMMENT THIS OUT THEN.
# TODO: check wheter faked host has mounted our /home, so that binding
# may be done in a generic way (for anyone ;)
mount --bind /home ${prefix}/home || error "Error binding /home"
}