Wed, Oct 29, 2003 at 05:44:44, sem (Sergey Matveychuk) wrote about "problems with
sysinstall":
SM> The first one: when I install -current on disk where WinXP on first
SM> slice, sysinstall brakes WinXP boot complete. I got 'Missing operation
SM> system' everyt
Wed, Oct 29, 2003 at 17:32:29, dwhite (Doug White) wrote about "Re: problems with
sysinstall":
>> 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.
DW> yes, this is a change to -curr
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 f
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
Sergey Matveychuk wrote:
> Richard Nyberg wrote:
> >Doug White wrote:
> > > 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
Doug White wrote:
> I don't know how WinXP's bootblocks are set up, but I have this setup on
> Win2k and it works as expected with boot0.
They are set up to boot directly from NTFS. An NTFS without a small
FAT/FAT16/FAT32 partition for initial load will prevent the boot
selector code from booting
Richard Nyberg wrote:
>Doug White wrote:
> > 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 pe
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
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
Sergey Matveychuk <[EMAIL PROTECTED]> wrote:
> > 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. S
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.
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
On Wed, 29 Oct 2003, Sergey Matveychuk wrote:
> The first one: when I install -current on disk where WinXP on first
> slice, sysinstall brakes WinXP boot complete. I got 'Missing operation
> system' everytime. Even I've tried 'fixboot' and reinstall WinXP.
> Helps only 'dd if=/dev/zero of=/dev/ad0
The first one: when I install -current on disk where WinXP on first
slice, sysinstall brakes WinXP boot complete. I got 'Missing operation
system' everytime. Even I've tried 'fixboot' and reinstall WinXP.
Helps only 'dd if=/dev/zero of=/dev/ad0 count=100' and reinstall WinXP
on clean disk.
When
I decided to grab the iso of 4.0-RC3 and do some installation testing,
since problems have plagued the previous releases and I wanted to do
my part to make sure that doesn't happen with 4.0. :-)
Initial installation from the ISO went flawlessly. My problems are
ocurring while using the post-inst
14 matches
Mail list logo
