unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Roman Scherer <roman.scherer@burningswell.com>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: Felix Lechner <felix.lechner@lease-up.com>,
	Tobias Geerinckx-Rice <me@tobias.gr>,
	help-guix@gnu.org
Subject: Re: Too many levels of symbolic links
Date: Wed, 15 Mar 2023 19:22:20 +0100	[thread overview]
Message-ID: <87h6ul98io.fsf@burningswell.com> (raw)
In-Reply-To: <ZBGu6aKan8EnlMv6@3900XT>

[-- Attachment #1: Type: text/plain, Size: 1825 bytes --]


Good to know about that unspoken rule. :) Should we do something about
that? I thought about adding a note to the manual. Or even not allowing
the user to re-configure in such a case?

WDYT?

Efraim Flashner <efraim@flashner.co.il> writes:

> [[PGP Signed Part:Undecided]]
> On Tue, Mar 14, 2023 at 08:16:52PM +0100, Roman Scherer wrote:
>>
>> Felix, I'm back on track! I found what triggered this horrible problem :)
>>
>> At some point I added the qemu-binfmt-service-type to my system. I
>> copied a snipped from the manual and finally "adjusted" it to this:
>>
>> ```
>> (define %qemu-service
>>   (service qemu-binfmt-service-type
>>            (qemu-binfmt-configuration
>>             (platforms (lookup-qemu-platforms "aarch64" "x86_64")))))
>> ```
>>
>> I don't know much about quem and I thought, well let's choose the
>> "aarch64" and "x86_64" qemu platforms on which I run Guix, and maybe
>> re-use this service on multiple machines.
>>
>> My Guix system runs on the aarch64 architecture. It turns out that
>> having "aarch64" in lookup-qemu-platforms causes the "Too many levels of
>> symbolic links" error. As soon as I remove it, everything is good again.
>>
>> Now, maybe it does not even makes sense to add "aarch64" to that list,
>> but I think it should not fail that catastrophical. I still don't know
>> which symlink was causing this issue, though.
>>
>> That's where I am. Just happy that I survived my first serious Guix
>> crash. :)
>>
>> Thanks for your help so far,
>>
>> Roman
>
> I'm surprised that it worked for you. One of the unspoken rules of qemu
> binfmt emulation is you don't emulate your own hardware. I'm also
> surprised because in the past I tried to enable binfmt emulation on my
> pinebook pro and the qemu-binfmt-service-type was the difference between
> booting and not booting.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 528 bytes --]

  reply	other threads:[~2023-03-15 18:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-05 16:19 Too many levels of symbolic links Roman Scherer
2023-03-05 16:43 ` Felix Lechner via
2023-03-05 16:53   ` Roman Scherer
2023-03-05 17:11     ` Felix Lechner via
2023-03-05 17:22     ` Tobias Geerinckx-Rice
2023-03-10 15:28       ` Roman Scherer
2023-03-10 17:10         ` Felix Lechner via
2023-03-14 19:16           ` Roman Scherer
2023-03-15 11:41             ` Efraim Flashner
2023-03-15 18:22               ` Roman Scherer [this message]
2023-03-15 11:56             ` Tobias Geerinckx-Rice

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h6ul98io.fsf@burningswell.com \
    --to=roman.scherer@burningswell.com \
    --cc=efraim@flashner.co.il \
    --cc=felix.lechner@lease-up.com \
    --cc=help-guix@gnu.org \
    --cc=me@tobias.gr \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).