From: Piter PUNK <piterpk@terra.com.br>
To: linux-hotplug@vger.kernel.org
Subject: Problems with disks and dhcp
Date: Mon, 03 Apr 2006 21:27:36 +0000 [thread overview]
Message-ID: <44319348.1040905@terra.com.br> (raw)
Hi,
I am making experimental packages of newer udev for slackware. But i got
some bug reports and can't solve (ok, i solve the problems, but i think
i solve it in the "wrong way").
What i was doing:
1) mount / ro
2) mounting sysfs and starting udev
2.1) mounting new /dev
2.2) copying devices from /lib/udev/devices
2.3) starting udevd and populating /dev
2.4) running udev.count_events.sh to wait
3) running fsck, if needed
4) remounting / rw
But, sometimes, in 3 i got error messages and the system
hangs, because my / device isn't created yet. In 2.3 i run
a loop, looking /dev/.udev/queue and waiting and in 2.4 i
run udev.count_events.sh. This is my first problem. A disk
problem.
The second problem is with dhcp. It hangs sometimes if is
called before 4. And my udev rules calls the network configuration
tools in 2.3.
I solve both problems, changing the order to 1,3,4,2. But i think
is wrong run udev after remounting /.
I am doing the things in the right way? If this is the wrong way,
what i can do to solve these problems?
Thanks for your help
Piter PUNK
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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-04-03 21:27 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=44319348.1040905@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.