Re: [aur-general] [arch-dev-public] final leg of /lib removal

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On Jul 3, 2012 8:18 PM, "Dave Reisner" <d@xxxxxxxxxxxxxx> wrote:
>
> On Tue, Jul 03, 2012 at 07:56:32PM +0200, Ike Devolder wrote:
> > Op dinsdag 3 juli 2012 11:41:08 schreef Dave Reisner:
> > > Hey all,
> > >
> > > *** If you use a custom kernel, this will affect you. Please read the
> > > big scary note at the end ***
> > >
> > > I'm taking today to work on the last roadblock before Allan can move
> > > glibc out of /lib. This basically consists of a rebuild of:
> > >
> > > - kmod (to drop our local patch)
> > > - linux, linux-lts (diff for linux here: http://paste.xinu.at/LLd/)
> > > - all OOT kernel modules (for /usr/lib/modules/extramodules-*)
> > > - bash-completion (temp patch until /lib is a symlink:
> > > http://paste.xinu.at/xEs/)
> > >
> > > I'll be doing this all locally to avoid building against allan's new
> > > toolchain in [staging]. This will hopefully all hit [testing] by the
> > > end of the day. You know where to find me if you have any questions or
> > > angry rants.
> > >
> > > If you'd like to do some early testing, I'm leaving the rebuilt kmod
and
> > > kernel packages on gerolde:
> > >
> > > http://dev.archlinux.org/~dreisner/linux-usrmove/
> > >
> > > (i686 packages are lagging behind at the moment)
> > >
> > > 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.
> > >
> > > Cheers!
> > > Dave
> >
> > I'm replying on this in arch-general and aur-general because i cant
post in
> > arch-dev.
> >
> > So if i understand correctly we (the people running custom kernels)
can't
> > prepare for this ?
>
> I posted the new kmod package here explicitly so that users can get this
> package in preparation... I'll post it again since I changed the server
> I'm hosting these on:
>
> updated URL: http://pkgbuild.com/~dreisner/linux-usrmove/
>
> > There is no way of moving the modules already to /usr/lib ? I assume
kmod now
> > only looks in /lib.
>
> Currently, kmod is patched to respect config dirs in /usr/lib, but
> modules in /lib. After removing the patch, it uniformly searches
> /usr/lib for everything (I'm intentionally ignoring /etc and /run here).
>
> > Another note, people with custom repositories should move their kernels
in
> > sync with the official repositories ?
> >
> > --Ike
>
> As with any large change, I'll mention on dev-public when this goes to
> testing, and there will be an associated news item when it moves to
> core.

And a post upgrade message from kmod?

> I realize this is a harsh change, but I don't really have many
> options for doing this more smoothly. If you're using the stock kernel,
> this should all just work. mkinitcpio has supported this setup for
> months now, and I've had my own kernel in /usr/lib/modules for almost as
> long.
>
> Worst case scenario, users of custom kernels can:
>
> - manually move /lib/modules/mycustomkernel to /usr/lib/modules/ until
>   they can do a proper rebuild.
> - boot a stock -ARCH kernel (you DO have it listed as a fallback,
>   right?) until they can do a proper rebuild.
>
> Emphasis on "until they can do a proper rebuild". It's important that
> this all gets done before we introduce a new glibc package that wipes
> out /lib entirely. If you have custom kernel bits lying around in
> /lib/modules, it's going to block the eventual glibc upgrade that brings
> this (no, it won't be immediately with 2.16).
>
> dave


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux