unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: coralgoat--- via <help-guix@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Help Guix <help-guix@gnu.org>
Subject: Re: Stuck at scheme prompt when booting
Date: Tue, 15 Feb 2022 21:38:09 +0100 (CET)	[thread overview]
Message-ID: <Mvz5pFE--B-2@tuta.io> (raw)
In-Reply-To: <87mtivsphb.fsf@elephly.net>

Thank you for sharing those commands.

I was able to start bash but at that point in the start up process chattr is not available.

Feb 12, 2022, 22:08 by rekado@elephly.net:

>
> coralgoat--- via <help-guix@gnu.org> writes:
>
>> I have some more information to add to my initial message.
>>
>> I have opened the computer to make sure the hard drive has a good
>> connection to the motherboard and it does.
>>
>> I have also tried typing `,bt` at the "scheme@(guile-user)>" prompt
>> the output is included below.  Note  there is a solid white square 
>> single character symbol in the output and I am representing it as
>>  "***" in the output below.
>>
>> The line in the output that catches my attention is:
>> "1 (copy-file "/etc/static/resolv.conf" "/etc/resolv.conf")"
>>
>
> This file is generated every time Guix System boots.  Most of the system
> is instantiated anew on every boot.  This also includes creating user
> accounts.
>
> Having a file there that cannot be modified is indeed the problem here.
>
>> I think that if I ran the command `chattr -i /etc/resolv.conf` it
>> might fix the problem and allow the system to boot however I get an
>> error when I try typing that at the scheme prompt.
>>
>> Any suggestions on how I should get a Linux console terminal so I can
>> enter the `chattr -i /etc/resolv.conf` command?
>>
>
> (system* "/gnu/store/…-bash/bin/bash")
>
> but for that to work you’d have to know the hash.  Dependent on how far
> along the boot process has come along you may already have
> /run/current-system/profile/bin/bash, so try
>
>  (system* "/run/current-system/profile/bin/bash")
>
> This gives you a proper shell.
>
> You may also have chattr in that location, so you could do this
> directly:
>
>  (system* "/run/current-system/profile/bin/chattr" "-i" "/etc/resolv.conf")
>
> -- 
> Ricardo
>


  reply	other threads:[~2022-02-15 20:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09 16:00 Stuck at scheme prompt when booting coralgoat--- via
     [not found] ` <MvUCoKH--7-2@tuta.io-MveXQCV----2>
2022-02-12 19:15   ` coralgoat--- via
2022-02-12 22:08     ` Ricardo Wurmus
2022-02-15 20:38       ` coralgoat--- via [this message]
2022-02-15 20:51         ` Ricardo Wurmus
2022-02-15 21:53           ` coralgoat--- via
2022-02-12 23:11     ` SeerLite
2022-02-15 20:46       ` coralgoat--- via

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=Mvz5pFE--B-2@tuta.io \
    --to=help-guix@gnu.org \
    --cc=coralgoat@tuta.io \
    --cc=rekado@elephly.net \
    /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).