So the safest way is $ su - $ /usr/local/bin/bash $ cd /...wherever you compiled ntop.../ $ make install $ exit
(and you're back to ksh, still as root) $ exit (and you're back to little 'ole you) no mussing with /etc/passwd, other stuff doesn't get broken 'cause you changed the shell, etc. You just fire off bash when it's the best choice. -----Burton -----Original Message----- From: David Birnbaum [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 4:45 PM To: Burton M. Strauss III Subject: Re: bash vs. ksh (was ... on Solaris SPARC ) root is /bin/ksh on our world. I see it doing various voodoo to look past /bin/sh and others. Guess it ran out of voodoo before it searched /usr/local/bin. David. ----- On Tue, 2 Dec 2003, Burton M. Strauss III wrote: > Right ... configure won't go looking for bash, it uses the #! value > (typically /bin/sh), which becomes whatever your admin set your userid to > be. > > But you should be able to start bash > > /usr/local/bin/bash > > and then fire away... with the normal ./configure and gmake lines > > -----Burton > > -----Original Message----- > From: David Birnbaum [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 02, 2003 4:02 PM > To: Burton M. Strauss III > Cc: Ntop-Dev > Subject: RE: NTOP on Solaris SPARC > > > On Tue, 2 Dec 2003, Burton M. Strauss III wrote: > > <snip /> > > > Really, with all the stuff you have to load from Sun Freeware just to get > > ntop to compile, well, what's a little bash among friends <grin/>. > > > > /usr/local/bin/bash ./configure > > /usr/local/bin/bash gmake > > We have bash: > > hite /root 35# which bash > /usr/local/bin/bash > > But configure didn't pick it up. > > David. > > > _______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
