From: Michael Hampicke <gentoo-user@hadt.biz>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] nano in install-amd64-minimal-20121013.iso broken?
Date: Mon, 15 Oct 2012 23:41:25 +0200 [thread overview]
Message-ID: <507C8305.4030901@hadt.biz> (raw)
In-Reply-To: <507C641E.8090703@gmail.com>
Am 15.10.2012 21:29, schrieb Jarry:
> On 15-Oct-12 21:18, Michael Hampicke wrote:
>
>>> livecd gentoo # nano -w /mnt/gentoo/etc/portage/make.conf
>>> nano: error while loading shared libraries: libmagic.so.1:
>>> cannot open shared object file: No such file or directory
>>> livecd gentoo #
>>>
>>> So what am I supposed to do now? Seems to me nano is broken...
>>
>> Use another editor - like vi(m) - or just chroot into /mnt/gentoo and
>> run nano from there. It does not matter if you edit make.conf before or
>> after chrooting.
>
> I already chrooted. So it means nano in stage3 is broken?
> Concerning vi, it is 10 years since I used it for the last time!
> Do not even remember how to save file after editing... :-(
I just downloaded stage3-amd64-20121013.tar.bz2 and tried it. nano
inside the chroot works just fine here. Maybe you should check your
stage3 / iso file. See section 2.c of the gentoo handbook [1].
If the checksums don't match, just downloaded the files again, if the
checksums are ok, just try emerge --sync && emerge nano inside the chroot.
[1] http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?full=1
next prev parent reply other threads:[~2012-10-15 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 18:33 [gentoo-user] nano in install-amd64-minimal-20121013.iso broken? Jarry
2012-10-15 19:18 ` Michael Hampicke
2012-10-15 19:29 ` Jarry
2012-10-15 21:41 ` Michael Hampicke [this message]
2012-10-20 15:30 ` AleiPhoenix (A.K.A Areverie)
2012-10-21 5:17 ` Jarry
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=507C8305.4030901@hadt.biz \
--to=gentoo-user@hadt.biz \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox