(John P. Rouillard writes:)
> In message <199402081614.AA10387@email@example.com>,
> "Vincent D. Skahan" writes:
> > I grabbed it and have a couple of comments and at least one question :-)
> > I'm running on an Apollo with Domain/OS.
> > Problems:
> > - apollos don't have the `arch` command so the wrapper fails.
> Ok. Install-shared will not be the default install mechanism. Actually
> depending on how hard the wrapper gets banged on, having a shell
> wrapper to do archetecture selection may not be "a good thing". The
> reason I use it is for testing. I can use the same alias files on a
> coule of hosts (sun4 and ultrix) and do my testing on both hosts.
you make the call...I don't see why you need to change direction
due to Dead/OS :-) but at least you should document that the arch
command is not necessarily in every o/s and that the workaround is
no big deal.
> > Questions:
> > - what the heck are newconfig, writeconfig, etc ?
> Oops, I thought that was in the README.CONFIG. The following commands
> have been added to majordomo:
[...nice docs omitted...]
> > I guess the real question is 'ok - you added all this cool new
> > functionality - now how to I configure majordomo to use it ?'
> Config files will be created as needed for any list that is without
> one. If you run a "lists" command against majordomo, it will
> automatically create config files for all of the lists, but a request
> for the config file should do the same albeit for that one list.
pretty cool. that works nicely and the comments in the newly created
config file look great (as long as when the new release comes out,
all the possible options are in there...)
----------- Vince Skahan ------ firstname.lastname@example.org -----------
Vendor "Apollo" can not be deleted (network license server/server)
[...output of 'stcode 1d01001e' on HP Domain/OS...]