Re: euos add/remove/setup
Good idea, but i'd suggest that we use a number assigned by the OS as a unique
identifier. If we used times, then there might be problems with the date (for
example, a year x problem would make the OS unable to recognize the difference
between a file installed on 3:00:00 on 1/1/x and 3:00:00 on 1/1/y. Hopefully,
EuOS would be immune to such problems, but I think that it would be best to
eliminate as many possible errors as possible. Another problem would be that a
program would take a while to install the files so the OS would have to keep
track of the time at which the instilation program was started. Finally, it is
possible (though unlikely) that the user would run two setup programs at the
same time. Though the times would have to be minutely different, it still might
cause an error if they were very close and the OS didn't store enough
information about the time.
>I am still new to the list: could you tell me what the euos project is?
>maybe a sort of 4dos replacement, an euphorized shell? or something
>much more integrated with a GUI, mouse... like GeoWorks?
>- I like the idea 
EuOS is a project to write a real operating system using the Euphoria language
and programming theory as much as possible. It won't be a shell, but a real
multi-tasking operating system. You can visit the EuOS web page at
http://euos.hypermart.net/
rltoews at pangea.ca wrote:
> good day,
> currently i use cleansweep but it has problems with other programs that
> want the same resources. i recently found a program called 1disk that
> monitors removable media and creates a database and issues mount
> messages etc. it has problems because it wants the same resources as
> cleansweep.
> i use cleansweep mostly to monitor installs so i can remove trial
> versions of programs. or re-install for an improved system.
>
> re: add / remove/ setup
> i recently thought of another way which can be implemented in the euos
> project.
> adding /removing programs need to know what files are related so they
> can all be removed without leaving pieces of programs around. my idea is
> based on
> the fact that programs are installed one at a time and therefore no
> install will use the same time block. just like no physical item can
> exist in two places at the same time.
> if a field is kept for installation date/time in a directory database
> and is never modifiable afterwards it could be used to find related
> files and select them to be deleted/moved/backed up/restored.
> the o.s. file creation date won't work because it is retained when the
> file is zipped and unzipped on another system.the unzipped file date
> isn't the date the file was unzipped or installed by setup programs on
> the new system.
> this time block stamp could be implemented in the euos or newer versions
> of euphoria. it could aid in keeping projects seperated though i have'nt
> given more thought of using a time block in that fashion.
>
> just an idea. any comments.
>
> rudy
--
Jeffrey Fielding
JJProg at cyberbury.net
http://members.tripod.com/~JJProg/
|
Not Categorized, Please Help
|
|
