Re: [OpenIndiana-discuss] [osol-discuss] Can this scenario be accomplished?
> On the dead machine there are 3 sets of mirrored zpools (6 discs). > The one I mainly want access to now is 2 750GB sata drives. > > So I manage to connect one or both to a running os (livecd) > > ( How might that be achieved? ) If it were me, I would go the USB adapter/enclosure route. > Then the running os will see the discs and the zpool in it/them > along with the zfs filesystems? After a zpool import of the attached zpool, the zpool and associated zfs filesystems will be visible and accessible. > If that is right so far then I would have access to the data and could > even copy some piece of it to somewhere else on the network? Yes. You might need to modify the of the zpool (which can be done via the zpool import command) if it conflicts with an already existing zpool (you can't have two zpools named rpool, for instance). Then you might need to adjust the mountpoint attribute for the particular zfs filesystems that you wish to pull data off of so you can get to it using commands such as cp or rsync. > Lets say I don't really have room for the full zpool, but I could > still retrieve the needed bits by simple copy commands or rsync? Yes, assuming you've mounted the zfs filesystem(s) that you want to copy data off of. > Where my imagination gets in trouble is trying to visualize how the > new OS will see this disk... That is, will it see a zpool and have > immediate access? Like I could cd into some directory on it? You might want to look at the zpool manpage, but basically zpool import allows the storage pool and all of its associated filesystems to be accessible to the system. To get at the filesystems, i.e. to cd into some directory, you need to adjust the mountpoint attribute of the relevant zfs filesystems, and then just navigate to the now mounted filesystem. > But is there some reason NOT to hookup one of the actual discs to the > running OS (be it live cd or osol running in a VM) > > That is, is there a good chance of harming the disc in so doing? So long as you don't so something silly like zfs or zpool destroy, there isn't any real danger. Personally, I find it easier to actually learn a procedure and become comfortable with it when I don't have a real or imagined fear that I might accidentally make an unrecoverable mistake. > Any ideas how one would hook a raw internal disc up to an opensolaris > OS running on a laptop? The laptop has all modern connectors, esata, > usb, firewire. > > Is there some kind of adaptors or external housing available to make > such a connection? USB enclosures are extremely common, and while not the fastest option, the interface tends to be well supported across lots of different hardware. Hope that helps. -Sean ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [osol-discuss] Can this scenario be accomplished?
Sean writes: >> Would the newly installed OS recognize the data and zpool/zfs >> structures enough to retrieve the data or copy it over. >> >> Like if you made this external disk a zpool, would it just be erased >> or would the OS see the data and file structure? >> > > You just need to import the zpool(s). If there is someplace on the > network where you can copy the data to, there isn't even a need to > install OpenSolaris/Indiana, you can just boot up from the LiveCD and > go from there. Please excuse a bit of running off at the mouth here... I'm not really clear how to go at this. Your input sounds really good, but I'm getting stuck on how this to be done. (I mean in theory at this point) On the dead machine there are 3 sets of mirrored zpools (6 discs). The one I mainly want access to now is 2 750GB sata drives. So I manage to connect one or both to a running os (livecd) ( How might that be achieved? ) Then the running os will see the discs and the zpool in it/them along with the zfs filesystems? If that is right so far then I would have access to the data and could even copy some piece of it to somewhere else on the network? Lets say I don't really have room for the full zpool, but I could still retrieve the needed bits by simple copy commands or rsync? Where my imagination gets in trouble is trying to visualize how the new OS will see this disk... That is, will it see a zpool and have immediate access? Like I could cd into some directory on it? > It would be a good idea to first experiment with the procedure before > trying it out on your real drives, gather up a few USB thumbdrives and > do the same operations. Once you're confident that your procedure is > good, then carry on with the real drives. That is an excellent idea and is exactly what I am doing. But is there some reason NOT to hookup one of the actual discs to the running OS (be it live cd or osol running in a VM) That is, is there a good chance of harming the disc in so doing? I'd like to just copy my www stuff... all of htdocs, some 11-15 GB. Over to either the laptop or better still, a networked linux box that will pass as my apache server for the time being. Any ideas how one would hook a raw internal disc up to an opensolaris OS running on a laptop? The laptop has all modern connectors, esata, usb, firewire. Is there some kind of adaptors or external housing available to make such a connection? ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [osol-discuss] Can this scenario be accomplished?
> Would the newly installed OS recognize the data and zpool/zfs > structures enough to retrieve the data or copy it over. > > Like if you made this external disk a zpool, would it just be erased > or would the OS see the data and file structure? > You just need to import the zpool(s). If there is someplace on the network where you can copy the data to, there isn't even a need to install OpenSolaris/Indiana, you can just boot up from the LiveCD and go from there. It would be a good idea to first experiment with the procedure before trying it out on your real drives, gather up a few USB thumbdrives and do the same operations. Once you're confident that your procedure is good, then carry on with the real drives. -Sean ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [osol-discuss] How to permanently change a machines name
+-- | On 2010-11-10 17:41:26, Harry Putnam wrote: | | b 134 | How can I change a machines name permanently... not the IP numeric | address just the alphanumeric name? | | I managed it at least one other time but have now forgotten what all I | did. | | Is there a sort of starndard way? Or place where a new name can be | inserted and start being used on reboot, or after hostname ? /etc/nodename /etc/hosts -- bdha cyberpunk is dead. long live cyberpunk. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Setting up the recommended build environment errors with oi_147
On 11/10/10 12:08, Ron Parker wrote: I left a comment about this on the "Setting up the recommended build environment" wiki page.[1] According to Rich Lowe a change in caiman removed the "Primary Administrator" rights from the user that's created during installation.[2] I am relatively new to Solaris-based operating systems. What is the "right" solution or workaround to this? [1] http://wiki.openindiana.org/oi/Setting+up+the+recommended+build+environment [2] http://www.illumos.org/issues/204#note-4 the intended use of Primary Administrator was that it be granted to a non-root role account that would be used only during system administration. caiman skipped that step and granted it to the initial user. this was a bug, but casual use of pfexec as the initial user got embedded into a bunch of documentation before it was fixed. In the short term, the path of least resistance is to re-grant Primary Administrator to the user doing the build: % su root Password: # usermod -P 'Primary Administrator' build_user_name but it's a big hammer (makes that user id equivalent to root). I don't recommend that on a general purpose system; if you're setting up an effectively single-user system just to do package builds, it should be OK as a workaround for now. - Bill ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Amazon EC2 and OpenIndiana
On Wed, Nov 10, 2010 at 12:13 PM, Alex Smith (K4RNT) wrote: > So I can create a ZFS mirror on my local machine, or should I use one > of the instance-storage pre-existing AMIs and move to EBS? The example I gave merely creates two mirrored EBS instances to attach to a single EC2 instance (in my case, hardened OpenSolaris). I don't know if Solaris has a way to boot from EBS. But development on a lot of this stuff has dropped off since the Oracle acquisition... The most recent AMIs released appear to be from January of this year (probably not a coincidence as Jan 27 '10 was the date Oracle announced completion of their acquistion): http://aws.amazon.com/amis/Sun-Microsystems -Gary ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Amazon EC2 and OpenIndiana
So I can create a ZFS mirror on my local machine, or should I use one of the instance-storage pre-existing AMIs and move to EBS? On Wed, Nov 10, 2010 at 14:09, Gary wrote: > Here's a brief document I wrote with the assistance of the previously > referenced PDF -- note that the command used do require having > Amazon's EC2 and ELB management tools installed and in your path. > Also, pfexec may be substituted for sudo, mount locations changed, > different types/sizes of pools, etc. It's just a sample walkthrough... > > > HOWTO create a ZFS mirror on OpenSolaris with Amazon Elastic Block Store > volumes > > set up your environment > > $ cat ~/.bash_profile > > if [ -f ~/.bashrc ]; then > . ~/.bashrc > fi > > EC2_CERT=$HOME/.ec2/cert-FPGAG6000DYMT5SPWUS4CNMGVND3WF7Y.pem > EC2_PRIVATE_KEY=$HOME/.ec2/pk-FPGAG6000DYMT5SPWUS4CNMGVND3WF7Y.pem > PATH=/usr/gnu/bin:/usr/bin:/usr/X11/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/ec2/bin:/opt/ec2/sbin:/opt/elb/bin > MANPATH=/usr/gnu/share/man:/usr/share/man:/usr/X11/share/man > PAGER="/usr/bin/less -ins" > AWS_ELB_HOME=/opt/elb > EC2_HOME=/opt/ec2 > JAVA_HOME=/usr/java > export PATH MANPATH PAGER AWS_ELB_HOME EC2_HOME JAVA_HOME EC2_CERT > EC2_PRIVATE_KEY > > > look at your instances, note their zone > > $ ec2-describe-instances > RESERVATION r-7ef60316 164967591565 default > > INSTANCE i-86d861ee ami-e56e8f8c > ec2-XXX-XXX-XXX-XXX.compute-1.amazonaws.com > domU-XXX-XXX-XXX-XXX.compute-1.internal running gd 0 > m1.small 2009-10-21T16:47:10+ us-east-1a > aki-1783627e ari-9d6889f4 monitoring-enabled > > RESERVATION r-eb78b183 164967591565 default > > INSTANCE i-7fce5417 ami-e56e8f8c > ec2-XXX-XXX-XXX-XXX.compute-1.amazonaws.com > ip-XXX-XXX-XXX-XXX.ec2.internal running gd 0 > m1.small 2009-11-12T17:37:48+ us-east-1d > aki-1783627e ari-9d6889f4 monitoring-enabled > > > check volume availability, note their zone > > $ ec2dvol -H > VolumeId Size SnapshotId AvailabilityZone Status > CreateTime > VOLUME vol-d18c75b8 16 us-east-1d available > 2009-11-12T17:39:17+ > VOLUME vol-19956c70 16 us-east-1a available > 2009-11-12T04:16:04+ > VOLUME vol-d08c75b9 16 us-east-1d available > 2009-11-12T17:39:29+ > VOLUME vol-dc8c75b5 16 us-east-1a available > 2009-11-12T17:38:45+ > > > create a script to attach volumes for the zone your instance resides in. > > $ more attach-vols > #!/usr/bin/bash > # usage: attach-vols instance-id starting-dev number-of-vols > # instance to attach volume > inst=$1 > # starting device number > dev=$2 > # number of volumes to attach > num=$3 > let count=0 > # get a list of available volumes > for vol in `ec2-describe-volumes | egrep -i available | egrep -i > us-east-1a | cut -f2` > do > # attach the volume to the next device > echo "ec2-attach-volume -i $inst -d $dev $vol" > ec2-attach-volume -i $inst -d $dev $vol > # increment the device number > let dev=dev+1 > let count=count+1 > # if specified number have been attached then exit > if (( count == num )) > then > exit 0 > fi > done > > $ ./attach-vols i-86d861ee 2 3 > ec2-attach-volume -i i-86d861ee -d 2 vol-19956c70 > ATTACHMENT vol-19956c70 i-86d861ee 2 attaching > 2009-11-13T18:54:26+ > ec2-attach-volume -i i-86d861ee -d 3 vol-dc8c75b5 > ATTACHMENT vol-dc8c75b5 i-86d861ee 3 attaching > 2009-11-13T18:54:35+ > > $ ec2-describe-volumes | egrep -i attached | cut -f2,3,4,5 > vol-19956c70 i-86d861ee 2 attached > vol-dc8c75b5 i-86d861ee 3 attached > > find out what devices they've attached as (the first two are local EC2 > volumes) > then create a ZFS mirror, check its status and mount > > $ sudo format > Password: > Searching for disks...done > > > AVAILABLE DISK SELECTIONS: > 0. c7d0 > /xpvd/x...@0 > 1. c7d1 > /xpvd/x...@1 > 2. c7d2 > /xpvd/x...@2 > 3. c7d3 > /xpvd/x...@3 > Specify disk (enter its number): ^C > > $ sudo zpool create logs mirror c7d2 c7d3 > > $ sudo zpool status > Password: > pool: logs > state: ONLINE > scrub: none requested > config: > > NAME STATE READ WRITE CKSUM > logs ONLINE 0 0 0 > mirror ONLINE 0 0 0 > c7d2 ONLINE 0 0 0 > c7d3 ONLINE 0 0 0 > > errors: No known data errors > > pool: mnt > state: ONLINE > scrub: none requested > config: > > NAME STATE READ WRITE CKSUM > mnt ONLINE 0 0 0 > c7d1p0 ONLINE 0 0 0 > > errors: No known data errors > > pool: rpool > state: ONLINE > scrub: none requested > config: > > NAME STATE READ
Re: [OpenIndiana-discuss] Amazon EC2 and OpenIndiana
Here's a brief document I wrote with the assistance of the previously referenced PDF -- note that the command used do require having Amazon's EC2 and ELB management tools installed and in your path. Also, pfexec may be substituted for sudo, mount locations changed, different types/sizes of pools, etc. It's just a sample walkthrough... HOWTO create a ZFS mirror on OpenSolaris with Amazon Elastic Block Store volumes set up your environment $ cat ~/.bash_profile if [ -f ~/.bashrc ]; then . ~/.bashrc fi EC2_CERT=$HOME/.ec2/cert-FPGAG6000DYMT5SPWUS4CNMGVND3WF7Y.pem EC2_PRIVATE_KEY=$HOME/.ec2/pk-FPGAG6000DYMT5SPWUS4CNMGVND3WF7Y.pem PATH=/usr/gnu/bin:/usr/bin:/usr/X11/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/ec2/bin:/opt/ec2/sbin:/opt/elb/bin MANPATH=/usr/gnu/share/man:/usr/share/man:/usr/X11/share/man PAGER="/usr/bin/less -ins" AWS_ELB_HOME=/opt/elb EC2_HOME=/opt/ec2 JAVA_HOME=/usr/java export PATH MANPATH PAGER AWS_ELB_HOME EC2_HOME JAVA_HOME EC2_CERT EC2_PRIVATE_KEY look at your instances, note their zone $ ec2-describe-instances RESERVATION r-7ef60316 164967591565default INSTANCEi-86d861ee ami-e56e8f8c ec2-XXX-XXX-XXX-XXX.compute-1.amazonaws.com domU-XXX-XXX-XXX-XXX.compute-1.internal running gd 0 m1.small2009-10-21T16:47:10+us-east-1a aki-1783627eari-9d6889f4monitoring-enabled RESERVATION r-eb78b183 164967591565default INSTANCEi-7fce5417 ami-e56e8f8c ec2-XXX-XXX-XXX-XXX.compute-1.amazonaws.com ip-XXX-XXX-XXX-XXX.ec2.internal running gd 0 m1.small2009-11-12T17:37:48+us-east-1d aki-1783627eari-9d6889f4monitoring-enabled check volume availability, note their zone $ ec2dvol -H VolumeIdSizeSnapshotId AvailabilityZoneStatus CreateTime VOLUME vol-d18c75b816 us-east-1d available 2009-11-12T17:39:17+ VOLUME vol-19956c7016 us-east-1a available 2009-11-12T04:16:04+ VOLUME vol-d08c75b916 us-east-1d available 2009-11-12T17:39:29+ VOLUME vol-dc8c75b516 us-east-1a available 2009-11-12T17:38:45+ create a script to attach volumes for the zone your instance resides in. $ more attach-vols #!/usr/bin/bash # usage: attach-vols instance-id starting-dev number-of-vols # instance to attach volume inst=$1 # starting device number dev=$2 # number of volumes to attach num=$3 let count=0 # get a list of available volumes for vol in `ec2-describe-volumes | egrep -i available | egrep -i us-east-1a | cut -f2` do # attach the volume to the next device echo "ec2-attach-volume -i $inst -d $dev $vol" ec2-attach-volume -i $inst -d $dev $vol # increment the device number let dev=dev+1 let count=count+1 # if specified number have been attached then exit if (( count == num )) then exit 0 fi done $ ./attach-vols i-86d861ee 2 3 ec2-attach-volume -i i-86d861ee -d 2 vol-19956c70 ATTACHMENT vol-19956c70i-86d861ee 2 attaching 2009-11-13T18:54:26+ ec2-attach-volume -i i-86d861ee -d 3 vol-dc8c75b5 ATTACHMENT vol-dc8c75b5i-86d861ee 3 attaching 2009-11-13T18:54:35+ $ ec2-describe-volumes | egrep -i attached | cut -f2,3,4,5 vol-19956c70i-86d861ee 2 attached vol-dc8c75b5i-86d861ee 3 attached find out what devices they've attached as (the first two are local EC2 volumes) then create a ZFS mirror, check its status and mount $ sudo format Password: Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c7d0 /xpvd/x...@0 1. c7d1 /xpvd/x...@1 2. c7d2 /xpvd/x...@2 3. c7d3 /xpvd/x...@3 Specify disk (enter its number): ^C $ sudo zpool create logs mirror c7d2 c7d3 $ sudo zpool status Password: pool: logs state: ONLINE scrub: none requested config: NAMESTATE READ WRITE CKSUM logsONLINE 0 0 0 mirrorONLINE 0 0 0 c7d2ONLINE 0 0 0 c7d3ONLINE 0 0 0 errors: No known data errors pool: mnt state: ONLINE scrub: none requested config: NAMESTATE READ WRITE CKSUM mnt ONLINE 0 0 0 c7d1p0ONLINE 0 0 0 errors: No known data errors pool: rpool state: ONLINE scrub: none requested config: NAMESTATE READ WRITE CKSUM rpool ONLINE 0 0 0 c7d0s0ONLINE 0 0 0 errors: No known data errors $ df -k Filesystem 1K-blocks Used Available Use% Mounted on rpool/ROOT/opensolaris 8319892 3728123 4591770 45% / swap 2093032 276 2092756 1% /etc/svc/volatile /usr/lib/libc/libc_hwcap3.so.1 8319892
[OpenIndiana-discuss] Setting up the recommended build environment errors with oi_147
I left a comment about this on the "Setting up the recommended build environment" wiki page.[1] According to Rich Lowe a change in caiman removed the "Primary Administrator" rights from the user that's created during installation.[2] I am relatively new to Solaris-based operating systems. What is the "right" solution or workaround to this? [1] http://wiki.openindiana.org/oi/Setting+up+the+recommended+build+environment [2] http://www.illumos.org/issues/204#note-4 -- Ron Parker ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Amazon EC2 and OpenIndiana
You definitely _don't_ want to use S3 for raw volume storage -- that's why they released EBS in the first place. I would start with the PDF linked in the first URL below. I don't know if anyone's created an OI AMI yet but I'm still using hardened OpenSolaris images without issue. http://blogs.sun.com/ec2/entry/ebs_is_supported_on_opensolaris http://blogs.sun.com/prateek/entry/using_ebs_with_opensolaris_2008 q.v. http://blogs.sun.com/ec2 -Gary ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Amazon EC2 and OpenIndiana
I have never actually tried, but I do have these (2) URL's that I have archived. Hope these help. http://blogs.sun.com/angelo/entry/mounting_amazon_s3_buckets_as http://blogs.sun.com/skr/entry/sun_ray_in_opensolaris_2009 Jerry Kemp On 11/10/10 12:29, Alex Smith (K4RNT) wrote: > Has anyone here used EC2 with OpenSolaris or OpenIndiana? If so, > please contact me off-list. I'm not sure how to do it allowing use of > Elastic Block Storage. > > Thanks! > ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Amazon EC2 and OpenIndiana
Has anyone here used EC2 with OpenSolaris or OpenIndiana? If so, please contact me off-list. I'm not sure how to do it allowing use of Elastic Block Storage. Thanks! -- " ' With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.' Those words were uttered by Judge Aaron Satie as wisdom and warning... The first time any man's freedom is trodden on we’re all damaged." - Jean-Luc Picard, quoting Judge Aaron Satie, Star Trek: TNG episode "The Drumhead" - Alex Smith (K4RNT) - Murfreesboro, Tennessee USA ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [b 147] Consensus on how to set up static IP
On 11/10/10 04:05 PM, Harry Putnam wrote: Christopher Chan writes: On Tuesday, November 09, 2010 07:16 AM, Harry Putnam wrote: Can anyone point me to, or supply a brief step thru describing a known to work method for setting up a static IP address. One with complete steps that are current, as it appears from googling around that there are several ways described and not all work on newer opensolaris like b 134. ??? Is it really too hard to ask a question? A series of question marks is pretty meaningless. [...] Do we have a standard way to do this now? I don't know about standard but for static ips, I use the 'old way' and not nwam. Which is stuff ip-address into /etc/hostname.interface0, svcadm disable network:nwam; svcadm enable network:physical and edit /etc/resolv.conf and check for dns in /etc/nsswitch.conf for hosts. Exactly what I hoped to avoid. ---- ---=--- - DerSaidin writes: Hello, See: http://blogs.sun.com/PlasticPixel/entry/nwam_static_ip_address_for The other files you'll want to check (I'm unsure if these are essential) when setting up a NIC are: /etc/nsswitch.conf /etc/defaultrouter I've seen various comments about that /etc/nsswitch.conf In my case it shows `files' first at every entry including `host'. Apparently some where added by dhcp when that was used: From /etc/nsswitch.conf on opensolaris b 134 [...] #hosts: files # Commented out by DHCP hosts: files dns # Added by DHCP #ipnodes:files # Commented out by DHCP ipnodes: files dns # Added by DHCP [...] About /etc/defaultrouter I do not have that file. I could of course create it, but it seems to work without it. find /etc/ -iname '*router*' But the route is still set and shows up in `netstat -nr' So that one (/etc/defaultrouter) may not be necessary (this is on opensolaris b 134) --- - ---=--- - Thanks for the URL... yes, I found other input very similar and did that on an opensolaris install successfully so hopefully it will also do the job on openindiana b 147 Haven't got to it yet. However I will say that opensolaris b 134 does not have the same setup at the network icon on upper left of desktop. oi b 147 has a different and better dialog far as I saw. And it may have actually done the job... it turned out that my virtual networking was confused by having both vmware and vbox installed apparently when I installed vbox (after vmware by a week or two) it took over the vmware vmnet adaptors somewhat confusing... but ok now. NWAM does static IP nicely, just not all settings are entirely accessible by GUI (imo config files are simpler/nicer anyway). Yes, give me files too but which are you referring to that are not accessible? Do you mean /etc/defaultrouter and /etc/nsswitch.conf? I haven't done it since b134 but there using the GUI to NWAM from the status bar next to the clock worked. Should be fairly straight forward. Think I may have needed one or two relogins to get the status bar to show both correct info and green instead of errors but it worked. Regards, Jon ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] snv148 out in 2, 3 weeks?
Hi, Is it possible that oi148 will be ready in 2, 3 weeks? Does anybody know how long it will take? I won't install snv147. Hi Daniel, I believe what's been posted to the list was that it's expected to be available in 1Q 2011 (meaning 1st quarter of 2011). Since that won't be until after the beginning of the new year I would suspect the answer to your question is 'no'. But I have no inside knowledge. Cia W The 2011.Q1 is for the first "stable" release as opposed to the more regular "dev" releases. oi_147 and oi_148 are dev releases. 148 will be out ASAP - obviously not before it is all built though. Check http://wiki.openindiana.org/display/oi/oi_148 for the current status. You'll see at the moment the hold up is getting g11n built. Once that is done progress should be more easy to spot. Regards, Jon ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [b 147] Consensus on how to set up static IP
Christopher Chan writes: > On Tuesday, November 09, 2010 07:16 AM, Harry Putnam wrote: >> Can anyone point me to, or supply a brief step thru describing a known >> to work method for setting up a static IP address. >> >> One with complete steps that are current, as it appears from googling >> around that there are several ways described and not all work on newer >> opensolaris like b 134. > > ??? Is it really too hard to ask a question? A series of question marks is pretty meaningless. [...] >> Do we have a standard way to do this now? >> > > I don't know about standard but for static ips, I use the 'old way' > and not nwam. Which is stuff ip-address into /etc/hostname.interface0, > svcadm disable network:nwam; svcadm enable network:physical and edit > /etc/resolv.conf and check for dns in /etc/nsswitch.conf for hosts. Exactly what I hoped to avoid. ---- ---=--- - DerSaidin writes: > Hello, > > See: http://blogs.sun.com/PlasticPixel/entry/nwam_static_ip_address_for > > The other files you'll want to check (I'm unsure if these are essential) > when setting up a NIC are: > /etc/nsswitch.conf > /etc/defaultrouter I've seen various comments about that /etc/nsswitch.conf In my case it shows `files' first at every entry including `host'. Apparently some where added by dhcp when that was used: >From /etc/nsswitch.conf on opensolaris b 134 [...] #hosts: files # Commented out by DHCP hosts: files dns # Added by DHCP #ipnodes:files # Commented out by DHCP ipnodes: files dns # Added by DHCP [...] About /etc/defaultrouter I do not have that file. I could of course create it, but it seems to work without it. find /etc/ -iname '*router*' But the route is still set and shows up in `netstat -nr' So that one (/etc/defaultrouter) may not be necessary (this is on opensolaris b 134) --- - ---=--- - Thanks for the URL... yes, I found other input very similar and did that on an opensolaris install successfully so hopefully it will also do the job on openindiana b 147 Haven't got to it yet. However I will say that opensolaris b 134 does not have the same setup at the network icon on upper left of desktop. oi b 147 has a different and better dialog far as I saw. And it may have actually done the job... it turned out that my virtual networking was confused by having both vmware and vbox installed apparently when I installed vbox (after vmware by a week or two) it took over the vmware vmnet adaptors somewhat confusing... but ok now. > > NWAM does static IP nicely, just not all settings are entirely accessible by > GUI (imo config files are simpler/nicer anyway). Yes, give me files too but which are you referring to that are not accessible? Do you mean /etc/defaultrouter and /etc/nsswitch.conf? ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] snv148 out in 2, 3 weeks?
-Original Message- From: Daniel Bossert [mailto:dan...@dalll.se] Sent: 10 November 2010 15:46 To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] snv148 out in 2, 3 weeks? Hia Cia >> Is it possible that oi148 will be ready in 2, 3 weeks? Does anybody know >> how long it will take? >> >> I won't install snv147. >> > Hi Daniel, > > I believe what's been posted to the list was that it's expected to be > available in 1Q 2011 (meaning 1st quarter of 2011). Since that won't be > until after the beginning of the new year I would suspect the answer to > your question is 'no'. But I have no inside knowledge. > > > Cia W Thank you for this answer (even if that isn't that what I hoped). Daniel ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss Anyone with inside knowledge care to comment on this please? Paul ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] snv148 out in 2, 3 weeks?
Hia Cia >> Is it possible that oi148 will be ready in 2, 3 weeks? Does anybody know >> how long it will take? >> >> I won't install snv147. >> > Hi Daniel, > > I believe what's been posted to the list was that it's expected to be > available in 1Q 2011 (meaning 1st quarter of 2011). Since that won't be > until after the beginning of the new year I would suspect the answer to > your question is 'no'. But I have no inside knowledge. > > > Cia W Thank you for this answer (even if that isn't that what I hoped). Daniel ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] snv148 out in 2, 3 weeks?
On Wed, 10 Nov 2010 11:05:44 +0100 Daniel Bossert wrote: > > > Hello all > > Is it possible that oi148 will be ready in 2, 3 weeks? Does anybody know > how long it will take? > > I won't install snv147. > Hi Daniel, I believe what's been posted to the list was that it's expected to be available in 1Q 2011 (meaning 1st quarter of 2011). Since that won't be until after the beginning of the new year I would suspect the answer to your question is 'no'. But I have no inside knowledge. Cia W ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] snv148 out in 2, 3 weeks?
Hello all I am taking a looking into http://wiki.openindiana.org/oi/oi_148. I am wondering when snv148 will be ready as I am planning to change my desktop-computer from Ubuntu to OI. Is it possible that oi148 will be ready in 2, 3 weeks? Does anybody know how long it will take? I won't install snv147. Kind regards Daniel ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
