From: <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] sysvinit: fix problem in switching runlevels
Date: Mon, 11 Nov 2013 17:26:08 +0800 [thread overview]
Message-ID: <cover.1384161495.git.Qi.Chen@windriver.com> (raw)
From: Chen Qi <Qi.Chen@windriver.com>
This patch has been tested with the following steps.
1. Build an image with nfs-utils and rpcbind.
2. Add to /etc/fstab an nfs mount point with the following commands.
mount -o loop tmp/deploy/images/qemux86/core-image-minimal-qemux86.ext3 root-disk-dir/
mkdir -p root-disk-dir/home/root/test
if ! grep -q 'nfs' root-disk-dir/etc/fstab; then
echo "192.168.7.1:/home/chenqi/test /home/root/test nfs defaults 0 0" >> root-disk-dir/etc/fstab
fi
umount root-disk-dir
3. runqemu qemux86 qemuparams="-serial stdio" bootparams="console=ttyS0"
4. init 1 (Network interface down and no nfs mount point)
5. init 3 (Network interface up and nfs mount point available)
6. init 5 (Network interface up and nfs mount point available)
The following changes since commit 4fdc3d77d4a875b7236536bf78849a4d1f6a7449:
kbd: Fix stdarg related errors on uclibc (2013-11-08 17:31:36 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib ChenQi/sysvinit-runlevels
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/sysvinit-runlevels
Chen Qi (1):
sysvinit: fix problem in switching runlevels
.../init-ifupdown/init-ifupdown_1.0.bb | 2 +-
meta/recipes-core/initscripts/initscripts_1.0.bb | 4 ++--
meta/recipes-extended/rpcbind/rpcbind_0.2.0.bb | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-11-11 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 9:26 Qi.Chen [this message]
2013-11-11 9:26 ` [PATCH 1/1] sysvinit: fix problem in switching runlevels Qi.Chen
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=cover.1384161495.git.Qi.Chen@windriver.com \
--to=qi.chen@windriver.com \
--cc=openembedded-core@lists.openembedded.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.