A Simple VNC Server and GDM Configuration Example for OpenSolaris 2008.05
My requirement was to be able to connect my VNC client to a system running OpenSolaris 2008.05 and to be able to login as root. I have now done this successfully on a system running the original OpenSolaris 2008.05 binary distribution and on a system running OpenSolaris 2008.05 after I ran a full image update to snv_91.
Update September 19th 2008: This procedure does not work if you have updated the image to snv_97 but does work if you update the image to snv_98. The upgrade from snv_97 to snv_98 wiped out the entries I had made in /etc/X11/gdm/custom.conf so I had to make those again. I have added an extra step at the end, based on Chris Drake's comments, to make the VNS server session persist if you exit the client.
1. Check that the VNC Server is Installed
This should be present as it is part of the 2008.05 binary distribution, but I checked anyway.
# pkg info SUNWxvnc
Name: SUNWxvnc
Summary: X11/VNC server
State: Installed
Authority: opensolaris.org (preferred)
Version: 4.1.2
Build Release: 5.11
Branch: 0.91
Packaging Date: Fri Jun 13 17:49:25 2008
Size: 6.3 MB
FMRI: pkg:/SUNWxvnc@4.1.2,5.11-0.91:20080613T174925Z
2. Add this line to /etc/services
vnc-server 5900/tcp # Xvnc
3. Edit /etc/X11/gdm/custom.conf as below
[xdmcp]
Enable=true
[security]
DisallowTCP=false
AllowRoot=true
AllowRemoteRoot=true
4. Enable the Services
# svcadm enable xvnc-inetd
# svcs xvnc-inetd
STATE STIME FMRI
online 16:22:30 svc:/application/x11/xvnc-inetd:default
# svcadm enable gdm
# svcs gdm
STATE STIME FMRI
online 14:43:13 svc:/application/graphical-login/gdm:default
5. Connect to the Display with a VNC Client
You should now be able to connect to
If you cannot connect, try stopping & starting the services:
# svcadm disable xvnc-inetd gdm
# svcadm enable xvnc-inetd gdm
6. Making the Session Persist
This may or may not be desirable for you, but if you want the VNC session to persist if you exit the VNC client then do the following:
# svccfg -s xvnc-inetd
svc:/application/x11/xvnc-inetd> editprop
This take you into a vi session. Look for the line...
#setprop inetd/wait = boolean: false
Copy the line, uncomment it and set it to true. Save the file, exit svccfg and run the command...
# svcadm refresh xvnc-inetd
Connect again with you VNC client. Now, when you exit/kill the VNC client, the session on the server will persist and you will be able to connect to it again.
You may now want to add an extra level of security to enable password protection on your VNC server. That is something that I have been unable to make work...and from searching around, it seems that others have a similar problem.I often get queries about mounting NTFS / Ext2 / Ext3 / FAT 16 / FAT 32 partions in Solaris . Follow the below steps . Note that its only read-only support for NTFS / Ext2 / Ext3 .
* Download packages
FSWpart
FSWfsmisc
Note these are packages for x86 Solaris .
* unzip the packages and install it
root~#gzcat FSWpart.tar.gz | tar xvf -
root~#gzcat FSWfsmisc.tar.gz | tar xvf -
root~#pkgadd -d . FSWpart
root~#pkgadd -d . FSWfsmisc
* Now run the prtpart tool
root~#/usr/sbin/prtpart
It would result in following output
root~#/usr/sbin/prtpart
Fdisk information for device /dev/rdsk/c1d0p0
Block Size : 512 bytes
Controller : ide
Disk : cmdk
Capacity : 74 GB
# start block # nblocks startCylSecHd endCylSecHd OSType
1: 0000000063 0006152832 0/ 1/ 1 7e/7f/fe Diagnostic
2: 0006152895 0025173855 7f/41/ 0 ff/ff/fe WIN95 FAT32(LBA)
3: 0031328640 0052432128 ff/ff/fe ff/ff/fe Solaris x86
4: 0083760830 0072535555 ff/ff/fe ff/ff/fe DOS Extended
# start block # nblocks startCylSecHd endCylSecHd OSType
5: 0000000001 0031407012 ff/ff/fe ff/ff/fe Linux native
0: 0031407013 0001994202 ff/ff/fe ff/ff/fe DOS Extended
# start block # nblocks startCylSecHd endCylSecHd OSType
6: 0000000063 0001994139 ff/ff/fe ff/ff/fe Linux swap
0: 0033401215 0039134340 ff/ff/fe ff/ff/fe DOS Extended
# start block # nblocks startCylSecHd endCylSecHd OSType
7: 0000000063 0039134277 ff/ff/fe ff/ff/fe WIN95 FAT32(Upto 2047GB)
Now note the disk id. In the above example its "/dev/rdsk/c1d0p0"
Now run
root~#/usr/sbin/prtpart /dev/rdsk/c1d0p0 -ldevs
Fdisk information for device /dev/rdsk/c1d0p0
** NOTE **
/dev/dsk/c1d0p0 - Physical device referring to entire physical disk
/dev/dsk/c1d0p1 - p4 - Physical devices referring to the 4 primary partitions
/dev/dsk/c1d0p5 ... - Virtual devices referring to logical partitions
Virtual device names can be used to access EXT2 and NTFS on logical partitions
/dev/dsk/c1d0p1 Diagnostic
/dev/dsk/c1d0p2 WIN95 FAT32(LBA)
/dev/dsk/c1d0p3 Solaris x86
/dev/dsk/c1d0p4 DOS Extended
/dev/dsk/c1d0p5 Linux native
/dev/dsk/c1d0p6 Linux swap
/dev/dsk/c1d0p7 WIN95 FAT32(Upto 2047GB)
The above command scan you hard-disk and displays all available filesystems. Note the required filesystems to be mounted.
To mount NTFS partition use
root~#mount -F ntfs /dev/dsk/c1d0p
To mount FAT 16 / FAT 32 partition use
root~#mount -F pcfs /dev/dsk/c1d0p
if the above command fails you can try the below option
root~#prtpart /dev/dsk/c1d0p0 -fat
the above command should list the available PCFS / FAT partitions in colon notation, then use the same for mounting (eg)
root~#mount -F pcfs /dev/dsk/c1d0p0:d /mnt/windows
To mount Ext2 / Ext3 partitions use
root~#mount -F ext2fs /dev/dsk/c1d0p
To unmount a partition use "umount
root~#umount /mnt/linux
passwd postgresIf u get some error e.x : su: No shell, u should config shell apply for postgres user
usermod -P "Postgres Administration" -R postgres bearsoft
su - postgres
suu change shell apply for root, bearsoft (current user), and postgres account into /bin/bash
gedit /etc/passwd
pfexec /usr/postgres/8.3/bin/initdb /var/postgres/8.3/datadone.
Start server
/usr/postgres/8.3/bin/pg_ctl -D /var/postgres/8.3/data -l var/postgres/8.3/logfile start
