Re: Linux conceptual configuration problems

[Avi Alkalay]

On Sat, 06 Nov 2004 02:37:56 -0800, Kenneth Porter
<shiva(a)sewingwitch.com&gt; wrote:
>  --On Saturday, November 06, 2004 7:25 AM -0300 Avi Alkalay
>  <avibrazil(a)gmail.com&gt; wrote:
>  
>  > I see Linux today as many separated programs
>  > that were forced to work together, but not designed to do so. So the
>  > system as a whole is not integrated.
>  
>  Don't forget that Linux is not Fedora. There are many flavors of Linux at
>  many scales, from tiny embedded systems to massive clusters. Configuration
>  machinery for one deployment may be inappropriate for another. 
Of course.
But currently no massive cluster and no tiny deployment provides a way
to apps integrate themselves automatically through their
configurations. They allways have to ask users to manualy edit
configuration files.

Regards,
Avi

Linux conceptual configuration problems

[Jon Savage]

>  Of course.
>  But currently no massive cluster and no tiny deployment provides a way
>  to apps integrate themselves automatically through their
>  configurations. They allways have to ask users to manualy edit
>  configuration files. 
IMHO assuming that adaquate discovery/testing has been done
prior to
deployment *users* at foocorp should never need to edit config files
at all beyond desktop/shell preferences. There are GUIs available for
just about all of these. Pretty much the same sort of tweaks users can
make to their own profiles in Windows. Now if foocorp has been running
windows w/ users having admin rights by default the transition might
be more interesting since the concept of locking user accounts down
will be  err... new.
Check out stateless linux.
-- 
Bests,
Jon

Linux conceptual configuration problems

[Kyrre Ness Sjobak]

lør, 06.11.2004 kl. 18.40 skrev Jon Savage:
>  > Of course.
>  > But currently no massive cluster and no tiny deployment provides a way
>  > to apps integrate themselves automatically through their
>  > configurations. They allways have to ask users to manualy edit
>  > configuration files.
>  IMHO assuming that adaquate discovery/testing has been done prior to
>  deployment *users* at foocorp should never need to edit config files
>  at all beyond desktop/shell preferences. There are GUIs available for
>  just about all of these. Pretty much the same sort of tweaks users can
>  make to their own profiles in Windows. Now if foocorp has been running
>  windows w/ users having admin rights by default the transition might
>  be more interesting since the concept of locking user accounts down
>  will be  err... new.
>  Check out stateless linux.
>  -- 
>  Bests,
>  Jon 
If i am not completely wrong, you may use sudo to give users admin
rigths on their personal desktop.

If that is preferable, i think is up to each deployer...