You are not logged in.
Would it be possible to take an existing installation and effectively reinstall all packages, restore all configuration files to their default config as if on a new install on that program, and wipe all user data (probably not in that order) so as to restore a system to a kind of "first boot" setting but with your current package listing retained.
How would one go about this? Could one slip into a terminal, sudo rm -r /some/folders/here (what folders necessary?) and then use pacman to reinstall ... everything (what kind of command would get you that? something with a grep listing?)
Offline
Pacman doesn't know about files created by the packages after they were installed, so you would have to monitor them yourself.
You can reinstall and bring back the default settings if the settings are shipped with the package.
That would effectively mean you need to configure your system from scratch, so why not just reinstall or use a backup?
Offline
I suppose you could delete all the files in ~/.config (as well as any other hidden files in your home folder) but it could be risky...
Plus you still might not get all of the config files that aren't stored in home, hmm
Last edited by Reded (2012-07-29 12:04:01)
"Some humans would do anything to see if it was possible to do it. If you put a large switch in some cave somewhere, with a sign on it saying "End-of-the-World Switch. PLEASE DO NOT TOUCH", the paint wouldn't even have time to dry."
Offline
As your system ages, the desire to do this should diminish.
As a partial step, one could create a new user. Logging in as the new user would give you just the system defaults.
Or, since disk storage is relatively cheap for most machines, why not repartition and create a new skeleton installation to use for comparisons? A list of the packages you've installed from the normal repos can be generated with
pacman -Qqe | grep -Fvx "$(pacman -Qqm)" > package_listA list of locally installed packages, those from the AUR and your own, can be generated with
pacman -Qqm > local_package_listOffline
Logging in as the new user would give you just the system defaults.
Unless you use a ton of system-wide configs ;P
The problem of using a backup or hard drive image of your pristine installation is that Arch changes pretty fast and a 6-month-old installation would need a bit of work to get up to speed.
Offline
thisoldman wrote:Logging in as the new user would give you just the system defaults.
Unless you use a ton of system-wide configs ;P
The problem of using a backup or hard drive image of your pristine installation is that Arch changes pretty fast and a 6-month-old installation would need a bit of work to get up to speed.
Correct me if I'm wrong but wouldnt a pacman -Syu do most of the job?
Offline
karol wrote:thisoldman wrote:Logging in as the new user would give you just the system defaults.
Unless you use a ton of system-wide configs ;P
The problem of using a backup or hard drive image of your pristine installation is that Arch changes pretty fast and a 6-month-old installation would need a bit of work to get up to speed.
Correct me if I'm wrong but wouldnt a pacman -Syu do most of the job?
Depends on what changed in Arch in the meantime, what changes you made and what do you mean by 'most of the job'.
Let's say you've made your backup a couple months ago and now you want to move from grub-legacy to syslinux, install KDE and try systemd. If you revert to said backup in a month, you will have to do a few important changes "manually" because at the time of that backup you were using grub, initscripts and e.g. Gnome.
Reverting to the "clean slate" backup, updating it and making a fresh backup once you've tested the new configuration shouldn't be much of a problem but it's not automatic. You may need to perform some manual conflict resolution etc. (see the home page).
Offline
r3bel wrote:karol wrote:Unless you use a ton of system-wide configs ;P
The problem of using a backup or hard drive image of your pristine installation is that Arch changes pretty fast and a 6-month-old installation would need a bit of work to get up to speed.
Correct me if I'm wrong but wouldnt a pacman -Syu do most of the job?
Depends on what changed in Arch in the meantime, what changes you made and what do you mean by 'most of the job'.
Let's say you've made your backup a couple months ago and now you want to move from grub-legacy to syslinux, install KDE and try systemd. If you revert to said backup in a month, you will have to do a few important changes "manually" because at the time of that backup you were using grub, initscripts and e.g. Gnome.
Reverting to the "clean slate" backup, updating it and making a fresh backup once you've tested the new configuration shouldn't be much of a problem but it's not automatic. You may need to perform some manual conflict resolution etc. (see the home page).
This is exactly why I wanted to strip the system clean and let the programs act as if this were a new install, without changing my partition table, have to download 12 gigs of data, etc. Reinstall the system without a format. Some of these changes that needed manual adjustment have caused a bit of a headache, it would be nice to have a nuclear option without having to reinstall. Especially now that AIF isn't around anymore I'd have to have a second computer to tell me what commands to run just to get things going again...
Offline
This is exactly why I wanted to strip the system clean and let the programs act as if this were a new install, without changing my partition table, have to download 12 gigs of data, etc. Reinstall the system without a format. Some of these changes that needed manual adjustment have caused a bit of a headache, it would be nice to have a nuclear option without having to reinstall. Especially now that AIF isn't around anymore I'd have to have a second computer to tell me what commands to run just to get things going again...
Why not just save /var/cache/pacman/pkg contents and then do a fresh install. That saves the data download, at least. And since you already have an Arch system presumably you'd know how to do the reinstall quickly.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
I'd have to have a second computer to tell me what commands to run just to get things going again...
I haven't done a new installation in a while, but you don't need a second computer.
The last time, I downloaded 'links' from core and ran it on one terminal while I performed the installation on another. Another method is shown here: https://wiki.archlinux.org/index.php/In … ting_Linux
Offline