Ok... first question... Before I ask it, I would like to say that I printed out the installation guide for 4.0 and did read it *in detail*
So, as I told you I had an ubuntu system on the laptop (I am using now an ibm t43p to test OpenBSD before I install it on the laptop I use as a production machine) The installation guide gives a nice example of a system with a windows partition on it. I intend to enable in the future the suspend-to-disk option and I see that ubuntu had done a partition in the end of the disk with a size of ~4GB, so that I presume this is the partition for this feature. Therefore I do not delete it and let it as it is. Then I proceed with the fdisk step and edit the zero partition, which has a size of 73GB or so: e 0 My problem is that I don't understand what this paragraph means: "On platforms which use fdisk, it is important that the first partition skips the first track of the disk, in this case, starting on sector 63. This will vary from machine to machine and disk system to disk system. If an OpenBSD partition is created starting at offset 0, this partition table will end up being overwritten by the OpenBSD partition's Partition Boot Record." How many C/H/S are a track? I try to assign an offset to the first partition, I tried both with CHS and raw mode but in the end the same happens always: I go through the install, which is rather easy and logical, download the system, install it and halt to reboot afterwards and... alas, fortune and glas break soon: When the laptop is booting I get a GRUB message popping up and saying that it cannot load the system. Of course, this GRUB used to belong to ubuntu and it must be in the first track, somewhere... if I give an offset to the first partition, this residual ubuntu thing will be sill there... Of course, I can always go for the "use the whole disk for OpenBSD" but then that potential suspend-to-disk partition will be deleted. On the other hand, what I am interested on is NOT suspend to disk, but suspend to ram. But being prudent as I am, I am aware that this may not work out and I want to leave open the possibility of suspending to disk in case of. I guess I am doing something wrong, but what? I was a good boy, I read the documentation and this is not a MY-OPENBSD-DOES-NOT-BOOT-HELP! message... don't throw tomatoes to me, please... Cheers, Pau _______________________________________________ Openbsd-newbies mailing list [EMAIL PROTECTED] http://mailman.theapt.org/listinfo/openbsd-newbies
