Yes, things break.
Symlinked ls doesnt work anymore ... kinda but it
was my mistake. Actually, no things seem to break
here for me when I mount sysfs somewhere else.
mount -t sysfs /System
Does not work
mount -t sysfs none /System
Works but my ls is broken
EDIT: Ok found out... i had kept /System
special dir. I now tried it with /System2
and System2 got populated
Seems to work, die /sys die die die!
There is however a problem
I cannot create new dirs in /System
nor in /sys
mkdir: cannot create directory `foo': Operation not permitted
Anyone knows how to allow creation of dirs there?
Ok I didnt bother to look at the reason, but it seems to be
to create or touch etc.. do anything with a sysfs
mounted directory. I had a look at Gobolinux and indeed,
it had the same "problem" (its only a problem if you, as user,
want to create dirs in that mounted target).
On Gobolinux they do another indirection, they do:
--> sysfs is mounted on /System/Kernel/Objects
And thus get away with having an IMHO better directory
structure. The fact still remains that you cant create
anything there hmm. Which means that I cant easily create
a /System directory there, as I will not be able to
manipulate it at all.
So I probably will use an indirection similar to how
Gobolinux does it as well.
Well, I guess my question is somehow solved