We will be undergoing scheduled maintenance on May 20th, 2013 at 02:00 GMT.
For our next topic we're going to look at administering boot environments in IPS. Now you might be wondering what a Package Manager has to do with managing boot environments, well the answer is simple. The way Solaris 11 refers to boot environments, they're multiple images with different kernels, software applications or updates. And you can have multiple images on a box so that you can boot into each separately, each boot environment and have different kernels and software and so forth. Now only one boot environment can be active at a time but you can have multiple boot environments installed. Now what typically happens is you have an image that is installed by default, when you install a Solaris box. And this is named by default Solaris and that's your base image and it's your only active image. You can also create additional images that are exact copies and save those images for later or update them if you want to try our new software without damaging your initial image. So, there's different ways you can manage these boot environments. Now you can use the Package Manager GUI to a small degree but you typically will use the Command Line interface, the B-E-A-D-M Command which stands for Boot Environment Admin. And you can manage the boot environments with these two utilities. So let's go ahead and take a look at both. We're in Solaris 11 again and we're going to look at the Package Manager really quickly. And what we want to do is look at File and Manage Boot Environments. And there's not a lot to see here actually, you don't really manage the boot environments too much in this GUI. The few things that you can do I'll show you in a moment. Right now we have one boot environment installed and that's the default, Solaris one that was installed when the box was installed. And it shows that it's active on reboot. It also shows that you can delete it but you can't do that with the default active boot environment. And it will actually tell you this is the currently active one. So let's go ahead and cancel this for right now. Actually let's go ahead and move to the Command Line interface and what we see here, we're at the prompt and I've already logged in as Root because you can't perform some of these Boot Environment Commands without being Root. So let's just go ahead and run a simple BÐE-A-D-M List Command and this will list the active boot environments. And this really is a repeat of what we saw a moment ago in the GUI. You have the Solaris boot environment, then R shows that it is the active one and that it will be the active on the next reboot and that's important to know is which one will be active on the next reboot. And you can set those to be the active one in the GUI itself. So let's go ahead and create a boot environment and we use the Create Command to do that. And we can name it anything we want. I'm just going to name it VTC Test, that'll be our new boot environment. So we're going to create that and right now what it's going to give us is a snapshot of the current boot environment. Let's go ahead and do another list and now that we see that we have a different boot environment created. And right now there's not too much it, it's just basically a snapshot. Let's go back for a second to the GUI and let's cancel this out, we want to refresh this. So let's go and Manage Boot Environments again and we should have two boot environments and we do. So now we can actually change these and make this one the active one when we reboot. Now it is an exact copy of it but the exact copy is really just the changes. It will save off the changes and make a different image when it reboots. And you can delete it from here as well. You can delete this boot environment. You can also rename them from the Command Line but you cannot do anything with the active image. Let's go ahead and leave that the way it is and we'll say Cancel. Now let's go back to the Command Line and let's go ahead and destroy this and that's how you delete one is to destroy one. And you have to specify which one you want and it will prompt you to see if you're sure and tell you that it can't be undone and we'll say Yes to that. And let's go ahead and look at B-E-A-D-M List and see what we have. We're back to where we were and I think if we go back into the GUI we'll see the same thing. We'll see that, that has been deleted from the list of boot environments and it has been. There are other commands as well that we can use for B-E-A-D-M and let's look at a couple of them. We have several commands, we can activate a boot environment we can create it obviously and there's different values we can assign to the boot environment itself. We can destroy them, we can list them, we saw that already. We can mount them in a different mount point and we can rename them. And one thing you need to know is that the active boot environment cannot be renamed or deleted. You must change it to a different active boot environment in order to delete or rename that particular boot environment. So B-E-A-D-M is a very simple command to use and if you want to play around with different boot environments or make changes to your initial image, this is the best way to do it without damaging anything and without changing some of your initial software or current one. So that's all there really is to boot environments.
| Course: | Oracle Solaris 11 System Administration - Exam 1Z0-821 |
| Author: | Bobby Rogers |
| SKU: | 34398 |
| ISBN: | 978-1-61866-083-1 |
| Release Date: | 2012-12-24 |
| Duration: | 8 hrs / 92 lessons |
| Work Files: |
Yes |
| Captions: | No |
| Compatibility: |
Vista/XP/2000, OS X, Linux QuickTime 7, Flash 8 |