[osol-discuss] kde 4 on opensolaris
Hi all, I'm trying to install kde4 on a solaris machine (running thru virtual box) but I got the following error that I don't know how to fix: l...@opensolaris:~$ pfexec pkg install KDEbase-apps KDEgdm-integration Creating Plan - pkg: Vincoli violati dai seguenti pacchetti: Package pkg:/sunwgnome-me...@0.5.11,5.11-0.121 conflicts with constraint in installed pkg:/entire: Pkg SUNWgnome-media: Optional min_version: 0.5.11,5.11-0.111 max version: 0.5.11,5.11-0.111 defined by: pkg:/entire The opensolaris is 2009.06. Anyone has a suggestion on how to solve it? Thanks, Luca ___ 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
Re: [osol-discuss] kde 4 on opensolaris
Hi Luca, did you try to install from a repository, that was built on 200906 and not dev-121? Another option would be to image-update to build 121 from the /dev repository. hnhn Luca Ferrari wrote: Hi all, I'm trying to install kde4 on a solaris machine (running thru virtual box) but I got the following error that I don't know how to fix: l...@opensolaris:~$ pfexec pkg install KDEbase-apps KDEgdm-integration Creating Plan - pkg: Vincoli violati dai seguenti pacchetti: Package pkg:/sunwgnome-me...@0.5.11,5.11-0.121 conflicts with constraint in installed pkg:/entire: Pkg SUNWgnome-media: Optional min_version: 0.5.11,5.11-0.111 max version: 0.5.11,5.11-0.111 defined by: pkg:/entire The opensolaris is 2009.06. Anyone has a suggestion on how to solve it? Thanks, Luca ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org -- Jan Hnatek jan.hna...@sun.com ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [belenix-discuss] log failed login attempts
On Thu, 2009-10-08 at 18:16 +0530, Arun Tomar wrote: Hi! i was trying to log the failed login attempts to my opensolaris box and i tried the methods specified in the book, OpenSolaris bible page 421, In short this is what it says, To enable failed login log, first add the following lines to /etc/default/login: SYSLOG=YES SYSLOG_FAILED_LOGINS=0 edit: /etc/syslog.conf auth.notice /var/adm/authlog touch /var/adm/authlog ls -l /var/adm/authlog chmod 600 /var/adm/authlog chgrp sys /var/adm/authlog ls -l /var/adm/authlog svcadm refresh system-log but i get the following error and nothing gets logged into /var/adm/authlog Oct 8 07:49:59 opensolaris syslogd: line 42: unknown priority name notice /var/adm/authlog Oct 8 07:49:59 opensolaris syslogd: line 48: WARNING: loghost could not be resolved Oct 8 08:55:08 opensolaris oss_sadasupport: [ID 517056 kern.warning] WARNING: ldi_open_by_name(/dev/dsp) failed, errno=19 Oct 8 08:55:15 opensolaris last message repeated 1 time Oct 8 18:08:10 opensolaris syslogd: line 42: unknown priority name notice /var/adm/authlog Oct 8 18:08:10 opensolaris syslogd: line 48: WARNING: loghost could not be resolved please help. regds, Arun Tomar. ___ belenix-discuss mailing list http://mail.opensolaris.org/mailman/listinfo/belenix-discuss http://groups.google.com/group/belenix-discuss WARNING: loghost could not be resolved. Check your /etc/hosts, must be 127.0.0.1 localhost loghost -- ::alhazred ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] kde 4 on opensolaris
On Thursday 08 October 2009 02:04:14 pm Jan Hnatek's cat walking on the keyboard wrote: Hi Luca, did you try to install from a repository, that was built on 200906 and not dev-121? Another option would be to image-update to build 121 from the /dev repository. Well, actually I followed instructions here http://techbase.kde.org/Projects/KDE_on_Solaris/OpenSolaris Moreover, I've got the repository bionicmutton in the package manager but I cannot find any kde package. Can you please give me more info about which repository to use? Thanks, Luca ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [belenix-discuss] log failed login attempts
On Thu, 2009-10-08 at 18:57 +0530, Arun Tomar wrote: auth.notice /var/adm/authlog Verify that /etc/syslog.conf uses Tab and not whitespaces in new line -- ::alhazred ___ 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] Dresden Conference
Uros, I would go but I will have to present a speech at OSC in Tokyo on the end of this month. I saw you will give a speech there I hope you will succeed in presentation. -masafumi On 2009/10/08, at 8:29, Uros Nedic wrote: Does anyone out of Europe comes to Dresden? (USA, China, India people?) Uros --- Every kind of peaceful cooperation among men is primarily based on mutual trust and only secondarily on institutions such as courts of justice and police. - Albert Einstein (1879 - 1955) Windows Live: Make it easier for your friends to see what you’re up to on Facebook.___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org Masafumi Ohta a Leader of Tokyo OpenSolaris User Group mailto:masafumi.o...@gmail.com http://www.twitter.com/masafumi_ohta ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] log failed login attempts
Hi! i was trying to log the failed login attempts to my opensolaris box and i tried the methods specified in the book, OpenSolaris bible page 421, In short this is what it says, To enable failed login log, first add the following lines to /etc/default/login: SYSLOG=YES SYSLOG_FAILED_LOGINS=0 edit: /etc/syslog.conf auth.notice /var/adm/authlog touch /var/adm/authlog ls -l /var/adm/authlog chmod 600 /var/adm/authlog chgrp sys /var/adm/authlog ls -l /var/adm/authlog svcadm refresh system-log but i get the following error and nothing gets logged into /var/adm/authlog Oct 8 07:49:59 opensolaris syslogd: line 42: unknown priority name notice /var/adm/authlog Oct 8 07:49:59 opensolaris syslogd: line 48: WARNING: loghost could not be resolved Oct 8 08:55:08 opensolaris oss_sadasupport: [ID 517056 kern.warning] WARNING: ldi_open_by_name(/dev/dsp) failed, errno=19 Oct 8 08:55:15 opensolaris last message repeated 1 time Oct 8 18:08:10 opensolaris syslogd: line 42: unknown priority name notice /var/adm/authlog Oct 8 18:08:10 opensolaris syslogd: line 48: WARNING: loghost could not be resolved please help. regds, Arun Tomar. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [belenix-discuss] log failed login attempts
On Thu, 2009-10-08 at 16:51 +, Alexander Eremin wrote: On Thu, 2009-10-08 at 18:16 +0530, Arun Tomar wrote: Hi! i was trying to log the failed login attempts to my opensolaris box and i tried the methods specified in the book, OpenSolaris bible page 421, In short this is what it says, To enable failed login log, first add the following lines to /etc/default/login: SYSLOG=YES SYSLOG_FAILED_LOGINS=0 edit: /etc/syslog.conf auth.notice /var/adm/authlog touch /var/adm/authlog ls -l /var/adm/authlog chmod 600 /var/adm/authlog chgrp sys /var/adm/authlog ls -l /var/adm/authlog svcadm refresh system-log but i get the following error and nothing gets logged into /var/adm/authlog Oct 8 07:49:59 opensolaris syslogd: line 42: unknown priority name notice /var/adm/authlog Oct 8 07:49:59 opensolaris syslogd: line 48: WARNING: loghost could not be resolved Oct 8 08:55:08 opensolaris oss_sadasupport: [ID 517056 kern.warning] WARNING: ldi_open_by_name(/dev/dsp) failed, errno=19 Oct 8 08:55:15 opensolaris last message repeated 1 time Oct 8 18:08:10 opensolaris syslogd: line 42: unknown priority name notice /var/adm/authlog Oct 8 18:08:10 opensolaris syslogd: line 48: WARNING: loghost could not be resolved please help. regds, Arun Tomar. ___ belenix-discuss mailing list http://mail.opensolaris.org/mailman/listinfo/belenix-discuss http://groups.google.com/group/belenix-discuss WARNING: loghost could not be resolved. Check your /etc/hosts, must be 127.0.0.1 localhost loghost hi! Ive added the loghost to the /etc/hosts, now the warning is gone, but the error persists. Oct 8 18:43:25 opensolaris syslogd: line 42: unknown priority name notice /var/adm/authlog Oct 8 18:45:06 opensolaris syslogd: line 42: unknown priority name notice /var/adm/authlog output of my /etc/syslog.conf # i saw that auth.notice is already present on the line below by default #but it still whether it's there or not it doesn't log the messages. #*.err;kern.notice;auth.notice /dev/sysmsg *.err;kern.notice /dev/sysmsg *.err;kern.debug;daemon.notice;mail.crit/var/adm/messages *.alert;kern.err;daemon.err operator *.alert root *.emerg * auth.notice /var/adm/authlog # if a non-loghost machine chooses to have authentication messages # sent to the loghost machine, un-comment out the following line: #auth.noticeifdef(`LOGHOST', /var/log/authlog, @loghost) mail.debug ifdef(`LOGHOST', /var/log/syslog, @loghost) # # non-loghost machines will use the following lines to cause user # log messages to be logged locally. # ifdef(`LOGHOST', , user.err/dev/sysmsg user.err/var/adm/messages user.alert `root, operator' user.emerg * ) arun ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] not able to create vnic over wlan card
hi! i was trying to create vnic over my wifi card so that i can use it with virtualbox for further networking etc, but failed, any help is appreciated. a...@opensolaris:~# dladm show-phys LINK MEDIASTATE SPEED DUPLEXDEVICE rum0 WiFi up 48 unknown rum0 rge0 Ethernet unknown0 unknown rge0 vboxnet0 Ethernet unknown0 unknown vboxnet0 a...@opensolaris:~# dladm show-link LINKCLASSMTUSTATEOVER rum0phys 1500 up -- rge0phys 1500 unknown -- vboxnet0phys 1500 unknown -- a...@opensolaris:~# dladm create-vnic -l rum0 r1 dladm: vnic creation over rum0 failed: operation not supported arun. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [belenix-discuss] not able to create vnic over wlan card
On Thu, Oct 8, 2009 at 7:12 PM, Arun Tomar tomar.a...@gmail.com wrote: hi! i was trying to create vnic over my wifi card so that i can use it with virtualbox for further networking etc, but failed, any help is appreciated. a...@opensolaris:~# dladm show-phys LINK MEDIA STATE SPEED DUPLEX DEVICE rum0 WiFi up 48 unknown rum0 rge0 Ethernet unknown 0 unknown rge0 vboxnet0 Ethernet unknown 0 unknown vboxnet0 a...@opensolaris:~# dladm show-link LINK CLASS MTU STATE OVER rum0 phys 1500 up -- rge0 phys 1500 unknown -- vboxnet0 phys 1500 unknown -- a...@opensolaris:~# dladm create-vnic -l rum0 r1 dladm: vnic creation over rum0 failed: operation not supported I do not think wifi interfaces are yet supported for VNICs. See: http://opensolaris.org/jive/thread.jspa?messageID=337539 Regards, Moinak. -- http://www.belenix.org/ http://moinakg.wordpress.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] about htdocs directory on home web server
I just want to make sure I'm not doing something that will cause grief somewhere. First understand that this is all happening on a home lan protected by a firewall/router... with NO http server visible from the internet. I want to put the apache2 htdocs directory on a different zpool than rpool. And make it available to all home lan machines via nfs and maybe smb too. As well as available via apache of course. I plan to setup a subversion server under htdocs for a web development project I have. And expect to read/write files in module checked from subversion, also under htdocs To set it up: I thought I'd just empty existing htdocs to tmpdir since I haven't setup much of anything... rsync avv [...]/htdocs /some/tmpdir rm -rf [...]/htdocs then create a zfs file system like: zfs create somezfs/htdocs And mount it where htdocs used to be zfs set mountpoint=/var/apache2/2.2/htdocs somezfs/htdocs turn on nfs zfs set sharenfs=on somezfs/htdocs And maybe smb too: zfs set sharesmb=on somezfs/htdocs zfs set sharesmb=name=`hostname_htdocs` somezfs/htdocs And finally copy everything back to the mounted htdocs. rsync -avv /some/tmpdir/ [...]/htdocs/ rm -rf /some/tmpdir/ Is this a seriously bad idea... if not. I imagine it will need some different settings... in httpd.conf which I could also use some advice on. I'm thinking about files being written from different local machines and making sure apache will serve them without permissions errors. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] about htdocs directory on home web server
I wouldn't recommend messing with moving and linking htdocs. Just change your DocumentRoot setting in the apache httpd.conf file to point to the directory you want to use. -- Alan Harry Putnam wrote: I just want to make sure I'm not doing something that will cause grief somewhere. First understand that this is all happening on a home lan protected by a firewall/router... with NO http server visible from the internet. I want to put the apache2 htdocs directory on a different zpool than rpool. And make it available to all home lan machines via nfs and maybe smb too. As well as available via apache of course. I plan to setup a subversion server under htdocs for a web development project I have. And expect to read/write files in module checked from subversion, also under htdocs To set it up: I thought I'd just empty existing htdocs to tmpdir since I haven't setup much of anything... rsync avv [...]/htdocs /some/tmpdir rm -rf [...]/htdocs then create a zfs file system like: zfs create somezfs/htdocs And mount it where htdocs used to be zfs set mountpoint=/var/apache2/2.2/htdocs somezfs/htdocs turn on nfs zfs set sharenfs=on somezfs/htdocs And maybe smb too: zfs set sharesmb=on somezfs/htdocs zfs set sharesmb=name=`hostname_htdocs` somezfs/htdocs And finally copy everything back to the mounted htdocs. rsync -avv /some/tmpdir/ [...]/htdocs/ rm -rf /some/tmpdir/ Is this a seriously bad idea... if not. I imagine it will need some different settings... in httpd.conf which I could also use some advice on. I'm thinking about files being written from different local machines and making sure apache will serve them without permissions errors. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Iscsi target setup on 2009.06
I'm a totally new user to solaris and opensolaris and I'm sure that these are pretty naive questions. I have been playing with ZFS and would like to try setting up a zfs pool as an iscsi target. Can someone point me to documentation that might get me started? I have tried a few things, but simple things like the iscsitadm not existing have me confused. Also, it looks like COMSTAR is going to replace some older infrastructure--it isn't clear where that stands and trying to activate anything COMSTAR-related using svcs and svdadm shows no svc available. Thanks, Sean ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] about htdocs directory on home web server
Alan Steinberg alan.steinb...@sun.com writes: I wouldn't recommend messing with moving and linking htdocs. Just change your DocumentRoot setting in the apache httpd.conf file to point to the directory you want to use. That makes sense... but what about the rest.. I mean offering the htdocs on nfs and smb for example. Does that lead to complications with permissions? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Iscsi target setup on 2009.06
Here is a simple way to get going: http://wikis.sun.com/display/OpenSolarisInfo200906/How+to+Configure+iSCSI+Target+Ports Here are my notes to myself when I upgrade to 2009.06. I am a relative newbie too, so if these instructions don't work or make sense, I'll try to clarify. In many places I have used my own names, so replace with your own as you come across them. The man pages are good references too, as well as the links off of the wiki page above. Finally, I use 'sudo' below, but 'pfexec' is a little easier, and from what I understand, more 'correct' for solaris. There are four steps to managing iSCSI in COMSTAR. 1. Create the backing store, 2. Create a LUN pointing to the store, 3. Create the iSCSI target, 4. connect the LUN to the initiator using a view. Note - usually one target is sufficient for all iscsi requests. Views will present different LUNs to different initiators over the same target. But first, disable the old iscsi target daemon, and enable the iscsi transport 1. sudo svcadm disable iscsitgt 2. sudo svcadm enable stmf The four steps: 1. sudo zfs create -s -V 5t data01/san/gallardo/g (the -s makes it thin, -V specifies a block volume) 2. sbdadm create-lu /dev/zvol/rdsk/data01/san/gallardo/g 3. sudo itadm create-target 4. sudo stmfadm add-view 600144F0E24785004A80910A0001 (don't do this! It will happen later as the last step, step 5 below. This command will create a view that allows any initiator to see this LUN - bad security) Access to this LUN will be specified using Host Groups and Target Groups. Host Groups group hosts together that need to access the same resources. Target Groups group export the same views to the same set of Host Groups. E.g., a single server could be in a host group. A target group could hold a single view/LUN destined for that single server. The target group would then allow the host group access. 1. sudo stmfadm create-hg HG-Gallardo (create the host group) 2. sudo stmfadm add-hg-member -g HG-Gallardo iqn.1991-05.com.microsoft:gallardo.aerospace.craneae.com (add a host into the group) 3. sudo stmfadm create-tg TG-Gallardo (create the target group) 4. sudo stmfadm add-tg-member -g TG-Gallardo iqn.1986-03.com.sun:02:49d108b8-2aca-e000-f3d7-8f35e46689df (add the OpenSolaris iSCSI target to the target group) 5. sudo stmfadm add-view -h HG-Gallardo -t TG-Gallardo -n 0 600144F0E24785004A80910A0001 (setup a view, connecting host group HG-Gallardo with target group TG-Gallardo to the LUN starting with 60014...) Nice levels of abstraction, but maybe a little too abstract? -Scott -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Is there a driver for Marvell?
I am using Solaris on one machine and looking at using opensolaris on another, just can't get enough of this Sun stuff. The reason I do not have opensolaris is the fact that I could not find a driver for my ethernet. It is a Marvell 88E8056 PCI-E gigabyte Rev(13). Does anyone know if there is a driver for opensolaris and marvell? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Is there a driver for Marvell?
On Thu, Oct 8, 2009 at 8:49 PM, Larry Robinson lark...@aol.com wrote: I am using Solaris on one machine and looking at using opensolaris on another, just can't get enough of this Sun stuff. The reason I do not have opensolaris is the fact that I could not find a driver for my ethernet. It is a Marvell 88E8056 PCI-E gigabyte Rev(13). Does anyone know if there is a driver for opensolaris and marvell? -- It looks like there was a relevant putback a few weeks ago... http://hg.genunix.org/onnv-gate.hg/rev/fa1b0b185963 The tag for build 124 of ON came 3 days later... http://hg.genunix.org/onnv-gate.hg/tags And the latest in the dev branch seems to be build 124... http://pkg.opensolaris.org/dev/info/0/entire%400.5.11%2C5.11-0.124%3A20090925T222419Z -- Mike Gerdts http://mgerdts.blogspot.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] bluetooth project
It would be a shame to put this on holdso many ways that this will displease users: - Bluetooth mice - phone sync - phone/hsdpa modem - bluetooth printing IMHO these things missing will push users away from OpenSolaris On Thu, Oct 8, 2009 at 14:38, Michael Li mikore...@sun.com wrote: Robert Milkowski wrote: Michael Li wrote: Dear all, No bluetooth feature will be introduced into build125. If you think any Bluetooth function is important or must support, please file RFE to http://defect.opensolaris.org/bz with good judgment. That's the most expected voice from development team's point of view, before putting much more resources onto bluetooth project. Does it mean the project is on-hold or are you still actively working on it and would like to get extra resource? I'm just curious... It's almost on-hold, see: http://www.opensolaris.org/jive/thread.jspa?threadID=113271tstart=15 Thanks, Michael ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Problem on boot
I have opensolaris on virtualbox, I installed well, no problem, ran it well, and all that stuff, but suddenly when I boot solaris only boot me on console mode. The loading splash appears, then when it finish to load, send me to the console mode. I logged in, then typed su -, then tried metacity --replace and shows me an error Window manager error: Unable to open X display i don't know how to repair it. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
