update path for undev + systemd

update path for undev + systemd

[Allin Cottrell]

I wonder if there's a recommended path/method for updating 
from udev 175 + systemd 37 to the current versions? Given the 
reorganization of files in both packages it's quite easy to 
end up with a fscked system (as I did today -- system not 
bootable; had to boot from CD, remove the new versions and 
reinstall the old).

With udev one can force the use of the old /lib/udev location 
by giving --with-rootlibdir=/lib --libexecdir=/lib, but I 
didn't find a way of making current git systemd install into 
/lib/systemd; even configuring with --with-rootlibdir=/lib, 
all files that used to go into /lib/systemd go into 
/usr/lib/systemd.

In principle I have no problem with everything going under 
/usr/lib, it's just that it seems the chances of a successful 
update would be better if the old files were overwritten 
rather than the new ones being installed in parallel.

Thanks for any guidance.

-- 
Allin Cottrell
Department of Economics
Wake Forest University, NC

Re: update path for undev + systemd

[Kay Sievers]

On Sun, Jan 15, 2012 at 21:52, Allin Cottrell <cottrell@wfu.edu> wrote:
> I wonder if there's a recommended path/method for updating from udev 175 +
> systemd 37 to the current versions? Given the reorganization of files in
> both packages it's quite easy to end up with a fscked system (as I did today
> -- system not bootable; had to boot from CD, remove the new versions and
> reinstall the old).
>
> With udev one can force the use of the old /lib/udev location by giving
> --with-rootlibdir=/lib --libexecdir=/lib, but I didn't find a way of making
> current git systemd install into /lib/systemd; even configuring with
> --with-rootlibdir=/lib, all files that used to go into /lib/systemd go into
> /usr/lib/systemd.
>
> In principle I have no problem with everything going under /usr/lib, it's
> just that it seems the chances of a successful update would be better if the
> old files were overwritten rather than the new ones being installed in
> parallel.

Udev and systemd are in full sync with the configure options now.

You better read NEWS in the udev tree, and not just install new things
in a running system and hope all works. :)

Check out the examples in the INSTALL file in the udev tree, it's
--with-rootprefix= which specifies if stuff installs in /usr or /.

Kay

Re: update path for undev + systemd

[Allin Cottrell]

On Sun, 15 Jan 2012, Kay Sievers wrote:

> On Sun, Jan 15, 2012 at 21:52, Allin Cottrell <cottrell@wfu.edu> wrote:
>> I wonder if there's a recommended path/method for updating from udev 175 +
>> systemd 37 to the current versions? Given the reorganization of files in
>> both packages it's quite easy to end up with a fscked system (as I did today
>> -- system not bootable; had to boot from CD, remove the new versions and
>> reinstall the old). [...]
>
> Udev and systemd are in full sync with the configure options now.
>
> You better read NEWS in the udev tree, and not just install new things
> in a running system and hope all works. :)

I had in fact read udev's NEWS and acted accordingly, i.e. changed 
the --libexecdir= configure line, installed libkmod, etc. (I was 
already up to date in respect of devtmpfs and /run). I don't think 
my booting problem lay with udev, but rather with systemd, whose 
package contains no docs pertaining to configuring/installing or 
changes from the previous version.

Allin Cottrell