From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Frank van Maarseveen <frankvm@frankvm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.20*: PATA DMA timeout, hangs (2)
Date: Mon, 12 Mar 2007 13:52:19 +0000 [thread overview]
Message-ID: <200703121352.19505.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <20070312132546.GC12265@janus>
On Monday 12 March 2007 13:25, Frank van Maarseveen wrote:
[snip]
> So, are /dev/hd* going to disappear in a few years? iow, does it make
> sense to _slowly_ start to migrate to /dev/sd*?
How would you propose doing this? I'm sure modern distros with an
initrd/initramfs probably already do some sort of root detection. Doesn't fix
the fstab issue, but I suppose this could be auto-generated too.
> The problem is there's no plan B in case of any troubles except rename
> everything back again to boot an old kernel.
I doubt this matters for distributors, as they'll simply switch over when you
upgrade the distro, and the earliest supported kernel will be the one that
shipped with the newer version.
I accept that it's a bit of a drag, but it's better to have a standard naming
convention for all disks, isn't it?
Glad this is working for you.
--
Cheers,
Alistair.
Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2007-03-12 13:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 8:54 2.6.20*: PATA DMA timeout, hangs Frank van Maarseveen
2007-03-12 11:24 ` 2.6.20*: PATA DMA timeout, hangs (2) Frank van Maarseveen
2007-03-12 12:07 ` Alistair John Strachan
2007-03-12 13:25 ` Frank van Maarseveen
2007-03-12 13:52 ` Alistair John Strachan [this message]
2007-03-19 8:22 ` Tejun Heo
2007-03-12 12:21 ` Bartlomiej Zolnierkiewicz
2007-03-12 12:40 ` Frank van Maarseveen
2007-03-12 20:40 ` Bartlomiej Zolnierkiewicz
2007-03-13 9:19 ` Frank van Maarseveen
2007-03-13 11:04 ` Bartlomiej Zolnierkiewicz
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=200703121352.19505.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=frankvm@frankvm.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
all inboxes | Powered by JetHome®