Casper.Dik at Sun.COM wrote:
> >Nicolas Williams wrote:
> >> On Sat, May 05, 2007 at 11:32:01AM +0200, Casper.Dik at Sun.COM wrote:
> >> > Then it occurs to me that setting them in /etc/profile, /etc/*rc*
> >> > is WRONG.
> >>
> >> Right: how does one write class action scripts to update these shell
> >> scripts?
> >
> >Erm, what about doing the same as we did for /etc/ksh.kshrc as
> >introduced by PSARC 2006/550+2006/587 and set the package database entry
> >to "e renameold" ?
>
> Hm, that will really make administrators happy.
Uhm... was that sarcastic (note: I don't have a good builtin sense for
sarcasm... it usuaully results in problems that I misunderstand people
and trouble follows... ;-( ) ?
IMO at least it's better than an "automated" thing which tries to patch
a script like /etc/profile. Guess why I do not prefer Solaris updates
and do reinstalls from scatch (the "cleanup" after the updates usually
takes more time than a clean reinstall from scratch) ?
> Note that /etc/ksh.kshrc is still an essentially new file and
> ksh93 a new part, so any settings for it are not what I would consider
> random change inflicted on existing users.
>
> But renameold and the other edits are a poor solution.
I slightly disagree. The general work-in-process state of the
ksh93-integration project and the size+complexity (three lines) of the
current /etc/ksh.kshrc script does IMO not justify the creation of a
more complex "update" mechanism which later generates more heaches in
this case. The file is maintained in sync with the ksh93 updates anyway.
> Perhaps we should migrate to something like:
>
> # Include default ksh.
> . /etc/ksh.kshrc.default
>
> and edit them a final time (so administrators can customize them
> to their hearts content and we have no longer a problem updating the
> defaults)
Umpf... technially we'll get something similar with /etc/env.d/ (it
works like /etc/profile.d/ except that supports more "methods" than just
profile shells (e.g. methods={ login, logout, interactive_shell_start,
interactive_shell_exit etc. } ) and has some "clever"
enummeration/tagging/filter scheme) later where you can "inject" scripts
(e.g. Solaris provides /etc/env.d/interactive/I010prompt.sh and a site
could override these settings in
/etc/env.d/interactive/I990prompt_mysite.sh (or I010prompt,pri=20.sh))
in the profile or interactive shell startup chain. Unfortunately
/etc/env.d/ is still in my ToDo queue... ;-(
----
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) roland.mainz at nrubsig.org
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 7950090
(;O/ \/ \O;)
