Horst von Brand writes:
> Bingo! Keep devices in inodes on disk. To do persistence right, you'll have
> to keep them in inodes on disk anyway... so this whole kludge can go.
> Solves the different devices visible with different permissions in
> different chroot(2)s too, without any extra effort.
>
> You know, there were flamewars about this exact point around devfs for
> _years_... and no magic solution came forth, not even an idea for a
> workable solution.
My, you have a selective memory. I've proposed more than one workable
solution to this:
- tar/untar (it may not appeal to you, and it doesn't appeal to me
that much either, but it will do the job)
- set permissions in /etc/devfsd.conf, edit to change
- configure devfsd to automatically save/restore (possible *right
now*, although requires configuring, I could provide a canned
solution to make it easier)
- tunnel through to the underlying disc-based FS we're mounted over.
You personally might not like some or all of them, but they do/will
*work*. They will get the job done.
Horst, I don't care if you agree with my view or not. But you're
debating style leaves a lot to be desired. Frankly, it's slimey and
intellectually dishonest. Makes me wonder how much you cheated to get
your PhD.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Apr 15 2000 - 21:00:21 EST