From: Piter Punk <piterpk@terra.com.br>
To: linux-hotplug@vger.kernel.org
Subject: Re: NEWBIE - Upgrading udev
Date: Wed, 24 Aug 2005 14:33:15 +0000 [thread overview]
Message-ID: <430C852B.4030900@terra.com.br> (raw)
In-Reply-To: <430C8342.10809@wiggly.org>
Nigel Rantor wrote:
> 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?
Use the udev package in slackware current. It works fine now.
You can found the package in any slackware mirror, one of the fastest
is www.slackware.at.
Good Luck
Piter PUNK
--
____________
/ Piter PUNK \_____________________________________________________
| |
| | E-Mail: piterpk@terra.com.br (personal) |
| .|. roberto.freires@gds-corp.com (professional) |
| /V\ |
| // \\ UIN:116043354 Homepage:www.openslack.org/~piterpk |
| /( )\ |
| ^`~'^ ----> Slackware Linux - The Best One! <---- |
| #105432 |
`-------------------------------------------------------------------'
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-08-24 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 14:25 NEWBIE - Upgrading udev Nigel Rantor
2005-08-24 14:33 ` Piter Punk [this message]
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=430C852B.4030900@terra.com.br \
--to=piterpk@terra.com.br \
--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;
as well as URLs for NNTP newsgroup(s).