Date: Sat, 1 Nov 2003 13:35:29 +0000 From: David Taylor <davidt@yadt.co.uk> To: current@freebsd.org Subject: Re: problems with sysinstall Message-ID: <20031101133529.GA30137@gattaca.yadt.co.uk> In-Reply-To: <20031029173150.Q39476@carver.gumbysoft.com> References: <3F9F299C.8050504@ciam.ru> <20031029090121.U37386@carver.gumbysoft.com> <3F9FF8DD.7040100@ciam.ru> <20031029173150.Q39476@carver.gumbysoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 29 Oct 2003, Doug White wrote: > On Wed, 29 Oct 2003, Sergey Matveychuk wrote: >> Doug White wrote: >>> 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. My own safety? I can down the system in a million ways, yet can't do what I actually want? A major reason I got fed up with Windows (other than it not working right) was it's insistance of knowing what was best for me. I hope FreeBSD doesn't fall down the same path. Or at least have a kernel option FOOT_SHOOTING, or something, that will disable all the helpful code protection people from themselves. -- David Taylor davidt@yadt.co.uk "The future just ain't what it used to be"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031101133529.GA30137>