Date: Fri, 18 Aug 2000 11:48:21 -0400 From: "Patrick Bihan-Faou" <patrick@mindstep.com> To: "Johan Kruger" <jkruger@oskar.dev.nanoteq.co.za> Cc: <freebsd-hackers@FreeBSD.ORG> Subject: Re: Bootable CD... Message-ID: <03b801c0092b$bc8db0a0$040aa8c0@local.mindstep.com> References: <XFMail.000818095809.jkruger@oskar.dev.nanoteq.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > Might be that you need to disklabel the image of the filesystem on > which you copy this files, ( not talking about the mfs filesystem that > is crunced into the kernel ) > So, try the following. > Mount this image by doing 'vnconfig /dev/vn0 /pathtobootimage/myimage.img' > where myimgae.img is the 2.88 M boot image. > Now do a 'mount /dev/vn0 /mnt' > now do a 'disklabel -B -b /mnt/boot/boot1 -s /mnt/boot/boot2 /dev/vn0 Actually I am using the doFS.sh script from /usr/src/release. The disklabel is done (without the -b and -s options though) by that script. Also I used to be able to build bootable CDs from the same procedure a few weeks ago (before the code in /usr/src/sys/boot was updated). The CD is recognized as bootable and starts to boot. I can stop the boot at the first "spinning bar" (I think that's boot0 or boot1) before the control is passed to "loader". From there I am sort of stuck: the only thing I can boot is loader which in turn crashes immediately. I tried to load "kernel.gz" but its format is not recognized at this stage of the boot (probably because it is compressed). BTW I tried you procedure above, and I get: su-2.03# vnconfig /dev/vn0 boot.cdrom.img su-2.03# mount /dev/vn0 /mnt su-2.03# disklabel -B -b /mnt/boot/boot1 -s /mnt/boot/boot2 /dev/vn0 disklabel: /dev/vn0: Device busy su-2.03# disklabel -B -b /mnt/boot/boot1 -s /mnt/boot/boot2 /mnt disklabel: /mnt: Is a directory su-2.03# umount /mnt su-2.03# disklabel -B -b mindbox/boot/boot1 -s mindbox/boot/boot2 /dev/vn0 disklabel: ioctl DIOCWLABEL: Operation not supported by device su-2.03# I'd rather fix the problem with the current version of the boot code, but time is pressing and I am tempted to revert to the code tagged with the FreeBSD-4.0 release. Is this something that I should do ? Patrick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?03b801c0092b$bc8db0a0$040aa8c0>