Edgy LiveCD : unexpected volatility & persistance of files

Unless I'm mistaken, you should just be able to restart and everything will be fine. Unfortuntely, this really isn't a bug, unless I misinterpreted what you are saying, in which case, please reopen.

Thanks for your reply.

Maybe this was not clear enough. So..

Keep in mind that my use for the Edgy LiveCD is as a "one session only" Ubuntu system. I don't install Edgy at all.

So "restarting" is not an option.

I just expect commands to behave as they should. In the example given, the mv command does not :/
I suggest that you give a try to reproducing what I described.

Please reconsider.

I agree that it stinks that the mv command is getting stumped, but your trying to move active kernel files, its like, trying to remove a heart and getting upset about the veins that are still attached. (ok, far too gory a metaphore, but I'm surrounded by med students at the moment) In short, those files are still being accessed and cannot be moved until release, which will not be until the kernel has shut down. :( sorry!

I understand your point. But on an installed system, things would not behave this way. On an installed Edgy, the system would not prevent you from doing "gory" stuff via sudo :)

In this perspective, a "LiveCD session" is not a "true" Ubuntu Edgy session. Playing in a terminal with basic commands does not give results conforming to what common sense expects.

To explain further what I am bothered with:

I use the LiveCD to test deb packages of mine. In these, the installation scripts succeed, but the effects are not as expected with respect to the underlying filesystem.

To me, this should be at least signaled somewhere. It took me time to figure out that the problem was not the quality of my deb packages, but rather a lower level issue related to the "LIVEness".