Re: [indiana-discuss] No graphical login after upgrade from b106 to b108
Ok I guess I'll wait some weeks until those issues have been fixed ;) To much hassle for to simply get it running. But thanks for your help! pato -- This message posted from opensolaris.org ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] install osol 08.11 on asus 1000HE
I filed 7235 (http://defect.opensolaris.org/bz/show_bug.cgi?id=7235) against install-lan faulting in this situation. -- This message posted from opensolaris.org ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] install osol 08.11 on asus 1000HE
Hi Michael, On 03/10/09 09:15, Michael Hunter wrote: I filed 7235 (http://defect.opensolaris.org/bz/show_bug.cgi?id=7235) against install-lan faulting in this situation. Actually, install-lan is remnant from old times of SXDE installer and has been removed from LiveCD as part of fix for bug 5831. As Glenn pointed out, 08.11 GUI installer is to be invoked in following way: $ pfexec /usr/bin/gui-install Thank you, Jan ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] install osol 08.11 on asus 1000HE
Ah, much better. A cosmetic issue I noticed was that on the screen lacking vertical height the progress bar ended up below the displayed area. That made it appear at first blush like maybe things were not moving forwards. Maybe the progress bar should be in a fixed part of the screen. But then I suck at any kind of graphic design so what do I know. In any case thank you! mph -- This message posted from opensolaris.org ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] install osol 08.11 on asus 1000HE
atge doesn't seem to indicate link state correctly (always up). Is that expected? -- This message posted from opensolaris.org ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] install osol 08.11 on asus 1000HE
Hi Michael Could you type scanpci? It will be easy for us to check your wifi driver.. ASUS Eees have a bit difference in the same Eee machines,that is,Eee 900 for Europe is different from the one for Japan.. Regards, -masafumi On 2009/03/10, at 20:41, Michael Hunter wrote: The i915 and atge drivers installed and worked fine (I used the atge binaries in the package). I'm not sure that the rwn driver is the right part for this machine. I think the wireless part is identifying itself as pci1a3b, 1067. I added a line to the aliases file for ath (based upon googling) but that didn't seem to work. 'prtconf -v' attached if you have any ideas. mph -- This message posted from opensolaris .org 1000he.prtconf.txt___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] install osol 08.11 on asus 1000HE
On Tue, 10 Mar 2009 21:08:43 +0900 Masafumi Ohta masafumi.o...@gmail.com wrote: Hi Michael Could you type scanpci? It will be easy for us to check your wifi driver.. ASUS Eees have a bit difference in the same Eee machines,that is,Eee 900 for Europe is different from the one for Japan.. Attached. mph Regards, -masafumi On 2009/03/10, at 20:41, Michael Hunter wrote: The i915 and atge drivers installed and worked fine (I used the atge binaries in the package). I'm not sure that the rwn driver is the right part for this machine. I think the wireless part is identifying itself as pci1a3b, 1067. I added a line to the aliases file for ath (based upon googling) but that didn't seem to work. 'prtconf -v' attached if you have any ideas. mph -- This message posted from opensolaris .org 1000he.prtconf.txt___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss pci bus 0x cardnum 0x00 function 0x00: vendor 0x8086 device 0x27ac Intel Corporation Mobile 945GME Express Memory Controller Hub pci bus 0x cardnum 0x02 function 0x00: vendor 0x8086 device 0x27ae Intel Corporation Mobile 945GME Express Integrated Graphics Controller pci bus 0x cardnum 0x02 function 0x01: vendor 0x8086 device 0x27a6 Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller pci bus 0x cardnum 0x1b function 0x00: vendor 0x8086 device 0x27d8 Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller pci bus 0x cardnum 0x1c function 0x00: vendor 0x8086 device 0x27d0 Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 pci bus 0x cardnum 0x1c function 0x01: vendor 0x8086 device 0x27d2 Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 pci bus 0x cardnum 0x1c function 0x03: vendor 0x8086 device 0x27d6 Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 pci bus 0x cardnum 0x1d function 0x00: vendor 0x8086 device 0x27c8 Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 pci bus 0x cardnum 0x1d function 0x01: vendor 0x8086 device 0x27c9 Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 pci bus 0x cardnum 0x1d function 0x02: vendor 0x8086 device 0x27ca Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 pci bus 0x cardnum 0x1d function 0x03: vendor 0x8086 device 0x27cb Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 pci bus 0x cardnum 0x1d function 0x07: vendor 0x8086 device 0x27cc Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller pci bus 0x cardnum 0x1e function 0x00: vendor 0x8086 device 0x2448 Intel Corporation 82801 Mobile PCI Bridge pci bus 0x cardnum 0x1f function 0x00: vendor 0x8086 device 0x27b9 Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge pci bus 0x cardnum 0x1f function 0x02: vendor 0x8086 device 0x27c4 Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x168c device 0x002a Atheros Communications Inc. Device unknown pci bus 0x0003 cardnum 0x00 function 0x00: vendor 0x1969 device 0x1026 Attansic Technology Corp. L1 Gigabit Ethernet Adapter ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] install osol 08.11 on asus 1000HE
On 2009/03/10, at 21:23, Michael Hunter wrote: On Tue, 10 Mar 2009 21:08:43 +0900 Masafumi Ohta masafumi.o...@gmail.com wrote: Hi Michael Could you type scanpci? It will be easy for us to check your wifi driver.. ASUS Eees have a bit difference in the same Eee machines,that is,Eee 900 for Europe is different from the one for Japan.. Attached. mph Thanks, Your wifi seems Atheros AB5B91,it is BGN adapter and it seem to be used MSI U100 Windbook... Well sorry I have no idea it would work but could you try to add pci168c,2a for your Atheros wifi? And Does anyone using MSI have ideas? -masafumi Regards, -masafumi On 2009/03/10, at 20:41, Michael Hunter wrote: The i915 and atge drivers installed and worked fine (I used the atge binaries in the package). I'm not sure that the rwn driver is the right part for this machine. I think the wireless part is identifying itself as pci1a3b, 1067. I added a line to the aliases file for ath (based upon googling) but that didn't seem to work. 'prtconf -v' attached if you have any ideas. mph -- This message posted from opensolaris .org 1000he.prtconf.txt___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss 1000he.scanpci.txt ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
[indiana-discuss] System monitor doesn't display disk activity on b108?
Title: E-mail Signature Sun 2008 Hi! Since recent updates (don't remember during which build it started) the system monitor doesn't show disk activity (processor and memory meters seem to work OK). Anybody else see this? Gilles. -- Gilles Gravier, CISSP Government Industry Solutions Architect Voice : +41 (22) 999 9051 Mobile : +41 (79) 472 8437 Fax : +41 (860) 79 472 8437 E-mail : gilles.grav...@sun.com Sun Microsystems 12 route des Avouillons CH-1196 Gland Switzerland http://www.sun.com/opensource/ SunIM : ggrav...@sun.com ICQ : 77488526 AIM : gillesgravier Y! : ggravier Jabber : ggrav...@jabber.org/Gaim Skype : ggravier MSN : gil...@gravier.org Google : gilles.grav...@gmail.com Sent from a laptop running OpenSolaris 2008.11 snv_108 using Mozilla Thunderbird (v2.0.0.18) ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] System monitor doesn't display disk activity on b108?
On Tue, 2009-03-10 at 15:00 +0100, Gilles Gravier wrote: Hi! Since recent updates (don't remember during which build it started) the system monitor doesn't show disk activity (processor and memory meters seem to work OK). Anybody else see this? Yes: http://defect.opensolaris.org/bz/show_bug.cgi?id=4504 -- Christian ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] System monitor doesn't display disk activity on b108?
Title: E-mail Signature Sun 2008 Thanks, Gilles. Christian Thalinger wrote: On Tue, 2009-03-10 at 15:00 +0100, Gilles Gravier wrote: Hi! Since recent updates (don't remember during which build it started) the system monitor doesn't show disk activity (processor and memory meters seem to work OK). Anybody else see this? Yes: http://defect.opensolaris.org/bz/show_bug.cgi?id=4504 -- Christian -- Gilles Gravier, CISSP Government Industry Solutions Architect Voice : +41 (22) 999 9051 Mobile : +41 (79) 472 8437 Fax : +41 (860) 79 472 8437 E-mail : gilles.grav...@sun.com Sun Microsystems 12 route des Avouillons CH-1196 Gland Switzerland http://www.sun.com/opensource/ SunIM : ggrav...@sun.com ICQ : 77488526 AIM : gillesgravier Y! : ggravier Jabber : ggrav...@jabber.org/Gaim Skype : ggravier MSN : gil...@gravier.org Google : gilles.grav...@gmail.com Sent from a laptop running OpenSolaris 2008.11 snv_108 using Mozilla Thunderbird (v2.0.0.18) ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
[indiana-discuss] Can't install IPSlame from Blastwave
Title: E-mail Signature Sun 2008 Hi, Gang! Trying to install VLC (or it's dependency : lame) from Blastwave... I keep getting : ggrav...@opensoltink:~$ pfexec pkg install IPSlame DOWNLOAD PKGS FILES XFER (MB) Completed 6/6 3021/3021 43.38/43.38 PHASE ACTIONS Install Phase 3301/4887 Action install failed for 'opt/csw/bin/lame' (pkg://blastwave/IPSlame): OSError: [Errno 2] No such file or directory The Boot Environment opensolaris-8 failed to be updated. A snapshot was taken before the failed attempt and is mounted here /tmp/tmpxC7wuN. Use 'beadm unmount opensolaris-9' and then 'beadm activate opensolaris-9' if you wish to boot to this BE. pkg: An unexpected error happened during installation: [Errno 2] No such file or directory Traceback (most recent call last): File "/usr/bin/pkg", line 2259, in ? __ret = main_func() File "/usr/bin/pkg", line 2208, in main_func return install(mydir, pargs) File "/usr/bin/pkg", line 736, in install api_inst.execute_plan() File "/usr/lib/python2.4/vendor-packages/pkg/client/api.py", line 482, in execute_plan self.img.imageplan.execute() File "/usr/lib/python2.4/vendor-packages/pkg/client/imageplan.py", line 699, in execute p.execute_install(src, dest) File "/usr/lib/python2.4/vendor-packages/pkg/client/pkgplan.py", line 258, in execute_install dest.install(self, src) File "/usr/lib/python2.4/vendor-packages/pkg/actions/hardlink.py", line 80, in install os.link(target, path) OSError: [Errno 2] No such file or directory pkg: This is an internal error. Please let the developers know about this problem by filing a bug at http://defect.opensolaris.org and including the above traceback and this message. The version of pkg(5) is 'dde59f7de2b4'. ggrav...@opensoltink:~$ Any idea what may be wrong? I've cleared the /var/pkg/download cache... no change. Cheers, Gilles. -- Gilles Gravier, CISSP Government Industry Solutions Architect Voice : +41 (22) 999 9051 Mobile : +41 (79) 472 8437 Fax : +41 (860) 79 472 8437 E-mail : gilles.grav...@sun.com Sun Microsystems 12 route des Avouillons CH-1196 Gland Switzerland http://www.sun.com/opensource/ SunIM : ggrav...@sun.com ICQ : 77488526 AIM : gillesgravier Y! : ggravier Jabber : ggrav...@jabber.org/Gaim Skype : ggravier MSN : gil...@gravier.org Google : gilles.grav...@gmail.com Sent from a laptop running OpenSolaris 2008.11 snv_108 using Mozilla Thunderbird (v2.0.0.18) ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] Can't install IPSlame from Blastwave
Gilles Gravier wrote: Hi, Gang! Trying to install VLC (or it's dependency : lame) from Blastwave... I keep getting : ggrav...@opensoltink:~$ pfexec pkg install IPSlame DOWNLOADPKGS FILES XFER (MB) Completed6/6 3021/3021 43.38/43.38 PHASEACTIONS Install Phase 3301/4887 Action install failed for 'opt/csw/bin/lame' (pkg://blastwave/IPSlame): OSError: [Errno 2] No such file or directory The Boot Environment opensolaris-8 failed to be updated. A snapshot was taken before the failed attempt and is mounted here /tmp/tmpxC7wuN. Use 'beadm unmount opensolaris-9' and then 'beadm activate opensolaris-9' if you wish to boot to this BE. pkg: An unexpected error happened during installation: [Errno 2] No such file or directory Traceback (most recent call last): File /usr/bin/pkg, line 2259, in ? __ret = main_func() File /usr/bin/pkg, line 2208, in main_func return install(mydir, pargs) File /usr/bin/pkg, line 736, in install api_inst.execute_plan() File /usr/lib/python2.4/vendor-packages/pkg/client/api.py, line 482, in execute_plan self.img.imageplan.execute() File /usr/lib/python2.4/vendor-packages/pkg/client/imageplan.py, line 699, in execute p.execute_install(src, dest) File /usr/lib/python2.4/vendor-packages/pkg/client/pkgplan.py, line 258, in execute_install dest.install(self, src) File /usr/lib/python2.4/vendor-packages/pkg/actions/hardlink.py, line 80, in install os.link(target, path) OSError: [Errno 2] No such file or directory This is a bug in the blastwave packages that IPS doesn't handle yet. You can find the details and a workaround here: http://defect.opensolaris.org/bz/show_bug.cgi?id=1770#c34 Cheers, -- Shawn Walker ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] Can't install IPSlame from Blastwave
Gilles Gravier wrote: Except that I don't get the not owner error... :) Sure it's the same bug? Sorry, bug 2358: http://defect.opensolaris.org/bz/show_bug.cgi?id=2358 There are many bugs related to the blastwave packages... Cheers, -- Shawn Walker ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] Can't install IPSlame from Blastwave
Title: E-mail Signature Sun 2008 Argh... This one doesn't have a workaround. :( Gilles. Shawn Walker wrote: Gilles Gravier wrote: Except that I don't get the "not owner" error... :) Sure it's the same bug? Sorry, bug 2358: http://defect.opensolaris.org/bz/show_bug.cgi?id=2358 There are many bugs related to the blastwave packages... Cheers, -- Gilles Gravier, CISSP Government Industry Solutions Architect Voice : +41 (22) 999 9051 Mobile : +41 (79) 472 8437 Fax : +41 (860) 79 472 8437 E-mail : gilles.grav...@sun.com Sun Microsystems 12 route des Avouillons CH-1196 Gland Switzerland http://www.sun.com/opensource/ SunIM : ggrav...@sun.com ICQ : 77488526 AIM : gillesgravier Y! : ggravier Jabber : ggrav...@jabber.org/Gaim Skype : ggravier MSN : gil...@gravier.org Google : gilles.grav...@gmail.com Sent from a laptop running OpenSolaris 2008.11 snv_108 using Mozilla Thunderbird (v2.0.0.18) ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] System monitor doesn't display disk activity on b108?
Christian Thalinger writes: On Tue, 2009-03-10 at 15:00 +0100, Gilles Gravier wrote: Hi! Since recent updates (don't remember during which build it started) the system monitor doesn't show disk activity (processor and memory meters seem to work OK). Anybody else see this? Yes: http://defect.opensolaris.org/bz/show_bug.cgi?id=4504 -- Christian If you're also missing network also missing network activity, see 6793416. tom ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] install osol 08.11 on asus 1000HE
On Tue, 10 Mar 2009 21:52:31 +0900 Masafumi Ohta masafumi.o...@gmail.com wrote: [...] Thanks, Your wifi seems Atheros AB5B91,it is BGN adapter and it seem to be used MSI U100 Windbook... Well sorry I have no idea it would work but could you try to add pci168c,2a for your Atheros wifi? And Does anyone using MSI have ideas? I tried this last night but it doesn't seem to work. I'll have to dig deeper. mph -masafumi Regards, -masafumi On 2009/03/10, at 20:41, Michael Hunter wrote: The i915 and atge drivers installed and worked fine (I used the atge binaries in the package). I'm not sure that the rwn driver is the right part for this machine. I think the wireless part is identifying itself as pci1a3b, 1067. I added a line to the aliases file for ath (based upon googling) but that didn't seem to work. 'prtconf -v' attached if you have any ideas. mph -- This message posted from opensolaris .org 1000he.prtconf.txt___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss 1000he.scanpci.txt ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] images, bootenv, clone, snapshot..
Bart Smaalders bart.smaald...@sun.com writes: [...] Harry wrote: So.. it can't be a clone... isn't a clone supposed to be a duplicate in every detail? Like in science fiction stories where a human is cloned but some tiny dna difference leads to a monster who isn't a clone anymore. hehe Bart responded: But this is a ZFS clone - which does copy on write - so until you change something, there's no disk space overhead ;-). Put another way, do I need that capability to be able to completely roll back to a known good state? Create a clone of the current environment and never touch it. Thanks for that reference to `copy on write (COW)'. This is my first brush with those concepts which I am finding good discussion of with google. I'll admit I don't fully understand it yet. But correct me if I have this wrong. The miss-named `clone', is not stand alone (Something one would expect from a `clone'). That is, it relies still on the parent if called into duty. Is that right? Could you move(mv) the clone to a new disc and boot it up? Or does the COW kick in during mv... I'm not clear what happens. Similar with the `snapshot'. It sounds like an OS frozen in time when the shutter snapped. But can you move it to a new disc and boot up? ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] images, bootenv, clone, snapshot..
Harry Putnam rea...@newsguy.com writes: Create a clone of the current environment and never touch it. Thanks for that reference to `copy on write (COW)'. This is my first brush with those concepts which I am finding good discussion of with google. I'll admit I don't fully understand it yet. But correct me if I have this wrong. The miss-named `clone', is not stand alone (Something one would expect from a `clone'). That is, it relies still on the parent if called into duty. Is that right? Could you move(mv) the clone to a new disc and boot it up? Or does the COW kick in during mv... I'm not clear what happens. BZT = wrong: Similar with the `snapshot'. It sounds like an OS frozen in time when the shutter snapped. But can you move it to a new disc and boot up? On further consideration I need to drop this about snapshot.. After all, applying the term to real photographic snapshots, one would never expect a real snapshot to have the capabilities of the subject of the snap. So poor analagy... deeply flawed. But what about `clone'? It seems my reasoning stands on that. ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] images, bootenv, clone, snapshot..
Harry Putnam wrote: Harry Putnam rea...@newsguy.com writes: Create a clone of the current environment and never touch it. Thanks for that reference to `copy on write (COW)'. This is my first brush with those concepts which I am finding good discussion of with google. I'll admit I don't fully understand it yet. But correct me if I have this wrong. The miss-named `clone', is not stand alone (Something one would expect from a `clone'). That is, it relies still on the parent if called into duty. Is that right? Could you move(mv) the clone to a new disc and boot it up? Or does the COW kick in during mv... I'm not clear what happens. BZT = wrong: Similar with the `snapshot'. It sounds like an OS frozen in time when the shutter snapped. But can you move it to a new disc and boot up? On further consideration I need to drop this about snapshot.. After all, applying the term to real photographic snapshots, one would never expect a real snapshot to have the capabilities of the subject of the snap. So poor analagy... deeply flawed. But what about `clone'? It seems my reasoning stands on that. ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss A clone is part of the zpool; it can only be copied elsewhere, not moved. A snapshot is the filesystem state at a moment in time. Such snapshots can be cloned, and then the clone can be modified. This is like a sci-fi movie, where you can take a picture, create a working world from the picture, and then step into it. Hmmm... fun plot... it has potential at a variety of levels :-). Anyway, the resulting clone shares all unmodified blocks w/ original snapshot, which shares them w/ the original FS. This is really ZFS details, not Indiana, though. You may find zfs-discuss a more appropo list... - Bart -- Bart Smaalders Solaris Kernel Performance ba...@cyber.eng.sun.com http://blogs.sun.com/barts You will contribute more with mercurial than with thunderbird. ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] images, bootenv, clone, snapshot..
Hi Harry, I would recommend that you let the tasks guide you rather than let the terminology confuse you, if that's possible. :-) For example, the beadm commands in the OpenSolaris release are built around some ZFS features such as snapshots and clones. These ZFS terms are defined here: http://docs.sun.com/app/docs/doc/817-2271/ftyue?a=view Also, check out this section on creating and promoting clones in the purely ZFS context: http://docs.sun.com/app/docs/doc/817-2271/gbcxz?a=view Then, you could contrast how these terms are used in the OpenSolaris environment: http://dlc.sun.com/osol/docs/content/2008.11/snapupgrade/gentextid-173.html However, to work with bootable environments using the beadm commands that rely on these ZFS features, you must use the correct beadm command to add, remove, or clone them. For example, you wouldn't want to use zfs destroy to remove a BE. You would use beadm destroy. You wouldn't use zfs promote to activate a BE, you would use beadm activate, and so on. I hope this helps... Cindy Harry Putnam wrote: Harry Putnam rea...@newsguy.com writes: Create a clone of the current environment and never touch it. Thanks for that reference to `copy on write (COW)'. This is my first brush with those concepts which I am finding good discussion of with google. I'll admit I don't fully understand it yet. But correct me if I have this wrong. The miss-named `clone', is not stand alone (Something one would expect from a `clone'). That is, it relies still on the parent if called into duty. Is that right? Could you move(mv) the clone to a new disc and boot it up? Or does the COW kick in during mv... I'm not clear what happens. BZT = wrong: Similar with the `snapshot'. It sounds like an OS frozen in time when the shutter snapped. But can you move it to a new disc and boot up? On further consideration I need to drop this about snapshot.. After all, applying the term to real photographic snapshots, one would never expect a real snapshot to have the capabilities of the subject of the snap. So poor analagy... deeply flawed. But what about `clone'? It seems my reasoning stands on that. ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] images, bootenv, clone, snapshot..
On Tue, Mar 10, 2009 at 02:38:31PM -0500, Harry Putnam wrote: Could you move(mv) the clone to a new disc and boot it up? Or does the COW kick in during mv... I'm not clear what happens. BZT = wrong: As others have answered this is all about ZFS, and much has been written elsewhere about ZFS. Suffice it to say that the COW stuff happens on every write to the ZFS pool, and that you can't separate (move) ZFS filesystems and snapshots from the pool they are in. Similar with the `snapshot'. It sounds like an OS frozen in time when the shutter snapped. But can you move it to a new disc and boot up? On further consideration I need to drop this about snapshot.. After all, applying the term to real photographic snapshots, one would never expect a real snapshot to have the capabilities of the subject of the snap. So poor analagy... deeply flawed. If you think of a filesystem as a movie and a snapshot as a single frame then the analogy works: the snapshot isn't of the things that appear in the movie, it's a snapshot of the _movie_ itself at a given point in time. And the TimeSlider (the Nautilus GUI for retrieving files from ZFS snapshots) analogy works too. But what about `clone'? It seems my reasoning stands on that. The word 'clone' doesn't seem to have much in relation to photography, but certainly works. I've got a snapshot of a filesystem, now I want a copy I can write to (ah, you need to know that ZFS snapshots are read-only -- you don't write to them, you clone them instead and write to the clones). Nico -- ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
[indiana-discuss] beadm destroy bug... what to do
In another thread I was told it was a known bug for beadm destroy to fail to destroy snapshots. At first I thought I didn't have the syntax right: beadm list -a (wrapped for mail) BE/Dataset/Snapshot Active Mountpoint Space Policy Created ---- -- - -- --- opensolaris-1 rpool/ROOT/opensolaris-1 NR / \ 4.82G static 2009-03-07 21:02 rpool/ROOT/opensolari...@2009-03-08-03:02:43 - - \ 183.26M static 2009-03-07 21:02 rpool/ROOT/opensolari...@install - - \ 74.67M static 2009-03-07 12:47 rpool/ROOT/opensolari...@osol-108_cifs - - \ 65.57M static 2009-03-09 02:35 [...] # beadm destroy rpool/ROOT/opensolari...@2009-03-08-03:02:43 The BE name provided is invalid. Please check it and try again. Is there anything I can do about this short of waiting for a new build? ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] beadm destroy bug... what to do
Harry Putnam wrote: In another thread I was told it was a known bug for beadm destroy to fail to destroy snapshots. At first I thought I didn't have the syntax right: beadm list -a (wrapped for mail) BE/Dataset/Snapshot Active Mountpoint Space Policy Created ---- -- - -- --- opensolaris-1 rpool/ROOT/opensolaris-1 NR / \ 4.82G static 2009-03-07 21:02 rpool/ROOT/opensolari...@2009-03-08-03:02:43 - - \ 183.26M static 2009-03-07 21:02 rpool/ROOT/opensolari...@install - - \ 74.67M static 2009-03-07 12:47 rpool/ROOT/opensolari...@osol-108_cifs - - \ 65.57M static 2009-03-09 02:35 [...] # beadm destroy rpool/ROOT/opensolari...@2009-03-08-03:02:43 The BE name provided is invalid. Please check it and try again. Is there anything I can do about this short of waiting for a new build? First, your argument there should just be the ben...@snapshot # beadm destroy opensolari...@2009-03-08-03:02:43 However, this is defect 7071, which isn't fixed until build 110. The workaround is to manually destroy the snapshot using zfs. # zfs destroy -r rpool/ROOT/opensolari...@2009-03-08-03:02:43 -ethan ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] Packaging issue: dependency between SUNWsshd and SUNWloc
Matthieu Boyer wrote: Hello and apologies if this isn't the appropriate list for this post. I ran into a packaging-related issue last week when upgrading an ipkg zone from 2008.11 to snv_108 from the dev repository. The problem manifested itself by a failure to ssh into the upgraded zone. I posted the details on security-discuss (here: http://www.opensolaris.org/jive/thread.jspa?threadID=96270 ) and it turns out that: a) The ssh daemon needs /usr/bin/locale to run properly. /usr/bin/locale is delivered within SUNWloc. b) In the world of SysV packages, that dependency is declared explicitly between SUNWsshdu and SUNWloc (http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/pkgdefs/SUNWsshdu/depend) c) As far as I can tell, that dependency isn't declared in the manifest for SUNWsshd. As I understand it, SUNWsshd replaces both SUNWsshdu and SUNWsshdr while also declaring them as legacy_pkg. I would like to know whether the dependency declared in the pkgdef for SUNWsshdu carries over into the SUNWsshd IPS package even though it's not explictly declared in SUNWsshd's manifest (http://pkg.opensolaris.org/dev/manifest/0/SUNWsshd%400.5.11%2C5.11-0.108%3A20090218T054853Z). As shown in the original post on security-discuss, I was able to create an ipkg local zone from a 2008.11 install that didn't include SUNWloc, so it doesn't look like it does. If it is indeed confirmed that there is currently no dependency in IPS between SUNWsshd and SUNWloc, could such a dependency be declared going forward? CR6432078 is relevant to this request. I'm really not sure how I managed to ssh into the local zone after it was created on 2008.11 with /usr/bin/locale missing, but I know that I couldn't ssh into my zone after I did 'pkg image-update' on its zbe owing to the absence of SUNWloc. I believe this is a rather serious issue and would appreciate some help from people familiar with the process of packaging OpenSolaris. This is a bug in the OpenSolaris distro 7158 Sun SSH daemon crashes if /usr/bin/locale isn't present This is of course actually two bugs - 1) the crash, and 2) a missing dependency. - Bart -- Bart Smaalders Solaris Kernel Performance ba...@cyber.eng.sun.com http://blogs.sun.com/barts You will contribute more with mercurial than with thunderbird. ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
[indiana-discuss] IPS distro-import changes needed for X packages for nv_110
These changes in the X packages in Nevada build 110 will need updates to the IPS distro-import package definitions for X. As usual, this only lists the changes that need distro-import changes, the full list of X changes in this build can be seen at: http://opensolaris.org/os/community/x_win/changelogs/changelogs-nv_100/#Build_109 (Mostly bugfixes or updates to non-redistributable packages in this build) -alan- * 6803790 Add Google Droid fonts - New SVR4 package SUNWttf-google-droid to import to IPS, no special handling should be needed. (Doesn't really have an upstream version number since they're taken from the Android mobile platform sources.) ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] IPS distro-import changes needed for X packages for nv_110
Alan Coopersmith wrote: These changes in the X packages in Nevada build 110 will need updates to the IPS distro-import package definitions for X. As usual, this only lists the changes that need distro-import changes, the full list of X changes in this build can be seen at: http://opensolaris.org/os/community/x_win/changelogs/changelogs-nv_100/#Build_109 Oops, forgot to update that URL from 109, should have been: http://opensolaris.org/os/community/x_win/changelogs/changelogs-nv_110/#Build_110 -- -Alan Coopersmith- alan.coopersm...@sun.com Sun Microsystems, Inc. - X Window System Engineering ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] Cannot install OpenSolaris snv108 on my SDHC
Hi Fajar I digged this case.I found my SDHCs were dead it couldn't fsck on my Mac and it couldn't format on my Windows sometimes.thanks you a lot for your advice:-)) And I found my USB stick Imation Nano couldn't mount as storage device. /var/adm/messages didn't say it was mounted as a storage device and said Device gone.. so I guess it couldn't use as LiveUSB for OpenSolaris installation to SDHC running as usb device. Regards, -masafumi On 2009/03/08, at 19:54, Fajar A. Nugraha wrote: On Sun, Mar 8, 2009 at 12:46 PM, Masafumi Ohta masafumi.o...@gmail.com wrote: but zpool status said the error (see attached files) That zpool status shows that your pool experience checksum errors. It MIGHT be that your SD card is bad, or your system is incompatible to use SD as boot device. My experince trying to get SD as boot device on multiple OS has been unsucsessfull due to a lot of factors : - on my current Acer Aspire One, SD controller is PCI. It has high throughput, but not BIOS-bootable. Ouch. - on my earlier eepc 2G, SD controller is connected via USB (is it the same thing with your 901?). It's bootable, but throughput is dead slow (compared to the same card attached to my Aspire One). This means Windows is no-no because performance is simply not acceptable. - using Linux with squashfs on eepc SD increased the performance somewhat to an acceptable level (due to I/O need reduced). I had to gave up on that as well though, because after several hours the SD card overheated, and Linux shows lots of disk errors that it remounts the filesystem read-only. The same condition (overheat) MIGHT be what's causing zfs checksum errors on your setup. If that is the case, then your SD is not suitable as boot device for any OS. Regards, Fajar ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
