Linux Hotplug development
 help / color / mirror / Atom feed
From: Allin Cottrell <cottrell@wfu.edu>
To: linux-hotplug@vger.kernel.org
Subject: Re: update path for undev + systemd
Date: Sun, 15 Jan 2012 22:45:37 +0000	[thread overview]
Message-ID: <alpine.DEB.2.00.1201151737080.9663@myrtle> (raw)
In-Reply-To: <alpine.LNX.2.01.1201151539210.14830@waverley.dhcp.wfu.edu>

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



      parent reply	other threads:[~2012-01-15 22:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-15 20:52 update path for undev + systemd Allin Cottrell
2012-01-15 21:30 ` Kay Sievers
2012-01-15 22:45 ` Allin Cottrell [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.00.1201151737080.9663@myrtle \
    --to=cottrell@wfu.edu \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox