*** This mailing list is moving ***
*** http://curl.haxx.se/mail/ ***
(CC'ed to old list)

> That been said, chroot'ed environments will as a general rule have to make
> sure that everything it needs is, in fact, available inside the chroot'ed
> environment itself. Sometimes hard links can help, e.g.
> ln /etc/resolv.conf /chroot/etc/resolv.conf or something.

You're absolutely right about that (though mknod is better than a hard link
since a hard link will not work across file systems). But the thing is, as
I'm sure you know, the reason for using chroot is to basically cut yourself
off from the outside world. The more files you have to link, the more you
reduce the security benefits that chroot gives. And since, at least in my
opinion, the reading of /etc/resolv.conf is only really needed to be done
one time (at startup), it seems foolish and wasteful to require such a link
when it really isn't needed.

Dominick Meglio

-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
Received on 2004-02-05