| 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
| ||
|
Message-Id: <200801200007.00125.hpj@urpla.net> Date: Sun, 20 Jan 2008 00:06:59 +0100 From: Hans-Peter Jansen <hpj@...la.net> To: "Lars Callenbach" <lars.callenbach@....de>, linux-kernel@...r.kernel.org Subject: Re: linux device ordering at boot time Am Samstag, 19. Januar 2008 schrieben Sie: > I have a question concerning the ordering of devices during the boot > process and I hope that the kernel mailing list is the right place for > this question. In my computer are two raid controllers with one raid > array connected to each of them (/dev/sda, /dev/sdb). In the debian > 2.6.18 boot process the ordering is root @ /dev/sda and data are on > /dev/sdb. This behaviour has changed in the plain 2.6.23.1 (and 2.6.23.8) > kernel. The /dev/sd(a|b) devices have switched so that root @ /dev/sdb. > So my standard fstab does not work. What determines the device ordering > during the boot process? What is a workaround for this problem? Well, it's a major pain in the a**. I've no idea, what reversed the order of PCI devices, but I had to disable the automatic dvb driver loading in order to get the picture back (dedicated vdr system with one FF and one budget card). I could have taken the route of exchanging the cards, but that would have been even more painful.. Oh well, Pete -- 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/
Powered by blists - more mailing lists