Re: Speaking of ATAisms...
It seems Alex Zepeda wrote: > On Wed, 26 Jan 2000, Soren Schmidt wrote: > > > You could try to do a dd of the first say 2 cyls of the ZIP with > > both drivers and check is they are different, they shouldn't be... > > How many bytes is this again? Erhm, I've forgotten the geometry of the zip, just be sure to have the first two tracks. > > > > Well I haven't updated my kernel yet. *grin* > > > > Yeah, progress does have its victims :) > > Progress is indeed overrated. > > I wanna play mp3s through the pca device! ;) Wow! I havn't used the pca dev in years, but it should work I guess given the right bitrates etc :) -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Speaking of ATAisms...
On Wed, 26 Jan 2000, Soren Schmidt wrote: > Erhm, I've forgotten the geometry of the zip, just be sure to have > the first two tracks. [counting on fingers, then toes, then kunckles ensues] afd0: 96MB (196608 sectors), 96 cyls, 64 heads, 32 S/T, 512 B/S first 16k? zippy:~#dd if=/dev/afd0c bs=1k count=16 of=afd0c.output dd: /dev/afd0c: Input/output error zippy:~#Jan 26 00:38:32 zippy /kernel: afd0: error reading primary partition table reading fsbn 0 Hmm. I know this disk works with Windows 98SE. /me goes off and compiles a kernel with the wd driver instead - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: grep --binary-files=without-match (fwd)
On Wed, Jan 26, 2000 at 10:17:05AM +0600, Max Khon wrote: > hi, there! > > can we merge this when it's ready before freeze? > Of course, if Jordan approves. This will be a pretty small diff. Jordan? > -- Forwarded message -- > Date: Tue, 25 Jan 100 22:47:26 -0500 (EST) > From: Alain Magloire <[EMAIL PROTECTED]> > To: Paul Eggert <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] > Subject: Re: grep --binary-files=without-match > > Bonjour > > >Date: Tue, 25 Jan 2000 10:18:30 +0600 (NS) > >From: Max Khon <[EMAIL PROTECTED]> > > > >Sometimes I need to find all files that > >contain something. Sometimes I need only text files > >(e.g: vi `grep -rl xxx .` -- no binary files are desired). > > > > Thanks; that explains why you need a short-option equivalent to > > --binary-files=without-match. Here is a proposed patch to implement > > this, plus it fixes a couple of minor manual bugs I found while > > documenting this. It assumes all the previous patches that I've sent > > to the grep maintainer. > > > > 2000-01-25 Paul Eggert <[EMAIL PROTECTED]> > > > > * NEWS, doc/grep.1, doc/grep.texi: Add -I option. > > * src/grep.c (short_options, usage, main): Likewise. > > > > * doc/grep.texi: Fix some incorrect references to ASCII. > > Patch applied. > Ruslan, there will be a beta on alpha, this weekend, grep-2.4d, I will > notify you since FreeBSD'ers are the one pushing hard for the > --binary-files options. > > -- > alain > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message -- Ruslan Ermilov Sysadmin and DBA of the [EMAIL PROTECTED]United Commercial Bank, [EMAIL PROTECTED] FreeBSD committer, +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Speaking of ATAisms...
It seems Alex Zepeda wrote: > On Wed, 26 Jan 2000, Soren Schmidt wrote: > > > Erhm, I've forgotten the geometry of the zip, just be sure to have > > the first two tracks. > > [counting on fingers, then toes, then kunckles ensues] > > afd0: 96MB (196608 sectors), 96 cyls, 64 heads, 32 S/T, 512 B/S > > first 16k? Make that 2M just to be sure.. > zippy:~#dd if=/dev/afd0c bs=1k count=16 of=afd0c.output > dd: /dev/afd0c: Input/output error > zippy:~#Jan 26 00:38:32 zippy /kernel: afd0: error reading primary > partition table reading fsbn 0 > > Hmm. I know this disk works with Windows 98SE. Well, if it has problems with the partitions you should use /dev/afd0 and /dev/wfd0. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bzip2 in src tree
John LoVerso wrote: > > Again, lemmie get on my soap box, and ask have you looked at the man page, > > and compared the memory required when using -s to the memory required by > > gzip? > > Actually, lemmie get on my soap box and ask have you measured the time that > bunzip2 takes to run? While it does give better compression in many cases, it > is just too SLOW. Using "-s" on decompression just makes it slower. > > I played on a test machine (PII 233MHz 192Mb, spare ST34502LW disk) with some > large package binaries: > [...] > A decompression time of 13 seconds vs. 67 seconds (or 125 seconds with "-s). > Given that ports and packages need a multi-CD anyway, I don't think the speed > penalty of bzip2 is worth it. All this apply only when download cost is not considered. IMHO it is clean that CPU time nowadays is much less expensive than the online time, at least for dialup connections. Also you should take into consideration that usually you packing package ONCE, while number of users downloading this package could be very huge, so online costs savings from decreased download time multiplied by the number of downloads and divided by the costs associated with required CPU time increase will be considerable. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
USB on SMP
I've had reports that a machine having USB compiled into an SMP kernel panics. Could someone try the current version of the kernel and see what that brings. Don't plug in any device, that will panic your system for sure (I am working on that one). If init of the OHCI driver fails it should now clean up after itself properly. Cheers, Nick -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release failure
Thus spake Rajappa Iyer ([EMAIL PROTECTED]): > That's certainly possible, although it might be a good idea to use a > variable to point to a make.conf file. This way "make release" does > not have to be too aware of what "make world" requires in > /etc/make.conf. though a make release in any case should contain sendmail, as an example, and so far if you have NO_SENDMAIL in your /etc/make.conf it's somehow bad. Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Speaking of ATAisms...
On 25 Jan, Alex Zepeda wrote: > I haven't been able to mount an msdos (FAT16) formattted zip disk (well > any FAT16 formatted zip disk) for quite a while. Currently I'm trying to > mount afd0s4, but no such luck (I think the latest error is something > about reading the partition table). The wd driver used to grok the same > disks. Any thoughts? As a workaround use mtools (it's faster than msdosfs anyway [at least I noticed this with wfd]). mtools.conf: ---snip--- drive z: file="/dev/afd0s4" partition=4 ---snip--- ^^^ This is important. Bye, Alexander. -- A PBS mind in an MTV world. http://www.Leidinger.net Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic in dev/usb/usbdi.c
I copied stack trace. But this is handmade copy from console, so arguments are omitted, sorry. - panic() usbd_do_request_flags() csr_write_1() aue_miibus_readreg() MIIBUS_READREG() miibus_readreg() MIIBUS_READREG() ukphy_service() mii_tick() softclock() doreti_swi() link_elf_lookup_symbol() kldsym() syscall() Xint0x80_syscall() - Jun Kuriyama To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
This morning's make world.
This morning's make world > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include >-D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale >-DBROKEN_DES -DYP -I/usr/obj/usr/src/i386/usr/include -c >/usr/src/lib/libc/../libc/net/nsap_addr.c -o nsap_addr.o > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include >-D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale >-DBROKEN_DES -DYP -I/usr/obj/usr/src/i386/usr/include -c >/usr/src/lib/libc/../libc/net/rcmd.c -o rcmd.o > /usr/src/lib/libc/../libc/net/rcmd.c: In function `rresvport_af': > /usr/src/lib/libc/../libc/net/rcmd.c:337: too many arguments to function >`bindresvport_sa' > *** Error code 1 > > Stop in /usr/src/lib/libc. > *** Error code 1 > > Stop in /usr/src/lib. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. Thanks, ed To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
At 22:01 01/25/2000 +0100, you wrote: >It seems Tom Embt wrote: >> Don't mean to butt in here, I haven't really been following the thread - >> but I may have found a workaround/clue. I have a Sony CDU-55E (ooold 2x) >> on secondary master of the PIIX4 on my BP6. By going into the BIOS (the >> section of it where you would set CHS numbers, LBA, etc) and changing the >> secondary master device from "none" to "auto", I have gone from: >> >> BTW, this was on a kernel from around 20:00 GMT Jan 25 > >Interesting... > >What version is you ata-all.c ?? its damn close to the commit I just >made, that should fix that problem... > >-Søren > That was with 1.43 I just updated all the files in /usr/src/sys/dev/ata (ata-all.c v1.44) and made a new kernel. While rebooting I set the BIOS back to "none" and watched FreeBSD boot. No error :) - then I rebooted to kernel.old (1.43) without touching the BIOS and the error came back. Looks like you got it. Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: This morning's make world.
On Wed, 26 Jan 2000 07:35:32 PST, Edwin Culp wrote: > This morning's make world What are you trying to achieve with these e-mail messages? If you're looking for confirmation that ``make world'' is broken, then "Yes, it is." :-) And then when you get past _that_, you'll break in the includes, for which Peter Wemm posted a tentative fix which doesn't work 100%. :-) Watch your cvs-all mail for a commit on src/include/Makefile (something more recent than rev 1.107) and try again once you've got that. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: How can I use current release of FreeBSD?
On Tue, 25 Jan 2000 15:27:13 +0300, Grigory Kljuchnikov wrote: > How can I update 4.0-2110 directoty tree to 4.0-2124? > And how do these updates do properly? Where can I see more about this? The short answer is that you don't. Just wait for 4.0-RELEASE to come out in a few weeks. The long answer is contained in the FreeBSD Handbook, available online at: http://www.freebsd.org/handbook/ In particular, see the section titled The Cutting Edge: FreeBSD-current and FreeBSD-stable Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: y2k problem? naahhh...
On Tue, 25 Jan 2000 21:19:16 EST, John Baldwin wrote: > Ok then: > > 'egrep -v '^(---|+++|@@|[+-]#)', geez, am I the only one who knows regex? Are you the only person who doesn't know sed? ;-) My untested guess (since we all seem to be mouthing off the first thing that comes to mind) is sed 's/^\([^:#+@-][^:]*\):[^:]*:/\1:(password):/' This assumes that empty usernames and usernames which do not begin with an alphanumeric character won't appear. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ascii art in hosts.allow
On Wed, 26 Jan 2000 02:02:36 +1100, Andy Farkas wrote: > > So you'll notice that this file is an example and *demands* your > > attention in configuring your system properly. > > Change it to hosts.allow.sample then? No hosts.allow file is essentially > the same as the ALL:ALL:allow rule, no? No. In the absence of a hosts.allow file, hosts_access(3) denies all. Can we please move onto something else now. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ascii art in hosts.allow
On Wed, 26 Jan 2000, Sheldon Hearn wrote:
> > Change it to hosts.allow.sample then? No hosts.allow file is essentially
> > the same as the ALL:ALL:allow rule, no?
>
> No. In the absence of a hosts.allow file, hosts_access(3) denies all.
Not according to what I read in 'man 5 hosts_access' - especially the
second paragraph titled "ACCESS CONTROL FILES".
>
> Can we please move onto something else now. :-)
>
But...but... ITS SUCH AN EYE-SORE IMHO.
> Ciao,
> Sheldon.
>
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ascii art in hosts.allow
On Thu, 27 Jan 2000 03:57:51 +1100, Andy Farkas wrote: > > No. In the absence of a hosts.allow file, hosts_access(3) denies all. > > Not according to what I read in 'man 5 hosts_access' - especially the > second paragraph titled "ACCESS CONTROL FILES". Wtf?! You're right. I'm frightened now. > But...but... ITS SUCH AN EYE-SORE IMHO. While this thread has been fun? C'mon, look around, there are bigger fish to fry. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Today's buildworld breakages
Here's the latest fault, from a cvsup just performed: cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libc/../libc/net/rcmd.c -o rcmd.o /usr/src/lib/libc/../libc/net/rcmd.c: In function `rresvport_af': /usr/src/lib/libc/../libc/net/rcmd.c:337: too many arguments to function `bindresvport_sa' *** Error code 1 Stop in /usr/src/lib/libc. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
help! need kernel!
hello! I have Abit motherboard with ATA-66 support. I try to install FreeBSD-CURRENT, all good when install, but after reboot kernel boots, but ask me a root device, when I press '?', there are no 'ad' device (this is my HDD). ;( As I understand - there are no support in that kernel for my HDD... ;( As I understand there are one way to help me - create new kernel with ata-pci0 support. If somebody can help me - please help! Thanks! P.S. I have latest cvs tree (but on the 3.4 box) and have latest kern.flp and mfsroot.flp. Regards, Listopad Alexandr ([EMAIL PROTECTED]), LAA7-RIPE ZGIA, Zaporozhye, Ukraine. http://www.zgia.zp.ua. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
cvsup8
What happened, it fell off the edge of the earth? Nslookup can't find it anymore. Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Sendmail on current
Firs tof all, I apologize if I am reasking a question, since I haven't done a good job of keeping up on my -current mail. Chastisment humbly accepted. I did check the -current archive on www.freebsd.org and have not seen a mention of this. On my last two make worlds I have had trouble with my system restarting. It hangs on the startup of sendmail. I have replaced sendmail on my system with Postfix. Addtionally, I have the following line in /etc/make.conf NO_SENDMAIL=true The only references to sendmail that I see in the UPDATING file is about the move of the sendmail.cf, which doesn't seem relevant. Since starting this email, I have created an /etc/mailer.conf. If this resolves it, I will be surprised, but feel free to let me know how stupid I am being. Reinstalling the Postfix port resolves this, as you might expect. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: help! need kernel!
On Wed, Jan 26, 2000 at 07:26:30PM +0200, Alexandr Listopad wrote: > hello! > > I have Abit motherboard with ATA-66 support. > I try to install FreeBSD-CURRENT, all good when install, but after reboot > kernel boots, but ask me a root device, when I press '?', there are no > 'ad' device (this is my HDD). ;( As I understand - there are no support in > that kernel for my HDD... ;( > > As I understand there are one way to help me - create new kernel with > ata-pci0 support. The boot floppies have ATA in the kernel. I installed a new system on a BP6 with the hard drive on one of the HPT366 controllers just fine about two weeks ago. Sorry, but I have no idea what is going on here.. I just wanted to say that it worked for me ata-pci1: port 0xd400-0xd4ff,0xd000-0xd003, 0xcc00-0xcc07 irq 18 at device 19.0 on pci0 ... ad4: 12949MB disk at ata2 as master mode UDMA66 BTW, sos, if you're reading this: I like this format for reporting the hard drives present a lot better :-). -Chris -- [EMAIL PROTECTED] [EMAIL PROTECTED] Abbotsford, BC, Canada To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvsup8
On Wed, Jan 26, 2000 at 01:38:44PM -0500, Chuck Robey wrote: > What happened, it fell off the edge of the earth? Nslookup can't find it > anymore. I seem to recall an announcement from John yesterday or so, saying that it was going to fall off the edge of the earth temporarily. -- Matthew Hunt <[EMAIL PROTECTED]> * Stay close to the Vorlon. http://www.pobox.com/~mph/ * To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sendmail on current
On Wed, 26 Jan 2000 11:47:04 MST, Matt Miller wrote: > Chastisment humbly accepted. *chastise* :-) > The only references to sendmail that I see in the UPDATING file is > about the move of the sendmail.cf, which doesn't seem relevant. It's sorta relevant. > Since starting this email, I have created an /etc/mailer.conf. Should be /etc/mail/mailer.conf. There are two things that would have saved you from this problem (and the chastisement above :-) : 1) Reading your cvs-all mail. 2) Using mergemaster(1). Have fun. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvsup8
On Wed, 26 Jan 2000, Matthew Hunt wrote: > On Wed, Jan 26, 2000 at 01:38:44PM -0500, Chuck Robey wrote: > > > What happened, it fell off the edge of the earth? Nslookup can't find it > > anymore. > > I seem to recall an announcement from John yesterday or so, saying > that it was going to fall off the edge of the earth temporarily. Yeah, now I remember, thanks guys. I'd thought that huge cvsup thread was about 8 coming on line, not going off. > > Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: help! need kernel!
On Wed, Jan 26, 2000 at 07:26:30PM +0200, Alexandr Listopad wrote: > hello! > > I have Abit motherboard with ATA-66 support. > I try to install FreeBSD-CURRENT, all good when install, but after reboot > kernel boots, but ask me a root device, when I press '?', there are no > 'ad' device (this is my HDD). ;( As I understand - there are no support in > that kernel for my HDD... ;( > > As I understand there are one way to help me - create new kernel with > ata-pci0 support. > > If somebody can help me - please help! > > Thanks! > > P.S. I have latest cvs tree (but on the 3.4 box) and have latest kern.flp > and mfsroot.flp. > > Its a simply. Install 3.4 with full sources, then use CVSup with "." tag and upgrade your sources tree. Then compile & install new kernel & do make world. Rgdz, Sergey A. Osokin, [EMAIL PROTECTED] http://www.FreeBSD.ORG.ru/~osa/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: help! need kernel!
In <[EMAIL PROTECTED]> Alexandr Listopad <[EMAIL PROTECTED]> wrote: > hello! > > I have Abit motherboard with ATA-66 support. > I try to install FreeBSD-CURRENT, all good when install, but after reboot > kernel boots, but ask me a root device, when I press '?', there are no > 'ad' device (this is my HDD). ;( As I understand - there are no support in > that kernel for my HDD... ;( What is the BIOS version on your motherboard ? In my case - ABIT BP6 two Celeron motherboard with HPT66 controller - there was problems with disks numbering and booting by BIOS when there are HDDs on both regular and ATA-66 controllers. Those problems was resolved by changing the BIOS to the next version (NJ). N.Dudorov To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: locking problem FreeBSD 3.4 - kermit and mgetty
Hi, On Tue, Jan 25, 2000 at 08:51:40PM +0100, Christoph Kukulies wrote: > But as a result mgetty gets into kermit's ways such that when a > modem connection is made I suddenly get a modem prompt like > +FCON as if someone (mgetty) is either messing with my local > or the remote modem while kermit opens the connection. The modem is in fax mode, and has established a fax connection. Have kermit send an AT+FCLASS=0 first. gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany [EMAIL PROTECTED] fax: +49-89-35655025[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
Soren Schmidt wrote: > > It seems Alex wrote: > > > You need to update.. > > > > > > OK - I've just updated. Here goes again: > > > > ata1-slave: ata_command: timeout waiting for intr > > ata1-slave: identify failed > > ad0: 6194MB [13424/15/63] at ata0-master using > > UDMA33 > > acd0: CDROM at ata1-master using PIO4 > > Mounting root from ufs:/dev/ad0s2a > > > I wouldn't be surprised if ATAPI_CMD_IDENTIFY failed on ata1-master, but > > why does it say ata1-slave? It's a notebook PC, so unfortunately I'm > > not sure how it's all connected. > > Apparently it thinks something is there, could you mail me a complete > verbose bootlog (dmesg) please, and I'll try to figure out what is > going wrong.. OK - here's the part relevant to ata: ata-pci0: port 0xfcf0-0xfcff at device 1.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xfcf0 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xfcf8 ata1: mask=03 status0=00 status1=00 ata1: mask=03 status0=00 status1=00 ata1: devices = 0xc ata1 at 0x0170 irq 15 on ata-pci0 ... (delay) ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ata0-master: success setting up UDMA2 mode on PIIX4 chip ad0: ATA-4 disk at ata0 as master ad0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad0: piomode=4 dmamode=2 udmamode=2 cblid=0 Creating DISK ad0 Creating DISK wd0 ata1-master: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 ata1-master: success setting up PIO4 mode on generic chip acd0: CDROM drive at ata1 as master acd0: read 4134KB/s (4134KB/s), 128KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm photo disc loaded, unlocked Mounting root from ufs:/dev/ad0s2a ad0s1: type 0xb, start 63, end = 5322239, size 5322177 : OK ad0s2: type 0xa5, start 5322240, end = 12685679, size 7363440 : OK Any ideas? Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
NFS /usr/src and /usr/obj?
I'm wondering how one can do a buildworld on a machine, and then NFS mount /usr/src and /usr/obj on a client machine and do an installworld of the freshly built sources? I've been looking in the archives without much success, and haven't figured it out by reading the makefiles yet. Can anyone shed some light on this? -- Kyle Mestery| Ancor Communications [EMAIL PROTECTED]| http://www.freebsd.org/ [EMAIL PROTECTED] | http://www.netwinder.org/ Protect your right to privacy: www.freecrypto.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NFS /usr/src and /usr/obj?
On Wed, Jan 26, 2000 at 04:26:20PM -0600, [EMAIL PROTECTED] wrote: > I'm wondering how one can do a buildworld on a machine, and then NFS > mount /usr/src and /usr/obj on a client machine and do an installworld > of the freshly built sources? I've been looking in the archives without > much success, and haven't figured it out by reading the makefiles yet. > Can anyone shed some light on this? We've done this several times - though we often just use rdist or rsync these days ;-) David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NFS /usr/src and /usr/obj?
In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED] writes: >I'm wondering how one can do a buildworld on a machine, and then NFS >mount /usr/src and /usr/obj on a client machine and do an installworld >of the freshly built sources? I've been looking in the archives without >much success, and haven't figured it out by reading the makefiles yet. >Can anyone shed some light on this? I've done it in the past, but not recently. Consider the alternative of mounting the destination on the compilehost and make install DESTDIR=/mnt -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NFS /usr/src and /usr/obj?
Sure. This can be done with no problems. It is, in fact, a good way to put the same OS on multiple machines. -Steve - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, January 26, 2000 5:26 PM Subject: NFS /usr/src and /usr/obj? > I'm wondering how one can do a buildworld on a machine, and then NFS > mount /usr/src and /usr/obj on a client machine and do an installworld > of the freshly built sources? I've been looking in the archives without > much success, and haven't figured it out by reading the makefiles yet. > Can anyone shed some light on this? > > -- > Kyle Mestery | Ancor Communications > [EMAIL PROTECTED] | http://www.freebsd.org/ > [EMAIL PROTECTED] | http://www.netwinder.org/ > Protect your right to privacy: www.freecrypto.org > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ipfilter and ipfstat
On Tue, Jan 25, 2000 at 09:23:23PM -0800, Kris Kennaway wrote: > On Tue, 25 Jan 2000, the Webslave wrote: > > > > Okay, so I finally decided to take the plunge and check out ipfilter. ipf > > > seemed to load my ruleset with no problems, but ipfstat dies with: > > > > > > ioctl(SIOCGETFS): Invalid argument > > > > And what would that ruleset be? > > > > # Default to deny > block in log on tun0 from any to any [snip] I have tested your ruleset in my ipf/ipfstat version. The one I have comes from the 4.0-2124-CURRENT snapshot, since I haven't had the time to cvsup/make-world since. The results of the tests are shown below, and as you can see ipfstat reports the rules correctly. hades# ipf -FA hades# cd /tmp hades# ipf -f ipf.conf hades# ipfstat -nio @1 pass out quick on tun0 proto tcp/udp from any to any keep state @2 pass out quick on tun0 proto icmp from any to any keep state @3 pass out quick on lo0 from any to any @1 block in log on tun0 from any to any @2 block in quick on tun0 from 192.168.0.0/16 to any @3 block in quick on tun0 from 172.16.0.0/12 to any @4 block in quick on tun0 from 10.0.0.0/8 to any @5 block in quick on tun0 from 127.0.0.0/8 to any @6 pass in quick on tun0 proto tcp from any to any port = 12345 flags S/FSRPAU keep state keep frags @7 pass in quick on tun0 proto udp from any to any port = 31337 keep state @8 pass in quick on lo0 from any to any hades# ipf -FA hades# ipf -f /etc/ipf.conf What version of ipfilter/ipfstat are you using? I don't now if cvsup'ing your sources to a more recent version might help at all, but I don't see a problem with these rules and ipfstat... I'm sorry if that is not of any help to you, but I can't seem to find anything wrong here :/ -- Giorgos Keramidas, < keramida @ ceid . upatras . gr > "Don't let your schooling interfere with your education." [Mark Twain] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm - stutters
It is rumoured that Devin Butterfield had the courage to say: > I too notice these problems of mpg123 skipping during disk activity or X > graphics ops but I have always had these problems, both with -STABLE and > -CURRENT. I notice this with xmms too. So this is nothing new. Isn't this simply a typical issue of IDE hardware? I too notice xmms skipping on heavy disk activity (typically the find command that runs from cron at 01:59). This happens even though I have two processors and a disk that can do 16 Mb/sec on UDMA66. One would expect such a system to be able to do a find and play mp3's simultaneously. However, AFAIK the IDE hardware typically handles only one request at a time and handles all requests sequentially, contrary to scsi. It may thus happen that the read requests from xmms, small as they may be, get delayed too long and unnecessary. I'm not an expert on this, but I believe scatter/gather is the way scsi handles this problem in hardware. Perhaps the ata driver could be made to do something similar on the driver level. I have experienced significantly better responsiveness during high disk usage of much slower systems that are running with scsi disks only. In fact, I have a 486 that has better response times (it has an EISA bus and adaptec 2740 scsi with a disk that can do -- and does! -- 8 Mb/sec disk->memory) than my Abit BP6 dual celeron UDMA66 system during the cron job at 1:59. Regards, Dave Boers. -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NFS /usr/src and /usr/obj?
Hi, On Wed, 26 Jan 2000, Poul-Henning Kamp wrote: > I've done it in the past, but not recently. > > Consider the alternative of mounting the destination on the compilehost > and make install DESTDIR=/mnt > Thanks to everyone for the replies. It works fine for me now. I was automounting all of the directories from the server using AMD, and then I had /usr/src and /usr/obj as symlinks to their respective automount locations. This apparently was what was causing me problems. With /usr/src and /usr/obj directly mounted themselves, the installworld is proceeding as I type this. Again, thanks for all the responses. -- Kyle Mestery| Ancor Communications [EMAIL PROTECTED]| http://www.freebsd.org/ [EMAIL PROTECTED] | http://www.netwinder.org/ Protect your right to privacy: www.freecrypto.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
namei() costs for symlink farms and big dirs
Can I pick some FreeBSD experts brains off-list please? anybody who can comment on the cost(s) of running large flat directories of symlinks (eg using GNU stow for /usr/local/bin) especially over NFS? cheers -George To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make release weirdness?
I fianlly got -current from this morning to build and install so I started a make release this afternoon only to hit the USA_RESIDENT block. I modified /etc/make.conf to include the appropriate line and started again. After awhile it hit the same block: -- >>> elf make world started on Thu Jan 27 02:41:33 GMT 2000 -- !! >>> You must define the value of USA_RESIDENT as 'YES' or >>> 'NO' as appropriate, in the environment or /etc/make.conf >>> before building can proceed. !! *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. root@deimos:/usr/src/release$ cat /etc/make.conf USA_RESIDENT=YES root@deimos:/usr/src/release$ Shouldn;t it be pulling the USA_RESIDENT value out of /etc/make.conf? Am I missing something here? -Bill -- -=| --- B i l l S w i n g l e --- http://www.dub.net/ -=| [EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED] -=| Different all twisty a of in maze are you, passages little To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: namei() costs for symlink farms and big dirs
:Can I pick some FreeBSD experts brains off-list please? : :anybody who can comment on the cost(s) of running large :flat directories of symlinks (eg using GNU stow for /usr/local/bin) :especially over NFS? : :cheers : -George There is definitely more overhead but you may not notice it. We ran just about everything at BEST through softlinks (1), sometimes several levels, and never noticed any problems. (1) home directories, most configuration files, htdocs, virtual host directory links. -Matt Matthew Dillon <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ipsec errors
I was just wondering how to get rid of these errors in my startup: Jan 26 22:12:19 culverk inetd[739]: ftp/tcp: ipsec initialization failed; out entrust Jan 26 22:12:19 culverk inetd[739]: telnet/tcp: ipsec initialization failed; in entrust Jan 26 22:12:19 culverk inetd[739]: telnet/tcp: ipsec initialization failed; out entrust Jan 26 22:12:19 culverk inetd[739]: finger/tcp: ipsec initialization failed; in entrust Jan 26 22:12:19 culverk inetd[739]: finger/tcp: ipsec initialization failed; out entrust Jan 26 22:12:19 culverk inetd[739]: ntalk/udp: ipsec initialization failed; in entrust Jan 26 22:12:19 culverk inetd[739]: ntalk/udp: ipsec initialization failed; out entrust Maybe there was a message on here that I overlooked, I'm not sure, but how exactly do I get rid of them? = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release weirdness?
Today Bill Swingle wrote:
> !!
> >>> You must define the value of USA_RESIDENT as 'YES' or
> >>> 'NO' as appropriate, in the environment or /etc/make.conf
> >>> before building can proceed.
> !!
> *** Error code 1
>
> Stop in /usr/src/release.
> root@deimos:/usr/src/release$ cat /etc/make.conf
> USA_RESIDENT=YES
> root@deimos:/usr/src/release$
>
>
> Shouldn;t it be pulling the USA_RESIDENT value out of /etc/make.conf?
> Am I missing something here?
It's probably looking in ${CHROOTDIR}/etc/make.conf and finding
the freshly cvs co'ed copy with that commented out. :(
--
Jack O'NeillSystems Administrator / Systems Analyst
[EMAIL PROTECTED] Crystal Wind Communications, Inc.
Finger [EMAIL PROTECTED] for my PGP key.
PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD
enriched, vcard, HTML messages > /dev/null
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: make release weirdness?
On Wed, Jan 26, 2000 at 10:42:54PM -0500, jack wrote:
> Today Bill Swingle wrote:
>
> > !!
> > >>> You must define the value of USA_RESIDENT as 'YES' or
> > >>> 'NO' as appropriate, in the environment or /etc/make.conf
> > >>> before building can proceed.
> > !!
> > *** Error code 1
> >
> > Stop in /usr/src/release.
> > root@deimos:/usr/src/release$ cat /etc/make.conf
> > USA_RESIDENT=YES
> > root@deimos:/usr/src/release$
> >
> >
> > Shouldn;t it be pulling the USA_RESIDENT value out of /etc/make.conf?
> > Am I missing something here?
>
> It's probably looking in ${CHROOTDIR}/etc/make.conf and finding
> the freshly cvs co'ed copy with that commented out. :(
Yeah, this makes a lot of sense, especially it's working in a chrooted
environment. Thanks :)
-Bill
--
-=| --- B i l l S w i n g l e --- http://www.dub.net/
-=| [EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED]
-=| Different all twisty a of in maze are you, passages little
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ipsec errors
> I was just wondering how to get rid of these errors in my startup: > > Jan 26 22:12:19 culverk inetd[739]: ftp/tcp: ipsec initialization > failed; out entrust > Jan 26 22:12:19 culverk inetd[739]: telnet/tcp: ipsec initialization > failed; in entrust > Jan 26 22:12:19 culverk inetd[739]: telnet/tcp: ipsec initialization > failed; out entrust > Jan 26 22:12:19 culverk inetd[739]: finger/tcp: ipsec initialization > failed; in entrust > Jan 26 22:12:19 culverk inetd[739]: finger/tcp: ipsec initialization > failed; out entrust > Jan 26 22:12:19 culverk inetd[739]: ntalk/udp: ipsec initialization > failed; in entrust > Jan 26 22:12:19 culverk inetd[739]: ntalk/udp: ipsec initialization > failed; out entrust > > Maybe there was a message on here that I overlooked, I'm not sure, but how > exactly do I get rid of them? Now IPsec related control functionalities are added to inetd, and when kernel is not compiled with IPSEC related options, IPsec related socket initialization fails and those messages are print out. It is not harmful but I should have lower the syslog level, sorry. I'll soon fix it. Thanks, Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
BROKEN WORLD
Peter, I'd like to see your world log, and the output of cd src/share/mk ; cvs diff bsd.kmod.mk. I get the following error when I try to build world as of about 2 hours ago. I just did a cvsup and only things in lib and ports updated. ===> sys/modules/vpo @ -> /home/imp/FreeBSD/src/sys machine -> /home/imp/FreeBSD/src/sys/i386/include perl @/kern/makedevops.pl -h @/kern/bus_if.m perl @/kern/makedevops.pl -h @/kern/device_if.m make: don't know how to make ppbus_if.h. Stop Yours in frustration, Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: BROKEN WORLD
Warner Losh writes: : I'd like to see your world log, and the output of : cd src/share/mk ; cvs diff bsd.kmod.mk. I get the following error : when I try to build world as of about 2 hours ago. I just did a cvsup : and only things in lib and ports updated. Ummm, I think cvs did something strange... I retract this statement until such time as I can make sure that cvs didn't do something stupid. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ipsec errors
> > Maybe there was a message on here that I overlooked, I'm not sure, but how
> > exactly do I get rid of them?
>
> It is not harmful but I should have lower the syslog level,
> sorry.
> I'll soon fix it.
I just added debug flag check instead of changing syslog
level.
Could you please try the following patch to
usr.sbin/inetd/inetd.c ?
Thanks,
Yoshinobu Inoue
Index: inetd.c
===
RCS file: /home/ncvs/src/usr.sbin/inetd/inetd.c,v
retrieving revision 1.75
diff -u -r1.75 inetd.c
--- inetd.c 2000/01/25 14:52:10 1.75
+++ inetd.c 2000/01/27 04:41:15
@@ -1256,7 +1256,8 @@
buf = ipsec_set_policy(policy_in, strlen(policy_in));
if (buf != NULL) {
if (setsockopt(sep->se_fd, level, opt,
- buf, ipsec_get_policylen(buf)) < 0) {
+ buf, ipsec_get_policylen(buf)) < 0 &&
+ debug != 0) {
syslog(LOG_ERR,
"%s/%s: ipsec initialization failed; %s",
sep->se_service, sep->se_proto,
@@ -1271,7 +1272,8 @@
buf = ipsec_set_policy(policy_out, strlen(policy_out));
if (buf != NULL) {
if (setsockopt(sep->se_fd, level, opt,
- buf, ipsec_get_policylen(buf)) < 0) {
+ buf, ipsec_get_policylen(buf)) < 0 &&
+ debug != 0) {
syslog(LOG_ERR,
"%s/%s: ipsec initialization failed; %s",
sep->se_service, sep->se_proto,
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: BPF bug or not?
On Wed, 26 Jan 2000, Yevmenkin, Maksim N, CSCIO wrote: > > > I've just found that read from /dev/bpfX never return > > EAGAIN/EWOULDBLOCK. > > > It means that when you do a non blocking read and there is > > no data you will > > > always get 0. > [ untested fix removed :) ] > > Yes, it works. But it returns EAGAIN for both O_RDONLY|O_NONBLOCK and > O_RDWR|O_NONBLOCK open modes. In the same time pipe returns 0 for > O_RDONLY|O_NONBLOCK mode and EAGAIN for O_RDWR|O_NONBLOCK. > > It there any specs for "read" system call? Well, POSIX is very complete for read() on regular files and pipes (both ordinary pipes and fifos. read() on a pipe with no data and writers returns 0 because that case is considered to be EOF. O_RDWR for fifos gives undefined behaviour. I don't know of any legitimate use for it. It has the illegitimate use of talking to oneself using only one channel :-). This gives the EAGAIN behaviour for O_RDWR|O_NONBLOCK. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FIC SD-11 not happy with ata
%> %It seems Russell L. Carter wrote: %> %> %It seems Russell L. Carter wrote: %> %> %> %> %> %> I swapped out my motherboard and am seeing this now: %... % %> %> )(*&$#%$# stupid magazine benchmarkers never actually test %> things like IO... gr % %We in the computer hardware business have a better name for ``FIC'', %Fix It Continuously. They are not known for their quality, or should %I say they are known for their lack of quality :-). Yah... as before ok I fixed this by swapping in an ASUS K7M (forget the audio, I can't figure that one out) For all of the bitching on Soren's ata driver, I'd like to make this observation on a 500MHz/256MB ASUS K7 systemm, bonnie -s 500: ad0: 13783MB [28005/16/63] at ata0-master using UDMA33 Seeker 1...Seeker 2...Seeker 3...start 'em...done...done...done... ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 500 8273 27.7 7734 8.4 3009 7.6 8549 31.8 8828 7.2 134.6 1.3 ad1: 19574MB [39770/16/63] at ata1-master using UDMA66 Seeker 1...Seeker 2...Seeker 3...start 'em...done...done...done... ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 500 20650 84.1 20805 30.8 5644 14.8 22111 86.2 21253 21.1 148.9 1.4 Um, that ad1 drive cost me $224US, direct from the IBM mothership. Best regards, Russell %-- %Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] % % %To Unsubscribe: send mail to [EMAIL PROTECTED] %with "unsubscribe freebsd-current" in the body of the message % To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: OpenSSL docs for FAQ
Only recommendation I might pass on is being consistant in the use of "USA" instead of "US". The document starts off with references to "USA" and then changes to "US". Following the custom used in current crypto source (i.e. "USA_RESIDENT" in make.conf) I would suggest using "USA". Keith According to the writings of Kris Kennaway > > Can people please review this for style and content, for inclusion in > the FAQ? I'll also need someone to mark it up once it's ready since SGML > is currently not among my abilities :-) > [ ... ] > > However, some of the algorithms (specifically, RSA and IDEA) included > in OpenSSL are protected by patents in the USA and elsewhere and are > not available for unrestricted use. In addition, export of > cryptographic code from the USA has (until recently) been heavily > restricted. As a result, FreeBSD has available three different > versions of OpenSSL depending on geographical location (US/non-US) and > compliance with the RSAREF license (see below). [ ... ] > People who are located outside the USA, and who obtain their crypto > sources from internat.freebsd.org (the International Crypto > Repository), will build a version of OpenSSL which includes RSA, but > does not include IDEA, because the latter is restricted in certain > locations elsewhere in the world. In the future a more flexible > identification system may allow building of IDEA in countries for > which it is not restricted. > > US USERS: ^^ (and others follow throughout the remainder of the doc) -- Keith Ward N5OOD [EMAIL PROTECTED] ...!rwsys!rowdy!kward =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= I don't suffer from insanity, I enjoy every minute of it. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sendmail on current
Matt Miller <[EMAIL PROTECTED]> writes: > It hangs on the startup of sendmail. I have replaced sendmail on my > system with Postfix. Addtionally, I have the following line in > /etc/make.conf > > NO_SENDMAIL=true That's ok : the 'make replace' of the postfix port replace /usr/sbin/sendmail (see the /usr/port/mail/postfix/Makefile) but, now in CURRENT, /usr/sbin/sendmail is a symlink to /usr/sbin/mailwrapper (see man mailwrapper). In CURRENT, the command 'sendmail' runs the mailwrapper program which, in turn, runs the correct ones according to /etc/mail/mailer.conf (there's an exemple in 'man mailer.conf'). So, to take advantage of MTA wrapping, don't do a 'make replace' when installing Postfix but rather edit /etc/mail/mailer.conf. Hope this helps, -- Eric Jacoboni Ta mère, son mot de passe c'est « toto » ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: help! need kernel!
cpiazz>> hello! cpiazz>> cpiazz>> I have Abit motherboard with ATA-66 support. cpiazz>> I try to install FreeBSD-CURRENT, all good when install, but after reboot cpiazz>> kernel boots, but ask me a root device, when I press '?', there are no cpiazz>> 'ad' device (this is my HDD). ;( As I understand - there are no support in cpiazz>> that kernel for my HDD... ;( cpiazz>> cpiazz>> As I understand there are one way to help me - create new kernel with cpiazz>> ata-pci0 support. Thanks you for your answer! cpiazz> cpiazz>The boot floppies have ATA in the kernel. I installed a new system on cpiazz>a BP6 with the hard drive on one of the HPT366 controllers just fine cpiazz>about two weeks ago. Sorry, but I have no idea what is going on cpiazz>here.. I just wanted to say that it worked for me I had installed FreeBSD-CURRENT on my PC, from flopppies and ftp, all ok. But after reboot and press F3 new kernel boots (!) and after test wd0 and some other devices (no ata-pci) ask me: from what partition we will boot? My root partition is ad4s3a, but its don't work... ;< I have a question - where from the kernel boots? ;) And why it don't work on ad4s3a cpiazz> cpiazz>ata-pci1: port 0xd400-0xd4ff,0xd000-0xd003, cpiazz>0xcc00-0xcc07 irq 18 at device 19.0 on pci0 cpiazz>... cpiazz>ad4: 12949MB disk at ata2 as master mode UDMA66 cpiazz> cpiazz>BTW, sos, if you're reading this: I like this format for reporting cpiazz>the hard drives present a lot better :-). cpiazz> What is your HPT-366 (Abit BE6) BIOS ver? Thanks. Regards, Listopad Alexandr ([EMAIL PROTECTED]), LAA7-RIPE ZGIA, Zaporozhye, Ukraine. http://www.zgia.zp.ua. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
My atapi-cdrom is back!
with version 1.44 of ata-all.c i have my cdrom back. Last evening making world succeeded with a current system! -- Fritz Heinrichmeyer mailto:[EMAIL PROTECTED] FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FIC SD-11 not happy with ata
It seems Russell L. Carter wrote: > > Yah... as before ok I fixed this by swapping in an ASUS K7M (forget the audio, > I can't figure that one out) Working on it :) > For all of the bitching on Soren's ata driver, I'd like to > make this observation on a 500MHz/256MB ASUS K7 systemm, bonnie -s 500: > > ad1: 19574MB [39770/16/63] at ata1-master using UDMA66 > > Seeker 1...Seeker 2...Seeker 3...start 'em...done...done...done... > ---Sequential Output ---Sequential Input-- --Random- > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks-- > MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CU > 500 20650 84.1 20805 30.8 5644 14.8 22111 86.2 21253 21.1 148.9 1.4 > > Um, that ad1 drive cost me $224US, direct from the IBM mothership. Yup, those new IBM drives (the DPTA series) are pretty cool -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
It seems Alex wrote: > > OK - here's the part relevant to ata: > > > ata-pci0: port 0xfcf0-0xfcff at device > 1.1 on pci0 > ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xfcf0 > ata0: mask=03 status0=50 status1=00 > ata0: mask=03 status0=50 status1=00 > ata0: devices = 0x1 > ata0 at 0x01f0 irq 14 on ata-pci0 > ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xfcf8 > ata1: mask=03 status0=00 status1=00 > ata1: mask=03 status0=00 status1=00 > ata1: devices = 0xc Here it sees two devices, apparently you cdrom is reacting both on master AND slave addresses :( > ata1-slave: ata_command: timeout waiting for intr > ata1-slave: identify failed But when we try to talk to it it fails... > ata0-master: success setting up UDMA2 mode on PIIX4 chip But when we try to talk to it it fails... > Any ideas? I'll try to come up with a patch that solves this... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: BPF bug or not?
Bruce, [...] > > I've just found that read from /dev/bpfX never return > EAGAIN/EWOULDBLOCK. > > It means that when you do a non blocking read and there is > no data you will > > always get 0. > > > > Does it suppose work this way? > > I think it is a bug. Perhaps applications depend on it. > > Untested fix: [ untested fix removed :) ] Yes, it works. But it returns EAGAIN for both O_RDONLY|O_NONBLOCK and O_RDWR|O_NONBLOCK open modes. In the same time pipe returns 0 for O_RDONLY|O_NONBLOCK mode and EAGAIN for O_RDWR|O_NONBLOCK. It there any specs for "read" system call? I have small problem with blocking read in pthreads under 3.X. Since blocking read implemented as non-blocking inside pthread (libc_r to be honest), returning 0 instead of EAGAIN from read confuses libc_r. It expects EAGAIN. BTW such "blocking" read inside thread gives almost 100% CPU utilization :( thanks, emax To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
MD5 Sigs on 3.4-20000124-STABLE
I checked the signatures on the files I downloaded from current.freebsd.org/pub/FreeBSD/snapshots/i386/3.4-2124-STABLE/ and the following fail the MD5 check: < = from CHECKSUM.MD5 listing > = downloaded file. 68c70 < MD5 (bin.cp) = c688b821316686fb8393b52ef9af1d86 --- > MD5 (bin.cp) = 5b448c5cffd07e612873c80bd5ed6b41 93c95 < MD5 (bin.do) = f87680f6cb58bf21af6e18825e7e23a2 --- > MD5 (bin.do) = 3dd11e1748dabf91bd36add0a05b0ea5 75c77 < MD5 (scontrib.cp) = 1d19d8fd622d067a4bd6167e84357ece --- > MD5 (scontrib.cp) = 56d9a710f54b7f1ba0ab10ad0c917b79 I've downloaded several times as a group and individually is their a known problem? Jorge To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
