Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 1
    Not to “create the file descriptors” (that doesn't make any sense). To create the file. It isn't read that opens a file for writing (that would be silly), it's <<<. Commented Nov 2, 2013 at 23:59
  • @Gilles - thanks, I didn't quite understand what it was telling me. Cleaned up the A. Commented Nov 3, 2013 at 0:19
  • Thank you very much! A very nice technique, which might even help me multiple times in the future with similar issues. However, one thing is worrying me, and that is the fact that /tmp is a hardcoded path. And probably you've guessed it, /tmp IS there already, but read-only as well! And since working on that recovery console will have me logged into my live file system, I would not want to mess in there by symlinking or whatever (not even while in that console). Commented Nov 3, 2013 at 11:04