You are on page 1of 4

The below doc assumes that visionfs has been installed but not configured.

This also assumes that the unix account pharmacy exists on the system.
#
#
# visionfs setup
-------------------------------------------------------------------------Setting up SCO VisionFS 3.1
-------------------------------------------------------------------------Setup recommends you use the following settings:
Replace existing profile? = no
License mode = Fully licensed using OpenServer licensing
Keep VisionFS Administrators? = yes (pharmacy)
Change naming? = no
Restore default connection settings? = no
Restore default share settings? = no
Restore default directory settings? = no
Maximize logging? = no
Change authentication method? = no (VisionFS passwords (encrypted for Windows))
Start VisionFS on reboot? = yes (Run level = 2)
Start VisionFS after Setup? = yes
Are these settings OK?
Y - Yes, install using these settings
N - No, tell me more about the options and let me change the settings
Q - Quit now
OK to use these settings? [Y] N ......<--------------------- select N
-------------------------------------------------------------------------Replace existing profile
-------------------------------------------------------------------------Would you like Setup to remove your existing profile, and restore the
factory default settings for this release?
Replace existing profile? [no] Y ......<--------------------- select Y

-------------------------------------------------------------------------Authentication
-------------------------------------------------------------------------How would you like to authenticate users?
U - UNIX passwords (unencrypted)
V - VisionFS passwords (encrypted for Windows)
P - Another VisionFS or Windows NT server (pass-through)
Note: Windows NT 4, Windows 98 and newer versions of Windows 95
won't send unencrypted passwords by default. Using UNIX passwords
might cause authentication problems for those PCs.
Authentication method [v] ......<--------------------- select V.. this is the default

-------------------------------------------------------------------------VisionFS Administrator
-------------------------------------------------------------------------A VisionFS Administrator is a Windows user who's allowed to
configure the server using the Profile Editor.
Type the Windows and UNIX usernames of a user you want to be a
VisionFS Administrator. This user can add other
Administrators later using the Profile Editor.
Important: This user is as powerful as the UNIX superuser.
Windows username of VisionFS Administrator [pharmacy] ......<--------------------- enter
pharmacy
UNIX username of VisionFS Administrator [root] ......<--------------------- enter root

-------------------------------------------------------------------------VisionFS server name


-------------------------------------------------------------------------Would you like your VisionFS server to keep using the names
in the list below?
Windows users and programs use these names to connect to the server.
To change the names later, use the Profile Editor.
hcctest
Keep server names? [yes] N ......<--------------------- select N
VisionFS server name [s018042] ......<--------------------- verify the name now matches with
their correct system id
-------------------------------------------------------------------------Start VisionFS on reboot
-------------------------------------------------------------------------Would you like the VisionFS server to start automatically
when the UNIX host reboots?
Start VisionFS on reboot? [yes] ......<--------------------- select Y.. this is the default
At which run level should the VisionFS server start?
Choose from:
S - Single-user mode
1 - Administration mode
2 - Multi-user mode
3 - Remote file-sharing mode
4 - Alternative remote file-sharing mode
Current run level is: 2
Currently installed at run level: 2
Run level [2] ......<--------------------- select 2.. this is the default

-------------------------------------------------------------------------Start VisionFS after Setup


-------------------------------------------------------------------------Would you like the VisionFS server to start automatically
after Setup has finished?
Start VisionFS after Setup? [yes] ......<--------------------- select Yes . this is the default
-------------------------------------------------------------------------Setting up SCO VisionFS 3.1
-------------------------------------------------------------------------Replace existing profile? = yes ......<--------------------- select Yes . this is the default
License mode = Fully licensed using OpenServer licensing
Authentication method = VisionFS passwords (encrypted for Windows)
VisionFS Administrator = pharmacy (root on UNIX)
VisionFS server name = s018042
Start VisionFS on reboot? = yes (Run level = 2)
Start VisionFS after Setup? = yes ......<--------------------- select Yes . this is the default
Are these settings OK?
Y - Yes, install using these settings
N - No, tell me more about the options and let me change the settings
Q - Quit now
OK to use these settings? [Y] ......<--------------------- select Yes . this is the default
Copying and modifying files.......................done.
-------------------------------------------------------------------------SCO VisionFS Setup is complete.
-------------------------------------------------------------------------Starting SCO VisionFS 3.1 from /usr/vision/visionfs...
The server is running in fully enabled mode.
2009/02/20 14:53:49.960 (pid 742)
server/process/start SCO VisionFS(3.1)
#

You might also like