Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#33589 - symlink /bin to /usr/bin and /sbin to /usr/sbin

Attached to Project: Arch Linux
Opened by Joseph Lutz (CipherWizard) - Sunday, 27 January 2013, 05:51 GMT
Last edited by Allan McRae (Allan) - Sunday, 27 January 2013, 06:22 GMT
Task Type Feature Request
Category Arch Projects
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
archlinux does not allow /bin and /sbin to be symlinks to /usr/bin and /usr/sbin. I request the packages be modified to allow this type of configuration.

Additional info:
* package version(s)
dhcpcd 5.6.4-1
iproute2 3.6.0-2
systemd-sysvcompat 197-4
bash 4.2.042-2

* config and/or log files etc.


Steps to reproduce:
I was following along the steps in the Beginners' Guide. After I mounted the all my file-systems I created two symlinks. I set up /bin to point to /usr/bin and /sbin to /usr/sbin. I then continued along through the tutorial. The first noticed there was a problem when I ran the mkinitcpio script. The script was unable to find the depmod program. (/usr/bin/mkinitcpio: line 333: depmod: command not found)
I noticed there were problems with my symlinks. In the bin and sbin directories there were symlinks that were using relative paths. Therefore those links were broken. There were also circular symlinks. Examples of the circular symlinks are the ip and the dhcpcd commands. The file /usr/sbin/ip was a symlink to /sbin/ip. This ended up pointing to itself.
I was able to get my system up and running with base and base-devel installed after fixing a few symlinks. I also had to uninstall packages, create /sbin, re-install the packages, copy programs to /usr/sbin, and recreate the /sbin symlink. This will work until one of the packages that were causing the problem had an upgrade. At that point the upgrade would not install.
This task depends upon

Closed by  Allan McRae (Allan)
Sunday, 27 January 2013, 06:22 GMT
Reason for closing:  Deferred
Additional comments about closing:  We have to provide conflicts in /bin and /usr/bin etc to prepare to make these symlinks official.
Comment by Daniel Wallace (gtmanfred) - Sunday, 27 January 2013, 05:56 GMT Comment by Allan McRae (Allan) - Sunday, 27 January 2013, 06:21 GMT
Our packages - particularly bash and glibc - are preparing for this change, but it does make it difficult for those who want to modify theirs systems so that /bin, /sbin and /usr/sbin are symlinks now. Until we official move to do this, you will need to fix the packages that have the same file in /bin and /usr/bin and so on...

pacman-4.1 will hopefully be released soon, and then we can handle this transition.

Loading...