linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hai Zaar <haizaar@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Fwd: blkid descends into /dev/.udev/... and stucks.
Date: Thu, 26 Jan 2006 16:10:35 +0000	[thread overview]
Message-ID: <cfb54190601260810wf8dca9dk5880db4fedeb4a20@mail.gmail.com> (raw)
In-Reply-To: <cfb54190601260717i39e89f58n973886ea65194091@mail.gmail.com>

<skipped>
> Use vol_id, it fits better on a udev system. Note, you may not need anything
> custom here, if you use the persistent symlinks in /dev/disk, which almost
> all distros have these days.
Thanks for the hint! Actually what I can do in initramfs is just:
-----------------------------
trigger_all_events
# now lets find device by uuid. UUID value is hardcoded to /init by my
mkinitramfs script.
timeout0
while ((timeout > 0); do
    if [[ -e /dev/disk/by-uuid/$UUID ]];
        ROOTDEV=/dev/disk/by-uuid/$UUID
        break
    fi
    let timeout --
    sleep 1
done
if [[ "$ROOTDEV" != "" ]]; then
    mount $ROOTDEV  /newroot -o ro -t $(vol_id -t $ROOTDEV)
else
     exit
fi
-----------------------------
Another question:
Why halt command does not work in during initramfs?
How can I properly halt system at this stage?
For now I just use 'exit', but this is unpretty, since I get "kernel
panic - attempted to kill init"

> And please send the blkid patch to the e2fsprogs maintainer, as it would be good
> to have this fixed soon. But I think it's better to ignore _any_ dot file in /dev
> instead of the udev directory only.
Already there - actually I've posted a forward of the message I've sent to him.


P.S. Thank you guys for your great work! For me, udev and friends is
one of the most exciting features of 2.6.x

--
Zaar


-------------------------------------------------------
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://sel.as-us.falkag.net/sel?cmd_______________________________________________
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

      parent reply	other threads:[~2006-01-26 16:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-26 15:17 Fwd: blkid descends into /dev/.udev/... and stucks Hai Zaar
2006-01-26 15:31 ` Kay Sievers
2006-01-26 16:10 ` Hai Zaar [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=cfb54190601260810wf8dca9dk5880db4fedeb4a20@mail.gmail.com \
    --to=haizaar@gmail.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).