Hi i'm a bit new here :-)

Welcome... I'm not that experienced myself. I've been running a box since late Aug. but *nix since 95 so here are some thoughts...

Installed Ebox and works perfectly for my small server.
Still how can i setup better shares with samba? that means i correctly
can join my xp pro clients to ebox, but i don't have any particular
setting panel for home directories and cannot set rights to them.
And still the other problem i have is to make the http proxy to
authenticate users for browsing the internet, which now it doesn't.

my question about all that is: do i have to make all the changes with
vi by editing the confs? won't they be rewritten ever again when i
update some settings?

Ebox uses mason files to rewrite the real conf files for all the important ones that ebox messes with. For example smb.conf is actually rolled from smb.conf.mas (updatedb then locate smb.conf.mas from the command line). For instance,

a) I've had to make changes to my smb.conf.mas file because the default shares were given an underscore at the beginning ie/ my old pub-stu was become _pub-stu and then it would have caused confusion so I modded the smb.conf.mas file.

b) Another change I've had to make for my own school environment is removing the permissions sticky bit on new folders created in this share (changed 1774 to 0774 instead).

For the most part any confs can be changed manually but learning how mason works is a bit time consuming - you'll want to do this out of production, of course. The downfall of vi'ing manual changes is that when ebox is upgraded these mas files will get overwritten and you'll have to make changes again. (you wrote down the mods you did, right? My memory isn't as good as it used to be.)

Ebox is certainly not the most flexible environment but it is easy to use and reliable. Greater flexibility = more chance to screw it up.

Also, I've been a user of squid and dansguardian for six years already so I also make custom changes to my dansguardian.conf.mas file. As to authenticating users to squid/dans I think we are all still fighting/patching against incomplete support for NTLM authentication. This known, by far the easiest method I've setup in the past is ident. The hardest part is deploying an ident daemon on each windows box... and that's not very hard at all, either. squid.conf.mas and dansguardian.conf.mas are the files you need to attack.

FWIW,
Jamie



thanks


------------------------------

_______________________________________________
Ebox-user mailing list
[email protected]
https://lists.warp.es/mailman/listinfo/ebox-user

End of Ebox-user Digest, Vol 20, Issue 2
****************************************


_______________________________________________
Ebox-user mailing list
[email protected]
https://lists.warp.es/mailman/listinfo/ebox-user

Responder a