In message <[EMAIL PROTECTED]>, Warner Losh writes:
>In message <14760.981228917@critter> Poul-Henning Kamp writes:
>: In message <[EMAIL PROTECTED]>, Warner Losh writes:
>: >In message <[EMAIL PROTECTED]> Peter Wemm writes:
>: >: As bizzare as it sounds, I like Julian's hack for populating this stuff...
>: >: ie: use a hard link to propagate nodes to the jailed /dev.
>: >:
>: >: eg: mount -t devfs -o empty /home/jail/dev
>: >: ln /dev/null /home/jail/dev/null
>: >: ln /dev/zero /home/jail/dev/zero
>: >: ...
>: >: mount -u -o ro /home/jail/dev
>: >
>: >But you can't do hard links accross file systems. Or is that a hack
>: >of devfs to allow it, [...]
>:
>: Yes, it was a hack, and it will not be hacked that way in my DEVFS.
>
>I seem to recall talking to you about having symbolic links in your
>devfs mean something "special" as a way around this problem.
No that was another, and probably too avant garde idea Julian and I
have discussed:
Basically device-drivers create devices in a private
namespace, in /dev you link from the filesystem namespace
to the private namespace with a kind of symbolic link.
It has too many "issues" with standards and VOP's to be viable
right now.
Doing straight symlinks would not work.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
