06-25-2008
illegal option
can this mean that the argument needs space between -I and /dev... ?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi. I have been having problems with restoring from a tape backup. I use the following cpio command:
find / -print | cpio -ouvB > /dev/rStp0
After running this cpio command, the screen will display all files, but when I try to read or restore the tape I get the following error:
Tape input... (1 Reply)
Discussion started by: cstovall
1 Replies
2. Filesystems, Disks and Memory
I have been restoring from tape some old data. I have done quite a few tapes and have had no problems until now.
The command I am running is "dd if=/dev/rmt/1hbn bs=1024 | tar -pBxF - ".
This is the second tape have have come up with the error "Not enough space". This tape has a couple of... (1 Reply)
Discussion started by: mtoombs
1 Replies
3. HP-UX
I am trying to do a restore on a backup tape (DDS2) and am having a little trouble. For one, I dont know how the tape was made, whether is was tar, cpio, dump..etc. Anyone know how to restore a tape without knowing the format of the backup? (5 Replies)
Discussion started by: bake255
5 Replies
4. AIX
Hello everyone
I have a tape with some information that I got
to restore, the tape was made with the fbackup
command in a hp box.
My question is that I have to restore in a Ibm
box, how can I do this ?
Thanks in advance (1 Reply)
Discussion started by: lo-lp-kl
1 Replies
5. SCO
Here is the scenario. We have an billing system that ran on SCO 5.0.6. The HP Netserver went dwon, along with SCSI disks. They are unretrievable. I installed an IDE HDD, and reinstalled SCO. I am not too familiar w/ SCO or UNIX, and need to know how to install Tape drive, and how to restore from... (11 Replies)
Discussion started by: jlewis808
11 Replies
6. Solaris
I have a T2000 server that is JumpStarted with Solaris 10 from the JumpStart server. Host name and IP address is changed after that. Then we backup the server using FLAR to tape:
root.damas# date; flarcreate -c -t -n "Sol10_cairo_image" -a "engineering@starsolutions.com" -R / /dev/rmt/0n ;... (2 Replies)
Discussion started by: StarSol
2 Replies
7. SCO
Looking for specifically naming convention for a tape device for SCO Unix
What full system backup command should I use for SCO UNIX (1 Reply)
Discussion started by: jedimaster
1 Replies
8. Solaris
Hope someone can help me here...
I've got to restore an E450 with 300MHz cpus which was running Solaris 2.6 from tape. Regrettably the boot drive has failed.
I've access to the first release of Solaris 2.6 CD's and to a set of Solaris 9 CD's.
I remember that different E450 CPUs needed different... (1 Reply)
Discussion started by: pamplemousse
1 Replies
9. SCO
Hello folks. I have the following problem:
I'm trying to create a tape backup of a list of files on a 10 year old server, running SCO Openserver 5.0.5 (the tape drive is a Seagate STD224000N, connected as a SCSI drive).
I then want to restore the contents of this tape onto a new server... (6 Replies)
Discussion started by: klabelkholosh
6 Replies
10. Emergency UNIX and Linux Support
Hi
I recently deleted my /etc but I had a backup on tape. I was able to boot the server with a cd-rom and mounted the /c1t0d0s0 which is where the root directory resides. However when I tried to restore the backup with tar xvf /dev/rmt/0n I wasn't successful even though I was able to use the tar... (2 Replies)
Discussion started by: rahmantanko
2 Replies
LEARN ABOUT OPENSOLARIS
kmem
mem(7D) Devices mem(7D)
NAME
mem, kmem, allkmem - physical or virtual memory access
SYNOPSIS
/dev/mem
/dev/kmem
/dev/allkmem
DESCRIPTION
The file /dev/mem is a special file that provides access to the physical memory of the computer.
The file /dev/kmem is a special file that provides access to the virtual address space of the operating system kernel, excluding memory
that is associated with an I/O device.
The file /dev/allkmem is a special file that provides access to the virtual address space of the operating system kernel, including memory
that is associated with an I/O device. You can use any of these devices to examine and modify the system.
Byte addresses in /dev/mem are interpreted as physical memory addresses. Byte addresses in /dev/kmem and /dev/allkmem are interpreted as
kernel virtual memory addresses. A reference to a non-existent location returns an error. See ERRORS for more information.
The file /dev/mem accesses physical memory; the size of the file is equal to the amount of physical memory in the computer. This size may
be larger than 4GB on a system running the 32-bit operating environment. In this case, you can access memory beyond 4GB using a series of
read(2) and write(2) calls, a pread64() or pwrite64() call, or a combination of llseek(2) and read(2) or write(2).
ERRORS
EFAULT Occurs when trying to write(2) a read-only location (allkmem), read(2) a write-only location (allkmem), or read(2) or write(2) a
non-existent or unimplemented location (mem, kmem, allkmem).
EIO Occurs when trying to read(2) or write(2) a memory location that is associated with an I/O device using the /dev/kmem special
file.
ENXIO Results from attempting to mmap(2) a non-existent physical (mem) or virtual (kmem, allkmem) memory address.
FILES
/dev/mem Provides access to the computer's physical memory.
/dev/kmem Provides access to the virtual address space of the operating system kernel, excluding memory that is associated with an
I/O device.
/dev/allkmem Provides access to the virtual address space of the operating system kernel, including memory that is associated with an
I/O device.
SEE ALSO
llseek(2), mmap(2), read(2), write(2)
WARNINGS
Using these devices to modify (that is, write to) the address space of a live running operating system or to modify the state of a
hardware device is extremely dangerous and may result in a system panic if kernel data structures are damaged or if device state is
changed.
SunOS 5.11 18 Feb 2002 mem(7D)