[indiana-discuss] FF3 freezes with build 95.. Can we install FF2 , will it work ?
Hi Seems that if users have lot of live RSS feeds within their bookmark, then Firefox 3 freezes regularly. This seems to be a known issue and fix for this might not come in until 3.0.3 or above . Thought, other users running into this 'frequent freeze' might be interested in this. http://forums.mozillazine.org/viewtopic.php?f=38t=736555start=15 Now, in this context, is it okay to install FF2 from IPS repository while using build 95 ? For example, can I do some thing like below ? Is there any dependency or issues that I need to be aware of ? pfexec pkg refresh pfexec pkg uninstall SUNWfirefox pfexec pkg install pkg:/[EMAIL PROTECTED],5.11-0.86 - Sriram ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] [desktop-discuss] 2008.11 UI Spec
Hi Calum, The current tooltip for gok is Type and navigate applications using alternative input devices and the suggested one in the UI spec is Navigate applications and type using alternative input devices. The only change is reordering. Is this really what we want? Regards, Jedy ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] [desktop-discuss] 2008.11 UI Spec
Hi Calum, Why we want to change GIMP Image Editor to Image Editor when we change Move Player to Totem Movie Player with an internal patch. To show or not to show applications' own branding/name seems an issue would be brought up once in a while, but my own humble, little, tiny $0.02 is that I prefer to see the names of applications instead of a general description like Browse Internet or Movie Player or Image Editor For one reason I think it's sorta salute to the application and author(s) behind it. another is that I feel better if I know what to be launched before any icon/button is clicked rather than after. My $0.02 anyway. Ivan. I also do not think Play movies and music is better than Play movies and songs. Regards, Jedy ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-d iscuss -- 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] [desktop-discuss] 2008.11 UI Spec
On Thu, 2008-08-21 at 01:16 -0700, Ivan Wang wrote: Hi Calum, Why we want to change GIMP Image Editor to Image Editor when we change Move Player to Totem Movie Player with an internal patch. To show or not to show applications' own branding/name seems an issue would be brought up once in a while, but my own humble, little, tiny $0.02 is that I prefer to see the names of applications instead of a general description like Browse Internet or Movie Player or Image Editor I am OK with both to show or not to show the application's name. but I think if we decide to not show the application's name, we should keep consistent. Regards, Jedy For one reason I think it's sorta salute to the application and author(s) behind it. another is that I feel better if I know what to be launched before any icon/button is clicked rather than after. My $0.02 anyway. Ivan. I also do not think Play movies and music is better than Play movies and songs. Regards, Jedy ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-d iscuss -- This message posted from opensolaris.org ___ 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] FF3 freezes with build 95.. Can we install FF2 , will it work ?
Hi Sriram, just give it a try :-) Looking forward to your experiences. I also like to go back to FF2 on my test env w/ b95. This question was asked on desktop-discuss due to some FF3 annoyances. Those got fixed (for me) but the question of downgrading was unanswered. -best Frank -- 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] [Fwd: beadm: Unable to activate opensolaris-x (build 95)]
andrew wrote: Booting a ZFS pool from an EFI labelled disk has never been supported. I suspect they have just added checking for an EFI labelled disk in a recent build of beadm. Can you possibly post the output of these commands: fdisk /dev/rdsk/c5t0d0p0 fdisk /dev/rdsk/c5t1d0s0 t0 shows Partition StatusType Start End Length% = == = === == === 1 ActiveSolaris2 1 3039930399100 t1 shows Partition StatusType Start End Length% = == = === == === 1 EFI 0 3040030401100 Obviously when I added the second disk, it created it with an EFI label. I don't remember making any such decision, I think it's done this as a default action. I suspect what you have is an SMI labelled disk (c5t0d0) and an EFI labelled disk (c5t1d0). How did you add the second disk to the root pool? I think you're spot on. I just did `zpool attach rpool device'. Seems like it's worked before just by chance. (Bootadm should be printing the reason for the failure. Users should not be expected to activate secret debugging options just to find out why a command failed). Absolutely. I half remembered this discussion, and went looking for the magic environment variable without success. (Once I saw the error message, I also went googling, but couldn't spot the discussion, now it's been confirmed I'll go looking again.) I'm tempted to just detach the device, try the activate, reboot into the new system, fdisk the second device by hand, and re-attach. Like I say, it's only a workstation, not a production machine. Rob -- E-Mail: [EMAIL PROTECTED] PHONE: +44 24 7652 3037 Rob McMahon, IT Services, Warwick University, Coventry, CV4 7AL, England ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] [desktop-discuss] 2008.11 UI Spec
On 21 Aug 2008, at 07:59, Jedy Wang wrote: Hi Calum, Why we want to change GIMP Image Editor to Image Editor when we change Move Player to Totem Movie Player with an internal patch. It's a very good question :) FWIW, the reason we change Movie Player - Totem Movie Player is that, at one time, we had three media players on the JDS menus: Totem, Java Media Player and Real Player. So the Totem change was just to help users tell them apart. Of course, that doesn't apply to OpenSolaris, and in Nevada, it's less of a problem now that JMP is gone from the menus. But Songbird seems to be very popular now, and we may even install it by default at some point. So the Totem patch is probably still useful. For GIMP, I suggested the change just because we have no other image editors on the menus for users to be confused with. When that's the case, we prefer to show only the functional name on the menus. (I'm not even sure if there are any other 'image editors' for Solaris that users might want to install themselves, that would need to be distinguished from GIMP.) (FWIW, gimp is also an American slang word for a handicapped person, so it's potentially a slightly offensive term to some people. But given how popular the GIMP project has become without any major complaints about the name, that's only a very small concern... and anyone who runs the application will immediately be shown a GIMP splash screen anyway.) So anyway, that's the reason :) I agree this is a low priority change. If there are more important things you need to be doing to get the UI spec implemented, or if you think we're already generating too many trivial patches for menu changes, I'd be happy enough not to make this change for GIMP. I also do not think Play movies and music is better than Play movies and songs. It's certainly not worth changing, if that would be the only change we were making to that desktop file. I suggested it only because the GNOME docs team tends to prefer the term Music to Songs-- not all music files are songs. (Nor are all audio files music, of course, but there isn't really any good generic, non-technical term for audio files, or we'd use that instead.) Of course, we now also have a Music folder in GNOME by default, which reinforces the use of that term. Cheeri, Calum. -- CALUM BENSON, Usability Engineer Sun Microsystems Ireland mailto:[EMAIL PROTECTED]GNOME Desktop Team http://blogs.sun.com/calum +353 1 819 9771 Any opinions are personal and not necessarily those of Sun Microsystems ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] [desktop-discuss] 2008.11 UI Spec
On 21 Aug 2008, at 09:08, Jedy Wang wrote: Hi Calum, The current tooltip for gok is Type and navigate applications using alternative input devices and the suggested one in the UI spec is Navigate applications and type using alternative input devices. The only change is reordering. Is this really what we want? I re-ordered it because the original wording just doesn't read very well, in English-- it suggests that gok helps you type applications and navigate applications. But obviously, type applications doesn't make sense. T he correct punctuation without re-ordering would be Type, and navigate applications, using alternate input devices, but that also reads a bit clumsily for a tooltip. However, I suggest you don't bother making this change for now. I've cc'ed Willie Walker-- perhaps he can make this change in GOK upstream for us, and we'll just pick it up when it's done :) Thanks, Calum. -- CALUM BENSON, Usability Engineer Sun Microsystems Ireland mailto:[EMAIL PROTECTED]GNOME Desktop Team http://blogs.sun.com/calum +353 1 819 9771 Any opinions are personal and not necessarily those of Sun Microsystems ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] [desktop-discuss] 2008.11 UI Spec
Here you go! I know the GOK maintainer well, and will prod him to get to this: http://bugzilla.gnome.org/show_bug.cgi?id=548859 If he doesn't do it, and I remember, I'll commit it with his permission. Will On Thu, 2008-08-21 at 13:57 +0100, Calum Benson wrote: On 21 Aug 2008, at 09:08, Jedy Wang wrote: Hi Calum, The current tooltip for gok is Type and navigate applications using alternative input devices and the suggested one in the UI spec is Navigate applications and type using alternative input devices. The only change is reordering. Is this really what we want? I re-ordered it because the original wording just doesn't read very well, in English-- it suggests that gok helps you type applications and navigate applications. But obviously, type applications doesn't make sense. T he correct punctuation without re-ordering would be Type, and navigate applications, using alternate input devices, but that also reads a bit clumsily for a tooltip. However, I suggest you don't bother making this change for now. I've cc'ed Willie Walker-- perhaps he can make this change in GOK upstream for us, and we'll just pick it up when it's done :) Thanks, Calum. ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] http://pkg.opensolaris.org/ package repository update (build 95)
On 20 Aug 2008, at 23:11, Dave Miner wrote: Chris Ridd wrote: On 18 Aug 2008, at 18:31, Dave Miner wrote: David Orman wrote: Hi, When attempting to download via the torrent: [00:11:36] Error regarding osol-0811-95-global.iso: rejected by tracker - Torrent unauthorised [00:11:36] rejected by tracker - Torrent unauthorised Anybody else having any luck? Seems to have been corrected now, but please follow up if you're still seeing problems there. I see Al pointed out the genunix mirror, and we're going to try to coordinate more closely on future image releases. Dave, I am still getting torrent unauthorised from the tracker on 16969, and Unknown error (0) from the tracker on 6969. Apologies if I've got the terminology wrong, but it basically still won't let me share. It's working for me at the moment, I'm wondering if we're having some intermittent tracker failures. Well I downloaded the torrent again, and now I do not get the authorisation error when I try to reconnect afterwards. Did the torrent change at all? Cheers, Chris ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] update from b86 to b95: unable to update grub
Hello Gerard, What does the command zpool status show you? It appears that update_grub thinks that /dev/dsk/c5t1d0s0 is attached to the root pool as part of a mirror and it's that device that looks like it's getting all the errors. What does fdisk show for /dev/dsk/c5t1d0s0? It would also be helpful to see what zfs list shows. -evan [EMAIL PROTECTED] wrote: hello all, 200805 b86 is installed on a sun ultra 20, with two disks mirrored. I've got this error: -bash-3.2# pfexec /mnt/boot/solaris/bin/update_grub -R /mnt Creating GRUB menu in /mnt bootadm: failed to determine fdisk partition: /dev/dsk/c5t1d0s0 bootadm: is_bootdisk(): cannot determine BIOS disk ID 'hd?' for disk: /dev/dsk/c5t1d0s0 Installing grub on /dev/rdsk/c5t0d0s0 stage1 written to partition 0 sector 0 (abs 16065) stage2 written to partition 0, 266 sectors starting at 50 (abs 16115) Creating GRUB menu in /mnt bootadm: failed to determine fdisk partition: /dev/rdsk/c5t1d0s0 bootadm: failed to get grubsign for root: /mnt, device /dev/rdsk/c5t1d0s0 Installing grub on /dev/rdsk/c5t1d0s0 cannot open/stat device /dev/rdsk/c5t1d0s2 the disks are: 0. c5t0d0 DEFAULT cyl 9726 alt 2 hd 255 sec 63 /[EMAIL PROTECTED],0/pci108e,[EMAIL PROTECTED]/[EMAIL PROTECTED],0 1. c5t1d0 ATA-ST380815AS-B-74.53GB /[EMAIL PROTECTED],0/pci108e,[EMAIL PROTECTED]/[EMAIL PROTECTED],0 /dev/dsk/c5t0d0s0 is part of active ZFS pool rpool. Please see zpool(1M). /dev/dsk/c5t0d0s1 is currently used by swap. Please see swap(1M). Part TagFlag CylindersSizeBlocks 0 rootwm 262 - 9725 72.50GB(9464/0/0) 152039160 1 swapwu 1 - 2612.00GB(261/0/0)4192965 2 backupwu 0 - 9725 74.50GB(9726/0/0) 156248190 -bash-3.2# bootadm list-menu -R /mnt The location for the active GRUB menu is: /mnt/boot/grub/menu.lst bootadm: no matching entry found -bash-3.2# bootadm list-menu The location for the active GRUB menu is: /boot/grub/menu.lst bootadm: no matching entry found but the machine correctly boot the actual BE: -bash-3.2# beadm list BEActive Active on Mountpoint Space Name reboot Used -- - -- - opensolaris-2 no nolegacy 2.12G opensolaris-1 yesyes legacy 4.22G opensolaris no no- 8.40M -bash-3.2# /sbin/biosdev 0x80 /[EMAIL PROTECTED],0/pci108e,[EMAIL PROTECTED]/[EMAIL PROTECTED],0 0x81 /[EMAIL PROTECTED],0/pci108e,[EMAIL PROTECTED]/[EMAIL PROTECTED],0 What's the problem? Is there a way to verify if grub is correctly installed? thanks in advance for help, gerard ___ 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] update from b86 to b95: unable to update grub
Evan Layton wrote: Hello Gerard, What does the command zpool status show you? It appears that update_grub thinks that /dev/dsk/c5t1d0s0 is attached to the root pool as part of a mirror and it's that device that looks like it's getting all the errors. What does fdisk show for /dev/dsk/c5t1d0s0? It would also be helpful to see what zfs list shows. here are the infos: -bash-3.2# zpool status pool: rpool state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror ONLINE 0 0 0 c5t0d0s0 ONLINE 0 0 0 c5t1d0s0 ONLINE 0 0 0 errors: No known data errors -bash-3.2# format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c5t0d0 DEFAULT cyl 9726 alt 2 hd 255 sec 63 /[EMAIL PROTECTED],0/pci108e,[EMAIL PROTECTED]/[EMAIL PROTECTED],0 1. c5t1d0 ATA-ST380815AS-B-74.53GB /[EMAIL PROTECTED],0/pci108e,[EMAIL PROTECTED]/[EMAIL PROTECTED],0 selecting c5t0d0 [disk formatted] /dev/dsk/c5t0d0s0 is part of active ZFS pool rpool. Please see zpool(1M). /dev/dsk/c5t0d0s1 is currently used by swap. Please see swap(1M). partition p Current partition table (original): Total disk cylinders available: 9726 + 2 (reserved cylinders) Part TagFlag CylindersSizeBlocks 0 rootwm 262 - 9725 72.50GB(9464/0/0) 152039160 1 swapwu 1 - 2612.00GB(261/0/0)4192965 2 backupwu 0 - 9725 74.50GB(9726/0/0) 156248190 3 unassignedwm 0 0 (0/0/0)0 4 unassignedwm 0 0 (0/0/0)0 5 unassignedwm 0 0 (0/0/0)0 6 unassignedwm 0 0 (0/0/0)0 7 unassignedwm 0 0 (0/0/0)0 8 bootwu 0 -07.84MB(1/0/0)16065 9 unassignedwm 0 0 (0/0/0)0 Specify disk (enter its number): 1 selecting c5t1d0 [disk formatted] /dev/dsk/c5t1d0s0 is part of active ZFS pool rpool. Please see zpool(1M). partition p Current partition table (original): Total disk sectors available: 156285070 + 16384 (reserved sectors) Part TagFlag First Sector Size Last Sector 0usrwm 256 74.52GB 156285070 1 unassignedwm 0 0 0 2 unassignedwm 0 0 0 3 unassignedwm 0 0 0 4 unassignedwm 0 0 0 5 unassignedwm 0 0 0 6 unassignedwm 0 0 0 8 reservedwm 1562850718.00MB 156301454 it seems that the second doesn't contains the same inforamtion than the first one. The mirror was created at indiana installation. -bash-3.2# zfs list NAMEUSED AVAIL REFER MOUNTPOINT rpool 45.9G 25.0G 60K /rpool [EMAIL PROTECTED] 19.5K - 55K - rpool/ROOT 6.43G 25.0G 18K /rpool/ROOT rpool/[EMAIL PROTECTED] 0 - 18K - rpool/ROOT/opensolaris 8.40M 25.0G 2.75G legacy rpool/ROOT/opensolaris-1 4.29G 25.0G 2.92G legacy rpool/ROOT/[EMAIL PROTECTED] 59.9M - 2.22G - rpool/ROOT/[EMAIL PROTECTED]:-:2008-05-30-05:29:40 406M - 2.75G - rpool/ROOT/[EMAIL PROTECTED]:-:2008-08-20-12:06:34 165M - 2.64G - rpool/ROOT/opensolaris-1/opt709M 25.0G 709M /opt rpool/ROOT/opensolaris-1/[EMAIL PROTECTED] 72K - 3.60M - rpool/ROOT/opensolaris-1/[EMAIL PROTECTED]:-:2008-05-30-05:29:4038K - 595M - rpool/ROOT/opensolaris-1/[EMAIL PROTECTED]:-:2008-08-20-12:06:34 0 - 709M - rpool/ROOT/opensolaris-2 2.12G 25.0G 3.01G legacy rpool/ROOT/opensolaris-2/opt 32K 25.0G 709M /opt rpool/ROOT/opensolaris/opt 79K 25.0G 595M /opt AVAILABLE DISK SELECTIONS: 0. c5t0d0 DEFAULT cyl 9726 alt 2 hd 255 sec 63 /[EMAIL PROTECTED],0/pci108e,[EMAIL PROTECTED]/[EMAIL PROTECTED],0 1. c5t1d0 ATA-ST380815AS-B-74.53GB /[EMAIL PROTECTED],0/pci108e,[EMAIL PROTECTED]/[EMAIL
Re: [indiana-discuss] http://pkg.opensolaris.org/ package repository update (build 95)
Chris Ridd wrote: On 20 Aug 2008, at 23:11, Dave Miner wrote: Chris Ridd wrote: On 18 Aug 2008, at 18:31, Dave Miner wrote: David Orman wrote: Hi, When attempting to download via the torrent: [00:11:36] Error regarding osol-0811-95-global.iso: rejected by tracker - Torrent unauthorised [00:11:36] rejected by tracker - Torrent unauthorised Anybody else having any luck? Seems to have been corrected now, but please follow up if you're still seeing problems there. I see Al pointed out the genunix mirror, and we're going to try to coordinate more closely on future image releases. Dave, I am still getting torrent unauthorised from the tracker on 16969, and Unknown error (0) from the tracker on 6969. Apologies if I've got the terminology wrong, but it basically still won't let me share. It's working for me at the moment, I'm wondering if we're having some intermittent tracker failures. Well I downloaded the torrent again, and now I do not get the authorisation error when I try to reconnect afterwards. Did the torrent change at all? I checked with the operations people, nothing showed up in the logs, but they'll turn up the logging to see if we can catch anything should problems recur. Dave ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] update from b86 to b95: unable to update grub
[EMAIL PROTECTED] wrote: Evan Layton wrote: Hello Gerard, What does the command zpool status show you? It appears that update_grub thinks that /dev/dsk/c5t1d0s0 is attached to the root pool as part of a mirror and it's that device that looks like it's getting all the errors. What does fdisk show for /dev/dsk/c5t1d0s0? It would also be helpful to see what zfs list shows. here are the infos: -bash-3.2# zpool status pool: rpool state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror ONLINE 0 0 0 c5t0d0s0 ONLINE 0 0 0 c5t1d0s0 ONLINE 0 0 0 errors: No known data errors -bash-3.2# format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c5t0d0 DEFAULT cyl 9726 alt 2 hd 255 sec 63 /[EMAIL PROTECTED],0/pci108e,[EMAIL PROTECTED]/[EMAIL PROTECTED],0 1. c5t1d0 ATA-ST380815AS-B-74.53GB /[EMAIL PROTECTED],0/pci108e,[EMAIL PROTECTED]/[EMAIL PROTECTED],0 selecting c5t0d0 [disk formatted] /dev/dsk/c5t0d0s0 is part of active ZFS pool rpool. Please see zpool(1M). /dev/dsk/c5t0d0s1 is currently used by swap. Please see swap(1M). partition p Current partition table (original): Total disk cylinders available: 9726 + 2 (reserved cylinders) Part TagFlag CylindersSizeBlocks 0 rootwm 262 - 9725 72.50GB(9464/0/0) 152039160 1 swapwu 1 - 2612.00GB(261/0/0)4192965 2 backupwu 0 - 9725 74.50GB(9726/0/0) 156248190 3 unassignedwm 0 0 (0/0/0)0 4 unassignedwm 0 0 (0/0/0)0 5 unassignedwm 0 0 (0/0/0)0 6 unassignedwm 0 0 (0/0/0)0 7 unassignedwm 0 0 (0/0/0)0 8 bootwu 0 -07.84MB(1/0/0)16065 9 unassignedwm 0 0 (0/0/0)0 Specify disk (enter its number): 1 selecting c5t1d0 [disk formatted] /dev/dsk/c5t1d0s0 is part of active ZFS pool rpool. Please see zpool(1M). partition p Current partition table (original): Total disk sectors available: 156285070 + 16384 (reserved sectors) Part TagFlag First Sector Size Last Sector 0usrwm 256 74.52GB 156285070 1 unassignedwm 0 0 0 2 unassignedwm 0 0 0 3 unassignedwm 0 0 0 4 unassignedwm 0 0 0 5 unassignedwm 0 0 0 6 unassignedwm 0 0 0 8 reservedwm 1562850718.00MB 156301454 it seems that the second doesn't contains the same inforamtion than the first one. The mirror was created at indiana installation. The OpenSolaris installer is not capable of creating the mirror at install time. The mirror had to have been created my hand after the installation with a zfs attach command. It appears that there may be a problem with the way ZFS did the attach when this was first created and several others have seen similar issues (along with the fdisk partition being set to EFI). -bash-3.2# zfs list NAMEUSED AVAIL REFER MOUNTPOINT rpool 45.9G 25.0G 60K /rpool [EMAIL PROTECTED] 19.5K - 55K - rpool/ROOT 6.43G 25.0G 18K /rpool/ROOT rpool/[EMAIL PROTECTED] 0 - 18K - rpool/ROOT/opensolaris 8.40M 25.0G 2.75G legacy rpool/ROOT/opensolaris-1 4.29G 25.0G 2.92G legacy rpool/ROOT/[EMAIL PROTECTED] 59.9M - 2.22G - rpool/ROOT/[EMAIL PROTECTED]:-:2008-05-30-05:29:40 406M - 2.75G - rpool/ROOT/[EMAIL PROTECTED]:-:2008-08-20-12:06:34 165M - 2.64G - rpool/ROOT/opensolaris-1/opt709M 25.0G 709M /opt rpool/ROOT/opensolaris-1/[EMAIL PROTECTED] 72K - 3.60M - rpool/ROOT/opensolaris-1/[EMAIL PROTECTED]:-:2008-05-30-05:29:4038K - 595M - rpool/ROOT/opensolaris-1/[EMAIL PROTECTED]:-:2008-08-20-12:06:34 0 - 709M - rpool/ROOT/opensolaris-2
Re: [indiana-discuss] I need a little info about this distro
On 18 Aug 2008, at 01:08, Willie Walker wrote: Darnyou're right about both the menu and run application keystrokes. I use them both all the time, and I'm perpetually confused because I constantly switch between Ubuntu and OpenSolaris. GNOME supports multiple keybindings for these commands, we should be binding both Super+R AND Alt+F2 to the Run dialog. (It was Sun who requested the feature, precisely so we could do this!) I'll add that (and the others we remap) to the Indiana UI Spec... hopefully we can sneak it in for 2008.11. Cheeri, Calum. -- CALUM BENSON, Usability Engineer Sun Microsystems Ireland mailto:[EMAIL PROTECTED]GNOME Desktop Team http://blogs.sun.com/calum +353 1 819 9771 Any opinions are personal and not necessarily those of Sun Microsystems ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] [sysadmin-discuss] /dev/null disappeared and unable to recreate it
Francois, I'm reposting this on indiana-discuss to see if anyone on that list can provide some input. Is this happening during a netinstall? Can you provide the output of ls -l /dev/null? Cindy François Feugeas wrote: Hello, We're having a strange issue on one of our OpenSolaris 64bit installs. For some unknown reason, /dev/null disappeared. We tried to reboot but it didn't help. We're running SNV93. /devices/pseudo/[EMAIL PROTECTED]:null does exist and permissions are correct : # ls -l /devices/pseudo/[EMAIL PROTECTED]:null crw-rw-rw- 1 root sys 13, 2 août 21 15:59 /devices/pseudo/[EMAIL PROTECTED]:null devfsadm and devfsadm -P fail : # devfsadm -V chatty | grep null devfsadm: cannot create link: /dev/null - ../devices/pseudo/[EMAIL PROTECTED]:null. max attempts exceeded devfsadm[2456]: chatty: minor_process: node=mm, minor=null devfsadm[2456]: chatty: reset_node_permissions: phy_path=/devices/pseudo/[EMAIL PROTECTED]:null lphy_path=/pseudo/[EMAIL PROTECTED]:null /dev is writable by root and I can create files or symlinks into it, as long as they're not named, you guessed it, null. I didn't find any reference to that particular issue. Has anyone encountered that issue already ? This message posted from opensolaris.org ___ sysadmin-discuss mailing list [EMAIL PROTECTED] http://mail.opensolaris.org/mailman/listinfo/sysadmin-discuss ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] [sysadmin-discuss] /dev/null disappeared and unable to recreate it
Hi, Looks like the devname filesystem is confused. DO the following 1. Use ln -s to create /dev/null manually # ln -s ../devices/pseudo/[EMAIL PROTECTED]:null/dev/null 2. Do a reboot -d to generate a kernel core file 3. File a bug and attach core file to bug report. The system should come up normally after a reboot. BTW, mention the exact conditions when this problem happened (was it normal boot or install boot - did you do anything in /dev etc.) Vikram - Original Message From: [EMAIL PROTECTED] [EMAIL PROTECTED] To: François Feugeas [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; indiana-discuss@opensolaris.org Sent: Thursday, August 21, 2008 1:10:48 PM Subject: Re: [indiana-discuss] [sysadmin-discuss] /dev/null disappeared and unable to recreate it Francois, I'm reposting this on indiana-discuss to see if anyone on that list can provide some input. Is this happening during a netinstall? Can you provide the output of ls -l /dev/null? Cindy François Feugeas wrote: Hello, We're having a strange issue on one of our OpenSolaris 64bit installs. For some unknown reason, /dev/null disappeared. We tried to reboot but it didn't help. We're running SNV93. /devices/pseudo/[EMAIL PROTECTED]:null does exist and permissions are correct : # ls -l /devices/pseudo/[EMAIL PROTECTED]:null crw-rw-rw- 1 root sys 13, 2 août 21 15:59 /devices/pseudo/[EMAIL PROTECTED]:null devfsadm and devfsadm -P fail : # devfsadm -V chatty | grep null devfsadm: cannot create link: /dev/null - ../devices/pseudo/[EMAIL PROTECTED]:null. max attempts exceeded devfsadm[2456]: chatty: minor_process: node=mm, minor=null devfsadm[2456]: chatty: reset_node_permissions: phy_path=/devices/pseudo/[EMAIL PROTECTED]:null lphy_path=/pseudo/[EMAIL PROTECTED]:null /dev is writable by root and I can create files or symlinks into it, as long as they're not named, you guessed it, null. I didn't find any reference to that particular issue. Has anyone encountered that issue already ? This message posted from opensolaris.org ___ sysadmin-discuss mailing list [EMAIL PROTECTED] http://mail.opensolaris.org/mailman/listinfo/sysadmin-discuss ___ 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] [sysadmin-discuss] /dev/null disappeared and unable to recreate it
Hi, ok in that case you will have to take the risk of rebooting without creating /dev/null. Do a reboot -d to create a core dump file and reboot. If you have problems on reboot due to missing /dev/null, boot the Live CD, mount the hard disk and create /dev/null via ln. That should succeed as you are then operating outside devname filesystem Vikram - Original Message From: François Feugeas [EMAIL PROTECTED] To: Vikram Hegde [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; indiana-discuss@opensolaris.org Sent: Thursday, August 21, 2008 2:05:20 PM Subject: Re: [indiana-discuss] [sysadmin-discuss] /dev/null disappeared and unable to recreate it Hello, I weren't clear the first time, but this issue is encountered on a system that has been running perfectly for a few weeks (and not during an install). Nothing special happened on that system, though OpenSSH (which we use on that system in replacement of SunSSH) crashed on us 10 minutes before we noticed /dev/null went missing. Maybe one issue caused the other. Nothing was done under /dev. As stated earlier, I am not able to create *anything* named null under /dev/ : # ln -s ../devices/pseudo/[EMAIL PROTECTED]:null/dev/null ln: cannot create /dev/null: No such file or directory # touch /dev/null touch: /dev/null cannot create touch /dev/anything succeeds, though Best regards, François Feugeas - Original Message From: [EMAIL PROTECTED] [EMAIL PROTECTED] To: François Feugeas [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; indiana-discuss@opensolaris.org Sent: Thursday, August 21, 2008 1:10:48 PM Subject: Re: [indiana-discuss] [sysadmin-discuss] /dev/null disappeared and unable to recreate it Francois, I'm reposting this on indiana-discuss to see if anyone on that list can provide some input. Is this happening during a netinstall? Can you provide the output of ls -l /dev/null? Cindy François Feugeas wrote: Hello, We're having a strange issue on one of our OpenSolaris 64bit installs. For some unknown reason, /dev/null disappeared. We tried to reboot but it didn't help. We're running SNV93. /devices/pseudo/[EMAIL PROTECTED]:null does exist and permissions are correct : # ls -l /devices/pseudo/[EMAIL PROTECTED]:null crw-rw-rw- 1 rootsys 13, 2 août 21 15:59 /devices/pseudo/[EMAIL PROTECTED]:null devfsadm and devfsadm -P fail : # devfsadm -V chatty | grep null devfsadm: cannot create link: /dev/null - ../devices/pseudo/[EMAIL PROTECTED]:null. max attempts exceeded devfsadm[2456]: chatty: minor_process: node=mm, minor=null devfsadm[2456]: chatty: reset_node_permissions: phy_path=/devices/pseudo/[EMAIL PROTECTED]:null lphy_path=/pseudo/[EMAIL PROTECTED]:null /dev is writable by root and I can create files or symlinks into it, as long as they're not named, you guessed it, null. I didn't find any reference to that particular issue. Has anyone encountered that issue already ? This message posted from opensolaris.org http://opensolaris.org ___ sysadmin-discuss mailing list [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] http://mail.opensolaris.org/mailman/listinfo/sysadmin-discuss ___ indiana-discuss mailing list indiana-discuss@opensolaris.org mailto:indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss -- François Feugeas Directeur technique Oxileo Micro tél. : +33.8 20 48 02 50 port. : +33.6 28 05 53 50 -- Société Oxileo Siège Social : 9, rue du Gué, F-92500 Rueil Malmaison RCS Nanterre B 483 520 375 - Forme Sociale : S.A.S. Capital Social : 40 000 E - SIREN/SIRET : 483 520 375 00013 -- Ce message électronique constitue, avec ses pièces jointes, une correspondance confidentielle exclusivement réservée à son ou ses destinataires désignés. Les vues et opinions exprimées dans ce message ne reflètent pas nécessairement les vues ou opinions de la société Oxileo. Compte tenu de la nature du réseau Internet, Oxileo n'est pas en mesure de garantir l'authenticité ni l'intégrité de cette correspondance qui ne peut par conséquent pas l'engager ni lui être opposée. Si vous n'êtes pas destinataire de ce message, il vous est rappelé que toute utilisation, divulgation ou reproduction de ce message ou de son contenu est strictement interdite. Si vous avez reçu ce message par erreur, veuillez nous avertir aussitôt par courrier électronique et le supprimer de votre messagerie. Merci.___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] Choice of text Editor
nano + vim is the way to go. Removing VIM would be a very bad idea, as a lot of people (myself included) cannot live without it, and it (or vi) are almost always expected to be available. Nano is a good, easy to use, editor for those new to unix. If emacs was possible, I'd say include it too. Maybe a stripped down version? (Not an emacs user, don't know much about it, sorry...) David On Tue, Jun 24, 2008 at 8:22 PM, Paul Harper [EMAIL PROTECTED] wrote: I started with pine too at uni. If there is space on the cd perhaps a good compromise would be to include nano or pico and vim. -- This message posted from opensolaris.org ___ 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] [Fwd: beadm: Unable to activate opensolaris-x (build 95)]
t0 shows Partition StatusType Start End Length% = == = === == === 1 ActiveSolaris2 1 30399 30399100 hows Partition StatusType Start End Length% = == = === == === 1 EFI 0 30400 30401100 ously when I added the second disk, it created it with an EFI label. I don't remember making any such decision, I think it's done this as a default action. I suspect what you have is an SMI labelled disk (c5t0d0) and an EFI labelled disk (c5t1d0). How did you add the second disk to the root pool? I think you're spot on. I just did `zpool attach rpool device'. Seems like it's worked before just by chance. (Bootadm should be printing the reason for the failure. Users should not be expected to activate secret debugging options just to find out why a command failed). Absolutely. I half remembered this discussion, and went looking for the magic environment variable without success. (Once I saw the error message, I also went googling, but couldn't spot the discussion, now it's been confirmed I'll go looking again.) I'm tempted to just detach the device, try the activate, reboot into the new system, fdisk the second device by hand, and re-attach. Like I say, it's only a workstation, not a production machine. That;s probably what I would have done as well, unfortunately it seems that this won't quite work - here is the safe way of removing the EFI-labelled disk posted by evanl above: I would follow the instructions Dan Price sent out last week: If you want to remove an EFI labelled disk from your root pool, my advice to you would be to do the following. Note that I have not tested this particular sequence, but I think it will work. Hah. 0) Backup your data and settings. 1) 'zpool detach' the EFI labelled disk from your pool. After you do this YOU MUST NOT REBOOT. Your system is now in a fragile state. 2) Run 'zpool status' to ensure that your pool now has one disk. 3) Edit /etc/boot/solaris/filelist.ramdisk. Remove the only line in the file: etc/zfs/zpool.cache 4) Delete /platform/i86pc/boot_archive and /platform/i86pc/amd64/boot_archive 5) Run 'bootadm update-archive' -- This rebuilds the boot archive, omitting the zpool.cache file. It may also be necessary to do installgrub at this point. Probably, and it wouldn't hurt. 6) Reboot your system, to ensure that you have a working configuration. I hope this helps... -evan Once you've done that you should be OK to manually create the fdisk partition then the required slices within in on the second disk. Cheers Andrew. -- 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] Choice of text Editor
I have since discovered [b]pfexec gedit /foo/bar[/b] It is a lot easier than pointing newcomers who want thier internet to work at man vi I know that Dave Miner is trying to put OS200811 on a diet to keep the iso size down. So keeping vim and letting people know about [b]pfexec gedit'[/b] may be the way forward. -- This message posted from opensolaris.org ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
