In article <jkq6tg$dil$
1...@dont-email.me>, YTC#1 <
b...@ytc1-spambin.co.uk> wrote:
>On 03/26/12 04:47 PM, Rich Teer wrote:
>> On Mon, 26 Mar 2012, YTC#1 wrote:
>>
>>> /etc/hostname.<nic> is a config file
>>>
>>> That was a nice easy thing to use in SunOS until S11
>>
>> I must admit (and it seems I'm not alone here), but as Solaris
>> moves further and further away from plain old text config files
>> (in the grand old UNIX tradition), us old timers appreciate it
>
>I don't class myself as old, yet :-)
>
>> less and less. What next, a registry a la Windoze?!
>
>That has been an ugly rumour that has circulated for a long time....
>
>>
>> Give me plain text files and vi over n (for suitably large values
>> of n) bespoke tools for editing opaque XML (or other) files!
>>
>
>+1
>
>And lets not have servers install with NWAM/DHCP by default as well.
Agreed -- ASCII files are nice for config files.
And I suppose, at least with emacs, there could be
various modes for editing the more complex ones.
Maybe even with some protection built-in for
catching "stupid" errors, like entering unlikely values,
things like that.
OK -- about Solaris seemingly moving away from ASCII
config files:
WHO is it who decides on such things?
Maybe some of the more knowledgeable in this group, say,
could work to become outside advisors to or members
of whatever groups decide this stuff.
Likely the MBA-types will insist on GUI-type interfaces,
a la Microsoft.
BUT, even so, maybe at very low cost they could make available
a parallel text-based interface.
Plus, for even those who prefer the GUI style, once the
config for something has been set up, maybe you could
talk the Oracle (or whatever) people into a facility
that would take that config-info and write it out
in an ASCII file (such that it can be read back in).
The sales point of course being that it makes it
simpler to config multiple machines. And if
the config can vary slightly from one machine to
another, it's certainly simple enough to make
minor edits for each one. Even via sed! (via
saved sed-files, one per different config)
Also, easier training of new unix sysadmins, since
each will ALREADY be proficient in these text-based
tools.
And, if you can get your company behind you, and
it's big enough to be important to Oracle or whoever,
they can threaten to to linix. Pretty sure they
won't think you're bluffing.
Far better to make the effort than to just
sit back and let the marketing types decide
what's going to be inflicted on you!
David
PS: No, I can't do it.
A: I'm just a sole operator.
B: From my question-posts here, you know only
too well how technically IGNORANT I am
on sysadmin stuff.