From: Moshe Yudkowsky <msha5_17@bl.com>
To: linux-hotplug@vger.kernel.org
Subject: udev and yaird
Date: Thu, 05 Jan 2006 02:36:20 +0000 [thread overview]
Message-ID: <43BC8624.8090601@bl.com> (raw)
I'm trying to puzzle out a problem with udev and yaird. Please bear with
me -- I suspect that this is a yaird problem, but I'm not entirely certain.
I'm using 2.6.14, Debian unstable. (2.6.14-2-k7)
Symptom: the ide-cd module does not load at boot time. No /dev entries
are created.
Problem: when I use cpio to look at the boot image, I see that the init
script loads ide-{core, generic, disk} and some other modules, but not
ide-cd.
Question: doesn't the ide-cd load the way it used to in prior versions
of the kernel created with mkinitrd?
I suspect that the problem is that yaird doesn't use the udev script
under /usr/share/initramfs-tools/scripts, for example. That udev script
would test each ide device and load ide-cd if it found a cdrom.
Even if I modify /etc/modules I still don't get ide-cd in yaird images.
Instead, yaird just looks for the bare minimum to mount the root file
system:
> yaird: goal: mountdir, / (/etc/yaird/Default.cfg:143)
> yaird: action: insmod, /lib/modules/2.6.14-2-k7/kernel/drivers/ide/ide-core.ko {optionList=-- }
> yaird: action: insmod, /lib/modules/2.6.14-2-k7/kernel/drivers/ide/ide-generic.ko {optionList=-- }
> yaird: action: insmod, /lib/modules/2.6.14-2-k7/kernel/drivers/ide/ide-disk.ko {optionList=-- }
> yaird: hardware: completed ide0/0.0
> yaird: action: mkbdev, /dev/hda {sysname=hda }
> yaird: action: mkbdev, /dev/hda1 {sysname=hda/hda1 }
> yaird: action: insmod, /lib/modules/2.6.14-2-k7/kernel/drivers/md/md-mod.ko {optionList=-- }
> yaird: action: insmod, /lib/modules/2.6.14-2-k7/kernel/drivers/md/raid1.ko {optionList=-- }
> yaird: action: mdadm, /dev/md1 {components=ARRAY(0x89b78c8) major=9 minor=1 uuidX42a331:676c7ce4:06417154:50dffb65 }
> yaird: action: insmod, /lib/modules/2.6.14-2-k7/kernel/fs/reiserfs/reiserfs.ko {optionList=-- }
> yaird: action: mount, /mnt {device=/dev/md1 fsType=reiserfs isRoot=1 options=-- }
So, why doesn't yaird -- or something else -- modprobe ide-cd anymore?
Is this a distro problem, a yaird problem, or a "udev needs to remind
yaird to include something in /etc/yaird/Default.cfg" problem?
Thanks,
Moshe
--
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:[~2006-01-05 2:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43BC8624.8090601@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).