I have an ultra 10 - running solaris 9 that I installed a few weeks ago...
I am not sure how to phrase this but basically I have some html doc's that I store on the ultra but I want people to be able to access from their windows workstation on our lan...
How can I do this?
If you could help start me off that would be great - I am not sure if I need to use/configure tomcat or apache or whats the best approach?
I you only want the users to be able to read the documents the easiest solution would be to install a webserver lets say apache on the sun box.
You can download apache from www.sunfreeware.com in solaris pkg format. (to install pkg files use the pkgadd command))
then just place the files in the htdocs directory
/Peter
exactly - I only want them to be able to read from the box...
I will give that a go - thanks for help - I was not sure where to begin.
No problems..
If you are having additional questions regardning this matter just ask and we will do our best to reply 
Good luck
/Peter
HELP!!
I got all of the necessary packages (I think) - these are what I got and installed:
apache-1.3.27.tar
mod_ssl-2.8.12-1.3.27.tar
openssl-0.9.6i.tar
gcc_small-3.4.1-sol9-sparc-local
But when I 'cd mod_ssl-2.8.13-1.3.27' and I run configure I get an error as below - any help is appreciated:
Configuring mod_ssl/2.8.12 for Apache/1.3.27
+ Apache location: ../apache_1.3.27 (Version 1.3.27)
+ OpenSSL location: ../openssl-0.9.6i
+ Auxiliary patch tool: ./etc/patch/patch (local)
./configure:Error: Building of 'patch' tool failed:
-------------------------------------------------
checking for fcntl.h... (cached) yes
checking for rename... (cached) yes
checking for pathconf... (cached) yes
checking for strerror... (cached) yes
checking for long file names... (cached) yes
creating ./config.status
creating Makefile
creating config.h
config.h is unchanged
./configure: make: not found
-------------------------------------------------
Hint: Either try to build 'patch' under etc/patch/
Hint: manually and re-run this 'configure' script
Hint: or provide us the path to your vendor 'patch'
Hint: program via the --with-patch=FILE option (but
Hint: expect perhaps failures when applying patches!)