Re: [osol-discuss] SoftwareFreedomDay 2010 on Sep 18th
(2010/07/26 13:28), HeCSa wrote: On 07/26/10 12:35 AM, Masafumi Ohta wrote: Hi, Are you planning to do some for celebrating softwarefreedomday 2010? if any plans,please reply on this osol mailing lists. Hi, my friend! Yes, we do. Today AOSUG and CaFeLUG (Capital Federal GNU/Linux Users Group) had a meeting about SFD'2010. And I was there, of course. It will take place on Sep, 18th., at the National Technology University (UTN). We expect to receive more than 200 people (last year Argentina OpenSolaris Users Group sent the invite, and organized SFD'09, and we received almost 300!!!), and will give more than 10 tech talks, have a "tech doctor", and an install stand. Let's see how it goes! Best regards, Ohta-San! http://softwarefreedomday.org/ thanks, -masafumi Lead of Tokyo OpenSolaris User Group. Core Contributer for OpenSolaris. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org Thanks info my friends! Some of we japanese FOSS User groups are planning to hold the events for SFD 2010. but in Japan SFD is not familiar though there are much events all over the world,so I am planning to introduce SFD at OSS events here in Japan so that much of we would celebrate SFD with you FOSS guys all over the world :) -masafumi Lead of Tokyo OpenSolaris User Group Core Contributer for OpenSolaris. -- 。・。・゜☆・。・。★・゜・。・゜。・。・゜★・。・。☆・。 Masafumi Ohta Itouchu Techno-Solutions Corp. Enterprise Engineering Div. IT Integration Team Art Village Osaki Central Tower.,1-2-2,Osaki,Shinagawa-ku,Tokyo,141-8522 Japan tel +81-3-6417-8546 fax +81-3-5434-0057 mailto:masafumi.o...@ctc-g.co.jp OpenSolaris Core Contributer http://www.opensolaris.org/os/community/on/observers/ 。・。・゜☆・。・。★・゜・。・゜。・。・゜★・。・。☆・。 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SoftwareFreedomDay 2010 on Sep 18th
On 07/26/10 12:35 AM, Masafumi Ohta wrote: Hi, Are you planning to do some for celebrating softwarefreedomday 2010? if any plans,please reply on this osol mailing lists. Hi, my friend! Yes, we do. Today AOSUG and CaFeLUG (Capital Federal GNU/Linux Users Group) had a meeting about SFD'2010. And I was there, of course. It will take place on Sep, 18th., at the National Technology University (UTN). We expect to receive more than 200 people (last year Argentina OpenSolaris Users Group sent the invite, and organized SFD'09, and we received almost 300!!!), and will give more than 10 tech talks, have a "tech doctor", and an install stand. Let's see how it goes! Best regards, Ohta-San! http://softwarefreedomday.org/ thanks, -masafumi Lead of Tokyo OpenSolaris User Group. Core Contributer for OpenSolaris. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [xen-discuss] Xen EOF?
> Don't know about that. Dtrace is certainly useful to > detect bottlenecks in VM > setup and configuration. Now that there are rumours > that Bryan Cantrill has > left Oracle, the future development of dtrace is not > clear, anyway. This particular rumour is very much true: http://dtrace.org/blogs/bmc/2010/07/25/good-bye-sun/#comments Kind of dumbfounded by this :( -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Virtualization on solaris/opensolaris
(2010/07/26 11:40), Jorgen Lundman wrote: We've run XEN here on b134 very successfully, and it came with opensolaris (or at least, you can just go 'pkg install $module'. We ran b134 as the dom0, and we tested: osol_119 osol_134 Sol 10u8 centos_5.3 Windows 7 FreeBSD 7.2 Win2k3_srv ubuntu 9.10 as domU. The "production test" environment is all on XENs now. Cool.since two weeks ago ESXi 4.1 has released,I have been trying on OpenSolaris on it but won't finished installation stopping on the way of making BE process.workaround is importing OVF templates former made on ESXi 4.0.it runs well on my ESXi 4.1. VMware Go is,I guess,just improving as,web client for using PCs without "Windows".just runs well but works very slw access to my ESXi.now not useful for me.so will try Xen 4.0 or KVN on my PC. I have tried Xen as OracleVM,PVM is good solution,running much faster while compiling some than running on ESXi.but sometimes crashes on my PC,going back ESXi now tring on it. Thanks some infomations, -masafumi Lead of Tokyo OpenSolaris User Group Core Contributer for OpenSolaris. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] SoftwareFreedomDay 2010 on Sep 18th
Hi, Are you planning to do some for celebrating softwarefreedomday 2010? if any plans,please reply on this osol mailing lists. http://softwarefreedomday.org/ thanks, -masafumi Lead of Tokyo OpenSolaris User Group. Core Contributer for OpenSolaris. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Virtualization on solaris/opensolaris
> We've run XEN here on b134 very successfully, and it > came with opensolaris (or at least, you can just go > 'pkg install $module'. > > We ran b134 as the dom0, and we tested: > > osol_119 > osol_134 > Sol 10u8 > centos_5.3 > Windows 7 > FreeBSD 7.2 > Win2k3_srv > ubuntu 9.10 > > as domU. > > The "production test" environment is all on XENs now. I'm not very fond about xen virtualization because, if the hypervisor has bugs it might bring the entire stack down( host OS along with the guest) where as if virtualization was being done through something like virtualbox and if their were any any bugs. most likely it would only affect the guest OS and not the host OS. but i think virtualization itself is a can of problems because, the unit will be running mutiple kernels at the same time and i think that increases the risk of having many, many bugs where security might become an issue. Regards eam1 -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SchilliX-0.7.0 ready for testing
HeCSa wrote: > > > On 07/24/10 07:51 PM, Rob McMahon wrote: >> On 24/07/2010 23:27, Shawn Walker wrote: >>> >>> The version of pkg(5) that will be part of b144 should deliver >>> somewhere around a 20% or greater performance improvement in >>> transport performance when used with a properly configured web and/or >>> depot server. >>> >> Do you know how frustrating it is when people say "putback in b135", >> "fixed in b140", "the version in b144 is so much better" when we're >> all stuck at b134. Aagh. > > This is why I need to know if there is some tutorial, or even tty output > record about how to start from the source code tarfile, and end with a > repo such as Rich Lowe did. Rich Lowe published the steps he took in his README. http://genunix.org/dist/richlowe/README.txt -- -Alan Coopersmith-alan.coopersm...@oracle.com Oracle Solaris Platform Engineering: X Window System ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SchilliX-0.7.0 ready for testing
Stefan Parvu wrote: > How IPS handles the process of applying patched ? AFAIK OSOL does not really > have the concept > of a patch, right ? Or ? Right - IPS simply has new versions of packages, in which the packaging system determines which files are different from what you've already installed and just downloads those, unlike SVR4 where you download a patch containing every change since the base package release, even if you're only upgrading from patch -94 to -95 and already have most of the changed files downloaded & installed, and the patch builder is responsible for determining which files were changed by a putback and need to be included in a patch (mistakes have happened there sometimes). -- -Alan Coopersmith-alan.coopersm...@oracle.com Oracle Solaris Platform Engineering: X Window System ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Virtualization on solaris/opensolaris
We've run XEN here on b134 very successfully, and it came with opensolaris (or at least, you can just go 'pkg install $module'. We ran b134 as the dom0, and we tested: osol_119 osol_134 Sol 10u8 centos_5.3 Windows 7 FreeBSD 7.2 Win2k3_srv ubuntu 9.10 as domU. The "production test" environment is all on XENs now. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Virtualization on solaris/opensolaris
Hi, Edward! On 07/25/10 11:22 PM, Edward Ned Harvey wrote: Suppose you want to use solaris/opensolaris as a VM host, and Windows Server as a guest. What would be the preferred hypervisor to use? Sun Virtualbox? It is desired to start the guest when the host boots up. And vice-versa for shutdown. I had a very good experience virtualizing in this way, and creating simple startup/shutdown scripts invoking VBoxManage startvm V_MACHINE_NAME --type headless, or --type vrdp, for example, for the boot. I see that sol10/osol are not supported host OSes for any vmware product. And I'm rather displeased with some of the limitations of ESXi. (In other words, I don't want to virtualize *both* the solaris and windows server machines inside an ESXi hypervisor.) Welcome home! I presume some incantation of xen works. But I don't see it preinstalled ... and honestly I'm not in love with xen based on other experiences ... Anyway, looking for suggestions. Thanks. Best regards, HeCSa. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] opensolaris vs schillix etc
I am wondering ... SchilliX is being built, using the same procedures and source as opensolaris, right? What differences are there / will there be, between opensolaris and schillix? I am speaking technical differences. Obviously there will also be cultural differences, and that's not the question for now. Is it intended to be a separate OS, which maybe branches off from opensolaris? Has its own source development which is separate from osol? Or is it intended to just fill the void where oracle isn't building osol ISO's anymore? So schillix becomes the "developer build" of opensolaris? I know in the case of Centos vs RHEL, they build redhat sources using redhat scripts, but there is a little bit of redhat proprietary code that isn't open source (and can't be built into centos) ... so there are a few situations where centos needs to substitute some open-source alternative to something that's normally included in RHEL. Also there are some trademarked/copyrighted materials including the redhat logo etc, which are not permissible to redistribute. So ... As close as centos might be to "just like rhel" there are still some technical differences. Those differences form pros & cons both, in different situations. Thanks... ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Virtualization on solaris/opensolaris
Suppose you want to use solaris/opensolaris as a VM host, and Windows Server as a guest. What would be the preferred hypervisor to use? Sun Virtualbox? It is desired to start the guest when the host boots up. And vice-versa for shutdown. I see that sol10/osol are not supported host OSes for any vmware product. And I'm rather displeased with some of the limitations of ESXi. (In other words, I don't want to virtualize *both* the solaris and windows server machines inside an ESXi hypervisor.) I presume some incantation of xen works. But I don't see it preinstalled ... and honestly I'm not in love with xen based on other experiences ... Anyway, looking for suggestions. Thanks. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] I hope we also get a welcome mat at openworld.
> > > On 07/20/10 02:18 PM, Edward Martinez wrote: > > Well i guess the MySQL guys fears are now put to > rest. > > I do hope Opensolaris community also gets a welcome > mat at OpenWorld. crossing my fingers! > > > > extract: > > Oracle is rolling out the welcome mat for the MySQL > community as part of Oracle OpenWorld. > > > > > http://www.oracle.com/us/corporate/features/mysql-1315 > 55.html > > > > Well...I've been using MariaDB for some time now, and > works incredibly > good for me (us). You can download pre-built binaries > for OpenSolaris > from here: http://askmonty.org/wiki/MariaDB:Download > Will MariDB get a welcome mat too :D ? > Best regards, > > HeCSa. > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org > this is nice, thanks. I was not aware Monty forked MySQL. I gotta tried this out on OpenSolaris and see if it compiles in DragonflyBSD -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [xen-discuss] Xen EOF?
Hi Matthias! > Looking at the fact, that OVM is free, and has a way better graphical > management system, and also comes with already predefined "Images", I don't > see that many problems. Well, I don't care much about GUI management systems, I care about scripts. > Who would really be using ZFS in the Dom0, if you build bigger environments? I am not sure if you mention this intentionally, but this is exactly the point: For small and mid-sized installations, it is very convenient to have everything "inside one box". You do everything you can with zones, and the rest inside VMs. When you set up your hardware in a proper (redundant) way, you can have the power of Solaris in the global and non-global zones, and run other OSes in VMs. > Dtrace in Dom0 would be useful for the device-drivers only. The Dtrace > interface to Xen was based on an asynchronous message bus, with no guarantee > of getting all messages, not even in time. Don't know about that. Dtrace is certainly useful to detect bottlenecks in VM setup and configuration. Now that there are rumours that Bryan Cantrill has left Oracle, the future development of dtrace is not clear, anyway. > Crossbow might be the only > advantage, that's not deployable in an OVM-like environment. One of the advantages. :-) > But given the > advantages of predefined image-sets for OVM Hmmm... what keeps Oracle from providing images for Xen? > and the already available > graphical interface for managing OVM, What about Sun xVM Ops Center or whatever it was called? > I really like the engineers working on > making Solaris a better DomU, than working on porting Xen 4.0 to Solaris. I want both; I want choice. I want a stable Dom0 OS. > You > also no longer buy your PC based on whether it runs an AMI BIOS or an AWARD > BIOS. That's something, that's simply there... ;-) Now you are comparing Apples... erm... Bananas and Oranges. Sorry, you don't really convince me that it was a technologically sound decision. Economically and business-oriented is another story... Regards -- Volker -- Volker A. Brandt Consulting and Support for Sun Solaris Brandt & Brandt Computer GmbH WWW: http://www.bb-c.de/ Am Wiesenpfad 6, 53340 Meckenheim Email: v...@bb-c.de Handelsregister: Amtsgericht Bonn, HRB 10513 Schuhgröße: 45 Geschäftsführer: Rainer J. H. Brandt und Volker A. Brandt ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SchilliX-0.7.0 ready for testing
On 07/25/10 06:27 PM, Shawn Walker wrote:
On 07/24/10 11:55 PM, HeCSa wrote:
...
On 07/24/10 08:23 PM, Shawn Walker wrote:
...
The source is there, and you can build it you know ;)
Alternatively, you could use the bits someone made available on
genunix.org for b142:
http://genunix.org/dist/richlowe/README.txt
http://genunix.org/dist/richlowe/
Hi, Shawn!
Do you know about any tutorial / white paper / something explaining how
to start from the sources, and create a repo such as Rich Lowe did with
snv_142?
I wrote something in English, and posted, and something in Spanish for
our community site about how to upgrade from snv_134 to onnv_142, but
don't know how to start from sources and end with such a repo.
I understand Rich did a great job with this, and want to reproduce it
locally.
Any help will be appreciated.
The last time I built ON I used the developer's guide and some
instructions provided by the ON community:
http://hub.opensolaris.org/bin/view/Community+Group+on/devref_toc
http://hub.opensolaris.org/bin/view/Project+indiana/building_on
I suspect the process will roughly be:
* install OpenSolaris b134a
* setup an ON repository containing b142 using the bits rich lowe
provides at genunix.org: http://genunix.org/dist/richlowe/
* upgrade the system to those bits
* install ON build dependencies (studio 12 u1 bits from
opensolaris.org download page, developer/opensolaris/osnet,
developer/opensolaris/pkg5, etc.)
* follow instructions on pages linked above to build ON and in
Rich's README.txt.
This paragraph sound like music for me:
"...
4.4.3 Packages
The -p option to nightly will package the files that were installed
into your proto area. If your workspace contains the directory
usr/src/pkgdefs, this will result in SVr4 packages. If instead it
contains usr/src/pkg, it will produce an IPS package repository. In
either case, this is done automatically by the main makefile's all and
pkg_all targets (see usr/src/Makefile) as part of a successful build.
SVr4 packages or IPS package repositories are placed in
${CODEMGR_WS}/packages. See nightly(1) and section 4.2 for more
information on automating package construction as part of your automatic
build.
..."
Thanks a lot, Shawn!
Best regards,
HeCSa.
Cheers,
-Shawn
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SchilliX-0.7.0 ready for testing
On 07/24/10 03:51 PM, Rob McMahon wrote: On 24/07/2010 23:27, Shawn Walker wrote: The version of pkg(5) that will be part of b144 should deliver somewhere around a 20% or greater performance improvement in transport performance when used with a properly configured web and/or depot server. Do you know how frustrating it is when people say "putback in b135", "fixed in b140", "the version in b144 is so much better" when we're all stuck at b134. Aagh. The general community is capable of building newer bits; this is an excellent opportunity for someone to do so. -Shawn ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SchilliX-0.7.0 ready for testing
On 07/24/10 11:55 PM, HeCSa wrote: ... On 07/24/10 08:23 PM, Shawn Walker wrote: ... The source is there, and you can build it you know ;) Alternatively, you could use the bits someone made available on genunix.org for b142: http://genunix.org/dist/richlowe/README.txt http://genunix.org/dist/richlowe/ Hi, Shawn! Do you know about any tutorial / white paper / something explaining how to start from the sources, and create a repo such as Rich Lowe did with snv_142? I wrote something in English, and posted, and something in Spanish for our community site about how to upgrade from snv_134 to onnv_142, but don't know how to start from sources and end with such a repo. I understand Rich did a great job with this, and want to reproduce it locally. Any help will be appreciated. The last time I built ON I used the developer's guide and some instructions provided by the ON community: http://hub.opensolaris.org/bin/view/Community+Group+on/devref_toc http://hub.opensolaris.org/bin/view/Project+indiana/building_on I suspect the process will roughly be: * install OpenSolaris b134a * setup an ON repository containing b142 using the bits rich lowe provides at genunix.org: http://genunix.org/dist/richlowe/ * upgrade the system to those bits * install ON build dependencies (studio 12 u1 bits from opensolaris.org download page, developer/opensolaris/osnet, developer/opensolaris/pkg5, etc.) * follow instructions on pages linked above to build ON and in Rich's README.txt. Cheers, -Shawn ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Problem with snv_134 networking in zones
> And you determined this how? Can you show any dtrace output, or similar? Determined by stopping one zone and testing connectivity from global+remaining zone. Starting zone again and repeat. > I think you might be confusing simpler with familiar. I tnking your'e making an assumption without having enough facts. If I were to go familiar, I'd install Solaris, HPUX, AIX or Linux. Not FreeBSD. Simpler simply refers to "where I don't have to jump through umpteen hoops wasting time on something that should work flawlessly on first try". (Open)Solaris has never held the pride of third-party hardware support. Ever. That it's getting better is nice. I just happen to have better things to do with my time than chase ghosts that weren't there in the first place. FreeBSD does however offer ZFS, which is what I crave most. Albeit not the latest fanciest dedup version, but still fairly recent. If it works, good. Less time wasted. > Best of luck. Thanks, but given my luck lately, I think that's best left out of the equation :) -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] I hope we also get a welcome mat at openworld.
On 07/20/10 02:18 PM, Edward Martinez wrote: Well i guess the MySQL guys fears are now put to rest. I do hope Opensolaris community also gets a welcome mat at OpenWorld. crossing my fingers! extract: Oracle is rolling out the welcome mat for the MySQL community as part of Oracle OpenWorld. http://www.oracle.com/us/corporate/features/mysql-131555.html Well...I've been using MariaDB for some time now, and works incredibly good for me (us). You can download pre-built binaries for OpenSolaris from here: http://askmonty.org/wiki/MariaDB:Download Will MariDB get a welcome mat too :D ? Best regards, HeCSa. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [xen-discuss] Xen EOF?
Those are good points. I'm not opposed to going with Oracle VM but keeping Xvm in Solaris would have allowed so many more consolidation opportunities. We were looking to replace a pair of clustered V880s with 12 shared D2 arrays stuffed with 72GB disks and other various servers (clustered for NBU master, DNS/SMTP servers, a couple windows boxes, and a pair of VMware servers on IBM hardware) down into a pair of clustered servers (thinking X4470) with dual attached SAS arrays filled with 2TB disks (moving from ~8TB to ~16TB with capactiy to quickly go to ~32TB). The Dom0s can serve the data and be netbackup media servers and the rest could have been virtualized into DomU's with NBU client software. We have a mock up in a test lab and it works great minus the DomU migration between systems since the cluster agent isn't there. I would be concerned with the I/O of the backup except none of the systems are really taxed to begin with and the capabilities of this system are FAR above what we have today. I would consider going with OracleVM but I'm not sure I'm going to get money to add seperate HA file/NBU media servers into the picture. I am open to creative sugguestions. > Looking at the fact, that OVM is free, and has a way > better graphical > management system, and also comes with already > predefined "Images", I don't > see that many problems. > > Who would really be using ZFS in the Dom0, if you > build bigger environments? > You would place the binaries/images on some network > device, so no disadvantage > here. Dtrace in Dom0 would be useful for the > device-drivers only. The Dtrace > interface to Xen was based on an asynchronous message > bus, with no guarantee > of getting all messages, not even in time. Crossbow > might be the only > advantage, that's not deployable in an OVM-like > environment. But given the > advantages of predefined image-sets for OVM and the > already available > graphical interface for managing OVM, I really like > the engineers working on > making Solaris a better DomU, than working on porting > Xen 4.0 to Solaris. You > also no longer buy your PC based on whether it runs > an AMI BIOS or an AWARD > BIOS. That's something, that's simply there... ;-) > > Again: This is all my private thinking! > >Matthias > ustin Lee Ewing) wrote: > > Wow, that is really disappointing... especially > with all the features of ZFS, the intergration of > Crossbow, etc. One would think you would deprecate > OracleVM in favor of the combined Solaris/Xvm and try > to consolidate. I was definiately looking forward to > getting rid of VMware... but no point in that if I'm > not moving towards a single OS/command set. > -- > Matthias Pfützner | Tel.: +49 700 PFUETZNER | By > 2000 Apple will be > Lichtenbergstr.73 | mailto:matth...@pfuetzner.de | > acquired by Wal-Mart. > D-64289 Darmstadt | AIM: pfuetz, ICQ: 300967487 | > Germany | http://www.pfuetzner.de/matthias/ | > Ted Nelson (Chief Ed. Byte) > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org > -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Community distro
Hi, Ken! This *really* help us! Thanks a lot, I'll start contacting the referred POC's. Best regards, HeCSa. On 07/25/10 01:44 PM, Ken Mays wrote: To: Hernán Saltiel& Community User Groups The community needs resources to maintain the components updated by the various teams. For the upcoming Hackathon and user meetings, users interested in building a 'community distro' or providing support for it should know where to look for help. The offloads can be through the current major distro providers: SchilliX, Belenix, Nexenta, Milax, EON, Korona, and Jaris. Users can use those distros to provide current solutions or provide feedback/bug reporting on what they would like to see improved. Also, users can work with those distros in doing the work. IPS repositories are needed in geographic locations to support their local user groups. The /dev repository has about 1730 packages that can be compressed to a DVDs for global distribution or can use the older OSOL 2009.06 distro for initial setup. The goal here is to support the pkg(5) team in using IPS as a package management solution and provided 'basic' docs on how to use it and keep it updated. I'll mention Package Factory and SourceJuicer. These were concepts to provide users with a way to have packages compiled through an "automated" build engine (SJ) through a front-end web interface (PF/SJ). You could provide an URL to your FOSS packages with some basic package definition and purpose through Package Factory, then Package Factory would send this information off to automate a build. The community could pick up on this concept to provide a system of this nature. Users can ensure the Wikipedia info located here is accurate and up-to-date: http://en.wikipedia.org/wiki/OpenSolaris The 'community' people that could be contacted for expertise in OpenSolaris distro creation and repository support: Ref: https://www.opensolaris.org/jive/thread.jspa?threadID=122454&tstart=0 Getting ON sources through web access (Genunix/Mercurial)? see Cyril Plisko Jaris, led by Kotaro-san, a Japanese-centric desktop distro. SchilliX, led by Joerg Shilling, a server-centric development distro. Belenix, led by Moinak Ghosh, a general-purpose desktop and graphics distro. Jeos, led by Rudolf Kutina, on VM builds LiveUSB creation, led by Hiroshi Chonan, on LiveUSB builds Korona, led by Pavel Heimlich, a KDE-centric distro. EON, led by Andre Lue, NAS/ZFS storage solution marTux, led by Martin Bochnig, first community distribution for SPARC workstations MilaX, led by Alexander Eremin, mini recovery CD/USB distro Nexenta/NexentaStor, led by Anil Gulecha and Garrett d' Amore, on OpenSolaris/Ubuntu-based (Debian) community distro and advanced storage solutions. StormOS, led by Andrew Stormont, a lightweight desktop OS based on Nexenta and Xfce. OSUNIX project, led by C. Bergstrom (codestr0m) and Max Bruning, distro and expertise in the best of OpenSolaris technologies Device drivers, led by people like Jürgen Keil and Masayuki Murayama, on their expertise on various device drivers. Blastwave/OpenCSW for advanced Solaris-based package management and FOSS porting support. So you have a lot of community people that can help as well as many user groups. ~ Ken Mays Atlanta, Georgia (USA) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SchilliX-0.7.0 ready for testing
On 07/24/10 07:51 PM, Rob McMahon wrote: On 24/07/2010 23:27, Shawn Walker wrote: The version of pkg(5) that will be part of b144 should deliver somewhere around a 20% or greater performance improvement in transport performance when used with a properly configured web and/or depot server. Do you know how frustrating it is when people say "putback in b135", "fixed in b140", "the version in b144 is so much better" when we're all stuck at b134. Aagh. This is why I need to know if there is some tutorial, or even tty output record about how to start from the source code tarfile, and end with a repo such as Rich Lowe did. I own a public IP, and some domains. AOSUG's own site is hosted in one of my machines, then I can make publicly available a repo for this. But I really don't know how to do it. Again, any help will be very appreciated. Thanks, and best regards, HeCSa. Rob ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Community distro
To: Hernán Saltiel & Community User Groups The community needs resources to maintain the components updated by the various teams. For the upcoming Hackathon and user meetings, users interested in building a 'community distro' or providing support for it should know where to look for help. The offloads can be through the current major distro providers: SchilliX, Belenix, Nexenta, Milax, EON, Korona, and Jaris. Users can use those distros to provide current solutions or provide feedback/bug reporting on what they would like to see improved. Also, users can work with those distros in doing the work. IPS repositories are needed in geographic locations to support their local user groups. The /dev repository has about 1730 packages that can be compressed to a DVDs for global distribution or can use the older OSOL 2009.06 distro for initial setup. The goal here is to support the pkg(5) team in using IPS as a package management solution and provided 'basic' docs on how to use it and keep it updated. I'll mention Package Factory and SourceJuicer. These were concepts to provide users with a way to have packages compiled through an "automated" build engine (SJ) through a front-end web interface (PF/SJ). You could provide an URL to your FOSS packages with some basic package definition and purpose through Package Factory, then Package Factory would send this information off to automate a build. The community could pick up on this concept to provide a system of this nature. Users can ensure the Wikipedia info located here is accurate and up-to-date: http://en.wikipedia.org/wiki/OpenSolaris The 'community' people that could be contacted for expertise in OpenSolaris distro creation and repository support: Ref: https://www.opensolaris.org/jive/thread.jspa?threadID=122454&tstart=0 Getting ON sources through web access (Genunix/Mercurial)? see Cyril Plisko Jaris, led by Kotaro-san, a Japanese-centric desktop distro. SchilliX, led by Joerg Shilling, a server-centric development distro. Belenix, led by Moinak Ghosh, a general-purpose desktop and graphics distro. Jeos, led by Rudolf Kutina, on VM builds LiveUSB creation, led by Hiroshi Chonan, on LiveUSB builds Korona, led by Pavel Heimlich, a KDE-centric distro. EON, led by Andre Lue, NAS/ZFS storage solution marTux, led by Martin Bochnig, first community distribution for SPARC workstations MilaX, led by Alexander Eremin, mini recovery CD/USB distro Nexenta/NexentaStor, led by Anil Gulecha and Garrett d' Amore, on OpenSolaris/Ubuntu-based (Debian) community distro and advanced storage solutions. StormOS, led by Andrew Stormont, a lightweight desktop OS based on Nexenta and Xfce. OSUNIX project, led by C. Bergstrom (codestr0m) and Max Bruning, distro and expertise in the best of OpenSolaris technologies Device drivers, led by people like Jürgen Keil and Masayuki Murayama, on their expertise on various device drivers. Blastwave/OpenCSW for advanced Solaris-based package management and FOSS porting support. So you have a lot of community people that can help as well as many user groups. ~ Ken Mays Atlanta, Georgia (USA) -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] VLC building help
Thanks everyone... I opted to use the SJT packages and got things working. Since I'm only going to use this for transcoding I wasn't too concerned that it isn't the latest version. Mixing g++ and Sun Studio compiled library dependencies was very problematic in getting things working. I ended up rebuilding g++ dependencies, even if they were provided in an IPS package. I have one of my MPEG-2 home movies streaming via mediatomb. I also successfully streamed an MPEG-4 video so I can concentrate on moving all my content to the OpenSolaris box instead of banging my head on this issue. Yay! Gary -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SchilliX-0.7.0 ready for testing
On 24/07/2010 23:27, Shawn Walker wrote: The version of pkg(5) that will be part of b144 should deliver somewhere around a 20% or greater performance improvement in transport performance when used with a properly configured web and/or depot server. Do you know how frustrating it is when people say "putback in b135", "fixed in b140", "the version in b144 is so much better" when we're all stuck at b134. Aagh. Rob ___ 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
> 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] SchilliX-0.7.0 ready for testing
> today, I put SchilliX-0.7.0 out. > > > ftp://ftp.berlios.de/pub/schillix/ > ftp://ftp.berlios.de/pub/schillix/SchilliX-0.7.0.iso.bz2 Joerg, I'm going to recommend xz instead of (or in addition to) bzip2. It's much faster and compresses better. My experience is 2x faster and 2x better compression. Oh - Specifically if you use compression level 1. xz -1 SchilliX-0.7.0.iso ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SchilliX-0.7.0 ready for testing
Stefan Parvu wrote: > 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. A main problem with using more than a single packet management system is the fact that they usually use different data bases and do not know about packages installed by the other system. Another one is that you thus cannot have cross packaging dependencies. Your mail reminds me on the fact that there should be discussions between different distros to get a compatible minimum base. It is now nearly two weeks after the OGB teleconference where an Oracle manager confirmed to attend. He did not attend and he did nt even send an excuse. I am not sure about Oracle's intention for the future, but it may be needed to have the Solaris supply done by comunity distros and in this case, it is important to have a common compatibility base. > IPS should have fixed all these things what you have listed. > To me, as a SysAdmin important are the following: Let me strip that down... If IPS nicely interacts with other packaging systems I see not reason why it is not used by one or more distros. Whether it meets the needs of commercial users is another issue. If we like to keep Solaris viable, we need to take care of commercial users also. 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] 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] Community distro
On 07/17/10 01:38 PM, Alasdair Lumsden wrote: On 17 Jul 2010, at 16:35, Paul Gress wrote: On 07/17/10 09:07 AM, Ken Mays wrote: Ken, what you say make a lot of sense. But when I look at those community distributions I don't see what I'm exactly looking for. So I guess I going to try to add to this thread what I'd like to see in a community distro. This is just my start, maybe others can add to it, or disagree with what I said, after all, this is a discussion. Paul +1 A community distribution to take the place of OpenSolaris Indiana is exactly what's needed. I'm hoping to collect together a list of people who are interested in volunteering/helping out with just such an effort - if you could drop an email to me - alasdairrr at gmail, with details of how you're interested in helping out, then I'll jot down your details and get in touch. Cheers, Alasdair Hi, Alasdair! I can help too. Count on me, and the Argentina OpenSolaris Users Group. Best regards, HeCSa. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SchilliX-0.7.0 ready for testing
On Sat, Jul 24, 2010 at 11:50 PM, Stefan Parvu wrote: > IPS tries to be a network pkg management system. It needs to be simple > ... list of good ideas ... These are all things that could easily be addressed, and aren't per-se reasons to abandon IPS. If it was important, these things could be done. With the new on-disk format, I'd assume it would be easier to maintain a mirror using the existing mirroring tools... As Machiavelli said, change is opposed by those with a vested interest in the status quo... > What comparative analysis have you done Last time I looked, probably 5 years ago, and if I recall correctly, the basic work flow in the SVr4 package tools was something like start pkgadd, pkgrm, pkginfo, ... process read /var/sadm/install/contents into memory install/remove/whatever a package read /var/sadm/install/contents and merge/modify the lines into a new /var/sadm/install/contents file if the world was modified exit process for every single package installed. The thrashing over the /var/sadm/install/contents file was more than huge, and is one reason why patch management in zones sucked rocks so badly (tens of hours to days to upgrade a system with many zones...). There were some simple comp-sci style modifications that could/did speed things up by orders of magnitude, but they required replacing the /var/sadm/install/contents text file with some sort of structured object (database, btree, whatever) that was incompatible with way too many things that had come to depend on the project private contents file. There were proposals to cache the file in memory (ala nscd), to make it a special kernel driver (ala /etc/mnttab) and others, none of which (IIRC) made it past the proposal/prototype stage. -John ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
