Date: Wed, 17 May 2006 20:39:38 +0300 From: Maslan <maslanbsd@gmail.com> To: "Stas Myasnikov" <myst@tut.by> Cc: freebsd-hackers@freebsd.org Subject: Re: Sysinstall sucks Message-ID: <319cceca0605171039t2a823313s5553603bab3bd436@mail.gmail.com> In-Reply-To: <446B4084.5000903@tut.by> References: <319cceca0605170643u4b407a2fg9c2d60f6c8c1ddb4@mail.gmail.com> <446B4084.5000903@tut.by>
next in thread | previous in thread | raw e-mail | index | archive | help
> Strange enough, since sysinstall writes to disk ONLY after you set all > options and press YES. BTW at (1) you write that sysinstall had > finished before your MBR was wiped out. So did sysinstall finish, or it > catch the some signal? > > Stas > It didn't run at all fdisk, it catch a some signal and crash. I didn't need to repartation since i've already 2 bsd slices each has each own partitions so i just clicked on the labeling step and make some changes to the partitions inside the already bsd slice (ad0s4). Then everything contiued normally, and the system has been installed. but i found grub (installed on MBR with files on linux ext3 partition) gives as i remember error 22, i booted my slack cd and run cfdisk and found that parititions is no longer available and marked as empty space. I used gpart and fixed the problem, and i didn't need to re-install anything. even the newly installed freebsd system was preserved. --=20 I'm Searching For Perfection, So Even If U Need Portability U've To Use Assembly ;-) http://www.maslanlab.org http://libosdk.berlios.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?319cceca0605171039t2a823313s5553603bab3bd436>