Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: Review Request: ltsp-server-config - LTSP5 server-side configurations and setup
scripts
https://bugzilla.redhat.com/show_bug.cgi?id=331731
------- Additional Comments From pertusus(a)free.fr 2007-10-17 04:44 EST -------
(In reply to comment #18)
comment 10:
if ltsp-initialize is moved to /usr/sbin/, someone is more likely to find it by
accident and run it to see what it does ("./ltsp-initialize -h" is not an
unreasonable use-case). I changed this command to require a "-y" flag,
otherwise
it spits out a warning & exit 1
Agreed, this is safer. Although in the unix philosophy you are not
meant to do mistakes, I agree that it is right.
(In reply to comment #21)
Is there any specific reason that configuration file is
/etc/sysconfig/ltsp5 as
opposed to merely ltsp? We don't usually have version specific configuration
file names and it would be problematic for documentation if we have to change
all the references when ltsp 6 rolls out.
Between ltsp releases there are lots of changes, so it is not obvious
that /etc/sysconfig/ltsp5 will be suitable for ltsp6. Currently
we support ltsp4 with ltsp-utils, and the design of ltsp5 and ltsp4
are very different. Also quite different were the design of ltsp3 and
ltsp4. And in general there are years between releases. Moreover we should
certainly maintain different ltsp releases in parallel, as long as they
are maintained upstream (currently it seems that ltsp4 and ltsp5
are maintained).
In fact I think that we could even try to ensure that the paths
are version specific such that it will be possible to install in
parallel ltsp5 and ltsp6. It is not obvious either, especially
for the client nfs root, but this should be considered.
--
Configure bugmail:
https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.