Login or Register to Ask a Question and Join Our Community


UNIX for Dummies Questions & Answers

[Solved] Not able to do a chroot.

 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers [Solved] Not able to do a chroot.
Prev   Next
# 1  
Old 01-24-2013
Ubuntu [Solved] Not able to do a chroot.
Hi all,

I have two doms on my machine. I boot my machine from an rfs in one dom1 and mount the other rfs in the other dom2 at /media. Now I wanted to restrict access of users on dom2 to only their home directories. I do not want them to access any other directories on dom1 or dom2. So I mounted the dom2 at /media, after booting from dom1, and changed the directory to /media. Now when I try to do a chroot ., it is giving an error
chroot: failed to run command `/bin/bash': No such file or directory

Can anybody help me please?

Waiting for a reply. Thank you in advance.

Thanks and Regards,
Sai.
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Red Hat

Chroot DNS RHEL6

Hi, Just installed BIND on rhel6 as a primary new DNS server and all went well, digging and resolving as it should. However, all zone files are listed in the /var/named dir as well as the /var/named/chroot/var/named. Although no dynamic links are shown, they are. This doesn't seem secure to me,... (2 Replies)
Discussion started by: Duffs22
2 Replies

2. AIX

sftp chroot + winbind + ad

I have next configuration : - AIX 5.3 (5300-11-03-1013) - pWare.SAMBA 3.5.8.1 - OpenSSH 5.2.0 - OpenSSL 0.9.8 Now, to be more clearly I'll explain what I need indeed. My task is set up integration AIX server to Active Directory 2008 with Samba (Winbind) for chrooted SSH connections. It... (3 Replies)
Discussion started by: jess_t03
3 Replies

3. Solaris

BIND in chroot

Hi all, I'm trying to start named in chroot environment manually but i'm getting the following error bash-3.00# cat /etc/release Solaris 10 6/06 s10s_u2wos_09a SPARC Copyright 2006 Sun Microsystems, Inc. All Rights Reserved. Use is... (1 Reply)
Discussion started by: h@foorsa.biz
1 Replies

4. Solaris

chroot Issues on Solaris

Hello Friends, I am trying the chroot command on a Solaris box (SunOS sx07 5.10 Generic_144489-12 i86pc i386 i86pc) but i am getting an error message chroot: exec failed: Exec format error Did any of you folks got this error before .. and how did you guys fix it .. please help me... (2 Replies)
Discussion started by: sudharma
2 Replies

5. AIX

DNS with chroot in aix 5.3

i am planning to configure the DNS server with restricted environment by chroot. Can anybody help me that what are all the filesets required to configure DNS with Chroot for aix 5.3 os. And also i need to run the bind with non root user. How can i configure that. I tried googling and... (1 Reply)
Discussion started by: kmvinay
1 Replies

6. Solaris

openssh and chroot.

Hi all. I have installed openssh 5.3 and set up jailed root. It works almost as I want it to I cant cd to any directory above my ch root. my config : entry in passwd: test2:x:103:113::/users2/test2:/bin/false sshd_conf: Match User test2 ChrootDirectory /users2/%u # ... (4 Replies)
Discussion started by: vettec3
4 Replies

7. UNIX for Dummies Questions & Answers

How to start a chroot jail?

I was reading an article on how it is very important to setup a chroot jail to run bind. I can follow what the article says but one thing I am unclear about is now on system boot the BIND process in the chroot jail will start since it the owner will no longer be root but some other user. Can... (1 Reply)
Discussion started by: mojoman
1 Replies

8. UNIX for Advanced & Expert Users

CHRoot Problem

HI , I am trying to setup chrooted environment on RHEL4, for squid proxy. I have copied the required libraries and stuff for chroot. Used the below for chroot-shell . user is squid # grep squid /etc/passwd squid:x:500:501::/opt/squid:/bin/chroot-shell directory trying to jail is... (2 Replies)
Discussion started by: Crazy_murli
2 Replies

9. AIX

chroot environment

Hi!! I'm currently running AIX 4.3.3 and i'm trying to setup a chroot environment for the users who use SFTP, i spend a lot time SFTW but i can't make it work. I got openssh3.9p1 whit the chroot patch. Any help is greatly appreciated. (0 Replies)
Discussion started by: samurai79
0 Replies

10. Linux

chroot?

If i were to create a new user for my ftp would chroot be the proper command to set there root directory as the file i've put all my FTP stuff in? Also would that jail them, or would they beable to get out of the set directory? (0 Replies)
Discussion started by: byblyk
0 Replies
Login or Register to Ask a Question

LEARN ABOUT OPENSOLARIS

systemd-machine-id-commit.service

SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)			 systemd-machine-id-commit.service		      SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)

NAME

       systemd-machine-id-commit.service - Commit a transient machine ID to disk

SYNOPSIS

       systemd-machine-id-commit.service

DESCRIPTION

       systemd-machine-id-commit.service is an early boot service responsible for committing transient /etc/machine-id files to a writable disk
       file system. See machine-id(5) for more information about machine IDs.

       This service is started after local-fs.target in case /etc/machine-id is a mount point of its own (usually from a memory file system such
       as "tmpfs") and /etc is writable. The service will invoke systemd-machine-id-setup --commit, which writes the current transient machine ID
       to disk and unmount the /etc/machine-id file in a race-free manner to ensure that file is always valid and accessible for other processes.
       See systemd-machine-id-setup(1) for details.

       The main use case of this service are systems where /etc/machine-id is read-only and initially not initialized. In this case, the system
       manager will generate a transient machine ID file on a memory file system, and mount it over /etc/machine-id, during the early boot phase.
       This service is then invoked in a later boot phase, as soon as /etc has been remounted writable and the ID may thus be committed to disk to
       make it permanent.

SEE ALSO

       systemd(1), systemd-machine-id-setup(1), machine-id(5), systemd-firstboot(1)

systemd 237												      SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)