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 - LTSP5 server-side configurations and setup scripts
https://bugzilla.redhat.com/show_bug.cgi?id=331731
------- Additional Comments From pertusus(a)free.fr 2007-11-02 05:23 EST -------
(In reply to comment #71)
Normally I would agree with you, but you have to think about the
target audience
here... it is essential that we make things Just Work by default. If this is
the case then a service is insufficient, RPM trigger would be the only option
until we figure out hal and PolicyKit, as it would fix itself immediately.
I agree with the rpm trigger conditionalized on a sysconfig variable
as you said. But not with the service. The service is run on reboot,
and it is not helpful in that case. So it seems to me that it should
be a simple script run by a rpm trigger.
And it would also certainly be helpful to split it in 2, the modification
of /etc/udev/rules.d/99-fuse.rules should better be in ltsp5/script.d/xx-*,
while the setuid change would be in the aforementioned script.
loading the fuse is already done in the fuse package.
> In any case is having the fuse mounts insecure a requirement for
ltsp?
> It doesn't seems so to me.
ltspfs (we don't have packages yet) relies upon fuse to mount USB keys, floppies
and optical media from the thin client.
So I think that it should be in that package, not here.
--
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.