You are not logged in.
Pages: 1
Topic closed
Pacman warnings:
warning: /etc/profile saved as /etc/profile.pacorig
warning: /etc/fstab saved as /etc/fstab.pacorig
warning: /etc/passwd saved as /etc/passwd.pacorig
warning: /etc/ld.so.conf saved as /etc/ld.so.conf.pacorig
warning: /etc/resolv.conf saved as /etc/resolv.conf.pacorig
warning: /etc/group saved as /etc/group.pacorig
warning: /etc/hosts saved as /etc/hosts.pacorig
warning: /etc/shadow saved as /etc/shadow.pacorig
warning: /etc/gshadow saved as /etc/gshadow.pacorig
$ sudo cp /etc/passwd.pacorig /etc/passwd
sudo: unknown uid: 1000
Any ideas? Thanks in advanced!!
Offline
Boot a live cd, mount the root fs and fix it from there.
And that is bizarre. Was it a result from pacman -Sf or maybe an ancient version of pacman?
Offline
Actually sounds like for some reason, the filesystems package was not in his local db, and therefor pacman moved the files when he updated/installed it from the repo.
Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest
Offline
I'm curious. What you were doing w/ pacman when this happened?
PLEASE read and try to FIX/FILE BUGS instead of assuming other have/will.
Offline
Shouldn't pacman save the new files as whatever.pacnew? This problem looks like the package filesystem was removed and pacman saved all the important files.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Boot a live cd, mount the root fs and fix it from there.
And that is bizarre. Was it a result from pacman -Sf or maybe an ancient version of pacman?
Thanks for your response . I did pacman -Sf. Unfortunately for me I only have an old copy of hardy.8.04 which doesn't support mounting ext4 and I have no blank cd's.... I'll have to get some tomorrow
Actually sounds like for some reason, the filesystems package was not in his local db, and therefor pacman moved the files when he updated/installed it from the repo.
I got an error, but I can't remember exactly what it said. Something about the pacman database being non-existent... Not sure why though because I haven't done anything to my pc recently
I'm curious. What you were doing w/ pacman when this happened?
I was just trying to update using pacman
Shouldn't pacman save the new files as whatever.pacnew? This problem looks like the package filesystem was removed and pacman saved all the important files.
Yep, it usually does
Anyway, thanks for all your responses
Offline
... I did pacman -Sf...)
Ooh..that is usually not a good idea, unless you know the possible resulting breakages and exactly how to fix them. Please don't use -Sf casually.
Offline
I still insint on ext3. Once I couldn't mount my fedora from a fedora rexcue disk, so ext4 was then over for me. ext3 is recoverable and mountable from down the hell straightly, and the most stable at all
Offline
I still insint on ext3. Once I couldn't mount my fedora from a fedora rexcue disk, so ext4 was then over for me. ext3 is recoverable and mountable from down the hell straightly, and the most stable at all
This may be true, I don't know.. but the only difference I have personally felt is the speed of fsck.
Offline
Doing continually with my installation, just root [enter] and you will enter on your root account.
My arch was fééé up just after installing snort!!!
Now, I will format , pacman is f** up I install packages only with --force, pacman -Q pacman gives nothing and now I can install the dual-core arch.
Offline
Offline
Pages: 1
Topic closed