Re: [OpenIndiana-discuss] Sun ssh no work with recent OpenSSH
You can't because the crypto's not there, and if you're not root you can't get around the changes to defaults. There's a series of changes to sunssh pending against upstream as issue 5414. On 26 December 2014 at 23:02, Harry Putnam wrote: > Running b 151_a9 > > How can I tweak: > pkg:/network/ssh@0.5.11-0.151.1.9 > > So that it will work with newly released versions of OpenSSH? > > Currently I see this error: > ssh gv (`gv' is a gentoo linux box running openssh-6.7_p1-r3) > > , > | no common kex alg: client > 'diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1', server ' > curve25519-sha...@libssh.org > ,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1' > ` > They can find no common Kex algorithm. > > From what I understand, newer versions of OpenSSH have changed which > algorithms it allows, and has pulled some of older less secure algo > out of service. > > So apparently `Sun ssh' cannot find a an agreeable algorithm to > cooperate with OpenSSH. > > I could not get enough of an idea from `man ssh' to see a way to get > past this. > > Is it possible to add algorithms to our ssh? Assume for a moment that > I don't have root on gentoo box. How could I make our ssh work with > it? > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss > ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Newer OpenSSH causes probs for OI ssh
There's been substantial change in crypto support in OpenSSH, which deprecated a bunch of old crypto from default settings in their latest release. I've got changes parked from a while ago to import this into illumos, which I'll try to get out for review during the holidays. I'll file an issue to track it. On 27 November 2014 at 04:45, Alexander Pyhalov wrote: > Harry Putnam писал 27.11.2014 04:13: > >> Alan Coopersmith writes: >> >> On 11/26/14 03:28 PM, Harry Putnam wrote: >>> I did not discover what ssh binary we are using... (is it a Solaris ssh?) by using pkg tools, other than the pkg name and version: pkg://openindiana.org/network/ssh@0.5.11,5.11-0.151.1.9 >>> >>> Either ssh -V or ssh -v should tell you it's running Sun_SSH, which is a >>> fork of OpenSSH. OI should be using the version from the illumos gate. >>> >> >> OK, thanks >> >> ssh -V >> Sun_SSH_1.5, SSH protocols 1.5/2.0, OpenSSL 0x0090819f >> >> > Hello. > First of all, check that problem exists in fresh illumos-gate (compile it > manually or use Hipster). > If the issue still exists with new SSH version, please, file a bug on > bugs.illumos.org. > > --- > System Administrator of Southern Federal University Computer Center > > > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss > ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Future of OI (was Bash Bug issue)
On 9 October 2014 20:41, openindi...@out-side.nl wrote: > From my limited tunnelview: > > Nexenta: closed source, no real root, no zones. IF you want storage with > support this is the best option. > Please define closed source while accounting for this fundamental fact: https://github.com/nexenta/illumos-nexenta ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Bash bug issue
No new CVE. This looks to be a proper fix for CVE-2014-6278, where the assessment is that the parser bugs that make this exploitable were already addressed either by the Red Hat patches or upstream patch 027. That's what I gather between these sources: https://lists.gnu.org/archive/html/bug-bash/2014-10/msg00032.html http://lcamtuf.blogspot.co.uk/2014/09/bash-bug-apply-unofficial-patch-now.html http://lcamtuf.blogspot.co.uk/2014/09/quick-notes-about-bash-bug-its-impact.html Note that patch 030 for bash 4.3 is attributed to lcamtuf. I've not found any security responders who shipped previously available fixes telling people that they need to ship these further changes as an urgent response or even that they have to have them. Red Hat explicitly references lcamtuf's blog post as independent confirmation of their analysis and fixes. Cheers, Bayard On 7 October 2014 04:19, Richard L. Hamilton wrote: > Which CVE is that, or is it something else? > > On Oct 6, 2014, at 9:35 PM, Bob Friesenhahn > wrote: > > > The gift keeps on giving. There is yet another related security patch > for bash. Here is the one for bash 4.3: > > > > http://lists.gnu.org/archive/html/bug-bash/2014-10/msg00040.html > > > > Bob > > -- > > Bob Friesenhahn > > bfrie...@simple.dallas.tx.us, > http://www.simplesystems.org/users/bfriesen/ > > GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ > > > > ___ > > openindiana-discuss mailing list > > openindiana-discuss@openindiana.org > > http://openindiana.org/mailman/listinfo/openindiana-discuss > > > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss > ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Bash bug issue
These aren't new aspects of the bug. The fact is that default operation of systems using bash as the shell for interpolation with system or for scripts interpreted by bash allows remote code execution by taking strings from untrusted sources (e.g. USER_AGENT in web servers) and passing them through the environment, which allows remote code execution. What you're reporting here is instances of the resulting problem in products matching this description, not fundamental changes to the understanding of the bug. What's been difficult is that Red Hat's security response team and bash upstream initially differed on the scope of the issue and thus patching, as Red Hat believed there were broader problems and that upstream patches were therefore too limited in scope. Red Hat was subsequently shown to be correct. The confusion is that there are a number of CVEs out there, and the patches went out in batches. There are quite a variety of tests proposed for the fully documented CVEs, and some of the CVEs remain embargoed, with Red Hat simply advising that people take patches which bash upstream subsequently accepted. On 6 October 2014 18:58, The Outsider wrote: > Search q-nap & shellshock and you see how deep this goes... > > > On 6 oktober 2014 19:28:00 David Brodbeck wrote: > > On Thu, Oct 2, 2014 at 8:12 AM, Alan Coopersmith < >> alan.coopersm...@oracle.com> wrote: >> >> > On 10/ 2/14 07:00 AM, Brandon Hume wrote: >> > >> >> On many (most? all?) Linuxes, /bin/sh *is* /bin/bash. >> >> >> > >> > Many, but not all - the Debian family and some others use a lighter >> weight, >> > POSIX compatible shell instead, dash, the Debian Almquist Shell; and >> many >> > embedded distros use BusyBox instead. >> > >> > https://en.wikipedia.org/wiki/Almquist_shell >> > http://lwn.net/Articles/343924/ >> >> >> >> A big driver of this was faster boot, since boot scripts run on /bin/sh. >> On some systems the startup time for all those bash processes was a >> considerable portion of the total boot time. >> >> Note: It's not enough to make sure no CGI scripts are being run with >> /bin/bash. You also need to make sure no bash processes are being >> launched >> by other scripts, since many scripting languages launch a shell to run >> external commands. Unless the environment is explicitly cleared these are >> likely to inherit the environment of the calling process, with all the >> nasties in it. >> >> -- >> D. Brodbeck >> System Administrator, Linguistics >> University of Washington >> GPG key fingerprint: 0DB7 4B50 8910 DBC5 B510 79C4 3970 2BC3 2078 D875 >> ___ >> openindiana-discuss mailing list >> openindiana-discuss@openindiana.org >> http://openindiana.org/mailman/listinfo/openindiana-discuss >> > > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss > ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [oi-dev] INTEL, IA32, i80686, AMD64 *is* *well* *supported* by OpenSXCE: Some run it on theit Netbook! - OR: The ability to read a text and absorb information
The noise-to-signal ratio on these posts to world+dog is deeply inconsiderate. Please set up a distro-specific list and invite those who are interested. On 8 Jun 2013, at 23:51, G B wrote: I downloaded and went to install OpenSXCE and chose not to proceed when I was prompted with the language. Being from the United States of America I selected English, but there was no option for US, but there was Canada, New Zealand, Britain, Australia, and maybe another I'm missing. If this was an oversight on your behalf, then my apologies, but if it was intentional because of your dislike of the USA for some personal reason, then I'm not going to bother with your operating system. I served in the US Air Force, my uncle was a navigator on a B-52 during Vietnam, my mother's husband was in the US Air Force in Vietnam, my grandfather was in the US Army in the Pacific during WWII, another uncle served 30 years in the US State Dept. A good friend of mine served in the US Navy in Vietnam. You see, my blood doesn't bleed red, it bleeds Red, White, & Blue. Your largest user base would likely be the USA, but by neglecting to add the country to the language during installation it seems you are making a statement, and so am I. I refuse to use it. If you add the USA then I may look at it, but won't go out of my way. As I said before, if this was just an oversight then you have my apologies. Otherwise, good luck with your endeavor. -- *From:* Martin Bochnig *To:* Discussion list for OpenIndiana ; OpenIndiana Developer mailing list ; develo...@lists.illumos.org; disc...@lists.illumos.org; Martin Bochnig < mar...@martux.org> *Sent:* Saturday, June 8, 2013 11:26 AM *Subject:* [oi-dev] INTEL, IA32, i80686, AMD64 *is* *well* *supported* by OpenSXCE: Some run it on theit Netbook! - OR: The ability to read a text and absorb information Unfortunately I was forced to re-join and then re-unsubscribe to finally debunk some neverdying MYTHS. INTEL, IA32, i80686, AMD64 *is* *well* *supported* by OpenSXCE: Some run it on theit Netbook! - OR: The ability to read a text and absorb information I followed the discussion from the archives at http://openindiana.org/pipermail/openindiana-discuss/2013-June/date.htmland I'm shocked about all the nonsense that people can claim uncorrected, about what OpenSXCE is all about. I have always re-iterated all these technical aspects over and over again, when I was still on the Illumos and OI lists. To me it looks as if few ever read even the subject line. I also wrote all this to twitter.com/martinbochnig, twitter.com/opensxce, facebook.com/opensxce, facebook.com/martinbochnig, OpenSXCE's blog http://opensxce.blogspot.de/ as well as to contributors in probably hundreds of private messages and skype calls, plus google chats. It is a real mystery, why such NONSENSE can be claimed days-long without being corrected by or understood by the majority (BIG THANKS TO THE GOOD SOULS, who tried it) : OpenSXCE is SPARC-only: WRONG OpenSXCE is not based on Illumos: WRONG OpenSXCE will in the future not (indirektly) be based on Illumos modified OS/Net: WRONG OpenSXCE is Desktop-only: WRONG OpenSXCE is instable crap: WRONG OpenSXCE has "no users": WRONG Igor's DilOS.org OS/Net doesn't update itself to incorporate always the most recent stuff from Illumos (except where he has implemented things better, as you can read on his site or my blog) : WRONG MartinBochnig never works together with others: WRONG MartinBochnig never writes technical details to these technical lists: WRONG See my the OpenSXCE Blog, for example: OH “DilOS brings in the waffle cones” - Ken Mays / PLUS: *Hypocrisy* http://opensxce.blogspot.de/2013/06/oh-dilos-brings-in-waffle-cones-ken.html DilOS-OS/Net: The more I learn from and about Igor, the more I have to wonder why nobody ever put attention to him! But: He avoids fights. He rather writes code, code, code http://opensxce.blogspot.de/2013/06/dilos-osnet-more-i-learn-from-and-about.html Will you ever notice, that x86/x64 is also supported? what OpenSXCE actually is about: IA32, AMD64, sun4u, sun4v. You and everybody could read this from the beginning on (in bold letters: *COULD*). [OpenIndiana-discuss] A potential new Illumos reference distro candidate: IA32, AMD64, sun4u, sun4v http://openindiana.org/pipermail/openindiana-discuss/2012-December/010922.html I do not bitch around because "nobody uses my distro", because - believe it or not: That's not the case. I simply think, that if somebody talks about me or my work, he should at least have a clue, what he is talking about. And YES: I guess I do have this humble right, as anybody has and should have. If you (most at OI and Illumos) never read what I write, maybe it is easier to watch my x86 screenshots: http://www.flickr.com/photos/96825400@N05/sets/72157633874850547/ To avoid ambiguity I should add: Although these pkgutil'ified SVR4 pkgs can sit on any filesystem anf can be installed
Re: [OpenIndiana-discuss] SOLVED - pkg/server behind reverse proxy needs AllowEncodedSlashes On
On Wed, Apr 11, 2012 at 11:43 AM, Gabriele Bulfon wrote: > I finally found the reason for the pkg.depotd not working behind Apache > reverse proxy: I had to > configure a virtual host with "AllowEncodedSlashes On", or manifests and > packages URLs > never worked! > Strange one... Not so strange, really, as package FMRIs need to have encoded slashes in them. It's a reasonable default for a web server to refuse non-canonical representations that could allow for path traversals. Cheers, Bayard ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Project status
The edit in question came from an IP belonging to a Swedish VPN pool on February 17. OI has its own page: http://en.wikipedia.org/wiki/OpenIndiana On Sun, Apr 8, 2012 at 8:07 PM, Linda Kateley wrote: > Yes open indiana should have it's own page. They are different things. > > Is there someplace that shows the name of the editor? > > > -- > Linda Kateley > Global Evangelist and Community Manager > (mobile) 612-807-6349 > (email) linda.kate...@nexenta.com > (skype) lkateley ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Newbie Questions - Installing various software
On Sun, Apr 8, 2012 at 1:45 AM, Andrew Myers wrote: > How difficult is packaging? Is OI looking for people to help? Is it perhaps > some way I could get involved? I have some experience with rpmbuild - is > there an Solaris equivalent? Yes, we are looking for people. Start with: http://wiki.openindiana.org/oi/Building+with+illumos-userland There are child pages that describe the contribution and development process. The documentation is itself a work in progress, as is the build system. See also: http://strictlygeeking.blogspot.com/2012/03/new-development-and-contribution-model.html ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Project status
Fixed. Clarified that illumian is derived from illumos and OpenIndiana community development and distinguished by continued use of Debian packaging. On Sun, Apr 8, 2012 at 2:35 PM, Alexander Eremin wrote: > Absolutely wrong, that's should be fixed. > Thanks, > Alexander > > On Apr 8, 2012, at 5:16 PM, Andrew Myers wrote: > >> This Wikipedia page seems to indicate that openindiana has been discontinued >> in favour of illumian. >> >> That's wrong, isn't it? >> >> http://en.wikipedia.org/w/index.php?title=Nexenta_OS&useformat=desktop >> >> ___ >> OpenIndiana-discuss mailing list >> OpenIndiana-discuss@openindiana.org >> http://openindiana.org/mailman/listinfo/openindiana-discuss > > ___ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [developer] First illumos-userland hackathon
On Fri, Mar 23, 2012 at 4:41 PM, Garrett D'Amore wrote: > I'm glad to see this, although a little disappointed that its strictly an > illumos userland bit -- why not also include some opportunity for > illumos-gate. I've definitely been encouraging people with a primary interest in porting and packaging who are interested in distro development to get more involved with illumos-gate as our closest upstream. I've done a scan of issues in the OI tracker recently, and there's a decent amount of stuff that needs upstream resolution, so one of the things I might do is create upstream issues for that and walk people through fixing as many of those as possible. The distros are definitely one place where the rubber hits the road for illumos-gate, and I'd like to see more of that fed back into illumos-gate for resolution. If people in the community are willing to use our stuff in anger, we should oblige them with a measure of support. One of the things that's on my list to get going is a community backline, which would pull issues from all the distros (SmartOS, illumian, OI), get them proposed diagnosed, identify already existing fixes (Joyent's way ahead on this with SmartOS), and drive resolution in illumos-gate. If I were putting this in a larger context, I'd say we've addressed our first challenge as a community, which is showing that we can have a critical mass of developers successfully working under distributed ownership, moving our codebase forward. Our next challenge seems to me to be providing processes for maintaining production quality, including providing a degree of shared risk management for distro support, emphasizing the ever-moving target that is working code without getting caught up in the kings and presidents governance questions. If we mean to embrace the devops concept, this seems a strategic way to do it. Cheers, Bayard ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] First illumos-userland hackathon
Thanks to Linda Kateley, Nexenta's community manager, we are holding a hackathon for illumos-userland in Amsterdam on May 23, alongside the European Open Storage Summit: http://www.meetup.com/illumos-User-Group/events/56953802/ Closer to the date we will be putting up an ideas page. If you're interested in contributing to this porting and packaging project, join us on the userland list: https://www.listbox.com/subscribe/?listname=userl...@lists.illumos.org We're currently spinning up our first dev cycle with our revised development and contribution process: http://strictlygeeking.blogspot.com/2012/03/new-development-and-contribution-model.html If you haven't been previous involved in development, please have a look at our documentation, which will be improving in the next month as we pick up the pace: http://wiki.openindiana.org/oi/Building+with+illumos-userland If there are things you'd like to see added or updated in userland, please see if it's already in our tracker and submit a new issue if it isn't already: https://www.illumos.org/projects/illumos-userland/issues/ Hope to see you there. Cheers, Bayard ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox on OpenIndiana
There are three problems running on VBox I've seen previously: 1) building illumos-gate from source takes days instead of hours; 2) the debug kernel is extremely unstable, frequently locking up and unable to recover; and 3) scalability for vCPU and memory is flat on the reference host platform (Ubuntu) and actually degrades materially going from 2 vCPUs and 4 GB memory to 4 vCPUs and 8 GB memory with an OS X host. I worked directly with the VBox developers on benchmarks a year ago to document some of these issues. There are definite gaps in what was tested, as well as assumptions that I was told were reasonable that I'd want to evaluate more critically this time out. The VBox devs are very reasonable, at least once you establish that you come bringing quality bug reports and strong supporting data, and they seems pretty dedicated to understanding and resolving problems with their product. I'm pretty heavily committed at this point, so this isn't a problem I can chase. I have, however, elsewhere recently offered to help other illumos developers who want to see this resolved. Cheers, Bayard On Mar 19, 2012, at 5:34 AM, Geoff Nordli wrote: > I have been using vbox 4.1.x on OI 151 for about 5 months now running > some server-based VMs with good success. > > I noticed some comments from Bayard on the list about how vbox was > completely unusable for development. > > Are there other people having success using it on servers or have I > just been lucky? > > thanks, > > Geoff > > ___ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Hi everyone
Ooh, tasty. Please register kit that can be made accessible here: https://www.illumos.org/projects/illumos-gate/wiki/SPARC_resources On Sun, Mar 18, 2012 at 11:05 AM, Jeppe Toustrup wrote: > On Sat, Mar 17, 2012 at 14:09, Bayard Bell > wrote: >> Both OI and illumos generally need SPARC hardware, particularly >> higher-spec kit suitable for our build environment, to support >> development. If you are willing to donate hardware to ship to a data >> centre, please contact me directly. We have a number of hosting >> options available in the US and UK. > > The company I work for already make a T5240 available for the > OpenIndiana and Illumos projects, could this cover some of the needs > you have? > It is however not something the company wants to get rid of, in the > sense of sending it away. But the server is connected to a 100 Mbit > uplink. > > -- > Venlig hilsen / Kind regards > Jeppe Toustrup (aka. Tenzer) > > ___ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Support OI and illumos for GSoC 2012
Hi, Nikola, On Sat, Mar 17, 2012 at 8:06 PM, Nikola M wrote: > Bayard Bell wrote: >> VirtualBox has proven to be effectively unusable >> (building from source takes days instead of hours, and debug kernels >> suffer awful performance and lockups) > Why Vmware? > Vmware is not available for Openindiana/Illumos. > And Virtualbox is there for Solaris and until now, Illumos/Openindiana. To reiterate: what we need is a set of free and easy virtualization solutions for students who don't yet have an illumos distro installed. VirtualBox, as already explained, is unusable for development on several levels. The VirtualBox developers are very clear in saying that their virtual desktop product doesn't target the developer space. Asking an Oracle-owned product to devote cycles to making their product enable development for illumos is a dead letter and VirtualBox a dead end. I've interacted directly with the VirtualBox developers--I like them, they seem to know their stuff, but none of that is going to get past the fact that the problems here require a considerable allocation of resources controlled by the lawnmower. > Maybe reason for mentioning VmWare is because you think students have MS > Windows or OSX on their laptops and just lucky ones have Linux? We make no assumptions about this or judgements about what existing installs mean. vmWare gets coverage where KVM is not an option, which is why I'm asking after both. If someone's building the OS on a guest and saying it doesn't work (which is entirely consistent with previous experience), we need viable and flexible options for other kinds of guests. > Maybe one nice dual-boot setup (Installing system on same disk as > current one but on separate partition) with setting up ZFS and > Openindiana on it with numerous separate boot environments (BE's) for > testing Illumos kernels are in place for development? We're seeing a lot of students who are already triple-booting laptops and can't take on another bare metal OS install as the price of entry. Repartioning with enough space to add another OS isn't a solution that gets people in the door. Once people are in the door, it's a different question. We need to get them there. We've already got a volunteer, but I'm always happy to have a team. Cheers, Bayard ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] SPARC resources for OI and illumos
We had a number of responses to a query for SPARC resources in support of illumos and OI. I've provided a basic wiki page with four buckets, providing a continuum of access, from shipping kit to a hosting arrangement to running tests of specific changes and reporting back on any bugs. If you have SPARC kit and would like to see the project continue to support it, we need hardware, particularly kit that can support substantial compile loads but also including a broad range of hardware for testing drivers and working up a SPARC HCL. If you haven't already registered for the illumos wiki, you'll need to do so. Use this wiki page to register what you've got. If you have something you can ship or have picked up, I'll be back in touch re: arrangements, although probably not immediately. If you want to support remote builds, there's some bundled CI cooking that will provide a foundation for that. https://www.illumos.org/projects/illumos-gate/wiki/SPARC_resources Cheers, Bayard ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Hi everyone
Both OI and illumos generally need SPARC hardware, particularly higher-spec kit suitable for our build environment, to support development. If you are willing to donate hardware to ship to a data centre, please contact me directly. We have a number of hosting options available in the US and UK. There's a few other bits going on the back burner to allow a distributed hardware testing model so that we can keep our HCL relatively current using kit people have at home or work. Watch this space for further updates. Cheers, Bayard On Thu, Mar 8, 2012 at 1:18 AM, Gonzalo Seoane wrote: > Hi ! > > i have an Sun A61-UltraSPARC IIIi and i looking for openindiana for this > machine! > > I was looking for a iso or something but i can't find it. > > cheers! > Gonzalo Seoane > ___ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Support OI and illumos for GSoC 2012
Folks, First off, if you haven't already heard, illumos has been accepted to participate in GSoC 2012: http://www.google-melange.com/gsoc/org/google/gsoc2012/illumos OpenIndiana is participating under the illumos umbrella. If you are a graduate or undergraduate student interested in operating system development and related topics (networking, virtualization, storage, instrumentation), I'd encourage you to get involved and consider applying. One thing that we need to help expose students to OI and illumos is virtual appliances. VirtualBox has proven to be effectively unusable (building from source takes days instead of hours, and debug kernels suffer awful performance and lockups). A lot of the students we've seen are running on laptops without an immediate option to run off bare metal and not enough internet access to use hosted solutions, so we need to provide simple ways for them to run virtualized. There are two obvious options: one is running under Linux KVM, and the other is providing VMWare appliances with a fresh install of 151 prestable. If you've got some experience with KVM, it would be much appreciated if people could provide blog posts and mail links to for aggregation and/or work on a common page on the illumos or OI wiki documenting what's known to work. Both of these can subsequently be turned into formal documentation--what we need right now is a bit more sharing and circulation of what people are already doing. If you have a copy of VMWare, it would be much appreciated if you could contact me directly and/or join the oi-dev mailing list and work with us to provide an appliance distribution. The latter's not difficult, but the development team has so much else on at the moment that we really need someone to step up for this. Cheers, Bayard ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] illumos-userland
As many of you will have heard, the OpenIndiana and illumian development teams have joined forces to provide a common development environment for porting and packaging software to illumos outside of the core illumos-gate. If you would like to get involved in porting and packaging, please join us on the new userland mailgroup: https://www.listbox.com/subscribe/?listname=userl...@lists.illumos.org If you need to report a bug in a ported application or library in illumian or OpenIndiana, request that something be ported, or register your interest in providing a port or updating an existing one, please use the issue tracker at: https://www.illumos.org/projects/illumos-userland If you want to learn how to build software using the illumos-userland system, please start with: http://wiki.openindiana.org/oi/Building+with+illumos-userland Cheers, Bayard ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [oi-dev] OpenIndiana/illumos hacking session - cancellation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Could we get slightly more detail than has been available thus far, such as the times when the facility will be available on each day and not just the dates? On 27 Jun 2011, at 12:01, Damian Wojsław wrote: > Quoting Damian Wojsław : > > Thanx to wonderful Hans Rosenfeld the session will take place. Time, place > and cost as in original announcement. > > Please mail rosenf...@grumpf.hope-2000.org for more information. > > Regards > > > > > -- > Damian Wojsław > > > > This message was sent using IMP, the Internet Messaging Program. > > ___ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.12 (Darwin) iQIcBAEBAgAGBQJOCGYmAAoJEHm5cBpJ87doze8P/1JclR8ydT8BNqnN5ekYfmbV 9ZfRIJxj6UFVxvFI2p5e06Ng+9nwl0RcBBKipDcRD9siZTlQ7OQ0mUJ9FaLYyCeo oXpAaD13UGMlof+SzggUlogzjGXxrm5uDly/ZWZ7YhFkALnq8yi1F06KSQTSd9ZT p+RKpmaN4d7OKehHXe53ZdWZYX0k2tRbuvl7c7o0LnxgNkm2aQfqk2adsWKlBluu JNobX0qw2BUfLiay2FT+EFGv/GTVIlkMepROiQoK2aMPRM5TVbEbiopcMLz7g64r Rf5WamqcSYqX6LqBznwBrbeNizMnpc5hacg7SSWAbhDO39uqrWw2trOYmWTmy/Fy C5Qzo7icZkV9497sfNgHGrHAphANjq/8196Wb8+OUhbiY2o+IxO+EpaGNxhoLoJ+ HcWsW0buaM0ozs3Bfb+PA0Nc+D3Rn3q2JQx0BXC/mlAC6qFNoHDecNPnmmzFi85p bqYuMRDyINE/jJM9t6TuIlyXrkG17xLOblOwIZVKMJD+6DhY9MiMuBjIREEuIf5+ B3dSPsqqU58y5Lr/q2mSXBXTKYW/jpAONcewApoHcd3Gkb6scYO+KawBFZR5SDkw SI+xzW/Yrl91samv3ye99M5cRwPnfsosM2IZYCKeHI4JZk0pKpH7LuWkdduNoJMJ Ygfm+9M4hfRc2hLT9cDg =vaNh -END PGP SIGNATURE- ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [illumos-Developer] [illumos-Discuss] OpenIndiana/illumos hacking session
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Could we get some details on this? I had put off booking, waiting for confirmation of the details, which turned into a cancellation notice. Now the event may yet be on, but there still aren't any particulars to help with booking. On 27 Jun 2011, at 11:52, Hans Rosenfeld wrote: > On Mon, Jun 27, 2011 at 11:31:18AM +0200, Hans Rosenfeld wrote: >> On Mon, Jun 27, 2011 at 10:40:59AM +0200, Damian WojsÅ?aw wrote: >>> I'm very sorry to inform you that due to unexpected interference the >>> session cannot proceed. I'm sorry for the inconvenience that I may >>> have caused. >>> In the short: 2nd - 3rd of July hacking session in Berlin won't take place. >> >> I just mailed the guy who is supposedly responsible for the buero 2.0 >> site. I haven't got a reply yet, but I think we can still have the >> session in Berlin. >> >> So please don't cancel your flights and hotel rooms yet, there is still >> hope :) > > The cancellation has been cancelled. > > > To make that absolutely clear again: > > The OpenIndiana/Illumos hacking session on 2nd/3rd of July will take > place as announced. Sorry for the confusion. > > The information from the original announcement is still valid. If you > have any questions, mail me. > > See you in Berlin! > > > Hans > > -- > %SYSTEM-F-ANARCHISM, The operating system has been overthrown > > ___ > Developer mailing list > develo...@lists.illumos.org > http://lists.illumos.org/m/listinfo/developer -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.12 (Darwin) iQIcBAEBAgAGBQJOCGHOAAoJEHm5cBpJ87dorH4QALOjiKypWm67QHc05iwIr742 RXGS2Q/8wBrqY/H0MdIQbuBxb0FCPZ121zY5T5qX/ofGIB86vuJuKqGdrL7ZMvsO qNj/fjx6UCq1C+zZuB5MccA3tw08U58ywVs/oqMk7k33Wo1Bb080hEp/DK9QoPza H/vF5EeA24kPTKyJjZO/P90QmhZkqfsyav69FodwPWk9Rj2BHjrp4IpTR+BqoC9x x6ccy8lxiemRuZBkpQ80fdm2YT6E/GxblKoYD6hQE/FS3xh1f5XBgDjgcrOrwYAW USzuNeXHp7coifsIww+PmTASiC54DM4i7VUgksvz5CQPvDhb3XuKiG8iiPLd8QxW wzumK0K55AZDbsDfQqFZM+pUaD8LQjcZXhQy9y5CBQjYS54QFv/3aocftAxu6yvh 63Q4LkuYdXsOefJzxrqoOtbL9V1PdPyflPF0AAY/qLhD8BRvLR9wEIAw9W6G+YCf XuIeHVl7aZGZ6HIAeqSzzDNNO7H6sL3BqusQo3tJKukUZ+x4Z44q3MUPlrCUdrmX LQUCvRatrmIbTiaolinUMKQUcwMqdvGyw3++naHQp02sVwB8OUUL+FZ3grGCfDtA GWx9rwQmjDLO6CGxvYX7BA4rzXP4rlg5tscmKNfmQK21MQqUJgkegZNpVrYYz9WK tUpGpBADZ1cIuf0E00is =tbnM -END PGP SIGNATURE- ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [illumos-Discuss] branding for illumos/openindiana
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22 Jun 2011, at 09:58, Volker A. Brandt wrote: > Nikola M. writes: >> On 06/22/11 09:28 AM, Gregory Youngblood wrote: Do you want to tell me that last year, during which I have done everything to promote OpenIndiana in my local Open and Free software community, is going to be wasted? No one and I really mean no one will ever take a second look again if I have to go yet another round of "So, this *was* OpenSolaris and it *was* OpenIndiana, now it is SomeOtherShit." > > Damian, you are absolutely completely correct. I totally fully agree! > >> I would like to share with you some insights about this promotion thing, >> since in previious period, I was still giving away 2009.06 CD's together >> with OI update and Illumos/S11ex story to tell. > > Nikola, this is really a much better idea. Let's focus on producing > a good stable Live CD and then distribute it as widely as possible. > I would not mind paying 30 Euros for 100 CDs to give away. I don't > know what the actual costs are, but they would be less per CD as > the total number increases. > > At one point, Sun managed to get the OpenSolaris Live CD included in > an issue of a well-known and respected computer magazine here in Germany. > Something like this would be great marketing. :-) Amidst this outpouring of cratylist fallacy, I tend to the views above: talking about marketing without first identifying your targets of opportunity is folly. The important question is where there is immediate growth potential, what gets us there, and which targets promise to help most with accumulation. Revisiting some of the comments made at the Illumos meet-up, some consideration should be given to existing deployments of Solaris that aren't supported or economically viable with the sharp cut-off of Sun4u support in Solaris 11 or under Oracle's licensing terms. Sun also had a tremendous presence in universities, and this was valuable not just because computer science students developed a Solaris affinity but because you had people who would push the operating system in intriguing ways and provide very solid bug reports or enhancement requests if and when they had problems. I'm not averse to the idea of trying to pick up users from people running Linux, but I think there's a tremendous opportunity to consolidate the previous Sun base, particularly for people who are looking for an actively developed OS to run on older kit. More valuable than naming the OS is having solid localisation support for places like Brazil, India, China, and Russia, where there are large pools of engineering talent and interest in open-source software. These are suggestions sketched out for exemplary purposes, emphasising the fundamental point that I think implicit but clear in Volker's suggestion: branding and marketing require a notion of targeting and some hard work to back up that decision-making process, and I think a thread like this needs more of that kind of bloody-mindedness. I think the objections expressed by Damian are on target for similar reasons: re-branding without having a clear sense of target audience, determinate recruitment strategies, or clear metrics for evaluating progress looks an awful lot like churning and frothing that undermines what progress has been made. Cheers, Bayard -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.12 (Darwin) iQIcBAEBAgAGBQJOAcMjAAoJEHm5cBpJ87do3ysP/RzuS2owMX077kti8FIJ1UQv hmqN6kDKJ4uaw4aSdt+ry4dUztCMmcKDQTpsEmmPwrjsOn5DAAcq8gbZtcvjztjW ztVHenoKV7wD3NJSbRQMSDOcLedTqtfc40Klh3Poe8du3FzQNcxVxV5wpFLTnkXd 3HFYSNitEPSa/e3Vieo/rrGN1qZlYgvJqMSdXrad3l3es7hTFoGUsdYElQaenAZt HRQDyHiV/djH8bTPKqy2b5M4eM071y0iJx6VmBwEqII4VjRoBPfma3JmELnn/zCJ DRv1Uag37kgH+8wxn/03f5tMbcIc+RW0qg66ItDo5uEHp7Y8jyzIUBleMxi9bovA 0JaEut92RY7k6uhzeB6ZFcjqN53tM1MGAOUZ+H5lSyzmZFa31iB+nrH7RFgfBM5N 6A0VNJsO+YnzMRyUZkDHHaKTjdrTinhsYdPiDi1k06eG/ueCLIEMcPbv1ll+eOy/ 6V2h3/JX6gCDC0/eKRA+TJNiTLsBD+YfZqb24UPntwlFW6g4gC+ac/9elpxcbtWL JLkinUUGncKmsmnVHBw/8Na69f8Nb24DxH0dXEvczaCtJXc3Q1h8pJXEt/mcgU67 eqhel9utIIaL4go3XAyjp+T6QGz/CcNm+9aGQWtTuQbpZIRljMn6GgNaLZbrtgWq 5kJJVT26DqG0uxeaxtgF =HKEX -END PGP SIGNATURE- ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Update info?
Found some further background reading from security-discuss@ for anyone looking for further technical background info: http://opensolaris.org/jive/thread.jspa?threadID=98824 http://opensolaris.org/jive/thread.jspa?threadID=98824&tstart=210 http://opensolaris.org/jive/thread.jspa?threadID=98729&tstart=210 On 24 May 2011, at 10:42, Bayard Bell wrote: > On 23 May 2011, at 22:29, Jeppe Toustrup wrote: > >> 2011/5/23 Ken Gunderson : >>> On Mon, 2011-05-23 at 15:39 -0400, Alex Smith (K4RNT) wrote: >>>> Another related question - why have we stopped using pfexec and >>>> started using sudo? I preferred RBAC... >>> >>> Have we? I've been testing 148b and just assumed it was a defect. If >>> not, I concur with you that RBAC is preferrable to sudo. >> >> The change was made upstream. See this bug report which discusses the change: >> https://defect.opensolaris.org/bz/show_bug.cgi?id=4885 > > This looks to me like a comedy of analogical errors: it's not, for example, > that Windows users no longer have access to admin privileges, it's just that > asserting those privileges requires authentication. Similarly, it's not that > sudo is the right way to do things in general, nor is it all that important > that using sudo provides an affordance to people accustomed to using it > elsewhere. It's that pfexec doesn't have a mechanism to require > authentication for the assertion of particular levels of privilege, and it > looks like a decision was made to kick the can down the road on that. You > could follow the various offered analogies conclude not that access to root > should be mediated by sudo because that's what people expect but that people > rightly expect there to be an authentication requirement, in principle if not > in fact, between them and access to those privileges. It wouldn't be a > show-stopper to say that for most people's purposes, pfexec is like sudo, > it's just called pfexec and has a different configuration system because the > privileges have a different structure, if you need to edit the config files, > read the fine man page. The problem is a decision was made, however > implicitly or explicitly, not to fill in the functional gap and add > authentication. Instead of agreeing that pfexec needed to be like sudo in > this respect and making it that way, we just got sudo. > > That continues to be the case because the determinative constraints haven't > moved an inch. I don't see the point in the subsequent Talmudic arguments > about references to Ubuntu, as the protracted argument doesn't add up to the > inconsequence of the point. > >> -- >> Venlig hilsen / Kind regards >> Jeppe Toustrup (aka. Tenzer) >> >> ___ >> OpenIndiana-discuss mailing list >> OpenIndiana-discuss@openindiana.org >> http://openindiana.org/mailman/listinfo/openindiana-discuss > PGP.sig Description: This is a digitally signed message part ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Update info?
On 23 May 2011, at 22:29, Jeppe Toustrup wrote: > 2011/5/23 Ken Gunderson : >> On Mon, 2011-05-23 at 15:39 -0400, Alex Smith (K4RNT) wrote: >>> Another related question - why have we stopped using pfexec and >>> started using sudo? I preferred RBAC... >> >> Have we? I've been testing 148b and just assumed it was a defect. If >> not, I concur with you that RBAC is preferrable to sudo. > > The change was made upstream. See this bug report which discusses the change: > https://defect.opensolaris.org/bz/show_bug.cgi?id=4885 This looks to me like a comedy of analogical errors: it's not, for example, that Windows users no longer have access to admin privileges, it's just that asserting those privileges requires authentication. Similarly, it's not that sudo is the right way to do things in general, nor is it all that important that using sudo provides an affordance to people accustomed to using it elsewhere. It's that pfexec doesn't have a mechanism to require authentication for the assertion of particular levels of privilege, and it looks like a decision was made to kick the can down the road on that. You could follow the various offered analogies conclude not that access to root should be mediated by sudo because that's what people expect but that people rightly expect there to be an authentication requirement, in principle if not in fact, between them and access to those privileges. It wouldn't be a show-stopper to say that for most people's purposes, pfexec is like sudo, it's just called pfexec and has a different configuration system because the privileges have a different structure, if you need to edit the config files, read the fine man page. The problem is a decision was made, however implicitly or explicitly, not to fill in the functional gap and add authentication. Instead of agreeing that pfexec needed to be like sudo in this respect and making it that way, we just got sudo. That continues to be the case because the determinative constraints haven't moved an inch. I don't see the point in the subsequent Talmudic arguments about references to Ubuntu, as the protracted argument doesn't add up to the inconsequence of the point. > -- > Venlig hilsen / Kind regards > Jeppe Toustrup (aka. Tenzer) > > ___ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss PGP.sig Description: This is a digitally signed message part ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Gnome to become a Linux only project
I've read most of the thread, and I don't see anyone drifting that way. Instead I see people saying that they aren't too worried about kFreeBSD because it's a "toy" OS and then some varying degrees of sectarianism and ecumenism about Linux distros. What I took away from it was that there are a handful of developers who have some very strong views favouring Linux specificity but that almost anyone identifying themselves as members of the GNOME foundation or with a gnome.org address has the desire to limit focus to a single platform and rather think that the project's social skills need improvement. It's probably not coincidental that the thread fires up around systemd integration and that it's RH people associated with systemd development appear a majority of the handful given to categorical assertions about the wisdom of narrowed platform specificity. On 19 May 2011, at 23:08, Gary wrote: > Perhaps it would help if I read more of the actual email thread but > what I read quoted on Phoronix left me with a different impression. > What I understood is that the author is suggesting they create a GNOME > centric OS based around the Linux kernel. It could seem then that > their current efforts to keep it OS independent _may_ be left behind > as a result but that's still assuming all their devs agree that's a > sound choice going forward. Who's crazy enough to start a new OS > distro these days? ;) PGP.sig Description: This is a digitally signed message part ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Recover from user_attr corruption
Does nsswitch.conf have you sourcing user_attr from a name service other than local files? Do you have any other snapshot images of your rpool that you can boot from grub? On 4 May 2011, at 00:21, Gary Gendel wrote: > Hi, > > I installed a package that overwrote my privileges in user_attr. Now I can't > pfexec or do anythiing requiring raised privileges (software manager, etc.). > The laptop is running the dev_il repository. How the heck to I recover from > this? The only LiveCD I know of uses an earlier version of zfs. > > Thanks, > Gary > > > ___ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss PGP.sig Description: This is a digitally signed message part ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Grub2 and OI
grub2 is modular, so ZFS support exists as an extra module that exists in the
community code base. Legacy grub is a completely different kettle of fish.
On 1 Apr 2011, at 06:20, Christopher Chan wrote:
> ZFS support was added to grub2?
>
> I thought that the grub team did not take the patches and so only sun grub
> had zfs support?
>
> On Friday, April 01, 2011 09:24 AM, Darko Hojnik wrote:
>> Hi
>>
>> I have cloned my Rootfs and copied it with rsync over ssh to an FreeBSD
>> Laptop. I want dualbooting FreeBSD and OI from one ZFS Pool. Any Ideas
>> how to configure Grub2 for Solaris?
>>
>>
>> schleppi# zfs list
>> NAME USED AVAIL REFER MOUNTPOINT
>> pool 19.4G 127G 1.65M legacy
>> pool/debian 288M 127G 271M legacy
>> pool/freebsd8 7.60G 127G 6.91G legacy
>> pool/freebsd9 18K 127G 18K legacy
>> pool/home 7.23G 127G 7.23G /home
>> pool/solaris 2.27G 127G 2.27G legacy
>> pool/swap 2G 129G 155M -
>> schleppi#
>>
>>
>>
>> # Grub2.cfg
>>
>> # Timeout for menu
>> set timeout=10
>>
>> # Set default boot entry as Entry 0
>> set default=0
>>
>> menuentry "FreeBSD 8.1 RELEASE AMD64 on pool/freebsd8" {
>> kfreebsd /freebsd8@/boot/kernel/kernel
>> kfreebsd_module_elf /freebsd8@/boot/kernel/opensolaris.ko
>> kfreebsd_module_elf /freebsd8@/boot/kernel/zfs.ko
>> kfreebsd_module_elf /freebsd8@/boot/kernel/if_wpi.ko
>> kfreebsd_module_elf /freebsd8@/boot/modules/vboxdrv.ko
>> kfreebsd_module_elf /freebsd8@/boot/kernel/sound.ko
>> kfreebsd_module_elf /freebsd8@/boot/kernel/snd_hda.ko
>> kfreebsd_module /freebsd8@/boot/zfs/zpool.cache type=/boot/zfs/zpool.cache
>> set kFreeBSD.vfs.root.mountfrom=zfs:pool/freebsd8
>> }
>>
>> menuentry "FreeBSD 9.0 CURRENT AMD64 on pool/freebsd9" {
>> kfreebsd /freebsd9@/boot/kernel/kernel
>> kfreebsd_module_elf /freebsd8@/boot/kernel/opensolaris.ko
>> kfreebsd_module_elf /freebsd8@/boot/kernel/zfs.ko
>> kfreebsd_module_elf /freebsd8@/boot/kernel/if_wpi.ko
>> kfreebsd_module_elf /freebsd8@/boot/modules/vboxdrv.ko
>> kfreebsd_module_elf /freebsd8@/boot/kernel/sound.ko
>> kfreebsd_module_elf /freebsd8@/boot/kernel/snd_hda.ko
>> kfreebsd_module /freebsd8@/boot/zfs/zpool.cache type=/boot/zfs/zpool.cache
>> set kFreeBSD.vfs.root.mountfrom=zfs:pool/freebsd8
>> }
>> menuentry "Debian KfreeBSD Squeeze AMD64 on pool/debian" {
>> kfreebsd /debian@/boot/kfreebsd-8.1-1-amd64.gz
>> kfreebsd_module_elf /debian@/lib/modules/8.1-1-amd64/opensolaris.ko
>> kfreebsd_module_elf /debian@/lib/modules/8.1-1-amd64/zfs.ko
>> kfreebsd_module_elf /debian@/lib/modules/8.1-1-amd64/if_wpi.ko
>> kfreebsd_module /debian@/boot/zfs/zpool.cache type=/boot/zfs/zpool.cache
>> set kFreeBSD.vfs.root.mountfrom=zfs:pool/debian
>> }
>>
>> kind regards
>> Darko
>>
>> ___
>> OpenIndiana-discuss mailing list
>> OpenIndiana-discuss@openindiana.org
>> http://openindiana.org/mailman/listinfo/openindiana-discuss
>
>
> ___
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss@openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
PGP.sig
Description: This is a digitally signed message part
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Solaris Express server name broadcast
With all due respect, I think this starts from a bad premise and arrives at bad conclusions. The matter originally in question may be understood by a further analogy: it's a bit like jumping onto a list for C++ developers with a question about using an LDAP API in C. Sure, there might be people who know the answer on that list, possibly even a reasonable expectation that you might find that kind of overlap, but it's also asking people to be gracious to answer in that forum. If someone tells you that you'd be better off asking the question in a forum that's more problem-specific, that doesn't amount to there being a sign on the door saying that C developers and all others foreign to the C++ tribe aren't welcome. On the other hand, suggesting that you've got doubts about these people as C++ developers because they won't answer your question in that forum seems needlessly controversial, possibly though not necessarily a bit cheap. These are reasonable norms of netiquette: people who wear many hats may direct you to ask a question in a different forum and then be the person who answers that question when the redirect is made by the original poster. That's not rude or unhelpful: the person asking the question for the first time may face some latency and be a bit confused by standing on formalities, but the question may already be in the archive of the correct forum or will be more readily found there subsequently. I find Google queries get me a lot further when I not only know the search terms but know where to search via "site:" specification. It may be a little anal to point out these pragmatics, but it's not hostile, kicking someone off or calling them names, as I'd hope you'd concede after suggesting otherwise. Now, you raise Alan's contributions here, and they shouldn't go unacknowledged or fail to receive due credit. They also shouldn't be taken for something they aren't, which doesn't bear comparison here on the terms you suggest. Alan isn't answering "how do I use OpenIndiana" questions based on his understanding of continuing Solaris development at Oracle, he's giving people an understanding of how certain things came to pass in Solaris and outlining how changes relevant above all to X, packaging, and release management are happening in Solaris 11 post-fork, all of which is important and useful (and more concisely described by him as "color commentary"). I expect that if Alan spent a considerable amount of time on the OpenIndiana list answering end-user questions, his employers might have a problem with that and tell him he either needs to focus on his current job or find a new one more willing to support his evident interest in OpenIndiana. Let me hasten to say that example is valid in a context beyond Alan as a paid employee of a software-producing corporation: there is a general question of focus, commitment, and reliability here that is no less fundamental than the notion of "helping". It may be true that FOSS projects have their roots in helping people, but it has been my experience that these communities work because they rarely stray from their lanes to provide help under more abstract imperatives rather than weighing them as pragmatic considerations and communicating them as such. I might put this another way: would it be considered sustainable for OpenIndiana to tell prospective users to go ahead and adopt Solaris 11 Express while the kinks in OpenIndiana are worked out, with the expectation that they will be supported by the OpenIndiana community and given a cross-grade path across the fork? I think that's a bad premise leading to unsustainable commitments (for that matter, I wouldn't encourage anyone to deploy Solaris 11 Express without buying a support package to get patches), so I would argue it's better to be clear about not offering such support than to try to satisfy the expectations from making even an implicit commitment to that effect. What we're arguing isn't to help or not to help, it's what level of help is reasonable to expect and communicate as reasonable. I'm not saying that mine are the only possible or valid conclusions, but it seems to me deeply misconceived to take conclusions based on these pragmatics for hostile or unhelpful without giving them due consideration or even acknowledgement. We can disagree about what conclusions to draw, but it seems that the remarks you've offered don't engage these essentials. On 6 Mar 2011, at 09:10, Dmitry G. Kozhinov wrote: > Helping people != supporting competing product. > > I will *not* wonder getting support from FreeBSD or OpenBSD community. > You *are* not wonder getting support from e.g. Alan Coopersmith - Sol 11 > Express developer (AFAIK). > > Any FOSS initiative has it's roots in helping people. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-d
Re: [OpenIndiana-discuss] Solaris Express server name broadcast
There's a fork in the road, and you're asking people who've gone down the other fork for directions. You might reasonably expect those directions to start with: go back to the fork and go the other way, and, failing that, to ask a traveller who's taken the same fork as you. That response doesn't want for courtesy or respect. On 5 Mar 2011, at 21:28, Robert Soubie wrote: > Le 05/03/2011 18:43, Alasdair Lumsden a écrit : >> This list is for discussion of OpenIndiana rather than to provide support >> for Solaris 11 Express. If Oracle are failing to provide community support >> channels, you might want to take this up with them. > Thanks for your kind answer. I am not an Oracle consumer. > > I am running a home ZFS server under Solaris Express 11 because this was what > worked for me at the time I built the server, around November 15th, 2010, at > a time when, according to my experience, OpenIndiana was all but stable, and, > for any reason, I couldn't make Nexenta work for me either. Since SEx 11 > worked - and has worked reliably so far - I decided to use that for a while, > in hope OpenIndiana would become usable for my purposes. In the process I > learnt everything I know on *nix, and on Solaris in particular. Obviously > this is not much. > > When I switch back to a non-commercial OS (assuming SEx 11 *is* commercial), > I'll have to make a choice between OpenIndiana and, say, FreeBSD. One of the > criteria I'll use will surely be the willingness of people to provide help to > neophytes. Back to my initial concern, I fail to see why a question on how to > best backup a ZFS server could be off-topic. > > Regards. > > -- > Éditions de l'Âge d'Or — Stanley G. Weinbaum > http://www.lulu.com/robert_soubie > > > ___ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
