Proof reading this, I can see where a speller and grammaticer is in store
for this guy.

Ken

----- Original Message -----
From: "Kenneth Lang" <[EMAIL PROTECTED]>
To: "Esmith Developer" <[EMAIL PROTECTED]>
Sent: Tuesday, December 12, 2000 6:49 PM
Subject: [e-smith-devinfo] E-smith 4.1 First Time Install


Here is some feedback on my install of 4.1 Beta.

1).  After the installation, following the known issues, I downloaded the
e-smith-base-4.1.1-4.  It seemed to have install properly, except when I
install it from over the net, it installs, then I assume it configures is
then kicks be off back to my DOS session.

After the install, I noticed rpm -qa  that it did install and the previous
version is still there -4.1.1-3 of the base.

Should both version be here???

2)  When I install e-smith-email-4.3.1-14 from peters install, it removed
the previous version as has always happened
under 4.0 and 4.01.

3)  I had to follow the known issues page to remove e-smith-mod_ssl as
described to access thru the browser
and this seemed to have worked fine.

4)  After connecting thru the browser, under the workgroup, noticed that the
settings did not take as I requested during the install.  ie all pointed to
e-smith and it became the domain master. (This time it did not take over my
LAN and become the BDC, thanx)

I changed them to what I used to have, (as this is my LAB machine)

5)  When I go through network neighborhood now, I noticed a new domain call
Mygroup next to my original domain, ironically I can browse it but there is
nothing there, a reboot did not clear it up.

6)  Under 4.01 I installed PHP/Horde/IMP  in the browser I could type in
http://webmaster/e-smith-manager/phpMyAdmin
to get to the menu.  I cannot get it to come up under 4.1 is there a new URL
for this.

7)  On the e-smith.org there is a bulletin board for general new user and
advanced forum.  I recieve mail from developers but  I cannot find the
bulletin board for developers to follow all issues, does this even exist or
just e-mail recipients.

8)  I tried to accept_upgrade from 4.01 to 4.1, this failed as I was told it
would.  I can see where this will be challenge to upgrade my production
server.

Ken






Reply via email to