linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Moshe Yudkowsky <msha5_17@bl.com>
To: linux-hotplug@vger.kernel.org
Subject: udev /boot/img "was been altered"
Date: Tue, 27 Dec 2005 03:18:21 +0000	[thread overview]
Message-ID: <43B0B27D.2070504@bl.com> (raw)

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.

That should read "has been altered." But besides that, what exactly is 
the problem that's being reported?

I have to wonder if this has something to do with why I have to manually 
"modprobe ide-cd" after each reboot. The install program for new 
versions of linux-image claims it runs "depmod," but I can't find a copy 
of modules.dep anywhere. I suspect that I'm in some twilight zone, 
caught between udev and linux-image visions of how an install works... 
I'll send details when I figure out what's happening.

-- 
  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

             reply	other threads:[~2005-12-27  3:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-27  3:18 Moshe Yudkowsky [this message]
2005-12-27  4:00 ` udev /boot/img "was been altered" Greg KH
2006-01-03  8:10 ` Scott James Remnant
2006-01-03 14:46 ` Moshe Yudkowsky

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=43B0B27D.2070504@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).