From: Glenn Shannon <glenn@gecpalau.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] VGScan Crash workaround for DevFS
Date: Mon, 30 Apr 2001 16:52:48 +0900 [thread overview]
Message-ID: <3AED19D0.5430A65F@gecpalau.com> (raw)
Uhm......I got a workaround to work for me......
I put the following into my /etc/rc.d/rc.sysinit file right after the
part where the / partition is mounted read-write:
if [ ! -e /dev/hda ] ; then
action "Linking HDA for DevFS Compatibility" ln -s
/dev/ide/host0/bus0/target0/lun0/disc /dev/hda
fi
if [ ! -e /dev/hda1 ] ; then
action "Linking HDA for DevFS Compatibility" ln -s
/dev/ide/host0/bus0/target0/lun0/part1 /dev/hda1
fi
if [ ! -e /dev/hda2 ] ; then
action "Linking HDA for DevFS Compatibility" ln -s
/dev/ide/host0/bus0/target0/lun0/part2 /dev/hda2
fi
if [ ! -e /dev/hda3 ] ; then
action "Linking HDA for DevFS Compatibility" ln -s
/dev/ide/host0/bus0/target0/lun0/part3 /dev/hda3
fi
if [ ! -e /dev/hda4 ] ; then
action "Linking HDA for DevFS Compatibility" ln -s
/dev/ide/host0/bus0/target0/lun0/part4 /dev/hda4
fi
if [ ! -e /dev/hda5 ] ; then
action "Linking HDA for DevFS Compatibility" ln -s
/dev/ide/host0/bus0/target0/lun0/part5 /dev/hda5
fi
if [ ! -e /dev/hda6 ] ; then
action "Linking HDA for DevFS Compatibility" ln -s
/dev/ide/host0/bus0/target0/lun0/part6 /dev/hda6
fi
if [ ! -e /dev/hda7 ] ; then
action "Linking HDA for DevFS Compatibility" ln -s
/dev/ide/host0/bus0/target0/lun0/part7 /dev/hda7
fi
if [ ! -e /dev/hda8 ] ; then
action "Linking HDA for DevFS Compatibility" ln -s
/dev/ide/host0/bus0/target0/lun0/part8 /dev/hda8
fi
if [ ! -e /dev/hda9 ] ; then
action "Linking HDA for DevFS Compatibility" ln -s
/dev/ide/host0/bus0/target0/lun0/part9 /dev/hda9
fi
if [ ! -e /dev/hda10 ] ; then
action "Linking HDA for DevFS Compatibility" ln -s
/dev/ide/host0/bus0/target0/lun0/part10 /dev/hda10
fi
Hope this helps anyone out there.....but I'd still like to know why this
isn't needed in 2.4.3 but it is in 2.4.4.....is there something
different with the way DevFS works? As far as I can tell the DevFS
hasn't changed a bit.....
Glenn
reply other threads:[~2001-04-30 7:52 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=3AED19D0.5430A65F@gecpalau.com \
--to=glenn@gecpalau.com \
--cc=linux-lvm@sistina.com \
/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).