All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helge.hafting@aitel.hist.no>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Grant Coady <gcoady.lk@gmail.com>, Jeff Garzik <jeff@garzik.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Subject: Re: PATA drivers queued for 2.6.19
Date: Tue, 05 Sep 2006 15:26:54 +0200	[thread overview]
Message-ID: <44FD7B1E.7020102@aitel.hist.no> (raw)
In-Reply-To: <Pine.LNX.4.61.0609041406140.21005@yvahk01.tjqt.qr>

Jan Engelhardt wrote:
>>> I just pulled the "pata-drivers" branch of libata-dev.git into the 
>>> "upstream" branch, which means that Alan's libata PATA driver collection 
>>> is now queued for 2.6.19.
>>>
>>> Testing-wise, these PATA drivers have been Andrew Morton's -mm tree for 
>>> many months.  Community-wise, no one posted objections to the PATA 
>>> driver merge plan, when Alan posted it on LKML and linux-ide.
>>>       
>> Too friggin' hard to test Alan's stuff for older IDE here, therefore 
>> ignored so far :(   I have some old hardware that Alan is addressing, 
>> even an old IBM 260MB PCMCIA HDD.
>>
>> I can't see an easy way to arrange multi-boot with different /etc/fstab 
>> depending if I'm trying /dev/hdaX or /dev/sdaX.  Parallel '/' partitions?
>>     
>
> Got udev?
>
> /dev/disk/by-id/ata-ST3802110A_5LR13RN7-partX could be your friend.
>   
Udev fixes this for most filesystems - except / which is cruical.
With / on raid-1 this is not a problem, as md autodetect will
assemble the arrays whether they are on ide or scsi.
But anyone with / on a partition can't easily switch
between sda/hda unless they also use an initrd.  The kernel
itself does not seem to support partition by label. :-(

Helge Hafting


  parent reply	other threads:[~2006-09-05 13:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-04 11:01 PATA drivers queued for 2.6.19 Jeff Garzik
2006-09-04 12:02 ` Grant Coady
2006-09-04 12:07   ` Jan Engelhardt
2006-09-04 12:35     ` Tomasz Torcz
2006-09-04 13:35       ` Jan Engelhardt
2006-09-05 13:26     ` Helge Hafting [this message]
2006-09-05 14:39       ` Alan Cox
2006-09-05 16:51         ` Grant Coady
2006-09-05 17:57           ` Krzysztof Halasa
2006-09-05 21:24             ` Grant Coady
2006-09-04 12:12   ` Jeff Garzik
2006-09-04 13:27   ` Alan Cox
2006-09-04 12:02 ` Alan Cox
2006-09-04 12:10   ` Jan Engelhardt
2006-09-04 12:15     ` Jeff Garzik
2006-09-05 13:30   ` John Stoffel
2006-09-05 13:46     ` Sergei Shtylyov
2006-09-05 15:10       ` John Stoffel
2006-09-05 20:48   ` Bill Davidsen
2006-09-06  7:48     ` Alan Cox
2006-09-04 21:31 ` Andras Mantia
2006-09-05  2:25   ` Jeff Garzik
2006-09-21 11:55 ` Lennert Buytenhek
2006-09-22  9:51   ` Jeff Garzik
2007-01-28 20:21     ` cirrus ep93xx pata driver (was: Re: PATA drivers queued for 2.6.19) Lennert Buytenhek
2007-05-29  1:27       ` cirrus ep93xx pata driver Jeff Garzik
2007-05-29  1:48         ` Lennert Buytenhek
2007-05-29  2:58           ` Jeff Garzik

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=44FD7B1E.7020102@aitel.hist.no \
    --to=helge.hafting@aitel.hist.no \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gcoady.lk@gmail.com \
    --cc=jeff@garzik.org \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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.