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.
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)
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)
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)
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)
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)
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
LEARN ABOUT OPENDARWIN
script
SCRIPT(1) BSD General Commands Manual SCRIPT(1)NAME
script -- make typescript of terminal session
SYNOPSIS
script [-a] [-k] [-q] [-t time] [file [command ...]]
DESCRIPTION
The script utility makes a typescript of everything printed 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 all dialogue in file. If no file name is given, the typescript is saved in the file typescript.
If the argument command ... is given, script will run the specified command with an optional argument vector instead of an interactive shell.
Options:
-a Append the output to file or typescript, retaining the prior contents.
-k Log keys sent to program as well as output.
-q Run in quiet mode, omit the start and stop status messages.
-t time Specify time interval between flushing script output file. A value of 0 causes script to flush for every character I/O event. The
default interval is 30 seconds.
The script ends when the forked shell (or command) exits (a control-D to exit 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. The script utility works best with commands that do not
manipulate the screen. The results are meant to emulate a hardcopy terminal, not an addressable one.
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).
HISTORY
The script command appeared in 3.0BSD.
BUGS
The script utility places everything in the log file, including linefeeds and backspaces. This is not what the naive user expects.
It is not possible to specify a command without also naming the script file because of argument parsing compatibility issues.
When running in -k mode, echo cancelling is far from ideal. The slave terminal mode is checked for ECHO mode to check when to avoid manual
echo logging. This does not work when in a raw mode where the program being run is doing manual echo.
BSD June 6, 1993 BSD