Sponsored Content
Operating Systems SCO Sco UNIXware 7.1.4 error in booting Post 302961044 by jgt on Monday 23rd of November 2015 09:47:43 AM
Old 11-23-2015
When you list (ls -l) the contents of /mnt, does it look like a root file system?
Can you copy anything from /mnt to /tmp?

Many of the files in the root file system are links. Those links will not be correct when the file system is not mounted as /.
If it is possible to mount the non-root file systems, you might consider copying their contents to an offline device.
 

8 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

SCO Unixware 2.1

I am using SCO Unixware 2.1 & some PC clients are connected, suddenly one message appearslike : UX:strintercept error: dropping message this message starts coming repeatedly & agtre some time system hangs.I had to reset the system & now the problem is not there.Please suggest, why this is... (0 Replies)
Discussion started by: paprch
0 Replies

2. UNIX for Dummies Questions & Answers

SCO Unixware 7 download

According to this thread: https://www.unix.com/showthread.php?t=1 one guy says However, I cannot find any sco unixware7 iso download link in their download section (http://wdb1.sco.com/clbk_web/owa/dwn_customer), is it really for free, and if that is true, where can I download it? Thanks, (2 Replies)
Discussion started by: phalcos
2 Replies

3. SCO

Samba 3.0.24 in SCO UnixWare 7.1.4

Please help me in troubleshooting my problem in Samba? I tried to instal Samba 3.0.24 in our SCO UnixWare 7.1.4 but after installing the nmbd daemon is not running. When i check the syslog from /var/adm, the following error appears: Sep 30 13:04:22 unixeei nmbd: bind failed on port 137... (0 Replies)
Discussion started by: eric_hing
0 Replies

4. SCO

sco unixware + oracle 8.0.5

hi, anybody can give procedure for how to install oracle 8.0.5 in sco unixware 7.1.4. (0 Replies)
Discussion started by: prakrithi
0 Replies

5. UNIX for Dummies Questions & Answers

SCO Unixware 7.1.4 Network Adapter Error

Hi All I P2Vd a Unixware 7.1.4 box with VMWare Vsphere. I try to add a network adapter under Network Configuration Manager and it comes up with the error attached. I've added a virtual adapter using the "E1000" option. It detects both the AMD PCI NET and E1000 virtual adapters under Network... (8 Replies)
Discussion started by: flashinwrx
8 Replies

6. SCO

Noob needs help with Sco Unixware 7.1

We are retiring a Unixware 7.1 server that has custom applications on it. It has Raid 5 and we would like to use the machine for other things. Is there a way we can image/clone to virtual machine file and run that VM within say Virtual PC 2007 or VMware? I am not aware of anything to do this. I... (20 Replies)
Discussion started by: ccd1977
20 Replies

7. SCO

SCO Unixware 7.1.1 Install - Need help

(sorry my English, is really poor). I have a SCO Unixware 7.1.1 and I need install in ML350 G3. Reading in google and HP web, make a floppy disks for install, but the options that I have is for network or floppy disk. How install from CD with patch for HP smart array 532 ?? or How... (5 Replies)
Discussion started by: xplertor
5 Replies

8. SCO

My UnixWare SCO Server

Hi, I'm new to this Unix world and have taken over looking after the I.T side of things at work, which includes the internal ERP system which runs on a UNIX SCO platform. My initial worry is what state this is in as its been on site over 20 years. What would be the first things to check on... (13 Replies)
Discussion started by: Mick_Dundee
13 Replies
chroot(8)						      System Manager's Manual							 chroot(8)

NAME
chroot - Changes the root directory of a command SYNOPSIS
/usr/sbin/chroot directory command DESCRIPTION
Only root can use the chroot command. The chroot command changes the root directory from / to the specified directory when the command executes. (The command specified includes both the command name as well as any arguments.) Consequently, the root of any path (as indicated by the first / (slash) in the pathname) changes to directory and is always relative to the current root. Even if the chroot command is in effect, directory is relative to the current root of the running process. Several programs may not operate properly after chroot executes. You must ensure that all vital files are present in the new root file system and the relevant pathnames for the files map correctly in the new root file system. For example, the ls -l command fails to give user and group names if the new root file system does not have a copy of the /etc/passwd and /etc/group files. If the /etc/passwd and /etc/group files in the new root file system represent different user and group names, then the output from the ls -l command will be based on those names, not the ones for the system's own name database. Utilities that depend on description files produced by the ctab command may also fail if the required description files are not present in the new root file system. The chroot program uses the execv() function to invoke the specified command. As a consequence, the command specified must be an exe- cutable binary, not a shell script. Further, if the program requires indirect loading (for example, due to unresolved symbols requiring use of a shared library), then /sbin/loader as well as any files it requires (for example, shared libraries) must be present in the new root file system in the appropriate locations. EXAMPLES
To run a subshell with another file system as the root, enter a command similar to the following. Note in this example, the file system is on the /dev/disk/dsk13a device and is mounted to /mnt/dsk13a: chroot /mnt/dsk13a /sbin/sh The command shown in the previous example spec- ifies a change from the current root file system to the one mounted on /mnt/dsk13a while /sbin/sh (which itself is relative to the new root file system) executes. When /bin/sh executes, the original root file system is inaccessible. The file system mounted on /mnt/dsk13a must contain the standard directories of a root file system. In particular, the shell looks for commands in /sbin, /bin, and /usr/bin (among others) on the new root file system. Running the /sbin/sh command creates a subshell that runs as a separate process from the original shell. Press to exit the subshell and return to the original shell. This restores the environment of the original shell, including the meanings of the current directory (.) and the root directory (/). To run a command in another root file system and save the output on the initial root file system, enter a command similar to the following. Note in this example, the file system is on the /dev/disk/dsk13a device and is mounted to /mnt/dsk13a: chroot /mnt/dsk13a /bin/cc -E /u/bob/prog.c > prep.out The previous command runs the /bin/cc command with /mnt/dsk13a as the specified root file system. It compiles the /mnt/dsk13a/u/bob/prog.c file, reads the #include files from the /mnt/dsk13a/usr/include directory, and puts the compiled text in the prep.out file on the initial root file system. To create a file relative to the original root rather than the new one, use this syntax and enter: chroot directory command > file CAUTIONS
If special files in the new root have different major and minor device numbers than the initial root directory, it is possible to overwrite the file system. FILES
Specifies the command path. RELATED INFORMATION
Commands: cc(1), cpp(1), ls(1), sh(1) Functions: chdir(2), chroot(2) exec(2) delim off chroot(8)
All times are GMT -4. The time now is 05:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy