From: Patrick Mansfield <patmans@us.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: gerneral question for linux-2.6 and udev and hotplug
Date: Sat, 01 Oct 2005 00:30:02 +0000 [thread overview]
Message-ID: <20051001003002.GA20468@us.ibm.com> (raw)
In-Reply-To: <11E3973D1E78D311A5B400508B4A70CE02B3CEE1@COMSRVR>
On Fri, Sep 30, 2005 at 10:51:55AM -0400, Gavin Li wrote:
> All,
>
> I am trying migrate to 2.6 kernel from 2.4.
I didn't read the full problem report, but:
Why don't you install FC4, and go from there?
FC3 is already old, and AFAICT it is at kernel 2.6.12-1.1378, that is
quite a ways past the 667 you mention.
-- Patrick Mansfield
> I copied RedHat FC3 kernel binary vmlinuz-2.6.9-1.667 to my harddrive, and
> /bin /sbin and /lib /usr/ are also copied.
> I didn't copy /etc to my harddrive, I installed hotplug-2004_09_23 to my
> /etc
> In my /etc/inittab, I set start script to my own start script, which is
> /etc/rc.d/rcS
> this file is:
> #!/bin/bash
> kill_init=`ls /dev | grep -c tty`
> if [ $kill_init -eq 0 ]; then
> clear
> mount -n -t proc /proc /proc
> [ -d /proc/bus/usb ] && mount -n -t usbfs /usbfs /proc/bus/usb
> mount -n -t sysfs /sys /sys
> mount -n -t tmpfs /dev /dev modeu5
> mkdir -p /dev/shm /dev/pts
> mount -n -t tmpfs /devshm /dev/shm
> mount -n -t devpts -o gid=5,modeb0 /devpts /dev/pts
> echo /sbin/udevsend > /proc/sys/kernel/hotplug
> udevstart
> kill -HUP 1 2>&1 > /dev/null
> sleep 12
> fi
>
> PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
> export PATH
> ln -s /proc/self/fd /dev/fd
> ln -s /proc/self/fd/0 /dev/stdin
> ln -s /proc/self/fd/1 /dev/stdout
> ln -s /proc/self/fd/2 /dev/stderr
> ln -s /proc/kcore /dev/core
> mount -t tmpfs /dev/ram0 /tmp
> cd /var && tar -cf /tmp/var.tar * && cd /
> mount -t tmpfs /dev/ram1 /var
> cd /var && tar -xf /tmp/var.tar && cd /
>
>
>
> My problem is:
> when I plug in a USB flash drive, nothing happened, I can't find hotplug is
> working
>
> Then I change echo /sbin/udevsend > /proc/sys/kernel/hotplug to echo
> /sbin/mytest > /proc/sys/kernel/hotplug
>
> and mytest script is :
> echo "starting hotplug" > /tmp/tmp.txt
>
> then I do plug/unplug USB flash drive, the file size of /tmp/tmp.txt is 0,
> which means mytest script is never got executed.
>
> Anything I did wrong? or do I miss something
>
> One more question:If I use udev-070, do I still need to compile and install
> sysfsutils and/or sysutils?
>
> Regards,
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
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:[~2005-10-01 0:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 14:51 gerneral question for linux-2.6 and udev and hotplug Gavin Li
2005-09-30 17:07 ` Kay Sievers
2005-10-01 0:30 ` Patrick Mansfield [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=20051001003002.GA20468@us.ibm.com \
--to=patmans@us.ibm.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).