From: Moshe Yudkowsky <msha5_17@bl.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev /boot/img "was been altered"
Date: Tue, 03 Jan 2006 14:46:26 +0000 [thread overview]
Message-ID: <43BA8E42.1010608@bl.com> (raw)
In-Reply-To: <43B0B27D.2070504@bl.com>
Scott James Remnant wrote:
> On Mon, 2005-12-26 at 21:18 -0600, Moshe Yudkowsky wrote:
>
>
>>I'd like a quick hint: after udev updates, I get an error message that
>>reads:
>>
>>/boot/initrd.img-2.6.14-2-k7 was been altered. Cannot update.
>>
>
> This is an Ubuntu-specific problem, you should raise future problems
> like this with appropriate Ubuntu forums.
Actually, I run Debian unstable. Based on your comment and others, next
time I'll look at the Debian install scripts. Thanks for the
information. And I promise to try Ubuntu as soon as I have some free
time. :-)
> The fix is simple, install one of the 2.6.15 kernel packages.
Debian (?) seems to have fixed this install problem even in 2.6.14; I'll
verify the next time a udev update comes along.
--
Moshe Yudkowsky
work: http://www.Disaggregate.com
book: http://www.PebbleAndAvalanche.com
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
_______________________________________________
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
prev parent reply other threads:[~2006-01-03 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-27 3:18 udev /boot/img "was been altered" Moshe Yudkowsky
2005-12-27 4:00 ` Greg KH
2006-01-03 8:10 ` Scott James Remnant
2006-01-03 14:46 ` Moshe Yudkowsky [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=43BA8E42.1010608@bl.com \
--to=msha5_17@bl.com \
--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).