Am Mit, den 18.02.2004 schrieb Ph LelÃdy um 19:35: > I've been able to access may ieee1394 drives. > Everything is fine as far as drivers are concerned, but with recent > kernels there remains some stuff to be done in user space. I think it's > what rescan-scsi-bus is for. I did it manually by > echo "scsi add-single-device 0 0 0 0" > /proc/scsi/scsi we need rescan-scsi-bus.sh or something equivalent on the d-i image to recognise your disk automatically. This should be done in hw-detect-full.
> and the hd'a are recognized under long path like > /dev/scsi/host0/ââ/target0/lun0/disc. > This long path is not so much a problem as d-i knows about them when > it's time to partition them. > > You have to disrupt normal d-i process to have acces to a shell for > entering the echo command. After exiting the shell, the d-i finely goes > on, you can partition the disk and the system is installed on it. > > Unfortunately I was unable to actually achieve the installation, because > yaboot.conf can't be written -- sid the error message. It's perhaps due > to my 800k bootstrap partition non being HFS formatted. parse error :-) What is the exact error message of yaboot-installer. Probably it does not even recognize your Apple Bootstrap Partition. I never tested installation of yaboot on a SCSI disk, so this may well be the case. yaboot-installer uses libparted to find the available Apple Bootstrap partitions. I need more information to actually track down where exactly yaboot-installer fails. Gaudenz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
