From: A Guy Called Tyketto <tyketto@wizard.com>
To: dalecki@evision-ventures.com
Cc: devfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: [PATCH] Make IDE and DevFS get along
Date: Mon, 10 Jun 2002 03:34:15 -0700 [thread overview]
Message-ID: <20020610103415.GA303@wizard.com> (raw)
Martin,
A feature/patch from one of the generic IDE patchsets was introduced
into kernels >= 2.5.19 that, when DevFS is used, creates a directory called
/dev/ata, and a symlink to /dev/ata, called /dev/ide. This setup breaks DevFS'
use, as it does not follow the symlink when the IDE driver is initialised.
DevFS uses /dev/ide, which is the published interface, to create the
symlinks to /dev/hd*, which are created after reading /etc/fstab to get the
partitions. When /dev/ata is used, DevFS doesn't know what it is, can't find
/dev/ide/* for the /dev/hd* symlinks to be created, and drops into single user
mode to fix. This will always happen for anyone with their root partition on
an IDE drive, with DevFS used. The following patch fixes this problem.
BL.
P.S. The only other way around this, would be to rewrite /etc/fstab to
find the full patch to the /dev/ata/host*.../part1 partition for / . That
really shouldn't have to be done.
--
Brad Littlejohn | Email: tyketto@wizard.com
Unix Systems Administrator, | tyketto@ozemail.com.au
Web + NewsMaster, BOFH.. Smeghead! :) | http://www.wizard.com/~tyketto
PGP: 1024D/E319F0BF 6980 AAD6 7329 E9E6 D569 F620 C819 199A E319 F0BF
--- linux/drivers/ide/main.c.ata Mon Jun 10 02:47:50 2002
+++ linux/drivers/ide/main.c Mon Jun 10 02:49:03 2002
@@ -1290,8 +1290,7 @@
{
printk(KERN_INFO "ATA/ATAPI device driver v" VERSION "\n");
- ide_devfs_handle = devfs_mk_dir(NULL, "ata", NULL);
- devfs_mk_symlink(NULL, "ide", DEVFS_FL_DEFAULT, "ata", NULL, NULL);
+ ide_devfs_handle = devfs_mk_dir(NULL, "ide", NULL);
/*
* Because most of the ATA adapters represent the timings in unit of
reply other threads:[~2002-06-10 10:34 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=20020610103415.GA303@wizard.com \
--to=tyketto@wizard.com \
--cc=dalecki@evision-ventures.com \
--cc=devfs@oss.sgi.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox