Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Skywave LiveCD after cloning to HDD is still RO #1

Open
Szewcson opened this issue Sep 22, 2022 · 8 comments
Open

Skywave LiveCD after cloning to HDD is still RO #1

Szewcson opened this issue Sep 22, 2022 · 8 comments

Comments

@Szewcson
Copy link
Contributor

Can't upgrade cloned system.

@Szewcson
Copy link
Contributor Author

Sorry, I jus realize that there was 2 new commits since I last try to install skywave. I will try toomorow if now it works.

@Szewcson
Copy link
Contributor Author

Szewcson commented Sep 23, 2022

Ok, still system after cloning is in ro and can't be upgraded. Now also X not working. Don't know maybe my change with mounting /sys causing the problem but without it chrooted system can't see system partition.

@AB9IL
Copy link
Owner

AB9IL commented Sep 24, 2022

Hello Szewcson,
What error message do you get when X fails to run?

@Szewcson
Copy link
Contributor Author

xset:  unable yo open display ""
xset:  unable yo open display ""
xset:  unable yo open display ""

and after startx:

xauth:  error in locking authority file /home/skywave/.Xauthority
xauth:  error in locking authority file /home/skywave/.Xauthority
(EE)
Fatal server errorr:
(EE)  Cannot move old log file "/home/skywave/.local/share/xorg/Xorg.0.log" to "/home/skywave/.local/share/xorg/Xorg.0.log.old"
(EE)
(EE)
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
(EE)
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
xauth:  error in locking authority file /home/skywave/.Xauthority

@Szewcson
Copy link
Contributor Author

Szewcson commented Sep 25, 2022

I'm using skywave 4.3.0 flashback since I have some problems with i3 in vm.

@AB9IL
Copy link
Owner

AB9IL commented Sep 26, 2022

Those messages resemble the sequence sent from the system if the home folder and its contents are owned by root . If you can get a working prompt as root or chroot into the system, use "chown -R" to set the home folder ownership to your regular user:

chown -R skywave:skywave /home/skywave

Edit: /home is owned by root, but users own their own directories. So if you create a new user named "joe" then /home/joe is owned by joe (and the group for it is also "joe").

@Szewcson
Copy link
Contributor Author

Szewcson commented Sep 26, 2022

Ok, I will check it but I think it should be handled by script during chroot. I think that adding user creation and changing root password will be good feature.

@Szewcson
Copy link
Contributor Author

I tried from console and got many errors that fs is ro. Then I tried using chroot but after boot everything was the same.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants