From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: [RFC] Rollback FS
Date: Fri, 25 Oct 2013 20:22:05 +0100 [thread overview]
Message-ID: <20131025192205.GA15583@sauron> (raw)
Hi,
> Recently, I just do some stupid stuffs as follows.
>
> # mv /lib/x86_64-linux-gnu/libc.so.6 /tmp
>
> After move "/lib/x86_64-linux-gnu/libc.so.6" away, you could not run lots
> of commands, which show you some errors like this.
>
> # ls
> ls: error while loading shared libraries: libc.so.6: cannot open
> shared object file: No such file or directory
> # mv
> mv: error while loading shared libraries: libc.so.6: cannot open
> shared object file: No such file or directory
Well we all do stupid things sometimes... I done similar to you once, but copied (and overwrote) a different version trying to fix something...
/sbin/sln is your friend (if you don't panic when it happens). No need for a large vfs to monitor user errors like this.
/sbin/sln is a statically built ln, so you can symlink back the file to get userspace going, then copy the file (fix it) back properly.
Nick
--
FSF Associate Member 5508
http://linicks.net/
next reply other threads:[~2013-10-25 19:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 19:22 Nick Warne [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-20 7:06 [RFC] Rollback FS jiaweiwei
2013-10-20 7:57 ` Richard Weinberger
2013-10-20 11:33 ` jiaweiwei
2013-10-20 10:22 ` Kristof Provost
2013-10-20 11:41 ` jiaweiwei
2013-10-20 10:43 ` Vyacheslav Dubeyko
2013-10-20 11:37 ` jiaweiwei
2013-10-20 11:46 ` Richard Weinberger
2013-10-20 12:32 ` Vyacheslav Dubeyko
2013-10-20 12:35 ` Theodore Ts'o
2013-10-20 12:59 ` jiaweiwei
2013-10-20 13:07 ` Levente Kurusa
2013-10-20 13:19 ` jiaweiwei
2013-10-20 13:26 ` Levente Kurusa
2013-10-20 15:22 ` jiaweiwei
2013-10-22 14:29 ` Levente Kurusa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131025192205.GA15583@sauron \
--to=nick@linicks.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.