>> >> This is not needed... Don't believe the hype. With, or
>> >> without devfsd, you can
>> >>
>> >> chmod
>> >> chown
>> >> ln -s
>> >> ls -l
>> >> mkfifo /tmp/hda && (cat /dev/hda > /tmp/hda &) && strings /tmp/hda >
>> >> /dev/null && echo "DUH"
>> >>
>> >> All you want.
>> > Until you reboot.
>>
>> No, Mr Frost, this issue has been addressed. Devfsd
>> gives persistance.
> #1: If you chmod a file in /dev, devfsd does not save that change
> as I understand it (Unless you change your happy config
> file).
> #2: The way it did at one point (Using a tarball) was slimy to
> say the least. I don't know if it still uses a tarball,
> some say it does, others that it doesn't. If it doesn't,
> then what is it doing to save, say, links?
> Either way, it's something that is not a real filesystem trying to
> pretend it is. The problem of permissions being associated w/
> files was dealt with quite a while ago and has worked for a rather
> long time, why try and invent a new way?
To make it workable with new system. Why new system is needed ? Read devfs FAQ.
If you'll be able to write WORKING code to solve all problems and keep old
solution with permissions all (including me) will be happy. So far I've not
seen such code. For TWO YEARS now.
-
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/