[arch-dev-public] final leg of /lib removal

Dave Reisner d at falconindy.com
Tue Jul 3 12:22:35 EDT 2012


On Tue, Jul 03, 2012 at 06:11:16PM +0200, Thomas Bächler wrote:
> Am 03.07.2012 18:05, schrieb Dave Reisner:
> > On Tue, Jul 03, 2012 at 05:48:43PM +0200, Thomas Bächler wrote:
> >> Am 03.07.2012 17:41, schrieb Dave Reisner:
> >>> BIG SCARY NOTE: Due to the kmod changes, this will BREAK all module
> >>> tools for users with their own kernels. If you do not rebuild your
> >>> kernel after pulling in the new kmod, you're going to have a bad time.
> >>> See the paste link above for inspiration.
> >>
> >> This worries me, a lot. Can't we get a smoother upgrade path?
> > 
> > Not really.
> > 
> > We could patch all things using kmod (udev and kmod's tools) to look
> > in both /usr/lib as well as /lib, but that's ugly and doesn't really do
> > us any good.
> > 
> > We could make this rebuild coincide with the glibc rebuild to get rid of
> > /lib, but you can't install glibc with /lib as a symlink until
> > /lib/modules doesn't exist. The only way /lib/modules doesn't exist is
> > if people with custom kernels rebuild them into /usr/lib/modules.
> 
> Okay.
> 
> Why do we want /lib as a symlink to /usr/lib anyway? You could have the
> directory /lib, only containing the symlinks for ld-linux.so.2 ->
> /usr/lib/ld-linux.so.2 and ld-linux-x86_64.so.2 ->
> /usr/lib/ld-linux-x86_64.so.2 (and, of course
> /lib64/ld-linux-x86_64.so.2 for compatibility).
> 
> I don't see any advantage in having the symlink /lib -> /usr/lib, except
> a harder upgrade path where so many things could go wrong.
> 

No offense, but you're a bit late to be trying to shoot this down only
now. Perhaps you recall Tom's post (and ensuing discussion) from a few
months ago:

http://www.mail-archive.com/arch-dev-public@archlinux.org/msg19028.html

With a followup:

http://mailman.archlinux.org/pipermail/arch-dev-public/2012-March/022756.html

Maybe the wiki page that detailed the plan:

https://wiki.archlinux.org/index.php/DeveloperWiki:UsrMove

Or when we started on this with todolist 143:

https://www.archlinux.org/todo/143/

And did more of this with todolist 148:

https://www.archlinux.org/todo/148/

What's the point of doing 95% of this and then polishing it off with
some silly hack? /lib64 is already going away and turning into a symlink
with the glibc-2.16 package in [staging].

d

P.S. i686 rebuilds are done -- I've moved this all to brynhild to avoid
the bandwidth restrictions on gerolde:

http://pkgbuild.com/~dreisner/linux-usrmove/


More information about the arch-dev-public mailing list