PS:

https://wiki.archlinux.org/index.php/arch_filesystem_hierarchy

It does link to https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-inte... ;)

Am 07.03.2014 07:49, schrieb Cao, Renzhi (MU-Student):

Now, for my problem, is there any way to repair that? Or you think I should reinstall my arch linux system?

I am not a fan of reinstalling only to fix the system, but you should update more frequently ;) Chroot into your system, then look into /bin, /sbin and /usr/sbin, there shouldnt be any files. You can try then pacman -S filesystem Good luck!

I think you should boot with an Arch Installer, then chroot and try to fix your system removing the package that has files on those directories, following the steps on the Arch news about this issue. An then update again. I think that this will solve your trouble. Andrés Fernandez Software Peronista El 07/03/2014 04:13, "Caorenzhi" <rcrg4@mail.missouri.edu> escribió:

Hi, there are some files in /sbin,/usr/sbin. Should I just remove them directly and then run pacman -s filesystem? I find out that I cannot access the internet this time, can I still use that command?

Sent from my iPhone

On Mar 7, 2014, at 1:07, Simon Brand <simon.brand@postadigitale.de> wrote:

...

Am 07.03.2014 07:49, schrieb Cao, Renzhi (MU-Student):

...

Now, for my problem, is there any way to repair that? Or you think I should reinstall my arch linux system?

I am not a fan of reinstalling only to fix the system, but you should update more frequently ;)

Chroot into your system, then look into /bin, /sbin and /usr/sbin, there shouldnt be any files. You can try then pacman -S filesystem

Good luck!

On Friday 07 Mar 2014 08:46:02 Caorenzhi wrote:

Thank you for your good suggestion! I think I can use pacman to remove the packages, however, I cannot connect to Internet after chroot, so cannot use pacman to update. Do you have any idea?

Assuming you can plug your computer in with an ethernet cable, you could try: # ip link set eth0 up # dhcpcd eth0 That will hopefully give you access to the internet. Paul

On Friday 07 Mar 2014 09:12:39 Caorenzhi wrote:

Thank you Paul, I will check it in my lab later and tell you the details. I try add ip eth0 yesterday , and the system says there is no eth0.

In that case, you need to do: # ip link to see a list of your network interfaces. It might not be called eth0, but hopefully one of them will correspond to the wired interface, assuming this is a computer that can in fact be plugged in with a cable. Paul

Am 07.03.2014 08:13, schrieb Caorenzhi:

Hi, there are some files in /sbin,/usr/sbin. Should I just remove them directly and then run pacman -s filesystem? I find out that I cannot access the internet this time, can I still use that command?

Sent from my iPhone

On Mar 7, 2014, at 1:07, Simon Brand <simon.brand@postadigitale.de> wrote:

...

Am 07.03.2014 07:49, schrieb Cao, Renzhi (MU-Student):

...

Now, for my problem, is there any way to repair that? Or you think I should reinstall my arch linux system?

I am not a fan of reinstalling only to fix the system, but you should update more frequently ;)

Chroot into your system, then look into /bin, /sbin and /usr/sbin, there shouldnt be any files. You can try then pacman -S filesystem

Good luck!

Where are these files from? Are they from some AUR packages? You can check this with pacman -Qo /path/to/file Do NOT remove then. If they are from AUR packages, remove them, update filesystem and then reinstall them. You could probably try to move them to /usr/bin and then update. You need the internet to download the new filesystem package. You could download it on another system, check the signature, copy it to the broken system and then install it with pacman -U /path/to/package You should know best, how to access the internet in your network. The livesystem only trys to dhcpcd, do you have WLan?

Hi, Continue previous email, I think the warning of "core" does not exists if fixed. I try this command: #pacman -Syu mkinitcpio systemd linux Finally, it shows: error: failed to commit transaction (conflicting files) filesystem: /bin exists in filesystem filesystem: /sbin exists in filesystem filesystem: /usr/sbin exists in filesystem Errors occurred, no packages were upgraded. I try : #pacman -Qqo /bin /sbin /usr/sbin | pacman -Qm – ( based on the instruction from: https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-inte...) I get the following information: sysvinit-tool 2.88-9 lilo 23.2-3 grub-common 2.00-1 sysvinit-tool 2.88-9 lilo 23.2-3 How can I fix this? I checked the /bin,/sbin,/usr/sbin, I find out the following file may contain the package need to fixed: /sbin/lilo /usr/sbin/liloconfig /usr/sbin/lilo-uuid-diskid /usr/sbin/grub-bios-setup, grub-mkconfig,ofpathname,reboot,sparc64setup,install,mknetdir,probe,set-default #find /bin /sbin /usr/sbin -exec pacman -Qo -- {} + >/dev/null , have no output I don't have any packages in IgnorePkg or IgnoreGroup. Thank you all. Renzhi Cao Email : rcrg4@mail.missouri.edu ________________________________________ From: arch-general <arch-general-bounces@archlinux.org> on behalf of Cao, Renzhi (MU-Student) <rcrg4@mail.missouri.edu> Sent: Friday, March 7, 2014 3:52 PM To: General Discussion about Arch Linux Subject: Re: [arch-general] Problems of using pacman and updating the filesystem Hi, Before my system crash, I try this link: https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-inte... And I only get few non-official packages in /bin, /sbin, usr/sbin: sysvinit-tool 2.88-9 lilo 23.2-3 grub-common 2.00-1 sysvinit-tool 2.88-9 lilo 23.2-3 Today, I use arch chroot to the system, and run : #pacman -Qqo /bin /sbin /usr/sbin | pacman -Qm – I get a long list, for a lot of files: grub common 2.0.0 lilo 23.2-3 linux-atm 2.5.2-2 openssh 6.2p1-1 ppp 2.4.5-4 sudo syslinux vpnc util-linux wireless_tool ..... A lot, I cannot list all of them. And I try this command: #find /bin /sbin /usr/sbin -exec pacman -Qo -- {} + >/dev/null I get the warning: Warning: database file for "core" does not exist Warning: database file for "extra" does not exist Warning: database file for "community" does not exist By the way, the network problem is fixed, now my system can connect to the internet to download packages. What should I do now? Should I use mv command to move all files in /bin,/sbin,/usr/sbin to /usr/bin directly? Can I still update the filesystem in this case? Thank you all helping me. Renzhi Cao Email : rcrg4@mail.missouri.edu ________________________________________ From: arch-general <arch-general-bounces@archlinux.org> on behalf of Simon Brand <simon.brand@postadigitale.de> Sent: Friday, March 7, 2014 1:23 AM To: General Discussion about Arch Linux Subject: Re: [arch-general] Problems of using pacman and updating the filesystem Am 07.03.2014 08:13, schrieb Caorenzhi:

Hi, there are some files in /sbin,/usr/sbin. Should I just remove them directly and then run pacman -s filesystem? I find out that I cannot access the internet this time, can I still use that command?

Sent from my iPhone

On Mar 7, 2014, at 1:07, Simon Brand <simon.brand@postadigitale.de> wrote:

...

Am 07.03.2014 07:49, schrieb Cao, Renzhi (MU-Student):

...

Now, for my problem, is there any way to repair that? Or you think I should reinstall my arch linux system?

I am not a fan of reinstalling only to fix the system, but you should update more frequently ;)

Chroot into your system, then look into /bin, /sbin and /usr/sbin, there shouldnt be any files. You can try then pacman -S filesystem

Good luck!

Where are these files from? Are they from some AUR packages? You can check this with pacman -Qo /path/to/file Do NOT remove then. If they are from AUR packages, remove them, update filesystem and then reinstall them. You could probably try to move them to /usr/bin and then update. You need the internet to download the new filesystem package. You could download it on another system, check the signature, copy it to the broken system and then install it with pacman -U /path/to/package You should know best, how to access the internet in your network. The livesystem only trys to dhcpcd, do you have WLan?

Yes, I try pacman -Su, and they said the /usr/sbin is exists. I am thinking that is ok, so I reboot the system. I have a cd to load the system, and I have another computer to download packages and have a external hard disk to use, like copy files there. Is there still any way to solve my problem? Thank you so much! Sent from my iPhone On Mar 7, 2014, at 3:06, Thomas Bächler <thomas@archlinux.org> wrote:

Am 07.03.2014 07:06, schrieb Cao, Renzhi (MU-Student):

...

After this, I use the following command to update the system: pacman -Syu --ignore filesystem,bash pacman -S bash

and then reboot, get the following information:

And why didn't you complete the instructions by running 'pacman -Su' before rebooting?

Now you broke it, and you need to fix it with a live system.

That is my fault. Do I also need to remove files in /usr/bin as you said? Or you mean /usr/sbin, /sbin, /bin? Since that is what I see the error from at beginning. There are a lot of files in /sbin, should I remove all of them? Let me check my system in my lab and I will reply you later for details, thank you very much! Sent from my iPhone On Mar 7, 2014, at 8:58, Thomas or Bächler <thomas@archlinux.org> wrote:

Am 07.03.2014 15:51, schrieb Caorenzhi:

...

Yes, I try pacman -Su, and they said the /usr/sbin is exists. I am thinking that is ok, so I reboot the system.

The instructions explicitly stated that this is NOT okay.

...

I have a cd to load the system, and I have another computer to download packages and have a external hard disk to use, like copy files there. Is there still any way to solve my problem?

Sure there is.

Boot from a recent Arch Linux live CD, mount your file systems to /mnt and run arch-chroot /mnt /usr/bin/bash

Then make sure there are no files left in /usr/sbin, /sbin and /usr/bin - most likely, you need to uninstall a package that you built yourself - you can properly rebuild it later and install it again. Or you need to uninstall a package that used to be part of Arch, but it no longer needed.

When you are done, pacman -Su should work flawlessly (the package is already in your cache, so no network is required). To be safe, run 'mkinitcpio -P' so your system boots correctly.

Thank you! I remember when I run the command to find out the packages I should remove, it shows: lilo, grub-common, initvlinux( something like this), but I don't know how to move them to /usr/bin. I try directly mv lilo to /usr/bin, and use the command to search which package I should remove, it seems the lilo is still there. And I don't know which files belong to initvlinux, or grub-common, there are a lot of files start with grub- , I am afraid I remove it wrongly. Sent from my iPhone On Mar 7, 2014, at 9:15, Thomas Bächler <thomas@archlinux.org> wrote:

Am 07.03.2014 16:09, schrieb Caorenzhi:

...

Do I also need to remove files in /usr/bin as you said? Or you mean /usr/sbin, /sbin, /bin?

You are right, only files in /bin, /sbin and /usr/sbin should be gone. Everything should be in /usr/bin after the update.

...

Since that is what I see the error from at beginning. There are a lot of files in /sbin, should I remove all of them?

You should find out which packages they belong to and either uninstall or fix those packages!

On Fri, 2014-03-07 at 16:21 +0000, Paul Gideon Dann wrote:

If the last time you updated was before 2012-11-04, there's a good chance you never made the switch to systemd, which will make things even harder for you.

... for several reasons, e.g. eth0 likely will become enp3s0.

On Fri, 2014-03-07 at 16:15 +0100, Thomas Bächler wrote:

You are right, only files in /bin, /sbin and /usr/sbin should be gone. Everything should be in /usr/bin after the update.

JFTR if I build packages for private usage, I prefer to install to /usr/local/bin, /usr/local/sbin, those packages won't cause issues.

Hi, it seems your method is really complex. Is there any simple way? For my case, do you know how to fix the problem of lilo and grub-common? Sent from my iPhone On Mar 7, 2014, at 17:18, Nowaker <enwukaer@gmail.com> wrote:

It seems OP is already done, but I hope this will by useful for anyone struggling to upgrade a VERY old Arch Linux.

Warning: this is only for experienced users. Beginners do the backups and install Arch from scratch.

Before proceeding, be sure to have several ssh sessions, logged as root. Don't rely on sudo. If your session dies in the middle of the process, LiveCD and VNC will be your only help. SSH won't let you in because it won't be able to exec the shell.

pacman -Sy pacman -Sd pacman-static coreutils-static #1 sed -i 's@PackageRequired@Never #PackageRequired@' /etc/pacman.conf #2 pacman -Syu #3 pacman -Su --ignore filesystem,glibc,gcc-libs,gcc-libs-multilib pacman-static -Sd glibc --ignore filesystem #4 pacman-static -S filesystem pacman-static -S gcc-libs gcc libtool pacman -S pacman libarchive package-query pacman -S ca-certificates #5 pacman -Syu pacman -S mkinitcpio grub systemd #6 mkinitcpio -p linux grub-mkconfig -o /boot/grub/grub.cfg sed -i 's@Never #PackageRequired@PackageRequired@' /etc/pacman.conf

Why pacman-static? Because during the process you will end up with a broken system that is not able to execute anything because of mismatch between glibc (will be newer) and libraries (will be older). You won't be able to call pacman at some stage, so you need a statically compiled pacman.

Why coreutils-static? Just in case. No binary from coreutils is used in my guide, but if anything happens - static coreutils is your rescue. Find them in /rescue/bin.

During the process you may see lots of errors reported by pacman - cannot exec, or something like that. You can't help this. If a package does some important stuff in .install script, you should reinstall the package after the process yourself.

#1 I have these packages in my private repo; you need to build them yourself from AUR. https://aur.archlinux.org/packages/pacman-static/ https://aur.archlinux.org/packages/coreutils-static/

#2 In a (temporarily) broken Arch Linux, pacman can't check signatures because it's either trying to execute or dynamically link some library. It won't work. We have to disable signature checking.

#3 It will fail; done just to download all files to disk.

#4 glibc used to own the directories that currently filesystem owns; we upgrade glibc to get rid of these directories, so filesystem can be installed smoothly in the next step

#5 Depending on how old your Arch is, it's possible that ca-certificates's .install script was not properly run when -Syu was performed, so it has to be done again.

#6 In case they contain something important in .install which could fail during the first -Syu

-- Kind regards, Damian Nowak StratusHost www.AtlasHost.eu

On 8 March 2014 02:23, Doug Newgard <scimmia22@outlook.com> wrote:

----------------------------------------

...

From: rcrg4@mail.missouri.edu Date: Fri, 7 Mar 2014 19:30:59 -0600 To: arch-general@archlinux.org Subject: Re: [arch-general] Problems of using pacman and updating the filesystem

Hi, it seems your method is really complex. Is there any simple way? For my case, do you know how to fix the problem of lilo and grub-common?

Sent from my iPhone

Yeah, but either updating them to something that's actually in the repos or by updating the PKGBUILD to not put files in the old dirs and rebuild. s:but:by:

To clarify -- grub-comon is now simply grub (grub itself was dropped to the AUR some time ago, and grub2 was renamed 'grub' in it's place). If you are using grub2 as your boot loader, install the "grub" package from your chroot, and remove the lilo and grub-common packages. If you are booting with lilo, remove grub-common and update lilo.(now at 24.0-3 in the AUR). WorMzy

On 8 March 2014 03:29, Cao, Renzhi (MU-Student) <rcrg4@mail.missouri.edu> wrote:

I am not sure which one is used as my boot loader, could you please tell me how to check that? I am thinking using this following command:

#pacman -Rs lilo #pacman -Rs grub-common #pacman -S grub

Is that correct? Thank you so much!

Renzhi Cao

Email : rcrg4@mail.missouri.edu

You are new to Arch Linux, but you have an Arch Linux system that pre-dates the usr-bin move from over seven months ago? :/ You don't even know what boot loader you're using?? Give up with this installation. Reinstall Arch from an up-to-date installation media, and follow the beginner's guide. I think you will learn more by doing this than trying to fix your current installation. Regards, WorMzy

On Sat, Mar 08, 2014 at 03:56:28AM +0000, Cao, Renzhi (MU-Student) wrote:

I plan to use : dd if=/dev/hda bs=512 count=1 2>&1 | grep GRUB dd if=/dev/hda bs=512 count=1 2>&1 | grep LILO

to check the bootloader I have. I am really new to arch linux, but I want to fix that problem. It seems I almost fix the problem, just solve the lilo and grub-common problem. If I reinstall arch linux, that could be more difficult for me, and I am afraid of losing my data in the system.

Renzhi Cao

Email : rcrg4@mail.missouri.edu

________________________________________

Well, obviously you're going to make backups before you go about messing with highly sensitive parts of your system, especially when using dd, right? And take my word, and the word of every other Archer for it: If reinstalling by following the *Beginner's Guide* is too difficult for you, the previously posted, advanced update guide will be much harder, and Arch is likely not the right distribution for you.

On 03/08/2014 11:53 AM, Cao, Renzhi (MU-Student) wrote:

Hi, I can reinstall the system any time, but I can learn more when trying to fix the problem. Thank you very much! Ah. Sorry. I didn't read this before I posted.

But I will say this while I'm here. Yes. You can learn a lot by going through the fix. But, believe me, you'll have plenty of opportunities to learn systemd once you get your system up and going! So don't think your learning opportunities are over. :-) It just depends on how soon you want to get on with it. Again. Good luck. -- Kinney

On Sat, 2014-03-08 at 17:49 +0000, Cao, Renzhi (MU-Student) wrote:

By the way, I am thinking the upgrading process will only influence the system, not my data partition. I still need suggestions, am I think that correct? Or lack of experience.

Correct, but accidents happen, so _backup_ your data.

On Sat, 2014-03-08 at 17:49 +0000, Cao, Renzhi (MU-Student) wrote:

...

By the way, I am thinking the upgrading process will only influence the system, not my data partition. I still need suggestions, am I think that correct? Or lack of experience.

Correct, but accidents happen, so _backup_ your data.

On Sat, 2014-03-08 at 17:58 +0000, Cao, Renzhi (MU-Student) wrote:

Ok, I have about 2T data there, I need to go by a external disk to back up the data, and then updating the system. Thank you

Sorry for my broken English. I guess "accidents happen" does mean that sometimes data is touched by upgrades, but it isn't. I wanted to say that when fixing a broken install, then you could make a mistake, an accident, that will damage your data. Btw., please don't top post,

On Sat, Mar 08, 2014 at 06:08:32PM +0000, Cao, Renzhi (MU-Student) wrote:

I see, so I can continue upgrading the system. This time, I only want to upgrade the system, and rebuild the kernel. When I need other operations, I will backup all data first. I will continue posting, thank you!

Renzhi Cao

Email : rcrg4@mail.missouri.edu http://web.missouri.edu/~rcrg4/

________________________________________ From: arch-general <arch-general-bounces@archlinux.org> on behalf of Ralf Mardorf <ralf.mardorf@alice-dsl.net> Sent: Saturday, March 8, 2014 12:04 PM To: arch-general@archlinux.org Subject: Re: [arch-general] Problems of using pacman and updating the filesystem

...

On Sat, 2014-03-08 at 17:49 +0000, Cao, Renzhi (MU-Student) wrote:

...

By the way, I am thinking the upgrading process will only influence the system, not my data partition. I still need suggestions, am I think that correct? Or lack of experience.

Correct, but accidents happen, so _backup_ your data.

On Sat, 2014-03-08 at 17:58 +0000, Cao, Renzhi (MU-Student) wrote:

...

Ok, I have about 2T data there, I need to go by a external disk to back up the data, and then updating the system. Thank you

Sorry for my broken English. I guess "accidents happen" does mean that sometimes data is touched by upgrades, but it isn't. I wanted to say that when fixing a broken install, then you could make a mistake, an accident, that will damage your data.

Btw., please don't top post,

No, not "please don't stop posting," but rather "please don't top post." In other words, your responses should be at the bottom of the e-mail so that people can read from the top down and understand what's going on. Good luck! -- David J. Haines djhaines@gmx.com 0xAFB3D16D - F929 270F B7C3 78AE A741 434F A7C6 F264 AFB3 D16C

On Sat, 2014-03-08 at 12:40 -0500, Kinney Baughman wrote:

you could already have a new box up and running, one that you can be sure is trim and solid

and you will not learn something useful, if you try to repair your broken install. You will learn what to do and forget what you learned, because you won't need to do this things that often. Better make a new install and then update your Arch more often. From time to time take a look at the news on https://www.archlinux.org/ .

Thank you. Could you give me more details about updating them? I am new to arch linux, can I try to uninstall them, and later after my problem solved, install the new one by pacman? Renzhi Cao Email : rcrg4@mail.missouri.edu ________________________________________ From: arch-general <arch-general-bounces@archlinux.org> on behalf of Doug Newgard <scimmia22@outlook.com> Sent: Friday, March 7, 2014 8:23 PM To: General Discussion about Arch Linux Subject: Re: [arch-general] Problems of using pacman and updating the filesystem ----------------------------------------

From: rcrg4@mail.missouri.edu Date: Fri, 7 Mar 2014 19:30:59 -0600 To: arch-general@archlinux.org Subject: Re: [arch-general] Problems of using pacman and updating the filesystem

Hi, it seems your method is really complex. Is there any simple way? For my case, do you know how to fix the problem of lilo and grub-common?

Sent from my iPhone

Yeah, but either updating them to something that's actually in the repos or by updating the PKGBUILD to not put files in the old dirs and rebuild.