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

Support an already installed system #49

Closed
Torxed opened this issue Sep 7, 2020 · 3 comments
Closed

Support an already installed system #49

Torxed opened this issue Sep 7, 2020 · 3 comments
Labels
feature New feature or request

Comments

@Torxed
Copy link
Member

Torxed commented Sep 7, 2020

Assuming the following, that someone runs the scripts/library on a docker installation or re-running it after already performing an installation. It would be nice if the installer could run again and run different profiles scenarios. But that requires the mount points to be pointed towards the correct place.

Which, perhaps the archinstall.Installer() should take care of.

@Torxed Torxed added the feature New feature or request label Sep 7, 2020
@Torxed
Copy link
Member Author

Torxed commented Oct 16, 2020

Clarification: If something happens during the installation, archinstall.Installer() should not re-mount or re-open encrypted drives during a re-run. Or perhaps a template should be created called python -m archinstall patch --packages=XXX --mountpoint=/mnt. (Just a thought I wanted to put down)

@Torxed Torxed added this to the v2.1.2 milestone Jan 22, 2021
@Torxed Torxed modified the milestones: v2.1.2, v2.1.4 Mar 20, 2021
@Torxed
Copy link
Member Author

Torxed commented Mar 20, 2021

As this would require quite a bit of work and debugging, and it's not essential for day to day operations. I'm moving this up two versions.

@Torxed
Copy link
Member Author

Torxed commented Mar 29, 2021

Putting this on the back burner for now as the point of it is getting less and less relevant hehe.
Creating a example-profile that does the workload sounds more appealing.

@Torxed Torxed closed this as completed Mar 29, 2021
@Torxed Torxed removed this from the v2.1.4 milestone Mar 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant