From: "Matt P." <matt@area403.org>
To: linux-kernel@vger.kernel.org
Subject: pb with init for 2.5.62, not 2.4.20
Date: Mon, 10 Mar 2003 11:10:28 -0500 [thread overview]
Message-ID: <20030310161027.GA4386@scyld.com> (raw)
Hello,
I don't know if this is a kernel issue, but since I have a pb with one
kernel and not the other, I assume it is... Please don't flame.
I am trying to have a small distro that uses ramdisk for its partitions
that need rw access, and the cd for the rest. Part of the script
(slurped from boot-cd hint from linux from scratch) consists in copying
over from the cd to the ramdisk these partitions (script in app-1).
The behavior depend on the kernel... after the last mount, with 2.5 the
fake/needwrite directory doesn't contain anything, whereas with 2.4.20
it does contain what I put in it. And I think it is related, but with
2.5, I never get into run level 1 or 2 or 3, it just hangs after the
last script in rcsysinit.d., whereas 2.4.20 slides smoothly into
whatever inittab tells him to.
Do I need extra modules in 2.5?
(Note that the size of 2.4 is ~ 930k, where as 2.5 is 1.5M)
Thx for any suggestion.
Matt
App 1:
#!/bin/sh
dev_ram=/dev/ram0
dir_ramdisk=/fake/ramdisk
dir_needwrite=/fake/needwrite
source /etc/rc.d/init.d/functions
case "$1" in
start)
echo -n "Creating ext2fs on $dev_ram ... "
/sbin/mke2fs -m 0 -i 1024 -q $dev_ram > /dev/null 2>&1
evaluate_retval
sleep 1
echo -n "Mounting ramdisk on $dir_ramdisk ... "
mount -n $dev_ram $dir_ramdisk
evaluate_retval
sleep 1
echo -n "Copying files to ramdisk ... "
cp -dpR $dir_needwrite/* $dir_ramdisk > /dev/null 2>&1
evaluate_retval
sleep 1
echo -n "Remount ramdisk to $dir_needwrite ... "
umount -n $dir_ramdisk > /dev/null 2>&1
sleep 1
mount -n $dev_ram $dir_needwrite
sleep 1
;;
*)
echo "Usage: $0 {start}"
exit 1
;;
esac
reply other threads:[~2003-03-10 15:59 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=20030310161027.GA4386@scyld.com \
--to=matt@area403.org \
--cc=linux-kernel@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.