-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday 30 November 2002 01:15, Shawn wrote:
> receiving mail. I spent my spare time over a period of two weeks trying to
> figure this out, without much luck. I know that if I had been more
> focused, I would have been successful.
tip: a quick trip to a mailing list, google or IRC can almost always turn two
weeks of self-inflicted pain into 5 minutes of "A-HA!" ;-)
> On the other hand, I knew I could install Win2K, IIS, and Exchange in an
> afternoon. I did so and was sucessful. My email server is operational and
> I'm sending/receiving email through it no problem (except of course when I
> turn it off and forget to turn it back on....).
good to hear you got it working =)
> The deciding factor here was partially my own experience with Windows
> servers,
this is a very big point, and one that is always an issue. and will be for
people going the other way too as more people get comfy with Linux rather
than windows.
> mail client talking to the server and hope it was running right. One
> package, and about 5 or 10 minutes of configuring the mail server. That's
interestingly, that's what it takes me on linux. well, not one package, but
one distro and two packages: postfix and and a pop3 server. both are usually
installed when i select Mail server from the installation. and then i never
touch the thing again, except to add new users. so i think the real limiter
here is what you mentioned earlier: you already are used to and know Windows.
> When Linux can offer
> a simple install of it's server components, with a GUI interface (or even a
> command line menu system) to configure the components, then I think you'll
> see Linux fly.
this is already here and Linux already is flying on the server. it's the
desktop that's in question.
> are a large number of techs (mostly the newer/younger crowd I'd imagine -
> less exposure to DOS and such).
DOS and UNIX have nothing to do with each other. and the younger crowd tends
to be more Linux savvy than those of a few years back when Linux wasn't seen
as an option and wasn't "cool and sexy". the Linux presence in Universities
is also significant, which is important.
> applications for it just can't compete at the same level as Windows
> (typical office applications), in terms of ease of use, limited computer
> skill required, and overall user experience.
what's really important is whether or not users can get what they need and
want to get done accomplished. this is not a feature comparison in a glossy
magazine, this is "does it do what is needed?" if so, then the advantages of
freedom and future possibilities outweigh missing features that they don't
need/use anyways.
especially in corporate envs.
> hand. If not, the learning curve isn't as steep for Windows servers
> (ignoring the common material such as network theory, routing, etc.)
for the most basic stuff, perhaps. anything non-trivial and Linux usually wins
hands down, especially in the mid-long term.
> I expect this is Flame material,
not really. you presented your thoughts clearly =)
> must not know Linux very well, but the choice is easy for me... "What's the
> quickest way for me to get the job done?" For me, it was the windows
> route. Although I'm still going to be working with Linux occasionally, and
> see if I can make it work the way I need.
if you'd like, i bet someone here *ahem* would probably have no problems
helping you convert your windows email server to a linux one. should take
about an hour, including initial install time, if the system is decently
quick (mostly CD-ROM and HD Disk speed are the limiters for installing these
days).
- --
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
"Everything should be made as simple as possible, but not simpler"
- Albert Einstein
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE96Psk1rcusafx20MRAu3jAJkBi3FtJsVrwcaDkxGdF0u5c1SJnwCfQnCw
0RjKxjx1PslwYEKnMw5oGKg=
=P46e
-----END PGP SIGNATURE-----
