planetlab-users — Discussion among PlanetLab users; but send trouble reports to planetlab-support

RE: [Planetlab-users] dynamic slices doc

[Sedayao, J. <jef...@in...>]

Yun,

This is back now.

Jeff

-----Original Message-----
From: pla...@li...
[mailto:pla...@li...]On Behalf Of Yun Mao
Sent: Friday, January 09, 2004 11:29 AM
To: pla...@li...
Subject: [Planetlab-users] dynamic slices doc


Hi, where can I find dynamic slice programming interface doc? The link =
at
planet-lab.org
(http://www.planet-lab.org/doc/InfraGuide.php#DynamicSlicesAPI) is =
broken.
Thank you!

Yun



-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Planetlab-users mailing list
Pla...@li...
https://lists.sourceforge.net/lists/listinfo/planetlab-users

[Planetlab-users] dynamic slices doc

[Yun M. <ma...@ci...>]

Hi, where can I find dynamic slice programming interface doc? The link at
planet-lab.org
(http://www.planet-lab.org/doc/InfraGuide.php#DynamicSlicesAPI) is broken.
Thank you!

Yun

Re: [Planetlab-users] useful ssh tools/links

[Neil S. <ns...@cs...>]

On Jan 9, 2004, at 10:57 AM, Aaron Klingaman wrote:
> As for Macintoshes, I'll have to let someone else fill in on which 
> tools work
> well. :)
>

Mac users should see:
http://www.cs.washington.edu/homes/bershad/Mac/ssh/ssh.html
and possibly:
http://www.phil.uu.nl/~xges/ssh/

As usual, it just works.

-neil

Re: [Planetlab-users] useful ssh tools/links

[Scott A. <at...@cs...>]

On Jan 9, 2004, at 1:57 PM, Aaron Klingaman wrote:

> Hi all, I thought I'd put together an email of some useful ssh tools 
> and
> websites, if you are new to ssh, or not aware of some ways to make 
> using it
> easier.
>
> <snip>
> As for Macintoshes, I'll have to let someone else fill in on which 
> tools work
> well. :)

On MacOSX, openssh is installed by default. For Mac OS 9 and earlier, 
there is MacSSH (http://pro.wanadoo.fr/chombier/).

Scott

[Planetlab-users] useful ssh tools/links

[Aaron K. <al...@CS...>]

Hi all, I thought I'd put together an email of some useful ssh tools and 
websites, if you are new to ssh, or not aware of some ways to make using it 
easier.

First, this document has a good overview of the most common uses of ssh:
http://kimmo.suominen.com/ssh/

Also, if you haven't seen this document, it outlines some basic points on 
using ssh keys on PlanetLab:
https://www.planet-lab.org/db/web_accounts/ssh_public_key.php

Most linux systems will have ssh (OpenSSH) already installed for you, but if 
this is not the case, visit http://openssh.com/ for official releases for 
numerous linux-based platforms.

If you are using Windows based machines, several options exist. There are 
commercial ssh clients like SecureCRT:
http://www.vandyke.com/products/securecrt/
or freeware clients like putty:
http://www.chiark.greenend.org.uk/~sgtatham/putty/

Another option worth mentioning is cygwin. For windows, its a complete linux 
like environment. For more information, see:
http://cygwin.com/
If you install it, make sure to add OpenSSH to the list of packages to 
install, as I last checked, it was not enabled by default. Once installed, 
this will give you a command prompt running the common bash shell, and you 
can use ssh as if you were on a linux box.

As for Macintoshes, I'll have to let someone else fill in on which tools work 
well. :)

The other reason for this email was to introduce ssh-agent and similar 
programs. Since PlanetLab strongly suggests that you use a passphrase on your 
private ssh key, it can be very cumbersome to have to type in the passphrase 
everytime you login to a node. This is especially true if you have scripts to 
handle logging into many machines. Without this passphrase, if your key is 
compromised, it can be used by anyone to access your slice, which puts you at 
risk. 

ssh-agent is a program available from the OpenSSH distribution that allows you 
to add your private keys to a running agent program on your computer and only 
have to type in the passphrase once, where the keys are then stored in 
memory. Then, all ssh operations (including scp - secure file copy), 
transparently contact the agent and use the key there, so you don't have to 
type in the passphrase more than once.

For information on how to setup ssh-agent:
http://kimmo.suominen.com/ssh/#ssh-agent
http://www.caip.rutgers.edu/~vincentm/LINKS/sshagent.html

For windows, there is a similar program available from the same authors who 
wrote putty, called Pageant. This works in the same way, where you add your 
keys to the Pageant application after its running, and putty contacts Pageant 
for the authorization while logging in. See the putty website above for more 
specific documentation.

Aaron

[Planetlab-users] kaist nodes will be off-line on Sat, 1/10, KST.

[Sue M. <sb...@cs...>]

We're moving the boxes to another room.
The KAIST nodes (csplanetlab[1-4].kaist.ac.kr) will be off-line on Sat,
1/10, Korea Standard Time (UTC+9).
-Sue

Re: [Planetlab-users] rc.vinit

[Scott K. <sc...@CS...>]

Hi Neil,

The contents of /etc/rc.vinit were a temporary measure
to get the keys installed.  In the next couple of days,
we will have an alternate method for doing this.

Your impressions are correct.  It should be called with
a "start" parameter on startup and a "stop" parameter
on shutdown (with the caveat that a call on shutdown is
best effort and not guaranteed).

Scott


On Thu, Jan 08, 2004 at 02:07:45PM -0800, Neil Spring wrote:
> rc.vinit on new slices has the following contents:
> 
> [uw_nspring@planetlab3 log]$ cat /etc/rc.vinit
> #!/bin/sh
> /etc/ssh/fetch_keys
> 
> Although I'd prefer to have my very own file for managing what should 
> be started on my slice, I recognize the attractiveness of reusing the 
> rc.vinit mechanism for slice management.  I have two questions, though.
> 
> First, it was my impression that rc.vinit would be called with "start" 
> as a parameter on startup, and "stop" as a parameter on a graceful 
> shutdown.  I am starting to doubt that, as this rc.vinit would try to 
> populate authorized_keys on startup and shutdown.  Should I continue to 
> expect "start" to be the first parameter?  Or was I mistaken?
> 
> Second, how likely is it that planetlab will want to modify rc.vinit?  
> I think it would be better to make /etc/rc.vinit instead be:
> 
> #!/bin/sh
> # do not modify this file, as planetlab may change it.
> /etc/ssh/fetch_keys
> # other initialization code may go here
> test -e /etc/rc.vinit.local && /bin/sh /etc/rc.vinit.local $1
> 
> and instruct users like me to write rc.vinit.local.
> 
> -neil

[Planetlab-users] rc.vinit

[Neil S. <ns...@cs...>]

rc.vinit on new slices has the following contents:

[uw_nspring@planetlab3 log]$ cat /etc/rc.vinit
#!/bin/sh
/etc/ssh/fetch_keys

Although I'd prefer to have my very own file for managing what should 
be started on my slice, I recognize the attractiveness of reusing the 
rc.vinit mechanism for slice management.  I have two questions, though.

First, it was my impression that rc.vinit would be called with "start" 
as a parameter on startup, and "stop" as a parameter on a graceful 
shutdown.  I am starting to doubt that, as this rc.vinit would try to 
populate authorized_keys on startup and shutdown.  Should I continue to 
expect "start" to be the first parameter?  Or was I mistaken?

Second, how likely is it that planetlab will want to modify rc.vinit?  
I think it would be better to make /etc/rc.vinit instead be:

#!/bin/sh
# do not modify this file, as planetlab may change it.
/etc/ssh/fetch_keys
# other initialization code may go here
test -e /etc/rc.vinit.local && /bin/sh /etc/rc.vinit.local $1

and instruct users like me to write rc.vinit.local.

-neil

RE: [Planetlab-support] Re: [Planetlab-users] less, man, gzip, and rpmbuild

[Paul B. <pau...@pl...>]

Neil

You can download the linux-headers RPM from
http://boot.planet-lab.org/install-rpms/planetlab/linux-headers-2.4.22-r
2_planetlab.i386.rpm

Regards

Paul Brett
PlanetLab Support
Email: pau...@pl...
Tel No: +1 503 712 4520



|    -----Original Message-----
|    From: pla...@li... 
|    [mailto:pla...@li...] On 
|    Behalf Of Neil Spring
|    Sent: Tuesday, January 06, 2004 9:13 PM
|    To: <pla...@li...> 
|    <pla...@li...>
|    Cc: <pla...@li...>
|    Subject: Re: [Planetlab-support] Re: [Planetlab-users] 
|    less, man, gzip, and rpmbuild
|    
|    
|    Aaron, thanks, that's great, and I'm a lot closer.
|    
|    My next problem is that I can't build code that includes kernel 
|    headers.  This includes code that includes <limits.h>, and 
|    being able 
|    to include limits.h is a basic assumption of tests used by 
|    autoconf, so 
|    ./configure fails.
|    
|    I can't install the kernel headers because a dependency chain 
|    apparently wants to see a kernel in my vserver.
|    
|    My guess is that the dependency isn't real.  Is there a 
|    way to override 
|    the dependency tracking?  (perhaps like equivs for 
|    Debian.)  Or a way 
|    to install vserver-util without the kernel dependency?  Or 
|    glibc-kernheaders that doesn't require vserver-util?  Or a 
|    line to add 
|    to yum.conf to get the right stuff for planetlab?
|    
|    any help would be appreciated.
|    -neil
|    
|    [uw_nspring@planet1 uw_nspring]$ cat x.c
|    #include <limits.h>
|    
|    [uw_nspring@planet1 uw_nspring]$ gcc x.c
|    In file included from /usr/include/bits/posix1_lim.h:126,
|                      from /usr/include/limits.h:144,
|                      from 
|    /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include/limits.h:132,
|                      from 
|    /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include/syslimits.h:7,
|                      from 
|    /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include/limits.h:11,
|                      from x.c:1:
|    /usr/include/bits/local_lim.h:36:26: linux/limits.h: No 
|    such file or 
|    directory
|    
|    (on a controlled machine, I have no rh9 boxes)
|    skyo:~> rpm -qf /usr/include/linux/limits.h
|    glibc-kernheaders-2.4-7.16
|    
|    (back to planetlab)
|    [uw_nspring@planet1 uw_nspring]$ sudo yum  install 
|    glibc-kernheaders
|    Gathering header information file(s) from server(s)
|    Server: Red Hat Linux 9 - i386 - Base
|    Server: Red Hat Linux 9 - Updates
|    Finding updated packages
|    Downloading needed headers
|    Resolving dependencies
|    .package vserver-util needs linux >= 2.4.19-1_planetlab 
|    (not provided)
|    
|    (and in case I should have followed directions better)
|    [uw_nspring@planet1 uw_nspring]$ yum groupinstall 
|    "Development Tools"
|    Gathering header information file(s) from server(s)
|    Server: Red Hat Linux 9 - i386 - Base
|    Server: Red Hat Linux 9 - Updates
|    Finding updated packages
|    Downloading needed headers
|    Getting groups from servers
|    No groups provided or accessible on any server.
|    Exiting.
|    
|    
|    
|    On Jan 5, 2004, at 1:52 PM, Aaron Klingaman wrote:
|    
|    > Try this once logged in to your vserver, as root (use su):
|    >
|    > ------------------
|    > mkdir yum-rpms
|    > cd yum-rpms
|    > for i in stock-rh9/python-2.2.2-26.i386.rpm \
|    >           stock-rh9/libxml2-python-2.5.4-1.i386.rpm \
|    >           stock-rh9/libxml2-2.5.4-1.i386.rpm \
|    >           stock-rh9/expat-1.95.5-2.i386.rpm \
|    >           stock-rh9/rpm-python-4.2-0.69.i386.rpm \
|    >           stock-rh9/elfutils-0.76-3.i386.rpm \
|    >           stock-rh9/gmp-4.1.2-2.i386.rpm \
|    >           planetlab/yum-2.0.3-1_planetlab.noarch.rpm \
|    > ; do
|    >      curl -O http://boot.planet-lab.org/install-rpms/$i;
|    > done
|    > rpm -ivh *.rpm
|    > ----------------------------
|    >
|    > Now, as root, to install gzip for example, type:
|    >
|    > # yum install gzip
|    > or
|    > # yum groupinstall "Development Tools"
|    >
|    > Yum will handle the dependencies, and ask you if its ok 
|    before actually
|    > installing anything.
|    >
|    > :)
|    >
|    > Aaron
|    >
|    > On Monday 05 January 2004 04:32 pm, Paul Brett wrote:
|    >> Aaron
|    >>
|    >> Given that we have all the RPMS installed on the boot 
|    server, it 
|    >> there a
|    >> simple way for a user to get yum up and running inside 
|    their vserver?
|    >>
|    >> Regards
|    >>
|    >> Paul Brett
|    >> PlanetLab Support
|    >> Email: pau...@pl...
|    >> Tel No: +1 503 712 4520
|    >>
|    >> |    -----Original Message-----
|    >> |    From: pla...@li...
|    >> |    [mailto:pla...@li...] On
|    >> |    Behalf Of Aaron Klingaman
|    >> |    Sent: Monday, January 05, 2004 1:08 PM
|    >> |    To: Neil Spring; pla...@li...
|    >> |    Cc: pla...@li...
|    >> |    Subject: [Planetlab-support] Re: [Planetlab-users] less,
|    >> |    man, gzip, and rpmbuild
|    >> |
|    >> |
|    >> |    I've added gzip, and as a dependency, less is being
|    >> |    installed as well. This
|    >> |    change won't effect any already created slices nor any
|    >> |    nodes that have been
|    >> |    already installed (although this will change, we do have
|    >> |    the capability to
|    >> |    dynamically update the reference image on all the 
|    machines).
|    >> |
|    >> |    Aaron
|    >> |
|    >> |    > On Monday 05 January 2004 03:45 pm, Neil Spring wrote:
|    >> |    > > what is the "best" way to install these necessities on
|    >> |
|    >> |    a planetlab
|    >> |
|    >> |    > > slice?
|    >> |    > >
|    >> |    > > thanks,
|    >> |    > > -neil
|    >> |    > >
|    >> |    > > I'm used to Debian where:
|    >> |    > > [uw_nspring@planetlab02 uw_nspring]$ rpm -i
|    >> |
|    >> |    ftp://rpmfind.net/linux/redhat/9/en/os/i386/RedHat/RPMS/rpm
|    >> |    -build-4.2
|    >> |
|    >> |    > > -0.69.i386.rpm
|    >> |    > > warning: /var/tmp/rpm-xfer.PQp5Zf: V3 DSA signature:
|    >> |
|    >> |    NOKEY, key ID
|    >> |
|    >> |    > > db42a60e
|    >> |    > > error: Failed dependencies:
|    >> |    > >          file is needed by rpm-build-4.2-0.69
|    >> |    > >          patch >= 2.5 is needed by rpm-build-4.2-0.69
|    >> |    > >
|    >> |    > > doesn't happen.
|    >> |    > >
|    >> |    > >
|    
|    
|    
|    -------------------------------------------------------
|    This SF.net email is sponsored by: IBM Linux Tutorials.
|    Become an expert in LINUX or just sharpen your skills.  
|    Sign up for IBM's
|    Free Linux Tutorials.  Learn everything from the bash 
|    shell to sys admin.
|    Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
|    _______________________________________________
|    Planetlab-support mailing list
|    Pla...@li...
|    https://lists.sourceforge.net/lists/listinfo/planetlab-support
|    

[Planetlab-users] PlanetLab Status

[Scott K. <sc...@CS...>]

PlanetLab is currently experiencing trouble on a couple of fronts.
The implementation team is working diligently to get things running
smoothly as soon as possible.  This message is to provide everyone
status and, as a consequence, reduce the flow the tide of duplicate
messages to planetlab-support.

Please feel free to forward this information within your organization
as not everyone is subscribed to planetlab-users.  This is also a
request for everyone to subscribe to planetlab-users and planetlab-announce.

www.planet-lab.org
------------------
  * This week, our primary web server failed.  The problem was
    exacerbated by the winter storm in Hillsboro, Oregon, preventing
    the west coast implementation team from getting to the machine.
  * In the past day, we have remotely brought up an alternate server.
    Most (but not all) of the web content has moved; in addition, we
    are still in the process of moving the mail server.  Until this
    happens, e-mail notifications (e.g., when you request a password
    reset) will not work.

Kernel Bug
----------
  * Version 2.0 of the PlanetLab software appears to trigger
    a kernel bug related to semaphores leading to hung nodes.
    Prior to Version 2.0, we were seeing this behavior occasionally;
    it appears that we are now tickling this bug much more often.
  * This occurs on a relatively large set of nodes (approximately 30%).
  * We are currently testing more recent patches to the kernel
    and to the vserver subsystem.

Key Distribution
----------------
  * Additionally, we are improving the key distribution so that
    keys that are updated on the web are properly propagated to
    nodes that are already assigned to slices.  Currently, if you
    update your key, it will only be propagated to new slices
    and to nodes added to existing slices.
  * We expect to deploy a fix in 1-2 days.

Scott Karlin

Re: [Planetlab-support] Re: [Planetlab-users] less, man, gzip, and rpmbuild

[Aaron K. <al...@CS...>]

Yeah, check out your yum.conf. You'll notice by default it points to some Duke 
servers. Should have mentioned this earlier, but you'll probably want to 
point it at our servers (at least to get the correct kernel headers).

Here is an example yum.conf (actually from the real system):

------------------

[main]
cachedir=/var/cache/yum
debuglevel=2
logfile=/var/log/yum.log
pkgpolicy=newest

[RedHat9Base]
name=Red Hat Linux 9 Base
baseurl=http://boot.planet-lab.org/install-rpms/stock-rh9

[RedHat9Updates]
name=Red Hat Linux 9 Updates
baseurl=http://boot.planet-lab.org/install-rpms/updates-rh9

[PlanetLab]
name=PlanetLab RPMS
baseurl=http://boot.planet-lab.org/install-rpms/planetlab

[ThirdParty]
name=Third Party RPMS
baseurl=http://boot.planet-lab.org/install-rpms/3rdparty

---------------------

With this yum.conf file, you should be able to:

# yum install linux-headers

And only install that rpm, since, there is already some parts of the kernel in 
your slice (actually, rpm thinks the whole package is already installed).

Aaron

On Wednesday 07 January 2004 12:12 am, Neil Spring wrote:
> Aaron, thanks, that's great, and I'm a lot closer.
>
> My next problem is that I can't build code that includes kernel
> headers.  This includes code that includes <limits.h>, and being able
> to include limits.h is a basic assumption of tests used by autoconf, so
> ./configure fails.
>
> I can't install the kernel headers because a dependency chain
> apparently wants to see a kernel in my vserver.
>
> My guess is that the dependency isn't real.  Is there a way to override
> the dependency tracking?  (perhaps like equivs for Debian.)  Or a way
> to install vserver-util without the kernel dependency?  Or
> glibc-kernheaders that doesn't require vserver-util?  Or a line to add
> to yum.conf to get the right stuff for planetlab?
>
> any help would be appreciated.
> -neil
>
> [uw_nspring@planet1 uw_nspring]$ cat x.c
> #include <limits.h>
>
> [uw_nspring@planet1 uw_nspring]$ gcc x.c
> In file included from /usr/include/bits/posix1_lim.h:126,
>                   from /usr/include/limits.h:144,
>                   from
> /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include/limits.h:132,
>                   from
> /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include/syslimits.h:7,
>                   from
> /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include/limits.h:11,
>                   from x.c:1:
> /usr/include/bits/local_lim.h:36:26: linux/limits.h: No such file or
> directory
>
> (on a controlled machine, I have no rh9 boxes)
> skyo:~> rpm -qf /usr/include/linux/limits.h
> glibc-kernheaders-2.4-7.16
>
> (back to planetlab)
> [uw_nspring@planet1 uw_nspring]$ sudo yum  install glibc-kernheaders
> Gathering header information file(s) from server(s)
> Server: Red Hat Linux 9 - i386 - Base
> Server: Red Hat Linux 9 - Updates
> Finding updated packages
> Downloading needed headers
> Resolving dependencies
> .package vserver-util needs linux >= 2.4.19-1_planetlab (not provided)
>
> (and in case I should have followed directions better)
> [uw_nspring@planet1 uw_nspring]$ yum groupinstall "Development Tools"
> Gathering header information file(s) from server(s)
> Server: Red Hat Linux 9 - i386 - Base
> Server: Red Hat Linux 9 - Updates
> Finding updated packages
> Downloading needed headers
> Getting groups from servers
> No groups provided or accessible on any server.
> Exiting.
>
> On Jan 5, 2004, at 1:52 PM, Aaron Klingaman wrote:
> > Try this once logged in to your vserver, as root (use su):
> >
> > ------------------
> > mkdir yum-rpms
> > cd yum-rpms
> > for i in stock-rh9/python-2.2.2-26.i386.rpm \
> >           stock-rh9/libxml2-python-2.5.4-1.i386.rpm \
> >           stock-rh9/libxml2-2.5.4-1.i386.rpm \
> >           stock-rh9/expat-1.95.5-2.i386.rpm \
> >           stock-rh9/rpm-python-4.2-0.69.i386.rpm \
> >           stock-rh9/elfutils-0.76-3.i386.rpm \
> >           stock-rh9/gmp-4.1.2-2.i386.rpm \
> >           planetlab/yum-2.0.3-1_planetlab.noarch.rpm \
> > ; do
> >      curl -O http://boot.planet-lab.org/install-rpms/$i;
> > done
> > rpm -ivh *.rpm
> > ----------------------------
> >
> > Now, as root, to install gzip for example, type:
> >
> > # yum install gzip
> > or
> > # yum groupinstall "Development Tools"
> >
> > Yum will handle the dependencies, and ask you if its ok before actually
> > installing anything.
> >
> > :)
> >
> > Aaron
> >
> > On Monday 05 January 2004 04:32 pm, Paul Brett wrote:
> >> Aaron
> >>
> >> Given that we have all the RPMS installed on the boot server, it
> >> there a
> >> simple way for a user to get yum up and running inside their vserver?
> >>
> >> Regards
> >>
> >> Paul Brett
> >> PlanetLab Support
> >> Email: pau...@pl...
> >> Tel No: +1 503 712 4520
> >>
> >> |    -----Original Message-----
> >> |    From: pla...@li...
> >> |    [mailto:pla...@li...] On
> >> |    Behalf Of Aaron Klingaman
> >> |    Sent: Monday, January 05, 2004 1:08 PM
> >> |    To: Neil Spring; pla...@li...
> >> |    Cc: pla...@li...
> >> |    Subject: [Planetlab-support] Re: [Planetlab-users] less,
> >> |    man, gzip, and rpmbuild
> >> |
> >> |
> >> |    I've added gzip, and as a dependency, less is being
> >> |    installed as well. This
> >> |    change won't effect any already created slices nor any
> >> |    nodes that have been
> >> |    already installed (although this will change, we do have
> >> |    the capability to
> >> |    dynamically update the reference image on all the machines).
> >> |
> >> |    Aaron
> >> |
> >> |    > On Monday 05 January 2004 03:45 pm, Neil Spring wrote:
> >> |    > > what is the "best" way to install these necessities on
> >> |
> >> |    a planetlab
> >> |
> >> |    > > slice?
> >> |    > >
> >> |    > > thanks,
> >> |    > > -neil
> >> |    > >
> >> |    > > I'm used to Debian where:
> >> |    > > [uw_nspring@planetlab02 uw_nspring]$ rpm -i
> >> |
> >> |    ftp://rpmfind.net/linux/redhat/9/en/os/i386/RedHat/RPMS/rpm
> >> |    -build-4.2
> >> |
> >> |    > > -0.69.i386.rpm
> >> |    > > warning: /var/tmp/rpm-xfer.PQp5Zf: V3 DSA signature:
> >> |
> >> |    NOKEY, key ID
> >> |
> >> |    > > db42a60e
> >> |    > > error: Failed dependencies:
> >> |    > >          file is needed by rpm-build-4.2-0.69
> >> |    > >          patch >= 2.5 is needed by rpm-build-4.2-0.69
> >> |    > >
> >> |    > > doesn't happen.
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Planetlab-users mailing list
> Pla...@li...
> https://lists.sourceforge.net/lists/listinfo/planetlab-users

Re: [Planetlab-users] SSH Problems

[Larry P. <ll...@CS...>]

It looks like the problem is that you are still using an old
static slice (cornell6). Please read the "Version 2.0" link on
the main web page; we have moved to dynamic slices.

Larry

On Jan 7, 2004, at 8:56 AM, Scott Karlin wrote:

> Hi Rama,
>
> Currently, updates to your key are not being propagated to slivers
> that already existed.  We are working to fix this key distribution
> issue.
>
> If you remove the nodes from your slice, wait a bit (2 hours?),
> and then add the nodes back to your slice, your new key will be
> installed.
>
> Note that if you changed your key before about 23 December, you
> will need to upload a new one.
>
> If you continue to have trouble, please also report which nodes
> you are unable to ssh to.
>
> Scott
>
>
> On Wed, Jan 07, 2004 at 04:19:06AM -0500, Venu Ramasubramanian wrote:
>> Hi,
>>   I am not able to ssh into planetlab nodes ever since the recent 
>> global upgrade.  I changed my public key and uploaded the new key as 
>> adviced.  But my ssh always fails.  I've waited very long time for 
>> the public key to be propagated (upto 2 days).  I've also checked 
>> that the public key is correct by using it to ssh to some local 
>> nodes.  I've tried this process (key upload and check ssh) several 
>> times with different keys.  But my ssh always fails.  Here is a 
>> transcript from the ssh attempt.
>>
>> Enter passphrase for key '/usr/u/ramasv/.ssh/identity':
>> debug1: read PEM private key done: type RSA
>> debug3: sign_and_send_pubkey
>> debug2: we sent a publickey packet, wait for reply
>> debug1: authentications that can continue: 
>> publickey,keyboard-interactive
>> debug1: try privkey: /usr/u/ramasv/.ssh/id_rsa
>> debug3: no such identity: /usr/u/ramasv/.ssh/id_rsa
>> debug1: try privkey: /usr/u/ramasv/.ssh/id_dsa
>> debug3: no such identity: /usr/u/ramasv/.ssh/id_dsa
>> debug2: we did not send a packet, disable method
>> debug3: authmethod_lookup keyboard-interactive
>> debug3: remaining preferred: password
>> debug3: authmethod_is_enabled keyboard-interactive
>> debug1: next auth method to try is keyboard-interactive
>> debug2: userauth_kbdint
>> debug2: we sent a keyboard-interactive packet, wait for reply
>> debug1: authentications that can continue: 
>> publickey,keyboard-interactive
>> debug3: userauth_kbdint: disable: no info_req_seen
>> debug2: we did not send a packet, disable method
>> debug1: no more auth methods to try
>> Permission denied (publickey,keyboard-interactive).
>>
>>   I would appreciate any help regarding this problem.  My sliceid is 
>> cornell6.  I wonder if this problem is because of upgrade to version 
>> 2.
>>
>> thank you,
>> rama
>>
>> Department of Computer Science,
>> Cornell University,
>> Ithaca NY 14850.
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for 
> IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys 
> admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Planetlab-users mailing list
> Pla...@li...
> https://lists.sourceforge.net/lists/listinfo/planetlab-users
>

Re: [Planetlab-users] SSH Problems

[Scott K. <sc...@CS...>]

Hi Rama,

Currently, updates to your key are not being propagated to slivers
that already existed.  We are working to fix this key distribution
issue.

If you remove the nodes from your slice, wait a bit (2 hours?),
and then add the nodes back to your slice, your new key will be
installed.

Note that if you changed your key before about 23 December, you
will need to upload a new one.

If you continue to have trouble, please also report which nodes
you are unable to ssh to.

Scott


On Wed, Jan 07, 2004 at 04:19:06AM -0500, Venu Ramasubramanian wrote:
> Hi,
>   I am not able to ssh into planetlab nodes ever since the recent global upgrade.  I changed my public key and uploaded the new key as adviced.  But my ssh always fails.  I've waited very long time for the public key to be propagated (upto 2 days).  I've also checked that the public key is correct by using it to ssh to some local nodes.  I've tried this process (key upload and check ssh) several times with different keys.  But my ssh always fails.  Here is a transcript from the ssh attempt.
> 
> Enter passphrase for key '/usr/u/ramasv/.ssh/identity': 
> debug1: read PEM private key done: type RSA
> debug3: sign_and_send_pubkey
> debug2: we sent a publickey packet, wait for reply
> debug1: authentications that can continue: publickey,keyboard-interactive
> debug1: try privkey: /usr/u/ramasv/.ssh/id_rsa
> debug3: no such identity: /usr/u/ramasv/.ssh/id_rsa
> debug1: try privkey: /usr/u/ramasv/.ssh/id_dsa
> debug3: no such identity: /usr/u/ramasv/.ssh/id_dsa
> debug2: we did not send a packet, disable method
> debug3: authmethod_lookup keyboard-interactive
> debug3: remaining preferred: password
> debug3: authmethod_is_enabled keyboard-interactive
> debug1: next auth method to try is keyboard-interactive
> debug2: userauth_kbdint
> debug2: we sent a keyboard-interactive packet, wait for reply
> debug1: authentications that can continue: publickey,keyboard-interactive
> debug3: userauth_kbdint: disable: no info_req_seen
> debug2: we did not send a packet, disable method
> debug1: no more auth methods to try
> Permission denied (publickey,keyboard-interactive).
>  
>   I would appreciate any help regarding this problem.  My sliceid is cornell6.  I wonder if this problem is because of upgrade to version 2.
> 
> thank you,
> rama
> 
> Department of Computer Science,
> Cornell University,
> Ithaca NY 14850.  

[Planetlab-users] SSH Problems

[Venu R. <ra...@cs...>]

Hi,
  I am not able to ssh into planetlab nodes ever since the recent global =
upgrade.  I changed my public key and uploaded the new key as adviced.  =
But my ssh always fails.  I've waited very long time for the public key =
to be propagated (upto 2 days).  I've also checked that the public key =
is correct by using it to ssh to some local nodes.  I've tried this =
process (key upload and check ssh) several times with different keys.  =
But my ssh always fails.  Here is a transcript from the ssh attempt.

Enter passphrase for key '/usr/u/ramasv/.ssh/identity':=20
debug1: read PEM private key done: type RSA
debug3: sign_and_send_pubkey
debug2: we sent a publickey packet, wait for reply
debug1: authentications that can continue: =
publickey,keyboard-interactive
debug1: try privkey: /usr/u/ramasv/.ssh/id_rsa
debug3: no such identity: /usr/u/ramasv/.ssh/id_rsa
debug1: try privkey: /usr/u/ramasv/.ssh/id_dsa
debug3: no such identity: /usr/u/ramasv/.ssh/id_dsa
debug2: we did not send a packet, disable method
debug3: authmethod_lookup keyboard-interactive
debug3: remaining preferred: password
debug3: authmethod_is_enabled keyboard-interactive
debug1: next auth method to try is keyboard-interactive
debug2: userauth_kbdint
debug2: we sent a keyboard-interactive packet, wait for reply
debug1: authentications that can continue: =
publickey,keyboard-interactive
debug3: userauth_kbdint: disable: no info_req_seen
debug2: we did not send a packet, disable method
debug1: no more auth methods to try
Permission denied (publickey,keyboard-interactive).
=20
  I would appreciate any help regarding this problem.  My sliceid is =
cornell6.  I wonder if this problem is because of upgrade to version 2.

thank you,
rama

Department of Computer Science,
Cornell University,
Ithaca NY 14850. =20

Re: [Planetlab-support] Re: [Planetlab-users] less, man, gzip, and rpmbuild

[Neil S. <ns...@cs...>]

Aaron, thanks, that's great, and I'm a lot closer.

My next problem is that I can't build code that includes kernel 
headers.  This includes code that includes <limits.h>, and being able 
to include limits.h is a basic assumption of tests used by autoconf, so 
./configure fails.

I can't install the kernel headers because a dependency chain 
apparently wants to see a kernel in my vserver.

My guess is that the dependency isn't real.  Is there a way to override 
the dependency tracking?  (perhaps like equivs for Debian.)  Or a way 
to install vserver-util without the kernel dependency?  Or 
glibc-kernheaders that doesn't require vserver-util?  Or a line to add 
to yum.conf to get the right stuff for planetlab?

any help would be appreciated.
-neil

[uw_nspring@planet1 uw_nspring]$ cat x.c
#include <limits.h>

[uw_nspring@planet1 uw_nspring]$ gcc x.c
In file included from /usr/include/bits/posix1_lim.h:126,
                  from /usr/include/limits.h:144,
                  from 
/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include/limits.h:132,
                  from 
/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include/syslimits.h:7,
                  from 
/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/include/limits.h:11,
                  from x.c:1:
/usr/include/bits/local_lim.h:36:26: linux/limits.h: No such file or 
directory

(on a controlled machine, I have no rh9 boxes)
skyo:~> rpm -qf /usr/include/linux/limits.h
glibc-kernheaders-2.4-7.16

(back to planetlab)
[uw_nspring@planet1 uw_nspring]$ sudo yum  install glibc-kernheaders
Gathering header information file(s) from server(s)
Server: Red Hat Linux 9 - i386 - Base
Server: Red Hat Linux 9 - Updates
Finding updated packages
Downloading needed headers
Resolving dependencies
.package vserver-util needs linux >= 2.4.19-1_planetlab (not provided)

(and in case I should have followed directions better)
[uw_nspring@planet1 uw_nspring]$ yum groupinstall "Development Tools"
Gathering header information file(s) from server(s)
Server: Red Hat Linux 9 - i386 - Base
Server: Red Hat Linux 9 - Updates
Finding updated packages
Downloading needed headers
Getting groups from servers
No groups provided or accessible on any server.
Exiting.



On Jan 5, 2004, at 1:52 PM, Aaron Klingaman wrote:

> Try this once logged in to your vserver, as root (use su):
>
> ------------------
> mkdir yum-rpms
> cd yum-rpms
> for i in stock-rh9/python-2.2.2-26.i386.rpm \
>           stock-rh9/libxml2-python-2.5.4-1.i386.rpm \
>           stock-rh9/libxml2-2.5.4-1.i386.rpm \
>           stock-rh9/expat-1.95.5-2.i386.rpm \
>           stock-rh9/rpm-python-4.2-0.69.i386.rpm \
>           stock-rh9/elfutils-0.76-3.i386.rpm \
>           stock-rh9/gmp-4.1.2-2.i386.rpm \
>           planetlab/yum-2.0.3-1_planetlab.noarch.rpm \
> ; do
>      curl -O http://boot.planet-lab.org/install-rpms/$i;
> done
> rpm -ivh *.rpm
> ----------------------------
>
> Now, as root, to install gzip for example, type:
>
> # yum install gzip
> or
> # yum groupinstall "Development Tools"
>
> Yum will handle the dependencies, and ask you if its ok before actually
> installing anything.
>
> :)
>
> Aaron
>
> On Monday 05 January 2004 04:32 pm, Paul Brett wrote:
>> Aaron
>>
>> Given that we have all the RPMS installed on the boot server, it 
>> there a
>> simple way for a user to get yum up and running inside their vserver?
>>
>> Regards
>>
>> Paul Brett
>> PlanetLab Support
>> Email: pau...@pl...
>> Tel No: +1 503 712 4520
>>
>> |    -----Original Message-----
>> |    From: pla...@li...
>> |    [mailto:pla...@li...] On
>> |    Behalf Of Aaron Klingaman
>> |    Sent: Monday, January 05, 2004 1:08 PM
>> |    To: Neil Spring; pla...@li...
>> |    Cc: pla...@li...
>> |    Subject: [Planetlab-support] Re: [Planetlab-users] less,
>> |    man, gzip, and rpmbuild
>> |
>> |
>> |    I've added gzip, and as a dependency, less is being
>> |    installed as well. This
>> |    change won't effect any already created slices nor any
>> |    nodes that have been
>> |    already installed (although this will change, we do have
>> |    the capability to
>> |    dynamically update the reference image on all the machines).
>> |
>> |    Aaron
>> |
>> |    > On Monday 05 January 2004 03:45 pm, Neil Spring wrote:
>> |    > > what is the "best" way to install these necessities on
>> |
>> |    a planetlab
>> |
>> |    > > slice?
>> |    > >
>> |    > > thanks,
>> |    > > -neil
>> |    > >
>> |    > > I'm used to Debian where:
>> |    > > [uw_nspring@planetlab02 uw_nspring]$ rpm -i
>> |
>> |    ftp://rpmfind.net/linux/redhat/9/en/os/i386/RedHat/RPMS/rpm
>> |    -build-4.2
>> |
>> |    > > -0.69.i386.rpm
>> |    > > warning: /var/tmp/rpm-xfer.PQp5Zf: V3 DSA signature:
>> |
>> |    NOKEY, key ID
>> |
>> |    > > db42a60e
>> |    > > error: Failed dependencies:
>> |    > >          file is needed by rpm-build-4.2-0.69
>> |    > >          patch >= 2.5 is needed by rpm-build-4.2-0.69
>> |    > >
>> |    > > doesn't happen.
>> |    > >
>> |    > >

[Planetlab-users] Status of www.planet-lab.org

[Scott K. <sc...@CS...>]

As you may have noticed, www.planet-lab.org is having hardware
problems.  Due to the snowstorm in Hillsboro, Oregon, it is
difficult to physically get to the machine.

We are in the process of bringing up a replacement server.

Scott

Re: [Planetlab-support] Re: [Planetlab-users] less, man, gzip, and rpmbuild

[Aaron K. <al...@CS...>]

Try this once logged in to your vserver, as root (use su):

------------------
mkdir yum-rpms
cd yum-rpms
for i in stock-rh9/python-2.2.2-26.i386.rpm \
          stock-rh9/libxml2-python-2.5.4-1.i386.rpm \
          stock-rh9/libxml2-2.5.4-1.i386.rpm \
          stock-rh9/expat-1.95.5-2.i386.rpm \
          stock-rh9/rpm-python-4.2-0.69.i386.rpm \
          stock-rh9/elfutils-0.76-3.i386.rpm \
          stock-rh9/gmp-4.1.2-2.i386.rpm \
          planetlab/yum-2.0.3-1_planetlab.noarch.rpm \
; do
     curl -O http://boot.planet-lab.org/install-rpms/$i;
done
rpm -ivh *.rpm
----------------------------

Now, as root, to install gzip for example, type:

# yum install gzip
or
# yum groupinstall "Development Tools"

Yum will handle the dependencies, and ask you if its ok before actually 
installing anything.

:)

Aaron

On Monday 05 January 2004 04:32 pm, Paul Brett wrote:
> Aaron
>
> Given that we have all the RPMS installed on the boot server, it there a
> simple way for a user to get yum up and running inside their vserver?
>
> Regards
>
> Paul Brett
> PlanetLab Support
> Email: pau...@pl...
> Tel No: +1 503 712 4520
>
> |    -----Original Message-----
> |    From: pla...@li...
> |    [mailto:pla...@li...] On
> |    Behalf Of Aaron Klingaman
> |    Sent: Monday, January 05, 2004 1:08 PM
> |    To: Neil Spring; pla...@li...
> |    Cc: pla...@li...
> |    Subject: [Planetlab-support] Re: [Planetlab-users] less,
> |    man, gzip, and rpmbuild
> |
> |
> |    I've added gzip, and as a dependency, less is being
> |    installed as well. This
> |    change won't effect any already created slices nor any
> |    nodes that have been
> |    already installed (although this will change, we do have
> |    the capability to
> |    dynamically update the reference image on all the machines).
> |
> |    Aaron
> |
> |    > On Monday 05 January 2004 03:45 pm, Neil Spring wrote:
> |    > > what is the "best" way to install these necessities on
> |
> |    a planetlab
> |
> |    > > slice?
> |    > >
> |    > > thanks,
> |    > > -neil
> |    > >
> |    > > I'm used to Debian where:
> |    > > [uw_nspring@planetlab02 uw_nspring]$ rpm -i
> |
> |    ftp://rpmfind.net/linux/redhat/9/en/os/i386/RedHat/RPMS/rpm
> |    -build-4.2
> |
> |    > > -0.69.i386.rpm
> |    > > warning: /var/tmp/rpm-xfer.PQp5Zf: V3 DSA signature:
> |
> |    NOKEY, key ID
> |
> |    > > db42a60e
> |    > > error: Failed dependencies:
> |    > >          file is needed by rpm-build-4.2-0.69
> |    > >          patch >= 2.5 is needed by rpm-build-4.2-0.69
> |    > >
> |    > > doesn't happen.
> |    > >
> |    > >
> |    > >
> |    > > -------------------------------------------------------
> |    > > This SF.net email is sponsored by: IBM Linux Tutorials.
> |    > > Become an expert in LINUX or just sharpen your skills.
> |
> |     Sign up for IBM's
> |
> |    > > Free Linux Tutorials.  Learn everything from the bash
> |
> |    shell to sys admin.
> |
> |    > > Click now!
> |
> |    http://ads.osdn.com/?ad_id=1278&alloc_id=|    3371&op=click
> |
> |    _______________________________________________
> |
> |    > > Planetlab-users mailing list
> |    > > Pla...@li...
> |    > > https://lists.sourceforge.net/lists/listinfo/planetlab-users
> |    >
> |    > -------------------------------------------------------
> |    > This SF.net email is sponsored by: IBM Linux Tutorials.
> |    > Become an expert in LINUX or just sharpen your skills.
> |
> |    Sign up for IBM's
> |
> |    > Free Linux Tutorials.  Learn everything from the bash
> |
> |    shell to sys admin.
> |
> |    > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> |    > _______________________________________________
> |    > Planetlab-users mailing list
> |    > Pla...@li...
> |    > https://lists.sourceforge.net/lists/listinfo/planetlab-users
> |
> |    -------------------------------------------------------
> |    This SF.net email is sponsored by: IBM Linux Tutorials.
> |    Become an expert in LINUX or just sharpen your skills.
> |    Sign up for IBM's
> |    Free Linux Tutorials.  Learn everything from the bash
> |    shell to sys admin.
> |    Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> |    _______________________________________________
> |    Planetlab-support mailing list
> |    Pla...@li...
> |    https://lists.sourceforge.net/lists/listinfo/planetlab-support

[Planetlab-users] Planetlab1.ece.ucdavis.edu reinstalled on Jan 7

[Chen-Nee C. <ch...@ec...>]

Planetlab1.ece.ucdavis.edu will be re-installed on Jan 7, 2004
as part of hardware swap (replacing Dell PC with HP Proliant server).

Sorry for any inconvenience it may cause.


Regards,
Chen-Nee

RE: [Planetlab-support] Re: [Planetlab-users] less, man, gzip, and rpmbuild

[Paul B. <pau...@pl...>]

Aaron

Given that we have all the RPMS installed on the boot server, it there a
simple way for a user to get yum up and running inside their vserver?

Regards

Paul Brett
PlanetLab Support
Email: pau...@pl...
Tel No: +1 503 712 4520



|    -----Original Message-----
|    From: pla...@li... 
|    [mailto:pla...@li...] On 
|    Behalf Of Aaron Klingaman
|    Sent: Monday, January 05, 2004 1:08 PM
|    To: Neil Spring; pla...@li...
|    Cc: pla...@li...
|    Subject: [Planetlab-support] Re: [Planetlab-users] less, 
|    man, gzip, and rpmbuild
|    
|    
|    I've added gzip, and as a dependency, less is being 
|    installed as well. This 
|    change won't effect any already created slices nor any 
|    nodes that have been 
|    already installed (although this will change, we do have 
|    the capability to 
|    dynamically update the reference image on all the machines).
|    
|    Aaron
|    
|    > On Monday 05 January 2004 03:45 pm, Neil Spring wrote:
|    > > what is the "best" way to install these necessities on 
|    a planetlab
|    > > slice?
|    > >
|    > > thanks,
|    > > -neil
|    > >
|    > > I'm used to Debian where:
|    > > [uw_nspring@planetlab02 uw_nspring]$ rpm -i
|    > > 
|    ftp://rpmfind.net/linux/redhat/9/en/os/i386/RedHat/RPMS/rpm
|    -build-4.2
|    > > -0.69.i386.rpm
|    > > warning: /var/tmp/rpm-xfer.PQp5Zf: V3 DSA signature: 
|    NOKEY, key ID
|    > > db42a60e
|    > > error: Failed dependencies:
|    > >          file is needed by rpm-build-4.2-0.69
|    > >          patch >= 2.5 is needed by rpm-build-4.2-0.69
|    > >
|    > > doesn't happen.
|    > >
|    > >
|    > >
|    > > -------------------------------------------------------
|    > > This SF.net email is sponsored by: IBM Linux Tutorials.
|    > > Become an expert in LINUX or just sharpen your skills. 
|     Sign up for IBM's
|    > > Free Linux Tutorials.  Learn everything from the bash 
|    shell to sys admin.
|    > > Click now! 
|    http://ads.osdn.com/?ad_id=1278&alloc_id=|    3371&op=click
|    > > 
|    _______________________________________________
|    > > Planetlab-users mailing list
|    > > Pla...@li...
|    > > https://lists.sourceforge.net/lists/listinfo/planetlab-users
|    >
|    > -------------------------------------------------------
|    > This SF.net email is sponsored by: IBM Linux Tutorials.
|    > Become an expert in LINUX or just sharpen your skills.  
|    Sign up for IBM's
|    > Free Linux Tutorials.  Learn everything from the bash 
|    shell to sys admin.
|    > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
|    > _______________________________________________
|    > Planetlab-users mailing list
|    > Pla...@li...
|    > https://lists.sourceforge.net/lists/listinfo/planetlab-users
|    
|    
|    
|    -------------------------------------------------------
|    This SF.net email is sponsored by: IBM Linux Tutorials.
|    Become an expert in LINUX or just sharpen your skills.  
|    Sign up for IBM's
|    Free Linux Tutorials.  Learn everything from the bash 
|    shell to sys admin.
|    Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
|    _______________________________________________
|    Planetlab-support mailing list
|    Pla...@li...
|    https://lists.sourceforge.net/lists/listinfo/planetlab-support
|    

Re: [Planetlab-users] less, man, gzip, and rpmbuild

[Aaron K. <al...@CS...>]

I've added gzip, and as a dependency, less is being installed as well. This 
change won't effect any already created slices nor any nodes that have been 
already installed (although this will change, we do have the capability to 
dynamically update the reference image on all the machines).

Aaron

> On Monday 05 January 2004 03:45 pm, Neil Spring wrote:
> > what is the "best" way to install these necessities on a planetlab
> > slice?
> >
> > thanks,
> > -neil
> >
> > I'm used to Debian where:
> > [uw_nspring@planetlab02 uw_nspring]$ rpm -i
> > ftp://rpmfind.net/linux/redhat/9/en/os/i386/RedHat/RPMS/rpm-build-4.2
> > -0.69.i386.rpm
> > warning: /var/tmp/rpm-xfer.PQp5Zf: V3 DSA signature: NOKEY, key ID
> > db42a60e
> > error: Failed dependencies:
> >          file is needed by rpm-build-4.2-0.69
> >          patch >= 2.5 is needed by rpm-build-4.2-0.69
> >
> > doesn't happen.
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: IBM Linux Tutorials.
> > Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> > Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> > _______________________________________________
> > Planetlab-users mailing list
> > Pla...@li...
> > https://lists.sourceforge.net/lists/listinfo/planetlab-users
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Planetlab-users mailing list
> Pla...@li...
> https://lists.sourceforge.net/lists/listinfo/planetlab-users

Re: [Planetlab-users] less, man, gzip, and rpmbuild

[Aaron K. <al...@CS...>]

Well, gzip really should be there, I'm a bit surprised we didn't catch it (the 
proposed rpm list was sent out for review by all).

If you have a mirror for the RPMs, then use either curl or wget (both in the 
image), to save it somewhere before installing it. Might want to check out 
YUM too (http://linux.duke.edu/projects/yum/). There should be some slice 
provisioning services coming along as well.

Aaron

On Monday 05 January 2004 03:45 pm, Neil Spring wrote:
> what is the "best" way to install these necessities on a planetlab
> slice?
>
> thanks,
> -neil
>
> I'm used to Debian where:
> [uw_nspring@planetlab02 uw_nspring]$ rpm -i
> ftp://rpmfind.net/linux/redhat/9/en/os/i386/RedHat/RPMS/rpm-build-4.2
> -0.69.i386.rpm
> warning: /var/tmp/rpm-xfer.PQp5Zf: V3 DSA signature: NOKEY, key ID
> db42a60e
> error: Failed dependencies:
>          file is needed by rpm-build-4.2-0.69
>          patch >= 2.5 is needed by rpm-build-4.2-0.69
>
> doesn't happen.
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Planetlab-users mailing list
> Pla...@li...
> https://lists.sourceforge.net/lists/listinfo/planetlab-users

[Planetlab-users] less, man, gzip, and rpmbuild

[Neil S. <ns...@cs...>]

what is the "best" way to install these necessities on a planetlab  
slice?

thanks,
-neil

I'm used to Debian where:
[uw_nspring@planetlab02 uw_nspring]$ rpm -i  
ftp://rpmfind.net/linux/redhat/9/en/os/i386/RedHat/RPMS/rpm-build-4.2 
-0.69.i386.rpm
warning: /var/tmp/rpm-xfer.PQp5Zf: V3 DSA signature: NOKEY, key ID  
db42a60e
error: Failed dependencies:
         file is needed by rpm-build-4.2-0.69
         patch >= 2.5 is needed by rpm-build-4.2-0.69

doesn't happen.

Re: [Planetlab-users] Host Keys

[Scott A. <at...@cs...>]

Hi Paul,

I have updated my ssh keys and I ran your update script. How long 
before my new public key is distributed and I can login to the 
machines?

Scott

On Dec 22, 2003, at 2:55 PM, Paul Brett wrote:

> You can download the current host key for all running PlanetLab nodes
> from https://www.planet-lab.org/db/nodes/known_hosts.php.  Please note
> that machines in a debug state will have different hosts keys from 
> those
> published in this list.
>
> The attached perl script will download this list, and merge it into 
> your
> known hosts file.
>
> If you have any queries, please do not hesitate to contact me.
>
> Paul Brett
> PlanetLab Support
> Email: pau...@pl...
> Tel No: +1 503 712 4520
>
>
>
> |    -----Original Message-----
> |    From: pla...@li...
> |    [mailto:pla...@li...] On
> |    Behalf Of Scott Karlin
> |    Sent: Monday, December 22, 2003 10:38 AM
> |    To: pla...@li...
> |    Subject: [Planetlab-users] Host Keys
> |
> |
> |    As a consequence of updating nodes to Version 2.0, the
> |    host keys on the PlanetLab nodes have changed.
> |
> |    Scott
> |
> |
> |    -------------------------------------------------------
> |    This SF.net email is sponsored by: IBM Linux Tutorials.
> |    Become an expert in LINUX or just sharpen your skills.
> |    Sign up for IBM's
> |    Free Linux Tutorials.  Learn everything from the bash
> |    shell to sys admin.
> |    Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> |    _______________________________________________
> |    Planetlab-users mailing list
> |    Pla...@li...
> |    https://lists.sourceforge.net/lists/listinfo/planetlab-users
> |
> <update_known_hosts>

[Planetlab-users] Mono, Java and Higher-level Communication Middleware

[<b.r...@gm...>]

Hello,

in a pervious thread I have read that it is possible to install any java
runtime in a vserver if you change to root by su. Is it also possible to
install a mono runtime in a vserver which allows you to execute managed code
in il and to program e.g. in C#? If so, what about higher-level network
communication functionalities? Is it possible to communicate between the
slivers of a slice via rmi or corba?

Thanks a lot for helping

Regards
Bjoern Roeber
Universitaet Duisburg-Essen 

RE: [Planetlab-users] Host Keys

[Sue M. <sb...@cs...>]

Paul,
I generated a new public key and uploaded it.  But I can't login, nor
all my students.  Am I the only one who complains about the problem?
I'm trying to login to planetlab1.lcs.mit.edu using kaist_1 slice.  I'll
try to call you up late tonite my time.
-Sue

> -----Original Message-----
> From: pla...@li...
[mailto:planetlab-users-
> ad...@li...] On Behalf Of Paul Brett
> Sent: Tuesday, December 23, 2003 4:55 AM
> To: pla...@li...
> Cc: 'Scott Karlin'
> Subject: RE: [Planetlab-users] Host Keys
> 
> You can download the current host key for all running PlanetLab nodes
> from https://www.planet-lab.org/db/nodes/known_hosts.php.  Please note
> that machines in a debug state will have different hosts keys from
those
> published in this list.
> 
> The attached perl script will download this list, and merge it into
your
> known hosts file.
> 
> If you have any queries, please do not hesitate to contact me.
> 
> Paul Brett
> PlanetLab Support
> Email: pau...@pl...
> Tel No: +1 503 712 4520
> 
> 
> 
> |    -----Original Message-----
> |    From: pla...@li...
> |    [mailto:pla...@li...] On
> |    Behalf Of Scott Karlin
> |    Sent: Monday, December 22, 2003 10:38 AM
> |    To: pla...@li...
> |    Subject: [Planetlab-users] Host Keys
> |
> |
> |    As a consequence of updating nodes to Version 2.0, the
> |    host keys on the PlanetLab nodes have changed.
> |
> |    Scott
> |
> |
> |    -------------------------------------------------------
> |    This SF.net email is sponsored by: IBM Linux Tutorials.
> |    Become an expert in LINUX or just sharpen your skills.
> |    Sign up for IBM's
> |    Free Linux Tutorials.  Learn everything from the bash
> |    shell to sys admin.
> |    Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> |    _______________________________________________
> |    Planetlab-users mailing list
> |    Pla...@li...
> |    https://lists.sourceforge.net/lists/listinfo/planetlab-users
> |