From: Felix Miata <mrmazda@ij.net>
To: linux-ide@vger.kernel.org
Subject: Re: [RFC] Separating out libata out of SCSI (finally)
Date: Tue, 24 Jun 2008 12:27:36 -0400 [thread overview]
Message-ID: <48612078.3000905@ij.net> (raw)
In-Reply-To: <4861176E.8040008@kernel.org>
On 2008/06/25 00:49 (GMT+0900) Tejun Heo apparently typed:
> Felix Miata wrote:
>> On 2008/06/24 23:59 (GMT+0900) Tejun Heo apparently typed:
>>> I'm currently working on a scheme where partitions above gd->minors get
>>> allocated dynamic MAJ:MIN. It looks like it can be done mostly in block
>>> layer proper. The only problem I can foresee is not being able to
>>> specify MAJ:MIN as root device but that shouldn't be a major problem.
>>> I'll report back when I make more progress.
>> Please correct me if I'm wrong, but on the following, would it not
>> be a major problem booting, without deleting any existing or moving
>> any existing, with only a few more upgrade cycles to replace what's
>> there installed now with current and near future distros?
> I'm not sure what you mean. If you switch to libata now, you'll only be
> able to see 15 partitions, so, yes, you'll have problem updating to a
Well, on the Fedora 9 on hda9 that is already the case, as it provided no
option to not use libata. ;-)
> distro which uses libata now and in near future. If the dynamic
> partition thing goes well, hopefully the next major distro releases work
> fine.
I responded as I did due to your statement "only problem I can foresee is not
being able to specify MAJ:MIN as root device", hoping to see some elaboration
on the statement from you. I read your statement as "don't expect to be able
to use any partition >15 as a root device". So, in the past root=3:17 would
have been a valid replacement for root =/dev/hda17? If so, sorry for the
noise, as I'd never seen that type of usage, and certainly would not miss it.
--
"Where were you when I laid the earth's
foundation?" Matthew 7:12 NIV
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://fm.no-ip.com/
next prev parent reply other threads:[~2008-06-24 16:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <485B2CC6.6070201@kernel.org>
2008-06-20 19:41 ` [RFC] Separating out libata out of SCSI (finally) Brian King
2008-06-20 20:28 ` James Bottomley
2008-06-20 22:41 ` Jeff Garzik
2008-06-20 23:50 ` Tejun Heo
2008-06-23 21:04 ` Greg Freemyer
2008-06-23 21:11 ` James Bottomley
2008-06-23 21:56 ` Felix Miata
2008-06-24 8:30 ` Boaz Harrosh
2008-06-24 14:42 ` James Bottomley
2008-06-24 14:58 ` Greg Freemyer
2008-06-24 15:13 ` Felix Miata
2008-06-24 14:59 ` Tejun Heo
2008-06-24 15:42 ` Felix Miata
2008-06-24 15:49 ` Tejun Heo
2008-06-24 16:27 ` Felix Miata [this message]
2008-06-24 16:35 ` Tejun Heo
2008-06-24 16:54 ` Alan Cox
2008-06-20 23:47 ` Tejun Heo
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=48612078.3000905@ij.net \
--to=mrmazda@ij.net \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).