Re: [osol-discuss] upcoming web event:strategy for Oracle's Sun Servers, Storage and solaris
I just returned from a short trip. So what was the conclusion and what are the news about Oracle Systems Strategy Update ? Something new ? How about Solaris/OpenSolaris ? thanks, Stefan -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] upcoming web event:strategy for Oracle's Sun Servers, Storage and solaris
thanks. stefan -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] The Illumos Project
Another idea: I was driving today and came to my mind: huh what could be a better example about a simple and classic HPC setup, used on a practical matter: BMW Oracle Racing ! Is this a retired business used only by academic and governments ? Of course not. BMW is a very commercial entity seeking profits. http://www.oracle.com/technology/events/hpc_consortium2010/bmw_oracle_racing_frank_albina.pdf Does this mean Oracle system's are not suitable doing HPC ? I bet Larry does count if his team ends on 3rd or 4th position... stefan -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] The Illumos Project
I know they uses SUSE and HP. I dont think Oracle is realizing anything regarding this except there is no license revenue for them on HPC Solaris/systems. And thats so plastic and real. Its true indeed since Sun/Solaris never been a top 10 HPC player, *but* Sun did improve the image past years and start convincing people about its HPC resources. So Oracle should have invest and continue the effort. Thats my point. HPC business is important but probable with a return a bit later. What Im afraid, based on this example, is that Oracle is looking for a simple market segment, where they could milk a lot of licenses for their products. Thats all. This means goodbye to old good Solaris from many parts of industry ! And might mean legacy :( Probable Cockcroft is starting to be right http://perfcap.blogspot.com/2010/08/open-letter-to-my-sun-friends-at-oracle.html stefan -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] The Illumos Project
OpenSolaris community on February 14th 2008 because Sun did not make OpenSolaris a truely oSS project: http://roy.gbiv.com/untangled/2008/watching-the-ripples Im very sad by the latest development of (Open)Solaris. I hope to be 100% wrong on this and think that OSOL and Solaris will value and improve over time not as a legacy OS, ala AIX. Lets hope that ! Time will tell us. Greetings, Stefan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] The Illumos Project
HPC is almost completely reserved for simulation these days, which means heavy use by academic (and quasi-academic) organizations, with some government stuff thrown in as as well. I'm also of course seeing usage for render farms. :-) What are you talking about !? Think something simple and common which connects everything: weather prediction ! Oracle exiting HPC market shows clearly that they drive the hdw business of Sun from a perspective of database house with no intimately knowledge of hardware business nor understanding what means to invest in certain directions. Too bad. Clear point Oracle is a business house not a technology house. Yep, looks like. stefan -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] The Illumos Project
yes - that's simulation. What I said. And who do you think has these big weather simulation setups? Certainly not each TV station... HPC is a vital business close to our society. If Oracle is a system company they must play HPC and support it the way IBM and other big irons do. Im not gonna start to explain you here the pro and cons of HPC nor advocate whats good about it. Who knows about HPC will understand me right ahead. I have no idea what Oracle is after but killing the HPC market will have a negative impact on future Oracle x86/SPARC hdw. Oracle is starting more and more to show visible signs that they will play in a very restricted market segment for their DB products. Dicard here all marketing stunts and big liners mgmt talks about ;) About weather prediction: in US AFAIK there are already private companies which can run different models. They offer the results to many other private companies so, yes it is already a business. In EU things are on smaller scale so you will find governments involved. In Asia I have no info, probable close to EU. Some of these accounts are on Solaris already and killing them is simple not a smart move. Scientific community might move away from Sun/Oracle as a vendor/provider. And when they do that they will trigger others to lose interest for Oracle systems: schools, agencies, universities etc. But probable this is what Oracle really wants !? Small, dedicated market segment ? If you need a DB and have big $$$ then you are lucky if not go somewhere else... Greetings, Stefan -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] The Illumos Project
I think that is something very much deep inside the community - the love for secrecy. Remember Secret Six - many years ago when Sun stopped Solaris x86. Then OpenSolaris Pilot, then many OpenSolaris projects, that were done secretly. I do recall every bit of it and I do recall how hard time I had to explain to other people and convince them about OSOL, all these stories and fictions - they are real and exist ! Cmon! As I said to John already, if Garret is up to something thats very cool and laudable and he should properly announce his effort. He did publish some weeks ago an entry in his blog saying just wait, we all be saved and delivered - Whats that, what should we understand out of it ? That they are building a new distro ? Who they , why, how !? And why on his blog ? If he is talking about OSOL normal place would be under OSOL mailing list not on wordpress, blogspot ... In addition, if he is up to something he should first publish and set some minimal goals open to anybody *before* making a teleconference, announcing his work, project. He should gather opinions, if he wants community - for instance hosting, servers, contributions, members, names, colors etc etc... From day 0 ! I will keep quiet now, but at least thats my opinion. It is quite hard to change people' mind and way of thinking. We (community) will get there (being open) eventually, but it will take quite some time. I hope, we will. stefan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] The Illumos Project
A number of the community leaders from the OpenSolaris community have been working quietly together on a new effort called Illumos, and we're Why quietly ? Is this a secret organization or !? If you value the community why haven't you talked public *before* your project has started ? thanks, stefan -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SchilliX-0.7.0 ready for testing
This is not an IPS issue; this is a distribution issue. Remember that all of the bits on pkg.opensolaris.org have been redistributable for a long time. That means that if someone wanted a mirror in say, Finland, they could have set one up. For that matter, one could have been setup on genunix.org a while ago. IPS tries to be a network pkg management system. It needs to be simple and easy to be used by folks to create simple mirrors and maintain them. IPS stays at the heart of this process. You need to measure how many such mirrors are available worldwide and try to understand why there are few, many etc. Then, there should be as well a connection between installer, pkg management and all these repositories/mirrors worldwide. The OSOL installer, IPS should keep a list of all hot mirrors available and automatically select the one close to you. Your TIMEZONE - auto select a close repo - validate - if ok install from there if not fall back to another one Otherwise again all these things are disconnected and users are left in dark ! Fixes went in builds after b134 that reduced memory usage by as much as 60%. At the moment (after the fixes noted above), memory usage remains primarily a function of the amount of package data the client has to process. Considering that the /dev repository contains nearly 70,000 unique package versions, I'd say it's pretty good at the moment. Thanks. Looks good. What comparative analysis have you done IPS vs SVR4 pkg management regarding: memory usage, cpu or net usage , resource consumption in general ? Do you have any open documents where we can see how good IPS is versus SVR4 in terms of resource utilisation ? As well what means in terms of CPU/MEM/Net to install 2000 pkg with IPS versus SVR4 ? Thanks for all updates. stefan -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SchilliX-0.7.0 ready for testing
True. Im not reffering here as a drop of IPS but rather as a understanding point for future and how this compares against SVR4. Anyway for future community distro , if any, would be good if we can keep one pkg management system and be compatible between distros. IPS should have fixed all these things what you have listed. To me, as a SysAdmin important are the following: - resource consumption. Still I would be glad to see a comparative analysis between SVR4 and IPS in terms of CPU, Mem, Disk and Net usage - simplicity, robustness - patching How IPS handles the process of applying patched ? AFAIK OSOL does not really have the concept of a patch, right ? Or ? Thanks, Stefan -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SchilliX-0.7.0 ready for testing
Star-1.5.1 is also available from Blastwave. The star on SchilliX has one new feature: 1) create a meta data only archive with star -c -dump -meta . arch 2) extraxt the archive uwing star -xp -xmeta -force-hole arch in order to create all plain files as 100% empty holes New is the combination -xmeta -force-hole. Such a tree does nse nearly no space on disk and it is sufficient as a reference for a wget -mirror call. sweet. star should have been long time inside Solaris. I hope to see star first class citizen in future OSOL. Nothing new that was not yet part of previous SchilliX release. I created this release mainly in order to have a start base for replacing closed source stuff from Sun/Oracle. yep. Got some info already from READMEs. thanks, Stefan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Community distro
It may even be seek times are the main problem... True. Too much concurrency on spinning platters can cause seek time bottlenecks. Possibly an iostat log during boot can provide some clues. If true then the situation will be better with SSDs. We have DTrace and we might think something about this. But we need a solution and accomodate this for all folks, since not everybody runs on SSDs. What means for a system like a laptop to start 100 services in parallel vs a server with 8 physical cpus. Probable SMF folks can help us here and tell us how have they tested this setup on different hdw profiles. Plus here is to have a defect management system where such things will be logged. Currently bugzilla/bugster/etc is no go from a community point of view. As well here some competitive comparations we could add versus FreeBSD, Ubuntu, RedHat. stefan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SchilliX-0.7.0 ready for testing
The only problem I can see in regards to how IPS was introduced that perhaps more explanation to the community at the project inception about why IPS and not something else would do good... a little bit more open dialog with the community before you start coding on why IPS, what are its design goals, etc. would help here. In my opinion, we will always have some gaps here, how open this process will be. Sun/Oracle will not ask the community unless they engage the community in the building process. In my view RedHat is a very well player which knows how to extract the goodies from Fedora without getting burned maintaining it ;) We need to learn to do the same. Otherwise we will live in hope. Regarding IPS and future we need to think and co-work this with vendor and find a common way together. IPS has still long way until it reaches some sort of stable status. From Finland some feedback I got from users regarding IPS (our internal FIOSUG, and other folks regarding IPS status found on 2009.06): - not a download format for a package. Meaning somebody would like to simple download emacs.pkg and manuall install it ! Cant do that now - repository cloning. Still hairy and poor documentation - mirrors: slow links to fetch packages from US. Who cares how well and smart IPS is if it takes forever to have some pkgs install in your machine. Ubuntu has a nice mirror list where pkgs are fetched within minutes. I can confirm as well this. Its a pain sometimes to download something from main repo. I live in Finland and have a 8Mbps line. - IPS resource consumption. Big and fat process when installing some basic pkgs. Dont have facts here but I have seen it too. I had the impression some work went in to get this fixed and improve things. Greetings, stefan -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SchilliX-0.7.0 ready for testing
thanks. I never tried previously the distro, but I will install this into one of my test machines. Is star part of the distro ? Hope so :) Would be nice to have a list somewhere what we get as plus on top of build130, all tools. Cheers, Stefan -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Community distro
Interesting. Do you have any comparative numbers between OSOL and others: RHAT, Ubuntu for instance ? I had the impression SMF did improve things. As I read your post it seems, sometimes in past but not anymore ... why is that ? Probable somebody should fill in some bugs regarding this ? Stefan -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Community distro
right. Good point is to keep all these things logged somewhere and we could track them down in time. Btw: if community thinks for a itself distro, which I salute more than anything, we could think first to have a defect management system where we could freely log these sort of defects and a light website ( I suggest people looking into nginx [1], a scalable HTTP server which does not require the big MB what apache wants. Its fast, simple and highly configurable for different usages: php, perl etc... ) When we have a bugzilla, then we could compare Ubuntu, Rhat etc and improve things and log these things. thanks, stefan Ref: [1] - http://www.nginx.org/ -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Community distro
Berlios.de is a service that exists already and after we moved to berlios.eu we will have plenty of space. sounds good. nginx I was thinking since is small, compact and does not require pre-forking ala Apache. wise consumption is always better. Here you have some details: http://wiki.nginx.org/Main http://www.kegel.com/c10k.html Stefan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Community distro
Do you believe you need bugzilla or would the bugtracker at Berlios be sufficient? any defect managemetn system would be enough. Probable easier would be to have bugzilla since we might need to have a compatibility with vendor which uses bugzilla. We need to think a bit. As well: product/components/etc ... we should not start to make a hairy business out of it but rather be simple and to the point. But now when you guys think about site, defect management system, forums etc ... we should think be flexible, easy to re-locate, if needed and resource consumption wise: see here Apache vs Nginx. cheers, stefan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [distribution-discuss] Community distro
+1 -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [distribution-discuss] Community distro
And I think this is the *biggest* problem people are currently complaining: new version of current OSOL distro, new packages etc. And this clearly supports my ideas: - OSOL as a *distribution* will never work. Even under Sun nor Oracle. I said that when Indiana was formed. OpenSolaris was meant to be the source code of entire Solaris OE, a repository. Sun made a mistake taken this and forming a classic distro: driven by Sun and somehow involving community. Thats a waste. From start ! - Sun/Oracle donates a large amount of their Solaris as source code, presented under different consolidations. Thats great and the community should think what to do with that. - The community should think and take this bunch of code and form a single reference distro, maintained *by community* with rules and procedures driven by community. Periodically the source code released from master ship: Sun, Oracle, etc would be merged into a new release of the community distro. Other distros of course can follow and have their own lifetime. - A communication channel should be established between the community and vendor, in this case Oracle. - Names and procedures should be put in place in order to avoid confusion and cut the FUD. OGB should take a lead in establishing new rules and propose new operating ways. This way we will stay close to master ship and have the distros we like. Complaining every single day that Oracle hasnt come up with something for OSOL is not helping anyone. The entire process should be changed to better accommodate all parties and attract new users. Otherwise only FUD, waste of time and bad publicity will be generated for OSOL. stefan -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Why do we need Oracle's permission or vision for OpenSolaris?
joerg , A much simpler approach could be taken where everybody benefits: - Oracle is donating a large amount of src code outside. Thats great. Community should take it and make their own cookies as they please ! - Im not really sure if you will have a connection established the way the community thinks with Oracle. Oracle I bet is more busy in trying to make profitable Sun's business and gain profit, since they are a profit company. right ? There will *always* be gaps ! As well this co-development will never work in my opinion since there are different agendas ! You cant fix that. - Indiana was a failure from start. Why not fixing this ? If the community cannot support itself, then what are we talking about !? Thats not a community at all. We should think this a bit better. -If we do this right everybody wins: eng. from Oracle will focus on their jobs, producing more code and sometimes opening new things out. Community re-syncing and updating their own distro ... People can contribute each way: Oracle - Community and Community - Oracle. Stefan -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] OGB Threatens to Shoot Itself In The Head
If I could add my comment(s) regarding latest developments: - Oracle clearly *is* a moving boat. But maybe a bit slower than expected for many of us. As well Oracle is not very well known for active relationships with open source communities , where they *actively* participate and communicate. I might be wrong here... So we should wait a bit longer, I would say. I know this is frustrating for many of us... - I fully agree on the other hand with OGB. It's pointless to have a OGB good for nothing. However, probable a better time slot should have been selected and monitored its activity. If nothing is really recorded during this period of time, I would assume OGB simple must exit. - Another crucial part I would say is this: we need to think carefully what is OpenSolaris outside of Oracle ? Is anything which reassembles a community ? Can OSOL be maintained outside Oracle ? Can we survive as a standalone community ? I wish we will come and find ways to continue, support and enhance as much as we can OSOL. The only issue here, now, is how to keep the communication open with master ship[*] and get their attention. Hopefully we will find ways and we will get Oracle's support ! Greetings, Stefan [*] Do people recall OSOL is not different as it was 1,2 years ago, we are seeing a delay caused by a massive integration between Sun/Oracle - this project is not and will never be what FreeBSD project is, for instance. Its roots with the master ship sometimes been troubled and difficult. But we found many times ways to work these out ! We will probable now. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] X58 and i7?
Hi all, Want to upgrade one of my computer to something like this mobo: 750W 80+ Corsair CMPSU-750TX Asus P6T Deluxe V2 Intel X58 2xGbLan 7.1 audio fw cf/sli RAID Intel Core i7 930 2.80 GHZ 8 MB LGA 1366 Boxed 12 Gt Kingston HyperX DDR3 1600 MHZ CL9 (6x2 Gt kit) 2 x 1 TB WD Caviar Green Power Sata 2 64MB Nvidia Quadro FX 580 PCI-E 512 MB GDDR3 Is this mobo/cpu suitable for OSOL ? Thanks, Stefan -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] X58 and i7?
thx. I was asking if anyone else is running this mobo with OSOL. stefan -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] X58 and i7?
:) cheers. Looks good. I need to see how much would cost me this new machine + nvidia . Thx, stefan -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Opera drops browser support for Solaris
Ginn, Thanks for sharing this. Would be very valuable that Oracle/Sun team will encourage you to do this kind of work and dedicate you more space to make these things happen more often. This way we ensure OpenSolaris community is enlarging and communicate better with other projects/groups outside us. As well we should probable attract more users to do such things. Opera, etc exactly do such things because of the previous point, meaning they see very few interactions of OSOL with outside world. For them porting and maintaining their application on OSOL/SOL is a waste since nobody rewards them anyhow more they consider wasting time. OGB should take such examples and drive/talk further with Oracle/Sun/etc what means keeping and enlarging a community... Your port basically links our community to Google world and really means a lot to me. cheers -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Opera drops browser support for Solaris
With the right portability framework, it is sufficient to develop on Solaris and the code will work on Linux and FreeBSD also. True. However I dont see Opera's troubles caused by Oracle integration: support costs, etc but rather a more simplistic view: not enough interest. If they were interested enough they would have selected OSOL and start building on that. As well in past: Opera was not showing enough interest in Solaris , so main question would be how to keep them interested in our project and how to grow such things and engage with other communities. Thats the hard part. stefan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] articles about opensolaris demise becoming annoying
Fully agree that many variables changed since Oracle got Sun. As I posted on solarisx86 yahoo mailing list we need to wait a bit longer for all these things to be cleared but as well Oracle should commit and dont let space for confusion and mis-interpretations in a proper time frame window ;) Very simple to fix all this FUD flying around - we should have OGB working closely with Oracle, same way the presentation speaks about working with Linux community slide. 28. But this will take some time. Cheers -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] maxtor onetouch III 1TB USB storage snv_b64a
Colin Zou wrote: The USB FAQ storage section might help you. http://www.sun.com/io_technologies/usb/USB-Faq.html#Storage The scsa2usb.conf property is mentioned in question 20. yep, that was it. I will keep the drive for more days under observation and then submit an entry for HCL Solaris Express. Rgds, Stefan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] maxtor onetouch III 1TB USB storage snv_b64a
Hey, Anyone any ideas if Solaris can see this device: Maxtor 1TB OneTouch III Turbo Edition USB or firewire ? Connecting this to my Solaris Express build 64a, USB: Jul 19 21:16:27 earth usba: [ID 349649 kern.info] Maxtor OneTouch III 2CAD0L5P Jul 19 21:16:27 earth genunix: [ID 936769 kern.info] scsa2usb0 is /[EMAIL PROTECTED],0/pci1043,[EMAIL PROTECTED],1/[EMAIL PROTECTED] Jul 19 21:16:27 earth genunix: [ID 408114 kern.info] /[EMAIL PROTECTED],0/pci1043,[EMAIL PROTECTED],1/[EMAIL PROTECTED] (scsa2usb0) online Jul 19 21:16:27 earth scsi: [ID 193665 kern.info] sd1 at scsa2usb0: target 0 lun 0 Jul 19 21:16:27 earth genunix: [ID 936769 kern.info] sd1 is /[EMAIL PROTECTED],0/pci1043,[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 Jul 19 21:16:28 earth genunix: [ID 408114 kern.info] /[EMAIL PROTECTED],0/pci1043,[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 (sd1) online Jul 19 21:18:48 earth scsi: [ID 107833 kern.warning] WARNING: /[EMAIL PROTECTED],0/pci1043,[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 (sd1): Jul 19 21:18:48 earth SCSI transport failed: reason 'timeout': retrying command Would firewire work for the storage ? Im not able to see the device using format, rmformat. thanks, stefan This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] maxtor onetouch III 1TB USB storage snv_b64a
couple of more info: - I was able to fdisk it in Redhat AS. In Solaris it was not possible. - The device ships as MacOSX device so I needed to repartion it - Even if I have defined in Redhat AS 2 partitions Im not able to use fdisk nor format, rmformat in S11. Not sure whats going on. stefan This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] maxtor onetouch III 1TB USB storage snv_b64a
Hi Artem, Thanks for comments. - USB: I will try to add reduced-cmd-support=true, reboot my system and see whats going on. - FireWire: I was not able at all to access the disk, the storage is not detected. Stefan This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] maxtor onetouch III 1TB USB storage snv_b64a
For FireWire: nope. Nothing reported from scsa1394 driver. However after your suggestion Im able to see now: c4t0d0p0. [EMAIL PROTECTED]rmformat -l Looking for devices... 1. Logical Node: /dev/rdsk/c4t0d0p0 Physical Node: /[EMAIL PROTECTED],0/pci1043,[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 Connected Device: Maxtor OneTouch III 0303 Device Type: Removable Bus: USB Size: 476.9 GB Label: None Access permissions: Medium is not write protected. 2. Logical Node: /dev/rdsk/c0t0d0p0 Physical Node: /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 Connected Device: HL-DT-ST DVDRAM GSA-4167B DL10 Device Type: CD Reader Bus: IDE Size: Unknown Label: Unknown Access permissions: Unknown Why only 500GB ? Well, I think this device has two modes of operating: RAID 0 and 1. By default it was set as RAID 0 and it was formatted as MacOS partition. I did change that from windows to RAID 1... I will try to swtich it back to RAID 0 and see what I get in Solaris. big thanks for pointers about scsa2usb.conf property. stefan This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Perl 6 on snv_55b x86
Hi, The error is from Sun ld(1). We check to insure a symbol is really encapsulated by a backing section. right. Im wonder to try this in S10, not in Nevada to see the results. In the above, the symbol s44W_info is associated to section .text. The .text section is size 1042 (0x412), but the symbol claims to start at 0x400, and is size 20 (0x14). In other words, the symbol extends past the end of the enclosed section. The elements within libHSCabal.a look a little suspicious. I'd to and discover how the objects within libHSCabal.a were built. If you were to elfdump(1) the archive object, I think you'll discover the same error. the result after elfdump: http://www.nbl.fi/~nbl97/elfdump.libHSCabal.a.out.gz Any ideas what can I do ? Im wonder if I could instruct pugs to use gnu ld and see if that skips this error. So this is a problem how ghc was built in Solaris, right ? I will keep posted the maintainer of Haskell compiler for Solaris x86/sparc about it. thanks for help, Stefan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Perl 6 on snv_55b x86
Jason King wrote: Interestingly, I saw someone have the exact same error messages while trying to link Oracle on a reasonably recent Nevada build (might want to check in database-discuss for details). Don't know if there is a connection, but just seems a bit odd. cheers, I will check the database-discuss group thanks, stefan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Perl 6 on snv_55b x86
hi all, Im trying to get compiled pugs for Solaris Express build 55b. Pugs is documented under: http://www.pugscode.org/ Basically I have downloaded the Haskell compiler and installed temporarily under my home directory. I see that GHC was not compiled using -R so it complains when trying to run it: [EMAIL PROTECTED]ghc ld.so.1: ghc-6.6.1: fatal: libreadline.so.5: open failed: No such file or directory Killed Passing to env the LD_IBRARY_PATH (ugly) I got it running: [EMAIL PROTECTED]env LD_LIBRARY_PATH=/opt/csw/lib ghc ghc-6.6.1: no input files Usage: For basic information, try the `--help' option. So far so good. Now comes the difficult part. When trying to build pugs I get a lot of fatal errors from ld: [EMAIL PROTECTED]env LD_LIBRARY_PATH=/opt/csw/lib perl Makefile.PL *** Probing configuration (please ignore any warnings)... [1 of 1] Compiling Main ( Setup.lhs, Setup.o ) Linking ./Setup ... ld: fatal: symbol `s44W_info' in file /export/home/sparvu/ghc/lib/ghc-6.6.1/libHSCabal.a(Utils__90.o): section [1] .text: size 1042: symbol (address 0x400, size 20) lies outside of containing section ld: fatal: symbol `sax9_info' in file /export/home/sparvu/ghc/lib/ghc-6.6.1/libHSCabal.a(PackageDescription__359.o): section [1] .text: size 642: symbol (address 0x270, size 20) lies outside of containing section ld: fatal: symbol `s5cD_info' in file /export/home/sparvu/ghc/lib/ghc-6.6.1/libHSCabal.a(LocalBuildInfo__133.o): section [1] .text: size 1728: symbol (address 0x6b8, size 32) lies outside of containing section ld: fatal: symbol `s3Pm_info' in file /export/home/sparvu/ghc/lib/ghc-6.6.1/libHSCabal.a(Utils__45.o): section [1] .text: size 291: symbol (address 0x118, size 20) lies outside of containing section ld: fatal: symbol `s46i_info' in file /export/home/sparvu/ghc/lib/ghc-6.6.1/libHSCabal.a(Utils__92.o): section [1] .text: size 830: symbol (address 0x32c, size 20) lies outside of containing section ld: fatal: symbol `s41z_info' in file /export/home/sparvu/ghc/lib/ghc-6.6.1/libHSCabal.a(PreProcess__97.o): section [1] .text: size 484: symbol (address 0x1dc, size 20) lies outside of containing section ld: fatal: symbol `s1Ad_info' in file /export/home/sparvu/ghc/lib/ghc-6.6.1/libHSCabal.a(Unlit__27.o): section [1] .text: size 298: symbol (address 0x118, size 20) lies outside of containing section ld: fatal: symbol `s6DK_info' in file /export/home/sparvu/ghc/lib/ghc-6.6.1/libHSCabal.a(Simple__144.o): section [1] .text: size 450: symbol (address 0x1b0, size 20) lies outside of containing section ld: fatal: symbol `s3aI_info' in file /export/home/sparvu/ghc/lib/ghc-6.6.1/libHSCabal.a(JHC__25.o): section [1] .text: size 1985: symbol (address 0x7b0, size 20) lies outside of containing section ld: fatal: symbol `s2DJ_info' in file /export/home/sparvu/ghc/lib/ghc-6.6.1/libHSCabal.a(Compiler__139.o): section [1] .text: size 649: symbol (address 0x26c, size 40) lies outside of containing section ld: fatal: symbol `s4yS_info' in file /export/home/sparvu/ghc/lib/ghc-6.6.1/libHSCabal.a(ParseUtils__124.o): section [1] .text: size 561: symbol (address 0x220, size 20) lies outside of containing section ld: fatal: symbol `saB3_info' in file /export/home/sparvu/ghc/lib/ghc-6.6.1/libHSCabal.a(PackageDescription__369.o): section [1] .text: size 250: symbol (address 0xe8, size 20) lies outside of containing section ld: fatal: symbol `s3ol_info' in file /export/home/sparvu/ghc/lib/ghc-6.6.1/libHSCabal.a(Program__71.o): section [1] .text: size 2164: symbol (address 0x86c, size 32) lies outside of containing section ld: fatal: symbol `s6oi_info' in file /export/home/sparvu/ghc/lib/ghc-6.6.1/libHSCabal.a(InstalledPackageInfo__233.o): section [1] .text: size 250: symbol (address 0xe8, size 20) lies outside of containing section ld: fatal: symbol `s3EC_info' in file /export/home/sparvu/ghc/lib/ghc-6.6.1/libHSCabal.a(ParseUtils__75.o): section [1] .text: size 182: symbol (address 0xa4, size 20) lies outside of containing section ld: fatal: File processing errors. No output written to ./Setup collect2: ld returned 1 exit status *** Building Setup failed (exit code 256) Please check your GHC and Cabal installation. Anyone any ideas ? Is this a GNU ld / Sun ld issue ? Any other Perl 6 camel around ? thanks, stefan This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Do we even need a reference OpenSolaris binary distro
Ian, 1. We need a better answer to the question, What is OpenSolaris? Ideally, it's something tangible, i.e., something people can download and install. Not exactly, people can see and learn what OpenSolaris is. We already have distros based on OpenSolaris. I dont see useful to have such distro called 'the reference distribution of OpenSolaris.org' - it will make people more confused... Let me share with you the latest findings from FI OSUG: - people need more hardware support in OpenSolaris - already too many types of distros made by Sun: Solaris, Solaris Express, Solaris Express CR, Solaris Express Developer Edition - better representation in conferences and sessions around globe, not only in US I do agree with Darren and I think creating such distro is not a very wise thing to do. Cheers, Stefan This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Changes in Solaris future release
removed or not supported ? Isn't Motif 2.x part of Opengroup, IEEE 1295 specification ? Many commercial companies still use that - Sun currently certifies it, I think. So do we expect to see the runtime of Motif removed in Nevada or future builds ? Im thinking here for companies which currently are using Motif based applications in Solaris. thanks, stefan This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Re: Changes in Solaris future release
Sorry - I've never heard of IEEE 1295. This is the industrial standard of Motif. See http://tinyurl.com/ja3l4 A lot of companies are using IEEE nomenclature inside their documentation base - No - much like we removed the OpenWindows DeskSet tools but still have the Xol Xview libraries, we expect Motif to stay around for a very long time, especially given how many third party apps use it. right. thanks for info. cheers, stefan This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: [Fwd: Proposal to start new project on Streaming Server]
Hi, What is the status of SSS ? Any ideas ? thanks, stefan This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] OpenGL Solaris x86/64 status
Hi, Anyone any ideas what is the status of OpenGL on Solaris x86/64 ? Im tying to help a small firm in Romania to move from Windows/Ubuntu to Solaris x86. They are developing certain OpenGL weather applications and they have asked me what solutions exist for Solaris x86: - OpenGL SDK with nvidia cards supported by Sun - XiG ? - Mesa ? What other people are using to develop 3D applications under Solaris 10 or Nevada ? thanks, stefan This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: OpenGL Solaris x86/64 status
Right, so in other words: get Solaris 10, get a Nvidia video card, install the drivers. After that install Studio11 or use gcc and you should be ready to go to write OpenGL applications ? Are all the OpenGL libraries that I need included with the nvidia drivers ? Do I need anything else to download ? thanks, stefan This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Re: OpenGL Solaris x86/64 status
Cheers, Most likely they will use S10 06/06 and nvidia drivers. But is it possible to write OpenGL applications if not all libraries are delivered by nvidia ? Do we have any HowTo or a tutorial about this for Solaris ? stefan This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Re: Re: OpenGL Solaris x86/64 status
I would need as well glut.h and indeed blastwave has all needed bits. I was expecting to see a complete development SDK with all needed bits to use OpenGL on Solaris x86... Nvidia has the following include/libs: $ ls -lrt /usr/X11/include/NVIDIA/GL/ total 918 -rw-r--r-- 1 root bin29571 May 16 00:44 glxext.h -rw-r--r-- 1 root bin13644 May 16 00:44 glx.h -rw-r--r-- 1 root bin 339652 May 16 00:44 glext.h -rw-r--r-- 1 root bin72949 May 16 00:44 gl.h and [EMAIL PROTECTED]ls -lrt /usr/X11/lib/NVIDIA/ total 17754 -rw-r--r-- 1 root bin 8464396 May 16 00:42 libGLcore.so.1 -rw-r--r-- 1 root bin 595400 May 16 00:42 libGL.so.1 -rw-r--r-- 1 root bin 1944 May 16 00:42 libnvidia-tls.so.1 drwxr-xr-x 2 root bin 512 Aug 6 23:19 amd64 lrwxrwxrwx 1 root root 10 Aug 6 23:19 libGL.so - libGL.so.1 lrwxrwxrwx 1 root root 18 Aug 6 23:19 libnvidia-tls.so - libnvidia-tls.so.1 Where are: libGLU*.so libglut.so etc ? I know libglut is an external library but it is very used on many examples of OpenGL. Looks like many bits are missing... What can I do ? Install Mesa and GLUT from blastwave and simple use only that ? I can't mix NVIDIA include and lib with /opt/csw ... do I get this right that NVIDIA has a runtime OpenGL environment delivered for Solaris x86 but not a development set of libraries ? So if you want to develop on Solaris x86/64 right now what can you do ? Many thanks, stefan This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Oracle 10.2.0.1 on B42?
Hi John, Check Sun's SystemV IPC documentation: http://docs.sun.com/app/docs/doc/817-0547/6mgbdbsn6?a=view#whatsnew_403_da-1 seminfo_semmsl - process.max-sem-nsems and the default is 512. No worries to set that anymore ... as Oracle suggests. It is, I bet, a mistake under Oracle site http://download-uk.oracle.com/docs/cd/B19306_01/install.102/b15705/toc.htm#BABIAECC which should already know that by default in 10 the default value is 512 ... The one you try to set is: project.max-sem-ids refers to semsys:seminfo_semmni which by default is 128 so no worries again :) So check one more time the Sun's page with all SystemV IPC and match that with Oracle. I have a project too where I have to do the same... so I would need to match what has changed in S10 with Oracle's docs. Oracle is a bit confusing now the tings in their pages since some parameters dont exist anymore. e.g from Sun: The following related parameters have been removed. If these parameters are included in the /etc/system file on this Solaris system, the parameters are commented out. semsys:seminfo_semmns semsys:seminfo_semvmx semsys:seminfo_semmnu semsys:seminfo_semaem semsys:seminfo_semume semsys:seminfo_semusz semsys:seminfo_semmap shmsys:shminfo_shmseg shmsys:shminfo_shmmin msgsys:msginfo_msgmap msgsys:msginfo_msgseg msgsys:msginfo_msgssz msgsys:msginfo_msgmax and Oracle says pls set the following: semsys:seminfo_semmnsNA 1024 !? Hope it helps, stefan This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Re: Sun lost one of it's biggest and oldest x86 customer
No major IBM's SW had been open sourced, as far as I know. Exactly. IBM has done nothing to open source their software stack: z/OS, AIX, DB2, Websphere. I think they are not even looking to do that... since it is very complicated, time consuming - much easier: confuse the world with Linux, sign the deal and then turn to mainframe business :) Some years ago I was looking to buy AIX to experiment. The price they asked for the computer and software was too high for my wallet so I tried to contact them to get some help... This was only for my personal use... It was like mission impossible 1000. IBM Finland has never returned any calls nor emails, nothing... Simple a very big waste of my time. So there is a very big question mark what means for these companies Linux vs their own software stack... From my point of view: same old story goes over and over again: HP, IBM, Novell they all are loving Linux to make room for their own obsolete products. Does IBM, HP or Novell now run their internal business on Linux... ? What about all their web services ? Im not sure about that... stefan This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: StarOffice 8 and Solaris Express
I sent similar feedback during S10U2 Beta program. And I think Im not alone here :) At least we should see that in Express. stefan This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Delete files older than 1 hr
[EMAIL PROTECTED]uname -a SunOS earth 5.11 snv_36 i86pc i386 i86pc [EMAIL PROTECTED]which find /usr/bin/find [EMAIL PROTECTED]man find [...] -mmin n File's data was last modified n minutes ago. So you gotta use a newer version of Solaris. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Delete files older than 1 hr
Not sure but how about if you give a try to Mr. Joerg Schilling sfind utility... Simple point your browser to: http://www.blastwave.org/packages.php/schilyutils and start installing the CSWschilyutils Everything will go to /opt/csw/bin and therte you will have sfind. Read the man page. I bet sfind knows that. This is one solution. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Delete files older than 1 hr
well I should have said: 1. Download pkg-get from http://www.blastwave.org/pkg-get.php 2. pkgadd -d pkg_get.pkg 3. /opt/csw/bin/pkg-get -i schilyutils that's it. I've tried on my system: works fine. hope it helps, stefan This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: RE: PlatinGUI for SAP on Solaris x86
hehe... this reminds me of HP Openview ICM Tool which is 100% Java but requires Windows, Tivoli Client and Desktop which both are 100% Java but don't run unless your OS is supported... stefan This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Re: 4113420 (request for ksh93 integration)
Hi, We should think to have /bin/sh as ksh93. It is elegant and simple to do. Are there any objections why /bin/sh cannot be a ksh93 ? On other note: Im wonder what would happen with kstat(1M) when Perl6 would be out. I bet Perl5 would stay as it is somewhere around and Perl6 might be installed some other place. thanks, stefan This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: 4113420 (request for ksh93 integration)
I think we'd love to be able to make that change but I don't think we can. Why can't we do that ? Every sh script should work ok in ksh93. Isn't it ? Then we don't have so many other choices... we could deliver then something like /usr/ksh93 as we do with Perl5 - /usr/perl5 Im wonder when Perl6 will be out would we install it under /usr/perl6 ? Same thing we could do for ksh93. It is kind of strange.. but better to find a 93 version around than nothing :) rgds, stefan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: 4113420 (request for ksh93 integration)
Uaau, I see we have now a dedicated ksh93 migration forum: http://www.opensolaris.org/jive/forum.jspa?forumID=103 I hope folks will agree and get this fixed somehow. stefan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Perl 6 on SE or S10 ?
Hi, Any experiments with Perl6/Parrot and Solaris Express or Solaris 10 ? Im curious how much the language has changed and how well the new VM would work in Solaris ... thanks, stefan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Please update 4113420 (request for ksh93 integration)
I'm worried not about what Sun ships as part of the OS
(though I'm not too thrilled about regression testing patchadd/patchrm)
but about products and home grown scripts in the field.
Correct. If you check the file: src/cmd/ksh93/COMPATIBILITY from the ast-ksh
package you can see a complete list of the most know problems when doing 88 to
93:
KSH-93 VS. KSH-88
The following is a list of known incompatibilities between ksh-93 and ksh-88.
I have not include cases that are clearly bugs in ksh-88. I also have
omitted features that are completely upward compatible.
1. Functions, defined with name() with ksh-93 are compatible with
the POSIX standard, not with ksh-88. No local variables are
permitted, and there is no separate scope. Functions defined
with the function name syntax, maintain compatibility.
This also affects function traces.
2. ! is now a reserved word. As a result, any command by that
name will no longer work with ksh-93.
3. The -x attribute of alias and typeset -f is no longer
effective and the ENV file is only read for interactive
shells. You need to use FPATH to make function definitions
visible to scripts.
4. A built-in command named command has been added which is
always found before the PATH search. Any script which uses
this name as the name of a command (or function) will not
be compatible.
5. The output format for some built-ins has changed. In particular
the output format for set, typeset and alias now have single
quotes around values that have special characters. The output
for trap without arguments has a format that can be used as input.
6. With ksh-88, a dollar sign ($') followed by a single quote was
interpreted literally. Now it is an ANSI-C string. You
must quote the dollar sign to get the previous behavior.
Also, a $ in front of a indicates that the string needs
to be translated for locales other than C or POSIX. The $
is ignored in the C and POSIX locale.
7. With ksh-88, tilde expansion did not take place inside ${...}.
with ksh-93, ${foo-~} will cause tilde expansion if foo is
not set. You need to escape the ~ for the previous behavior.
8. Some changes in the tokenizing rules where made that might
cause some scripts with previously ambiguous use of quoting
to produce syntax errors.
9. Programs that rely on specific exit values for the shell,
(rather than 0 or non-zero) may not be compatible. The
exit status for many shell failures has been changed.
10. Built-ins in ksh-88 were always executed before looking for
the command in the PATH variable. This is no longer true.
Thus, with ksh-93, if you have the current directory first
in your PATH, and you have a program named test in your
directory, it will be executed when you type test; the
built-in version will be run at the point /bin is found
in your PATH.
11. Some undocumented combinations of argument passing to ksh
builtins no longer works since ksh-93 is getopts conforming
with respect to its built-ins. For example, typeset -8i
previously would work as a synonym for typeset -i8.
12. Command substitution and arithmetic expansion are now performed
on PS1, PS3, and ENV when they are expanded. Thus, ` and $(
as part of the value of these variables must be preceded by a \
to preserve their previous behavior.
13. The ERRNO variable has been dropped.
14. If the file name following a redirection symbol contain pattern
characters they will only be expanded for interactive shells.
15. The arguments to a dot script will be restored when it completes.
16. The list of tracked aliases is not displayed with alias unless
the -t option is specified.
17. The POSIX standard requires that test $arg have exit status
of 0, if and only if $arg is null. However, since this breaks
programs that use test -t, ksh93 treats an explicit test -t
as if the user had entered test -t 1.
18. The ^T directive of emacs mode has been changed to work the
way it does in gnu-emacs.
19. ksh-88 allowed unbalanced parenthes within ${name op val} whereas
ksh-93 does not. Thus, ${foo-(} needs to be written as ${foo-\(}
which works with both versions.
20. kill -l in ksh-93 lists only the signal names, not their numerical
values.
21. Local variables defined by typeset are statically scoped in
ksh93. In ksh88 they were dynamically scoped although this
behavior was never documented.
22. The value of the variable given to getopts is set to ? when
the end-of-options is reached to conform to the POSIX standard.
23. Since the POSIX standard requires
[osol-discuss] Re: snv_b28 this week ?
ok, thanks. stefan This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] snv_b28 this week ?
Hey, Any ideas when build28 should be out ? This week ? Thanks, Stefan This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
