linux-kernel - Re: PATA drivers queued for 2.6.19

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 06 Sep 2006 02:51:56 +1000
From:	Grant Coady <gcoady.lk@...il.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Helge Hafting <helge.hafting@...el.hist.no>,
	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	Jeff Garzik <jeff@...zik.org>,
	"linux-ide@...r.kernel.org" <linux-ide@...r.kernel.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>,
	Linus Torvalds <torvalds@...l.org>
Subject: Re: PATA drivers queued for 2.6.19

On Tue, 05 Sep 2006 15:39:36 +0100, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:

>Ar Maw, 2006-09-05 am 15:26 +0200, ysgrifennodd Helge Hafting:
>> between sda/hda unless they also use an initrd.  The kernel
>> itself does not seem to support partition by label. :-(
>
>This is correct and one reason vendor kernels generally use an initrd.
>The kernel does however support "root=/dev/sda1"

Which leads back to this slackware user, who's never used an initrd, 
thinking about dual root partitions just to get the name change from 
another /etc/fstab?  

I dual boot 2.4 / 2.6 kernels, looking for a simple solution so I can 
test Alan's work.  

No udev, no initrd, funny I see a second '/' partition as 'easy'? ;)

I'm missing something here?  Generally /etc/lilo.conf looks like:
  <http://bugsplatter.mine.nu/test/boxen/deltree/lilo.conf>

Grant.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/