Date: Thu, 30 Oct 2003 10:46:00 +0100 From: Richard Nyberg <rnyberg@it.su.se> To: Doug White <dwhite@gumbysoft.com> Cc: current@freebsd.org Subject: Re: problems with sysinstall Message-ID: <m1r80vawiv.wl@murmeldjur.it.su.se> 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>
index | next in thread | previous in thread | raw e-mail
At Wed, 29 Oct 2003 17:32:29 -0800 (PST),
Doug White wrote:
> 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.
I fail to understand either.
> yes, this is a change to -current. It is for your own safety.
I think this change in current is for the worse. I don't see why
I can't manage slices and partitions from my regular OS, but have
to boot up a CD to do the job. It's not even safer; I am perfectly
capable of destroying my disk layout from the CD too.
-Richard
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m1r80vawiv.wl>