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
lutab(4)																  lutab(4)

NAME
lutab - list of boot environments SYNOPSIS
/etc/lutab DESCRIPTION
The file /etc/lutab is a list of the boot environments (BEs) configured on a system. There are two entries for each BE. These entries have the following form: BE_id:BE_name:completion_flag:0 BE_id:root_slice:root_device:1 The fields in the lutab entries are described as follows: BE_id A unique, internally generated id for a BE. BE_name The user-assigned name of a BE. completion_flag Indicates whether the BE is complete (C) or incomplete (NC). A complete BE is one that is not involved in any copy or upgrade operation. A BE can be activated or compared only when it is complete. 0 Indicates first of two lines. BE_id As described above. root_slice Designation of the root slice. root_device Device on which the root slice is mounted. 1 Indicates second of two lines. The lutab file must not be edited by hand. Any user modification to this file will result in the incorrect operation of live upgrade. SEE ALSO
lu(1M), luactivate(1M), lucreate(1M), lucurr(1M), lufslist(1M), lustatus(1M), luupgrade(1M), attributes(5), live_upgrade(5) WARNINGS
The lutab file is not a public interface. The format and contents of lutab are subject to change. Use lufslist(1M) and lustatus(1M) to obtain information about BEs. SunOS 5.10 8 Jun 2001 lutab(4)