Re: Re: Raspberry PI synchron
  By: KK4QBN to Digital Man on Sat Feb 17 2018 04:41 am

 >   Re: Re: Raspberry PI synchron
 >   By: Digital Man to KK4QBN on Fri Feb 16 2018 23:09:34
 >
 >  >> kk4qbn@kk4qbn:~$
 >
 >  >> it is not working.
 >
 >  >> here is the last few lines of /etc/profile
 >
 >  >> done
 >  >> unset i
 >  >> fi
 >  >> export SBBSCTRL=/sbbs/ctrl/
 >
 >  DM> And you rebooted while it was that way?
 >
 > Yes, of course :)
 >
 >  DM> "HELLO" was the name of the environment variable. "Hi!" was the
 >  DM> content. No where did I suggest you should have "got Hello".
 >                                             Note the following statement
 >
 >
 >  > DM>> $ echo $HELLO
 >  > DM>> $ env <- shows all environment variables, you'll see HELLO there
 >  > DM>> too
 >
 > ^^^ Ummm little stuff like that is what throws me for loops at times

Ah, you're right, typo on my part. When you echo an environment variable, you
shoul see the value (contents) of that environment variable, not the name.

 > > kk4qbn@kk4qbn:~$ unset HELLO
 >  >> kk4qbn@kk4qbn:~$ source hi.sh
 >  >> bash: export: `HELLO-Hi!': not a valid identifier
 >
 >  DM> You did something wrong. :-)
 >
 > but what? the hi.sh is EXACTLY what you typed and I followed step by step.

How about paste the md5 sum of hi.sh here?

It should look this this:

root@cvs:~# cat hi.sh
export HELLO=Hi!
echo $HELLO
root@cvs:~# md5sum hi.sh
f7201385bdb7c523dade158d270014cc  hi.sh
root@cvs:~# source hi.sh
Hi!

 >  DM> No. The reported error ("bash: export: `HELLO-Hi!': not a valid
 >  DM> identifier") suggests to me you have a typo.
 >
 > well something is scrwed.. I would'nt think attempting to export Sooo many
 > times in so many different ways I would get that typo EVERY sing time, and
 > with EVERYTHING else it works, but sbbs still reports that SBBSCTRL
 > environment not set.

Don't use sbbs to test your methods of setting environment variables. Use
"echo" or "env" instead. Once "echo" and "env" show the environment variable(s)
that you have set are indeed there, then run 'sbbs'.

And if the SBBSCTRL environment variable shows up in 'env' output (or its value
can be echoed via $SBBSCTRL) and sbbs still reports that error, then revisit
your methods of starting sbbs - if it's a shell script, revisit the contents of
that that shell script.

 >  DM> Here's a FAQ on it: https://unix.stackexchange.com/questions/117467/how
 >  DM> -to-permanently-set-env ironm ental-variables#117470
 >
 > Thankss again, I have read a few docs on it.. it should'nt be giving this
 > much complications.

It's *nix. It's quirky and unforgiving by nature.

                                            digital man

This Is Spinal Tap quote #23:
David St. Hubbins: I envy us.
Norco, CA WX: 74.3øF, 18.0% humidity, 7 mph NE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.03-Win32