Re: [osol-discuss] build 130 nonsense
On Jan 3, 2010, at 6:53 AM, andrew wrote: On 01/ 1/10 10:36 AM, andrew wrote: Sorry - my mistake. Still looking for ability to install from local files though. ;-) You can do that now as long as you're willing to run a depot server (which is a very light-weight easy to start/run process). However, if you're wanting to install from files without running a depot server, that's still work in progress. Thanks for the info. However, I am still surprised that there is no ability to install from local files as we approach for 4th release. On the face of it, it would seem an easy thing to add. I guess if I really needed it I could add it myself. It isn't as trivial to add it as it might seem at first glance, which is why it didn't get done for this release. It was originally planned, but there has simply been been too much else needed for this release (2010.x). There was significant foundational or higher priority work that had to be done first. The pkg(5) project is now at a point where new subsystems require significant planning and analysis. An on-disk format is something that once added has to remain relatively stable. As such, any formal introduction of it has been purposefully delayed to ensure that there is as little pain as possible. Please remember that the needs of the pkg(5) system are primarily driven by what is required to deliver OpenSolaris and the project is still in the process of addressing user needs. -Shawn ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] OpenSolaris, Solaris 10, SXCE, Indiana: which to use for a developer?
On Jan 2, 2010, at 1:03 PM, Claus Assmann wrote: On Sat, Jan 02, 2010, Jürgen Keil wrote: [OpenSolaris Indiana: GNU?] Well, it does have both the gnu utilities (/usr/gnu/bin) and the solaris counterparts, and in the default setup the /usr/gnu/bin directory is ahead of /usr/bin in $PATH. I simply removed /usr/gnu/bin from $PATH, but I still got vim instead of vi[1] (in /usr/bin AFAIR), and bash as root sh. That's when I stopped using it and looked for alternatives. If there is a way to configure OpenSolaris to be(have) like Sun's Solaris (for which I develop software and to which I'm used (besides *BSD)), then please let me know. PS: [1] yes, vi on Solaris has some ugly restrictions, but nvi would be a more appropriate alternative (just remove the restrictions, don't change the behaviour). The vi that was previously delivered was replaced with vim's vi compatibility mode. The reason? The vi traditionally delivered with Solaris is essentially completely unmaintained. As has been discussed before, much of the Solaris userland is being obsoleted, dropped, or replaced as appropriate in favour of maintained or modern versions of utilities. I know this may not please some people, but which would you rather have? A known buggy, unmaintained for years version of vi, or a recent version of vim with vi compatibility? With that said, you can often find the older versions of many utilities that have been obsoleted in /usr/has/bin. In this particular case, you can find the version of vi you are likely looking for as: /usr/has/bin/vi This move was intentional to get users to start using the alternative versions in hopes of exposing any shortcomings and to discourage usage of the old ones. -Shawn ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] snv_130
On Jan 4, 2010, at 7:10 PM, Ian Collins wrote: Alan Coopersmith wrote: Volker A. Brandt wrote: Happy new year every1! 130 is the final SXCE release planned though, as previously announced. Which is too bad, really. Maybe the infrastructure to build SXCE can be kept in place a little bit longer. The final release of SXCE could then be cut in sync with the official OS 2010.02 release. The problem is it's dividing our attention - by ending SXCE at 130, that concentrates all testing and development on OpenSolaris for builds 131-136 for the OpenSolaris 2010.03 release. And once ON converts it's gate to build IPS packages instead of SVR4, it won't be possible to build SXCE anymore, since they're not planning on maintaining two sets of packaging metadata in the ON gate. It would have been nice to have held off killing SXCE until there was a migration path to OpenSolaris Sure, but realistically, it isn't cost or resource effective. SXCE releases are all about testing. Users that need something stable and supported should be either running the release versions of Solaris 10 or OpenSolaris 200x. As Alan said, running two release trains is tying up resources that are better spent focused on the rapidly maturing OpenSolaris builds. -Shawn ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] any work on bug ID 6807184
Hi Masa, Thx for responding: I have used netperf, here's the ouput: jer...@ex58ud501:~/Downloads/netperf-2.4.5/src# ./netperf TCP STREAM TEST from :::0.0.0.0 (0.0.0.0) port 0 AF_INET to ex58ud501 (127.0.0.1) port 0 AF_INET Recv SendSend Socket Socket Message Elapsed Size SizeSize Time Throughput bytes bytes bytessecs.10^6bits/sec 49152 49152 491529.99 27911.98 jer...@ex58ud501:~/Downloads/netperf-2.4.5/src# ./netperf -f M TCP STREAM TEST from :::0.0.0.0 (0.0.0.0) port 0 AF_INET to ex58ud501 (127.0.0.1) port 0 AF_INET Recv SendSend Socket Socket Message Elapsed Size SizeSize Time Throughput bytes bytes bytessecs.MBytes/sec 49152 49152 491529.99 3299.83 jer...@ex58ud501:~/Downloads/netperf-2.4.5/src# zpool iostat capacity operationsbandwidth pool used avail read write read write -- - - - - - - bromine 902G 26.2G 0 0477 76 chlorine12.4G 916G 0 0845336 fluorine 387G 541G 0 0434 8 iodine 73.3G 855G 3 0 384K 8 rpool 22.4G 46.6G 4 4 212K 247K -- - - - - - - I must say if I read this correctly, I definitely would suspect ZFS is the culprit... Still, any pointers and suggestions are still welcome as I entered another world of hurt ;-) J. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Syslog-ng?
I was able to compile and install it using http://pkgbuild.sourceforge.net/ a) Install SFE environment and build pkgtool and cd /path/to/build/of/packages/spec-files-extra.2009116 b) pkgtool build-only --svr4 --download --autodeps --interactive SFEeventlog.spec (build-only, because installation failed - requires manual intervention) pfexec pkgadd -d /path/to/build/of/packages/PKGS SFEeventlog (install package) c) pkgtool build --svr4 --download --autodeps --interactive SFEsyslog-ng.spec In step c) you will have build and installed syslog.ng package: pkginfo | grep SFE SFE SFEeventlog Library needed by Syslog-ng SFE SFEsyslog-ng Syslog-ng tries to fill the gaps original syslogd's were lacking SFE SFEsyslog-ng-rootSyslog-ng tries to fill the gaps original syslogd's were lacking - / filesystem Note that i have used svr4 option (you can experiment with IPS, but you need too install local IPS server) Regards. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] OpenSolaris, Solaris 10, SXCE, Indiana: which to use for a developer?
Shawn Walker swal...@opensolaris.org wrote: The vi that was previously delivered was replaced with vim's vi compatibility mode. The reason? The vi traditionally delivered with Solaris is essentially completely unmaintained. As has been discussed before, much of the Solaris userland is being obsoleted, dropped, or replaced as appropriate in favour of maintained or modern versions of utilities. The vi delivered with Solaris behaves like vi while the vi re-implementations don't. Note that most of the GNU userland is essentially unmaintained *) and incompatible to the POSIX standard. It would be a big mistake to switch to the GNU userland as the GNU userland is even unwanted by most Solaris users. *) GNU tar recently partially fixed a bug that I reported in 1993 and GNU make did never fix a serious design bug that I reported in 1998. There is no OS specific support in the GNU userland - GNU tar does not even support a single Linux specific feature. In order to change to modern implemenmtations, Sun would need to start collaboration with the OSS community - see the star desaster caused by Sun. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Here's some more info for bugster CR 6913752
andrew wrote: It doesn't have an option to use external power, however I'm assuming I can power it off a USB port on another PC. I'll give that a try tomorrow. I can tell you that the power is shut off to the USB port since the eSATA enclosure has a blue light that is illuminated when power is applied, and it goes out. Windows 7 leaves it powered when it suspends to disk (booted off the internal drive) whereas OpenSolaris doing an S3 suspend powers it down. It has no real reason to keep the USB port powered though, since it doesn't know that's how the drive is being powered. The paranoid part of me says this could be a bad idea (floating voltage levels between the two PC's power supplies, etc...). An alternative could be to plug in a powered USB hub to this system, then power the drive from the powered hub. Brian -- Brian Ruthven Solaris Revenue Product Engineering Sun Microsystems UK Sparc House, Guillemont Park, Camberley, GU17 9QG ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] snv_130
Shawn Walker wrote: On Jan 4, 2010, at 7:10 PM, Ian Collins wrote: Alan Coopersmith wrote: Volker A. Brandt wrote: Happy new year every1! 130 is the final SXCE release planned though, as previously announced. Which is too bad, really. Maybe the infrastructure to build SXCE can be kept in place a little bit longer. The final release of SXCE could then be cut in sync with the official OS 2010.02 release. The problem is it's dividing our attention - by ending SXCE at 130, that concentrates all testing and development on OpenSolaris for builds 131-136 for the OpenSolaris 2010.03 release. And once ON converts it's gate to build IPS packages instead of SVR4, it won't be possible to build SXCE anymore, since they're not planning on maintaining two sets of packaging metadata in the ON gate. It would have been nice to have held off killing SXCE until there was a migration path to OpenSolaris Sure, but realistically, it isn't cost or resource effective. SXCE releases are all about testing. Users that need something stable and supported should be either running the release versions of Solaris 10 or OpenSolaris 200x. Oh I agree, but I bet there's a lot of us who have been using, live upgrading, testing and providing feedback on SXCE since it was a stroppy teenager and haven't made the leap into the OpenSolaris realm. It's been too stable for its own good. -- Ian. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] PKG - dev repository
Hi, I configured my repository to http://pkg.opensolaris.org/dev/ and always that i use pkg image-update the system is upgraded to the last version (snv_130 now). But i don't want the snv_130. Is there any configuration on pkg that i can set to upgrade the opensolaris snv_111 (release) to snv_126, for example? Thanks, Vinicius Viteri ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] build 130 nonsense
On Jan 3, 2010, at 6:53 AM, andrew wrote: On 01/ 1/10 10:36 AM, andrew wrote: Sorry - my mistake. Still looking for ability to install from local files though. ;-) You can do that now as long as you're willing to run a depot server (which is a very light-weight easy to start/run process). However, if you're wanting to install from files without running a depot server, that's still work in progress. Thanks for the info. However, I am still surprised that there is no ability to install from local files as we approach for 4th release. On the face of it, it would seem an easy thing to add. I guess if I really needed it I could add it myself. It isn't as trivial to add it as it might seem at first glance, which is why it didn't get done for this release. It was originally planned, but there has simply been been too much else needed for this release (2010.x). There was significant foundational or higher priority work that had to be done first. The pkg(5) project is now at a point where new subsystems require significant planning and analysis. An on-disk format is something that once added has to remain relatively stable. As such, any formal introduction of it has been purposefully delayed to ensure that there is as little pain as possible. Please remember that the needs of the pkg(5) system are primarily driven by what is required to deliver OpenSolaris and the project is still in the process of addressing user needs. I haven't looked at the code but I was kind of assuming that I wouldn't need to implement an on-disk format - just replace code to suck files off the network with code to fetch them off disk. However, I have absolutely no knowledge of how any of it actually works. ;-) Thank you for the clarification about what stage the development of IPS is at. Cheers Andrew. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] X problem fixed in build 131? (bug 13598)
As reported in bug 13598[1] (opened by me) the changes in build 130 introduce a bug related to DRM with Intel video card, any hope to see that fixed in build 131? Thanks! [1] http://defect.opensolaris.org/bz/show_bug.cgi?id=13598 -- Luca Morettoni luca(AT)morettoni.net | OpenSolaris SCA #OS0344 Web/BLOG: http://www.morettoni.net/ | http://twitter.com/morettoni jugUmbria founder: https://jugUmbria.dev.java.net/ ITLOSUG leader: http://hub.opensolaris.org/bin/view/User+Group+itl-osug/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] PKG - dev repository
Not that I am aware of. You could just download that particular release as an ISO and install it... On Tue, Jan 5, 2010 at 21:51, Vinicius Segantin Viteri vinicius.vit...@gmail.com wrote: Hi, I configured my repository to http://pkg.opensolaris.org/dev/ and always that i use pkg image-update the system is upgraded to the last version (snv_130 now). But i don't want the snv_130. Is there any configuration on pkg that i can set to upgrade the opensolaris snv_111 (release) to snv_126, for example? Thanks, Vinicius Viteri ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] PKG - dev repository
This has been discussed before on this list (I don't have a reference handy , but google should be your friend here, and I think it was Nick Todd who posted it). From memory, the steps are something like this: beadm create snv-126 beadm mount snv-126 /mnt pkg install -R /mnt ent...@0.5.11,5.11-0.126 bootadm update-archive -R /mnt beadm unmount snv-126 beadm activate snv-126 reboot I don't recall whether the update-archive is necessary (I think it is), but it wouldn't hurt anyway. Regards, Brian Vinicius Segantin Viteri wrote: Hi, I configured my repository to http://pkg.opensolaris.org/dev/ and always that i use pkg image-update the system is upgraded to the last version (snv_130 now). But i don't want the snv_130. Is there any configuration on pkg that i can set to upgrade the opensolaris snv_111 (release) to snv_126, for example? Thanks, Vinicius Viteri ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org -- Brian Ruthven Solaris Revenue Product Engineering Sun Microsystems UK Sparc House, Guillemont Park, Camberley, GU17 9QG ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Here's some more info for bugster CR 6913752
div id=jive-html-wrapper-div br br andrew wrote: blockquote cite=mid:1485805089.881262654193109.JavaMail.Twebapp sf-app1 type=cite pre wrap=!It doesn't have an option to use external power, however I'm assuming I can power it off a USB port on another PC. I'll give that a try tomorrow. I can tell you that the power is shut off to the USB port since the eSATA enclosure has a blue light that is illuminated when power is applied, and it goes out. Windows 7 leaves it powered when it suspends to disk (booted off the internal drive) whereas OpenSolaris doing an S3 suspend powers it down. It has no real reason to keep the USB port powered though, since it doesn't know that's how the drive is being powered. The drive seems to work fine powered from a second PC. Unfortunately the failure mode here is exactly the same - OpenSolaris resumes slowly from S3 but fails to bring back the console display. I don't have a keyboard for the second PC at the moment so I can't SSH into the OpenSolaris box to see what is going on, but when I do I'll have a poke around. What stuff should I be looking at? Thanks Andrew. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] X problem fixed in build 131? (bug 13598)
Luca Morettoni wrote: As reported in bug 13598[1] (opened by me) the changes in build 130 introduce a bug related to DRM with Intel video card, any hope to see that fixed in build 131? Thanks! [1] http://defect.opensolaris.org/bz/show_bug.cgi?id=13598 Since build 131 closed last night and is being built and tested now, not really, unless someone else reported it and it was already fixed. -- -Alan Coopersmith- alan.coopersm...@sun.com Sun Microsystems, Inc. - X Window System Engineering ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Using OpenSolaris as a security gateway
Hi all,
I need to deploy a new perimetral security infraestructure to install the
following services:
- High availability and load balacing firewalls
- VPNs
- IDS/IPS
My first choice to install this scenario is to use openBSD, but will be possible
to do this with opensolaris?? The mos important point is high availability features ...
Thanks.
--
CL Martinez
carlopmart {at} gmail {d0t} com
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [osol-discuss] new vi [was: OpenSolaris, Solaris 10, SXCE, ....]
On Tue, Jan 05, 2010, Shawn Walker wrote: I know this may not please some people, but which would you rather have? A known buggy, unmaintained for years version of vi, or a recent version of vim with vi compatibility? What about a 3rd choice: nvi (or vi from OpenBSD who updated their version to fix all the bugs: it is freely available for reuse...). That would have the same behaviour as the original vi without the restrictions/bugs. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] build 130 nonsense
On 01/ 5/10 06:12 AM, andrew wrote: On Jan 3, 2010, at 6:53 AM, andrew wrote: On 01/ 1/10 10:36 AM, andrew wrote: Sorry - my mistake. Still looking for ability to install from local files though. ;-) You can do that now as long as you're willing to run a depot server (which is a very light-weight easy to start/run process). However, if you're wanting to install from files without running a depot server, that's still work in progress. Thanks for the info. However, I am still surprised that there is no ability to install from local files as we approach for 4th release. On the face of it, it would seem an easy thing to add. I guess if I really needed it I could add it myself. It isn't as trivial to add it as it might seem at first glance, which is why it didn't get done for this release. It was originally planned, but there has simply been been too much else needed for this release (2010.x). There was significant foundational or higher priority work that had to be done first. The pkg(5) project is now at a point where new subsystems require significant planning and analysis. An on-disk format is something that once added has to remain relatively stable. As such, any formal introduction of it has been purposefully delayed to ensure that there is as little pain as possible. Please remember that the needs of the pkg(5) system are primarily driven by what is required to deliver OpenSolaris and the project is still in the process of addressing user needs. I haven't looked at the code but I was kind of assuming that I wouldn't need to implement an on-disk format - just replace code to suck files off the network with code to fetch them off disk. However, I have absolutely no knowledge of how any of it actually works. ;-) Thank you for the clarification about what stage the development of IPS is at. I will just add that we have built experimental media that included a repository and hacked up an installer that could install from that repository. The performance was not usable (6+ hour install times, as I recall), because the performance of random access to files (which is what happens in reading from the repository) on stream-oriented media like DVD's is hideously bad. Dave ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Change Logs (or something similar) for dev releases?
Hi Folks, I'm curious if there is a good location that contains a list of changes, enhancements, bug fixes, etc for each OpenSolaris dev release? The email that comes out on opensolaris-announce, as far as I can tell, only includes IPS bugfixes, etc. I've also found the Flag Days pages, http://hub.opensolaris.org/bin/view/Community+Group+on/126-130, which are a little more inclusive, but don't appear to have been updated for the latest releases. Is there a better place I can look? Thanks... --joe ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Change Logs (or something similar) for dev releases?
Joseph Mocker wrote: Hi Folks, I'm curious if there is a good location that contains a list of changes, enhancements, bug fixes, etc for each OpenSolaris dev release? The email that comes out on opensolaris-announce, as far as I can tell, only includes IPS bugfixes, etc. I've also found the Flag Days pages, http://hub.opensolaris.org/bin/view/Community+Group+on/126-130, which are a little more inclusive, but don't appear to have been updated for the latest releases. The scripts that update that were broken by the transition from the old website to the new one and are in the process of being fixed still. Is there a better place I can look? Some consolidations publish their changelogs, but most don't. The ones that I know of that do: ON (The kernel, drivers, and core utilities): http://dlc.sun.com/osol/on/downloads/b129/on-changelog-b129.html X Window System: http://hub.opensolaris.org/bin/view/Community+Group+x_win/changelogs-nv_120 Desktop (GNOME, Mozilla, Evolution, etc.): http://src.opensolaris.org/source/xref/jds/spec-files/branches/gnome-2-28/ChangeLog http://src.opensolaris.org/source/xref/jds/spec-files-other/branches/gnome-2-28/ChangeLog Of course, internally you can see the RTC's filed for each build, which lists all the bugster bug ids for the consolidations that use it, but that's only helpful for people with access behind the Sun firewalls. -- -Alan Coopersmith- alan.coopersm...@sun.com Sun Microsystems, Inc. - X Window System Engineering ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] new member: documentation contributor
On 22 Dec 2009, at 06:25, Vikram Dhillon wrote: Hi all, Hope everyone is doing good. I am currently writing documentation for Ubuntu, Kubuntu, GNOME, KDE, Firefox and FreeBSD so I have some experience in writing :D Now I would like to get started with documentation in OpenSolaris, I have read the wiki pages and I would like to work with a sponsor to get started with docs. please help me out here. I really appreciate your help guys :) If you haven't found a sponsor yet, you might be better asking over on the docs-discuss mailing list: http://mail.opensolaris.org/mailman/listinfo/docs-discuss Cheeri, Calum. -- CALUM BENSON, Interaction Designer Sun Microsystems Ireland mailto:calum.ben...@sun.comOpenSolaris Desktop Team http://blogs.sun.com/calum +353 1 819 9771 Any opinions are personal and not necessarily those of Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Bugster CR 6889221 Intel IOMMU fix which helps M10 shutdown bug CR 6913815
The following comments were added to CR 6913815: This is a IOMMU related issue. It's a dup of 6884091 Portege R600 doesn't power all-the-way down after poweroff is uttered if IOMMU is enabled Vikram is having a fix for this via 6889221, so I'm closing this as a dup of 6889221 also. Can you tell me if this fix is expected to make it into build 131 or 132, i.e. in time for 2010.02? Thanks Andrew. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] build 130 nonsense
On 01/ 5/10 06:12 AM, andrew wrote: On Jan 3, 2010, at 6:53 AM, andrew wrote: On 01/ 1/10 10:36 AM, andrew wrote: Sorry - my mistake. Still looking for ability to install from local files though. ;-) You can do that now as long as you're willing to run a depot server (which is a very light-weight easy to start/run process). However, if you're wanting to install from files without running a depot server, that's still work in progress. Thanks for the info. However, I am still surprised that there is no ability to install from local files as we approach for 4th release. On the face of it, it would seem an easy thing to add. I guess if I really needed it I could add it myself. It isn't as trivial to add it as it might seem at first glance, which is why it didn't get done for this release. It was originally planned, but there has simply been been too much else needed for this release (2010.x). There was significant foundational or higher priority work that had to be done first. The pkg(5) project is now at a point where new subsystems require significant planning and analysis. An on-disk format is something that once added has to remain relatively stable. As such, any formal introduction of it has been purposefully delayed to ensure that there is as little pain as possible. Please remember that the needs of the pkg(5) system are primarily driven by what is required to deliver OpenSolaris and the project is still in the process of addressing user needs. I haven't looked at the code but I was kind of assuming that I wouldn't need to implement an on-disk format - just replace code to suck files off the network with code to fetch them off disk. However, I have absolutely no knowledge of how any of it actually works. ;-) Thank you for the clarification about what stage the development of IPS is at. I will just add that we have built experimental media that included a repository and hacked up an installer that could install from that repository. The performance was not usable (6+ hour install times, as I recall), because the performance of random access to files (which is what happens in reading from the repository) on stream-oriented media like DVD's is hideously bad. That's interesting - I guess you do need an on-disk format for that. There are two obvious use cases for a file-based package: 1 is to do an OS install, the other is to just add packages to a system after you download them. It is sometimes quicker to download a tarbar and install it than it is to use pkg to suck each seperate file over the network. The obvious example is the SUNWman package. Cheers Andrew. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Bugster CR 6889221 Intel IOMMU fix which helps M10 shutdown bug CR 6913815
Hi, The fix is on track to make build 132 and 2010.02. I have checked this issue. The R600 does power off but it takes a very long time (approx 2-3 minutes). Vikram On Tuesday 05 January 2010 10:12:39 am andrew wrote: The following comments were added to CR 6913815: This is a IOMMU related issue. It's a dup of 6884091 Portege R600 doesn't power all-the-way down after poweroff is uttered if IOMMU is enabled Vikram is having a fix for this via 6889221, so I'm closing this as a dup of 6889221 also. Can you tell me if this fix is expected to make it into build 131 or 132, i.e. in time for 2010.02? Thanks Andrew. -- Your talents will be recognized and suitably rewarded. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] snv_130
Oh I agree, but I bet there's a lot of us who have been using, live upgrading, testing and providing feedback on SXCE since it was a stroppy teenager and haven't made the leap into the OpenSolaris realm. It's been too stable for its own good. -- Ian. Of course! I have been using SXCR (?) since at least build_26 (the earliest build that I still keep a complete set of CDs--there was no DVD then). I will be more than happy for Sun's developers to continue to provide all those conveniences as well as the great live upgrade services as you mentioned for me for free, while I don't have to give anything of value in return (Sun itself has an excellent QA team for Solaris anyway). But for the long-term health of Solaris, I chose to switch to OpenSolaris as soon as it became available. At the present time, I am not yet able to contribute, but at least I filed my complaints. :-) -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Trying 2009.06 on T42 laptop, can't get Samsung Ptr to work. Help?
Hi all, Hoping someone can help with this. I went to the HCL pages and the T42 was listed as compatible for OpenSolaris, but I couldn't find anything on my printer which is a Samsung ML-1740 laser printer (cheap one from around 2005.) Is it possible to get it up and running? I tried the Manager tool and it said it was ready, but nothing printed, so I'm assuming it's a driver issue. Any suggestions? I'm doing all of this under Live CD before I install. If I install; at this rate I need the printer, otherwise I'll have to go with LINUX. Thanks, Kim -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Bugster CR 6889221 Intel IOMMU fix which helps M10 shutdown bug CR 6913815
Hi, The fix is on track to make build 132 and 2010.02. I have checked this issue. The R600 does power off but it takes a very long time (approx 2-3 minutes). Cool - thanks for the update. Andrew. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] redirect command --help to file
Hi folks [Please add me CC] How to redirect command --help to file? Why normal way doesn't work? keytool --help /tmp/keytool or keytool --help | tee /tmp/keytool keytool usage: [...] cat /tmp/keytool [-providerClass provider_class_name [-providerArg arg]] ... cheers Sven ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] redirect command --help to file
Sven Aluoor wrote: Hi folks [Please add me CC] How to redirect command --help to file? Why normal way doesn't work? keytool --help /tmp/keytool The help text is written to stderr, not stdout. From sh or ksh, try keytool --help 2/tmp/keytool instead. Scott -- Scott Rotondo Principal Engineer, Solaris Security Technologies President, Trusted Computing Group Phone/FAX: +1 408 850 3655 (Internal x68278) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] virt-manager hangs
I am running Solaris Express Community Edition snv_127 X86. I am having promblems running virt-manager (the GUI XVM manager.) When I run virt-manager I get the following warning: Gtk-Message: Failed to load module pk-gtk-module: ld.so.1: isapython2.4: fatal: libpk-gtk-module.so: open failed: No such file or directory Virt-manager does load but when I click connect it hangs up. THis is either via ssh (ssh -X) or VNC. The solaris server usually does not run a GUI console. I can run virt-manager from my Fedora Core 11 Linux PC and connect to the XVM service on the Solaris machine. However it does not let be browse for installation media. I have tried compiling the latest virt-manager from source- no luck yet. This did work on another machine running OpenSolaris 2008.11 1 snv_101b_rc2 X86 Any advice? Thanks -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Using OpenSolaris as a security gateway
I personally would not use OpenSolaris for a minimal firewall appliance because the OpenSolaris 2009.06 Caimain installer is very inflexible: It forces you to use DHCP (there's no way to set a static IP address set during the installation process- and you obviously don't want network auto-magic and avahi running on a firewall) and it also forces you to install a fully functional GNOME desktop X-windows environment (whether you want it to install this or not), and obviously in a minimal firewall setup you wouldn't want GNOME running because it adds more potential security vulnerabilities. If you're doing a firewall and want to use Solaris I would go with the free download of Solaris 10 U9: http://www.sun.com/software/solaris/get.jsp or if you really need crossbow for virtualized networking maybe try Solaris Express but be warned that Solaris Express is an unstable development product that is in the process of being killed off by the Solaris community, so make sure you download it fast, because it is currently at build 129 and will be discontinued after build 130. You can use the Solaris 10 installer (see pictures below): http://www.sun.com/software/solaris/howtoguides/installationhowto.jsp and you can use Interactive Text Console Session to do a text install and assign a static IP address and only install a very small, minimal amount of packages (no GNOME desktop or X-windows) to the firewall. In my opinion, OpenBSD is probably the best OS for firewalls if all you want is a firewall (and nothing else) because it has the newer pf firewall: http://www.openbsd.org/faq/pf/ which has more features than the older BSD ipfilter firewall has in Solaris. However, Solaris 10 has some very slight security advantages over OpenBSD on very large multi-user servers in large organizations (government, corporations, military, etc.) where you need fine grained security permissions and don't want to give all power to a single root user. Here is an example of a very powerful security feature in Solaris 10 that I don't think exists in OpenBSD: http://blogs.sun.com/gbrunett/entry/enforcing_a_two_man_rule Another powerful security feature that Solaris 10 has that OpenBSD doesn't have is trusted extensions: http://osug.org.ua/wp-content/uploads/2008/03/screenshot.png If you look at the link above you can see that the different windows and documents are classified at different levels of security and it's not possible to copy and paste from a more secret / classified window into a less secret / classified window. AFAIK, OpenBSD does not have this capability built in in a default install. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Bad news for running Oracle on Solaris?
Do any of you here think that this Oracle related article has any truth to it: http://kevinclosson.wordpress.com/2006/12/10/no-more-oracle-ports-to-solarisaixhp-ux-after-oracle11g/ or do you think it's just more anti-Solaris F.U.D. ? To me this article doesn't make any sense at all: the Application Binary Interface and D.D.I. for Linux changes all the time because Linus doesn't care about backward compatibility, so if you develop on Linux instead of Solaris, your backwards binary compatibility will break every time the Linux ABI changes just like all of my Linux desktop computers at home all break random things every time I upgrade them to the newest version of Fedora, Ubuntu, Debian, etc My personal experience of approximately 10 years of running Linux on the desktop is that it's about as stable as nitroglycerin when you update it. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Bad news for running Oracle on Solaris?
+-- | On 2010-01-05 22:20:35, Anon Y Mous wrote: | | or do you think it's just more anti-Solaris F.U.D. ? Published December 10, 2006 EOF -- bda cyberpunk is dead. long live cyberpunk. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Using OpenSolaris as a security gateway
Another powerful security feature that Solaris 10 has that OpenBSD doesn't have is trusted extensions: ttp://osug.org.ua/wp-content/uploads/2008/03/screensho t.png If you look at the link above you can see that the different windows and documents are classified at different levels of security and it's not possible to copy and paste from a more secret / classified window into a less secret / classified window. AFAIK, OpenBSD does not have this capability built in in a default install. Hello, do you know if MAC is also available in the OpenSolaris 2009.06? I.e. I assume this is mandatory access control implementation from trusted solaris edition, right? Thanks, Karel -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
