[FreeNX-kNX] FreeNX defaults: Change ENABLE_SAMBA_PRELOAD="1"

[Florian.Schmidt3 at infineon.com]

Hi,

I think it doesn't matter if a feature is preenabled or not. It's more important that it is documented and there is a sample to see how the syntax works. The actual node.conf doesn't have a good documentation about the LOAD_BALANCE feature. If you change the default for ENABLE_SAMBA_PRELOAD please test if disabling works fine because for our environment this would be a security risk, so I have to disable it.

Kind Regards,

Dipl.Ing.(FH), Florian Schmidt

Infineon Technologies IT-Services GmbH
LSF Mgmt, RD-Linux Admin
IFKL IT OS DSM-CD
Tel.: +43 (0) 51777 4216
florian.schmidt3 at infineon.com

Postadresse:
Lakeside B05
9020 Klagenfurt, Austria

Firmenbuch: LG Klagenfurt, FN 246787y

VISIT US AT: http://www.infineon.com/austria


-----Original Message-----
From: Terje Andersen [mailto:terander at guard.zapto.org]
Sent: Tuesday, March 11, 2008 3:15 PM
To: freenx-knx at kde.org
Subject: Re: [FreeNX-kNX] FreeNX defaults: Change ENABLE_SAMBA_PRELOAD="1"

----- Melding fra FabianFranz at gmx.de ---------
     Dato: Tue, 11 Mar 2008 02:09:40 +0100
      Fra: Fabian Franz <FabianFranz at gmx.de>
Svar-til: User Support for FreeNX Server and kNX Client <freenx-knx at kde.org>
     Emne: [FreeNX-kNX] FreeNX defaults: Change ENABLE_SAMBA_PRELOAD="1"
      Til: User Support for FreeNX Server and kNX Client <freenx-knx at kde.org>


> Hi,
>
> I am currently thinking if I should make ENABLE_SAMBA_PRELOAD="1"
> the default.
>
> The advantage is that konqueror or smbclient can be directly used for
> browsing the local client-side shares.
>
> The disadvantage is that it might be that a local samba server can no
> longer be accessed via localhost or 127.0.0.1.
>
> However I think that most options are more useful if they can be
> disabled if they are not needed and not that the user first has to
> find them, then enable them and then use them.
>
> As most users might not know, which nice things are under the hood of FreeNX.
>
> Is that an acceptable policy? Opinions?
>

I agree that it should be enabled by default. Many installs FreeNX through their packaging system and don't know much about the inner workings of FreeNX, let alone the node.conf file, but they want to be able to use their locally attached printers.

If I think of what the main purpose of FreeNX is (for me: SBC), then most functionality should be turned on by default, and if it conflicts with a user/admin preference, they can be instructed to change the defaults in node.conf. Maybe a small "hint" at the end of 'nxsetup'? :)

        /Terje
________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:
  http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________