Please review and advise... .bashrc code.

[AboveNBeyond]

Hello all,
The following is in my bashrc and all seems to work except the "netinfo" which works fine as stand alone command.

#WELCOME
clear
echo -e ${LIGHTBLUE}`cat /etc/lsb-release` ;
echo -e "Kernel Information: " `uname -smr`;
echo -ne "Hello $USER today is "; date
echo -e "${WHITE}"; cal ; echo "";
echo -ne "${CYAN}";netinfo; echo "";
echo -ne "${LIGHTBLUE}Uptime for this computer is ";uptime | awk /'up/
{print $3,$4}'
echo ""; echo ""

Can anyone see whats wrong? If so please tell me.
Thanks.

[wje_lf]

What, in detail now, makes you think anything is wrong?

[AboveNBeyond]

Because I get this when bash starts...

March 2008
Su Mo Tu We Th Fr Sa
1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30 31

bash: netinfo: command not found

Uptime for this computer is 16:33:14 up 1 day, 1:47, 2 users, load average: 1.00, 0.49, 0.38
1 day,

And I would expect the normal output of "netinfo".

[vsemaska]

If netinfo works fine as a stand-alone command then it sounds like PATH isn't defined properly yet to locate the command in your .bashrc. I suggest you put in your .bashrc the full path to the command like this:

echo -ne "${CYAN}";/path/to/netinfo; echo "";

where '/path/to' is the directory where netinfo is located.

[drl]

Hi.

If netinfo does not seem to be available or installable, then perhaps this may help.

I saw a number of mentions of netinfo related to Mac OS X. Sure enough, on an older PowerPC (10.3.9), there are some references to netinfo. The article at NetInfo - Wikipedia, the free encyclopedia suggests it lasted through 10.4 ... cheers, drl

[scm]

Why the "" after the trailing echoes? If you're just after a newline

echo

is all you need. And why the trailing semicolons?