Re: sendmail installed when it shouldn't during build world
On Sat, Apr 29, 2000 at 05:44:39PM -0500, Thomas T. Veldhouse wrote: > Hello. I have > > NO_SENDMAIL=true# do not build sendmail and related programs > > in my /etc/make.conf file. I use Postfix instead. I just built the world > and sendmail was built anyway and installed right over the links for Postfix. > I built on a 2418-4.0 system and cvsup'd to last nights stable sources. I thought the same thing, but that's not really what happened. See the man page for mailwrapper. Chris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: How good is AMI MegaRAID support?
- Original Message - From: "Mike Smith" <[EMAIL PROTECTED]> | If that's what they say, I'd be inclined to believe them. Since I've not | encountered any fatal problems with the 2.x firmware, I can't suggest | that upgrading would actually win you very much. I'm not even sure the HPDA flavor of cards is supported by FreeBSD to begin with. I hooked up my HPDA DAC960PL to a 4.0-STABLE box (cvsup'd last night) today and during bootup I get: mlx0: port 0xdc80-0xdcff irq 11 at device 13.0 on pci0 mlx0: couldn't allocate mailbox window device_probe_and_attach: mlx0 attach returned 6 The card and cable are good, they were last used with Win2K about two weeks ago. The disk cabinet (an HP "Disk Array" 5x1GB) I'm not sure about, though. When trying to initialize the array with Jetset, the HP DOS tool, and it just hangs there trying to do an inquiry on the drives. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
atdisk driver question...
I recently started upgrading several computers from 3.4S to 4.0S. The first one went off without a single problem, and is happily humming right next to me. With that success behind me, I decided to upgrade an old Toshiba Satellite Pro 2400CS notebook computer. It has worked perfectly with 3.3 and 3.4 in the past. I followed all of the instructions for the upgrade process. When I got to the point of rebooting with my spiffy new 4.0 kernel, the trouble began... All of the devices recognize fine. The root partition of the hard drive mounts. Then, I get an error that /dev/wd0s1f is larger than the partition. "fsck" also bombs out, telling me that it cannot read several sectors. If I reboot with my 3.4S kernel, the system comes up without a hitch. And yes, I created ad0, ad0s1[abcdefgh] to match the old "wd" device identifiers. The only difference I can think of between the two computers, is that the server I already upgraded has a 20GB hard drive, and an old BIOS. I had to partition that to get the whole thing recognized by FreeBSD. The notebook computer has the original Toshiba 503MB hard drive, which I used the "dangerously dedicated" option on when I installed. So, the short version of this question is, does the new "ad" driver not handle "dangerously dedicated" systems properly? Has anyone else seen this before? I'm going to try re-installing 3.4S using a "normal" disk partition, and see what happens. But, I wanted to send a message to the list while I'm doing that. Thanks! --Paul A. Howes To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: atdisk driver question...
"Paul A. Howes" wrote: > > I recently started upgrading several computers from 3.4S to 4.0S. The first > one went off without a single problem, and is happily humming right next to > me. With that success behind me, I decided to upgrade an old Toshiba > Satellite Pro 2400CS notebook computer. > > It has worked perfectly with 3.3 and 3.4 in the past. I followed all of the > instructions for the upgrade process. When I got to the point of rebooting > with my spiffy new 4.0 kernel, the trouble began... All of the devices > recognize fine. The root partition of the hard drive mounts. Then, I get > an error that /dev/wd0s1f is larger than the partition. "fsck" also bombs > out, telling me that it cannot read several sectors. If I reboot with my > 3.4S kernel, the system comes up without a hitch. And yes, I created ad0, > ad0s1[abcdefgh] to match the old "wd" device identifiers. First reaction would be to ask if you edited "etc/fstab". > The only difference I can think of between the two computers, is that the > server I already upgraded has a 20GB hard drive, and an old BIOS. I had to > partition that to get the whole thing recognized by FreeBSD. The notebook > computer has the original Toshiba 503MB hard drive, which I used the > "dangerously dedicated" option on when I installed. > So, the short version of this question is, does the new "ad" driver not > handle "dangerously dedicated" systems properly? Has anyone else seen this > before? I'm going to try re-installing 3.4S using a "normal" disk > partition, and see what happens. But, I wanted to send a message to the > list while I'm doing that. (I am not sure if this would apply given the error) Was the disk scanned for bad sectors w/bad144 on the initial install? -- Regards, Kevin G. Eliuk Technician | VerSys Communications Ltd. | http://www.versys.net To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Disk error and No /boot/loader
Hi all, Running 4.0-STABLE (though I had the same issue in 4.0-RELEASE). I've got a 10 gig IDE Hard drive with two FAT32 paritions taking 2 gig and 6 gig, and then a 2.4 gig FreeBSD partition. /- 100 megs /var - 100 megs swap - 268 megs /usr - 1800 megs On bootup, I get the following: >> FreeBSD/i386 BOOT Default: 0:ad(0,a)? boot: /load /boot/loader Disk error 0x1 (lba=0xfc093c) No /boot/loader The system continues to boot /kernel automatically and runs fine from there. (I've patched the kernel per kern/17422 to get top, vmstat etc. working). For the record, /boot/loader *does* exist. I've read an explanation about the 1024 cylinder limit, but I used the exact same configuration with 3.4-STABLE and /boot/loader worked fine. Any assistance would be appreciated. Regards, Roddie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Disk error and No /boot/loader
Booting above 8 Gb is not supported, due to BIOS problems. If you don't believe that, trying booting Windows above 8 Gb... :-) Alas, one developer had some interesting ideas on how to solve this problem recently. There is _unsupported_ options to make this work, but we can't activate them by default because not all hardware/firmware is compatible with it. Roddie Hasan wrote: > > Hi all, > > Running 4.0-STABLE (though I had the same issue in 4.0-RELEASE). I've got > a 10 gig IDE Hard drive with two FAT32 paritions taking 2 gig and 6 gig, > and then a 2.4 gig FreeBSD partition. > > /- 100 megs > /var - 100 megs > swap - 268 megs > /usr - 1800 megs > > On bootup, I get the following: > > >> FreeBSD/i386 BOOT >Default: 0:ad(0,a)? >boot: /load /boot/loader >Disk error 0x1 (lba=0xfc093c) >No /boot/loader > > The system continues to boot /kernel automatically and runs fine from > there. (I've patched the kernel per kern/17422 to get top, vmstat > etc. working). For the record, /boot/loader *does* exist. > > I've read an explanation about the 1024 cylinder limit, but I used the > exact same configuration with 3.4-STABLE and /boot/loader worked fine. > > Any assistance would be appreciated. > > Regards, Roddie > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] GPL certainly doesn't meet Janis Joplin's definition of freedom: "Freedom is just another word for nothing left to lose." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Disk error and No /boot/loader
Hi Daniel, Thanks for the quick reply.. > Booting above 8 Gb is not supported, due to BIOS problems. If you don't > believe that, trying booting Windows above 8 Gb... :-) Understood - But why would it have worked with 3.4 and the *exact* same configuration? (When I upgraded, I deleted the partition during install, and recreated it the same way). > problem recently. There is _unsupported_ options to make this work, but > we can't activate them by default because not all hardware/firmware is > compatible with it. I'd be happy to test them further.. :) Roddie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: How good is AMI MegaRAID support?
> On Sat, 29 Apr 2000 13:13:37 PDT, Mike Smith wrote: > > > >You leave out "how well you want it to perform" as well. All other > >things being equal, the PCI:SCSI adapters will give you better bang for > >your buck. > > Out of curiosity, how would a PCI-RAID (SCSI) adapter compare with > vanilla PCI-SCSI cards and vinum? It seems to me that the host CPU(s) > are much faster than the processors on the PCI-SCSI adapters. Or are > both of these "fast-enough" and thus performance differences are largely > an irrelevent consideration? (They both have similar software issues > but I suspect vinum is easier to debug. :) All other things being equal, software RAID is going to be faster. (ie. same disks, same # of SCSI channels, etc.) The hardware solution's sell there is: - better support/functionality (enclosure management, etc.) - better survivability (battery-backed cache) Plus you get a stack of SCSI channels onboard the card. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: How good is AMI MegaRAID support?
> > - Original Message - > From: "Mike Smith" <[EMAIL PROTECTED]> > > | If that's what they say, I'd be inclined to believe them. Since I've > not > | encountered any fatal problems with the 2.x firmware, I can't suggest > | that upgrading would actually win you very much. > > I'm not even sure the HPDA flavor of cards is supported by FreeBSD to > begin with. I hooked up my HPDA DAC960PL to a 4.0-STABLE box (cvsup'd > last night) today and during bootup I get: > > mlx0: port 0xdc80-0xdcff irq 11 at > device 13.0 on pci0 > mlx0: couldn't allocate mailbox window > device_probe_and_attach: mlx0 attach returned 6 What firmware revision are you running? This looks like your card isn't supporting a memory-mapped region for the mailbox window - I should check for this I guess. I'm fairly sure that 2.42 or later will work. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
