Re: [osol-discuss] any work on bug ID 6807184
I hope I'm not intruding. I ran across this discussion while trying to find solutions to my system (which uses the nge0 driver), and I wanted to also confirm that this version of the fix (the -9 revision) works for me as well. I had tried the mcast.3.tar.gz version but it did not fix the problem. The problem as I observed: I was trying to zfs send a 15GB filesystem from an Ultra-40 workstation via a Gb Ethernet switch to a white box machine that I built myself. The components I used to build the system are described here: http://blogs.sun.com/drapeau/entry/draft_2_my_home_media Anyway, I could never complete the zfs send -- zfs receive; the network connection would stall after a while. I found the mcast.3.tar.gz fix and tried that, but with the same results. When I found this discussion thread, I read through and found that the rge-6888015-9.tar.gz version seemed to work. I have been running with that version on my machine all day today (for about 14 hours) and it is working fine so far. I have successfully used zfs send | zfs receive on filesystems of 1.2G, 17G, 142G, 247G, and am right now 380G into a transfer of a 900G filesystem which I am hoping will complete some time tomorrow morning. (so far this latest transfer has sent 372GB of filesystem in 4 hours) I don't have any diagnostic data to offer; all I'm offering here is a second set of hands who has tried your patch, with rather large amounts of data. It works for me. Thank you very much for the fix; now I don't have to go buy a different white box setup for my home media server! --George -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Opensolaris 2009/06 2010/02 update/upgrade problems
BTW he use wifi for this problem : I am updating over a wireless 11b network That's what I get for skimming through this thread in less then 3 seconds and firing off a reply without reading everything. I only check this forum in a few spare minutes between doing other work that I actually get paid to do at my Linux job (LinuxWindozeCisco=customers paying me $$, Solaris*BSD=unpaid part-time hobby), so I'm usually talking on the phone and have somewhere between 10 and 20 SSH and rdesktop windows open to various broken Red Hat and Microsoft related things when I'm reading and responding to problems in this forum. I guess the inattention to detail from being pre-occupied with other things makes for weak help replies, but it's still sometimes better than no help replies. ;-) -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] virtualbox 3.0.12 IPS?
Alan Steinberg wrote: I'm not in the VirtualBox organization, but I'm not aware of any beta releases. VirtualBox has been releasing on a cadence of a new version about every 4 weeks. We've tried to keep the gap between SVR4 package and IPS availability as small as possible. They do release beta versions from time to time. For example recently they released beta version of VB 3.1 with many improvements. It would be really great if they could make IPS packages available for beta releases at the same time. On the other hand creating IPS packages is easy especially once one's got a working template - maybe developers building VB should make creating and publishing VB IPS packages as part of their publishing procedure being it beta or standard release? -- Robert Milkowski http://milek.blogspot.com ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Is the default 512MB to small for swap
I am just wondering if the default lower limit should be increased from 512MB when installed on small memory machines and depending on size of disk! The reason is I just tried a image-update of OpenSolaris 2009.06 to the latest dev release 127 and had the following message: pkg: There is not enough memory to complete the requested operation. At least 239MB of virtual memory was in use by this command before it ran out of memory. The machine has 1Gig of memory (which I know is small these days) and the default swap which was 512MB. I was logged in remotely so was not running the gnome desktop on the machine but did have CIFS enabled (idmap size=815M, RSS=161M) QUOTE: The swap volume size that is created during an initial installation is based on 1/2 the size of physical memory, but is generally in the 512 Mbyte to 2 Gbyte range. from opensolaris.org Andrew PS. before some one says to increase it I did! # zfs set volsize=1G rpool/swap ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Very slow boot time ( 35minutes)
By changing the package repository and using the update manager gui. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Opensolaris 2009/06 2010/02 update/upgrade problems
RedHat and Microsoft get broken? Unbelievable :-D (just joke). I hope that I will work soon with OpenBSD only. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] virtualbox 3.0.12 IPS?
On Tue, Dec 1, 2009 at 2:18 AM, Alan Steinberg alan.steinb...@sun.com wrote: I'm not in the VirtualBox organization, but I'm not aware of any beta releases. VirtualBox has been releasing on a cadence of a new version about every 4 weeks. We've tried to keep the gap between SVR4 package and IPS availability as small as possible. So, any ETA for having 3.1 in IPS ? It was released yesterday [1] [2] [1] http://www.virtualbox.org/wiki/Changelog [2] http://download.virtualbox.org/virtualbox/3.1.0/VirtualBox-3.1.0-55467-SunOS.tar.gz -- Alan Robert Milkowski wrote: Hi, It would also be nice if you would provide your beta releases in IPS packaging... On Tue, 24 Nov 2009, Alan Steinberg wrote: We hope to have the IPS version up in the next day or so. I don't think you would want to manually download and install the tarballs from the virtualbox.org website, since you would first have to uninstall the IPS version, then uninstall the tarball when you switch back to the IPS version. I would recommend just waiting the extra day or so. -- Alan keithk wrote: Hi: I have not been able to upgrade my virtualbox 3.0.12 because the IPS version has not been made available through the sun extra repository. Is there any way I can do a manual upgrade from my existing IPS package? Thanks, Keith ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org -- Regards, Cyril ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How do I install patches for sun studio 12 update 1 for opensolaris?
Hi Kulip, I am on the last build from /dev repository, build 127. Thanks for all of you who replied. I will wait for the SS12u1 + patches in /dev. Thanks. Kuldip Oberoi wrote: Hi Keith, Are you on an OpenSolaris 2009.06, a more recent build, or something else? We are planning on updating the /dev repo with SS12u1 + patches, likely during the build 128 timeframe, b/c of some issues we've seen on OSol builds after 2009.06 (116 and later to be exact). /kso Keith wrote: John Martin wrote: keithk wrote: Hi: I am getting some compilation error which I think one of the patches listed on http://developers.sun.com/sunstudio/downloads/patches/ss12u1_patches.jsp for Sun Studio 12 update 1 would fix the problem. I downloaded the patches, but could not patch the software because patchadd is not part of opensolaris. How do I patch Sun Studio in Opensolaris? Before trying the patch route, I would recommend loading the Sept 2009 CBE which is Studio 12 with select patches. http://hub.opensolaris.org/bin/view/Community+Group+tools/sun_studio_12_tools and see if that solves your compilation errors. Assuming this doesn't work, do you have the sunstudio12u1 or sunstudioexpress IPS package loaded? John, I have the sunstudio12u1 IPS package loaded. The current patch for the C++ compiler is Nov 28, 2009. http://sunsolve.sun.com/search/document.do?assetkey=1-21-128229-03-1 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] virtualbox 3.0.12 IPS?
On 01/12/2009 13:13, Cyril Plisko wrote: On Tue, Dec 1, 2009 at 2:18 AM, Alan Steinbergalan.steinb...@sun.com wrote: I'm not in the VirtualBox organization, but I'm not aware of any beta releases. VirtualBox has been releasing on a cadence of a new version about every 4 weeks. We've tried to keep the gap between SVR4 package and IPS availability as small as possible. So, any ETA for having 3.1 in IPS ? It was released yesterday [1] [2] [1] http://www.virtualbox.org/wiki/Changelog [2] http://download.virtualbox.org/virtualbox/3.1.0/VirtualBox-3.1.0-55467-SunOS.tar.gz Some critical fixes here:-) * 3D support: fixed crashes in FarCry, SecondLife, Call of Duty, Unreal Tournament, Eve Online (bugs #2801 http://www.virtualbox.org/ticket/2801, #2791 http://www.virtualbox.org/ticket/2791) * 3D support: fixed graphics corruption in World of Warcraft (#2816 http://www.virtualbox.org/ticket/2816) I like it, really. Rob -- E-Mail: rob.mcma...@warwick.ac.uk PHONE: +44 24 7652 3037 Rob McMahon, IT Services, Warwick University, Coventry, CV4 7AL, England ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Why is using Package Manager such a pain in the A$$?
Anon Y Mous wrote: Is anybody interested in tacking a crack at re-writing IPS in the C programming language if that would make it run faster? I'm amused that you think that re-writing IPS in the C language would make it run that much faster. You're aware that core parts of IPS are already written in C, yes? You're also aware that Google uses python for a significant portion of their infrastructure, right? Maybe it might be useful add an optional choice where local OpenSolaris user's groups could use an algorithm similar to bit-torrent to accelerate the downloading of packages from a distributed network of volunteer package seeders. This is planned functionality. As it is right now, apt-get on Nexenta seems to run subjectively faster than IPS on OpenSolaris Indiana for whatever reason. That depends on which functionality you're comparing. Not all of it can be compared directly as our functionality set is very different. We've done lots of performance work recently and more is coming. Cheers, -- Shawn Walker ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] system info
I wondered about a home made system info reporter that would report some basic info about the OS and hardware format (show Disks in use) zpool list zfs list -r /bin/df -h Come to mind as probably most useful in the event the sytem becomes unusable. I'm thinking to script something that posts that info to my website on a daily basis so I'll always have at least yesterdays info. There are probably tools that do this or at least collect the info. Any pointers on that are welcome. If not though, I wondered if someone could coach me a bit with `format' When `format' is run with no args it lists all disks and prompts for a command. It appears there is no simple way to get the output by scripting, since `format' doesn't close by itself. Its probably dead easy to run it with a `quit' or `exit' somewhere but I'm not sure how that might be done. I tried formats' `-f file' option which makes `format' read commands from the specified `file'. So maybe just putting `quit' in a file might do it. Something like: `echo quit file format -f file ' might work in a script but it does not.. I just get the --help output. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] system info
Harry Putnam wrote: : : If not though, I wondered if someone could coach me a bit with `format' When `format' is run with no args it lists all disks and prompts for a command. It appears there is no simple way to get the output by scripting, since `format' doesn't close by itself. Its probably dead easy to run it with a `quit' or `exit' somewhere but I'm not sure how that might be done. This works on my home system (OpenSolaris snv_127): % pfexec format /dev/null Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c5t0d0 DEFAULT cyl 30397 alt 2 hd 255 sec 63 /p...@0,0/pci108e,6...@5/d...@0,0 1. c5t1d0 ATA-ST3750330AS-SD1A-698.64GB /p...@0,0/pci108e,6...@5/d...@1,0 2. c6t0d0 ATA-ST3750330AS-SD1A-698.64GB /p...@0,0/pci108e,6...@5,1/d...@0,0 3. c6t1d0 ATA-ST3750330AS-SD1A-698.64GB /p...@0,0/pci108e,6...@5,1/d...@1,0 Specify disk (enter its number): % HTH - Tim ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Why is using Package Manager such a pain in the A$$?
I'm amused that you think that re-writing IPS in the C language would make it run that much faster. snip Cheers, -- Shawn Walker Hi Shawn, You are, of course, a very respectable member of this forum (an understatement), but please refrain from using languages that may cause resentment by other (especially long-time) forum members. Thanks for your understanding. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Why is using Package Manager such a pain in the A$$?
Is expressing amusement language that causes resentment? Or is the bad language you are talking about the reference to A$$ in the subject line? Has our forum come to this? Brian W. Wayne Liauh wrote: I'm amused that you think that re-writing IPS in the C language would make it run that much faster. snip Cheers, -- Shawn Walker Hi Shawn, You are, of course, a very respectable member of this forum (an understatement), but please refrain from using languages that may cause resentment by other (especially long-time) forum members. Thanks for your understanding. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] any work on bug ID 6807184
Anon Y Mous wrote: ... On a different note I don't know why Sun doesn't just give Masayuki Murayama core device driver contributor status so that he can freely work on fixing bugs in NIC drivers without having to run through the whole sponsorship obstacle course. If you look at how many Solaris device drivers he has written over the years, I think he has earned the it. All contributions by non-Sun employees have to go that route, there isn't a special classification available to give him, however well Murayama may have earned it. However, regular contributors do tend to end up with ongoing relationships with sponsors who get them in efficiently and make the sponsorship avenue not onerous. We'd need to advance the external gate development process further to streamline it any further, I believe. Dave ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] system info
Tim Bell tim.b...@sun.com writes: [...] Harry wrote: It appears there is no simple way to get the output by scripting, since `format' doesn't close by itself. Its probably dead easy to run it with a `quit' or `exit' somewhere but I'm not sure how that might be done. This works on my home system (OpenSolaris snv_127): % pfexec format /dev/null Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c5t0d0 DEFAULT cyl 30397 alt 2 hd 255 sec 63 /p...@0,0/pci108e,6...@5/d...@0,0 1. c5t1d0 ATA-ST3750330AS-SD1A-698.64GB /p...@0,0/pci108e,6...@5/d...@1,0 2. c6t0d0 ATA-ST3750330AS-SD1A-698.64GB /p...@0,0/pci108e,6...@5,1/d...@0,0 3. c6t1d0 ATA-ST3750330AS-SD1A-698.64GB /p...@0,0/pci108e,6...@5,1/d...@1,0 Specify disk (enter its number): % Fails miserably here: pfexec format /dev/null -bash: /dev/null .. no such file or directory From your PS1 symbol it looks like you might be using tsch or even csh? Wonder if that makes a difference ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] system info
About `failing miserably': Total pilot error... The shell I ran the command in was ssh'ed into a linux machine format /dev/null works just fine one the pilot gets his head out of his behind. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Is the default 512MB to small for swap
Andrew Watkins wrote: I am just wondering if the default lower limit should be increased from 512MB when installed on small memory machines and depending on size of disk! The reason is I just tried a image-update of OpenSolaris 2009.06 to the latest dev release 127 and had the following message: pkg: There is not enough memory to complete the requested operation. At least 239MB of virtual memory was in use by this command before it ran out of memory. The machine has 1Gig of memory (which I know is small these days) and the default swap which was 512MB. I was logged in remotely so was not running the gnome desktop on the machine but did have CIFS enabled (idmap size=815M, RSS=161M) QUOTE: The swap volume size that is created during an initial installation is based on 1/2 the size of physical memory, but is generally in the 512 Mbyte to 2 Gbyte range. from opensolaris.org It would be useful to file a bug capturing your experience so that we can consider whether a change in the algorithm is required. Memory requirements for image-update have fluctuated as pkg work has happened and will likely change a lot once the build 128 pkg implementation is used since the solver changed. Dave ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Very slow boot time ( 35minutes)
The boot log shown was from a boot with -v -m options. I haven't been able to complete a successful boot today, using -kv -m or normal options. For some attempts I forgot to start my timer, but they all ran passed one hour before I rebooted. However, the SVN_125 boot (to console) did succeed. It takes about 3 minutes. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] system info
Harry Putnam wrote: Tim Bell tim.b...@sun.com writes: [...] Harry wrote: It appears there is no simple way to get the output by scripting, since `format' doesn't close by itself. Its probably dead easy to run it with a `quit' or `exit' somewhere but I'm not sure how that might be done. This works on my home system (OpenSolaris snv_127): % pfexec format /dev/null Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c5t0d0 DEFAULT cyl 30397 alt 2 hd 255 sec 63 /p...@0,0/pci108e,6...@5/d...@0,0 1. c5t1d0 ATA-ST3750330AS-SD1A-698.64GB /p...@0,0/pci108e,6...@5/d...@1,0 2. c6t0d0 ATA-ST3750330AS-SD1A-698.64GB /p...@0,0/pci108e,6...@5,1/d...@0,0 3. c6t1d0 ATA-ST3750330AS-SD1A-698.64GB /p...@0,0/pci108e,6...@5,1/d...@1,0 Specify disk (enter its number): % Fails miserably here: pfexec format /dev/null -bash: /dev/null .. no such file or directory From your PS1 symbol it looks like you might be using tsch or even csh? Wonder if that makes a difference Works here: bash-4.0$ pfexec /usr/sbin/format /dev/null Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c8t0d0 DEFAULT cyl 15563 alt 2 hd 255 sec 63 /p...@0,0/pci1558,9...@1f,2/d...@0,0 1. c8t1d0 ATA-OCZ-VERTEX-1.3-238.47GB /p...@0,0/pci1558,9...@1f,2/d...@1,0 2. c8t2d0 ATA-INTEL SSDSA2MH16-8820-149.05GB /p...@0,0/pci1558,9...@1f,2/d...@2,0 Specify disk (enter its number): bash-4.0$ I had to specify the location for format explicitly, and it looks like you didn't add a space between and /dev/null (maybe it was a typo?). Try it again with copy and paste. Paul ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Why is using Package Manager such a pain in the A$$?
Is expressing amusement language that causes resentment? Or is the bad language you are talking about the reference to A$$ in the subject line? Has our forum come to this? Brian I believe you have answered your own question. (thus then why bothered to ask?) -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] system info
try echo | format -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] system info
Gopi Desaboyina gopidesaboy...@yahoo.com writes: try echo | format Nice, another good one. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] any work on bug ID 6807184
On a different note I don't know why Sun doesn't just give Masayuki Murayama core device driver contributor status so that he can freely work on fixing bugs in NIC drivers without having to run through the whole sponsorship obstacle course. If you look at how many Solaris device drivers he has written over the years, I think he has earned it. Sun cannot grant Core Contributor status - only the members of one of the community groups or the OGB can do so, and the Drivers community has already done so for him. The only rights that gives him though are a vote in OpenSolaris elections and the decisions of that community. It does not give him a VPN tunnnel through the Sun firewall to allow direct putbacks to the OpenSolaris ON master gates. Direct putback access without a sponsor depends on the master gate being outside the Sun firewall, as it is for the Desktop consolidation and several projects (like IPS) - not on the status of the contributor. -Alan Coopersmith- alan.coopersm...@sun.com Sun Microsystems, Inc. - X Window System Engineering -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Very slow boot time ( 35minutes)
Ok. I'm stuck now. My OS 2009.06 BEs won't boot, at least not within an hour. That includes a safe snapshot turned into a BE. The SVN_125 boots into console mode. It won't go into multi-user mode, because svc:/system/device/audio can't be started. Is it possible to remove the audio dependency from the mult-user service? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Why is using Package Manager such a pain in the A$$?
I am all for calling out bad language when its used but I am failing to see your point here. As for the C question, it has been discussed already in the IPS mailing list, as already mentioned performance critical portions are written in C at this stage. On Wed, Dec 2, 2009 at 05:22, W. Wayne Liauh w...@hawaiilinux.us wrote: Is expressing amusement language that causes resentment? Or is the bad language you are talking about the reference to A$$ in the subject line? Has our forum come to this? Brian I believe you have answered your own question. (thus then why bothered to ask?) -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] java classpath
Hi! I'm moving from OSX Server to an OpenSolaris box. There are some java services to install and it's driving me nuts... The are some jar-Files that call classes from the jar file jt400.jar. I always get: Exception in thread main java.lang.NoClassDefFoundError: jt400/jar Caused by: java.lang.ClassNotFoundException: jt400.jar [...] I tried: 1) export CLASSPATH=jt400.jar java -jar SFR.jar 2) java -cp jt400.jar -jar SFR.jar on OSX all I have to do is move the libraries into /Library/Java/Extensions and all works fine. Is there a similar directory in OpenSolaris? Regards, Martin ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] java classpath
Set your CLASSPATH to the path of the jt400.jar file and not the name of the file itself and then try it. On Tue, Dec 1, 2009 at 5:26 PM, Dr. Martin Mundschenk m.mundsch...@mundschenk.de wrote: Hi! I'm moving from OSX Server to an OpenSolaris box. There are some java services to install and it's driving me nuts... The are some jar-Files that call classes from the jar file jt400.jar. I always get: Exception in thread main java.lang.NoClassDefFoundError: jt400/jar Caused by: java.lang.ClassNotFoundException: jt400.jar [...] I tried: 1) export CLASSPATH=jt400.jar java -jar SFR.jar 2) java -cp jt400.jar -jar SFR.jar on OSX all I have to do is move the libraries into /Library/Java/Extensions and all works fine. Is there a similar directory in OpenSolaris? Regards, Martin ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] java classpath
Dr. Martin Mundschenk wrote on 12/ 1/09 02:26 PM: Hi! I'm moving from OSX Server to an OpenSolaris box. There are some java services to install and it's driving me nuts... The are some jar-Files that call classes from the jar file jt400.jar. I always get: Exception in thread main java.lang.NoClassDefFoundError: jt400/jar Caused by: java.lang.ClassNotFoundException: jt400.jar [...] I tried: 1) export CLASSPATH=jt400.jar java -jar SFR.jar 2) java -cp jt400.jar -jar SFR.jar on OSX all I have to do is move the libraries into /Library/Java/Extensions and all works fine. Is there a similar directory in OpenSolaris? CLASSPATH and -cp are ignored when using java -jar. Ideally SFR.jar would have a Class-Path entry in its MANIFEST.MF file referencing jt400.jar. If you know or can figure out the name of the main class in SFR.jar, you can use: java -cp SFR.jar:jt400.jar mainClassName You can also put jt400.jar in the /usr/java/jre/lib/ext directory, if you have permission, or use: java -Djava.ext.dirs=$PWD -jar SFR.jar Hope that helps. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] java classpath
Dr. Martin Mundschenk wrote: 1) export CLASSPATH=jt400.jar java -jar SFR.jar As was suggested, try: export CLASSPATH=/full/path/to/jt400.jar:. java -jar SFR.jar 2) java -cp jt400.jar -jar SFR.jar on OSX all I have to do is move the libraries into /Library/Java/Extensions and all works fine. Is there a similar directory in OpenSolaris? If you are using the Java runtime that is installed with OpenSolaris, that would be: /usr/jdk/latest/jre/lib/ext If you are using a JRE or a JDK you installed somewhere else, look for $JAVA_HOME/jre/lib/ext. HTH - Tim For more information, search for Installed Optional Packages here: http://java.sun.com/javase/6/docs/technotes/guides/extensions/spec.html ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] User management via http
Hi, I'm looking for a user management app with web page UI. Functionality? Every user (not only a root) can login on web page to see his account (solaris system user) with ability to check a quota, change own password, maybe change personal info like first name, surname etc. Is there any system like that? It will be great when it can work with zones. PS Maybe i'm not clear because my english isn't so good. Please ask me what you cannot understand. Thanks ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] virtualbox 3.0.12 IPS?
Should we be lobbying the VirtualBox folks then? Is there a better venue to do that? I'm really eagerly awaiting 3.1 due to the improved USB/Audio support for OpenSolaris. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Very slow boot time ( 35minutes)
[url=http://bugs.opensolaris.org/view_bug.do?bug_id=6902551]Bug #6902551[/url] was responsible for the audio device issue on SVN_127 (its was always 127 not 125 as I mentioned earlier). The fix described worked a treat and the box now boots. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Very slow boot time ( 35minutes)
or as in my case if you have a server with no audio, just comment out devfsadm -i audio from lib/svc/method/device-audio :) On Tue, Dec 1, 2009 at 8:44 PM, Chris chris.sola...@jalakai.co.uk wrote: [url=http://bugs.opensolaris.org/view_bug.do?bug_id=6902551]Bug#6902551[/url] was responsible for the audio device issue on SVN_127 (its was always 127 not 125 as I mentioned earlier). The fix described worked a treat and the box now boots. -- 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] IRQ confilct warning logged at the console.
Actually ejannett, I kind of messed up, a better way to get interrupt statistics might be to put a time interval after the intrstat command like this: pfexec intrstat 30 for 30 second intervals or pfexec intrstat 60 for 60 second intervals. There's also an intrtime command as well. These links might explain it better: http://lserinol.blogspot.com/2009/02/solaris-interrupts.html http://prefetch.net/blog/index.php/2005/07/22/monitoring-interrupts-with-solaris/ -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Static Ip Issue
If I may suggest, use # sys-unconfig, you will need to reboot (it'll take you), but this process will ensure you change every part correctly. I thought sys-unconfig doesn't work properly on OpenSolaris Indiana. Can anyone confirm or deny this? I know when I got one of those Toshiba OpenSolaris laptops there was a mention somewhere in the release notes that said something to the effect of DO NOT RUN sys-unconfig or it might brick your box If you go to this link: http://www.opensolaris.com/toshibanotebook/relnotesOS2009.06.html you'll see where it says: sys-unconfig Corrupts System Configuration Data! Description: Do not use the sys-unconfig utility! The sys-unconfig utility is not supported for use by OpenSolaris systems. If used, it will corrupt system configuration data and will leave the system in an unknown state. If you want to configure the system with a static IP address, see Configuring the OpenSolaris OS With a Static IP Address. Workaround: To recover your system, reinstall the OS from the Live CD and the supplementary software components from the OpenSolaris repositories. See How to Install the OpenSolaris 2009.06 OS From the Live CD, How to Install Supplementary Software Packages (CLI), and How to Install Supplementary Software Packages (GUI). Configuring the OpenSolaris OS With a Static IP Address Description: The OpenSolaris OS comes with a default network configuration for a DHCP client. To use a static IP address instead, perform the additional configuration steps described in the workaround. Workaround: Perform the following steps from a terminal window to configure a static IP address: 1. In the terminal window, manually enable the default network interface: svcadm enable physical:default 2. In the terminal window, disable the network automagic interface: svcadm disable physical:nwam 3. Open the network configuration panel from the System-Administration-Network menu and do the following: 1. a. Click Manual to disable Automatic mode 2. b. Select the network connection to be configured 3. c. Click Properties 4. d. Set the values you want in the Interface Properties panel 5. e. Enable the device by setting the IP address, subnet, and default gateway 4. 4. In the terminal window restart the network services: svcadm restart milestone/network -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Static Ip Issue
Anon Y Mous wrote: If I may suggest, use # sys-unconfig, you will need to reboot (it'll take you), but this process will ensure you change every part correctly. I thought sys-unconfig doesn't work properly on OpenSolaris Indiana. Can anyone confirm or deny this? correct. sys-unconfig isn't the way to go. Also, it's normally better to stay with nwam and just change the interface to static like this: http://blogs.sun.com/PlasticPixel/entry/nwam_static_ip_address_for And, add a persistent default route like this: # pfexec route -p add default 192.168.0.2 Cheers, Jim ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] system info
If all you want is basic hardware info (like what stick of RAM is in what slot on the motherboard and what device is in what slot) OpenSolaris has these three commands which I really love: pfexec prtdiag -v pfexec psrinfo -pv pfexec scanpci However, I always thought it was kind of retarded (for shell scripting purposes) that Solaris doesn't have a non-user interactive disk listing command that is the equivalent of fdisk -l in Linux. For example, on Red Hat Enterprise Linux you can just put this line in your shell script: fdisk -l | grep -i disk and you will get this kind of easy to read / easy to parse output: Disk /dev/sda: 500.1 GB, 500107862016 bytes Disk /dev/sdb: 250.0 GB, 250059350016 bytes Disk /dev/sdc: 320.0 GB, 320072933376 bytes On OpenSolaris if you try putting format -e in your shell script, then your shell script will hang at the: Specify disk (enter its number): prompt which is a real shame. There should be a format -l command for shell script use that lists disks without requiring user interaction. I have found a temporary workaround where I put: pfexec format /dev/null in a shell script and it works in terms of giving me a list of disks with out hanging while it waits for user input, but the output is still kind of clunky compared to fdisk -l in linux or the atacontrol list command on FreeBSD and the output needs to be worked over very heavily with awk, grep and sed to parse the info out that my shell script needs (i.e. the drive name and how many gigabytes of total space there is on the drive). However, typing in something like pfexec format /dev/null is still much better than some of the really scary pfiles based solutions I have come up with as a substitute for what I usually use lsof -ni for on BSD to keep track of what pid is bound to what tcp port / tcp connection in the /proc directory (some of my pfiles scripts are up to 20 lines long and they take forever to give output that I could get with one line of text in much less time using lsof -i on FreeBSD). -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] system info
If all you want is basic hardware info (like what stick of RAM is in what slot on the motherboard and what device is in what slot) OpenSolaris has these three commands which I really love: pfexec prtdiag -v pfexec psrinfo -pv pfexec scanpci However, I always thought it was kind of retarded (for shell scripting purposes) that Solaris doesn't have a non-user interactive disk listing command that is the equivalent of fdisk -l in Linux. For example, on Red Hat Enterprise Linux you can just put this line in your shell script: fdisk -l | grep -i disk and you will get this kind of easy to read / easy to parse output: Disk /dev/sda: 500.1 GB, 500107862016 bytes Disk /dev/sdb: 250.0 GB, 250059350016 bytes Disk /dev/sdc: 320.0 GB, 320072933376 bytes On OpenSolaris if you try putting format -e in your shell script, then your shell script will hang at the: Specify disk (enter its number): prompt which is a real shame. There should be a format -l command for shell script use that lists disks without requiring user interaction. I have found a temporary workaround where I put: pfexec format /dev/null in a shell script and it works in terms of giving me a list of disks with out hanging while it waits for user input, but the output is still kind of clunky compared to fdisk -l in linux or the atacontrol list command on FreeBSD and the output needs to be worked over very heavily with awk, grep and sed to parse the info out that my shell script needs (i.e. the drive name and how many gigabytes of total space there is on the drive). However, typing in something like pfexec format /dev/null is still much better than some of the really scary pfiles based solutions I have come up with as a substitute for what I usually use lsof -ni for on BSD to keep track of what pid is bound to what tcp port / tcp connection in the /proc directory (some of my pfiles scripts are up to 20 lines long and they take forever to give output that I could get with one line of text in much less time using lsof -i on FreeBSD). -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Setting up of a Sun lab with Sun Blade 1500, Sun Ray 1G, Sun Fire 440
Hi all, In my college, we have Sun Blade 1500 workstations, Sun Ray 1G thin clients, Sun Fire 440 server available. We intend to setup a Sun lab with Solaris/opensolaris. I could see from the internet that these machines are outdated products, but still I know it should be possible to configure them with the latest versions of the OS available. Sun Blade 1500 workstations have 512 MB RAM and I'm not sure it will be good enough to install opensolaris-2009.06 on it and also I have not installed opensolaris on a sparc machine before. I have downloaded the solaris and opensolaris sparc isos and have them ready. Will it be possible to install and run opensolaris on the workstation? And any places to look into with regards to configuring and setting up the thin clients? Thank you. Regards, Guruprasad. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] system info
If all you want is basic hardware info (like what stick of RAM is in what slot on the motherboard and what device is in what slot) OpenSolaris has these three commands which I really love: pfexec prtdiag -v pfexec psrinfo -pv pfexec scanpci However, I always thought it was kind of retarded (for shell scripting purposes) that Solaris doesn't have a non-user interactive disk listing command that is the equivalent of fdisk -l in Linux. For example, on Red Hat Enterprise Linux you can just put this line in your shell script: fdisk -l | grep -i disk and you will get this kind of easy to read / easy to parse output: Disk /dev/sda: 500.1 GB, 500107862016 bytes Disk /dev/sdb: 250.0 GB, 250059350016 bytes Disk /dev/sdc: 320.0 GB, 320072933376 bytes On OpenSolaris if you try putting format -e in your shell script, then your shell script will hang at the: Specify disk (enter its number): prompt which is a real shame. There should be a format -l command for shell script use that lists disks without requiring user interaction. I have found a temporary workaround where I put: pfexec format /dev / null in a shell script and it works in terms of giving me a list of disks with out hanging while it waits for user input, but the output is still kind of clunky compared to fdisk -l in linux or the atacontrol list command on FreeBSD and the output needs to be worked over very heavily with awk, grep and sed to parse the info out that my shell script needs (i.e. the drive name and how many gigabytes of total space there is on the drive). However, typing in something like pfexec format /dev/null is still much better than some of the really scary pfiles based solutions I have come up with as a substitute for what I usually use lsof -ni for on BSD to keep track of what pid is bound to what tcp port / tcp connection in the /proc directory (some of my pfiles scripts are up to 20 lines long and they take forever to give output that I could get with one line of text in much less time using lsof -i on FreeBSD). -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] system info
If all you want is basic hardware info (like what stick of RAM is in what slot on the motherboard and what device is in what slot) OpenSolaris has these three commands which I really love: pfexec prtdiag -v pfexec psrinfo -pv pfexec scanpci However, I always thought it was kind of retarded (for shell scripting purposes) that Solaris doesn't have a non-user interactive disk listing command that is the equivalent of fdisk -l in Linux. For example, on Red Hat Enterprise Linux you can just put this line in your shell script: fdisk -l | grep -i disk and you will get this kind of easy to read / easy to parse output: Disk /dev/sda: 500.1 GB, 500107862016 bytes Disk /dev/sdb: 250.0 GB, 250059350016 bytes Disk /dev/sdc: 320.0 GB, 320072933376 bytes On OpenSolaris if you try putting format -e in your shell script, then your shell script will hang at the: Specify disk (enter its number): prompt which is a real shame. There should be a format -l command for shell script use that lists disks without requiring user interaction. I have found a temporary workaround where I put: pfexec format /dev/null in a shell script and it works in terms of giving me a list of disks with out hanging while it waits for user input, but the output is still kind of clunky compared to fdisk -l in linux or the atacontrol list command on FreeBSD and the output needs to be worked over very heavily with awk, grep and sed to parse the info out that my shell script needs (i.e. the drive name and how many gigabytes of total space there is on the drive). However, typing in something like pfexec format /dev/null is still much better than some of the really scary pfiles based solutions I have come up with as a substitute for what I usually use lsof -ni for on BSD to keep track of what pid is bound to what tcp port / tcp connection in the /proc directory (some of my pfiles scripts are up to 20 lines long and they take forever to give output that I could get with one line of text in much less time using lsof -i on FreeBSD). -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Setting up of a Sun lab with Sun Blade 1500, Sun Ray 1G, Sun Fire 440
On 12/02/09 13:15, Guruprasad wrote: Hi all, In my college, we have Sun Blade 1500 workstations, Sun Ray 1G thin clients, Sun Fire 440 server available. We intend to setup a Sun lab with Solaris/opensolaris. I could see from the internet that these machines are outdated products, but still I know it should be possible to configure them with the latest versions of the OS available. Sun Blade 1500 workstations have 512 MB RAM and I'm not sure it will be good enough to install opensolaris-2009.06 on it and also I have not installed opensolaris on a sparc machine before. I have downloaded the solaris and opensolaris sparc isos and have them ready. Will it be possible to install and run opensolaris on the workstation? And any places to look into with regards to configuring and setting up the thin clients? http://wikis.sun.com/display/srs. Thanks P.S.M.Swamiji Thank you. Regards, Guruprasad. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] system info
Ok, I really need to apologize for this quadruple post, I'm trying to type in greater than and less than signs to symbolize input and output redirection in BASH and KSH and for some reason the OpenSolaris forums interpret greater than and less than signs as HTML tags or something similar and garble up my message. I'm trying to post: pfexec format less than symbol /dev/null but everything after the less than symbol disappears when I type that in. If anyone else wants to see the bug for themselves, just type in a less than symbol (shown below) followed by /dev/null and everything after it disappears for some strange reason: -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
