Swap space - The Answer

Dan Osterrath do3 at mail.inf.tu-dresden.de
Mon Nov 11 17:01:39 PST 2002

Hash: SHA1

> 1) remote login to a machine via ssh
> 2) install a new version of ssh 'over' the existing one
>    -> the previous sshd is _not_ overwriten! It is just unlinked, and a new
>       one is created elsewhere on the filesystem.
>    -> you keep goin' on with the 'old' one.
> 3) The machines 'swaps-out' the old sshd, but because blocks are not freed
>    it is capable of re-reading them.
> 4) when 'resuming' your 'old' sshd session, the ssytem is able to get the
>    'old' sshd. Any new connection will use the new sshd.

Ok, that would be a solution but what about the seperation of code and data?

Another example:
Program x is executed and modifies its own code in memory. (For example there 
is a counter in the code segment.) When it is swapped and re-read the counter 
would be set to the initial value.

> Am I being clear? Correct me if I say nonsense ( it's a bit late here in
> France! ;-) ).

Here in germany too.  :-)

- -- 
- ----------------------------------------------------------------------
%> ln -s /dev/null /dev/brain
%> ln -s /dev/urandom /dev/world
%> dd if=/dev/world of=/dev/brain
Version: GnuPG v1.0.7 (GNU/Linux)


Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-support' in the subject header of the message

More information about the lfs-support mailing list