Re: [osol-discuss] Opensolaris or Solaris VPN solutions
The problem with specifying VPN solutions is that it allows for SSL and IPSec VPNs. Worked with Checkpoint for over 14 years I do not remember their ever being a Solaris VPN client but they do offer SSL VPN. Cisco do support Solaris SPARC on one of their VPN client applications, however the latest Cisco AnyConnect VPN client is Windows only and is a SSL VPN technology. I know that Palo Alto Networks do not provide any IPSec client software and only support SSL VPNs. Juniper does not support Solaris (but does Win, Linux, MacOS) while Fortinet's ForiClient is Windows only. It is fair to say that Solaris VPN client solutions from Firewall vendors are not common, however as IPSec is used then it possible to configure an IPsec tunnel from a OpenSolaris/Solaris host to any firewall. However, getting a Firewall Administrator unless you are a CEO of a corporate is virtually nil. What is required is on OpenSolaris/Solaris is a generic VPN client, which allows central control of the IPFilter firewall on the host, secure authentication which would require account locking of non authorised accounts, dynamic interface and route creation and policy enforcement. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] VirtualBox v3.2.0 BETA download
Hi, The latest version of VirtualBox v3.2.0 Beta is available for download here http://download.virtualbox.org/virtualbox/3.2.0_BETA1/VirtualBox-3.2.0_BETA1-60785-SunOS.tar.gz Unfortunately there appears to be a problem at present where you can only download 6.3MB of the 82MB file. Not being paranoid, I check other downloads from the same directory which worked perfectly. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] OpenSolaris build 134a has closed
Thanks for the good news, personally I was expecting a May release date anyway. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [install-discuss] OpenSolaris packaging feedback suggestion
Hi Stephen, Thanks for the feedback, I had not thought about submitting the idea as a defect. While it is easy to track application installs from the server logs to gauge popularity for version and feature enhancement, understanding what happened to an application after installation was not. If included this will allow OpenSolaris.org to respond more effectively to user base requirements. It would also be useful if the following option was added to allow user feedback to indicate a preferred application. If sufficient users are installing it then it could be included in the Package Repository. 8. Switching to application application name As a matter of interest, when using the Package Manager and a search is performed for an application could this information be captured and fed back to draw up a list of most searched for applications? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] OpenSolaris packaging feedback suggestion
Hi, After installing Ubuntu 9.10 desktop on another desktop, I used the Ubuntu Software Update tool to add a number of applications. However, one or two of these applications failed to run and did not report errors in the logs or when run from the command line; as a result I uninstalled them. When someone uninstalling an application using the Package Manager. would it be worth while to get the user to indicate why they were uninstalling this version. ie The user could be provided with a list 1. Incorrect software choice 2. Software Bug 3. Upgrading to newer version 4. Downgrading to older version 5. Software no longer required 6. Security problem 7. Switching to external/own build -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] LiveCD - additional software
Hi, While attempting to remove viruses from my wife's pc, only one remains now. I thought I would boot from the LiveCD mount the NTFS filesystem as read/write and then run one of the online virus scanners against the mounted disk. While I did find the necessary pre-built OpenSolaris packages here http://www.sunfreepacks.com after reading this blog entry http://blogs.sun.com/AlokChakrabarty/entry/how_to_mount_ntfs_and . Unfortunately, when attempting to install the packages I get the following message pkgadd: ERROR: Not enough space to backup /var/sadm/install/contents pkgadd: ERROR: Need=41011 blocks, Available=1594 blocks (block size=512) Could the NTFS file support be added to the LiveCD? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Legacy GRUB v GRUB2
Hi, I found a reference here ( http://en.wikipedia.org/wiki/GNU_GRUB ) that OpenSolaris uses a modified Legacy GRUB install to support disk labels, automatic 64 bit kernel selection and booting from ZFS (with compression and multiple boot environments). Are there plans to support GRUB2 as the its ability to be extended ( see here http://www.gnu.org/software/grub/grub-2.en.html ) via dynamically loaded modules would allow only specific modules to be replaced, added or removed. eg If rpool is upgraded to support encryption and encryption is applied, this would automatically trigger the installation of correct GRUB2 module which would be able to prompt for the appropriate access key from the keyboard or usb memory stick. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] OpenSolaris 1002 build 124 - unexpected reboot
Bug was logged http://defect.opensolaris.org/bz/show_bug.cgi?id=11870 and now has been transferred to http://bugs.opensolaris.org/view_bug.do?bug_id=6892416 The unexpected reboot can avoided by modifying the kernel boot options to include -kv , this generates a verbose messaging but it will boot and correctly identify all hardware. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] OpenSolaris 1002 build 124 - unexpected reboot
Hi, I have been looking at the release notes for Solaris 10 10/09 and came across the following point x86: NVidia SATA Controllers Do Not Support ATAPI Devices (6595488) The driver for the NVidia SATA controller MCP55 and CK804 chipsets included in the Solaris 10 5/09 release does not support ATAPI CD/DVD devices. During system installation or upgrade by using a SATA CD/DVD device, the Solaris installer starts and appears to function but fails with the following error messages: ERROR: The disc you inserted is not a Solaris OS CD/DVD or There were problems loading the media from /cdrom During normal system operation, the SATA CD/DVD drive is not configured and cannot be used. I find that when I try to boot from OpenSolaris my computer reboots as it probes devices, do you think it could be related to this bug? Given that the old NVidia driver for the MCP55 and CK804 chipsets did support SATA DVD/CD drives (see below for units I currently use extracted from Cdrecord-ProDVD-ProBD-Clone 2.01.01a57 ) PIONEER ' 'DVD-RW DVR-212D' '1.24' Removable CD-ROM 'LITE-ON ' 'DVDRW LH-20A1S ' '9L08' Removable CD-ROM What additional functionality has the new driver provided? Can the new driver be fixed so that it does support SATA DVD drives? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] OpenSolaris 1002 build 124 - unexpected reboot
Just found the following at http://docs.sun.com/app/docs/doc/819-2254/nv-sata-7d?l=ena=viewq=nv_sata about the nv_sata driver Name nv_sata– Nvidia ck804/mcp55 SATA controller driver Synopsis s...@unit-address = Description The nv_sata driver is a SATA HBA driver that supports Nvidia ck804 and mcp55 SATA HBA controllers. [b]Note that while these Nvidia controllers support standard SATA features including SATA-II drives, NCQ, hotplug and ATAPI drives, the driver currently does not support NCQ features.[/b] -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Display CPU temprature
Hi Ken, In my case I am running the latest Bios version which claims to support APCI v3.0 which includes Thermal Zone information, however this is not implemented by the motherboard manufacturer. If motherboard manufacturers implemented the ACPI standard in full then all the modern OSes could report CPU temperature information without any additional software or by reading directly from hardware. The dtrace script will not work on my workstation because the Solaris can not create the ACPI probe which accesses the CPU temperature information. I contacted Alan Perry at Sun about this previously and he provided a tool which analysed the ACPI information on my computer. As I understand if the Bios implements the ACPI specification fully then Solaris will provide this information using prtdiag. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] OpenSolaris 1002 build 124
Hi, Downloaded osol-1002-124.iso from http://www.genunix.org/ and attempted to boot the ISO image. The boot process reached mounting root read/write and OpenSolaris started to probe devices, after about thirty seconds the system rebooted with no warning message. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Display CPU temprature
Hi Dennis, The tzmon (thermal zone monitoring is part of the ACPI specification v3.0 and enhanced in v4.0). If your BIOS is fully ACPI v3.0 or v4.0 compliant then you can access the information otherwise you have to write an application to access the hardware directly. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Display CPU temprature
Hi Husam, Assuming you are running on x86/x64 platform check if your bios supports ACPI v3.0 or ACPI v4.0 both versions of the ACPI standard include information on thermal information. The ACPI v3.0 specification includes from 2004 includes Major specification revision. General configuration enhancements. Inter-Processor power, performance, and throttling state dependency support added. Support for 256 processors added. NUMA Distancing support added. PCI Express support added. SATA support added. Ambient Light Sensor and User Presence device support added. Thermal model extended beyond processor-centric support. The ACPI v4.0 specification released June 2009 includes :- Major specification revision. Clock Domains, x2APIC Support, Logical Processor Idling, Corrected Platform Error Polling Table, Maximum System Characteristics Table, Power Metering and Budgeting, IPMI Operation Region, USB3 Support in _PLD, Re-evaluation of _PPC acknowledgement via _OST, Thermal Model Enhancements, _OSC at \_SB, Wake Alarm Device, Battery Related Extensions, Memory Bandwidth Monitoring and Reporting, ACPI Hardware Error Interfaces, D3hot. OpenSolaris/Solaris/Windows/Linux all support the ACPI specification so that if all Motherboard vendors supported the ACPI specification the OS would be able to detect all the information without extra software to detect CPU temperature, etc. The ACPI specification also allows settings to made, ie set the Max Temperature settings for thermal alarm. Try checking your BIOS settings, mine allows me to set ACPI v3.0 but does not include most of the functionality. I did contact my motherboard BIOS supplier AMI, they fully support the ACPI v3.0 and v4.0 specification but it is up to the motherboard vendor to build the BIOS and what functionality they provide. Contact your Motherboard supplier and ask them to fully support the ACPI specification. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] 3rd Party Libraries
Hi, I was looking at Building Free-CAD (link below) on OpenSolaris http://sourceforge.net/apps/mediawiki/free-cad/index.php?title=Main_Page In order to build Free-CAD, I would have to build all the required third party libraries except those which are provided as part of OpenSolaris (see list) Lib name Version needed Link to get it Python = 2.5.xhttp://www.python.org/ OpenCasCade = 5.2 http://www.opencascade.org Qt = 4.1.xhttp://www.qtsoftware.com Coin3D = 2.x http://www.coin3d.org ODE = 0.10.x http://www.ode.org SoQt= 1.2 http://www.coin3d.org Xerces-C++ = 2.7.x 3.0 http://xml.apache.org/xerces-c/ GTS = 0.7.xhttp://gts.sourceforge.net/ Zlib= 1.x.xhttp://www.zlib.net/ Boost = 1.33.x http://www.boost.org/ OpenCV = 1.0 http://sourceforge.net/projects/opencvlibrary/ As a Debian/Ubuntu user these are available via apt-get, so only Free-CAD source would be required to be built. Is there a list of third party libraries which can voted on for inclusion in the OpenSolaris repository? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [desktop-discuss] OpenSolaris b121 and printing
Hi, Has this printing problem with foomatic been fixed in Build 123? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] OpenSolaris b121 and printing
Hi, FYI Bug reference CR6878506 updated today Priority - High, Status - Accepted and an Engineer has been assigned -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] one time passwords - apache infrastructure incident report 8/28/2009
Hi, Just be reading about apache.org incident report for 8/28/2009 ( https://blogs.apache.org/infra/entry/apache_org_downtime_report ) The use of Solaris and ZFS on the European server was interesting including the recovery. However, what I found more interesting was the use of one time passwords which is supported by FreeBSD ( http://www.freebsd.org/doc/en/books/handbook/one-time-passwords.html ). Could or should this technology be incorporated into OpenSolaris? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [desktop-discuss] OpenSolaris b121 and printing
Hi,
Here is the output as requested.
$ lpstat -p deskjet -l 2
printer deskjet idle. enabled since September 2, 2009 9:37:50 AM BST.
available.
printer-name=deskjet
printer-uri-supported=lpsched://localhost/printers/deskjet
job-sheets-supported=standard
document-format-supported=application/postscript
printer-info=HP Photosmart c6280
device-uri=socket://192.168.2.130:9100
lpsched-interface-script=/usr/lib/lp/model/uri
nolpsched-login-term
nolpsched-daisy
lpsched-printer-type=unknown
lpsched-cpi-value=0
lpsched-cpi-unit=0
lpsched-lpi-value=0
lpsched-lpi-unit=0
lpsched-plen-value=0
lpsched-plen-unit=0
lpsched-pwid-value=0
lpsched-pwid-unit=0
ppd-file-uri=file://ts4/etc/lp/ppd/deskjet.ppd
lpsched-printer-configure-ppd-uri=file://ts4/usr/share/ppd/SUNWhpijs/HP/hp-photosmart_c6200_series-hpijs.ppd.gz
lpsched-ppd-source-path=/usr/share/ppd/SUNWhpijs/HP/hp-photosmart_c6200_series-hpijs.ppd.gz
printer-make=HP
printer-model=HP Photosmart c6200 series Foomatic
printer-make-and-model=HP Photosmart c6200 series Foomatic
media-default=Letter
media-supported=Letter,A4,Photo,Photo5x7,PhotoTearOff,3x5,5x8,A5,A6,A6TearOff,B5JIS,CDDVD80,CDDVD120,Env10,EnvC5,EnvC6,EnvDL,EnvISOB5,EnvMonarch,Executive,FLSA,Hagaki,Legal,Oufuku,w558h774,w612h935
PageRegion-default=Letter
PageRegion-supported=Letter,A4,Photo,Photo5x7,PhotoTearOff,3x5,5x8,A5,A6,A6TearOff,B5JIS,CDDVD80,CDDVD120,Env10,EnvC5,EnvC6,EnvDL,EnvISOB5,EnvMonarch,Executive,FLSA,Hagaki,Legal,Oufuku,w558h774,w612h935
PrintoutMode-default=Normal
PrintoutMode-supported=Draft,Draft.Gray,Normal,Normal.Gray,High,High.Gray,Photo
lpsched-disable-reason=new printer
lpsched-disable-date=Wednesday, September 2, 2009 9:37:50 AM BST
lpsched-reject-reason=new destination
lpsched-reject-date=Wednesday, September 2, 2009 9:37:50 AM BST
printer-current-time=Thursday, September 3, 2009 10:49:51 AM BST
printer-up-time=1251971391
printer-state=3
printer-is-accepting-jobs
printer-is-processing-jobs
printer-state-reasons=none
multiple-document-jobs-supported
multiple-document-handling-supported=seperate-documents-colated-copies
pdl-override-supported=not-attempted
job-priority-supported=40
job-priority-default=20
copies-supported=1-65535
copies-default=1
page-ranges-supported
number-up-supported=1
number-up-default=1
job-hold-until-supported=no-hold,indefinite
job-hold-until-default=no-hold
document-format-default=application/octet-stream
On the OpenSolaris discussion list, a work around was given see below
This looks like a known issue and I'm pretty sure that there is a bug
filed against it, though I can't seem to locate it (See
http://www.opensolaris.org/jive/thread.jspa?threadID=87603tstart=0).
There are two possible workarounds here.
1. modify the interface script that LP uses to print to the printer
(/etc/lp/interfaces/{queue}so that it runs
/usr/lib/cups/filterfoomatic-rip-hplip instead of
/usr/lib/lp/bin/foomatic-rip
2. switch to CUPS and create your queue under CUPS.
# pkg install SUNWcups
# svccfg import /var/svc/manifest/application/cups.xml
# print-service -s cups
You can create your queue by launching System - Administration
- Printer Manager after switching to CUPS, CUPS web interface
(http://localhost:631/admin/), or lpadmin (1cups) man -s 1cups lpadmin
As previously posted I have logged a Bug and be given the reference CR6878506,
from the update I have received it appears there is a bug with foomatic.
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
[osol-discuss] OpenSolaris b121 and printing
Hi, I downloaded the development build (osol-1002-121-x86.iso) and installed it as a VBox client using VirtualBox 2.2.4 on my Solaris host giving the VBox host access to the network. Everything is okay except for the printing to my network connected HP Photosmart C6280. My Solaris host and VBox windows xp client can both successfully access the printer. However, after configuring OpenSolaris b121 to access the printer after configuring it with either the Solaris LP Print Manager or the Print Manager the printer is configured and indicated as ready, print jobs can be sent but nothing it printed and I can not find any error in the logs. Using Solaris LP Print Manager configuration is as follows :- Printer Name: hp1 Printer Server: localhost Description: hp photosmart c6280 Printer Make: HP Printer Model: HP Photosmart c6280 series Foomatic/hpijs Printer Driver: SUNWhpijs(S):, hpijs 2.8.7.3 Fault Notification: Write to Superuser Destination: hpdeskjet:9100 Protocol: TCP Options: Default printer Banner: Never Print Banner User Access list: All Or using Print Manager Type: Socket Name or IP Address: hpdeskjet Port:9100 Local Queue Name: deskjet Description: hp photosmart c6280 Manufacturer: HP Model:HP Photosmart c6200 series Foomatic/hpijs Driver:, hpijs 2.8.7.3 Set as default printer queue: Yes I have checked connectivity, it is possible to telnet to port 9100 on the printer from OpenSolaris VBox install. Surely getting printing to work should be a simple matter of running Print Manager and everything working. As a matter of interest is Solaris LP Print Manager depreciated and being replaced by Print Manager? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] OpenSolaris b121 and printing
Hi Norm, Thanks for the info, I logged a bug (reference CR6878506). -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Digital Camera support
Hi, I noticed that GPhoto2 was not included in SXCE b121 but is provided in Solaris 10 as the Digital Camera Browser. Is there a replacement for GPhoto2 in latest release of OpenSolaris or has it been replaced with some other application to perform a similar function? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Notice to VirtualBox users - v3.0.4 released
Hi, If you are interesting in downloading the latest OpenSolaris/Solaris release http://download.virtualbox.org/virtualbox/3.0.4/VirtualBox-3.0.4-50684-SunOS.tar.gz There are a number of bugs that have been fixed :) -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Change log missing on web page for b117 ?
Hi, is this it? http://dlc.sun.com/osol/on/downloads/b117/on-changelog-b117.html -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Solution for CISCO Anyclient VPN
Hi Jörg, I used that last year it was a SSL VPN client which required an OS specific download in order to route traffic over the VPN. There was a version for Windows and Linux but supported on only two versions (Suse/RedHat) but I believe it was tested on Ubuntu as well. Hope that helps -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Solution for CISCO Anyclient VPN
Hi Jörg, This appears to give details of the SSL VPN http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a008072462a.shtml Then your best approach is to try and get OpenVPN working with Cisco http://openvpn.net/index.php/open-source.html Russell -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Regarding GCC
You can download the Sun Studio 12 C, C++ and Fortran compiler from here http://developers.sun.com/sunstudio/downloads/index.jsp -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] OpenSolaris 2009.06 missing SXCE b114 desktop applications
Thanks Andrew for the email. It appears that OpenSolaris has gimp is labelled as SUNWgnome-img-editor. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] LSI card query
Hi, Is is probable that the following LSI devices would be supported by the lsimega driver if it was configured to recognise them. If you have any of the cards below, can you check to see if the card is recognised using the lsimega driver. For example to test if the device is recognised you need to add the correct pci entry to /etc/driver_aliases via the following command eg # update_drv -a -i pci1011,46 lsimega The list below gives the pci ids for the card, as you can see some cards have two different pci ids so you will need to run prtconf -pv or scanpci to determine which pci id to use where there are two pci ids. pci1011,46 and pci8086,B555 - MegaRAID Enterprise 3000 (489) pci101E,1960 - LSI Express 500 (475) pci101E,1960 and pci1000,1960 - MegaRAID i4133 (522) pci101E,1960 - HP 475 pci101E,1960 - HP 475 netraid 1M pci101E,1960 - HP 493 pci101E,1960 - HP 493 netraid 2M pci101E,1960 - LSI Express 500 (475) pci101E,1960 - MegaRAID Elite 1600 (493) pci101E,1960 - MegaRAID Elite 1650 (494) pci101E,1960 - MegaRAID Elite 3100 (477) pci101E,1960 - MegaRAID Enterprise 1600 pci101E,1960 - MegaRAID Enterprise 1600 (471) pci101E,1960 - MegaRAID Enterprise 1650 (503) pci101E,1960 - MegaRAID i4 IDE RAID Controller (LSI Logic) pci101E,1960 and pci1000,1960 - MegaRAID i4133 (522) pci101E,1960 and pci1000,1960 - MegaRAID i4133 (522) pci101E,9010 - MegaRAID Enterprise 1200 (428) pci101E,9060 - MegaRAID Enterprise 1300 (434) pci8086,1960 and pci101E,1960 - MegaRAID Elite 1600 (493) pci8086,1960 and pci101E,1960 - MegaRAID Elite 1650/1700 (494) pci8086,1960 and pci101E,1960 - MegaRAID Enterprise 1600 (471) pci8086,1960 and pci101E,1960 - MegaRAID Enterprise 1700 (503) pci8086,1960 and pci101E,1960 - MegaRAID Express 500/500LC (475) pci8086,1960 - HP netraid pci8086,1960 - HP netraid 3si pci8086,1960 - HP netraid lsi pci8086,1960 - MegaRAID 431 pci8086,1960 - MegaRAID Enterprise 1400 (438) pci8086,1960 - MegaRAID Enterprise 1500 (467) pci8086,1960 - MegaRAID Express 000 (762) pci8086,1960 - MegaRAID Express 200 (466) pci8086,1960 - MegaRAID Express 300 (490) -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] sxce b114 problems
Just tried to install sxce b 144 in as a VirtualBox client, while the installation occurred normally the system reported missing on line 1124 in /etc/driver_aliases. The system boots and I was able to install VirtualBox v2.2.2 additions but the system reboots a USB hub errors and reboots automatically. Anyone else experienced a similar problem? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Booting in Safe Mode
As part of a my Solaris 10 installation I needed to install a device driver to recognise my disk controller to access my hard disk. As an experiment one day I booted into Solaris Safe Mode but found that I could not access my hard disk as the disk controller was not detected and therefore no disks were found. Assuming that the future release of the OpenSolaris LiveCD will allow the user to install a device driver (like Solaris after the grub boot during the initial stages of the install). Are the device drivers incorporated into the Normal Boot and Safe Mode environments? If the device drivers are not added to the Safe Mode environment, will there be a provision to be able to install drivers temporarily in order to access and mount drives? If the drivers are incorporated into the Safe Mode Environment and you update with a newer device driver which replaces the good driver with a bad driver. Will it be possible to remove the newer driver and add the old device driver to the Safe Mode environment in order to access the disk controller and drive then replace the newer driver installed on the drive? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How to add driver during Live CD booting? Tried -s
Hi Juergen I have filed a bug this morning. Thanks for the help. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How to add driver during Live CD booting? Tried -s
Hi Jurgen, Thanks for the tip. # update_drv -a -i pci1000,409 lsimega # update_drv -a -i pci1000,409.1000.3008 lsimega # update_drv -a -i pci1000,409,1000.3008.a lsimega The above worked, OpenSolaris Device Driver Utility correctly identified the LSI MegaRAID SATA 300-8X card and I able to successfully mount my UFS filesystem. Now I will be able to perform a clean install of OpenSolaris. Will the modified driver settings be transferred to the disk installation or will it be necessary to perform the update_drv manually on the disk installation in order to boot from disk? Can the SUNWlismega driver in OpenSolaris be modified to recognise the LSI MegaRAID SATA controller by default? It is only a single text line change in Postinstall. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How to add driver during Live CD booting? Tried -s
Hi Martin, I booted from the LiveCD, modified the kernel Grub entry to -s and succeeded to get to single user mode. I tried to remove the SUNWlsimega driver with pkgrm SUNWlsimega but this failed. So I modified the /etc/driver_aliases so that lsimega entries are as follows to match the entries that are in my tweaked SUNWlsimega driver. lsimega pci1000,408.1000.2* in standard driver lsimega pci1028,13.1028.16c lsimega pci1028,13.1028.16d lsimega pci1000,408.1028.2 lsimega pci1000,407.1000.532 * in standard driver lsimega pci1028,13* in standard driver lsimega pci1000,407 * in standard driver lsimega pci1000,408 * in standard driver lsimega pci1000,409 lsimega pci1000,409.1000.3008 lsimega pci1000,409.1000.3008.a lsimega pci1000,1960 * in standard driver lsimega pci1001,1965 Correspond to the ids of the devices below, Windows uses a common driver for all these devices. The Sun SUNWlsimega VERSION: 11.10.0,REV=2005.09.15.00.24 works well with the LSI MegaRAID SATA 8X controller and has been for nearly two years. Intel(R) RAID Controller SRCU41L, SRCZCRX, SROMBU42E, SRCS16, SRCU42E, SRCU42X MegaRAID Express 500/500LC RAID Controller Driver MegaRAID SCSI 320-1E, 320-2E RAID Controller Driver MegaRAID Express 300 RAID Controller Driver MegaRAID Elite 1600, 1650/1700 RAID Controller Driver MegaRAID Enterprise 1200, 1500, 1600, 1700 RAID Controller Driver MegaRAID i4 IDE RAID Controller MegaRAID SCSI 320-1, 320-2 RAID Controller Driver MegaRAID i4133 RAID Controller Driver MegaRAID SCSI 320-0, 320-0X,320-2X, 320-4X RAID Controller Driver HP NetRAID-1M, NETRAID-2M RAID Controller Driver MegaRAID PCI Express(TM) ROMB MegaRAID SATA 150-4, 150-6, 300-4X, 300-8X, 300-8XLP RAID Controller My problem is how can I get the system to rescan the hardware and recognise my LSI controller. I tried devfsadm but without success. I suppose an alternative approach would be to add the additional pci identifiers to the SUNWlsimega Version 11.11,Rev=2008.10.30.20.37 driver for inclusion in the next LiveCD release. I have noted that the lsimega binaries in Version 11.11 are bigger than those in Version 11.10. It would also increase the amount of hardware supported by OpenSolaris. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How to add driver during Live CD booting?
Can OpenSolaris 2009.06 have the functionality to add drivers during the initial stages of OpenSolaris booting like Solaris and SXCE? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] About open solaris 2009.06 release
Can OpenSolaris 2009.06 be configured to allow driver installation during the early boot process like Solaris and SXDE? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] About open solaris 2009.06 release
Is this functionality scheduled to be included in OpenSolaris? If so, when should it be included? TIA -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] About open solaris 2009.06 release
It would be very helpful to have it in 2009.06 as it would allow me to actually install OpenSolaris as my base OS instead of having it as a client in VirtualBox. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] How to add driver during Live CD booting?
Hi. I would like to install a device driver during the boot process of the Live CD so that it correctly identifies my hardware? Is this a feature that the Live CD supports? Could this feature be added to subsequent Live CDs? This message is relates to the posting below in OpenSolaris:Discuss and Device Drivers:Discuss OpenSolaris 2008.11 and modified Sun LSImega driver TIA -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How to add driver during Live CD booting?
Thanks for the reply but building my own Live CD distro is not a very elegant solution. Surely a more practical approach would enable drivers to be added during the boot process either by automatically scanning USB drives or a second DVD drive if present. This would allow a Live CD to recognise newer hardware just by using the latest drivers stored in a USB or DVD/CD. Manufacturers could then be asked to supply drivers for inclusion on the driver DVD/CD. A user copies the driver DVD/CD to disk, add additional drivers that were supplied with their hardware and write a new driver DVD/CD specifically for their computer which could be used in future versions of Live CD. On the the case of a USB drive, just copy the manufacturers drive to the USB drive. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How to add driver during Live CD booting?
Hi, It is great that it can be done using the methods you have outlined but the user is not prompted Do you wish to add a device driver? Press Y to add driver so the process is not that user friendly compared to Windows or Ubuntu. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How to add driver during Live CD booting?
The only reason I pointed it out was that I tried to install OpenSolaris as my base OS and found the feature missing. Sometimes, knowing what question to ask is almost as difficult as answering the question. Thanks for the feedback. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How to add driver during Live CD booting?
Hi Martin, Nearly two years ago I tweaked the SUNWlsimega driver to recognise the LSI MegaRAID SATA 300-8X raid controller and have been using ever since (as I used to manage the ftp site so know from which locations it was downloaded which included Sun). It was a minor change and I found the driver reliable but the SUNWlsimega driver still does not support the MegaRAID SATA controllers. Even though this range of hardware is no longer being produced, it is odd that it still only supports the scsi raid controllers. I assumed correctly that because LSI use a common Windows MegaRaid driver for their SCSI and SATA raid controllers (working through the windows driver configuration files) the Solaris driver would also be compatible. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] OpenSolaris 2008.11 and modified Sun LSImega driver
Hi, I use a modified Sun SUNWlsimega driver (tweaked to recognise the LSI MegaRAID SATA300-8X raid controller ) and after upgrading to Solaris 7 update 7 my computer failed to boot. As I took a backup on an external USB 1TB drive I thought I would give OpenSolaris 2008.11 a try. Booting from the CD was easy and it recognised everything except the LSI MegaRAID SATA300-8X drive, checking the system it already had the Sun LSImega driver dated 2008. How can I replace the Sun LSImega driver with the modified SUN SUNWlsimega driver? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Solaris vs HP-UX vs AIX
Hi System5, Having dealt with many customers over the years, the more astute have selected the application they wanted and then selected the OS of the selection provided by the application provider. For example, running a Database which is disk intensive on a server running anti-virus software will result in a performance penalty. In my experience, some decision makers understand this and will run their Databases only on an OS that does not require anti-virus software. Some do run there Databases on Windows but in an isolated network which includes the clients and no anti-virus. However you wanted a comparison of Solaris v HP-UX and AIX from a user perspective it should not matter. As an Administrator, installation is the important but the ease of tuning and patching I would rate as very important. From my experience patching Solaris is the easiest OS to patch, followed by HP-UX and worst by far is AIX (things may have changed since I last used AIX). When I needed to apply a patch for a specific issue on Solaris occasionally it had dependencies typically there were none, occasionally three of four and the single worst case it was easier to apply a patch cluster. For HP-UX I found that patching required at least six or more dependencies, while AIX always resulted in a CD of patches. From a tuning perspective all the OSes allowed it but I preferred the Solaris Dynamic kernel than rebuilding the kernel. I find it that odd that other Unixes have not adopted the dynamic kernel to simplify administration. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How can i forbid sftp users to change their home directory
Configure the users with /usr/bin/rksh as default shell so they will be unable to change directory. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Solaris vs HP-UX vs AIX
Hi, Having used Solaris (20+ yrs), HP-UX (10+ yrs), AIX (5+ yrs), IRIX (5+ yrs) , DEC Unix (2+ yrs), Cray OS (2+ yrs) and Linux (8+ yrs) each operating system has its own peculiarities. In my experience as a Systems Administrator you seldom get a choice over the OS you have to use, so if the company is an AIX shop then that is what you use. So one OS v another OS has a limited arena where it will have any effect. It tends to be applications driving the OS choice unless it supports multiple OSes, then performance/hardware costs become important and finally support costs. Sometimes you get a choice over the OS used because it is not imposed then you use what you are happiest using. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] could ZFS be used to replace FAT/FAT32 in removeable media
Hi, After purchasing a USB to IDE/SATA drive caddy to allow system backups, my attempt was to use a 120GB IDE drive that came out of an old PC. While changing the partition information with fdisk was straight forward, newfs'ing the disk was more of a problem as you had to enter the number of sectors. While searching for a solution, it was suggested using zfs instead and it worked really well, except for hot plugging required manual mount/remount. Given the whole nature of ZFS in terms of reliability, redundancy and availability would it be possible to Have a hot plug storage media which is automatically recognised by Solaris/ZFS and mounted automatically in a /rmedia directory (this would work with USB, Firewire hot plug devices) As ZFS does not have the limits of FAT/FAT32 and is also open source, could it be proposed to the makers of digitial devices like camera, usb memory manufacturers, router manufacturers, etc as a way of eliminating the FAT licensing yoke. This of course would require drivers to be available for Windows to allow read/write access and also speed up the time it makes the disk available for use. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Solaris 10 printer manager query
Hi, After upgrading to Solaris 10 5/08 the Solaris Printer Manager changed so that it offered the following options when adding New Attached Printer dialogue box Printer Name : Description : Printer Port: Printer Type: File Contents: Fault Notification: Options: Banner: After applying patch 138628-06 the New Attached Printer dialogue box reverted to its previous correct configuration Printer Name: Description: Printer Port: Printer Make: Printer Model: Printer Driver: Fault Notification: Banner: A friend is running Solaris 10 10/08 but despite applying 138628-06 it is not showing the extended Printer Manager functions of Make, Model and Driver. How can he enable the extended functionality. TIA -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Solaris 10 printer manager query
Hi, Problem resolved, a case of RTFM. It appears that the Make, Model and Driver options do not appear after a clean install of Solaris 10 10/08 in the Printer Manager. However, if you create a printer with a ppd interface and then delete it the options remain. example below. # lpadmin -p hp1 -v /dev/lp1 -I postscript -m standard_foomatic -n /usr/lib/lp/model/ppd/system/foomatic//HP/HP-DeskJet_950C-hpijs.ppd.gz -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Building Boost 1.38.0 on Solaris 10 5/08 x86 with Studio 12
Hi, While trying to build Stellarium 0.10.1 (not completed yet ) but I have the dependencies built now. During the process I had to build Boost v1.38.0 but it kept on failing to build. After much fiddling I have compiled Boost v1.38.0 using Studio 12 on Solaris 10 5/08 x86. The process was made possible by applying all the lastest Studio 12 compiler and Solaris patches. 1. Extract $ bunzip2 -d -c boost_1_38_0.tar.bz2 | ( cd /tmp ; gtar xf - ) $ cd /tmp/boost_1_38_0 2. Configure, installing into /opt/gnu (change as appropiate) $ ./configure --with-toolset=sun --prefix=/opt/gnu copy bjam exectuable into a directory in PATH (or build bjam seperately) $ cp ./tools/jam/src/bin.solaris/bjam PATH directory edit the user-config.jam # Boost.Build Configuration # Automatically generated by Boost configure # Compiler configuration using sun : 5.9 : /opt/SUNWspro/bin/CC : stdlibsun-stlport link-flags-library=stlport4 cxxflags ; # Python configuration using python : 2.4 : /usr ; 3. Build the libraries (32 bit) $ bjam toolset=sun stdlib=sun-stlport instruction-set=i586 address-model=32 --prefix=/opt/gnu --exec-prefix=/opt/gnu --libdir=/opt/gnu/lib --includedir=/opt/gnu/include install output ln-UNIX /opt/gnu/lib/libboost_wave-sw-mt.a ...failed updating 2 targets... ...skipped 11 targets... ...updated 8071 targets... Building 64 bit libraries, the bjam command could be as follows not tried! $ bjam toolset=sun stdlib=sun-stlport instruction-set=amd64 address-model=64 --prefix=/opt/gnu --exec-prefix=/opt/gnu --libdir=/opt/gnu/lib --includedir=/opt/gnu/include install The user-config.jam is not explicitly referenced in the bjam command so there is a possibility that it is surplus to process. Hope this helps, it was something I was looking for. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] tap interface for Solaris 10 x86 5/08 AMD64
Hi, The readme included with the tuntap driver has been updated. For more up to date information go to the forums on www.virtualbox.org -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Tried to run OpenSolaris200805
Hi, Thought that OpenSolaris 200805 would be worth giving a try on my home PC which is currently running Solaris 10 5/08. After booting from the OpenSolaris 200805, the splash screen appeared and select the first option, unfortunately everything from that point was downhill. OpenSolaris entered maintenance mode, after failing to recognise the Geforce 8600GTS (?). Is there a later version of OpenSolaris which I can download and run from cdrom without affecting my current Solaris 10 install? This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] SSL Certificate Management Tool
Hi, Has anyone considered implementing a SSL Certificate Management tool in OpenSolaris, so that the production of Self Signed and Third Party Signed Certificates can be managed via a simple user interface. Run a root, the SSL Certificate Manager would allow the full range of Certificates to be created, allowing the creation of a Master Certificate which can be used to self sign further certificates or other certificates which are externally signed. The tool would allow easy import and export of certificates. All the certificates would be stored in an encrypted file, can be defined for specific tasks HTTPS, SSL or SSH use. Selecting from a predetermined list would result in the certificate being placed in the correct location for the application selected. Run as a user, the SSL Certificate Manager would allow the user to create a certificate selecting for which purpose from a menu list which is automatically signed by the Master certificate defined by Root for that purpose. A programmatic interface would also need to be provided to allow applications to be installed and then called the Certificate Manager to create their certificates. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Lightning alarms don't work
I have problems with the Lightening 0.8 release but not with the 0.9 prelease version which can be found here. http://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/2008-06-27-03-mozilla1.8/ This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] tap interface for Solaris 10 5/08 AMD64 - Working
Hi, If you use the vnic_start.sh script previously posted you will experience duplicate ip address error messages. Remove the ifconfig tap0 ip address, the corrected script is below vnic_start.sh = #!/bin/sh tunctl -t tap0 ifconfig tap0 plumb brdgadm -a nge0 brdgadm -a tap0 ifconfig tap0 up Hope that helps This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] tap interface for Solaris 10 5/08 AMD64
Hi, Instructions for getting VirtualBox to work on Solaris 10 8/07 and Solaris 10 5/08 can be found here http://unixsadm.blogspot.com/2008/02/virtualbox-on-solaris-virtualization.html After downloading the library mentioned in the instructions above, a copy has been placed here as the later versions do not work. ftp://[EMAIL PROTECTED]/pub/sunwcslr_5.11.82-1_solaris-i386.deb This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] tap interface for Solaris 10 5/08 AMD64 - Working
When using the pre-compiled binaries, it is safer to reboot, this should result in the everything loading. I have VirtualBox v1.6 running with Tap and host connection successfully with Checkpoint's SecureClient. I created two scripts called vnic_start.sh and vnic_stop.sh which are used by VirtualBox for the creation and deletion of the tap0 interface. vnic_start.sh = = = = = = = #!/bin/sh tunctl -t tap0 ifconfig tap0 plumb ifconfig tap0 192.168.2.111 brdgadm -a nge0 brdgadm -a tap0 ifconfig tap0 up vnic_stop.sh = = = = = = = #!/bin/sh ifconfig tap0 down brdgadm -d tap0 brdgadm -d nge0 ifconfig tap0 unplumb tunctl -d tap0 My primary Network work interface is nge0 so change the script to reflect your default script. The IP address assigned in vnic_start.sh should be change to reflect your computer IP plus or minus one. The latest version of the Intel 82540EM driver requires Windows 2000 SP3 before it will install. Hope this helps. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] tap interface for Solaris 10 5/08 AMD64 - Working
Some of the posting on the VirtualBox forum advise using the Intel network adapter for Tap use. Make sure you use the latest Intel 82540EM driver available http://downloadcenter.intel.com/Product_Filter.aspx?ProductID=983lang=eng This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Problem with HP Smart Array 64xx controller on HP DL 380 G4
Hi, Checking the HP website the 6400 series is an Ultra320 SCSI controller with either 2 or 4 channels. If the card is made by LSI Logic and sold as an HP product you may be able to use an LSI driver. When you run scanpci what is the controller's vendor and product pci code? This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Fixing USB error open of /dev/rdsk/cXtXdXpX; Device busy
I have been bugged by this error message for the last four months when I inserted either my USB memory stick or digital camera (configured as usb storage). If volfs is not running then the USB memory stick is recognised correctly, I verified that the USB memory stick was working today in to other computers running Solaris 10 5/08. Apr 24 19:21:43 tesla usba: [ID 912658 kern.info] USB 2.0 device (usb90c,1000) operating at hi speed (USB 2.x) on USB 2.0 root hub: [EMAIL PROTECTED], scsa2usb4 at bus address 2 Apr 24 19:21:43 tesla usba: [ID 349649 kern.info] SMI Corporation USB DISK AA04012700703 Apr 24 19:21:43 tesla genunix: [ID 936769 kern.info] scsa2usb4 is /[EMAIL PROTECTED],0/pci15d9,[EMAIL PROTECTED],1/[EMAIL PROTECTED] Apr 24 19:21:43 tesla genunix: [ID 408114 kern.info] /[EMAIL PROTECTED],0/pci15d9,[EMAIL PROTECTED],1/[EMAIL PROTECTED] (scsa2usb4) online Apr 24 19:21:43 tesla scsi: [ID 193665 kern.info] sd4 at scsa2usb4: target 0 lun 0 Apr 24 19:21:43 tesla genunix: [ID 936769 kern.info] sd4 is /[EMAIL PROTECTED],0/pci15d9,[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 Apr 24 19:21:43 ts genunix: [ID 408114 kern.info] /[EMAIL PROTECTED],0/pci15d9,[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 (sd4) online However, volfs generated the following error :- Apr 24 19:25:56 tesla /usr/sbin/vold[1672]: [ID 848318 daemon.error] rmdisk: open of /dev/rdsk/c3t0d0p0; Device busy checking with cfgadm does not report any problems. # cfgadm Ap_Id Type Receptacle Occupant Condition c2 scsi-bus connectedconfigured unknown usb0/1 usb-hub connectedconfigured ok usb0/1.1 unknown emptyunconfigured ok usb0/1.2 unknown emptyunconfigured ok usb0/1.3 unknown emptyunconfigured ok usb0/1.4 unknown emptyunconfigured ok usb0/1.5 usb-kbd connectedconfigured ok usb0/2 usb-mouseconnectedconfigured ok usb0/3 unknown emptyunconfigured ok usb0/4 unknown emptyunconfigured ok usb0/5 unknown emptyunconfigured ok usb0/6 unknown emptyunconfigured ok usb0/7 unknown emptyunconfigured ok usb0/8 unknown emptyunconfigured ok usb0/9 unknown emptyunconfigured ok usb0/10unknown emptyunconfigured ok usb1/1 unknown emptyunconfigured ok usb1/2 unknown emptyunconfigured ok usb1/3 unknown emptyunconfigured ok usb1/4 unknown emptyunconfigured ok usb1/5 usb-storage connectedconfigured ok usb1/6 unknown emptyunconfigured ok usb1/7 unknown emptyunconfigured ok usb1/8 unknown emptyunconfigured ok usb1/9 unknown emptyunconfigured ok usb1/10unknown emptyunconfigured ok I have added the suggested fix in /kernel/drv/scsa2usb.conf but that makes no difference. The problem was volfs. If I disable volfs and run a manual mount then it works. # mount -F pcfs -o rw /dev/dsk/c3t0d0p0:c /rmdisk The mounting of dvds, cds and floppies is fine. I have vold.conf configured so that only my first dvd drive will automount, the second is configured for use with cdrecord, this works on my desktop at work with my USB memory stick. After using diff to see the difference between the vold.conf of my computer at home and work, I found the problem. # more /etc/vold.conf # ident @(#)vold.conf 1.2706/01/20 SMI # Copyright 2006 Sun Microsystems, Inc. All rights reserved. # Use is subject to license terms. # # # Volume Daemon Configuration file # # Database to use (must be first) db db_mem.so # Volfs support of removable media devices support nomedia # Labels supported label cdrom label_cdrom.so cdrom label dos label_dos.so floppy rmdisk pcmem label sun label_sun.so floppy rmdisk pcmem # Devices to use use cdrom drive /dev/rdsk/c0*s2 dev_cdrom.so cdrom%d - only 1st dvd for volfs use floppy drive /dev/rdiskette[0-9] dev_floppy.so floppy%d use pcmem drive /dev/rdsk/c*s2 dev_pcmem.so pcmem%d forceload=true use rmdisk drive /dev/rdsk/c* dev_rmdisk.so rmdisk%d- problem line # Actions eject dev/diskette[0-9]/* user=root /usr/sbin/rmmount eject dev/dsk/* user=root /usr/sbin/rmmount insert dev/diskette[0-9]/* user=root
[osol-discuss] device driver criteria
Hi, How is a device driver selected for inclusion within opensolaris? What process must the driver go through after inclusion? What is process must the driver go through for updates? This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] HP Linux Imaging and Printing for All-in-Printers - hplip.sourceforge.net
Hi, After replacing a broken HP Deskjet 895cxi printer with an HP C6280 All-in-printer the printing configuration was easy using the Ethernet connection. However accessing the Scanner component did not seem possible until visiting the HP web site and found a link to http://hplip.sourceforge.net. Is it possible to incorporate this within OpenSolaris? It would extend the number of printers supported by Solaris, provide support for the scanners (as well for use with Sane with a Sane compatible driver) and facsimile machines which are part of the All-in-one Printers. The software includes support for USB and Ethernet based connections. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] HP Linux Imaging and Printing for All-in-Printers - hplip.sourceforge.
Hi, After replacing a broken HP Deskjet 895cxi printer with an HP C6280 All-in-printer. The printing configuration was easy using the Ethernet connection. However accessing the Scanner component did not seem possible until visiting the HP web site and found a link to http://hplip.sourceforge.net. Is it possible to incorporate this within OpenSolaris? It would extend the number of printers supported by Solaris, provide support for the scanners (as well for use with Sane with a Sane compatible driver) and facsimile machines which are part of the All-in-one Printers. The software includes support for USB and Ethernet based connections. Reposted - missed the printing discussion group. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Qemu 0.8.2 v Qemu 0.9.0 v VirtualBox
After using the OpenSolaris project download of Qemu 0.8.2 (with and without Kqemu 64bit), Thoughtwave (32bit) build of Qemu 0.9.0 and VirtualBox (beta) to run Win98SE and Win2K on the same machine but sequentially (Dual Opteron 2218 with 8GB) Once VirtualBox has a full release for OpenSolaris/Solaris with audio support then it would be my preferrence for running Win98SE. Qemu 0.8.2 with Kqemu would cause Solaris 10 to freeze requiring a power off to recover. Without Kqemu being enabled then Windows 98SE would run without problem. However, Qemu would be my preference for running Win2K as I found the installation quicker, the Kqemu accelerator does improve performance. My reason for running Win98 is to run some old software which is still fit for purpose. Win2K is required for Checkpoint's SecureClient but this requires Qemu to have a unrestricted network connection, which I have attempted to get working. Providing an unrestricted network connection to virtual machines by default is not secure, but is it possible to provide OpenSolaris/Solaris with a network interface mechanism such that :- 1. Root can enable a virtual interface class and assign that class to a physical interface. 2. Root can create a instance of that virtual interface class to give an interfaceN, by default a stateful inspection firewall rule would be imposed of allowing all outgoing traffic. 3. Root can then modify or delete the firewall rule on that interfaceN, it would be useful to a predefined list of useful rules 4. Root can then use RBAC to give the a specific user RW access to interfaceN for use with the virtual machine. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Help with Qemu 0.8.2
Thanks, I have downloaded the thoughtwave build of Qemu 0.9.0 which does not appear to support kqemu as the Qemu project v0.8.2_cvs20070120_REV_2007.01.24 version does. I did find that running Win98se with kqemu accelerator enabled consistantly caused Solaris 10 8/07 to freeze completely; however Win2K worked perfectly. I built and installed the tuntap devices for Solaris from the sources here below :- http://www.whiteboard.ne.jp/~admin2/tuntap/ However, when I tried to get tunctl to build it failed with an include file errors in net/if.h ; building this should allow be to configure tap device without calling the sol_qemu_tap. Could Qemu be extended so that the tap/tun functionality is incorporated into the project, so that -net would support, for example to get unrestricted network access. -net direct,ip=X.X.X.X,subnet=Y.Y.Y.Y,hostif=interfaceN This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Help with Qemu 0.8.2
I have installed the Qemu binary package, the Kqemu and managed to get Win2K installed. It is possible to access the internet via the default DHCP configuration. Unfortunately I need to reconfigure Qemu so that it is assigned an IP address in the same network as the Solaris 10 8/07 host. I have built the sol_qemu_tap as a 64bit binary and know that I need to call the /opt/SUNWqemu/bin/64/qemu-system-x86_64 with -net tap. How do I get the tap0 device created? The host IP is 192.168.2.20, I need the Win2K to have 192.168.2.30. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Mesa 7.0.2 support in OpenSolaris
Ken makes valid points in respect of OpenGL 2.1 API. Having built open source OpenGL applications on both Solaris SPARC and x86, X86 is never as easy to build. Even when you do get everything built, I have found the OpenGL version detected is too old with Mesa I have been unable to build any OpenGL application that I wanted using the NVIDIA GL as there appears to be missing include files as detected by ./configure process. Being able to download an application source, uncompact it and then perform a simple $ CC=cc CXX=CC F77=f90 ./configure --prefix=/opt/application $ make Can the Mesa libraries also be located in /usr/X11/lib/mesa/GL this would also help when building open source applications. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Mesa 7.0.2 support in OpenSolaris
When will Mesa 7.0.2 be incorporated into OpenSolaris to provide OpenGL 2.1 support? This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] No sound with OSS on Solaris 10
Hi, I have experienced problems with OSS which appear to be related to the /dev/audio device which is linked to /devices/pseudo/[EMAIL PROTECTED]:sound,audio. So that applications which /dev/audio do not produce any sound. I used Ogle, Mplayer and XMMS which can be downloaded from blastwave.org. XMMS needs to be configured to use the Sun Audio device and not the OSS device, it will generate an error but play okay. Realplayer and Flash also work without problem. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Really only a recompile between x86 and SPARC?
Hi, I know Clearcase on Solaris SPARC is available, has IBM/Rational added Solaris x86 support and from when? Thanks This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Audio playback problems
The problem of play appears to be related to devices. In the case of Blastwave's XMMS using the liboss for output it is expecting /dev/dsp. However, running $ ossinfo -a Audio devices High Definition Audio front /dev/oss/hdaudio0/pcm0 (device index 0) High Definition Audio rear/dev/oss/hdaudio0/pcm1 (device index 1) High Definition Audio center/LFE /dev/oss/hdaudio0/pcm2 (device index 2) High Definition Audio side/dev/oss/hdaudio0/pcm3 (device index 3) High Definition Audio pcm4/dev/oss/hdaudio0/pcm4 (device index 4) High Definition Audio spdif-out /dev/oss/hdaudio0/spdout0 (device index 5) High Definition Audio rec1/dev/oss/hdaudio0/pcmin0 (device index 6) High Definition Audio rec2/dev/oss/hdaudio0/pcmin1 (device index 7) High Definition Audio spdif-in/dev/oss/hdaudio0/spdin0 (device index 8) When selecting libsolaris XMMS produces the following warning:- $ xmms ** WARNING **: solaris output: Unknown sound card type: SUNW,oss ** WARNING **: solaris output: Assuming capable of the bitstream Running a truss on gnome-cd provides the following information that it uses /dev/audioctl and /dev/audio /dev/audio links to /devices/pseudo/[EMAIL PROTECTED]:sound,audio /dev/audioctl links to /devices/pseudo/[EMAIL PROTECTED]:sound,audioctl The sadasupport device is created by the OSS driver, the truss is indicating no errors of failing to write to the /dev/audio or /dev/audioctl devices. So the error may be in the driver. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Audio playback problems
When I run /usr/dt/bin/sdtaudiocontrol and select View - Status, then use Sound Recorder to play back bark.au then Audio Control Status reflects the playing of the bark.au file. When I change the Volume setting (lower right hand corner) the change is immediately reflected in the Audio Control Playback Volume. Changing the Playback Volume setting similarly changes the Volume control in the lower right hand corner. However Sound Recorder completely ignores this, running File - Mixer and attempting to alter the volume this way has no effect. Similarly /usr/dt/bin/sdtaudio ignores the Volume setting as well (in fact the volume control within sdtaudio also has no effect. I have looked in /usr/bin and /usr/dt/bin and have not spotted the Motif cd player. I have installed XMMS, the cd plays but no audio. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Audio playback problems
Hi, Finally got cd playing to work. I had to pkg-get -i xmms from www.blastwave.org then configure xmms not to use the liboss library for output but the libsolaris accessible via preferences. I also had to remove /cdrom/cdrom0 from the directory setting as this link did not exist. When inserting an audio cd into a drive, should the /cdrom/cdrom0 link exist and should the directory contain the list of tracks on the cd? Could this be configured to happen so the tracks appear as either track.cda or the appropiate track name via the cddabase. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Audio playback problems
Hi, I am running Solaris 10 8/07 (64bit operation) on a PC using Supermicro H8DAE-2 motherboard with the OSS v4.0-1012 driver connected to Harman/Kardon 2.1 speakers, with Optiarc DVD RW AD-7170S firmware v1.00 drive connected to SATA0. 1) Not all Audio play back programs honour the volume setting of the Volume Control in the bottom right hand corner of the Java Desktop Interface. ie RealPlayer v10.0.9.1204 does honour volume setting CSWogle does not honour volume setting Sound Recorder playing back audio files does not honour volume setting 2) When attempting to play back CDs using the CD Player the CD is recognised and you can select play, but no audio is heard. 3) When attempting to play back CDs or DVDs using /usr/sfw/bin/Totem then I get the following error message An error occured Could not determine type of stream. Examining /vol/dev/aliases/cdrom0 is a link to /vol/dev/rdsk/c0t0d0/audio_cd when playing CDs This would indicate that the disk is identifed as an audio disk but the reading of the cd results in a corrupted stream. Is the volume issue related to the OSS driver or to the application or both? Is there a patch which would fix the playback of audio cds for either CD Player or Totem? TIA This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Really only a recompile between x86 and SPARC?
Hi, A couple of years ago I witnessed the building and testing of a Solaris SPARC application which was recompiled on Solaris x86 using an Studio 10 beta release. The most difficult problem was the extraction of the files required for building (Clearcase was the Source Code Management system and it did not support MVFS on Solaris x86 - Has this changed?). Due to this difficulty with 3rd Party Libraries only a portion of the code was extracted for the Solaris x86 build. The next problem was modifying the Build Flags so that 32 and 64 bit builds (-xarch=amd64 for example). Once changed the Solaris x86 build was easy as entering jam. Performance was superb, it was the quickest version of the software on 32 or 64 bit when compared on the same hardware. So, it you are using a Source Management System which fully supports Solaris x86 then it should be a simple recompile if you are already producing software for different oses. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Building QT-4.3.3 with OpenGL enabled
How do you specify the -I include for the Mesa directory so that the build can take place, as it automatically appends GL/include file . eg GL/gl.h GL/glu.h Attempting to build with the NVIDIA include indicates the file is not present it looks for GL/glu.h which is not provided. If NVIDIA provides its include files in /usr/X11/include/NVIDIA/GL and the you specify the include directory as -I/usr/X11/include/NVIDIA, then surely the Mesa include should follow the same convention of -I/usr/X11/include/mesa, the #include GL/glu.h is added. This would mandate the Mesa include files to be in a /usr/X11/include/mesa/GL directory and not /usr/X11/include/mesa. A minor inconvenience to programmers who are constantly developing and building code in their build environment and are use to the idiosyncrasy of the OpenSolaris/Solaris. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Building QT-4.3.3 with OpenGL enabled
Hi, When I try to build Qt-4.3.3 it fails as it requires OpenGL v1.2.1 or later but it also complains that the GL/glu.h is missing. Qt tests if OpenGL can be compiled in automatically, running the test in config.tests/x11/opengl when building with NVIDA and Mesa the results are below:- $ CC=cc CXX=CC F77=f90 ./configure --prefix=/opt/gnu -I/usr/X11/include/NVIDIA -L/usr/X11/lib/NVIDIA $ cd /tmp/qt-x11-opensource-src-4.3.3/config.tests/x11/opengl $ make CC -c -O2 -I../../../mkspecs/solaris-cc -I. -I/usr/X11/include/NVIDIA -I/usr/openwin/share/include -I/usr/openwin/share/include -I. -I/usr/sfw/include -o opengl.o opengl.cpp opengl.cpp, line 2: Error: Could not open include fileGL/glu.h. opengl.cpp, line 5: Error: #error Required GLU version 1.2 not found.. make: *** [opengl.o] Error 1 $ cd /tmp/qt* $ gmake confclean $ CC=cc CXX=CC F77=f90 ./configure --prefix=/opt/gnu -I/usr/X11/include/mesa -L/usr/X11/lib/mesa $ cd /tmp/qt-x11-opensource-src-4.3.3/config.tests/x11/opengl $ make CC -c -O2 -I../../../mkspecs/solaris-cc -I. -I/usr/X11/include/mesa -I/usr/openwin/share/include -I/usr/openwin/share/include -I. -I/usr/sfw/include -o opengl.o opengl.cpp opengl.cpp, line 1: Error: Could not open include fileGL/gl.h. opengl.cpp, line 2: Error: Could not open include fileGL/glu.h. opengl.cpp, line 5: Error: #error Required GLU version 1.2 not found.. make: *** [opengl.o] Error 1 Fixing /usr/X11/include/mesa by adding GL dir and copying files as root then trying make again $ su # cd /usr/X11/include/mesa # mkdir GL # chgrp bin GL # cp -p * GL # exit $ make CC -c -O2 -I../../../mkspecs/solaris-cc -I. -I/usr/X11/include/mesa -I/usr/openwin/share/include -I/usr/openwin/share/include -I. -I/usr/sfw/include -o opengl.o opengl.cpp CC -R/usr/lib -R/opt/gnu/lib -R/opt/gnu/lib -o opengl opengl.o -L/usr/sfw/lib -L/usr/openwin/lib -L/usr/X11/lib/mesa -L/usr/openwin/lib -lGL -lGLU -lXext -lX11 -lresolv -lsocket -lnsl Qt-4.3.3 will compile with OpenGL using MESA, however NVIDIA GL will still fail. Can NVIDIA be persuaded to fix the include files? This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Building QT-4.3.3 with OpenGL enabled
Hi, After the fixing the Mesa GL include problem, Qt-4.3.3 autodetects OpenGL, then building Qt takes a while. Once installed I tried to run $ qtdemo ld.so.1: qtdemo: fatal: libXrender.so.1: open failed: No such file or directory Killed $ echo $LD_LIBRARY_PATH :/usr/openwin/lib:/opt/gnu/lib $ LD_LIBRARY_PATH=:/usr/openwin/lib:/usr/openwin/sfw/lib:/usr/sfw/lib:/opt/gnu/lib:/usr/X11/lib/mesa ; export LD_LIBRARY_PATH $ qtdemo application runs This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Building QT-4.3.3 with OpenGL enabled
Hi, While Qtdemo does run, not all the demos run fully due to the limitations of the Mesa library. Getting NVIDIA to provide the correct include and library files. It would be also useful if the location of the libraries could be standardised into /usr/X11/lib. I hope now to build Stellarium 0.9.0 as it was the Qt OpenGl that was stopping me. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Building QT-4.3.3 with OpenGL enabled
Hi Alan, I know setting LD_LIBRARY_PATH can break applications but that was the quickest way to get qtdemo to find the libraries in /usr/openwin/sfw/lib. Should I need to write a wrapper script to set the environment to run the qtdemo? Maybe if the X library locations can be rationalised to /usr/X11/lib then it would not be necessary. Has the /usr/X11/include/mesa/GL directory fix already been applied to OpenSolaris? It would be great to be able to use the NVIDIA GL but many of the include files are not supplied to offer full Qt + OpenGL functionality so all the Qt demo OpenGL demos would run completely. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Building QT-4.3.3 with OpenGL enabled
Hi, I have been trying to build Qt-4.3.3-open-source (without OpenGL there is no problem) with OpenGL support. As I have a Geforce 8600 card and using the NVIDIA-Solaris-x86-169.07 driver, I thought it would be relatively easy on Solaris 10 8/07 which I know is an old build. Have the problems I have been experiencing been resolved in OpenSolaris? The NVIDIA drivers have include files in /usr/X11/include/GL and /usr/X11/include/NVIDIA/GL gl.h (opengl 1.1), glext.h (opengl 1.2.1), glx.h (v1.2), glxext.h (v1.2.1). When building qt-4.3.3 as follows (which requires a minimum of OpenGL v1.2.1): CC=cc CXX=CC F77=f90 ./configure --prefix=/opt/gnu -I/usr/X11/include/NVIDIA -L/usr/X11/lib/NVIDIA The #include GL/gl.h appends the /usr/X11/include/NVIDIA/ with GL/gl.h and finds the files, however with the Mesa option this can not work as the mesa library does not contain a GL subdirectory ie. CC=cc CXX=CC F77=f90 ./configure --prefix=/opt/gnu -I/usr/X11/include/mesa -L/usr/X11/lib/mesa The #include GL/gl.h appends the /usr/X11/include/mesa with GL/gl.h but the actual file is located in /usr/X11/include/mesa/gl.h but it should be /usr/X11/include/mesa/GL/gl.h This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Replacing NIS with LDAP
Is working being completed to make ldap on opensolaris as easy to use as it is on windows? I noted that windows ad can record your drink preference but that is going a little too far. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
