All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nigel Rantor <wiggly@wiggly.org>
To: linux-hotplug@vger.kernel.org
Subject: NEWBIE - Upgrading udev
Date: Wed, 24 Aug 2005 14:25:06 +0000	[thread overview]
Message-ID: <430C8342.10809@wiggly.org> (raw)


Hi all,

I've been trying to get a more recent kernel to work on my boxen and 
have found that it requires a later version of udev than I currently 
have installed.

I'm not exactly sure if this is the reason that things aren't working 
but I can't really go further on the lkml without checking that my 
versions of everything are up-to-date.

I realise that udev is fairly critical in terms of being able to get a 
working system so I'm reluctant to just go ahead and make the upgrade 
without having some idea of the likelyhood of buggering my box to oblivion.

Currently running 2.6.7-rc3 on a Slackware 10.1 install that comes with 
udev 050, 2.6.13-rc6 requires udev 058.

So, my question is, how easy is it going to be for me to kill my box? 
Any tips on upgrading udev?

Cheese,

   n



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

             reply	other threads:[~2005-08-24 14:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-24 14:25 Nigel Rantor [this message]
2005-08-24 14:33 ` NEWBIE - Upgrading udev Piter Punk
2005-08-24 16:49 ` Nigel Rantor

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=430C8342.10809@wiggly.org \
    --to=wiggly@wiggly.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.