Follow-up Comment #3, bug #29920 (project gnustep):
The error message is surely a bit misleading.
I think it should be possible to read files on synthesized virtual
filesystem. I have checked and different Linux installations on diffrent
computers share the same "problem". I'd say it is currently a "bug-feature"
instead of just an error.
I can try to add additional code to handle this special case. Maybe it is
just sensible to remove the check for certain files.
The first question is, however, how to recognize we are treating a special
file? Could checking for the first path element to be /sys a possible idea? It
is a bit "broad" perhaps?
I don't see a property on the file itself to identify it, however!
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?29920>
_______________________________________________
Messaggio inviato con/da Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
