<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Boot-Environments on sigtar.com</title>
		<link>https://sigtar.com/tags/boot-environments/</link>
		<description>Recent content in Boot-Environments on sigtar.com</description>
		<generator>Hugo</generator>
		<language>en-nz</language>
		
		
		
		
			<lastBuildDate>Tue, 31 Mar 2009 00:00:00 +1300</lastBuildDate>
		
			<atom:link href="https://sigtar.com/tags/boot-environments/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Opensolaris - Managing Boot Environments with beadm</title>
				<link>https://sigtar.com/2009/03/31/opensolaris-managing-boot-environments-with-beadm/</link>
				<pubDate>Tue, 31 Mar 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/03/31/opensolaris-managing-boot-environments-with-beadm/</guid>
				<description>&lt;p&gt;To get a list of all of your boot environments within Opensolaris use &lt;strong&gt;beadm&lt;/strong&gt; like so…. &lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;beadm list&lt;/strong&gt; &lt;/p&gt;&#xA;&lt;p&gt;Assuming you know the name of the boot environment that is causing issues you can use the following command (using its name) to remove the ones you think are suss. Note: you need to boot up in the environment that you wish to keep first. &lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;beadm destroy &lt;em&gt;opensolaris-2&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;If you destroy an environment that is active on boot it will be changed to another be that is available. You can use the following command to set it to a specific boot environment; &lt;/p&gt;</description>
			</item>
	</channel>
</rss>
