Re: problems with sysinstall
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' everytime. Even I've tried 'fixboot' and reinstall WinXP. SM> Helps only 'dd if=/dev/zero of=/dev/ad0 count=100' and reinstall WinXP SM> on clean disk. It can be better reported if you show here 1) 0th block of disk (where MBR and master PT resides) 2) full PT listing, with both standard fdisk and linux fdisk (from ports) and both of them before installing FreeBSD (when XP works) and after (when is already broken). SM> When I've installed first -current on first slice and second -current on SM> second slice I got booting only first one. I use grub and either I set SM> root(hd1,0) or root(hd1,1) (yes, it's a second disk) and 'chainloader SM> +1' and 'boot' I've got always first -current boot. Looks like problem SM> with boot sector where hardcoded booting from first slice (?). Yes, this is tied to algorithm of boot1. On first step, it founds first *active* BSD partition in master PT. If didn't find any, it tries to find BSD partition in any state (inactive, due to first step failure). When found, records its number and starts boot2. Boot switcher, called boot0 (/boot/boot0) or BootEasy (in sysinstall), changes active partition flag (see boot0cfg(8)). When you use GRUB to call chainloader, it will start boot1 with the described result. To select boots using GRUB, use UFS1 (GRUB can't understand UFS2), with "root (hd0,1); boot /boot/loader", or use boot0. SM> The second: when I've tried to save results from Fdisk or Label menu SM> I've got the message: 'ERROR: Unable to write data to disk ad0!' SM> Why? I can change slices and partitions only when I boot from CD-ROM. Current GEOM implementation is too restrictive and doesn't allow any write to disk which has opened slices/partitions. phk@ promised change of this as soon as someone gives working implementation. -netch- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problems with sysinstall
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 -current. It is for your own safety. Don't protect me when I didn't ask for it. FYI, phk@ said here some time ago how to remove this protection, and said that this nursery protection is in effect only until someone implements better algorithm. -netch- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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. 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. I agree, there should at least be some easy way to turn this behavior off. Maybe a foot.shoot sysctl of some kind. ;-) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problems with sysinstall
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 [EMAIL PROTECTED] "The future just ain't what it used to be" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problems with sysinstall
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 a CD to do the job. It's not even safer; I am perfectly
> > capable of destroying my disk layout from the CD too.
>
> Agree. Why I can't change active slice? Or add a partition? Or repair my
> master boot record?
> It's absolutely safe.
Its a major PITA and POLA violation IMHO.
The super-user should be able to foot-shoot whatever she wants to.
For example, you setup a production box with a 60 gig disk. You allocate
40 gig initially, leaving 20 gig as "reserve". Time passes. You now need
that extra 20 gig but can not down the server. You are stuffed.
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problems with sysinstall
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 Windows XP. FWIW, I use a small FAT32 partition in conjuction with BootMagic (from the PartitionMagic folks) with my dual boot XP systems (I have two of them). -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problems with sysinstall
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 perfectly capable of destroying my disk layout from the CD too. Agree. Why I can't change active slice? Or add a partition? Or repair my master boot record? It's absolutely safe. Sem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problems with sysinstall
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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problems with sysinstall
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 [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problems with sysinstall
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. So only way to boot -current is chainloader. Boot -current using the Windows XP bootloader. Unfortunately, I don't know of a single site with correct/complete information, but here are two pages to get you started (BACKUP your Windows partition before using the information in the following): http://bsdatwork.com/sections.php?op=viewarticle&artid=3 (Also read the OpenBSD section for additional WinXP info.) http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#NT-BOOTLOADER -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problems with sysinstall
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 redhat on the first disk and it works perfectly. Grub do not supporting UFS2. So only way to boot -current is chainloader. 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. Sem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problems with sysinstall
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 count=100' and reinstall WinXP > on clean disk. 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. It sounds like the active partition bit got misplaced, though. Blowing away the whole thing was a bit extreme. "Missing operating system" comes out of the DOS default bootblock, not the BIOS. > When I've installed first -current on first slice and second -current on > second slice I got booting only first one. I use grub and either I set > root(hd1,0) or root(hd1,1) (yes, it's a second disk) and 'chainloader > +1' and 'boot' I've got always first -current boot. Looks like problem > with boot sector where hardcoded booting from first slice (?). 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. > The second: when I've tried to save results from Fdisk or Label menu > I've got the message: 'ERROR: Unable to write data to disk ad0!' > Why? I can change slices and partitions only when I boot from CD-ROM. 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. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
problems with sysinstall
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've installed first -current on first slice and second -current on second slice I got booting only first one. I use grub and either I set root(hd1,0) or root(hd1,1) (yes, it's a second disk) and 'chainloader +1' and 'boot' I've got always first -current boot. Looks like problem with boot sector where hardcoded booting from first slice (?). The second: when I've tried to save results from Fdisk or Label menu I've got the message: 'ERROR: Unable to write data to disk ad0!' Why? I can change slices and partitions only when I boot from CD-ROM. Sem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
4.0-RC3 problems with sysinstall!!
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-install configure of sysinstall to add some packages (Configure/Packages). When attempting to install a package via FTP using a HTTP proxy (Squid to be exact), I found two problems. One is a minor problem, and the other is rather large, but they could be related. The minor problem is that the dialog box asking you for the address of the proxy server says the default port is 3128, but when I leave the port out, it initially tries port 21 instead. If I immediately select "Packages" again to make another attempt, it then correctly tries 3128, but says it still can't connect. Now here's the big problem... If I try selecting "Packages" a third time, I get a coredump (signal 11) and the terminal is screwed. No keyboard input works except Ctrl-C, which gives me successive prompts as if I were hitting the Enter key instead. Going to another terminal and killing csh on the offending terminal gives me a login prompt back. This is quite reproducible, since I've tried about 10 times with the same result. The only difference is that if I specify the correct port the first time, I get an immediate coredump instead of an error that it can't find the proxy server. Interestingly enough, after I run sysinstall a few times reproducing this, entering the proxy server address _without_ the port results in an immediate coredump as if I had entered the correct port the first time. No successive invocations of sysinstall show the initial behavior. Logging out and back in or using a fresh terminal doesn't change anything. Rebooting the system causes it to show the initial behavior again. That is particularly weird, since I don't see any weird environment variables or tempfiles laying around that would cause sysinstall to "keep state" like that. *boggle* Just as a datapoint, here is what is showing up in the Squid proxy logs each time I try this: 952812287.997 3 192.168.4.159 NONE/400 1100 GET / - NONE/- - -- Chris Dillon - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures. ( http://www.freebsd.org ) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
