OpenSolaris

Discussions Communities Projects Download Source Browser

Home » OpenSolaris Forums » indiana » discuss

Thread: Revised instructions for updating from http://pkg.opensolaris.org/

Welcome, Guest Help
Login Login
Guest Settings Guest Settings
Reply to this Thread Reply to this Thread Search Forum Search Forum Back to Thread List Back to Thread List

Permlink Replies: 21 - Last Post: Oct 6, 2008 1:45 PM by: khb
comay

Posts: 962
From: US

Registered: 3/9/05
Revised instructions for updating from http://pkg.opensolaris.org/
Posted: Jul 14, 2008 11:03 PM

  Click to reply to this thread Reply

Enclosed below are revised instructions for using "pkg image-update" to
update to the latest OpenSolaris development builds via
http://pkg.opensolaris.org/

For more information on this command and the Image Packaging System
(IPS) technology, refer to the pkg(1), beadm(1M) and pkg(5) manual
pages and the following documents

Getting Started With the Image Packaging System
http://dlc.sun.com/osol/docs/content/IPS/ggcph.html

Upgrading and Managing Your Boot Environments
http://dlc.sun.com/osol/docs/content/IPS/snap3.html

General instructions for updating to the latest OpenSolaris development build
=============================================================================
1) Before using the "image-update" subcommand, it is recommended that
the latest available version of the IPS software be installed for your
current boot environment (BE)

$ BUILD=`uname -v | sed s/snv_//`
$ pfexec pkg refresh
$ pfexec pkg install SUNWipkg@0.5.11-0.$BUILD
$ pfexec pkg install entire@0.5.11-0.$BUILD

2) Verify the build of OpenSolaris in the current BE

$ echo $BUILD

3) If you are running build 93 or greater, you can use "image-update"
directly as follows

$ pfexec pkg image-update

At this point, you can boot into the updated BE using reboot(1M) or
init(1M) as usual.

4) If you are using a build prior to 93, it is recommended one apply
the update directly to an alternate BE in order to work-around

2387 libbe.so:beCopy() frees nvlist variables before using them
http://defect.opensolaris.org/bz/show_bug.cgi?id=2387

First, display the list of the existing BEs on the system

$ beadm list
BE Active Active on Mountpoint Space
Name reboot Used
---- ------ --------- ---------- -----
opensolaris no no - 3.92G
opensolaris-1 yes yes - 17.06M

Next, choose the name of a new BE - if the most recent created BE is of
the form "opensolaris-<N>" where <N> is an integer, then a suitable
choice for the new BE is "opensolaris-<N+1>". In the above example,
the new BE would be "opensolaris-2".

Finally, execute the following sequence of commands to create, mount
and update the new BE

$ pfexec beadm create opensolaris-<N+1>
$ mkdir /tmp/mnt$$
$ pfexec beadm mount opensolaris-<N+1> /tmp/mnt$$
$ pfexec pkg -R /tmp/mnt$$ image-update

5) If you are running build 86, the following step is required in order
to work-around

1979 libbe: be_activate needs to run installgrub
http://defect.opensolaris.org/bz/show_bug.cgi?id=1979

>>>>>>>>>> IMPORTANT <<<<<<<<<<

Due to changes in the GRUB boot system, one must manually update the
Master Boot Record (MBR) to include these latest changes. Failure to
follow these instructions when updating from 2008.05 (build 86) to a
later build will result in a system that does not boot by default and
instead the original BE must be manually selected.

Update the GRUB configuration on your ZFS boot device(s) using

$ pfexec /t
$ pfexec beadm activate opensolaris-<N+1>

At this point, you can boot into the updated BE using reboot(1M) or
init(1M) as usual.
_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss


Dennis Clarke
blastwave@gmail.com
Re: Revised instructions for updating from http://pkg.opensolaris.org/
Posted: Jul 14, 2008 11:20 PM   in response to: comay

  Click to reply to this thread Reply

top-post : Thanks for the update. Clearly no one sleeps in Menlo park

On Tue, Jul 15, 2008 at 6:03 AM, <David dot Comay at sun dot com> wrote:
> Enclosed below are revised instructions for using "pkg image-update" to
> update to the latest OpenSolaris development builds via
> http://pkg.opensolaris.org/
>
> For more information on this command and the Image Packaging System
> (IPS) technology, refer to the pkg(1), beadm(1M) and pkg(5) manual
> pages and the following documents
>
> Getting Started With the Image Packaging System
> http://dlc.sun.com/osol/docs/content/IPS/ggcph.html
>
> Upgrading and Managing Your Boot Environments
> http://dlc.sun.com/osol/docs/content/IPS/snap3.html
>
> General instructions for updating to the latest OpenSolaris development build
> =============================================================================> 1) Before using the "image-update" subcommand, it is recommended that
> the latest available version of the IPS software be installed for your
> current boot environment (BE)
>
> $ BUILD=`uname -v | sed s/snv_//`
> $ pfexec pkg refresh
> $ pfexec pkg install SUNWipkg@0.5.11-0.$BUILD
> $ pfexec pkg install entire@0.5.11-0.$BUILD
>
> 2) Verify the build of OpenSolaris in the current BE
>
> $ echo $BUILD
>
> 3) If you are running build 93 or greater, you can use "image-update"
> directly as follows
>
> $ pfexec pkg image-update
>
> At this point, you can boot into the updated BE using reboot(1M) or
> init(1M) as usual.
>
> 4) If you are using a build prior to 93, it is recommended one apply
> the update directly to an alternate BE in order to work-around
>
> 2387 libbe.so:beCopy() frees nvlist variables before using them
> http://defect.opensolaris.org/bz/show_bug.cgi?id=2387
>
> First, display the list of the existing BEs on the system
>
> $ beadm list
> BE Active Active on Mountpoint Space
> Name reboot Used
> ---- ------ --------- ---------- -----
> opensolaris no no - 3.92G
> opensolaris-1 yes yes - 17.06M
>
> Next, choose the name of a new BE - if the most recent created BE is of
> the form "opensolaris-<N>" where <N> is an integer, then a suitable
> choice for the new BE is "opensolaris-<N+1>". In the above example,
> the new BE would be "opensolaris-2".
>
> Finally, execute the following sequence of commands to create, mount
> and update the new BE
>
> $ pfexec beadm create opensolaris-<N+1>
> $ mkdir /tmp/mnt$$
> $ pfexec beadm mount opensolaris-<N+1> /tmp/mnt$$
> $ pfexec pkg -R /tmp/mnt$$ image-update
>
> 5) If you are running build 86, the following step is required in order
> to work-around
>
> 1979 libbe: be_activate needs to run installgrub
> http://defect.opensolaris.org/bz/show_bug.cgi?id=1979
>
> >>>>>>>>>> IMPORTANT <<<<<<<<<<
>
> Due to changes in the GRUB boot system, one must manually update the
> Master Boot Record (MBR) to include these latest changes. Failure to
> follow these instructions when updating from 2008.05 (build 86) to a
> later build will result in a system that does not boot by default and
> instead the original BE must be manually selected.
>
> Update the GRUB configuration on your ZFS boot device(s) using
>
> $ pfexec /tmp/mnt$$/boot/solaris/bin/update_grub -R /tmp/mnt$$
>
> 6) Unmount and activate the newly created BE
>
> $ pfexec beadm unmount opensolaris-<N+1>
> $ pfexec beadm activate opensolaris-<N+1>
>
> At this point, you can boot into the updated BE using reboot(1M) or
> init(1M) as usual.
_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss


loomy

Posts: 567
From:

Registered: 3/17/07
Re: Revised instructions for updating from http://pkg.opensolaris.org/
Posted: Jul 16, 2008 4:49 AM   in response to: comay
To: Projects » indiana » discuss
  Click to reply to this thread Reply

> 4) If you are using a build prior to 93, it is recommended one apply

There are a bunch of new instructions there that I've not seen before. It appears that they work around a bug present pre-b93. My question is about the use of "recommended" here. These new instructions sound like they are required, not just recommended. Am I right?

comay

Posts: 962
From: US

Registered: 3/9/05
Re: Revised instructions for updating from http://pkg.opensolaris.org/
Posted: Jul 16, 2008 10:32 AM   in response to: loomy

  Click to reply to this thread Reply

>> 4) If you are using a build prior to 93, it is recommended one apply
>
> There are a bunch of new instructions there that I've not seen before. It appears that they work around a bug present pre-b93. My question is about the use of "recommended" here. These new instructions sound like they are required, not just recommended. Am I right?

They're not strictly required as beadm(1M) as-is often works but given
we're talking about using recently freed memory (which tickles the
bug), whether you run across the issue or not will vary.

The instructions should have specified that installing the latest
SUNWipkg and the "entire" incorporation is a requirement, however.
I'll update this for the next build.

dsc
_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss


ggravier

Posts: 182
From: FR

Registered: 9/26/05
Re: Revised instructions for updating from http://pkg.opensolaris.org/
Posted: Jul 17, 2008 7:31 AM   in response to: comay

  Click to reply to this thread Reply

David.

Now that I have a bunch of boot environments :

opensolaris
opensolaris-1
opensolaris-2
opensolaris-3

How do I clean up the mess? Can I remove, say, opensolaris and
opensolaris-1 (free up some space and make GRUB look nicer)? What's the
process so that I don't miss bits and parts?

Thanks,
Gilles.

David dot Comay at Sun dot COM wrote:
> Enclosed below are revised instructions for using "pkg image-update" to
> update to the latest OpenSolaris development builds via
> http://pkg.opensolaris.org/
>
> For more information on this command and the Image Packaging System
> (IPS) technology, refer to the pkg(1), beadm(1M) and pkg(5) manual
> pages and the following documents
>
> Getting Started With the Image Packaging System
> http://dlc.sun.com/osol/docs/content/IPS/ggcph.html
>
> Upgrading and Managing Your Boot Environments
> http://dlc.sun.com/osol/docs/content/IPS/snap3.html
>
> General instructions for updating to the latest OpenSolaris development build
> =============================================================================> 1) Before using the "image-update" subcommand, it is recommended that
> the latest available version of the IPS software be installed for your
> current boot environment (BE)
>
> $ BUILD=`uname -v | sed s/snv_//`
> $ pfexec pkg refresh
> $ pfexec pkg install SUNWipkg@0.5.11-0.$BUILD
> $ pfexec pkg install entire@0.5.11-0.$BUILD
>
> 2) Verify the build of OpenSolaris in the current BE
>
> $ echo $BUILD
>
> 3) If you are running build 93 or greater, you can use "image-update"
> directly as follows
>
> $ pfexec pkg image-update
>
> At this point, you can boot into the updated BE using reboot(1M) or
> init(1M) as usual.
>
> 4) If you are using a build prior to 93, it is recommended one apply
> the update directly to an alternate BE in order to work-around
>
> 2387 libbe.so:beCopy() frees nvlist variables before using them
> http://defect.opensolaris.org/bz/show_bug.cgi?id=2387
>
> First, display the list of the existing BEs on the system
>
> $ beadm list
> BE Active Active on Mountpoint Space
> Name reboot Used
> ---- ------ --------- ---------- -----
> opensolaris no no - 3.92G
> opensolaris-1 yes yes - 17.06M
>
> Next, choose the name of a new BE - if the most recent created BE is of
> the form "opensolaris-<N>" where <N> is an integer, then a suitable
> choice for the new BE is "opensolaris-<N+1>". In the above example,
> the new BE would be "opensolaris-2".
>
> Finally, execute the following sequence of commands to create, mount
> and update the new BE
>
> $ pfexec beadm create opensolaris-<N+1>
> $ mkdir /tmp/mnt$$
> $ pfexec beadm mount opensolaris-<N+1> /tmp/mnt$$
> $ pfexec pkg -R /tmp/mnt$$ image-update
>
> 5) If you are running build 86, the following step is required in order
> to work-around
>
> 1979 libbe: be_activate needs to run installgrub
> http://defect.opensolaris.org/bz/show_bug.cgi?id=1979
>
> >>>>>>>>>> IMPORTANT <<<<<<<<<<
>
> Due to changes in the GRUB boot system, one must manually update the
> Master Boot Record (MBR) to include these latest changes. Failure to
> follow these instructions when updating from 2008.05 (build 86) to a
> later build will result in a system that does not boot by default and
> instead the original BE must be manually selected.
>
> Update the GRUB configuration on your ZFS boot device(s) using
>
> $ pfexec /tmp/mnt$$/boot/solaris/bin/update_grub -R /tmp/mnt$$
>
> 6) Unmount and activate the newly created BE
>
> $ pfexec beadm unmount opensolaris-<N+1>
> $ pfexec beadm activate opensolaris-<N+1>
>
> At this point, you can boot into the updated BE using reboot(1M) or
> init(1M) as usual.
> _______________________________________________
> indiana-discuss mailing list
> indiana-discuss at opensolaris dot org
> http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
>

--
*Gilles Gravier, CISSP
*Chief Open Source Ambassador EMEA


<mailto:Gilles dot Gravier at Sun dot com>
Voice :
+41 (22) 999 9051
Mobile :
+41 (79) 472 8437
Fax :
+41 (860) 79 472 8437
E-mail :
Gilles dot Gravier at Sun dot com <mailto:Gilles dot Gravier at Sun dot com>

*Sun Microsystems*
12 route des Avouillons
CH-1196 Gland
Switzerland

http://www.sun.com/security/ SunIM : ggravier at sun dot com <http:// ICQ : 77488526 <http:// AIM : gillesgravier <aim:goim?screenname= Y! : ggravier <http:// Jabber : ggravier at jabber dot org/Gaim <http:// Skype : ggravier <callto:// MSN : Gilles at Gravier dot org <http:// Google : gilles at gravier dot org <mailto:mailto:Gilles at Gravier dot org> This mail was sent through Sun EdgeMail using Mozilla Thunderbird <http://
David.

Now that I have a bunch of boot environments :

opensolaris
opensolaris-1
opensolaris-2
opensolaris-3

How do I clean up the mess? Can I remove, say, opensolaris and opensolaris-1 (free up some space and make GRUB look nicer)? What's the process so that I don't miss bits and parts?

Thanks,
Gilles.

David dot Comay at Sun dot COM wrote:
<pre wrap="">Enclosed below are revised instructions for using "pkg image-update" to update to the latest OpenSolaris development builds via http://pkg.opensolaris.org/ For more information on this command and the Image Packaging System (IPS) technology, refer to the pkg(1), beadm(1M) and pkg(5) manual pages and the following documents Getting Started With the Image Packaging System http://dlc.sun.com/osol/docs/content/IPS/ggcph.html Upgrading and Managing Your Boot Environments http://dlc.sun.com/osol/docs/content/IPS/snap3.html General instructions for updating to the latest OpenSolaris development build ============================================================================= 1) Before using the "image-update" subcommand, it is recommended that the latest available version of the IPS software be installed for your current boot environment (BE) $ BUILD=`uname -v | sed s/snv_//` $ pfexec pkg refresh $ pfexec pkg install SUNWipkg@0.5.11-0.$BUILD $ pfexec pkg install entire@0.5.11-0.$BUILD 2) Verify the build of OpenSolaris in the current BE $ echo $BUILD 3) If you are running build 93 or greater, you can use "image-update" directly as follows $ pfexec pkg image-update At this point, you can boot into the updated BE using reboot(1M) or init(1M) as usual. 4) If you are using a build prior to 93, it is recommended one apply the update directly to an alternate BE in order to work-around 2387 libbe.so:beCopy() frees nvlist variables before using them http://defect.opensolaris.org/bz/show_bug.cgi?id=2387 First, display the list of the existing BEs on the system $ beadm list BE Active Active on Mountpoint Space Name reboot Used ---- ------ --------- ---------- ----- opensolaris no no - 3.92G opensolaris-1 yes yes - 17.06M Next, choose the name of a new BE - if the most recent created BE is of the form "opensolaris-<N>" where <N> is an integer, then a suitable choice for the new BE is "opensolaris-<N+1>". In the above example, the new BE would be "opensolaris-2". Finally, execute the following sequence of commands to create, mount and update the new BE $ pfexec beadm create opensolaris-<N+1> $ mkdir /tmp/mnt$$ $ pfexec beadm mount opensolaris-<N+1> /tmp/mnt$$ $ pfexec pkg -R /tmp/mnt$$ image-update 5) If you are running build 86, the following step is required in order to work-around 1979 libbe: be_activate needs to run installgrub http://defect.opensolaris.org/bz/show_bug.cgi?id=1979 >>>>>>>>>> IMPORTANT <<<<<<<<<< Due to changes in the GRUB boot system, one must manually update the Master Boot Record (MBR) to include these latest changes. Failure to follow these instructions when updating from 2008.05 (build 86) to a later build will result in a system that does not boot by default and instead the original BE must be manually selected. Update the GRUB configuration on your ZFS boot device(s) using $ pfexec /tmp/mnt$$/boot/solaris/bin/update_grub -R /tmp/mnt$$ 6) Unmount and activate the newly created BE $ pfexec beadm unmount opensolaris-<N+1> $ pfexec beadm activate opensolaris-<N+1> At this point, you can boot into the updated BE using reboot(1M) or init(1M) as usual. _______________________________________________ indiana-discuss mailing list indiana-discuss at opensolaris dot org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss </pre>

--
<meta http-equiv="Content-Type" content="text/html; "> <style type="text/css"> <!-- body,td,th { font-family: Arial, Helvetica, sans-serif; font-size: 12px; color: #000000; } --> </style> <title>E-mail Signature Sun 2006</title> <meta content="Gilles Gravier" name="author"> <table style="text-align: left; width: 850px; height: 41px; color: rgb(0, 0, 0);" border="1" cellpadding="1" cellspacing="1"> <tbody> <tr> <td style="text-align: center; vertical-align: top;"> <table style="text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="0" cellspacing="0"> <tbody> <tr> <td style="vertical-align: top;"></td> <td style="width: 15px;"> </td> <td nowrap="nowrap" valign="top">Gilles Gravier, CISSP
Chief Open Source Ambassador EMEA


<table border="0" cellpadding="0" cellspacing="0"> <tbody> <tr> <td>Voice :
</td> <td>+41 (22) 999 9051
</td> </tr> <tr> <td>Mobile :
</td> <td nowrap="nowrap">+41 (79) 472 8437
</td> </tr> <tr> <td>Fax :
</td> <td nowrap="nowrap">+41 (860) 79 472 8437
</td> </tr> <tr> <td style="vertical-align: top;">E-mail :
</td> <td style="vertical-align: top;">Gilles dot Gravier at Sun dot com
</td> </tr> </tbody> </table> </td> <td style="width: 15px;"> </td> <td style="vertical-align: top; white-space: nowrap;">Sun Microsystems
12 route des Avouillons
CH-1196 Gland
Switzerland

http://www.sun.com/security/</td> <td style="width: 15px; vertical-align: top;">
</td> <td style="vertical-align: top;"> <table style="width: 100%; text-align: left;" border="0" cellpadding="0" cellspacing="0"> <tbody> <tr> <td>SunIM :</td> <td>ggravier at sun dot com</td> </tr> <tr> <td style="vertical-align: top;">ICQ :
</td> <td style="vertical-align: top;">77488526
</td> </tr> <tr> <td style="vertical-align: top;">AIM :
</td> <td style="vertical-align: top;">gillesgravier
</td> </tr> <tr> <td style="vertical-align: top;">Y! :
</td> <td style="vertical-align: top;">ggravier
</td> </tr> <tr> <td style="vertical-align: top;">Jabber :
</td> <td style="vertical-align: top;">ggravier at jabber dot org/Gaim
</td> </tr> <tr> <td style="vertical-align: top;">Skype :
</td> <td style="vertical-align: top;">ggravier
</td> </tr> <tr> <td style="vertical-align: top;">MSN :
</td> <td style="vertical-align: top;">Gilles at Gravier dot org
</td> </tr> <tr> <td style="vertical-align: top;">Google :
</td> <td style="vertical-align: top;">gilles at gravier dot org
</td> </tr> </tbody> </table>
</td> </tr> </tbody> </table> </td> </tr> <tr> <td style="text-align: center; vertical-align: top;"> <table style="margin-left: auto; margin-right: auto; text-align: left; height: 18px; width: 815px;" border="0" cellpadding="0" cellspacing="0"> <tbody> <tr> <td style="vertical-align: top; text-align: center;">This mail was sent through Sun EdgeMail using Mozilla Thunderbird 
</td> </tr> </tbody> </table> </td> </tr> </tbody> </table>
_______________________________________________ indiana-discuss mailing list indiana-discuss at opensolaris dot org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss


dminer

Posts: 1,992
From: US

Registered: 3/9/05
Re: Revised instructions for updating from http://pkg.opensolaris.org/
Posted: Jul 17, 2008 7:39 AM   in response to: ggravier

  Click to reply to this thread Reply

Gilles Gravier wrote:
> David.
>
> Now that I have a bunch of boot environments :
>
> opensolaris
> opensolaris-1
> opensolaris-2
> opensolaris-3
>
> How do I clean up the mess? Can I remove, say, opensolaris and
> opensolaris-1 (free up some space and make GRUB look nicer)? What's the
> process so that I don't miss bits and parts?
>

beadm destroy is what you want to use.

Dave
_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss


ggravier

Posts: 182
From: FR

Registered: 9/26/05
Re: Revised instructions for updating from http://pkg.opensolaris.org/
Posted: Jul 17, 2008 11:09 AM   in response to: dminer

  Click to reply to this thread Reply

Hi!

Dave Miner wrote:
> Gilles Gravier wrote:
>
>> David.
>>
>> Now that I have a bunch of boot environments :
>>
>> opensolaris
>> opensolaris-1
>> opensolaris-2
>> opensolaris-3
>>
>> How do I clean up the mess? Can I remove, say, opensolaris and
>> opensolaris-1 (free up some space and make GRUB look nicer)? What's the
>> process so that I don't miss bits and parts
>
> beadm destroy is what you want to use.
>

And to think it was that simple. Thanks! Now I've cleaned up some space...

And... as they say... "On a clean disk, you can seek forever!". :)

Now I'll eagerly wait for b95 with Firefox 3... :)

Oh... And Pidgin 2.4.3 (yeah, I find it very cool that we already have
2.4.2... but whaddayaknow... the pidgin world hasn't stopped rotating).

Thanks again!

Gilles.
--
*Gilles Gravier, CISSP
*Chief Open Source Ambassador EMEA


<mailto:Gilles dot Gravier at Sun dot com>
Voice :
+41 (22) 999 9051
Mobile :
+41 (79) 472 8437
Fax :
+41 (860) 79 472 8437
E-mail :
Gilles dot Gravier at Sun dot com <mailto:Gilles dot Gravier at Sun dot com>

*Sun Microsystems*
12 route des Avouillons
CH-1196 Gland
Switzerland

http://www.sun.com/security/ SunIM : ggravier at sun dot com <http:// ICQ : 77488526 <http:// AIM : gillesgravier <aim:goim?screenname= Y! : ggravier <http:// Jabber : ggravier at jabber dot org/Gaim <http:// Skype : ggravier <callto:// MSN : Gilles at Gravier dot org <http:// Google : gilles at gravier dot org <mailto:mailto:Gilles at Gravier dot org> This mail was sent through Sun EdgeMail using Mozilla Thunderbird <http://
Hi!

Dave Miner wrote:
<pre wrap="">Gilles Gravier wrote: </pre>
<pre wrap="">David. Now that I have a bunch of boot environments : opensolaris opensolaris-1 opensolaris-2 opensolaris-3 How do I clean up the mess? Can I remove, say, opensolaris and opensolaris-1 (free up some space and make GRUB look nicer)? What's the process so that I don't miss bits and parts</pre>
<pre wrap=""><!----> beadm destroy is what you want to use. </pre> </blockquote> <br> And to think it was that simple. Thanks! Now I've cleaned up some space...<br> <br> And... as they say... "On a clean disk, you can seek forever!". :)<br> <br> Now I'll eagerly wait for b95 with Firefox 3... :)<br> <br> Oh... And Pidgin 2.4.3 (yeah, I find it very cool that we already have 2.4.2... but whaddayaknow... the pidgin world hasn't stopped rotating).<br> <br> Thanks again!<br> <br> Gilles.<br> <div class="moz-signature">-- <br> <meta http-equiv="Content-Type" content="text/html; "> <style type="text/css"> <!-- body,td,th { font-family: Arial, Helvetica, sans-serif; font-size: 12px; color: #000000; } --> </style> <title>E-mail Signature Sun 2006</title> <meta content="Gilles Gravier" name="author"> <table style="text-align: left; width: 850px; height: 41px; color: rgb(0, 0, 0);" border="1" cellpadding="1" cellspacing="1"> <tbody> <tr> <td style="text-align: center; vertical-align: top;"> <table style="text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="0" cellspacing="0"> <tbody> <tr> <td style="vertical-align: top;"></td> <td style="width: 15px;"> </td> <td nowrap="nowrap" valign="top">Gilles Gravier, CISSP
Chief Open Source Ambassador EMEA


<table border="0" cellpadding="0" cellspacing="0"> <tbody> <tr> <td>Voice :
</td> <td>+41 (22) 999 9051
</td> </tr> <tr> <td>Mobile :
</td> <td nowrap="nowrap">+41 (79) 472 8437
</td> </tr> <tr> <td>Fax :
</td> <td nowrap="nowrap">+41 (860) 79 472 8437
</td> </tr> <tr> <td style="vertical-align: top;">E-mail :
</td> <td style="vertical-align: top;">Gilles dot Gravier at Sun dot com
</td> </tr> </tbody> </table> </td> <td style="width: 15px;"> </td> <td style="vertical-align: top; white-space: nowrap;">Sun Microsystems
12 route des Avouillons
CH-1196 Gland
Switzerland

http://www.sun.com/security/</td> <td style="width: 15px; vertical-align: top;">
</td> <td style="vertical-align: top;"> <table style="width: 100%; text-align: left;" border="0" cellpadding="0" cellspacing="0"> <tbody> <tr> <td>SunIM :</td> <td>ggravier at sun dot com</td> </tr> <tr> <td style="vertical-align: top;">ICQ :
</td> <td style="vertical-align: top;">77488526
</td> </tr> <tr> <td style="vertical-align: top;">AIM :
</td> <td style="vertical-align: top;">gillesgravier
</td> </tr> <tr> <td style="vertical-align: top;">Y! :
</td> <td style="vertical-align: top;">ggravier
</td> </tr> <tr> <td style="vertical-align: top;">Jabber :
</td> <td style="vertical-align: top;">ggravier at jabber dot org/Gaim
</td> </tr> <tr> <td style="vertical-align: top;">Skype :
</td> <td style="vertical-align: top;">ggravier
</td> </tr> <tr> <td style="vertical-align: top;">MSN :
</td> <td style="vertical-align: top;">Gilles at Gravier dot org
</td> </tr> <tr> <td style="vertical-align: top;">Google :
</td> <td style="vertical-align: top;">gilles at gravier dot org
</td> </tr> </tbody> </table>
</td> </tr> </tbody> </table> </td> </tr> <tr> <td style="text-align: center; vertical-align: top;"> <table style="margin-left: auto; margin-right: auto; text-align: left; height: 18px; width: 815px;" border="0" cellpadding="0" cellspacing="0"> <tbody> <tr> <td style="vertical-align: top; text-align: center;">This mail was sent through Sun EdgeMail using Mozilla Thunderbird 
</td> </tr> </tbody> </table> </td> </tr> </tbody> </table>
_______________________________________________ indiana-discuss mailing list indiana-discuss at opensolaris dot org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss


Dennis Clarke
blastwave@gmail.com
Re: Revised instructions for updating from http://pkg.opensolaris.org/
Posted: Jul 17, 2008 7:22 PM   in response to: ggravier

  Click to reply to this thread Reply

On Thu, Jul 17, 2008 at 6:09 PM, Gilles Gravier <Gilles dot Gravier at sun dot com> wrote:
> Hi!
>
> Dave Miner wrote:
>
> Gilles Gravier wrote:
>
>
> David.
>
> Now that I have a bunch of boot environments :
>
> opensolaris
> opensolaris-1
> opensolaris-2
> opensolaris-3
>
> How do I clean up the mess? Can I remove, say, opensolaris and
> opensolaris-1 (free up some space and make GRUB look nicer)? What's the
> process so that I don't miss bits and parts
>
> beadm destroy is what you want to use.
>
>
> And to think it was that simple. Thanks! Now I've cleaned up some space...
>
> And... as they say... "On a clean disk, you can seek forever!". :)
>
> Now I'll eagerly wait for b95 with Firefox 3... :)
>
> Oh... And Pidgin 2.4.3 (yeah, I find it very cool that we already have
> 2.4.2... but whaddayaknow... the pidgin world hasn't stopped rotating).
>
> Thanks again!
>

I don't know what the fascination is with pidgin but, if you want the
latest version you *can* get pidgin-2.4.3 from Blastwave.

I have run it today and, yes it works but doesn't do anything
particularly fascinating. Isn't just IRC enough for people? What is
this thing with pidgin? Am I missing the point or what?

Dennis
_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss


ggravier

Posts: 182
From: FR

Registered: 9/26/05
Re: Pidgin 2.4.3
Posted: Jul 17, 2008 11:32 PM   in response to: Dennis Clarke

  Click to reply to this thread Reply

Hi!

Dennis Clarke wrote:
> I don't know what the fascination is with pidgin but, if you want the
> latest version you *can* get pidgin-2.4.3 from Blastwave.
>
> I have run it today and, yes it works but doesn't do anything
> particularly fascinating. Isn't just IRC enough for people? What is
> this thing with pidgin? Am I missing the point or what?
>
> Dennis
>
When Package-Manager is fast enough to install pidgin from blastwave in
less than 45 minutes (I canceled the "checking for dependencies" after
45 minutes of waiting) then I will install things from Blastwave...

Now... why Pidgin. Yes... I think you are missing the point. IRC is on
it's way to join the dodo. Geeks use it. Mostly geeks. Yeah... and some
IT people, who, like me, qualify as geeks-emeritus.

The thing is that the rest of the world... in particular my friends, but
more importantly my customers, use other kinds of IM tools. MSN, Yahoo,
ICQ, AOL (yech), and now XMPP-based tools (Sun's Instant Messenger
server is XMPP based as well). If you want to talk to the rest of the
world, you need to talk their language.

Pidgin also supports something called OTR which offers point-to-point
encryption for most IM protocols (except Facebook and IRC, as far as I
know). This is great for business conversations where confidentiality is
a must-have.

So Pidgin is the way to go. Looking at the future... but implementable
today.

IRC is enough for geeks. Not for people. Certainly not for my mom and
dad, or my sister (who is a political scientist and has no clue as to
what IRC even stands for - like most people I know).

Gilles.

_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss


Dennis Clarke
blastwave@gmail.com
Re: Pidgin 2.4.3
Posted: Jul 18, 2008 12:01 AM   in response to: ggravier

  Click to reply to this thread Reply

On Fri, Jul 18, 2008 at 6:32 AM, Gilles Gravier <Gilles dot Gravier at sun dot com> wrote:
> Hi!
>
> Dennis Clarke wrote:
>> I don't know what the fascination is with pidgin but, if you want the
>> latest version you *can* get pidgin-2.4.3 from Blastwave.
>>
>> I have run it today and, yes it works but doesn't do anything
>> particularly fascinating. Isn't just IRC enough for people? What is
>> this thing with pidgin? Am I missing the point or what?
>>
>> Dennis
>>
> When Package-Manager is fast enough to install pidgin from blastwave in
> less than 45 minutes (I canceled the "checking for dependencies" after
> 45 minutes of waiting) then I will install things from Blastwave...

ha haaa ... use Solaris 10. Then it slides right in.

> Now... why Pidgin. Yes... I think you are missing the point. IRC is on
> it's way to join the dodo. Geeks use it. Mostly geeks. Yeah... and some
> IT people, who, like me, qualify as geeks-emeritus.

I have multi-blade propeller top hats.

> The thing is that the rest of the world... in particular my friends, but
> more importantly my customers, use other kinds of IM tools. MSN, Yahoo,
> ICQ, AOL (yech), and now XMPP-based tools (Sun's Instant Messenger
> server is XMPP based as well). If you want to talk to the rest of the
> world, you need to talk their language.

The rest of the world annoys me ... really.

> Pidgin also supports something called OTR which offers point-to-point
> encryption for most IM protocols (except Facebook and IRC, as far as I
> know). This is great for business conversations where confidentiality is
> a must-have.

That is a good idea is aes256-cbc ( or similar ) is offered

> So Pidgin is the way to go. Looking at the future... but implementable
> today.

mmmkay .. but it is so ugly to use.
Can I get it to just be green text on a black background ? :-)

> IRC is enough for geeks. Not for people.

geeks are a subset of people.

> Certainly not for my mom and dad, or my sister (who is a political scientist
> and has no clue as to what IRC even stands for - like most people I know).

poly-sci is what you get when you take many small isomer-poly-sci
students and try to polymerize them via oxygen reduction in a small
room with 2 hour lectures. You either get latex/nylon wrapped students
or a poly-sci graduate out the other end.

I'm just blathering ..

Dennis
_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss


arpunk

Posts: 94
From: CO

Registered: 12/6/07
Re: Pidgin 2.4.3
Posted: Jul 18, 2008 8:23 AM   in response to: Dennis Clarke

  Click to reply to this thread Reply

On Fri, Jul 18, 2008 at 2:01 AM, Dennis Clarke <blastwave at gmail dot com> wrote:
> mmmkay .. but it is so ugly to use.
> Can I get it to just be green text on a black background ? :-)

Yes, pidgin is ugly and bloathed, but you can get it to run in
console using ncurses too :P

IRC should suffice though, there are gateways that let me use
my IRC client with most IM networks.

--
Ricardo Lanziano
6838 E880 7CA4 D4B6 8283 8F65 96AD EC0B F113 AB62
Unix is simple. It just takes a genius to understand its simplicity.
_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss


tmcmahon

Posts: 377
From: McLean, VA USA

Registered: 1/24/06
Re: Pidgin 2.4.3
Posted: Jul 18, 2008 8:28 AM   in response to: arpunk

  Click to reply to this thread Reply

Speaking of pidgin....why is the Sun package built with NSS/NSPR instead
of GnuTLS? Or is that a question for ??? alias?
_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss


Chris Ridd
chrisridd@mac.com
Re: Pidgin 2.4.3
Posted: Jul 18, 2008 8:48 AM   in response to: tmcmahon

  Click to reply to this thread Reply

Torrey McMahon wrote:
> Speaking of pidgin....why is the Sun package built with NSS/NSPR instead
> of GnuTLS? Or is that a question for ??? alias?

It looks like it isn't built with SASL either :-(

Cheers,

Chris
_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss


alanc

Posts: 5,504
From: US

Registered: 3/9/05
Re: Pidgin 2.4.3
Posted: Jul 18, 2008 8:56 AM   in response to: tmcmahon

  Click to reply to this thread Reply

Torrey McMahon wrote:
> Speaking of pidgin....why is the Sun package built with NSS/NSPR instead
> of GnuTLS? Or is that a question for ??? alias?

desktop-discuss is the alias to ask about that.

--
-Alan Coopersmith- alan dot coopersmith at sun dot com
Sun Microsystems, Inc. - X Window System Engineering

_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss


webmink

Posts: 689
From: GB

Registered: 5/18/05
Re: Pidgin 2.4.3
Posted: Jul 18, 2008 8:44 AM   in response to: arpunk

  Click to reply to this thread Reply


On Jul 18, 2008, at 08:23, Ricardo Lanziano wrote:

> IRC should suffice though, there are gateways that let me use
> my IRC client with most IM networks.

With OTR encryption so the conversation remains private?

S.



_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss


arpunk

Posts: 94
From: CO

Registered: 12/6/07
Re: Pidgin 2.4.3
Posted: Jul 18, 2008 12:14 PM   in response to: webmink

  Click to reply to this thread Reply

On Fri, Jul 18, 2008 at 10:44 AM, Simon Phipps <webmink at sun dot com> wrote:
> On Jul 18, 2008, at 08:23, Ricardo Lanziano wrote:
>> IRC should suffice though, there are gateways that let me use
>> my IRC client with most IM networks.
>
> With OTR encryption so the conversation remains private?

If I'm in the need of such privacy I'd use other methods instead of IM.

--
Ricardo Lanziano
6838 E880 7CA4 D4B6 8283 8F65 96AD EC0B F113 AB62
Unix is simple. It just takes a genius to understand its simplicity.
_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss


schwabe

Posts: 1
From:

Registered: 1/18/08
Re: Pidgin 2.4.3
Posted: Jul 18, 2008 12:48 PM   in response to: webmink

  Click to reply to this thread Reply

Simon Phipps schrieb:
> On Jul 18, 2008, at 08:23, Ricardo Lanziano wrote:
>
>
>> IRC should suffice though, there are gateways that let me use
>> my IRC client with most IM networks.
>>
>
> With OTR encryption so the conversation remains private?
>
OTR is vulnerable to man in the middle attacks unless user would check
fingerprint .....

Arne

_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss


ggravier

Posts: 182
From: FR

Registered: 9/26/05
Re: Pidgin 2.4.3
Posted: Jul 18, 2008 11:46 PM   in response to: schwabe

  Click to reply to this thread Reply

Yes. Good point. Using crypto blindly is just what it takes to make big
mistakes.

You do need to check fingerprints. But OTR gives you nice tools to do
that (OTR 3.2 in particular - OpenSolaris still ships 3.1).

OTR is a tool. As with ALL TOOLS, you need to know a bit what you are
doing with it. :)

But isn't it cool that OpenSolaris ships OUT OF THE BOX with OTR enabled
in Pidgin? :)

Gilles.

Arne Schwabe wrote:
> Simon Phipps schrieb:
>> On Jul 18, 2008, at 08:23, Ricardo Lanziano wrote:
>>
>>
>>> IRC should suffice though, there are gateways that let me use
>>> my IRC client with most IM networks.
>>>
>>
>> With OTR encryption so the conversation remains private?
>>
> OTR is vulnerable to man in the middle attacks unless user would check
> fingerprint .....
>
> Arne
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> indiana-discuss mailing list
> indiana-discuss at opensolaris dot org
> http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
>

--
*Gilles Gravier, CISSP
*Chief Open Source Ambassador EMEA


<mailto:Gilles dot Gravier at Sun dot com>
Voice :
+41 (22) 999 9051
Mobile :
+41 (79) 472 8437
Fax :
+41 (860) 79 472 8437
E-mail :
Gilles dot Gravier at Sun dot com <mailto:Gilles dot Gravier at Sun dot com>

*Sun Microsystems*
12 route des Avouillons
CH-1196 Gland
Switzerland

http://www.sun.com/security/ SunIM : ggravier at sun dot com <http:// ICQ : 77488526 <http:// AIM : gillesgravier <aim:goim?screenname= Y! : ggravier <http:// Jabber : ggravier at jabber dot org/Gaim <http:// Skype : ggravier <callto:// MSN : Gilles at Gravier dot org <http:// Google : gilles at gravier dot org <mailto:mailto:Gilles at Gravier dot org> This mail was sent through Sun EdgeMail using Mozilla Thunderbird <http://
Yes. Good point. Using crypto blindly is just what it takes to make big mistakes.

You do need to check fingerprints. But OTR gives you nice tools to do that (OTR 3.2 in particular - OpenSolaris still ships 3.1).

OTR is a tool. As with ALL TOOLS, you need to know a bit what you are doing with it. :)

But isn't it cool that OpenSolaris ships OUT OF THE BOX with OTR enabled in Pidgin? :)

Gilles.

Arne Schwabe wrote:
Simon Phipps schrieb:
On Jul 18, 2008, at 08:23, Ricardo Lanziano wrote:

 
IRC should suffice though, there are gateways that let me use
my IRC client with most IM networks.
   

With OTR encryption so the conversation remains private?
 
OTR is vulnerable to man in the middle attacks unless user would check fingerprint .....

Arne

<pre wrap=""> <hr size="4" width="90%"> _______________________________________________ indiana-discuss mailing list indiana-discuss at opensolaris dot org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss </pre>

--
<meta http-equiv="Content-Type" content="text/html; "> <style type="text/css"> <!-- body,td,th { font-family: Arial, Helvetica, sans-serif; font-size: 12px; color: #000000; } --> </style> <title>E-mail Signature Sun 2006</title> <meta content="Gilles Gravier" name="author"> <table style="text-align: left; width: 850px; height: 41px; color: rgb(0, 0, 0);" border="1" cellpadding="1" cellspacing="1"> <tbody> <tr> <td style="text-align: center; vertical-align: top;"> <table style="text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="0" cellspacing="0"> <tbody> <tr> <td style="vertical-align: top;"></td> <td style="width: 15px;"> </td> <td nowrap="nowrap" valign="top">Gilles Gravier, CISSP
Chief Open Source Ambassador EMEA


<table border="0" cellpadding="0" cellspacing="0"> <tbody> <tr> <td>Voice :
</td> <td>+41 (22) 999 9051
</td> </tr> <tr> <td>Mobile :
</td> <td nowrap="nowrap">+41 (79) 472 8437
</td> </tr> <tr> <td>Fax :
</td> <td nowrap="nowrap">+41 (860) 79 472 8437
</td> </tr> <tr> <td style="vertical-align: top;">E-mail :
</td> <td style="vertical-align: top;">Gilles dot Gravier at Sun dot com
</td> </tr> </tbody> </table> </td> <td style="width: 15px;"> </td> <td style="vertical-align: top; white-space: nowrap;">Sun Microsystems
12 route des Avouillons
CH-1196 Gland
Switzerland

http://www.sun.com/security/</td> <td style="width: 15px; vertical-align: top;">
</td> <td style="vertical-align: top;"> <table style="width: 100%; text-align: left;" border="0" cellpadding="0" cellspacing="0"> <tbody> <tr> <td>SunIM :</td> <td>ggravier at sun dot com</td> </tr> <tr> <td style="vertical-align: top;">ICQ :
</td> <td style="vertical-align: top;">77488526
</td> </tr> <tr> <td style="vertical-align: top;">AIM :
</td> <td style="vertical-align: top;">gillesgravier
</td> </tr> <tr> <td style="vertical-align: top;">Y! :
</td> <td style="vertical-align: top;">ggravier
</td> </tr> <tr> <td style="vertical-align: top;">Jabber :
</td> <td style="vertical-align: top;">ggravier at jabber dot org/Gaim
</td> </tr> <tr> <td style="vertical-align: top;">Skype :
</td> <td style="vertical-align: top;">ggravier
</td> </tr> <tr> <td style="vertical-align: top;">MSN :
</td> <td style="vertical-align: top;">Gilles at Gravier dot org
</td> </tr> <tr> <td style="vertical-align: top;">Google :
</td> <td style="vertical-align: top;">gilles at gravier dot org
</td> </tr> </tbody> </table>
</td> </tr> </tbody> </table> </td> </tr> <tr> <td style="text-align: center; vertical-align: top;"> <table style="margin-left: auto; margin-right: auto; text-align: left; height: 18px; width: 815px;" border="0" cellpadding="0" cellspacing="0"> <tbody> <tr> <td style="vertical-align: top; text-align: center;">This mail was sent through Sun EdgeMail using Mozilla Thunderbird 
</td> </tr> </tbody> </table> </td> </tr> </tbody> </table>
_______________________________________________ indiana-discuss mailing list indiana-discuss at opensolaris dot org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss


thommym

Posts: 168
From: SE

Registered: 6/18/05
Re: Pidgin 2.4.3
Posted: Jul 18, 2008 12:06 AM   in response to: ggravier

  Click to reply to this thread Reply

Gilles Gravier wrote:
> Hi!
>
> Dennis Clarke wrote:
>> I don't know what the fascination is with pidgin but, if you want the
>> latest version you *can* get pidgin-2.4.3 from Blastwave.
>>
>> I have run it today and, yes it works but doesn't do anything
>> particularly fascinating. Isn't just IRC enough for people? What is
>> this thing with pidgin? Am I missing the point or what?
>>
>> Dennis
>>
> When Package-Manager is fast enough to install pidgin from blastwave in
> less than 45 minutes (I canceled the "checking for dependencies" after
> 45 minutes of waiting) then I will install things from Blastwave...
>
> Now... why Pidgin. Yes... I think you are missing the point. IRC is on
> it's way to join the dodo. Geeks use it. Mostly geeks. Yeah... and some
> IT people, who, like me, qualify as geeks-emeritus.
>
> The thing is that the rest of the world... in particular my friends, but
> more importantly my customers, use other kinds of IM tools. MSN, Yahoo,
> ICQ, AOL (yech), and now XMPP-based tools (Sun's Instant Messenger
> server is XMPP based as well). If you want to talk to the rest of the
> world, you need to talk their language.
>
> Pidgin also supports something called OTR which offers point-to-point
> encryption for most IM protocols (except Facebook and IRC, as far as I
> know). This is great for business conversations where confidentiality is
> a must-have.
>
> So Pidgin is the way to go. Looking at the future... but implementable
> today.
>
> IRC is enough for geeks. Not for people. Certainly not for my mom and
> dad, or my sister (who is a political scientist and has no clue as to
> what IRC even stands for - like most people I know).

And what do they interpret Pidgin as?

_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss


khb

Posts: 121
From:

Registered: 4/27/05
Re: Revised instructions for updating from http://pkg.opensolaris.org/
Posted: Oct 6, 2008 12:53 PM   in response to: comay
To: Projects » indiana » discuss
  Click to reply to this thread Reply

Sadly this hasn't seemed to work for me. I've done it several times (minor variations). Here is the last attempt. After the script is finished, I do a pfexec reboot and it correctly tries to boot from the new "opensolaris-" but sadly it says it's not bootable (or something similar that flies by too fast to see) and then it's back to the grub select an image to boot from.

Script started on Mon Oct 06 12:23:09 2008
khb@opensolaris~>BUILD=`uname -v | sed s/snv_//`
khb@opensolaris~>echo $BUILD
86
khb@opensolaris~>alias pf=pfexec
khb@opensolaris~>pf pkg refresh
pfkhb@opensolaris~>pf pkg install SUNWipkg@0.5.11-0.$BUILD
Nothing to install in this image (is this package already installed?) ! yes, from previous attempts
khb@opensolaris~>beadm list

BE Active Active on Mountpoint Space
Name reboot Used
---- ------ --------- ---------- -----
opensolaris yes no legacy 169.65M
opensolaris9x_080922 no no - 2.43G
os0922 no yes - 5.60G
khb@opensolaris~>pf beadm create opensolaris-
khb@opensolaris~>mkdir /tmp/mnt$$
khb@opensolaris~>pf beadm mount opensolaris- /tmp/mnt$$
khb@opensolaris~>pf pkg -R /tmp/mnt$$ image-update
Checking that SUNWipkg (in '/') is up to date...
DOWNLOAD PKGS FILES XFER (MB)
Completed 548/548 29023/29023 501.96/501.96

PHASE ACTIONS
Removal Phase 7143/7143
Install Phase 13721/13721
Update Phase 73918/73918
PHASE ITEMS
Reading Existing Index 9/9
Indexing Packages 548/548
opensolaris- has been updated successfully

---------------------------------------------------------------------------NOTE: Please review release notes posted at:
http://opensolaris.org/os/project/indiana/resources/rn3/
---------------------------------------------------------------------------
khb@opensolaris~>beadm list

BE Active Active on Mountpoint Space
Name reboot Used
---- ------ --------- ---------- -----
opensolaris yes no legacy 178.71M
opensolaris9x_080922 no no - 2.43G
os0922 no yes - 5.60G
opensolaris- no no /tmp/mnt1988 2.43G
khb@opensolaris~>pf beadadm activate opensolaris-
beadadm: Command not found
khb@opensolaris~>pf beadm activate opensolaris-
khb@opensolaris~>exit

script done on Mon Oct 06 13:50:10 2008

evanl

Posts: 754
From: US

Registered: 3/9/05
Re: [indiana-discuss] Revised instructions for updating from http://pkg.opensolaris.org/
Posted: Oct 6, 2008 1:28 PM   in response to: khb

  Click to reply to this thread Reply

Hi Keith,

It appears that you may be hitting 3248 which can cause the running of
installgrub to fail. Does using the instruction for running update_grub
solve the problem?

Thanks,
-evan

Keith Bierman wrote:
> Sadly this hasn't seemed to work for me. I've done it several times (minor variations). Here is the last attempt. After the script is finished, I do a pfexec reboot and it correctly tries to boot from the new "opensolaris-" but sadly it says it's not bootable (or something similar that flies by too fast to see) and then it's back to the grub select an image to boot from.
>
> Script started on Mon Oct 06 12:23:09 2008
> khb@opensolaris~>BUILD=`uname -v | sed s/snv_//`
> khb@opensolaris~>echo $BUILD
> 86
> khb@opensolaris~>alias pf=pfexec
> khb@opensolaris~>pf pkg refresh
> pfkhb@opensolaris~>pf pkg install SUNWipkg@0.5.11-0.$BUILD
> Nothing to install in this image (is this package already installed?) ! yes, from previous attempts
> khb@opensolaris~>beadm list
>
> BE Active Active on Mountpoint Space
> Name reboot Used
> ---- ------ --------- ---------- -----
> opensolaris yes no legacy 169.65M
> opensolaris9x_080922 no no - 2.43G
> os0922 no yes - 5.60G
> khb@opensolaris~>pf beadm create opensolaris-
> khb@opensolaris~>mkdir /tmp/mnt$$
> khb@opensolaris~>pf beadm mount opensolaris- /tmp/mnt$$
> khb@opensolaris~>pf pkg -R /tmp/mnt$$ image-update
> Checking that SUNWipkg (in '/') is up to date...
> DOWNLOAD PKGS FILES XFER (MB)
> Completed 548/548 29023/29023 501.96/501.96
>
> PHASE ACTIONS
> Removal Phase 7143/7143
> Install Phase 13721/13721
> Update Phase 73918/73918
> PHASE ITEMS
> Reading Existing Index 9/9
> Indexing Packages 548/548
> opensolaris- has been updated successfully
>
> ---------------------------------------------------------------------------
> NOTE: Please review release notes posted at:
> http://opensolaris.org/os/project/indiana/resources/rn3/
> ---------------------------------------------------------------------------
>
> khb@opensolaris~>beadm list
>
> BE Active Active on Mountpoint Space
> Name reboot Used
> ---- ------ --------- ---------- -----
> opensolaris yes no legacy 178.71M
> opensolaris9x_080922 no no - 2.43G
> os0922 no yes - 5.60G
> opensolaris- no no /tmp/mnt1988 2.43G
> khb@opensolaris~>pf beadadm activate opensolaris-
> beadadm: Command not found
> khb@opensolaris~>pf beadm activate opensolaris-
> khb@opensolaris~>exit
>
> script done on Mon Oct 06 13:50:10 2008
> --
> This message posted from opensolaris.org
> _______________________________________________
> indiana-discuss mailing list
> indiana-discuss at opensolaris dot org
> http://mail.opensolaris.org/mailman/listinfo/indiana-discuss

_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss


khb

Posts: 121
From:

Registered: 4/27/05
Re: [indiana-discuss] Revised instructions for updating from http://pkg.opensolaris.org/
Posted: Oct 6, 2008 1:45 PM   in response to: evanl

  Click to reply to this thread Reply


On Oct 6, 2008, at 2:28 PM, Evan Layton wrote:

> Hi Keith,
>
> It appears that you may be hitting 3248 which can cause the running of
> installgrub to fail. Does using the instruction for running
> update_grub
> solve the problem?
>

I thought the OP was complete ... and that the following discussion
was rehashing various bits. Now that you call my attention to it, I
found the missing instructions (it might be a kindness to republish
the complete set of directions intact with a big sign on it, ignore
the others ;>).

>
> > $ pfexec /tmp/mnt$$/boot/solaris/bin/update_grub -R /tmp/mnt$$
> >
> > 6) Unmount and activate the newly created BE
> >
> > $ pfexec beadm unmount opensolaris-
> > $ pfexec beadm activate opensolaris-

Thanks!

--
Keith H. Bierman khbkhb at gmail dot com | AIM kbiermank
5430 Nassau Circle East |
Cherry Hills Village, CO 80113 | 303-997-2749
<speaking for myself*> Copyright 2008




_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss





Terms of Use | Privacy | Trademarks | Copyright Policy | Site Guidelines
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Use.
Copyright © 1995-2005 Sun Microsystems, Inc.