Re: ESDI Disk

[OBERLER@de.ibm.com]

On Fri, 17 Dec, 1999 à 04:03:43PM +0100, OBERLER@de.ibm.com wrote:
>> I have an rather! old IBM Thinkpad Model 720. It has MCA architecture and the
>> disk is an ESDI disk, but no CDROM.
>[...]
>>  eda: eda1 eda2 eda3
>> I assume that eda1 is my old DOS, while eda2 and eda3 are the Linux ext2 and
>> Linux Swap partitions (which I have created before).
>
>How did you created them without the devices files ?
 I used my old OS/2 'fdisk'. Still a very handsome program.
>
>[...]
>> When I shell-out and check /dev, I can not see any /dev/eda or /dev/eda1
>> devices. Are there devices missing? Which? How can I create them?
>
>Does /dev/MAKEDEV exist ? If so, /dev/MAKEDEV eda would suffice, if not then
use
>mknod to create the block devices (mknod b 36 0 /dev/eda ; mknod b 36 1
>/dev/eda1...)
 Yes, an 'mknod /dev/eda b 36 0', 'mknod /dev/eda1 b 36 1' and
 'mknod /dev/eda2 b 36 2' have done the job (Meanwhile I have erased the old DOS
 partition completely; just ext2 and swap ). Then I then 'exit' back to
'dbootstrap',
 the installation continues as normal with 'Assign Swap' and 'Mount Linux
partition'.
 Of course after the following re-boot with the kernel from the disk, I had to
issue
 the 'mknod' commands again to create the devices permanently on the disk (and
not only
 on the RAM-disk).
>
>> Is it sufficient to do this an the ash shell and continue installation or has
>> the root.bin to be changed? Am I right, if I assume that the resc1440.bin
does
>> not exactly fit to the root.bin in my situation?
>
>Not sure
 Now I'm quite sure, that there is a real (although not serious, because it
affects
 only very few users) problem with the combination of the SLink resc1440.bin and
the
 root.bin, because the kernel supports EDSI disks (very welcome for me) but the
root
 file system in root.bin does not have the devices created. Maybe someone
responsible
 for the installation diskettes can have an eye on that!
>
>> What do I have to do? I have another system running where I can compile a
kernel
>> or something else, if this would help!
>>
>Manually format /eda2 and mount it on /target then proceed with the menu
>after initialize a linux partition (you'll have to create /etc/fstab too I
>think) but try to let the menu does all the work once you've created the
>device files.
 All that (format, mount, fstab entry) was automatically done during the
following
 installation by 'dbootstrap'.

Thanks Laurent PICOULEAU for your ideas.

Best Regards / Mit freundlichen Grüßen   Roland Oberle