Eduard,

At 10:38 AM 03/13/2002 +0100, Eduard Bloch wrote:
>#include <hallo.h>
>Loren Jordan wrote on Tue Mar 12, 2002 um 05:23:25PM:
>
> > in.  "cat /proc/partitions" didn't show anything.  The disks have a 
> date on
> > them of Mar-10.  The kernel-config looks like it also has the cciss driver
> > as a module...
>
>There are no CD images from Mar-10. There are some from Mar-11. A
>testing image for XFS-Installation which really do not support CCISS
>without modules, and a pure CVS build in boot-floppies/cd-iso which
>should work for you.

The dates I was referring to was the data-time stamp listed in the 
directory listing of the dir on people.debian.org/~blade/...


> > My report is that the iso has an "older" root.bin built into it and the
> > floppies have an older rescue.bin.
>
>??
>
>CD contents are from the same build.

When booting from the floppies, I did not have cciss devices listed in the 
/proc/partitions file however I did have /dev/cciss/c0d0* files.
When booting from the .iso image, I had cciss devices in the 
/proc/partitions file and did NOT have a /dev/cciss dir...

Once I made the /dev/cciss/c0d0* files by hand, I was able to cfdisk so the 
kernel in the .iso has the cciss driver built in.

This is why I think that the boot floppies have an older rescue.bin "kernel 
image missing the cciss driver" and the cd seems to have an older root.bin 
"missing /dev/cciss and dbootstrap not knowing about cciss devices".

If I am getting these files from the wrong place then let me know the 
propper place and I will re-test.

I got the floppies from
http://people.debian.org/~blade/boot-floppies/dists/woody/main/disks-i386/current/images-1.44/bf2.4/
and the cd image from
http://people.debian.org/~blade/boot-floppies/cd-iso/

Thanks,
Loren


>Gruss/Regards,
>Eduard.
>--
>My growing impression of C++, object-oriented programming, etc., is that
>it attempts to allow programmers to conveniently reuse their mistakes.
>                                                         -- Stephen Uitti
>
>
>--
>To UNSUBSCRIBE, email to [EMAIL PROTECTED]
>with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to