Re: [osol-discuss] Any Rsync GUI's pre-compiled for OI-151
Hi Jeff, Jeff Goldrich píše v so 13. 08. 2011 v 19:50 -0400: I'm using Rsync for backup between OI-151 and SolarisExpress 11. I'm not very good at troubleshooting the error messages I get when trying to compile the various front ends ie Grsync, Qsync, Luckybackup etc. They all fail for different reasons which is beyond my scope of understanding. I've tried to trouble shoot with google but did not get very far in each case. Are there any of these Rsync GUI's ready to go or pre-compiled for Opensolaris? for Solaris 11 Express there is grsync available from http://pkg.opensolaris.cz/s11e/en/index.shtml Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] django in solaris 11 express?
Hi, Jyri J. Virkki píše v čt 24. 03. 2011 v 00:39 -0700: Once upon a time solarg wrote: hello all, actually, all my web servers are under opensolaris b134. I haven't upgraded to solaris 11 express yet... I discovered django on ubuntu, and i'm wondering if it is realistic to try to install all the dependances on opensolaris/solaris11 machine with a minimum of pain? currently, there is an older release of django here: http://pkg.opensolaris.org/webstack/en/catalog.shtml 1.0 instead of 1.2 (and since yesterday, 1.3) The Web Stack project was killed so that may never get updated. Looks like the build sources are still available, in case it helps you build a more recent one: http://src.opensolaris.org/source/xref/webstack/django/ there is more fresh version available from http://pkgbuild.sourceforge.net/spec-files-extra/ Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] intel wifi link 1000 driver
Hi Timmy, Timmy Ewell píše v čt 02. 12. 2010 v 14:51 -0800: Hello again. Just to clarify, I've been researching the answer for the last several months. I'm guessing the card is too new for Intel to release the source for the driver and the iwlwifi project is a work around. I normally don't post in forums for help because i know how particular communities can be about newbies (I used ArchLinux for my longest stint with distros). Posting in forums is usually my last resort so i can try and teach myself. Some help is all i'm looking for. Shawn Walker is correct, your wifi is not supported now. Could you fill RFE on bugs.opensolaris.org requesting such driver, please? Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Problem with Logitech G9 mouse
Hi, Dmitry G. Kozhinov píše v út 07. 12. 2010 v 13:28 -0800: What is the root password when i boot from live CD? opensolaris On S11e it is solaris. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Problem with Logitech G9 mouse
oHi, john kroll píše v so 27. 11. 2010 v 14:13 -0800: and can't work in 151a? What was changed? I've had opensolaris 2009.06,openindiana,korona 4.4.5,and snv130 all installed and working in three different machines in multi-boot situation. None will even boot up solaris 11 express live on cd. Error 25 on all didn't have time to look at other stuff or run any diagnostics yet but md5 check was correct. I do not know how your reply is connected with problem of not working mouse Logitech G9. I would recommend to start new thread and supply more info. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Problem with Logitech G9 mouse
Hi, user124 píše v so 27. 11. 2010 v 12:22 -0800: I'm very disappointed with solaris. Version 151a and problem with Logitech mouse... The question is: why my mouse worked fine in 111b and can't work in 151a? What was changed? Many things changed, many fixes done, new features added. And few new bugs introduced probably. Sorry, crystal balls are not available. It would be much better to send info as suggested by John Martin, otherwise we can only guess. It should not be hard for you to boot from 111b live cd, should it? Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] System always hits dns
Hi Mike, Mike Gerdts píše v pá 05. 11. 2010 v 13:06 -0500: On Fri, Nov 5, 2010 at 12:22 PM, Milan Jurik milan.ju...@oracle.com wrote: Hi, Mike Gerdts píše v pá 05. 11. 2010 v 12:10 -0500: It is trying to do an IPv6 lookup (via ipnodes) before trying an IPv4 lookup (via hosts). Since you probably aren't using IPv6, you can get the desired behavior with: hosts: files nis dns ipnodes: files such config is really bd idea. Keep them in sync from Solaris 10 releases. Can you elaborate? E.g. double parsing of flat file before going to DNS? If IPv6 is not in use, having ipnodes go to DNS does little other than cause unnecessary DNS requests that will always fail. My observation is that the times that you notice it is failing are those times where it causes a really long timeout to be invoked. In correctly set environment DNS server will not timeout for records requests. There are cases where such config will bring something good but only in rare cases it is not hiding some real setup problem. There is still not clear why with common setup of hosts/ipnodes he does not see effect of nscd cache and queries going to DNS even if needed data are in files. Still, ipnodes are not obsolete because if you query only hosts database, DNS backend will generate only query only fo A record, in case of ipnodes, it will generate both (so your workaround will work). Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] System always hits dns
Hi, Mike Gerdts píše v pá 05. 11. 2010 v 12:10 -0500: It is trying to do an IPv6 lookup (via ipnodes) before trying an IPv4 lookup (via hosts). Since you probably aren't using IPv6, you can get the desired behavior with: hosts: files nis dns ipnodes: files such config is really bd idea. Keep them in sync from Solaris 10 releases. Releases of Solaris/OpenSolaris later than what you appear to be running know how to look up IPv6 addresses via hosts as well. That is, ipnodes in nsswitch.conf becomes obsolete. Not at all. Anyway, I would check these things: /etc/hosts - ./inet/hosts /etc/inet/ipnodes - ./hosts aka - are both flat files pointing on the same file in /etc/inet/hosts --- Mike DeMarco píše v pá 05. 11. 2010 v 10:12 -0700: Even though nscd is running with the default ttl a ssh to the same host within a minute is still going out and hitting DNS. nscd is respecting DNS TTLs. Also check nscd.conf And use dtrace on nscd, check if nss_files functions are called and what they return. Best regards, Milan Mike On Fri, Nov 5, 2010 at 12:03 PM, Mike DeMarco mikej...@yahoo.com wrote: Build 134 My nsswitch.conf file is setup as such hosts files nis dns ipnodes files nis dns when snooping the interface I see dns lookups even though the ipaddress lives in the local host file and or the nis database. It was a very early problem with nsswitch that it would still follow through with requests even though they were satisfied with the prior request. I tried to limit it going out to the next resource if the current one was found with hosts: files [SUCCESS=return] nis [SUCCESS=return] dns ipnodes:files [SUCCESS=return] nis [SUCCESS=return] dns But still every request goes to dns no matter what it finds in the files database or nis database. Waiting for a dns timeout on every ssh to a host that is not in dns is a killer. Anyone seen this behavior and have input. Thanks -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org -- Mike Gerdts http://mgerdts.blogspot.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Merge other distros to OpenIndiana?
Hi, On 16.09.10 19:18, Jason wrote: I think part of that was the rather excessive amount of work just to get a usable build environment to be able to do that, Installation of SXCE or OSol and running one script was the rather excessive amount of work? Even before the script for installing SFE CBE existed, it needed only few steps to do it manually. or in the case of jucr, its incredible opaqueness which made doing anything with it incredibly painful (I finally gave up myself). If you make things hard (or take a lot more effort) for people that weren't on SWAN to do anything, it shouldn't be surprising no one else did anything... spec-files-extra has nothing to do with SWAN. You can ask those who were participating on it externally for years. Hopefully OpenIndiana is able to address those issues. Well, as I see spec-files-extra imported to Illumos, I hope they will contribute back to it and participate on it more and more. For last couple of years I was hearing mostly excuses from both sides. But for SFE the excuses from non-SUN people were invalid. SUN was not controlling it and it was purely community work. Still the most of work was/is done by SUN employees... Best regards, Milan On Thu, Sep 16, 2010 at 12:01 PM, Calum Bensoncalum.ben...@oracle.com wrote: On 16 Sep 2010, at 14:04, Ashish Nabira wrote: Lets add those important packages to repositories and make OpenIndiana popular to newbiesThat's one good way to make it popular . Anyone who wanted to was always free to contribute such packages to OpenSolaris, via spec-files-extra and later, Source Juicer. Not many people ever did, and of those, not everyone subsequently kept them up to date. If OpenIndiana can find the people to port and maintain a large package library that Sun/Oracle never could, then fair play to them! Cheeri, Calum. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Tor for opensolaris
Hi, John Thompson píše v st 08. 09. 2010 v 21:43 -0500: On 2010-09-08, Milan Jurik milan.ju...@sun.com wrote: # pkg publisher - output, please # pkg publisher PUBLISHER TYPE STATUS URI opensolaris.org (preferred) origin online http://pkg.opensolaris.org/dev/ Blastwave origin online http://blastwave.network.com:1/ OpenSolarisContriborigin online http://pkg.opensolaris.org/contrib/ SunFreeware origin online http://pkg.sunfreeware.com:9000/ opensolarisPendingorigin online http://pkg.opensolaris.org/pending/ Personally I would recommend to drop contrib and pending, they seem to be dead, with old unmaintained packages. # pkg image-update - output, please Pending... this seems to be taking quite a while. Yes :-( You have to finish this part (system upgrade to the latest build) till you will be able to install tor. Obviously you did not update your system to /dev Entirely likely; I am new to opensolaris, coming from a linux/FreeBSD/NetBSD background. I understand. One single package from new build is not installed if others dependencies are blocked. So you have to move to the latest build and then you could install tor. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Tor for opensolaris
Hi, On 8.09.10 05:45, John Thompson wrote: On 2010-09-07, Florian Manschwetusflorianmanschwe...@gmx.de wrote: looks like pkg install network/tor should work on b134 http://pkg.opensolaris.org/dev/en/search.shtml?token=3Dtoraction=3DSearch Alas, apparently not: # pkg install network/tor Creating Plan -pkg: install: The following package(s) violated constraints: Package consolidation/sfw/sfw-incorporation contains constraint incompatible with constraint in installed package entire proposed: Pkg SUNWmeld: Optional min_version: 1.1.5.1,5.11-0.133 max version: 1.1.5.1,5.11-0.133 defined by: pkg:/consolidation/sfw/sfw-incorporation installed: Pkg SUNWmeld: Optional min_version: 1.1.5.1,5.11-0.111 max version: 1.1.5.1,5.11-0.111 defined by: pkg:/entire # pkg publisher - output, please # pkg image-update - output, please Obviously you did not update your system to /dev Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] OpenSolaris cancelled, to be replaced with Solaris 11 Express
Hi, On 7.09.10 19:33, Orvar Korvar wrote: IBM has publicly said that they are phasing out AIX in favour of Linux. AIX will be killed. IBM has said that officially. Here is links that confirm my claim. Just google a bit and you will see. http://www.zdnet.co.uk/news/application-development/2003/01/29/ibm-linux-will-replace-aix-2129537/ http://news.cnet.com/2100-1001-982512.html I am aware of these very old news. And I would guess their plans changed... Only my personal guessing. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] OpenSolaris cancelled, to be replaced with Solaris 11 Express
Hi Orvar On 6.09.10 17:06, Orvar Korvar wrote: IBM has publicly said that they are phasing out AIX in favour of Linux. AIX will be killed. IBM has said that officially. Really? Where? Could you point on some recent info around this, please? Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] mplayer + VDPAU + opensolaris = ?
Hi John, John Martin píše v út 20. 07. 2010 v 13:53 -0400: For media players I always recommend Fluendo before trying to roll your own. Cannot test OS support for SSE, leaving disabled. . When I get some time I will look into the SSE message. See the fix for SSE/SSE2 below in cpudetect.c. Maybe someone could request pushing this to the upstream code. I tried with similar patch 2 years ago and it ended in no clear result because of http://lists.mplayerhq.hu/pipermail/mplayer-dev-eng/2008-September/058585.html Best regards, Milan SSE and SSE2 are enabled on my Atom N330 so hopefully this will help speedup the CPU bound portions of the playback. (I'm not certain the __sun is the correct macro going forward, but it is the only thing that seemed to work with all the compilers I tested). On a Atom N330 + ION 4GB system not on the Oracle network I loaded b134 and added the gcc-43, svn, gettext, and x11/header packages from the /dev repository. Downloaded mplayer following the VDPAU instructions: $ mkdir mplayer $ cd mplayer $ svn co --ignore-externals svn://svn.mplayerhq.hu/mplayer/trunk . $ svn co svn://svn.mplayerhq.hu/ffmpeg/trunk/libavcodec $ svn co svn://svn.mplayerhq.hu/ffmpeg/trunk/libavformat $ svn co svn://svn.mplayerhq.hu/ffmpeg/trunk/libavutil $ svn co svn://svn.mplayerhq.hu/ffmpeg/trunk/libpostproc $ svn co svn://svn.mplayerhq.hu/dvdnav/trunk/libdvdread/src libdvdread4 $ svn co svn://svn.mplayerhq.hu/dvdnav/trunk/libdvdnav/src libdvdnav Made the following changes: +++ configure 2010-07-20 09:27:25.178089569 -0400 @@ -1,4 +1,4 @@ -#! /bin/sh +#! /bin/bash # # Original version (C) 2000 Pontscho/fresh!mindworkz # ponts...@makacs.poliod.hu @@ -1503,6 +1503,10 @@ extra_cflags=$extra_cflags -I/usr/pkg/include fi +if sunos ; then +extra_cflags=$extra_cflags -Wa,--divide +fi + if darwin; then extra_cflags=-mdynamic-no-pic -falign-loops=16 -shared-libgcc $extra_cflags _timer=timer-darwin.c +++ version.sh 2010-07-20 09:28:42.220664374 -0400 @@ -1,4 +1,4 @@ -#!/bin/sh +#!/bin/bash test $1 extra=-$1 +++ cpudetect.c 2010-07-20 13:47:06.382713016 -0400 @@ -45,6 +45,8 @@ #include os2.h #elif defined(__AMIGAOS4__) #include proto/exec.h +#elif defined(__sun) +#include sys/auxv.h #endif /* Thanks to the FreeBSD project for some of this cpuid code, and @@ -416,6 +418,11 @@ mp_msg(MSGT_CPUDETECT,MSGL_WARN, Cannot test OS support for SSE, disabling to be safe.\n ); gCpuCaps.hasSSE=0; #endif /* _POSIX_SOURCE */ +#elif defined(__sun) +uint32_t ui = 0; +(void)getisax(ui, 1); +gCpuCaps.hasSSE = (ui AV_386_SSE) ? 1 : 0; +gCpuCaps.hasSSE2 = (ui AV_386_SSE2) ? 1 : 0; #else /* Do nothing on other platforms for now. */ Built with: $ export PATH=/usr/gcc/4.3/bin:$PATH $ export CC=/usr/gcc/4.3/bin/gcc $ export CXX=/usr/gcc/4.3/bin/g++ $ ./configure --disable-xvr100 --enable-gui --disable-x264-lavc --disable-x264 --enable-vdpau $ gmake ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Solaris gcc but gnu-ld
Hi, Joerg Schilling píše v ne 11. 07. 2010 v 16:05 +0200: Günther Schmidt gue.schm...@web.de wrote: Hi Joerg, I'm trying to compile ghc and there is an option for ld which Sun's ld does not understand but gnu's ld does. Do you mean this ghc: http://pkgbuild.svn.sourceforge.net/viewvc/pkgbuild/spec-files-extra/trunk/SFEghc.spec?revision=2570view=markup ? Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Solaris gcc but gnu-ld
Hi, Günther Schmidt píše v ne 11. 07. 2010 v 16:34 +0200: Hello Milan, actually it's about http://hackage.haskell.org/trac/ghc/ticket/1786 so, did you try that spec from SFE (see details on http://pkgbuild.sourceforge.net/spec-files-extra/)? Does it require GNU ld? Dirty hack how to force GNU ld usage, it is to replace /usr/bin/ld with /usr/gnu/bin/ld. But GNU ld is very problematic on Solaris, try the spec at first. Best regards, Milan Günther Am 11.07.10 16:22, schrieb Milan Jurik: Hi, Joerg Schilling píše v ne 11. 07. 2010 v 16:05 +0200: Günther Schmidtgue.schm...@web.de wrote: Hi Joerg, I'm trying to compile ghc and there is an option for ld which Sun's ld does not understand but gnu's ld does. Do you mean this ghc: http://pkgbuild.svn.sourceforge.net/viewvc/pkgbuild/spec-files-extra/trunk/SFEghc.spec?revision=2570view=markup ? Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Where is OpenSolaris 2010 release?
Hi Calum, Calum Benson píše v út 06. 07. 2010 v 21:19 +0100: On 6 Jul 2010, at 20:50, Rafael Barros Felix de Sousa wrote: Without the open source community (usually made of hardcore users with extensive knowledge of computing who usually work in IT companies or universities) support, they would lose even more clients, after all who would advocate for them besides theyselves also who would test their system before production release? While I'm sure we can all think of several potential disadvantages to closing the Solaris source again, I wouldn't say lack of QA would be one of them. Closed source, commercial software gets released all the time with sufficient testing, for example through formal beta programmes with paying customers -- very much like Sun used to do with Solaris, in fact. Just my personal oppinion - yes, there would be no lack of QA even in such bad situation, of course, but wider usage of pre-released versions is benefitial every time. None of QA can catch all real-life bugs (otherwise I would have no job in Solaris space). Personally I submitted bunch of CRs (including critical) only because somebody external had access to OpenSolaris and used it for his/her usecases. Also I fixed several unpleasant bugs discovered by external users (and not by QA for years). With high probability these bugs would not be discovered in QA process and would impact critical production systems later. So, this is one of the biggest benefits of free community, I think. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Oracle has Linux video codecs, so codecs for OSOL?
Hi, On 06/29/10 09:45, Orvar Korvar wrote: I know that Fluendo offers a free MP3 sound codec. But does Fluendo offer free video codecs? Alan, I know that many Linux distros has video codecs included. Wrong assumption. The most of Linux distros are not delivering non-free multimedia codecs for free. Some of them are cheating with some unofficial repositories and one-click installations. Others are using Codeina way with payed Fluendo codecs, the same way as OpenSolaris distro is doing. As Unbreakable Linux is another distro, maybe it also has video codecs included? (Unless it is a strictly server distro). If video codecs are included in Unbreakable Linux, then Oracle has licenses. Maybe those licenses could be transfered to OpenSolaris? I do not believe OEL bundles non-free multimedia codecs. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Open Solaris going the way of the Amiga
Hi Giovanni, On 06/29/10 06:57, Giovanni wrote 4) some key components (i.e. ramdisk implementation) have severe performance issues (a ram disk running at 500MB/s on DDR3 1333 is slower than working on a striped physical disk set; same ramdisk on Linux on same hw runs at several GB/s) Bug number, please? For the rest, I understand your frustration but that is all I can do. Use alternative distro if you cannot wait for Oracle distro, please. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Oracle needs to re-evaluate it's stance on pretty much everything
Hi Jack, On 06/29/10 06:32, Jack Kielsmeier wrote: I’m really missing pre-Oracle Sun. Recently, my company decided to purchase many Sun Fire X4200 servers. We needed DC power supplies and nothing too powerful CPU wise. Less than 24 hours upon submitting an order, we decided we wanted to lower the amount of systems ordered. In order to do so, we would have to pay a 15% fee (on LIST price) of canceled systems. My company has been a Sun customer for many years, ordering millions of dollars of equipment. This is not a good way to make your customers happy. We decided to simply keep the order as is. Additionally, we have been evaluating OpenSolaris for production purposes. We primarily use Solaris 10. OpenSolaris makes Solaris 10 look like a dinosaur, but Solaris 10 is proven and OpenSolaris isn’t exactly known to be used in major production environments. Before Oracle, Sun was very open and would talk about the product. Now, getting information is like pulling teeth. We are now considering abandoning the idea of using OpenSolaris in a production environment, just months prior to our planned rollout. We were also looking at Sun Open Storage as an alternative to some NetApp purchases, but once again, due to Oracles (in my opinion) shady business practices, we are going to abandon that also. It’s sad really. I really like Sun hardware, but I see my shop changing to HP or IBM in the future and transitioning off of Solaris 10. We have already started running a mix of Linux + Solaris. sorry to hear this. Much better thing you can do it is to escalate these things through your sales representatives in Oracle. opensolaris-discuss@ will not help you with it much. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] So who is ready to be let down?
Hi Gary, On 06/28/10 14:41, Gary wrote: If that post doesn't get your account suspended Totally inappropriate language. Well, it is hard to find proper language for your comments, do not be surprised. Yes, we can ignore them and follow others, if you want. But I also guess if you are pro-OpenSolaris then you'll be good to go and can say anything you want (and smiley faces make it okay). 2009.06 is not less than a year old. I supoose they froze the build and it went through security and other testing in one day. It takes FreeBSD 1-2 weeks after the announcement and the announcement is made after the build. Builds are only after RC's. So I doubt all of that prep work was done that quickly. Besides, July is only three days away and 90.06 was release June 1, 2009. So that makes it no less than 13 months old. So with the other work before the release it is closer to 14 months old. Truth, /release is more than year old. And the other operating systems I printed release dates for are RELEASES. I'm not talking about development releases like you mentioned. If I were to do that the list would be too long. All of those are RELEASES. OpenSolaris hasn't had a RELEASE in 13 months (and it's 14 months old). z/OS has even had 2 releases since the last OpenSolaris RELEASE. z/OS release 1.10 in 2008 z/OS release 1.11 in 2009 z/OS release 1.12 was not released yet AIX has v7 soon, but has had a number of updates for 5.3 and 6.1. AIX 6.1 was released in 2007. Lets continue: Red Hat Enterprise Linux 5.4 in 2009 Red Hat Enterprise Linux 5.5 in 2010 - these are on level of Solaris 10 updates, RHEL 5 was released in 2007, e.g. no core system features update. Yes, you can compare it against Fedora frequency. But you cannot buy support for Fedora. SUSE Linux Enterprise Server had one release in last 14 months. MS Windows Server 2008 - guess the release date Gary, you are bitching on wrong place with wrong arguments. I am sorry. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] whoo whoo - Oracle's net jumps 25 pct in first full Sun qtr
Hi, On 06/25/10 15:54, Fredrich Maney wrote: On Thu, Jun 24, 2010 at 8:27 PM, Bart Smaalders bart.smaald...@oracle.com wrote: As many of us have stated, the next release of Solaris will be based on the work done in OpenSolaris. But will it still be recognizable as Solaris? Or is it going to be just another Linux clone, albeit with a different kernel? It cannot be Linux clone with a different kernel because Linux is only kernel. The rest is not Linux. Linux based distros are building on top of GNU userspace usually. Is your point about bundling GNU utilities with OpenSolaris and about making them default? Well, traditional userspace utilities are in OpenSolaris and people are improving them in last builds. I am not happy GNU userspace is preferred in OpenSolaris because it breaks many things for me but for that reason I am changing defaults in my setups to traditional. And you can do it also. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] thanks to all who helped choochoo with OSOL message to Oracle/ Sun
Hi Erik, Erik Trimble píše v st 16. 06. 2010 v 23:02 -0700: adidas wrote: It is ridiculous to go through installation of windows/linux just to play movies/videos and voice/video chat. http://www.opensolaris.com/learn/features/whats-new/200906/#1 says it is for [b]users [/b]also (Toshiba laptops, that are sold, are not used as production servers I think!!!). Very few things need to be done to use a server as a desktop. No good business person denies the huge desktop market. Yes, plenty of good business people deny (i.e. avoid) the desktop market. It *sucks* for revenue for everyone except Microsoft. While it's certainly a worthy goal to support concepts like the SunRay and other corporate-style super-managed thin clients, going after the traditional home user/corporate desktop market is a Massive effort. And one which pays very, very, very little dividend. Right now, both Linux and Windows make reasonably good desktop OSes. From the OpenSolaris standpoint, what good does it bring the project to attempt to compete with them? Having a modestly-usable system for development is good, which is what we currently have by simply recompiling apps from Linux and *BSD land. What benefit would we gain by spending a whole lot of effort trying to improve the business/home user experience? Right now, OpenSolaris is targeted at the Enterprise and Technical User communities. What reason is sufficient for OpenSolaris to try to move beyond those communities? OpenSolaris is a niche OS - highly robust, highly scaleable, highly manageable servers and appliances. It's a rather broad niche, but it's a niche nonetheless. Given the more limited resources available for its development, I can't see any cost-benefit to trying to expand it out of that niche. OpenSolaris works very well in conjunction with other OSes, so there's no need for an OpenSolaris-everywhere strategy. All that said, it's an entirely worthy goal to continue to port over those Linux *BSD userland applications which require little effort, and enhance the user experience. I'm just not in favor of any serious effort at the OS level to accommodate more desktop-ish features at the expense of server features/improvements. For instance: I don't particularly care that OpenSolaris's firewire support isn't that great. The reason is simple for improving desktop feeling and you heard it here already - people prefer to use system which they know, on both sides. And not every admin will maintain own desktop at home for himself and the other for the rest of his family. I am not saying we should push commercial games for OpenSolaris. But we should try to make OpenSolaris good enough for typical users also. Otherwise only small portion of people will know about Solaris and will use Solaris on universities and will use it in their datacenters. If OpenSolaris will end in niche market only then it is on way to die. All niche markets are shrinking over time. There is need for an OpenSolaris-mostly-everywhere strategy in long-term. Otherwise it will be OpenSolaris-nowhere sooner or later. ObDisclaimer: All statements and opinions are my own, and do not represent in any way that of my employer or anyone else. The same applies for me. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Infiniband card
Hi, you could try to extract arbel driver from Solaris InfiniBand(IB) Updates 3.1 which you can download through: http://www.oracle.com/technology/software/sun_az_index.html But as you can see there is no supported version of arbel driver. Best regards, Milan Dne 16.06.10 16:20, Prudhvi Krishna Surapaneni napsal(a): Hi Milan, now that you mention. The arbel driver package that comes with OpenSolaris is empty. (My apologies) Can you point me to some links that provide the arbel driver that i can download. Just curious as to why they are not bundled along with other drivers. Thanks, Prudhvi Surapaneni. Which arbel driver did you try? Arbel was not distributed with OpenSolaris but only as unbundled and I think we are not distributing it now. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Infiniband card
Hi, Prudhvi Krishna Surapaneni píše v út 15. 06. 2010 v 17:56 -0500: Hi, I have a same MHEA28-XTC (mem-free) card. which prtconf -vp reports as pci15b3.6282. I manually tried attaching tavor and arbel drivers to pci15b3.6282. But, i could not get the drive listed in the ifconfig. My machine runs on b134 on amd64. If mem-free cards are not supported on opensolaris. I would like to hear your suggestions on which infiniband hca card i could purchase that i supported on OpenSolaris and is cheaper. Thanks, Prudhvi Surapaneni. Which arbel driver did you try? Arbel was not distributed with OpenSolaris but only as unbundled and I think we are not distributing it now. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SCSI board support?
Hi Xavier, Xavier Beaudouin píše v út 01. 06. 2010 v 22:49 +0200: Hello, I had some woes about OpenSolaris and SCSI support. I had on my desk a 2940, the band old reference that works everywhere but not on OpenSolaris. Well, Adaptec is distributing only 32-bit version of adp driver. You can try to contact Adaptec. I have difficulties to find an HCL about SCSI supported cards and models, and since I have a JBOD with 12 300GB HD, it will be a shame I'm not be able to use it LSI/symbios are good (see man glm), from Adaptec only AIC-7902 (man adpu320), some other LSI SCSI cards are supported by mpt (man mpt). Any good references for me ? (Tested some Qlogic - no luck at all...) Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Solaris 8/9 zones on OpenSolaris x64?
Hi Erik, Erik Trimble píše v čt 20. 05. 2010 v 00:48 -0700: Naturally, with all the re-alignment of the various virtualization technologies available for Solaris, I'm left with an old question that I can't seem to find out if there's a new answer. I'm looking to run a Solaris 8 zone/container on an OpenSolaris x64 host, not a SPARC host. Yes, I know I could do this via VirtualBox, but there are good reasons I would rather run in a zone. We used to support S8 containers in S10 on SPARC, but I can't sift through all the blizzard of product literature to see if we now support S8 zones on S10/OpenSolaris x64. I now see that we do S10 zones on OpenSolaris x64, and naturally, BrandZ (linux) zones run on S10 OpenSolaris x64. So, I'm a bit hopeful... PSARC 2007/350 is SPARC only. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Opensolaris or Solaris VPN solutions
Hi Albert, Albert Lee píše v st 12. 05. 2010 v 00:14 -0400: On Tue, 11 May 2010 23:55:09 +0100, Calum Benson calum.ben...@oracle.com wrote: On 11 May 2010, at 18:46, Francois Laagel wrote: There's also vpnc (http://www.unix-ag.uni-kl.de/~massar/vpnc/) I haven't tried it but it seems that development/maintenance of that project stopped several years ago. It works just fine any time I've used it, as an alternative to Cisco's VPN 3000 client. Cheeri, Calum. I created SFEvpnc a while ago which includes some minor improvements, I imagine it should still work. SFEvpnc should be OK, but SFEtun needs some update and nobody had time to do it yet. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Codeina popup
Hi, Gary Gendel píše v čt 01. 04. 2010 v 05:53 -0700: Whenever I log in, I get a message that there are Codeina updates available for the free mp3 decoder. So I installed the upgrade, but it still still happens every time I log in. If I tell it to install again, it tells me that it's already installed. Anyone know what the process is to find out whether it's really upgraded, or if this is a bogus popup? Then, if it is the latter, how do I convince the upgrade process that it's got the upgrade? I would guess it is bug in Codeina, Fluendo shop or, maybe, you have one more copy of that codec stored on the system somewhere else? Check content of ~/.gstreamer-0.10/plugins/ and /usr/lib/gstreamer-0.10/ and log the bug to defect.opensolaris.org, if you cannot find any reason. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Opensolaris 2010.03?
Hi, W. Wayne Liauh píše v út 23. 02. 2010 v 17:10 -0800: But b133 (LiveCD) still failed to boot from two of our three test machines (both are with multi-core, at least 4 GB DDR2, one with ATI HD graphics the other with Intel chip). On the one machine that it successfully boots (HP dv3, 4GB, ATI HD 4200), it keeps asking for password to a wifi network that does not require authentication. Could you send the CR numbers, please? Easily you can see from their status if they went to build 134 or not. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] building standalone modules
Hi Mark, Mark Maule píše v po 18. 01. 2010 v 16:15 -0800: Out of curiousity, why? Every compiler has bugs. SUN is doing very large testing of every build based on binaries produced by Sun Studio. If bug is found, it is fixed. GCC builds are done (shadow builds) but the results are not tested much. We build our current platform (QNX) and apps using gcc4.2. I've got an outstanding message posted to tool-compilers wondering if anyone has experience builing ONNV with 4.2. We have done some test builds of ONNV using gcc (3.4 I think) and it seems to boot x86 anyway. Current CBE includes GCC 3.4.3 with some fixes, but it is used only for shadow building. There were some fixes going to gate for support GCC 4.something.something (probably 4.2.x or 4.3.y, I do not remember which) but it is not used much, outside of Parfait backend I believe. There is no problem to use GCC for your binaries, but for ON gate you can be surprised by some bugs. Of course, you are welcome to report them, investigate them and fix them :-) Best regards, Milan Mark -Original Message- From: erik.trim...@sun.com [mailto:erik.trim...@sun.com] Sent: 2010-01-18 17:27 To: Mark Maule Cc: Jason King; Milan Jurik; opensolaris-discuss@opensolaris.org Subject: Re: [osol-discuss] building standalone modules Mark Maule wrote: Agreed - we plan on using documented interfaces. I'll puruse the driver tutorial and writer documents. My main issue at the moment is the specifics of getting things compiled and linked for i386 32/64. If that is addressed in the documents, then I should have what I need. Thanks for the responses. Mark One other thing - I'd recommend using the Sun Studio compilers, rather than GCC. The SS compilers are available for free on both SPARC and x86/x64. http://developers.sun.com/sunstudio/downloads/opensolaris/index.jsp -- Erik Trimble Java System Support Mailstop: usca22-123 Phone: x17195 Santa Clara, CA ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] building standalone modules
Hi Mark, Mark Maule píše v so 16. 01. 2010 v 14:12 -0800: Not sure if this is the correct forum, so starting here: It depends of what you really need. We are building a system based on opensolaris, and will be adding our own kernel modules. What is the precedent for building vendor-supplied modules? Are they generally incorporated under the os-nv src tree? My preference would be to build them outside the os-nv tree in order to avoid polluting the tree with vendor-specific module (and command) code. If you plan to keep those modules private for your company, then you can keep them in nested workspace everywhere you want. If you plan to integrate them later to upstream os-nv, follow os-nv tree structure, there are several examples of modules comming from device vendors (e.g. Intel) in os-nv gate. As for nested workspaces, Mercurial ignores subdirectories which are not maintained by it, so you can include them everywhere inside tree on build machines. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] building standalone modules
Mark, Mark Maule píše v po 18. 01. 2010 v 11:58 -0800: Thanks Milan: The things we are working on would remain private. I would plan on generating them using an opensolaris machine running a ONNV installation close to what we will be running on the product. Eventually, would like to be able to cross compile them from a different machine, possibly running Linux. OK, then it is your decision how to make your life easy :-) The cross-compile enviroment can be small challenge for kernel modules, as every good cross-compile enviroment. But I am not expert. As far as cc/ld flags necessary for generating the kernel modules, is that formally documented somewhere, or do I just look to ONNV modules for examples? I would start with simple Device Driver Tutorial and then Writing Device Drivers on docs.sun.com For non-device drivers modules I can recommend Solaris Internals, book and/or very good training. Best regards, Milan thanks Mark -Original Message- From: milan.ju...@sun.com [mailto:milan.ju...@sun.com] Sent: 2010-01-18 13:09 To: Mark Maule Cc: opensolaris-discuss@opensolaris.org Subject: Re: [osol-discuss] building standalone modules Hi Mark, Mark Maule píše v so 16. 01. 2010 v 14:12 -0800: Not sure if this is the correct forum, so starting here: It depends of what you really need. We are building a system based on opensolaris, and will be adding our own kernel modules. What is the precedent for building vendor-supplied modules? Are they generally incorporated under the os-nv src tree? My preference would be to build them outside the os-nv tree in order to avoid polluting the tree with vendor-specific module (and command) code. If you plan to keep those modules private for your company, then you can keep them in nested workspace everywhere you want. If you plan to integrate them later to upstream os-nv, follow os-nv tree structure, there are several examples of modules comming from device vendors (e.g. Intel) in os-nv gate. As for nested workspaces, Mercurial ignores subdirectories which are not maintained by it, so you can include them everywhere inside tree on build machines. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Bugster CR 6870290 and CR 6913815 - shutdown/restart and S3 suspend problems on Tecra M10
Hi Andrew, I fwded your e-mail to RandyF. Best regards, Milan andrew píše v po 04. 01. 2010 v 02:16 -0800: I filed 6913815 since I didn't see it tracked elsewhere - the Tecra M10 won't shutdown or restart through BIOS if VT extensions are enabled. I also see related bug 6870290 that was marked - defer - no resource in bugster in August this year. Can anyone tell me if there is resource to look at either of these for 2010.02? The responsible engineer for 6913815 but my attempt to guess his sun email address has failed. :-( Thanks Andrew. Message was edited by: andrewk7 That last bit should have read: The responsible engineer for 6913815 is Randy Fishel but my attempt to guess his sun email address has failed. :-( ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] pcie_hp_init: initialize hotplug controller failed with -1
Hi, Alexander píše v út 15. 12. 2009 v 09:31 -0800: Hello. After updating OpenSolaris from snv_126 to snv_129 I started to receive the following messages on boot: Dec 15 19:15:36 opensolaris genunix: [ID 936769 kern.info] pcieb0 is /p...@0,0/pci8086,2...@1 Dec 15 19:15:36 opensolaris pcie: [ID 441510 kern.warning] WARNING: pcie_hp_init: initialize hotplug controller failed with -1 Dec 15 19:15:36 opensolaris pcie: [ID 552151 kern.warning] WARNING: pcieb1: Failed setting hotplug framework Dec 15 19:15:36 opensolaris npe: [ID 236367 kern.info] PCI Express-device: pci8086,2...@1c, pcieb1 Dec 15 19:15:36 opensolaris genunix: [ID 936769 kern.info] pcieb1 is /p...@0,0/pci8086,2...@1c Dec 15 19:15:36 opensolaris pcie: [ID 441510 kern.warning] WARNING: pcie_hp_init: initialize hotplug controller failed with -1 Dec 15 19:15:36 opensolaris pcie: [ID 552151 kern.warning] WARNING: pcieb2: Failed setting hotplug framework Dec 15 19:15:36 opensolaris npe: [ID 236367 kern.info] PCI Express-device: pci8086,2...@1c,1, pcieb2 Dec 15 19:15:36 opensolaris genunix: [ID 936769 kern.info] pcieb2 is /p...@0,0/pci8086,2...@1c,1 Dec 15 19:15:36 opensolaris pcie: [ID 441510 kern.warning] WARNING: pcie_hp_init: initialize hotplug controller failed with -1 Dec 15 19:15:36 opensolaris pcie: [ID 552151 kern.warning] WARNING: pcieb3: Failed setting hotplug framework Dec 15 19:15:36 opensolaris npe: [ID 236367 kern.info] PCI Express-device: pci8086,2...@1c,2, pcieb3 Dec 15 19:15:36 opensolaris genunix: [ID 936769 kern.info] pcieb3 is /p...@0,0/pci8086,2...@1c,2 Dec 15 19:15:36 opensolaris pcie: [ID 441510 kern.warning] WARNING: pcie_hp_init: initialize hotplug controller failed with -1 Dec 15 19:15:36 opensolaris pcie: [ID 552151 kern.warning] WARNING: pcieb4: Failed setting hotplug framework Dec 15 19:15:36 opensolaris npe: [ID 236367 kern.info] PCI Express-device: pci8086,2...@1c,3, pcieb4 Dec 15 19:15:36 opensolaris genunix: [ID 936769 kern.info] pcieb4 is /p...@0,0/pci8086,2...@1c,3 Dec 15 19:15:36 opensolaris pcie: [ID 441510 kern.warning] WARNING: pcie_hp_init: initialize hotplug controller failed with -1 Dec 15 19:15:36 opensolaris pcie: [ID 552151 kern.warning] WARNING: pcieb5: Failed setting hotplug framework What does it mean??? There were some significant changes added to snv_128. Please, log new bug on bugs.opensolaris.org and add description of your system. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Some Why?-Questions
Hi Thomas, Thomas Maier-Komor píše v st 09. 12. 2009 v 09:32 +0100: On 08.12.2009 23:08, Francois Laagel wrote: Jörg Stephan schrieb: [...] Why doesn't Linux support ZFS? If does! In user mode through FUSE. Just the same way as, I've heard, if you're really determined you can implement NTFS under OpenSolaris. Francois I know ;-) My question was meant rhetorically... Anyway, both FUSE based solutions are really only a workaround. What I wanted to imply with my question is: don't expect other systems than Linux to support ext2/ext3, as Linux also doesn't support things like ZFS out of the box. One really has to live with the native filesystems an OS provides. Best thing that you can get in common are SMB and NFS, as VFAT has almost no features whatsoever and a lot of severe limitations (e.g. 4G file size limit that hit me already a couple of times...) There is no technical reason, only limited manpower, why OSol cannot support ext2/ext3. On-disk format is stable and documented and here is the solution: http://hub.opensolaris.org/bin/view/Project+ext3/ SMB/NFS is good for migration if you have 2 systems but for small business and dualboot it is not good enough. ext4 is different topic. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Some Why?-Questions
Hi Erik, Erik Trimble píše v st 09. 12. 2009 v 01:35 -0800: Milan Jurik wrote: Hi Thomas, Thomas Maier-Komor píše v st 09. 12. 2009 v 09:32 +0100: On 08.12.2009 23:08, Francois Laagel wrote: Jörg Stephan schrieb: [...] Why doesn't Linux support ZFS? If does! In user mode through FUSE. Just the same way as, I've heard, if you're really determined you can implement NTFS under OpenSolaris. Francois I know ;-) My question was meant rhetorically... Anyway, both FUSE based solutions are really only a workaround. What I wanted to imply with my question is: don't expect other systems than Linux to support ext2/ext3, as Linux also doesn't support things like ZFS out of the box. One really has to live with the native filesystems an OS provides. Best thing that you can get in common are SMB and NFS, as VFAT has almost no features whatsoever and a lot of severe limitations (e.g. 4G file size limit that hit me already a couple of times...) There is no technical reason, only limited manpower, why OSol cannot support ext2/ext3. On-disk format is stable and documented and here is the solution: http://hub.opensolaris.org/bin/view/Project+ext3/ SMB/NFS is good for migration if you have 2 systems but for small business and dualboot it is not good enough. How is small business relevant? Small business with one fileserver. Some of them cannot buy another system only for data migration, they migrate data inside one box (I participated on such activities few times). Small means few people company but sometimes with large amount of data (like some Public Relations companies, graphic studios etc.). I simply can't seem to think of a reason why ext2/3/4 support is really useful for OpenSolaris; all the scenarios I can come up with can be equally served by using ISO or FAT or network sharing, or, frankly, the situation is contrived. Will you share your documentation in dualboot on FAT partition on your laptop? Based on poor quality of FAT design and FAT implementation in OSol, no, thanks. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Some Why?-Questions
Erik, Erik Trimble píše v st 09. 12. 2009 v 05:11 -0800: Milan Jurik wrote: Hi Erik, Erik Trimble píše v st 09. 12. 2009 v 01:35 -0800: Milan Jurik wrote: Hi Thomas, Thomas Maier-Komor píše v st 09. 12. 2009 v 09:32 +0100: There is no technical reason, only limited manpower, why OSol cannot support ext2/ext3. On-disk format is stable and documented and here is the solution: http://hub.opensolaris.org/bin/view/Project+ext3/ SMB/NFS is good for migration if you have 2 systems but for small business and dualboot it is not good enough. How is small business relevant? Small business with one fileserver. Some of them cannot buy another system only for data migration, they migrate data inside one box (I participated on such activities few times). Small means few people company but sometimes with large amount of data (like some Public Relations companies, graphic studios etc.). That's insane. Nobody can do this - you can't expect to do a OS migration without having blank disks to install the new OS onto. Even then, you don't move between two major OSes and keep the old disk(s) in the previous OS's native filesystem, for use later as data partitions. When moving from Windows2000 server to Windows2003 server, they recommend you wipe and reformat any NTFS partitions. Switching Linux distros usually results in migrating ext2/3 versions on partitions. You back up the data on the machine, wipe it, and install the new OS. A small business server costs under $2k these days for a decent one, $5k for a beefy one. Businesses that can't afford those costs can't afford to do a migration. Manpower costs alone to do the migration exceed either of those. And, honestly, OpenSolaris isn't targeted at someone who can't afford to pay for a modest new machine every couple of years. Doing a OS migration on a single, non-redundant machine while retaining the original OS isn't a realistic rational scenario. Doesn't mean it can't be done in some OSes. Doesn't mean it SHOULD be done, even on those OSes. Call those people insane who paid for it. But I met such situations. If you have hundreds of gigabytes stored on such system, you are evaluating all possible ways. And yes, we did such migration for much smaller price than $2k. I simply can't seem to think of a reason why ext2/3/4 support is really useful for OpenSolaris; all the scenarios I can come up with can be equally served by using ISO or FAT or network sharing, or, frankly, the situation is contrived. Will you share your documentation in dualboot on FAT partition on your laptop? Based on poor quality of FAT design and FAT implementation in OSol, no, thanks. Best regards, Milan Once again, you don't do this. Nobody installs two completely different OSes onto the same partition, let alone two OSes that share virtually identical directory structures, so you certainly wouldn't be installing Linux and OpenSolaris on the same partition. Hell, you're not supposed to even do that with Windows. And, I forget the last time anyone rationally intended to install the root partition as FAT - I think I remember possibly doing that on Linux sometime around 1995, and even Windows hasn't recommended FAT as the C: drive for about a decade now. With a laptop or any other dual-boot situation, the rational thing to do is one partition per OS (i.e. one for Windows, one for OpenSolaris, maybe one for Linux if you're really feeling weird), and a separate one formatted in FAT as the data partition. And, there's nothing wrong with the OSol FAT implementation. It's worked fine for years. Really? Fine? Are you using it for longer time for data sharing? Not just downloading data from USB stick (but even that is not nice). Memory hungry, slow etc. Nobody said something about sharing root partition. But ~/Documents/ on dedicated partition? Will you share it on FAT? Yes, there are lots of scenarios where you COULD want it. Just like I COULD want to add a jet engine to my Honda. If someone really wants to add ext2/3/4 support, I'm not going to stop them. But I'm certainly not seeing any real use case outside the fringe-hobbyist niche, and nothing that would justify spending any non-volunteer time to support. Strange that at least once per month we have the same question across mailing lists - where is ext2/ext3 support in Solaris?. Yes, all major OSes, including MS Windows with 3rd party solution, has ext2 supported. And we use only excuses like use CIFS/NFS, use FAT. I prefer to spend my time to solve it if possible. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Some Why?-Questions
Erik, Erik Trimble píše v st 09. 12. 2009 v 06:22 -0800: Milan Jurik wrote: [...] Call those people insane who paid for it. But I met such situations. If you have hundreds of gigabytes stored on such system, you are evaluating all possible ways. And yes, we did such migration for much smaller price than $2k. How could we? I mean Sun, that is. Base rate for consulting is $100/hr for short jobs, plus the costs for client acquisition, sales, etc. I can't see how we didn't lose money. Ups, sorry, not we. I, years before I came to Sun. And I know about such situations happening also these days. Yes, no direct money for Sun. [...] Really? Fine? Are you using it for longer time for data sharing? Not just downloading data from USB stick (but even that is not nice). Memory hungry, slow etc. That's what Data exchange is: short-term. You don't do high I/O to data-sharing partitions, as no solution is going to give you reliable, good performance. I've worked with the ext2 solutions under Windows, and I would hardly consider them bulletproof or high-speed. Even in native Linux or *BSD, ext2 is one of the lower-performing filesystems outside of FAT. In ext2/ext3 you depend heavilly on way you access the data. Mainly in Linux it depends on tunning/setting. Like in ZFS case. Nobody said something about sharing root partition. But ~/Documents/ on dedicated partition? Will you share it on FAT? I tend to mount shared partitions on /shared or something like that, with my home wherever the local OS decides it should be. /shared is a FAT partition. You do your work in your normal OS partition, then copy data over to the shared partition only when you are prepared to reboot to a new OS. Most importantly, these days, dual-boot is a much-less require solution. Virtualization is a far better choice for a huge variety of places where dual-boot used to be the only solution. Not in case of Linux vs. Solaris. Some devices are supported only under Linux. And there are people who prefers running system on bare metal. Because of virtual machines speed. Frequently it is not required, but prefered. Yes, there are lots of scenarios where you COULD want it. Just like I COULD want to add a jet engine to my Honda. If someone really wants to add ext2/3/4 support, I'm not going to stop them. But I'm certainly not seeing any real use case outside the fringe-hobbyist niche, and nothing that would justify spending any non-volunteer time to support. Strange that at least once per month we have the same question across mailing lists - where is ext2/ext3 support in Solaris?. Yes, all major OSes, including MS Windows with 3rd party solution, has ext2 supported. And we use only excuses like use CIFS/NFS, use FAT. I prefer to spend my time to solve it if possible. Best regards, Milan The problem is one of target audience. OpenSolaris isn't a wholesale Linux replacement - that is, it's not intended to do everything that Linux does, nor be used everywhere that Linux is. People get confused on that. In many ways, OpenSolaris is more like the various *BSD OSes - we have a good niche, where our limitations are minimized, and our strengths reinforced. Staying in niche forced Solaris out of market share. Because niche markets are much smaller these days. Yes, we are able in invade to storage area these days because of ZFS and COMSTAR. But for how long will be ZFS helping us to expand in that market? People are continually asking for features that make OSol more like Linux or Windows, which IS THE WRONG THING. We're NEVER going to have the resources to make OSol a direct competitor to either in the broad sense. What we do need to spend our time on, both as a company and as a community is those niches where OpenSolaris makes sense. When we've fulfilled our feature sets for those niches, then it's a good idea to look for another niche to expand in. Or, if someone offers significant financial incentive to expand into a new niche. But it makes no sense to spread ourselves out, trying to replicate every feature that someone asks for. I agree it is important to concentrate on some parts at first. But if somebody is interested in different parts? For example: over in the ZFS area, you'll see that one of the longest-asked-for features is the ability of expand a RAID-Z set by adding a single disk. It's been asked for, repeatedly, by many people, for over 3 years now. Yet it's down on the priority list of things to do, for two reasons: (1) it's hard, and thus requires significant resources to do well, and (2) it's considerably less useful for the ZFS target audience, which is large-storage systems. We need to do the same (and, say the same) to the OpenSolaris community as a whole: people willing to do the work to scratch their own itch are more
Re: [osol-discuss] adp driver the extra repository
Hi, Francois Laagel píše v čt 29. 10. 2009 v 12:04 -0700: Can we expect the adp driver (present in SXCE build 125) to be included into the OpenSolaris extra repository at some point in the future? That driver supports a bunch of old Adaptec HBAs--the AHA 2940 (aka AIC7861) being one of them--and seems to be distributable only under binary form, which is why it was never integrated into OpenSolaris. Unlikely, there is plan to EOL cadp, adp, cadp160 and possibly even adpu320 in OpenSolaris, I believe. Still, it would be really nice to have, especially for people using old hardware. As an aside, Linux does provide source code for a similar driver. I myself would be greatly satisfied with a binary only driver. To get my 2940 to work under nv_b125, I had to download the full DVD image of the latest SXCE (3.7GB) and install the adp driver from there. Kind of overkill, I'd say... cadp and adp are not 64-bit-ready and there is nobody with time to make them 64-bit-ready (Adaptec's job I believe). But drivers are on Adaptec website, where they can be downloaded and they will stay there I think. Ask Adaptec for support. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] OpenSolaris: insecure or unstable ?
Hi, Mika Borner píše v ne 18. 10. 2009 v 13:09 +0200: Che Kristo wrote: Totally agree with this...forking out 324 USD a year for each of my systems (laptop + workstation) per year is just too much. A basic support option just for security fixes etc at a reasonable price would fill that hole well. Call me cynical but Sun will probably ignore this and keep on ignoring the fact that not everyone is and enterprise grade user. Maybe we just have to push them :-) Here's a poll I've set up: http://www.doodle.com/3ev8fvdxn7yghr84 I'm targeting private, non-corporate users with this poll, who just want security patches/bug fixes. Personally, I'm fine paying a small fee. But hey, USD 324 is too much, I have a family to feed :-) Maybe Sun starts to smell the money, if we get lots of participants in this poll who want to spend some cash... ;-) Cheers Mika Stupid question (and my personal oppinion) - why could this not be provided by community members? With build process more and more documented for all parts, community members can try to produce such backports based on source code commits to devel branch. Yes, it would not be excellent but better than nothing. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] bluetooth project
Hi, yes, the webpages are not active but Mikore Li is still working on it I think (and usually helpfull in more dedicated mailing lists like laptop-discuss@). Best regards, Milan Alexander Vlasov píše v po 05. 10. 2009 v 14:01 +0200: Looks like there were no announces since February and no blog posts ever. Not very alive-and-kicking. Tomas Bodzar wrote: http://www.opensolaris.org/os/project/bluetooth/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Video Capture cards Support
Hi, V pá, 25. 09. 2009 v 19:21, Husam Senussi píše: Hi, Does OpenSolaris video capture cards and TV tuners, No. There was old community project from times before Solaris 10: http://bt848x.sourceforge.net/ but it is based on Linux drivers under GPL. The project ended. if not is there any plan to support these kind of device. No idea. No community effort is seen. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] VLC 1.0.0 is out, but it doesn't compile under osol 2009.06
Hi Alex, Alex Viskovatoff píše v so 11. 07. 2009 v 21:10 -0700: Here's a patch. I think it should be passed upstream; I don't know how to go about doing that. The patch is interesting workaround, good idea. In mplayer source code you can find DOCS/tech/patches.txt which will show you how to contribute it. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] VLC 1.0.0 is out, but it doesn't compile under osol 2009.06
Hi Alex, Alex Viskovatoff píše v pá 10. 07. 2009 v 21:40 -0700: Of course I'm not building mplayer as root! Why would I do that? I hardly ever use su any more, since pfexec is so much more elegant... Some people are strange, aren't they? :-) I'm running snv_117 now, since it turns out that I was wrong when I thought that sound is broken under snv_117 on my system. I tried compiling mplayer from cvs using gcc-4.3.2, but I ran into the same problem as was mentioned in [url=http://opensolaris.org/jive/thread.jspa?threadID=104595tstart=0]this thread[/url], which I'd brought up before. Just replace the part of define inside brackets with 4 * 168 (or 672) People who are trying to build mplayer from CVS under OpenSolaris, including myself, understand that you need to use the GNU build tools and not the System V UNIX tools and Sun Studio compilers. Still, I've not seen any posts indicating that anyone has been able to build mplayer from CVS on OpenSolaris recently. I am not so interested in building old versions of mplayer, since I can get all the functionality I need out of mplayer/mencoder on my Linux box. And I'm not aware whether a binary for mencoder has ever been produced for Solaris. Strange, I do not need GNU utils (except those which are detected by configure script and gawk). And with GCC 3.4.3 (yes, I am aware of missalign warnings). My enviroment conforms to Single UNIX Specification v3 (see man standards). And still I can compile mplayer and mencoder, even under Solaris Express (e.g. the latest build 117 with todays today's CVS snapshot). No functionality loss, 3 patches need (and OpenSolaris should need only 2 of them). I think MPlayer upstream is very proactive in fixing multiplatforms problems. spec file for actual mplayer snapshot will go to SFE repository in few minutes. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] regretting for OS... (was ATI Radeon 1650 DRI)
Hi, Alexander píše v pá 10. 07. 2009 v 00:22 -0700: Ok. Let's stop flame and return to the constructive discussion... I'll try to compile totem from specs with enabled debug if I have free time... OK, thanks. But I think the core file (or even pstack from the corefile) can be good starting point. It's not funny... GDB error while trying to load core dump... :) Reading symbols from /usr/lib/libvorbisfile.so.3...elfread.c:366: internal-error: sect_index_data not initialized A problem internal to GDB has been detected, further debugging may prove unreliable. Learn about pstack command ;-) Quit this debugging session? (y or n) n ... The trace is: #0 0xf7ce5b40 in ?? () from /usr/lib/gstreamer-0.10/libgstffmpeg.so #1 0xf7df6bbf in ?? () from /usr/lib/gstreamer-0.10/libgstffmpeg.so #2 0xf7df73a2 in ?? () from /usr/lib/gstreamer-0.10/libgstffmpeg.so #3 0xf7e6e495 in ?? () from /usr/lib/gstreamer-0.10/libgstffmpeg.so #4 0xf7c2772c in ?? () from /usr/lib/gstreamer-0.10/libgstffmpeg.so #5 0xf7c28245 in ?? () from /usr/lib/gstreamer-0.10/libgstffmpeg.so #6 0xf7c2b3d4 in ?? () from /usr/lib/gstreamer-0.10/libgstffmpeg.so #7 0xfee53c37 in gst_pad_push () from /usr/lib/libgstreamer-0.10.so.0 #8 0xf84de1fc in gst_queue_loop () from /usr/lib/gstreamer-0.10/libgstcoreelements.so #9 0xfee7288e in gst_task_func () from /usr/lib/libgstreamer-0.10.so.0 #10 0xfc96c5c3 in g_thread_pool_thread_proxy () from /usr/lib/libglib-2.0.so.0 #11 0xfc96af6b in g_thread_create_proxy () from /usr/lib/libglib-2.0.so.0 #12 0xfc71cd66 in _thrp_setup () from /lib/libc.so.1 #13 0xfc71cff0 in __csigsetjmp () from /lib/libc.so.1 #14 0x in ?? () I think I should compile gst-ffmpeg myself, something with libgstffmpeg.so from ips.homeunix.com or maybe this is some version mismatch in gst-ffmpeg and gst-plugins-ugly... It does not look like mismatch, but wrong version of gstffmpeg plugin. Report it to owner of ips.homeunix.com Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] regretting for OS... (was ATI Radeon 1650 DRI)
Alexander, Alexander Pyhalov píše v pá 10. 07. 2009 v 13:18 +0400: В пт, 10/07/2009 в 11:09 +0200, Milan Jurik пишет: Hi, Alexander píše v pá 10. 07. 2009 v 00:59 -0700: After building gst-ffmpeg myself totem is not crashing on wma... However, there are 2 issues: - I can't check sound, because I've built it on VMware ESX VM (VM doesn't have sound card). And? Even if there is no sound card you can move the binary to system where you have it. I haven't real (not VM) system with OpenSolaris on work. I made some experiments too make compilation at home easier. Try your generic-slavic-language knowledge ;-) http://xylab.cz:8080/multimedia/doku.php/gstreamer_ffmpeg Thanks for the link. But I've compiled gst-ffmpeg-0.10.6 without patches. Only trick with ld. Wrong trick, it is better to use flags ;-) Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] regretting for OS... (was ATI Radeon 1650 DRI)
Alexander, I think there is huge misunderstanding between us (and this is not starting point for flame :-) ): Alexander píše v st 08. 07. 2009 v 22:48 -0700: Hi Alexander, I think you have already the most of things fixed, The only thing I've fixed is mplayer 2) There are not enough gstreamer plugins (all suggestions are to BUY fluendo codecs). Why should I do it, if there is gstreamer-plugins-ugly? I can compile it... Yes, but after compilation totem dies trying to play WMA files To fix this we need one thing from you - how does it die? Can you distribute some short WMA file with which I can reproduce it, so I can try to root cause it and fix it? Or give me core file of dying totem? Ok, when I have some more free time, maybe I'll recompile totem with debugging symbols and give feedback. gdb says Cannot access memory at address 0xf6f64000 That does not say much :-( And I tried some free WMA yesterday without problem. But it can be some other problem. I will wait for core file. But I still can try to compile mplayer. Yes, but it fails to compile with strange errors about asm files... Do you mean the latest snapshot? Because the released version 1.0rc2 is (with you widely known patches) working well. Yes, I've already compiled it (svn version). I had to to disable gcc optimization some times and to patch mlpdsp.c. Good to know, thanks. 3) I'd like to use MY graphic card, I've already bought it for about 70-100$ and it is not a small amount money for me... Maybe I should wait for OpenSolaris 10.02 of course You can ask the company which sold that graphic card to you for support. Not funny. And I don't want to change my card, I like it... Why does such strange advices appear? Because it is truth. OpenSolaris has the same open source driver as Linux. But ATi is producing also binary driver for Linux. Do you see the difference? I believe our X server team spoke with ATi (and later with AMD) several times, asking them for the same level of support. You can see the result. Ask ATi, not us. Or participate on that open source driver. That is the reality, you have 2 options. It is task for company, we can only volunteer if we have enough datasheets and volunteers to do it. Will you participate on development of that driver? 1) I'm admin, not a developer... 2) I haven't enough time 3) Is it a good practice we don't have it in OS, but you may write it...? :) Yes, it is good practice. It is the same practice in all operating systems, including closed source. You were only asking and asking. Even if you are only admin, you can contribute a lot. I see you were able to patchcompile mplayer for you. Why not to share such knowledge with the others? Yes, you cannot work on that driver probably, or not much enough. But you can use it, monitor the upstream and test it and report bugs (maybe with small patches from time to time). Even that is important contribution. And yes, you will be limited by limits of that driver for now. We all haven't enough time to support everybody's hardware. Many of us are only admins. But we are trying to do our best. 4) It's said on winehq site that Wine support with sound is available starting from snv_116, but 09.06 is snv_111b-based... When I'm trying to update to snv_117, ips tries to download approximately 330 Mb... Not very good. Why not very good? Just so many data were changed between build 111b and 117. Isn't it cool there is so huge progress? It's cool if traffic is free... I know. But if you want the latest bits, it costs :-( But I need to update to snv_119 to see my partition, and it's not ready. Yes and no. It depends on your knowledge. It is not available yet for simple click'n'click but you can have such support immediately if you know how to download/compile/apply. You are asking for something what is in main repository for few days only. And there were strange issues with transfering files (some network timeouts, happening only with pkg.opensolaris.org)... Did you report it on correct place (like indiana-discuss@), please? Yes :) Cool, thank you :-) Hopefully it resulted in some bug on defects.opensolaris.org And last... It is possible to run Oracle 10g R2 on Solaris/x64. It could work on OpenSolaris with some tricks... But there is Oracle 11g already. And it is supported on Linux without so many hacks. Do you know that OpenSolaris community is not developing Oracle software? Why are you asking here and not on Oracle support? I don't complain, I'm only explaining all issues which I had with OpenSolaris. I don't want to have a constructor (like RH 7.1). I want to have a normal system which just works without any magic actions and do what I need. And if it's a constructor, it should be a good constructor (compare ports collection and
Re: [osol-discuss] regretting for OS... (was ATI Radeon 1650 DRI)
Hi Alexander, I think you have already the most of things fixed, but let me comment this: Alexander píše v st 08. 07. 2009 v 05:27 -0700: Thank you all for replies... Nothing personal, but let's review my expreience with OpenSolaris as desktop system. 1) There were no support for extended partitions in OSOL 2009.06. It's a big disadvantage, cause I have a lot of data on NTFS-formatted logical drive on extended partition. No matter, I've said, there will be snv build 119 and everything will be ok. That is truth and it took several years to do it correctly. Our (OpenSolaris community) fault we were not investing more resources to it. But we reached the point, finally. 2) There are not enough gstreamer plugins (all suggestions are to BUY fluendo codecs). Why should I do it, if there is gstreamer-plugins-ugly? I can compile it... Yes, but after compilation totem dies trying to play WMA files To fix this we need one thing from you - how does it die? Can you distribute some short WMA file with which I can reproduce it, so I can try to root cause it and fix it? Or give me core file of dying totem? And yes, we must care about patents. Some members of OpenSolaris community would be heavilly impacted otherwise. But I still can try to compile mplayer. Yes, but it fails to compile with strange errors about asm files... Do you mean the latest snapshot? Because the released version 1.0rc2 is (with you widely known patches) working well. 3) I'd like to use MY graphic card, I've already bought it for about 70-100$ and it is not a small amount money for me... Maybe I should wait for OpenSolaris 10.02 of course You can ask the company which sold that graphic card to you for support. It is task for company, we can only volunteer if we have enough datasheets and volunteers to do it. Will you participate on development of that driver? 4) It's said on winehq site that Wine support with sound is available starting from snv_116, but 09.06 is snv_111b-based... When I'm trying to update to snv_117, ips tries to download approximately 330 Mb... Not very good. Why not very good? Just so many data were changed between build 111b and 117. Isn't it cool there is so huge progress? But I need to update to snv_119 to see my partition, and it's not ready. Yes and no. It depends on your knowledge. It is not available yet for simple click'n'click but you can have such support immediately if you know how to download/compile/apply. You are asking for something what is in main repository for few days only. And there were strange issues with transfering files (some network timeouts, happening only with pkg.opensolaris.org)... Did you report it on correct place (like indiana-discuss@), please? And last... It is possible to run Oracle 10g R2 on Solaris/x64. It could work on OpenSolaris with some tricks... But there is Oracle 11g already. And it is supported on Linux without so many hacks. Do you know that OpenSolaris community is not developing Oracle software? Why are you asking here and not on Oracle support? So, at the end we have the following disadvantages of running OpenSolaris as desktop system 1) insufficient of drivers; Not on my 4 different desktop x86 systems (2 desktops, 2 laptops). I must be lucky man. 2) insufficient of codecs; Not for me. 3) insufficient of 3-rd party software support... Yes, some 3rd parties are not supporting OpenSolaris. And there are 3rd parties not supporting other operating systems. What a surprise. Ask those parties, volunteer there. OpenSolaris community is not good place for such ranting. No, seriously. I really like OpenSolaris (I support two SR servers, running on it). Zones, ZFS, DTrace are perfect tools for server systems. But in my mind for desktop OpenSolaris is not enough. Everything is going to work (if you pay money or wait for next releases or work for at least several days on this problem...). Maybe when OSOL 2010.02 comes out, I'll give it a chance... But now as a desktop OS Ubuntu rocks... It just works. Without any tambourine dances. It can rocks for you. Not for me. As 10+ years-Debian user I tried Ubuntu several times (and I needed to use that ATi binary driver, OMG). No, thanks. One thing you should learn if you want to participate in good communities - complaining is important part of the contribution. But without enough data and/or complaining on proper places and/or offering help, it is only ranting if no good effect for you nor the community. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] GCC 4.4: Can we handle it?!?
Hi Ken, V čt, 11. 06. 2009 v 20:57, ken mays píše: Hello, Since developers are getting more involved in using the GCC compiler and especially the GCC 4.4.x compilers, I started wondering why not migrate to GCC 4.4.x sooner than later?? We have more community developers building, testing, and reporting on GCC 4.4.x than before. What is the price of admission for users/developers to enter the gates of GCC 4.4.x ?? Write ARC case, submit webrev, that is the admission I think. Or prepare spec file. I think it will be welcomed a lot :-) Also it would be good to try it with ON and fix all bugs in GCC. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Anyone else had any authentication problems in b113?
Hi Ian, CCing sparks-discuss@, Bccing opensolaris-discuss@, probably better for such discussion. Ian Collins píše v so 16. 05. 2009 v 22:14 +1200: I just upgraded a system to b113 and I'm unable to login with any user other then root. From which build? The system is an LDAP client, getent passwd shows all users, but su - user give an unknown user error. What about other local users, are they working? Can you show your pam.conf? Can you enable PAM stack debugging and look which PAM module fails? Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Printer for Open Solaris
Hi, V pá, 17. 04. 2009 v 00:49, Andrius píše: Alex Smith (K4RNT) wrote: Any printer that supports Postscript is the easiest to set up, but if you can find it in Foomatic, it'll work in OpenSolaris. On Thu, Apr 16, 2009 at 4:20 PM, Andrius ziniatink...@gmail.com mailto:ziniatink...@gmail.com wrote: Lads, would you reccomend please what kind of printer should suit for Open Solaris please? Regards, Andrius ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org mailto:opensolaris-discuss@opensolaris.org -- ' With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.' Those words were uttered by Judge Aaron Satie as wisdom and warning... The first time any man's freedom is trodden on we’re all damaged. - Picard, quoting Judge Aaron Satie - Alex Smith (K4RNT) - Nashville, Tennessee USA So why Canon PIXMA iP 2600 does not work? This one? http://www.openprinting.org/show_printer.cgi?recnum=Canon-PIXMA_iP2600 This printer entry is not yet included in the Foomatic packages Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Log messages when using an Linux (openfiler 2.3) iscsi target - a problem?
Hi Alastair, I am CCing storage-discuss@ as the best place for this question and Bccing the rest. V út, 14. 04. 2009 v 18:00, Alastair Neil píše: I see these messages in my logs of my snv_111 system. I see messages for every target, the targets are openfiler 2.3 Linux systems. The switches are 24 port dell powerconnect gigabit switches with jumbo frames enabled and the interfaces are all intel eepro 1000 ans all have MTU set to 9000. Apr 14 11:11:49 vsnfs-01Not enough sense information Apr 14 11:11:49 vsnfs-01 scsi: [ID 583861 kern.info] sd12 at iscsi0: name iqn.2006-01.com.openfiler%3Atsn.vsof-02-u20001,0, bus address iqn.2006-01.com.openfiler%3Atsn.vsof-02-u20001,0 http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/common/io/scsi/targets/sd.c#16999 I do not know from where SUN_MIN_SENSE_LENGTH as 4 is comming but it is there for many years and looks reasonable. Several possibilities: 1) Solaris is not decoding SCSI packet correctly 2) your targets have problems Could you look at data on TCP level and decode them with wireshark? Am I missing something in the setup? I am trying to use these targets as mirrored elements of a zpool. I do not know Linux iSCSI targets, so it can be config issue. Any pointers greatly appreciated __ Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [on-discuss] Emergency project to rescue Opensolaris from IBM (was: Re: Possible IBM aquisition of Sun)
Hi, ольга крыжановская píše v Po 23. 03. 2009 v 15:17 +0100: On 3/23/09, Alexander Eremin ere...@milax.org wrote: On Mon, 2009-03-23 at 14:51 +0100, Martin Bochnig wrote: 2009/3/23 ольга крыжановская olga.kryzhanov...@gmail.com: On 3/23/09, Malte Hahlbeck malte+sola...@gissmo.net wrote: What would happen to Opensolaris and other open sourced software like Glassfish, Netbeans etc.? Solaris customers are migrated to Linux. There's no point to allow competition to own products. IBM will be committed to existing contracts but no new contracts will be allowed. Называешь ли ты один фантастическое будущее? Ну страшно! (Dou you call this a fantastic future? Not nice.) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org May be this not so terrible. I think that opensolaris community will survive even in an underground ;) The community cannot survive without open code. Many parts of Opensolaris rely on closed sources. We need an emergency project to make as many parts of Opensolaris open source or replace them with open source. You could participate on Emancipation project for long time: http://opensolaris.org/os/project/emancipation/ We are wasting time with this thread. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] idmap seems to not use all information available in ActiveDirectory
Hi Florian, CCing sparks-discuss@ as better place for Naming topics, BCcing opensolaris-discuss@ I have no personal experience with MS AD, so only short question here - can you dump all attributes of Linuxadmin object as it is represented by AD to LDAP protocol, please? Best regards, Milan V út, 10. 03. 2009 v 17:34, Florian Manschwetus píše: This is exactly what I have done now, but doing a getent group linuxadmin shows me only: r...@filer2:~# getent passwd fm1007 fm1007:x:10023:1002:Florian Manschwetus:/home/fm1007:/bin/bash r...@filer2:~# getent group linuxadmin LinuxAdmin::100: On my linux machine (configured in the same way): trac:~# getent passwd fm1007 fm1007:*:10023:1002:Florian Manschwetus:/home/fm1007:/bin/bash trac:~# getent group linuxadmin LinuxAdmin:*:100:schnitt,fm1007,jschroed,erwin my ldap config script: cat ldapclientconfig.sh #!/bin/bash /usr/sbin/ldapclient -v manual \ -a credentialLevel=self \ -a authenticationMethod=sasl/GSSAPI \ -a defaultSearchBase=DC=ntdom,DC=changed,DC=de \ -a domainName=ntdom.changed.de \ -a defaultServerList=dc1,dc2 \ -a defaultSearchScope=sub \ -a attributeMap=passwd:gecos=displayname \ -a attributeMap=passwd:homedirectory=unixHomeDirectory \ -a objectClassMap=shadow:shadowAccount=user \ -a objectClassMap=group:posixGroup=group \ -a objectClassMap=passwd:posixAccount=user \ -a serviceSearchDescriptor=group:ou=Groups,dc=ntdom,dc=changed,dc=de?sub \ -a serviceSearchDescriptor=passwd:ou=Accounts,dc=ntdom,dc=changed,dc=de?sub I really need a hint. thx, florian Julian Pullen schrieb: Florian, I am not on the opensolaris-discuss alias so please include me on reply. idmap is for mapping Solaris identities to Windows identities. It does name based mapping. It coverts SIDs, UIDs and GID to names and hence maps a Windows name to a Solaris name. We currently don't have a naming backend that understands Active Directory, but you can use the current LDAP backend if you use Windows Identity Mangement for UNIX and a some LDAP attribute mapping. See http://www.sun.com/bigadmin/features/articles/kerberos_s10.jsp Regards Julian Florian Manschwetus wrote: Our ActiveDiretory (based on 2003 R2) is extended using ServicesForUnix, so there are fields for numericUID, numericGID, unixhomedir, loginshell and so on, in short all (at least for my linux stuff) what is needed to define *nix users. But idmap doesn't use it, it generates new mappings on demand what is not what I intended. Could some one tell me more detailed stuff about the fields used for mapping and what data is expected to be there. I have read a lot of the referenced documentation but nothing seems to really fit to my problem / setup. thanks, florian ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org __ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] isaexec?
Hi, V po, 09. 02. 2009 v 16:05, casper@sun.com píše: However, in OpenSolaris I can see few deviations from this principle: /usr/bin/amd64 contains more binaries than /usr/bin/i86 and /usr/bin/pentium_pro+mmx together; for example, take a look at `ls' or `sdl-config': /usr/bin/amd64/ls is 64-bit binary /usr/bin/i86/ls is not present /usr/bin/pentium_pro+mmx/ls is not present /usr/bin/ls is 32-bit binary of ls, not a link to isaexec so when user types `ls', 32-bit version of ls is always being called, regardless of architecture. 64-bit version is being useless unless called directly as /usr/bin/amd64/ls. If someone intended to use optimized version of ls, he had to ship 32-bit binary in /usr/bin/i86 and made /usr/bin/ls a link to isaexec I think the reason was optimization: make ls fast and save an execve. See some bits in CR 6248065. It is not about optimization so much. Now take a look at sdl-config: it's a shell script which outputs flags for compiling application using SDL library. /usr/bin/amd64/sdl-config is a script which outputs flags for 64-bit library /usr/bin/pentium_pro+mmx/sdl-config is a script which outputs flags for 32-bit library, SSE, SSE2, CMOV enabled /usr/bin/sdl-config is a script which outputs flags for generic 32-bit library so calling sdl-config will always print flags for most generic 32-bit version, ignoring more optimized ones. I have no idea about sdl-config. Interesting usage, which has it points, but no idea why it was done in this way. SDL maintainer should know. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] isaexec?
Hi Alex, V po, 09. 02. 2009 v 18:21, Alexander Vlasov píše: Hello, CR 6248065 is quite interesting. However, some reasons from 2005 aren't much applicable nowadays (system is more-or-less 64-bit-proof now). I would say there are many systems 32-bit only (and there is some probability even 32-bit SPARC kernel will return). Nevermind, do not argue here, argue in Bugster (e.g. by adding SR, public comments etc.) :-) And well, maybe it's not about optimization, it's more about policy for using isa directories. Which is ARC thing and the man commentting that CR knows ARC well :-) SDL case is absolutely unclear: if one knows which ISA to use, he doesn't need to call specific sdl-config, but rather can manually use appropriate dirs in -L flag; if one doesn't know which ISA to use, presence of many versions of sdl-config wouldn't help. Why should somebody hack such thing if he can use script? I agree that /usr/bin/sdl-config, as script, could be done in some improved way, to select the best possible config on your platform. But again, contact SDL maintainer, which is probably somebody from JDS/Desktop community. Best regards, Milan Milan Jurik wrote: Hi, V po, 09. 02. 2009 v 16:05, casper@sun.com píše: However, in OpenSolaris I can see few deviations from this principle: /usr/bin/amd64 contains more binaries than /usr/bin/i86 and /usr/bin/pentium_pro+mmx together; for example, take a look at `ls' or `sdl-config': /usr/bin/amd64/ls is 64-bit binary /usr/bin/i86/ls is not present /usr/bin/pentium_pro+mmx/ls is not present /usr/bin/ls is 32-bit binary of ls, not a link to isaexec so when user types `ls', 32-bit version of ls is always being called, regardless of architecture. 64-bit version is being useless unless called directly as /usr/bin/amd64/ls. If someone intended to use optimized version of ls, he had to ship 32-bit binary in /usr/bin/i86 and made /usr/bin/ls a link to isaexec I think the reason was optimization: make ls fast and save an execve. See some bits in CR 6248065. It is not about optimization so much. Now take a look at sdl-config: it's a shell script which outputs flags for compiling application using SDL library. /usr/bin/amd64/sdl-config is a script which outputs flags for 64-bit library /usr/bin/pentium_pro+mmx/sdl-config is a script which outputs flags for 32-bit library, SSE, SSE2, CMOV enabled /usr/bin/sdl-config is a script which outputs flags for generic 32-bit library so calling sdl-config will always print flags for most generic 32-bit version, ignoring more optimized ones. I have no idea about sdl-config. Interesting usage, which has it points, but no idea why it was done in this way. SDL maintainer should know. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] isaexec?
Hi Casper, V po, 09. 02. 2009 v 18:23, casper@sun.com píše: AFAIK, when we first did 64-bit SPARC, Kenbus was a very important benchmark; it suffered when ls needed to use isaexec. My memory could be failing, though. I cannot argue for or against, my memory is shorter :-) Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] *LOL* : - Xorg on SPARC will not work with any driver except the included wsfb (which only works on m64 graphics in 8-bit mode) unless you get updated matching driver packages from
Hi, Joerg Schilling píše v út 30. 12. 2008 v 13:49 +0100: Timo Schoeler timo.schoe...@riscworks.net wrote: thus Alan Coopersmith spake: Octave Orgeron wrote: Agreed.. this is definitely pushing the SPARC workstation market to an end. Sun already ended sales of SPARC workstations several months ago - there's no more pushing to that point to do. IBM sells POWER-based workstations. I like workstations, I like *real* workstations even more. Sun should not rely on x86/x64-only machines, IMHO. If the CPUs that are used in the new 9000 series are available for an affordable price, Sun could make Spars workstations. The old Sun sparc CPUs are just not in the right class for a today's workstation. another possibility can be based on CMT RD kit released few days ago. Yes, it's Niagara core, so generic desktop isn't the target there but somebody could find it good enough. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SRP target project
Hi, not mentioning that Sun is distributing unbundled IB SRP initiator for some time. Best regards, Milan Peter Dunlap pÃÅ¡e v Ät 18. 12. 2008 v 13:17 -0700: SRP as SCSI RDMA Protocol is an ANSI T10 standard: http://www.t10.org/cgi-bin/ac.pl?t=ff=srp-r16a.pdf http://www.t10.org/cgi-bin/ac.pl?t=ff=srp2r00a.pdf So yes there is a name collision between ANSI SRP and IETF SRP but SRP still seems like the logical name for this project. -Peter Nicolas Williams wrote: On Thu, Dec 18, 2008 at 11:39:29AM -0800, Chris Wood wrote: iSER and SRP are unot/u the same. iSER (along with iWARP) is a potential replacement for SRP. It just turns out that there are a lot more SRP initiators and devices out there than iSER right now. If we want to play in the IB attached storage arena right now, then SRP is the name of the game. I'd never heard of this use of 'SRP'. A Google search for iSCSI SRP finds results related to both, RDMA (3 results on the first page) and authentication (7 results...), but mostly the latter. Very, very, unfortunate, this. *sigh* A search for iSCSI SRP CHAP returns 6,860 results, while a search for iSCSI SRP iSER returns 4,310 results; iSCSI SRP RDMA returns 5,790 results, and iSCSI SRP security returns 12,800. Did I mention how unfortunate this is? Nico ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Experimental Bind packages
Hi, I know there are some people using OpenSolaris as DNS server with Bind. In SFW there is Bind 9.3, a bit older these days, so I prepared experimental Bind packages for Nevada, version 9.6.0b1 for now: http://xylab.cz/bind/ It's replacement for SUNWbind package (SVR4). No support available (you can send bugreports directly to me). I have no plans to integrate it, it's the experimental package only. If somebody is interested in new Bind in SFW (some more stable version, of course), I can sponsor his work. I plan to add Bind 9.5.1 (when released) and sun4v optimized Bind. Also, is there some interest in special naming mailing list on opensolaris.org? I know there are two related project lists (sparks and duckwater), but no naming wide list. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Account only available when LDAP is not?
Hi Johan, Johan Hartzenberg píše v Po 27. 10. 2008 v 20:20 +0200: On Mon, Oct 27, 2008 at 6:25 PM, Josh Rivel [EMAIL PROTECTED] wrote: Does not seem to work and then local accounts (i.e. root) are not seen as valid ones unless LDAP is down (which is not what we need) We just need a single account to only be able to login if LDAP is down. I suppose I could put something into that users .profile checking for the LDAP server and if it's there to log itself out sort of thing. Not ideal, but might suit the purpose for now. How about create an account locally AND in LDAP, but the one in LDAP is set to not be able to login. Then in nsswitch.conf you set it to check ldap before files. I'm not sure though, whether cached information may cause it to fail - eg if the user tries to login with the admin account and shortly after, while it is still cached on the system, ldap becomes unavailable... That system may continue to refuse access to the specific account based on cached information (which could then be solved by a reboot) Login is not cached and it's pam.conf relevant (mostly). Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Account only available when LDAP is not?
Johan Hartzenberg píše v Út 28. 10. 2008 v 16:16 +0200: On Tue, Oct 28, 2008 at 1:10 PM, Milan Jurik [EMAIL PROTECTED] wrote: Login is not cached and it's pam.conf relevant (mostly). I fail to see how this is more relevant to pam.conf than to name services, seeing as the OP asked for a solution which makes a local name service entry only available when the network name service is unavailable. But then I may be missing something because I don't know pam all that well. She said she would call me. From my understanding they want to have something like failover account available. Authentization and account management is PAM responsibility, not name services responsibility. E.g. if they are using pam_ldap, then playing with passwd in nsswitch.conf (which is about passwd database, not authentization) has no requested effect. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] VIA VT6420 SATA RAID Controller not working
Hi, Pawel Wojcik pÃÅ¡e v po 22. 09. 2008 v 14:07 -0700: Joerg, I do not know if VT8237R is ahci-compliant - it was not yet verified to work with the Solaris ahci driver (VT8251 was verified). Is BIOS mentioning somewhere AHCI mode? Using Knopix, find the pci vendor id/device id of this controller. You can try to add /etc/driver_aliases file either ahci pci1106,0591(providing that this is correct vid/did value) or, a bit dangerous, ahci pciclass, 010400 IF this chip is ahci-compliant, it may work, considering that ahci driver does not explicitly check vendor id. The caveat is, that you may have to further exeperiment with RAID settings to let system BIOS see unconfigured devices. There will be no RAID operation in Solaris, but if the BIOS can see individual disks that are not configured into RAID volumes and such disks may be considered as boot device, AND Solaris ahci driver really works with this chipset, then you my be able to used attached disks. This, however, is by no means a general solution to deal with software RAID controllers. -Pawel P.S. Let me know, if this works. In my case no: update_drv -a -i 'pci1106,3149' ahci NOTICE: ahci0: hba AHCI version = 0.0 WARNING: ahci0: Don't support AHCI HBA with lower than version 1.0 Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] VIA VT6420 SATA RAID Controller not working
Hi Joerg, Joerg Schilling pÃÅ¡e v Ät 25. 09. 2008 v 12:49 +0200: Milan Jurik [EMAIL PROTECTED] wrote: There will be no RAID operation in Solaris, but if the BIOS can see individual disks that are not configured into RAID volumes and such disks may be considered as boot device, AND Solaris ahci driver really works with this chipset, then you my be able to used attached disks. This, however, is by no means a general solution to deal with software RAID controllers. -Pawel P.S. Let me know, if this works. In my case no: update_drv -a -i 'pci1106,3149' ahci NOTICE: ahci0: hba AHCI version = 0.0 WARNING: ahci0: Don't support AHCI HBA with lower than version 1.0 This is what I did see also two days ago... It is a shame that Solaris does not have a useful SATA support many yaears after the move towards SATA dis start. The situation is improving, slowly, but improving. Look at driver-discuss@/storage-discuss@/code-discuss@, you will see people are working on drivers for various SATA controllers (like Areca new driver putbacked few days ago). Currently, there are only _very_ few controllers supported and none of the other supported controllers are a useful selection. - A controller with the price of 3 server grade disks is no option if you like to connect a single disk. - Buying a new Intel based board is no option and the supported Intel chips are not available in separate PCI cards. - PCIe is no option for a 3 year old PCI board purchased in December 2005. Note that I intentionally selected PCI only as in 2005 there have been no decent controllers with other than PCI and there was even PCIx (disk controllers only available) and PCIe (network controllers only). Note that this is a four core system with two Opteron 880 (2400 MHz) and that is is only ~ 10% slower than a recent Intel Core Duo Quad Dell system. - The board includes on-board SATA that is able to operate at 1.5 GBit/s into system memory. It works on Linux. - PCI is only the second choice for a disk that delivers 110 MB/s sustained, as PCI only allows ~ 80 MB/s. - I tried a SIL 3114 controller. It has bad firmware that completely hangs up the BIOS at the time the first connected disk is conntected. This controller is no option as it does not allow to reboot the syste. It works with Linux in native SATA mode, so it autodetects a disk connected after boot. Conclusion, there is currently _no_ option to connect a SATA disk to a decent home system except by using a SATA - PATA or SATA - USB adaptor. I'm using USB for now. Not optimal, but it's cheaper than additional card. BTW: porting a Linux driver is not an option as long as Sun did not prove that there is a will for a real collaboration with the community (see the distressing actions of some Sun Engineers against the star integration project). And? Must your driver be integrated in ON? I believe you can maintain it outside of ON, if you want to ignore others. There are public interfaces, so there is no need to maintain it in ON. Also, if you will decide to port driver for it, look at *BSD, they have more friendly license ;-) Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] snv_98 iso
Hi Shawn, Shawn Protsman pÃÅ¡e v Ät 25. 09. 2008 v 11:52 -0700: Bill Shannon wrote: I'm going to try installing 2008.05 and upgrade my way to snv_98. I've just installed 2008.05 inside VMware Fusion. Previously I was using the old SXDE. Now, I'd like to update the system and get the dev tools installed but I'm not sure how. If someone can point me in the right direction I'd really appreciate it. I found a blog that had some steps but they aren't working. [EMAIL PROTECTED]:~$ head -1 /etc/release OpenSolaris 2008.05 snv_86_rc3 X86 [EMAIL PROTECTED]:~$ pfexec pkg refresh [EMAIL PROTECTED]:~$ export PKG_CLIENT_TIMEOUT=300 [EMAIL PROTECTED]:~$ pfexec pkg install SUNWipkg DOWNLOADPKGS FILES XFER (MB) Completed 12/12 606/606 61.98/61.98 PHASEACTIONS Removal Phase 49/49 Update Phase 989/989 Install Phase246/246 [EMAIL PROTECTED]:~$ pfexec pkg image-update Traceback (most recent call last): File /usr/bin/pkg, line 50, in ? import socket File /usr/lib/python2.4/socket.py, line 45, in ? import _socket ImportError: ld.so.1: python2.4: fatal: relocation error: file /usr/ lib/libnsl.so.1: symbol MD5Init: referenced symbol not found I guess I'm a little clueless. As it is development release, it isn't so easy. Look at http://opensolaris.org/os/project/indiana/resources/rn3/image-update/ Your mistake was here I think: [EMAIL PROTECTED]:~$ pfexec pkg install SUNWipkg No version, you updated too much to live BE... I made the same mistake. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How to debug a weird nis+ issue?
Hi, V út, 23. 09. 2008 v 04:26, Yue Chen píše: Hi Peter It is as followings passwd: compat files nis This is wrong config for compat mode shadow: compat files nis shadow isn't using nsswitch, it's in conjunction with passwd backend group: files nis See manpage of nsswitch.conf how compat mode should be configured. Also, it's better to use pam_list for managing access to system. Best regards, Milan On Thu, Sep 18, 2008 at 9:36 AM, Yue Chen [EMAIL PROTECTED] wrote: Hi everyone I have a host installed with NIS+ client. There is a user named jsn in NIS server. His login shell is /bin/true. So he can not log on my host by default. Now I wanna grant his access so I added following line into /etc/passwd. +jsn::/bin/tcsh However, sometimes he is still unable to log on my host. To debug, I wrote a test binary using getpwnam to grab the user info and then check pw-pw_shell. To my surprise, the value for pw_shell is rather unstable. Sometimes it is /bin/tcsh (login is ok), sometimes it is /bin/true (login fails). How can I dig deeper on this weird issue? This issue almost drives me crazy. What does the passwd entry in your /etc/nsswitch.conf file look like? (Are you using compat?) -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] VIA VT6420 SATA RAID Controller not working
Hi Joerg, V po, 22. 09. 2008 v 17:58, Joerg Schilling píše: Pawel Wojcik [EMAIL PROTECTED] wrote: Solaris does not support (so far) SATA controllers that advertise themselves as RAID controllers. Your VIA controller shows pci class-code 00010400. Try to change BIOS setting to use either IDE or AHCI mode for this controller/ I am not sure that Solaris will work with it in AHCI mode, but should work in IDE mode (or legacy/compatible mode). We will soon allow such software RAID controllers to be used by Solaris, but not yet... I could not find a way to set up PATA compat in the BIOS. Would it help to add a line: ahci pciclass,010400 to /etc/driver_aliases? No, it wouldn't, the only way is to switch in BIOS or something else? Is it that SATA as additional sata interface (aka additional software RAID controller)? Do you know name and type of your mainboard. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] VIA VT6420 SATA RAID Controller not working
Hi Joerg, V po, 22. 09. 2008 v 18:15, Joerg Schilling píše: Milan Jurik [EMAIL PROTECTED] wrote: Would it help to add a line: ahci pciclass,010400 to /etc/driver_aliases? No, it wouldn't, the only way is to switch in BIOS or something else? Is it that SATA as additional sata interface (aka additional software RAID controller)? Do you know name and type of your mainboard. It is a MSI K8T Master2-FAR7 No way to switch that additional SATA controller to pATA legacy mode. AHCI support of this controller isn't very good also. Could you look at BIOS of this controller (see appendix A of the manual) and check if you didn't enable RAID on it? I have similar system at home so I could check later this week if there is possibility to access it from Solaris. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] VIA VT6420 SATA RAID Controller not working
Joerg, Joerg Schilling pÃÅ¡e v po 22. 09. 2008 v 19:14 +0200: Milan Jurik [EMAIL PROTECTED] wrote: It is a MSI K8T Master2-FAR7 No way to switch that additional SATA controller to pATA legacy mode. AHCI support of this controller isn't very good also. Could you look at What do you understand here by this controller isn't very good also? I wrote AHCI support of this controller, not this controlller. It's old, poorly designed SATA controller, with known limits (e.g. bad compatibility with SATAII) I did not see problems when booting a Knoppix DVD. VIA wrote Linux driver for it some time ago. BIOS of this controller (see appendix A of the manual) and check if you didn't enable RAID on it? I have similar system at home so I could check later this week if there is possibility to access it from Solaris. Neither the BIOS menus nor the manual did show a hint on how to switch to PATA legacy mode. There are three possibilities on some SATA controllers: a) operate in Legacy mode - for compatibility reasons - not available in SATA controller from VT8237R b) operate in SATA mode - this one could work with ahci driver in your case, maybe c) operate in RAID mode - this one is advertised by your controller now During system boot, there is possibility to enter configuration of this SATA controller, just press Tab when POST is asking for it. Look if you can change config of it to non-RAID somehow But looking at documentation of your mainboard, I don't believe it will work with Solaris drivers today. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] BIND update?
Hi Kyle, V st, 06. 08. 2008 v 17:50, Kyle McDonald píše: Hi all, Where can I look to be able to tell if NV will be , or has been, updated with a version of BIND that has the latest exploit patches installed? To Sun Alert or blogs.sun.com/security While NV policy is production code all the time, I understand that it's still not totally considered production environment, and therefore integrating these patches might not be a high priority. I'm just looking to guage if/when I should go compile it from source - Actually I've already started that. Isn't Bind 9.3.5-P1 part of build 95? If all will go well, I will integrate improved 9.3.5-P2 in the next days, probably for build 97. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] self-compilenced software
Hi, V ne, 20. 07. 2008 v 09:52, Bruno Damour píše: Hello, Just wondering, where should in your opinion self-compiled software be installed ? FreeBSD has /usr/local and there is /opt ? Thanks in advance, Bruno man filesystem Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Increadible slow when power cord is unplugged
Hi Roman, V st, 25. 06. 2008 v 08:52, Roman Morokutti píše: Is it just shutdown so slow? Or better - what's slow? It is overall a bit languidly. Startup time isn't significant slower but was so in recent versions before b91 as if it was waiting for some timeouts. Startup has now been accelareted. Some timeouts? What about verbose boot, do you see the source of such timeouts? But especially the shutdown last extremely long. And the overall feeling is that some processes wait for some event or so. I know Some processes? this is very vague. But maybe there are some diagnostic commands which could reveal this latency. The main time I spend waiting is kmdb, dtrace, vmstat, iostat etc. ? The first two should be possible to use during boot, but kmdb could hide the slowness between the message Going down on signal 15 ... and the physical shutdown. Just guessing - SMF has some problem with service monitoring status of power cord? Like dbus? But as said before. With AC (power cord is plugged in) those problems are not present. I always shutdown with init 5, or reboot with init 6 respectively. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Increadible slow when power cord is unplugged
Hi Roman, Roman Morokutti píše v Út 24. 06. 2008 v 09:08 +0200: Hi, I am currently running SXCE b91. My laptop is extremely slow when running without power cord, in other words, when running on battery. For shutdown it last about 4 minutes. With power supply (cord), the shutdown is done in about a minute. Is it just shutdown so slow? Or better - what's slow? Best regards, Milan What can I do to speed up the latency of the whole system when running on battery? By the way, this behaviour exists since I use SXCE. Roman. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] I give up.
Hi Mark, which ThinkPad? wpi0 could mean T60 or R60, both I know and both work well for me and my friend. Could we go off this list and discuss it directly, please? Best regards, Milan Mark Kaiman píše v Čt 05. 06. 2008 v 06:49 -0700: I installed OpenSolaris on my ThinkPad a couple of weeks ago, and I have never been able to get it to work. The wpi0 and e1000g drivers just dont work. I have posted on these forums and on usenet and received some suggestions. I have tried every possible combination of wired and wireless internet. WPA, WEP and no encryption. Let the cable modem reset to a new MAC address. Enable NWAM. Disable NWAM. Endless restarting NWAM. Endless wificonfig connect commands. NOTHING WORKS. I just have to conclude that OpenSolaris isn't ready for prime time and wait for the next release. In contrast, I put SLED 10 on the same ThinkPad and it works fine. Full connectivity. I really want to use Solaris and I wish someone could convince me otherwise. Sun could do a better job supporting people who want to use and enjoy their OS. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Wireless USB Keyboard/mouse
Hi Fernando, you are not the only one, I have the same problem. See http://bugs.opensolaris.org/view_bug.do?bug_id=6674852 Responsible engineer is working on the fix. Best regards, Milan Fernando Ochoa de Zuazola píše v Ne 23. 03. 2008 v 23:08 +0100: Hello, Yes, it's a lenovo keyboard/mouse, the product number of IBM is 73P4088 Regards, Fernando. -Mensaje original- De: Milan Jurik [mailto:[EMAIL PROTECTED] Enviado el: martes, 18 de marzo de 2008 16:02 Para: Fernando Ochoa de Zuazola CC: opensolaris-discuss@opensolaris.org Asunto: Re: [osol-discuss] Wireless USB Keyboard/mouse Hi, which model of set? Lenovo wireless set? Best regards, Milan V út, 18. 03. 2008 v 11:17, Fernando Ochoa de Zuazola píše: Hello, I have SXCE 81 on a thinkpad T60. I have a wireless USB keyboard/mouse connected, mouse is working OK, by keyboard only works in grub display, after that, it doesn't work in text or graphic desktop enviroments. Any idea? Regards, fernando. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org This e-mail and any attachments may contain confidential or privileged information. Any unauthorised copying, use or distribution of this information is strictly prohibited. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Wireless USB Keyboard/mouse
Hi, which model of set? Lenovo wireless set? Best regards, Milan V út, 18. 03. 2008 v 11:17, Fernando Ochoa de Zuazola píše: Hello, I have SXCE 81 on a thinkpad T60. I have a wireless USB keyboard/mouse connected, mouse is working OK, by keyboard only works in grub display, after that, it doesn't work in text or graphic desktop enviroments. Any idea? Regards, fernando. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Indiana review
Hi, Considering Solaris' rbac capabilities as well, I look for root to be extinct in the not too distant future. Roles / Profiles are a far better way to accomplish this. I strongly disagree, for two reasons: 1. if the system engineering has done their job correctly, no interactive logging in of any kind, by either the root or odrinary users should take place on the system - ever 2. RBAC is present only on Solaris and therefore useless in homogenous environments; sudo would have been a much better choice, especially because it makes system administration consistent and homogenous. I do not at all appreciate RBAC. And I don't like sudo. Too strange thing. And in that case we should forget about ZFS (because it is administred in different way), dtrace (strange, it is not on AIX or HP-UX), FMA, what else? Time to forget ACLs, they are not managed in the same way around all OSes... RBAC is Solaris way, correct and clean. Not sudo hack. You can use it, nobody will stop you. But don't stop RBAC just only because you don't understand RBAC. Write sudo wrapper around RBAC, if you want. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] ATI new graphic cards roxx! Solaris drivers?
Hi, V čt, 15. 11. 2007 v 10:47, Orvar Korvar píše: I think, because they draw ca 20W in idle, while performing not as good as a GeForce 88000GT, but almost. I dont want a GeForce drawing ca 100W idle mode on my desktop computer. Hence, I must buy the new ATI 3870 model. The problem is, how are the solaris drivers yet? Have they come? Anyone working on these? What is the latest news, on ATI opening up the specifications? Look at radeonhd driver (use your prefered web search). I don't know if it supports already your model, but it should do it in near future (hopefully). It works under OpenSolaris, but you will need to compile it itself from source code. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] I'm losing my mind... Or I've missed some change in NV...
Hi, V čt, 15. 11. 2007 v 02:33, Kyle McDonald píše: James Carlson wrote: [EMAIL PROTECTED] might be a better match.] Ah. Good Call. Kyle McDonald writes: # ping gatekeeper ping: unknown host gatekeeper The same case works fine here. It sounds to me like a local problem of some sort. Are you on b74? Though I'm inclined to agree with you... I just don't know where else to look locally. I'll send the original message to the other alias. Try to stop svc:/system/name-service-cache:default svcadm disable svc:/system/name-service-cache:default Does it help? Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [indiana-discuss] [advocacy-discuss] [trademark-policy-dev] Project Indiana and the OpenSolaris name
Hi John, John Plocher pÃÅ¡e v Ät 01. 11. 2007 v 21:12 -0700: Brandorr wrote: Now you are telling another $foo distro maker, that all the other $foo distro makers that they are marginal $foo players. And that only Sun can make a real $foo distro? Am I misinterpreting your statement? Yes. I'm trying to say: I am telling another $foo distro maker that all the $foo distros are either compatible, derivative or incompatible $foo distross, as defined by the OpenSolaris community. In addition, the OpenSolaris community itself produces a distro that is compatible. Why is THE OpenSolaris distribution the most controversial, if it should be THE distribution? I'm not against Indiana, I think it is good idea and several interesting things is comming from it. Except two things: a) how it is cooperating with the community (and it is outside and inside of Sun, both sides are in same position around this cooperation...) b) if it should be the basic of OpenSolaris distro (including name of the project), it shouldn't make controversial decisions without the community These two things destroy the whole work of the Indiana group :-( They should change on of these two and the situation will be much better. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Memory requirements to install Solaris
Hi Dev, Dev Mazumdar pÃÅ¡e v so 25. 08. 2007 v 11:42 -0700: On 8/25/07, Dev Mazumdar [EMAIL PROTECTED] wrote: I have a laptop with 512MB RAM and even Windows Vista happily installs on this however Solaris won't saying that it needs 768M to install Developer Express. I even tried installling Solaris Express and it hangs trying to load up Java. Is there any way to get Solaris on this machine? have you tried the text based install? nacho ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org Yes I've tried text based install. I verified that 512MB ram is not sufficient for B70. This memory requirement is absolutely unacceptable. I agree. It is known issue (after integration of new installer) and it should be fixed in build 72. I hope so... Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Memory requirements to install Solaris
Hi Al, Al Hopper pÃÅ¡e v so 25. 08. 2007 v 16:43 -0500: On Sat, 25 Aug 2007, Dev Mazumdar wrote: On 8/25/07, Dev Mazumdar [EMAIL PROTECTED] wrote: I have a laptop with 512MB RAM and even Windows Vista happily installs on this however Solaris won't saying that it needs 768M to install Developer Express. I even tried installling Solaris Express and it hangs trying to load up Java. Is there any way to get Solaris on this machine? have you tried the text based install? nacho ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org Yes I've tried text based install. I verified that 512MB ram is not sufficient for B70. This memory requirement is absolutely unacceptable. Oh C'mon. 512Mb is not enough to run Windoze XP reasonably - even if If you would say 256 MB, then no objections. But 512MB is enough, WinXP are OS from time when 512MB was a lot. you can actually install it. With 1Gb memory DIMMs around $50 (or less), expecting to run a state-of-the-art OS in 512Mb is absolutely 50$? Too much. unacceptable. If you're serious about (Open)Solaris, then you're serious about your hardware. PS: Take a quick look at these two cost effective systems, each with 4Gb of RAM built by Bob Palowoda at: http://www.fiver.net/misc/solarisamdbox.html There are tons of desktops and laptops with 512MB of memory. And tons of small servers which have even less. All are usable. Even under OpenSolaris. If they survive Solaris Express installer. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Memory requirements to install Solaris
Hi Andrew, andrewk9 pÃÅ¡e v ne 26. 08. 2007 v 05:05 -0700: I agree. It is known issue (after integration of new installer) and it should be fixed in build 72. I hope so... Can you tell me what changes are being made to get this fixed? I think some magic around miniroot. There should be some CR that we are not able to install on 384MB/512MB of RAM. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] making zfs open enough [was Re: An Open Letter to the Solaris Community.]
Hi Josh, Josh Berkus pÃÅ¡e v út 14. 08. 2007 v 09:55 -0700: OSOL folks, I'm also, quite frankly, not clear on how it benefits the opensolaris project to have ZFS be more available to other operating systems. DTrace, certainly, because we're trying to get people to include DTrace probes in the middleware layer which will only happen if it's multi-OS. But why do we want to spread ZFS independant of OSOL? Sharing data between operating systems? Not locking users to just one filesystem, which is locked to operating system. Today we have two possibilities: a) Veritas is everywhere - commercial closed source b) FAT - MS has some patent for it and tried to do something around it, I think and not very good for data. Do you know another? ext2 maybe, but it is old. Sharing is the key benefit for OSol and open source. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] making zfs open enough [was Re: An Open Letter to the Solaris Community.]
Hi Matthew, Kaiwai Gardiner pÃÅ¡e v st 15. 08. 2007 v 08:17 +1200: On Tue, 2007-08-14 at 22:13 +0200, Milan Jurik wrote: Hi Josh, Josh Berkus pÃÅ¡e v út 14. 08. 2007 v 09:55 -0700: OSOL folks, I'm also, quite frankly, not clear on how it benefits the opensolaris project to have ZFS be more available to other operating systems. DTrace, certainly, because we're trying to get people to include DTrace probes in the middleware layer which will only happen if it's multi-OS. But why do we want to spread ZFS independant of OSOL? Sharing data between operating systems? Not locking users to just one filesystem, which is locked to operating system. Today we have two possibilities: a) Veritas is everywhere - commercial closed source b) FAT - MS has some patent for it and tried to do something around it, I think and not very good for data. Do you know another? ext2 maybe, but it is old. Sharing is the key benefit for OSol and open source. How about UDF - I mean, you can write to it, read it, its universally supported, it works on a variety of devices and its open and available. UDF is mostly for optical media I think. Possible to use for other media, of course, but I never heard that somebody is using UDF for its home/document directory. Probably possible, but usable, with all nice features which can bring new people to it? Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] File Events Notification API - PSARC/2007/027
Hi Matthew, Kaiwai Gardiner pÃÅ¡e v út 07. 08. 2007 v 15:36 +1200: On Mon, 2007-08-06 at 20:09 +0200, Milan Jurik wrote: Hi Matthew, I know I'm not right man who should answer you, as I'm from Sun... But look at it from another perspective: V po, 06. 08. 2007 v 19:18, Kaiwai Gardiner pÃÅ¡e: Agreed, but at the same driver - are drivers *truely* that secret? I mean, wpi for 3945 was developed in 'secret' - why? what possible loss of competitive advantage would it yield? looking at it from my angle, all I see are positives by way of consumers actually seeing and knowing that Sun are making/porting drivers to Solaris. Are you sure that Sun employees had access to 3945 development except the developer of it? The most of them didn't know about it. And it is way how distributed development happens - somebody (or some team) is working on something till point it is compilable or usable or just publicable. The level of this point is on the developer decision, as usual in open source world. Some developers are publishing all their steps, some are publishing something usefull for users. You had the access to source code of wpi at the same time as the most of Sun employees. Today you can find on bugs.opensolaris.org the responsible engineer for all accepted RFEs, why not to contact him if you want to help with development and/or testing of some particular RFE? BUt at the same time - if the 'community' knew that wpi was being worked on - Sun might have actually found people helping port it to Solaris :-) A small hear-ye hear-ye would have been on order. But this happend, the responsible engineer took related RFE and you could see that on bugs.opensolaris.org. I agree with one thing - bugster is very good tool, but its public interface is not very useful in case that you want to monitor some CR. I mean, if they're going to worry about 'competitive advantage' then why announce to the world support for a product that doesn't yet exist in the marketplace/still in development? I don't think that in wpi case it was about competitive advantage. It was just way how the most of drivers in open source are developed - by some small team (typically with just one member), which is publishing their results when they are ready for public, per their decision. You can go and ask for source codes earlier if you want. And maybe the team will do it for you. But the driver is opensource and ported by Sun - I know about the existance of wpi, what I didn't know about was Sun porting it to Solaris. Because you didn't monitor the RFE probably. Otherwise you would see that something happend and one man started to work on it. I know, not very simple these days. But still possible. And I don't know why File Events Notification API - PSARC/2007/027 is not public. You can see who made the putback - ask him, maybe he is not reading this list. Its very hard to know when there is no name attached to the put back as far as I see. http://mail.opensolaris.org/pipermail/onnv-notify/2007-April/007227.html - 6381975 solaris need centrino ipw3945 wifi support http://bugs.opensolaris.org/view_bug.do?bug_id=6381975 - now you know ;-) And I think that Brian is very active even in community to help people with this driver :-) He just worked hard to release something and even at that time he was ready to communicate with those who wrote e-mail to him (I know it :-) ). Things should be merged into the public tree, just like they're merged inside the company. Everything that occurs inside Sun should occur at the same time on the other side - if a case log as been updated, then it should be accessible to the public. But wpi wasn't merged to Sun tree significantly sooner (it tooks few minutes, that sync between ON gate inside and outside). The developer worked on his source code in his own workspace. As usual. Would it be better to put documentation out there before the code? That's typically PSARC and sometimes updates in Bugster. E.g. manpage is written after driver completition. Which docu? Its all about transparency in the development process; and if it means that developers think out aloud on ideas - I'd sooner see Sun programmers conduct regular brain farts on a blog and know there is some cranium activity about future Solaris development than just sitting on the side lines praying something is occurring in the deep crypt of Sun. Did you look at RFEs? Did you look at PSARCs? Did you look at projects on opensolaris.org? And can you show me some really big project where all developers are informing community about their actual work and future plans? Please, leave the decision about their openness on developers. Some prefer public development (lots of Sun employee), some are working in their own workspaces (lots of Sun employee). You want just big amount
Re: [osol-discuss] File Events Notification API - PSARC/2007/027
Hi Matthew, V út, 07. 08. 2007 v 14:40, Kaiwai Gardiner píše: On Tue, 2007-08-07 at 08:25 +0200, Milan Jurik wrote: But this happend, the responsible engineer took related RFE and you could see that on bugs.opensolaris.org. I agree with one thing - bugster is very good tool, but its public interface is not very useful in case that you want to monitor some CR. Hence my leaning towards Bugzilla - people give it a hard time but it is easy to keep track of favourite bugs etc. etc. Much more 'collabortative' - you can actually update submissions etc. etc. all of that should be available on the bugster. It is in bugster, in very good way (in my oppinion). But bugster is not open and that is the root cause of many issues, missing open CR management. And I don't know why File Events Notification API - PSARC/2007/027 is not public. You can see who made the putback - ask him, maybe he is not reading this list. Its very hard to know when there is no name attached to the put back as far as I see. http://mail.opensolaris.org/pipermail/onnv-notify/2007-April/007227.html - 6381975 solaris need centrino ipw3945 wifi support http://bugs.opensolaris.org/view_bug.do?bug_id=6381975 But these are hardly 'visable' forms of communication; its like saying, 'yes, there is documentation, read the source code'. I said it is possible, you must be more active. - now you know ;-) And I think that Brian is very active even in community to help people with this driver :-) He just worked hard to release something and even at that time he was ready to communicate with those who wrote e-mail to him (I know it :-) ). Then maybe its the opensolaris.org website maintainers not willing to create some buzz about what is being worked on. It is not osol.org website maintainers responsibility. That's typically PSARC and sometimes updates in Bugster. E.g. manpage is written after driver completition. Which docu? The SPARC information before putting the code in. When it appears on the ONNV change, I want to be able to read about it straight away. Push on exact PSARC authors. Communication doesn't have to go overboard, but a quick, 'this what we're doing now' would suffice - atleast show there is some pulse in the body - I go past parts of opensolaris.org and wonder if any of the people involved are alive because its so quiet. I think there is good pulse in the body and you can see that in many projects on osol.org, you should monitor more than just opensolaris-discuss list. This is open source world, nobody should dictate to others on which level they are communicating. I came from open source world and know the difference. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] File Events Notification API - PSARC/2007/027
Hi Joerg, V út, 07. 08. 2007 v 15:03, Joerg Schilling píše: Milan Jurik [EMAIL PROTECTED] wrote: Did you look at RFEs? Did you look at PSARCs? Did you look at projects on opensolaris.org? And can you show me some really big project where all developers are informing community about their actual work and future plans? Umm, Linux ? Are you sure about this? I spent lots of time in lkml... Lots of patches (even bigger) are comming from sky. Do we need to repeat mistakes from the Linux world? You have some parser for keyword Linux ;-) You have good opportunity to discuss the most of features in psarc process before integration. And in many cases even in stages like one page. But it is project team decision if they want to work on their project in private group or not. Like in the rest of world. And I don't agree that this level of freedom is bad thing. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] File Events Notification API - PSARC/2007/027
Hi Matthew, I know I'm not right man who should answer you, as I'm from Sun... But look at it from another perspective: V po, 06. 08. 2007 v 19:18, Kaiwai Gardiner píše: Agreed, but at the same driver - are drivers *truely* that secret? I mean, wpi for 3945 was developed in 'secret' - why? what possible loss of competitive advantage would it yield? looking at it from my angle, all I see are positives by way of consumers actually seeing and knowing that Sun are making/porting drivers to Solaris. Are you sure that Sun employees had access to 3945 development except the developer of it? The most of them didn't know about it. And it is way how distributed development happens - somebody (or some team) is working on something till point it is compilable or usable or just publicable. The level of this point is on the developer decision, as usual in open source world. Some developers are publishing all their steps, some are publishing something usefull for users. You had the access to source code of wpi at the same time as the most of Sun employees. Today you can find on bugs.opensolaris.org the responsible engineer for all accepted RFEs, why not to contact him if you want to help with development and/or testing of some particular RFE? I mean, if they're going to worry about 'competitive advantage' then why announce to the world support for a product that doesn't yet exist in the marketplace/still in development? I don't think that in wpi case it was about competitive advantage. It was just way how the most of drivers in open source are developed - by some small team (typically with just one member), which is publishing their results when they are ready for public, per their decision. You can go and ask for source codes earlier if you want. And maybe the team will do it for you. And I don't know why File Events Notification API - PSARC/2007/027 is not public. You can see who made the putback - ask him, maybe he is not reading this list. Things should be merged into the public tree, just like they're merged inside the company. Everything that occurs inside Sun should occur at the same time on the other side - if a case log as been updated, then it should be accessible to the public. But wpi wasn't merged to Sun tree significantly sooner (it tooks few minutes, that sync between ON gate inside and outside). The developer worked on his source code in his own workspace. As usual. Its all about transparency in the development process; and if it means that developers think out aloud on ideas - I'd sooner see Sun programmers conduct regular brain farts on a blog and know there is some cranium activity about future Solaris development than just sitting on the side lines praying something is occurring in the deep crypt of Sun. Did you look at RFEs? Did you look at PSARCs? Did you look at projects on opensolaris.org? And can you show me some really big project where all developers are informing community about their actual work and future plans? Please, leave the decision about their openness on developers. Some prefer public development (lots of Sun employee), some are working in their own workspaces (lots of Sun employee). You want just big amount of paperwork from us ;-) I hope the community is not my second manager asking for weekly reports... Best regards, Milan (not opensolaris developer, only Solaris sustainer) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] File Events Notification API - PSARC/2007/027
Hi Cyril, Hi Milan, On 8/6/07, Milan Jurik [EMAIL PROTECTED] wrote: Did you look at RFEs? Did you look at PSARCs? Did you look at projects on opensolaris.org? And can you show me some really big project where all developers are informing community about their actual work and future plans? Umm, Linux ? Are you sure about this? I spent lots of time in lkml... Lots of patches (even bigger) are comming from sky. In fact in the open source world it is a matter of etiquette. Why? Why should he publish all his steps? He can go and develop something himself, because he prefers to spend some time just with his code. Not all are exhibicionists (please, read this word in positive way, or just say that I'm Czech who doesn't know English very well :-) ). Working privately is one's choice, of course. However, it would demonstrate a disrespect to the rest of the community. Why ? Because at the end of the work one will, essentially, throw the code over the wall. Disrespect? Because you want to publish something really working, not just some skeleton? Are you publishing all your everyday changes? Could you respect that some developers prefer to work in bigger steps and not consulting their everyday steps with others? It is normal even in companies. Please, leave the decision about their openness on developers. Some prefer public development (lots of Sun employee), some are working in their own workspaces (lots of Sun employee). We (community) cannot decide for Sun employees how to do their work for Sun. Nonetheless we can create rules for work integrated into OpenSolaris. I think it is fair. Of course. Could you specify one example of rule which will prohibit the integration that somebody is working in his own workspace and going to public just before integration or ARC, please? It is his decision to do it in this way. And potentially very dangerous, because: a) his work must not be accepted by others, as he implemented something in unpopular way b) somebody will implement it quicker c-d-e-f-...) add your own points here Is his contribution worse because he decided to not communicate frequently? You want just big amount of paperwork from us ;-) I hope the community is not my second manager asking for weekly reports... That strange conclusion. How did you get to it ? And what are you asking for in wpi cases? And btw. I added some hints how to receive FEM API to my previous e-mail, the main topic of this thread. Why are you complaining here? What are you expecting? That our CEO will go and push us in some way? Are you sure that this will make Sun engineers happy members of opensolaris community? We are just people, people with e-mail addresses ;-) Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] What is the proper forum to discuss alternate filesystems?
Hi Brian, In particular I am wondering if there is any work done or planned to start supporting additional file systems. Foe example: - jffs2/squashfs I have one student who just started to work on JFFS2 support. Based on docu, just from scratch, it will take some time. Another is working on ext2 native driver, which could be extended to ext3 in the future. And as others wrote, FUSE can be bridge for some other filesystems. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] xpg/bin/tr unexpect output on Sparc?
Hi, On st, 2007-04-11 at 22:38, Peter Tribble wrote: On 4/11/07, Bart Smaalders [EMAIL PROTECTED] wrote: Peter Tribble wrote: I like the second idea - remove the package entirely and make sure the files are always available under any conditions. (One could also ask why SUNWesu is a separate package.) I was under the impression that many people found our package breakdown already too coarse. Is this not the case? No, we have far too many packages. The resulting level of choice and subsequent diversity of configuration lead to chaos. Ultimately, the split into packages is done along boundaries that aren't useful for users. Two contrasting examples: SUNWsmapi shouldn't exist as a package - it supplies one library which is used by the format command. (And presumably other things, but splitting a single library used by the format command into a separate package just can't be right.) Are you sure that nobody needs just that library and not binaries which depend on that library? In snv_61, we get svn. In order for the svn client to work you need to install the apache2 server. OK, so svn client should go to apache2 package? And if somebody doesn't need svn client, but wants to have apache2? The second case argues for more granularity, for sure - we just need to do the other half of the problem and consolidate packages that don't need to be split. OK, you have some needs. But there are also others. It is much simpler to install two packages then delete some files, or not? Actually, I think we have too big packages. Best regards, Milan ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
Re: [osol-discuss] Re: blastwave package handling [was Re: Re: joining Sun]
Hi, Alan DuBoff pÃÅ¡e v pá 23. 03. 2007 v 12:12 -0700: On Friday 23 March 2007 01:00 am, Eric Enright wrote: Indeed. Several months ago a friend of mine running Debian did an `apt-get dist-upgrade'. Among other things, it upgraded apache2 and squid to newer versions, which took advantage of epoll(). epoll() is only available in Linux 2.6. These packages were built on 2.6, which made use of this newly available syscall. These packages were then deployed to systems running 2.4 kernels (also packaged by the same organization, and not obsoleted.) The resulting crashes were really quite spectacular. A friend of mine runs Debian also, and recentely had a different problem where only a 32-bit version was available for a package after he did a dist-upgrade, and that caused him to have to revert back to 32-bit and/or possibly UMP to get his system running. The binary compatibility in Solaris/OpenSolaris is something that doesn't get the respect it deserves in these cases. OK, boys, could you stop with this thread, please? I has been using Debian (and am still on some places) for aprox. 10 years. I met several problems, but: a) Eric case - wasn't it Debian testing (Etch), where Linux 2.4 is not officially supported? In the other case it was significant bug in buildd. b) Alan case - x86/amd64 platform or some other? Because amd64 is not supported officially in Debian stable (Sarge). So, please, if you are using testing version, please, expect that it is not stable release. The same if you are using backports. If you are upgrading your release, read release notes. Linux has +-, Debian has +-, OSOL has +- And, again, please, stop with this ..., it is not good for OSOL, community, world, peace etc. ;-) Have a nice weekend Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Intel 82562EZ Network Controller support
Hi, In Solaris Express Community Build 56 it is not yet supported. There is need to support it in OpenSolaris. http://bugs.opensolaris.org/ PCI ID of that controller is welcomed. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [Fwd: Re: [osol-discuss] GPLv3?]
Hi Erast, On Tue, 2007-01-30 at 21:07 -0800, Danek Duvall wrote: Stephen (or Jonathan and Rich via Stephen), what are the problems you're trying to solve with such a licensing change? its obvious... world domination. :-) and license shouldn't be a stopping factor. And that is why Mozilla dual-licensed their stuff, isn't it? Not sure (consider Netscape section in AOL), but if it is truth - the results? I'm not sure that it was successful, really. Anyway this thread wasn't started in good direction, I think. Why should we consider negatives? At first this should be about positives. GPLv3 (and why only GPLv3?) advocates should come with arguments, why GPLv3 is so good for OpenSolaris project. But I saw only yes, yes, yes, yes, yes from them... But: How can you argue? Do you know final GPLv3 already? Do you already know the impact on Open Source world? Please, stop and come with real arguments. When FSF will publish their license and it will be accepted by GPL community... Then we can think about dual-license. And that proposal from Stephen Harpster about GPLv3 with assembly exception (I don't know what it means...) - in the case that FSF will accept this, are you sure that GPL community will accept it? Best regards, -- Milan Jurik Revenue Product Engineer Sun Microsystems Inc. - Prague Czech Republic JKJ: I like work: it fascinates me. I can sit and look at it for hours. P.S.: I'm sorry that I'm sending it from sun.com, but I would like to be member of the OSOL community... ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Live Upgrade / SSL Certificates / Firefox
Hi, On Tue, 10 Oct 2006, Haik Aftandilian wrote: After a live upgrade from build 41 to build 47 (via Solaris Express Community Edition), whenever I visit an SSL site in Firefox, I get the Website Certified by an Unknown Authority Firefox message. Unable to verify the identity of blahblah.com as a trusted site. This occurs for any https site. Firefox version 1.5.0.6. Does anyone know if I need to rebuild my local certificates or something like that? I have tried blowing away my .mozilla directory and starting with a clean slate, but that did not work. shouldn't be needed. check edit - preferences - advanced - security - view_certs - authorities - there should be certificates of CA's. It seems that those default ones are all built in Firefox. There was known bug in build 47 (and few olders), certificates of CA's weren't included. It should be fixed in build 48. Bug number is 6459752. Could it be relevant to this problem? Jan. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Gaim busted?
Hi, OK, here's a weird one. For the longest time, gaim on Nevada worked fine for me. Then, sometime around build 28, it stopped working, and it couldn't find any plugins (so the Protocol field on the account dialogue was blank)--I think this concided with the switch from version 0.9x to 1.x. I shrugged it off as a temporary bug. I posted about it here (or possibly comp.unix.solaris) a bit later, but people said that they had no problem with it. Fast forward to today, after I installed Nevada build 41. I try again; still busted. Then I try using my wife's login--lo and behold, it worked! Using truss, I noticed my wife's gaim process was running /usr/bin/gaim, whereas mine was running /bin/gaim. On hunch, I tried running /usr/bin/gaim rather than relying on exec() to expand my $PATH get to /bin/gaim first, and it worked! So the question is: WTF is going on, and is this a bug? It is known bug. And reported to upstream: http://sourceforge.net/tracker/index.php?func=detailaid=1425603group_id=235atid=100235 Best regards, Milan Jurik ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: [smf-discuss] Project proposal: Enhanced SMF Profiles
Hello, On Fri, 12 May 2006, David Bustos wrote: Quoth De Mena, Ron on Fri, May 12, 2006 at 09:51:36AM -0400: Please correct me if I am wrong... You are looking to add properties and features similar to what /etc/default/sendmail file does for the sendmail service when we would define MODE= to disable daemon mode? Just trying to put it in perspective, because I got lost in those projects you linked, but I think I get the idea. It seems that you are not familiar with today's SMF profiles. Currently (Solaris 10 Nevada), you can write a file which comprises a list of services and whether each should be enabled or disabled. (The format is XML, following the service_bundle(4) DTD.) You can invoke 'svccfg apply' on that file, and it will enable or disable services according to the file. See the .xml files in /var/svc/profile on a Solaris 10 system for examples. This project is to extend this concept to allow people to customize more than just whether a service is enabled or disabled. What its dependencies are, what executables to use for the service, what resource management settings to use with the service, or any service-specific properties which the service may use. Furthermore, it allows projects to allow users to create these profiles easily for later use. Does it mean that SMF Profiles will be like MS Windows registry? In this case some SQLite files probably etc.? No text files for easy editing with vi-like editors? Problem restoring after corruption of SQLite data files? Best regards, Milan Jurik ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
