Sponsored Content
Operating Systems Solaris Automating old Boot Environment Cleanup Solaris 11 Post 303006479 by os2mac on Thursday 2nd of November 2017 01:47:20 PM
Old 11-02-2017
Wrench Automating old Boot Environment Cleanup Solaris 11

I'm trying to automate the patching process using scripts and cronjobs in Solaris 11.

one of the things I'd like to do is cleanup the old boot environments.

unfortunately

Code:
beadm destroy

requires a response

Code:
:~$ pfexec beadm destroy -f solaris-13
Are you sure you want to destroy solaris-13?  This action cannot be undone(y/[n]):

I've checked the man pages and even with a -f/F it still requires a response.

Anyone got any handy ideas on how to deal with the programmatically?

thanks

Jim
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

automating CDE X applications from boot

Ok, ... I tried posting this in the beginner's forum, but maybe that wasnt the right place. Does anyone know how to automate CDE X applications from boot? If I use the rc2 folder, the programs start in the background with no X window. I am stumped. any suggestions? (5 Replies)
Discussion started by: pkruse
5 Replies

2. UNIX for Dummies Questions & Answers

automating CDE X applications from boot

How do I do it? I am trying to automate an application that requires an X window from boot. help!!! (1 Reply)
Discussion started by: pkruse
1 Replies

3. UNIX for Dummies Questions & Answers

Adding to boot-up environment

During the boot-up process *nix runs scripts linked into the runlevel directories rc#.d. What I'm wondering is, how do I control the environment that those scripts see? I need to set a couple environment variables, and I can NOT do it from within the scripts because it poses a maintenance nightmare... (1 Reply)
Discussion started by: DreamWarrior
1 Replies

4. UNIX for Dummies Questions & Answers

Messed up my boot environment or root profile

Ok, a couple weeks ago I was fixing a cron report about perl not happy with 'locale' info (LANG and LC not set). As a result, I was experimenting with setting the correct 'locale' in several areas (like /etc/sysconfig/i18n and who knows where). Somehow after a reboot, as soon as the OS starts... (3 Replies)
Discussion started by: Garball
3 Replies

5. Solaris

Solaris live upgrade on Active boot environment

Hi, Is it possible to perform an luupgrade on the active boot environment in Solaris? I want to perform this on BEAlpha - the disk that has BEOmega will be unavailable whilst performing the upgrade but I still want to install the patches using luupgrade. Boot Environment Is... (4 Replies)
Discussion started by: Mr_Webster
4 Replies

6. Solaris

Restoring to previous Boot Environment

Hi all, I'm fairly new to Solaris and am just getting to grips with using LU (Live Upgrade) for OS patching purposes. worcester#uname -a SunOS worcester 5.10 Generic_144488-12 sun4v sparc SUNW,SPARC-Enterprise-T5220I have successfully created and patched a new BE (boot environment) using the... (5 Replies)
Discussion started by: polo_mint4
5 Replies

7. UNIX for Beginners Questions & Answers

Lucreate Fails to Create Boot Environment;

My OS solarius 5.10 Generic_147148-2 i86 Error: please review new boots environments using options 1. Solution - show me the commands Partition is full, try to remove some unneeded files, then try to compress some other unneeded files. man command creates a temp file under... (0 Replies)
Discussion started by: zbest1966
0 Replies

8. Solaris

T5-4 Bootloop with 11.4 Boot Environment

TLDR: Patched a separate boot environment to 11.4. Activated and rebooted the system only to have it boot loop and show 11.3 on the patched boot environment. Bootloop process: The system went down, came up showing 11.3 then spewed bunch of errors and resetted. SEE BELOW FOR THE FINAL MSG... (1 Reply)
Discussion started by: samthewildone
1 Replies
root_archive(1M)														  root_archive(1M)

NAME
root_archive - manage bootable miniroot archives SYNOPSIS
/boot/solaris/bin/root_archive pack archive root /boot/solaris/bin/root_archive unpack archive root /boot/solaris/bin/root_archive packmedia solaris_image root /boot/solaris/bin/root_archive unpackmedia solaris_image root The root_archive utility is used to manage bootable miniroot archives and is currently only available on platforms. The utility can pack and unpack boot/root archives in both ufs and hsfs (iso9660) format. It will always generate ufs archives. root_archive also uses the lofi file driver to export a file as a block device (see lofi(7D)) and mount to mount or unmount file systems and remote resources (see mount(1M)). root_archive requires the same privileges that are needed to run these commands. SUBCOMMANDS
The root_archive command has the following subcommands: pack archive root Pack from the image found under the root directory to the archive. unpack archive root Unpack from the archive to an unpacked image under the root directory. packmedia solaris_image root Pack the solaris image to the root directory. unpackmedia solaris_image root Unpack the solaris image from the root directory. For packmedia and unpackmedia, other items that do not go into the ramdisk image are copied or uncopied (see cpio(1)) as well. Specifi- cally, this includes all the packaging databases needed for pkgadd and the other packaging utilities to succeed which are not used in the running and hence pruned to conserve memory. EXAMPLES
Example 1: Unpacking the Solaris x86 install image The following command unpacks the current Solaris image from the root directory: # root_archive unpackmedia /export/nv/solarisdvd.nvx_dvd/latest /export/Boot Where /export/nv/solarisdvd.nvx_dvd/latest represents a path to a Solaris x86 install image and /export/Boot is a directory that will be purged or created, as necessary. Example 2: Packing the Solaris x86 install image The following command packs the current Solaris image to the root directory: # root_archive packmedia /export/nv/solarisdvd.nvx_dvd/latest /export/Boot The following exit values are returned: 0 The command completed successfully. 1 The command exited due to an error. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ cpio(1), bootadm(1M), mount(1M), attributes(5), lofi(7D) 26 Sep 2005 root_archive(1M)
All times are GMT -4. The time now is 12:51 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy