Working With Multiple Boot Environments on OpenSolaris


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris BigAdmin RSS Working With Multiple Boot Environments on OpenSolaris
# 1  
Old 12-03-2008
Working With Multiple Boot Environments on OpenSolaris

New in OpenSolaris is a utility called beadm, with which you can more efficiently manage boot environments. In this article on the Sun Developer Network, learn how to manage BEs with beadm through an example.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Solaris

ERROR: ZFS pool <Pool_Name> does not support boot environments

Hello, I am a newbie to the world of Solaris. so please ignore if I make any silly point. Recently I was trying to migrate UFS file system to ZFS on Solaris 10 (x86 platform). I have followed standard procedures/documents available online ... (4 Replies)
Discussion started by: Kumar07
4 Replies

2. Solaris

OpenSolaris GRUB> boot failure HELP

Hi, i am running an old Opensolaris 5.11 snv_111b on an x86 server. After almost 4 years of successful service, last night out of the blue started to refuse all connections to it's services, ssh, http,etc. The only visible solution at that time was a restart. But now instead of booting the... (2 Replies)
Discussion started by: d_oilen
2 Replies

3. Solaris

installed new opensolaris but sound not working

today i installed new opensola, but sound drivers are not working properly. getting this error, i m totally new to solaris. - nilesh Getting this error...... - nilesh (1 Reply)
Discussion started by: ynilesh
1 Replies
Login or Register to Ask a Question
lucurr(1M)																lucurr(1M)

NAME
lucurr - display the name of the active boot environment SYNOPSIS
/usr/sbin/lucurr [-l error_log] [-m mount_point] [-o outfile] [-X] DESCRIPTION
The lucurr command is part of a suite of commands that make up the Live Upgrade feature of the Solaris operating environment. See live_upgrade(5) for a description of the Live Upgrade feature. The lucurr command displays the name of the currently running boot environment (BE). If no BEs are configured on the system, lucurr dis- plays the message "No Boot Environments are defined". Note that lucurr reports only the name of the current BE, not the BE that will be active upon the next reboot. Use lustatus(1M) or luactivate(1M) for this information. The lucurr command requires root privileges. OPTIONS
The lucurr command has the following options: -l error_log Error and status messages are sent to error_log, in addition to where they are sent in your current environment. -m mount_point Returns the name of the BE that owns mount_point, where mount_point is the mount point of a BE's root file system. This can be a mount point of the current BE or the mount point of a BE other than the current BE. If the latter, the file system of the BE must have been mounted with lumount(1M) or mount(1M) before entering this option. -o outfile All command output is sent to outfile, in addition to where it is sent in your current environment. -X Enable XML output. Characteristics of XML are defined in DTD, in /usr/share/lib/xml/dtd/lu_cli.dtd.<num>, where <num> is the version number of the DTD file. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. FILES
/etc/lutab list of BEs on the system /usr/share/lib/xml/dtd/lu_cli.dtd.<num> Live Upgrade DTD (see -X option) ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWluu | +-----------------------------+-----------------------------+ SEE ALSO
lu(1M), luactivate(1M), lucancel(1M), lucompare(1M), lucreate(1M), ludelete(1M), ludesc(1M), lufslist(1M), lumake(1M), lumount(1M), lure- name(1M), lustatus(1M), luupgrade(1M), lutab(4), attributes(5), live_upgrade(5) SunOS 5.10 24 Jan 2002 lucurr(1M)