12-21-2017
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 /tmp for extracting zip manual and
no space.
2 Solution - show me the commands
Simply, error messages is showing you that no space left on,
extend the / size or allocate the different location.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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
2. UNIX for Dummies Questions & Answers
Hi, i was installing solaris 8 on sunfire v250 and the power fails :mad: , now it does not boot from cd rom and get the next msg:
ð
Sun Fire V120 (UltraSPARC-IIe 648MHz), No Keyboard
OpenBoot 4.0, 512 MB memory installed, Serial #56338483.
Ethernet address 0:3:ba:5b:a8:33, Host ID: 835ba833.
... (1 Reply)
Discussion started by: agustincm
1 Replies
3. HP-UX
I have a machine running HP-UX 11.23 (PARISC) and APA startup fails on boot. This is found in /etc/rc.log:
Configure Auto-Port Aggregation(LAN Monitor) interfaces
Output from "/sbin/rc2.d/S343hplm start":
----------------------------
get_start_dlpi_version: failed, errno is 22
ERROR: ... (1 Reply)
Discussion started by: kknigga
1 Replies
4. Solaris
Hi,
I currently have one BE and would like to create an ABE.
# lustatus
BE_name Complete Active ActiveOnReboot CopyStatus
------------------------------------------------------------------------
coolthreads yes yes yes - But... (3 Replies)
Discussion started by: pgarousi
3 Replies
5. UNIX for Advanced & Expert Users
Hi,
I am trying to setup a server for a diskless boot of a computer class (with ubuntu)
I followed the guidelines in https://help.ubuntu.com/community/DisklessUbuntuHowto
I have two computers: one is the server I installed and the other is my macbook on which I run a virtual machine... (8 Replies)
Discussion started by: yotamhc
8 Replies
6. Solaris
One of our T5220 servers fail to boot due to following error:
ERROR: The following devices are disabled:
XAUI1
XAUI0
I can't see any disabled components in SP console, any idea what is the problem? (1 Reply)
Discussion started by: belalr
1 Replies
7. Solaris
I have a T2000 enterprise SPARC server that's no longer on contract with Oracle. It's on old firmware (6.3.x). After a power-down this weekend, it won't boot normally. Boot snapshot at the bottom of the post.
It can boot to cdrom, and it'll boot to failsafe mode, but it won't do a regular... (9 Replies)
Discussion started by: val riverwalk
9 Replies
8. Solaris
I have an m5000 that Is down.
I have access to XSCF>
and was able to get to the ok prompt.
However, on
>ok boot
it failed to boot.
erred with :
svc.startd: svc:/system/device/fc-fabric:default: Method "/lib/svc/method/fc-fabric" failed due to signal KILL.
Nov 29... (3 Replies)
Discussion started by: goya
3 Replies
9. Solaris
My system suddenly crash and when it rebooted there was an error:
/dev/rdsk/c1t0d0s3 is logging
svc.startd: svc:/network/nis/client:default: Method "/method/yp" failed with status 96.
The system completes booting however when I log in a user account / directory is not longer... (1 Reply)
Discussion started by: NeedSolarisHelp
1 Replies
10. Solaris
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
MAN(1) General Commands Manual MAN(1)
NAME
man - display online manual pages
SYNOPSIS
man [-antkf] [-M path] [-s section] title ...
DESCRIPTION
Man displays the online manual pages for the specified titles in the specified sections. The sections are as follows:
1 User Commands
Generic commands such as ls, cp, grep.
2 System Calls
Low level routines that directly interface with the kernel.
3 Library Routines
Higher level C language subroutines.
4 Device Files
Describes devices in /dev.
5 File Formats
Formats of files handled by various utilities and subroutines.
6 Games
It's not UNIX without an adventure game.
7 Miscellaneous
Macro packages, miscellaneous tidbits.
8 System Utilities
Commands for the System Administrator.
9 Documents
Larger manuals explaining some commands in more detail.
(If you are new to Minix then try man hier, it will show you around the file system and give you many pointers to other manual pages.)
By default, man will try the following files in a manual page directory for the command man -s 1 ls:
cat1/ls.1
cat1/ls.1.Z
man1/ls.1
man1/ls.1.Z
Files in the man[1-8] directories are formatted with nroff -man. Those in man9 are formatted with nroff -mnx. Files in the cat? directo-
ries are preformatted. Files with names ending in .Z are decompressed first with zcat (see compress(1)). The end result is presented to
the user using a pager if displaying on the screen.
For each manual page directory in its search path, man will first try all the subdirectories of the manual page directory for the files
above, and then the directory itself. The directory /usr/man contains the standard manual pages, with manual pages for optional packages
installed in a subdirectory of /usr/man, with the same structure as /usr/man. The directory /usr/local/man contains manual pages for
locally added software. By default /usr/local/man is searched first, then /usr/man.
A title is not simply used as a filename, because several titles may refer to the same manual page. Each manual page directory contains a
database of titles in the whatis(5) file that is created by makewhatis(8) from the NAME sections of all the manual pages. A title is
searched in this database and the first title on a whatis line is used as a filename.
OPTIONS
The options may be interspersed with the titles to search, and take effect for the titles after them.
-a Show all the manual pages or one line descriptions with the given title in all the specified sections in all the manual directories
in the search path. Normally only the first page found is shown.
-n Use nroff -man to format manual pages (default).
-t Use troff -man to format manual pages.
-f Use whatis(1) to show a one line description of the title from the whatis(5) file.
-k Use apropos(1) to show all the one line descriptions of the title anywhere in the whatis(5) files (implies -a).
-M path
Use path as the search path for manual directories.
-s section
Section is the section number the page is to be found in, or a comma separated list of sections to use. Normally all sections are
searched. The search is always in numerical order no matter what your section list looks like. A single digit is treated as a sec-
tion number without the -s for compatibility with BSD-style man commands.
ENVIRONMENT
MANPATH This is a colon separated list of directories to search for manual pages, by default /usr/local/man:/usr/man.
PAGER The program to use to display the manual page or one line descriptions on the screen page by page. By default more.
FILES
/usr/man/whatis One of the whatis(5) databases.
SEE ALSO
nroff(1), troff(1), more(1), whatis(1), makewhatis(1), catman(1), whatis(5), man(7).
AUTHOR
Kees J. Bot (kjb@cs.vu.nl)
MAN(1)