Re: catch-22 upgrading to 2.6 kernel?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Marvin Lyndon schrieb:
Some googling reminded me that the naming convention for devices changes with 2.6: so I tried editing my /boot/initrd.conf so that it read

CRYPTROOT=/dev/discs/disc0/part1 (formerly /dev/hda1)
BOOTDEV=/dev/discs/disc1  (formerly /dev/sda?)

not necessarily. the naming convention is derived from the devfs filesystem, introduced in 2.3.x iirc and to be obsoleted again pretty soon in 2.6 [1]

for general linux-2.6 question, a good starting point is:
http://www.codemonkey.org.uk/docs/post-halloween-2.6.txt

> I am pretty much guessing concerning the second device name; how can I
> find the new correct name for /dev/sda if I cannot boot the 2.6 kernel?

"sda" with devfs is /dev/scsi/host0/bus0/target1/lun0 here. but /dev/sda should also do.

***  script was supposed to create block device nodes for     ***
***  BOOTDEV=, CRYPTROOT= and possibly EXTERNALGPGDEV= but    ***
***  lacked knowledge of how to create at least one of them.  ***
***  Script aborted.

hm, either you're using devfs, which should create the devicenodes by itself (not?) or you can create the nodes with mknod(1). but i've never done such things.

Christian.

[1] http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html
--
BOFH excuse #133:

It's not plugged in.

-
Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/


[Index of Archives]     [Kernel]     [Linux Crypto]     [Gnu Crypto]     [Gnu Classpath]     [Netfilter]     [Bugtraq]
  Powered by Linux