Sponsored Content
Full Discussion: Single user mode
Operating Systems Solaris Single user mode Post 302817601 by hicksd8 on Thursday 6th of June 2013 06:10:21 AM
Old 06-06-2013
The passwd file you are seeing is the one on the DVD that you booted from.

Boot into single user

Code:
 
boot cdrom -s

then mount your harddisk root filesystem under /a using the normal device string of your harddisk root filesystem (eg, /dev/dsk/sda0 or whatever it is)

Code:
 
mount /dev/dsk/sda0 /a

Now your harddisk root filesystem is accessible by

Code:
 
cd /a

Under /a you will have the whole filesystem.

When you're done, remember to shutdown in an orderly manner, eg.

Code:
 
init 0

Hope that helps.
This User Gave Thanks to hicksd8 For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

single user mode

Hi all, why "vi" acts differently is single user mode? Does anyone help ? I am using "x" to delete and it keeps messing up. Please help Thanks (2 Replies)
Discussion started by: guest100
2 Replies

2. UNIX for Dummies Questions & Answers

Single user mode

Hi all, Well back at work and back to crashing systems again :-) Does anyone know where I can find some decent information on single user mode? I need to be able to fix a few things. Don't know if it's possible in single user mode but I need to fix the "etc/vfstab" mainly I re-wrote it to... (2 Replies)
Discussion started by: merlin
2 Replies

3. UNIX for Dummies Questions & Answers

single-user mode

how do you boot into single user mode? RedHat 7.1 Caldera 2.4 (2 Replies)
Discussion started by: zorro81
2 Replies

4. Solaris

adding a user in single user mode

Just got a solaris 8 blade 150 box with no users, only a root account. no one seems to know the password. I'd like to add one user. So I booted into single user mode via cdrom and added one. Can't seem to login using the new account, though. Here's what I'm using: # useradd -d /tmp/"user" -m... (1 Reply)
Discussion started by: ECBROWN
1 Replies

5. UNIX for Advanced & Expert Users

single user mode

Is there another way of switching to single user mode except by typing /usr/sbin/shutdown 0 ??? :rolleyes: (5 Replies)
Discussion started by: kekanap
5 Replies

6. UNIX for Advanced & Expert Users

single user mode

How to diable the single user mode.. what i want is dat my users are unable to boot in single user mode via GRUB.. (1 Reply)
Discussion started by: ankit.jss
1 Replies

7. UNIX for Dummies Questions & Answers

how to Single user mode?

How to enter single user mode when UNIX/LINUX system is starting? (1 Reply)
Discussion started by: gkreddy
1 Replies

8. UNIX for Dummies Questions & Answers

single user mode - user accounts passwords

hello ppl, someone must be able to help with this --> I have an old NCR tower 32 with an ADDS terminal running a unix version 020102 (Im not sure if thats correct but its unix for sure). I have no user names and no passwords and need to login to read a tape. Is there any way to do that? I hear... (3 Replies)
Discussion started by: orestis
3 Replies

9. UNIX for Dummies Questions & Answers

Not able to log into single user mode.

Hi as per the article given. Boot Linux Grub Into Single User Mode I m modifying the boot entry grub edit> kernel /vmlinuz-2.6.18-92.el5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet Singleand then booting from it by pressing b. However the machine is getting booted into runlevel 5. if the... (2 Replies)
Discussion started by: pinga123
2 Replies

10. Solaris

Single user mode

Dear All I am trying to install my os as : ok>boot cdrom - install but receiving the following : "IDprom checksum error getexecname() failed /sbin/rcS /etc/vfstab cannot create INIT:failed write utmpx enrty INIT:single user mode INIT:execle of /etc/sulogin failed Enter run level" Can you... (6 Replies)
Discussion started by: hadimotamedi
6 Replies
SCRIPT(1)                                                          User Commands                                                         SCRIPT(1)

NAME
script - make typescript of terminal session SYNOPSIS
script [options] [file] DESCRIPTION
script makes a typescript of everything displayed on your terminal. It is useful for students who need a hardcopy record of an interactive session as proof of an assignment, as the typescript file can be printed out later with lpr(1). If the argument file is given, script saves the dialogue in this file. If no filename is given, the dialogue is saved in the file type- script. OPTIONS
-a, --append Append the output to file or to typescript, retaining the prior contents. -c, --command command Run the command rather than an interactive shell. This makes it easy for a script to capture the output of a program that behaves differently when its stdout is not a tty. -e, --return Return the exit code of the child process. Uses the same format as bash termination on signal termination exit code is 128+n. -f, --flush Flush output after each write. This is nice for telecooperation: one person does `mkfifo foo; script -f foo', and another can supervise real-time what is being done using `cat foo'. --force Allow the default output destination, i.e. the typescript file, to be a hard or symbolic link. The command will follow a symbolic link. -q, --quiet Be quiet (do not write start and done messages to standard output). -t[file], --timing[=file] Output timing data to standard error, or to file when given. This data contains two fields, separated by a space. The first field indicates how much time elapsed since the previous output. The second field indicates how many characters were output this time. This information can be used to replay typescripts with realistic typing and output delays. -V, --version Display version information and exit. -h, --help Display help text and exit. NOTES
The script ends when the forked shell exits (a control-D for the Bourne shell (sh(1)), and exit, logout or control-d (if ignoreeof is not set) for the C-shell, csh(1)). Certain interactive commands, such as vi(1), create garbage in the typescript file. script works best with commands that do not manipulate the screen, the results are meant to emulate a hardcopy terminal. It is not recommended to run script in non-interactive shells. The inner shell of script is always interactive, and this could lead to unexpected results. If you use script in the shell initialization file, you have to avoid entering an infinite loop. You can use for example the .profile file, which is read by login shells only: if test -t 0 ; then script exit fi You should also avoid use of script in command pipes, as script can read more input than you would expect. ENVIRONMENT
The following environment variable is utilized by script: SHELL If the variable SHELL exists, the shell forked by script will be that shell. If SHELL is not set, the Bourne shell is assumed. (Most shells set this variable automatically). SEE ALSO
csh(1) (for the history mechanism), scriptreplay(1) HISTORY
The script command appeared in 3.0BSD. BUGS
script places everything in the log file, including linefeeds and backspaces. This is not what the naive user expects. script is primarily designed for interactive terminal sessions. When stdin is not a terminal (for example: echo foo | script), then the session can hang, because the interactive shell within the script session misses EOF and script has no clue when to close the session. See the NOTES section for more information. AVAILABILITY
The script command is part of the util-linux package and is available from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils /util-linux/>. util-linux June 2014 SCRIPT(1)
All times are GMT -4. The time now is 07:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy