Don' borked asahi linux. Part 2: SUDO boogaloo.

[Rocketing-warp9]

Hi all!

When I was tampering. Around with the Mac' later on, I realized that I did not place this account in the sudoers file before deleting the other account.
Drat.
Now, I have entered into the back door recovery mode by placing init=/bin/bash after the Linux string on GRUB,
And am being faced with this when I press CTRL D---

Apparently it does not exist?

Any ideas on how to get this into the sudoers file?

 

[CaffeineAddict]

I have entered into the back door recovery mode by placing init=/bin/bash

Not an expert but I suppose you did that for recovery entry instead of normal entry in GRUB?
Can you run this command as root:

systemctl start dbus

It should get rid of the red error.

It appears some essential system services aren't running in your boot mode.

 

[Rocketing-warp9]

Not an expert but I suppose you did that for recovery entry instead of normal entry in GRUB?
Can you run this command as root:

This was done of the regular Fedora startup, As for some reason it did not install a recovery entry into the GRUB side of the system.

Bash:
systemctl start dbus

Alrighty! Will report back! thanks!

 

[osprey]

Hi all!

When I was tampering. Around with the Mac' later on, I realized that I did not place this account in the sudoers file before deleting the other account.
Drat.
Now, I have entered into the back door recovery mode by placing init=/bin/bash after the Linux string on GRUB,
And am being faced with this when I press CTRL D---


View attachment 32175
Apparently it does not exist?

Any ideas on how to get this into the sudoers file?

Another way to boot into recovery is to append: init=/bin/bash rw.
That mounts / as read-write. To obtain sudo rights for a user, one can amend the /etc/sudoers file and the
/etc/group file, or, depending on what the default is in the /etc/sudoers file, just the /etc/group file amendment may be sufficient.

For example, if the config: %sudo ALL=(ALL:ALL) ALL, is set in the /etc/sudoers file, then all members of the sudo group in /etc/group, can use sudo. For example, the default on this machine includes:

# Allow members of group sudo to execute any command
%sudo    ALL=(ALL:ALL) ALL

All that's needed in that case is to add the user to the sudo group in /etc/group. In emergency mode, to add the user to the sudo group, you can try and run:

/usr/sbin/usermod -a -G sudo <username>

If that doesn't work, and I've not gone that route, rather I have just written the user name in the /etc/group, for example:

/usr/bin/vi /etc/group
.
.
sudo:x:27:<username>
.

Ensure that the username is written. Then run the following commands to exit gracefully:

mount -o remount,ro /
sync
sync
/sbin/reboot -f

In emergency mode, it's best to use the full paths of the executables to avoid possible ambiguities. The above also assumes that /usr/bin and /usr/sbin are in the root partition under /.

 

[Rocketing-warp9]

sadly, before I was able to try it out, it nuked itself on startup again....

I so called "pressed the Big Red Button" and nuked the install off as I can retry again.
But- now I have a mOS partition dilemma (for some reason, the installer shrinks mOS only and not install to free space.

I'll report back once it's on.

 

[theLegionWithin]

everyone borks an install eventually. it's a rite of passage.

 

[Rocketing-warp9]

Alrighty! Asahi Linux is reinstalled. Just have to come up with some way to back it up if the Updates lock out again.

Hard to do with limited storage options..