in Alexander Clouter's honest opinion:
> Well the type of package is not always relevant on a per-distro basis. If
> its available or not (and occasionally the version number, however you
> should always try to avoid committing yourself to a particular version
> number on reasons of convenience) is a completely different matter.
first of all i have to thank you of all the information, you gave me many
interesting points of view.
> All those are in Debian (have a look at the Debian website[1] for the
> comprehensive list, make sure you keep to 'stable'), I have used all of
> them personally except for openldap and mit-krb5 however I know there are
> plenty of people whom do.
well now maybe i'm gonna really take a look at the debian website

and
maybe [50%] new pdc is gonna be debian: i did some reflections about
openbsd, but sincerely don't wanna renounce to many linux attractions.
> Well its not really my place to say. It will replace your Windoze box
> quite comfortably, however from my understanding I hear openldap with
> samba is 'fun' to do, so expect a few nights burning the midnight oil.
in fact, that's what i tried to ask: do that packages suit for the services
mentioned? i mean is it a right 'coupling' use samba, openldap, postfix for
replace an active domain?
i ask this just because i never used ldap and neither krb5, even if
teorically i have some idea. the problem is that i want to use a single
database for managing domain auth, mail, dns and any other stuff i'm gonna
add
> Again, well if you want a webserver great, you will find there are plenty
> of other webservers worth looking at. Again it depends on what you are
> serving up.
old pdc has iis5 for publishing offices website, that's why i need apache -
i know it can support activeX, ASP, and some frontpage extensions - and
i'll probably will need them for compatiblity with some old webpages,
probably will need also odbc connectors too.
> As for 'tightvnc', I'm unsure why you would want to do this when 'ssh' can
> do everything you need. If you need remote graphics and such then a
> locally installed X server (cygwin for windows) and running things
> remotely that way is much more efficient. However it depends what you are
> doing with VNC; then this is not a Debian specific thing.
in fact i tried some remote Xs (cygwin and remote linuxes), but not always
cygwin worked well, and even if probably it just needs some tuning and
configuration, it seems to load my network. i thought that vnc would be of
less impact and it would give me much more compatibility if i could use it
via webclient.
after all i might not need vnc: my only hope is to give to some other users
possibility to manage server if needed remotely via an GUI interface (even
http) when i'm out of site it would be difficult to give support explaining
commands via ssh.
you could say that's it is insecure to follow this road: but sometimes
connections and ISP problems would force us to change default gw and remote
dns, and then we have several public ip's behind which often we need to
change the servers (for demo purposes we would need several architectures
to show to clients) or some time ago there was a spam intrusion (my fault,
and exchange's) so remote configuration for mail server is also
requested... so these and some other stuff makes us change configuration on
dns, dhcp and apache and network quite often (2,3 times a month).
> Why? Most of the time the server probably will sit in IO-Wait (waiting
> for the harddisk to supply the data it needs). Optimisation of the
> applications is not really the magic bullet, you would be better off
> looking at optimisation of your implementation and looking for
> scalability. Sure the optimising will help, but its not going to get you
> out of a fix when your environment grows tenfold
you're right - i would like to touch as less as possible a server

unfortunately it's not always possible.
> The requirements of a server is not what you want in a desktop. Sure it
> would be nice to have the 'latest is greatest' approach but then you end
> up compromise on the stability and security aspects.
well i knew that when i was 16

"don't touch a functional computer", even
a desktop.
> Well you probably will find grsecurity[2] does more than help you.
> SELinux is a good thing if you understand what its doing. If you are
> asking the question its probably not for you
GrSecurity should
> introduce you to a number of things in a pleasant way that does not mean a
> steep learning curve.
>
> Have fun
>
> Alex
thanks again alex, it was a pleasure to exchange ideas with you.
--
remove_this_ on mailing