Date: Wed, 29 Oct 2003 17:32:29 -0800 (PST) From: Doug White <dwhite@gumbysoft.com> To: Sergey Matveychuk <sem@ciam.ru> Cc: current@freebsd.org Subject: Re: problems with sysinstall Message-ID: <20031029173150.Q39476@carver.gumbysoft.com> In-Reply-To: <3F9FF8DD.7040100@ciam.ru> References: <3F9F299C.8050504@ciam.ru> <20031029090121.U37386@carver.gumbysoft.com> <3F9FF8DD.7040100@ciam.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 29 Oct 2003, Sergey Matveychuk wrote: > Doug White wrote: > > "Missing operating system" comes out of the DOS default bootblock, not the > > BIOS. > > Yes, I know. But I don't feel better then. It means you were barking up the wrong tree :) > > > Don't use chainloader with FreeBSD. Use 'kernel /boot/loader' instead. > > This is documented in the GRUB info doc. Again, I have set this exact > > system up with redhat on the first disk and it works perfectly. > > Grub do not supporting UFS2. So only way to boot -current is chainloader. OK, I didn't test this. It works with UFS1 :) > > This is normal and for your protection. you can't edit the disk you're > > running off of. If you are running off of ad1, make sure 1) you're root > > when you run sysinstall and b) you aren't mounting any filesystems from > > ad0. > > Well, I understand it for slices. But why I can't create new partition > in exist slice and newfs it? It was OK in -stable. yes, this is a change to -current. It is for your own safety. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031029173150.Q39476>