[Info-vax] Logging systartup_vms.com progress to operator.log VMS 7.3-2
Dave Froble
davef at tsoft-inc.com
Thu Oct 15 16:57:02 EDT 2020
On 10/15/2020 1:49 PM, Simon Clubley wrote:
> On 2020-10-15, Arne Vajhøj <arne at vajhoej.dk> wrote:
>> (no quote as this is not really a reply to a specific post)
>>
>> WTF are people doing in their SYSTARTUP_VMS.COM ??
>>
>> To me it needs 5-10 lines for VMS stuff and 5-20 lines
>> for application stuff.
>>
>> And it is mostly just lines like:
>>
>> $ @somedisk:[somedir]something_startup.com
>>
>
> What happens when something is uninstalled and someone has to remember
> to reverse the manual changes ?
>
> Or what if you would like a way to disable a service at startup without
> having to manually edit the startup files ?
Perhaps one might queue up a message telling a particular service what
to do?
>> I don't see a need for a database or anything else
>> advanced.
>>
>
> You need it when you start thinking in terms of package management.
>
> In addition to the above examples, what about dependency management
> where one package depends on another ?
If a function is dependent on something, should not it check to see if
the required service is available?
>> These lines are easy to find and easy to read/modify
>> using a plain editor.
>>
>> Why complicate something that can be simple.
>>
>
> Because it's not as simple as it looks.
Actually, in a decent design, yes it is just that simple.
> That's why every other normal operating system still around (including
> Windows) has a proper package manager built into it.
Perhaps because they need them?
--
David Froble Tel: 724-529-0450
Dave Froble Enterprises, Inc. E-Mail: davef at tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA 15486
More information about the Info-vax
mailing list