[Coco] OS-9 environment variables?

[t.fadden at cox.net]

Don't most OS's keep the environment variables in a file?  like 
.profoile, .csh, .login .logout etc?  Seems that approch would be best. 
The printenv and setenv are temporary. To make it permenant, the file 
needs to be changed.  Solaris works this way, and I suspect so do all 
the rest of the unix's.  These would be kept on the /dd device, and read 
by the shell when it starts.  On multiuser systems, it would be read 
from the users home directory.  This would be a great addition to our 
OS9.

Unless you are talking about something else.

Tim Fadden


On Wed, Apr 15, 2009 at 11:30 AM , Roger Taylor wrote:

> At 11:08 AM 4/15/2009, you wrote:
>> Non-6809 OS-9 versions do have environment variable space.
>>
>> It would be trivial to write a getenv/setenv library... How soon 
>> would
>> you need it?
>
> That's a nice offer.  No major rush!
>
> Is the data guaranteed to be there after hitting Reset?  I know 
> nothing is truly guaranteed, but you get the idea.  Some untoucable 
> space, and I'm sure there's a lot there right now without having to 
> make the environment routines, but it sure would be nice to have them 
> persist across a Reset, and just have the routines in the first place 
> so programs can at least share a few pieces of information in style. 
> :)
>
>
>
>
>
>
>
>
>> Sent from my iPhone
>> Follow me on Twitter - http://twitter.com/allenhuffman
>>
>> On Apr 15, 2009, at 11:04 AM, Roger Taylor <operator at coco3.com> 
>> wrote:
>>
>>> At 10:37 PM 4/14/2009, you wrote:
>>>> On Apr 14, 2009, at 10:30 PM, Roger Taylor wrote:
>>>>
>>>>> Is there a way in OS-9 to store a few bytes or a string from one
>>>>> module and access that data from another module by nickname or 
>>>>> some
>>>>> other global handle?
>>>>
>>>> There is a DATA MODULE type, where the body of the module can be
>>>> linked to from multiple processes, then each gets a pointer and
>>>> access
>>>> to the body area and can read/write that data. That is the OS-9
>>>> mechanism for data sharing.
>>>>
>>>> You can fix the CRC and save the module out, load it on reboot, and
>>>> the variables would be back.
>>>>
>>>> I should write some code for that. (Semaphores, I am not sure of,
>>>> under OS-9/6809.)
>>>>
>>>> Boisy, you know?
>>>
>>>
>>>
>>>
>>> I think OS-9 should have had some SetEnv and GetEnv routines a long
>>> time ago.  One of the seed modules that are still there after you
>>> hit reset could just open up some static space, just enough to not
>>> hurt the os9boot size issue but to allow 4 to 8 variables to be set
>>> by nickname and retreived the same.  I guess this would involve
>>> adding 2 new system calls?
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Roger Taylor
>>>
>>> http://www.wordofthedayonline.com
>>>
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
> -- 
> Roger Taylor
>
> http://www.wordofthedayonline.com
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco