Re: SIOCADDMULTI doesn't work, proposed fix

Of all the gin joints in all the towns in all the world, Garrett Wollman had to walk into mine and say: > < said: > > > a struct sockaddr_dl will be used. However, the user is supposed to > > pass the address using a struct ifreq, and struct ifreq uses struct > > sockaddr, not struct sockaddr_d

Re: Network/ARP problem? Maybe pn driver?

Stefan Esser writes: > You could have blocked reception of ARP requests / ARP replies in your IPFW > rules on one of the systems involved. Just try again with a completely open FYI- There's no way to block ARP packets with ipfw... it only deals with IP packets. -Archie

Re: a nit, however....

Brian Feldman writes: > > any reason why the kernel "config" program shouldn't > > be changed to dramatically reduce the requirement for > > the silling quoting of option values??? if an option > > needs embedded whitespace, but other than that, > > is there any reason other than historical for >

Re: btokup().. patch to STYLE(9) (fwd)

On Jan 29, 8:34am, Brian Somers wrote: } Subject: Re: btokup().. patch to STYLE(9) (fwd) } } My argument is that this sort of thing gets out of hand. I've seen } things such as } } if (((a == b) || (c == d))) } } where a, b, c & d are just simple variables - there are so many } redundant b

Re: btokup().. patch to STYLE(9) (fwd)

On Jan 29, 9:13am, Poul-Henning Kamp wrote: } Subject: Re: btokup().. patch to STYLE(9) (fwd) } } On the other hand style(9) should still firmly outlaw stuff like: } } /* wait 10 ms */ } if (((error = tsleep((caddr_t)dev, PPBPRI | PCATCH, } "ppbpoll", hz/100)) != EWOULDBLOC

Re: btokup().. patch to STYLE(9) (fwd)

On Jan 29, 12:05pm, Sheldon Hearn wrote: } Subject: Re: btokup().. patch to STYLE(9) (fwd) } The reason I'm interested in this (now tiresome) thread is that I'd much } rather have to read } } /* }* Bail out if the time left to next transaction is less than }* the duration of

Re: Can't boot from 1st disk on 2nd IDE controller

set root_disk_unit=2 > Hello!! > I'm running 4.0-CURRENT cvsupped last Friday. I've tried to move my > installation from a partition on the first disk of the first IDE > controller to a new disk that I've placed as master of the second IDE > controller. Everything looks fine until the system tri

SIOCADDMULTI doesn't work, proposed fix

< said: > a struct sockaddr_dl will be used. However, the user is supposed to > pass the address using a struct ifreq, and struct ifreq uses struct > sockaddr, not struct sockaddr_dl. This is called ``poor man's inheritance''. I believe it is an error for any code to use AF_UNSPEC for any purpos

Re: Even more interesting NFS problems..

< said: > Erm, I haven't tried it between 3.0 and 3.0 boxes because all my test > environments currently involve one of each (4.0 and 3.0), but I can > certainly say that in none of these test environments does amd work at > all. Works just fine on a somewhat older 3.0 (which is still running the

Re: btokup().. patch to STYLE(9) (fwd)

> > > On Fri, 29 Jan 1999 00:55:21 EST, Mikhail Teterin wrote: > > > Everybody's goal is to keep/make code readable (accusations of "trying > > to obfuscate" are silly). You, people, are just not agreeing what > > "readable" means. Hoping to aid in the ending of this thread(s), > > Thank you ve

Re: Persistent files under /usr/obj

>do a >chflags -R noschg /usr/obj >before you rm it Uh no... do the 'rm' first, tolerate the few warnings, _then_ do the chflags and then another 'rm'. It's faster on my stopwatch anyway :) Cheers, Jerry Hicks wghi...@bellsouth.net > >-Scott > >On 31-Jan-99 Michael Graziano wrote: >> I went t

Re: Network/ARP problem? Maybe pn driver?

On Fri, Jan 29, 1999 at 06:28:46PM -0500, Bill Paul wrote: > - Change the if() clause so that it looks like this: > > if (sc->pn_promisc_war /*&& ifp->if_flags & IFF_PROMISC*/) { > > (In other words, comment out the test for the IFF_PROMISC flag.) > > This will enable the workaro

Re: Even more interesting NFS problems..

I've been using amd on bleeding-edge current for the past year or so with no problems - the servers in my case are Solaris 2.5.1 boxes. I remember becoming extremely confused when I configured my first amd map file, since there was no coherent documentation to be found at the time, but I ended up

Re: a nit, however....

actually, i was there when Sam Leffler first wrote "config" and that was never the intention, and that proposed fix would be astoundingly silly -mo To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message

Re: btokup().. patch to STYLE(9) (fwd)

At 12:09 PM 2/1/99 +1100, Gregory Bond wrote: >> I seem to remember there once was a comment in a well-known body of code, which >> went something like: >> "You are not supposed to understand this." > >It was (IIRC) the process switching magic at the heart of fork() in V7 (and >earlier, I assume).

Re: btokup().. patch to STYLE(9) (fwd)

> I seem to remember there once was a comment in a well-known body of code, > which > went something like: > "You are not supposed to understand this." It was (IIRC) the process switching magic at the heart of fork() in V7 (and earlier, I assume). To Unsubscribe: send mail to majord...@freebsd

Re: Persistent files under /usr/obj

On Sun, 31 Jan 1999, Michael Graziano wrote: >I went to remove everything from my /usr/obj directory this morning in >preparation to do a make world, and found that two files >(/usr/obj/usr/src/tmp/usr/lib/libc.so.3 and >/usr/obj/usr/src/tmp/usr/lib/libc_r.so.3) can't be deleted. Am I >missing so

Re: Even more interesting NFS problems..

> Err On all of the machines where I use amd, I don't use -l syslog. > I use -l /tmp/.automsg (or some other filename that lusers aren't likely You're right, that does produce more information. Unfortunatly, not enough to help diagnose the problem. :( I think something more fundamental is br

Re: a nit, however....

On Sun, 31 Jan 1999, Mike O'Dell wrote: > > any reason why the kernel "config" program shouldn't > be changed to dramatically reduce the requirement for > the silling quoting of option values??? if an option > needs embedded whitespace, but other than that, > is there any reason other than histo

a nit, however....

any reason why the kernel "config" program shouldn't be changed to dramatically reduce the requirement for the silling quoting of option values??? if an option needs embedded whitespace, but other than that, is there any reason other than historical for the silliness about nubmers, etc??

Re: vn and 4.0

On Mon, 1 Feb 1999, Kris Kennaway wrote: > On Mon, 1 Feb 1999, Daniel C. Sobral wrote: > > > Is vn safe right now on -current? > > It's broken for me without Matt's patch posted the other day (not yet checked > in). I can send you a copy if you missed it. > > > And does current's msdos fs > > s

Kernel wont compile

Hi, Iv'e CVSupped on Friday 29/1/99 and proceeded to make world seemed to go OK but when I tried to compile the kernel I got this Script started on Sat Jan 30 00:27:14 1999 [2]r...@scratch1/usr/src/sys/ compile/SCRATCH1# make depend cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-p

current.freebsd.org backup and then back down :-(

Connected to usw2.freebsd.org. 220 usw2.freebsd.org FTP server (Version 6.00) ready. Name (current.freebsd.org:mdtancsa): ftp 331 Guest login ok, send your email address as password. Password: 550 Can't set guest privileges. ftp: Login failed. Remote system type is UNIX. Using binary mode

Re: vn and 4.0

On Mon, 1 Feb 1999, Daniel C. Sobral wrote: > Is vn safe right now on -current? It's broken for me without Matt's patch posted the other day (not yet checked in). I can send you a copy if you missed it. > And does current's msdos fs > support fat-32? Don't know, but I think so. Kris - (AS

SIOCADDMULTI doesn't work, proposed fix

After experimenting some more, I've come to the conclusion that trying to manually add a non-IP ethernet multicast address doesn't work properly. The ether_resolvemulti() assumes that addresses will be specified as either AF_LINK or AF_INET; if the family is AF_LINK, it assumes that a struct sockad

Can't boot from 1st disk on 2nd IDE controller

Hello!! I'm running 4.0-CURRENT cvsupped last Friday. I've tried to move my installation from a partition on the first disk of the first IDE controller to a new disk that I've placed as master of the second IDE controller. Everything looks fine until the system tries to mount the root partition an

RE: Persistent files under /usr/obj

On Sun, 31 Jan 1999, Scott A. Barron wrote: > On 31-Jan-99 Michael Graziano wrote: > > I went to remove everything from my /usr/obj directory this morning in > > preparation to do a make world, and found that two files > > (/usr/obj/usr/src/tmp/usr/lib/libc.so.3 and > > /usr/obj/usr/src/tmp/usr/li

RE: Persistent files under /usr/obj

do a chflags -R noschg /usr/obj before you rm it -Scott On 31-Jan-99 Michael Graziano wrote: > I went to remove everything from my /usr/obj directory this morning in > preparation to do a make world, and found that two files > (/usr/obj/usr/src/tmp/usr/lib/libc.so.3 and > /usr/obj/usr/src/tmp/usr

Persistent files under /usr/obj

I went to remove everything from my /usr/obj directory this morning in preparation to do a make world, and found that two files (/usr/obj/usr/src/tmp/usr/lib/libc.so.3 and /usr/obj/usr/src/tmp/usr/lib/libc_r.so.3) can't be deleted. Am I missing something, or are these two files just hanging out fo

Have a problems with SLIP under 4.0-current

Hello! My system is 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sun Jan 31 22:42:09 MSK 1999 Have a following problem: $ ifconfig sl0 % ifconfig sl0 sl0: flags=c013 mtu 296 inet X.Y.Z.116 --> X.Y.Z.115 netmask 0xfff0 broadcast X.Y.Z.115 Does it right? Rgdz, Осокин Сергей aka oZZ, o...@etr

Re: Even more interesting NFS problems..

> I use -l /tmp/.automsg (or some other filename that lusers aren't likely ..snip.. > I've found that am-utils is much more verbose than previous versions of > amd so you may not want to leave it that way permanently ... /var/log/amd.log and add it to /etc/newsyslog.conf. Since this is what I use

Re: btokup().. patch to STYLE(9) (fwd)

Doug Rabson wrote: >On Fri, 29 Jan 1999, Sheldon Hearn wrote: >> >> The reason I'm interested in this (now tiresome) thread is that I'd much >> rather have to read >> >> /* >> * Bail out if the time left to next transaction is less than >> * the duration of the previous transact

Re: c_caddr_t (etc)

[.] > It's probably a good idea to go easy on the new committers for now > though. Oops, I meant ``to go easy on the *introduction of* new committers''. > > - Jordan > > -- > Brian > > Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail t

Re: Reading a text file with BTX

Patrick Hartling wrote: > > } @set kernelname=kernel > } @read -t 5 -p "Enter kernel name [kernel] : " kernelname > } @load $kernelname > } @include /boot/modules.default > } -include /boot/modules.$kernelname > } @autoboot 5 > > That looks great to me. I was thinking that something like the abo

Re: Scsi chatty'ness can be good..

Hi folks, Well, to add a positive vote to this issue I run alot of ccd arrays... When I put one together last week, those messages alerted me to a bad drive One drive in the array immediately went from 64 available opennings down to about 30. None of the other drives exhibitted this

Re: Reading a text file with BTX

Mike Smith wrote: } > Is there a way to view the contents of a text file (specifically, } > /boot/loader.rc) with BTX? Now that there are all these nifty new modules, } > my kernel is a lot smaller and my /boot/loader.rc is a lot longer. The way } > I have my /boot/loader.rc setup is such that

Re: Even more interesting NFS problems..

Of all the gin joints in all the towns in all the world, Jordan K. Hubbard had to walk into mine and say: > > Why is it clearly broken? proto=tcp,vers=3 is what is in 3.0-RELEASE, > > Amd in 3.0 works for many. I won't defend that the new Amd works the > > best with us, but then neither did the

Re: Reading a text file with BTX

I'd like to suggest that nobody depends on the exact syntax below. Using "@" at the beginning of the lines is EVIL, and has to go away. Well, for *this* purpose, at least. Likewise, - at the beginning of the line is also very evil. Very, very evil. I have now, at last, a fully working version of "

vn and 4.0

Is vn safe right now on -current? And does current's msdos fs support fat-32? -- Daniel C. Sobral(8-DCS) d...@newsguy.com Would you mind not shooting at the thermonuclear weapons? To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-curren

Re: more about yield() versus sched_yield()

On Sun, Jan 31, 1999 at 09:34:45PM +1100, John Birrell wrote: > Peter Dufault wrote: > > > I've got a synch_yield() in kern_synch and a call into it from yield() > > > in kern_thread that duplicates the yield() behavior for the non-RTPRIO, > > > non-sched_yield() condition. synch_yield() also KASS

Re: Reading a text file with BTX

> Is there a way to view the contents of a text file (specifically, > /boot/loader.rc) with BTX? Now that there are all these nifty new modules, > my kernel is a lot smaller and my /boot/loader.rc is a lot longer. The way > I have my /boot/loader.rc setup is such that it unloads everythin > autom

Re: Even more interesting NFS problems..

"Jordan K. Hubbard" wrote: > > Why is it clearly broken? proto=tcp,vers=3 is what is in 3.0-RELEASE, > > Amd in 3.0 works for many. I won't defend that the new Amd works the > > best with us, but then neither did the old Amd. > > Erm, I haven't tried it between 3.0 and 3.0 boxes because all my t

Re: more about yield() versus sched_yield()

> >(This also will let people who haven't looked at that code > >complain about the function interface - it doesn't bother me, > >macros could come later.) > > I might complain about style bugs, and typedefs named priority_type, > and magic conversions between priority_type and int. Or you might

Re: more about yield() versus sched_yield()

>> Another difference is that it correctly counts context switches as voluntary. > >Good point. The patched version calls maybe_resched(), and I'm >adding the line at "<<<". This counts context switches twice (once as voluntary here, once as involuntary when switch is done on return from the sysc

Re: Even more interesting NFS problems..

> Why is it clearly broken? proto=tcp,vers=3 is what is in 3.0-RELEASE, > Amd in 3.0 works for many. I won't defend that the new Amd works the > best with us, but then neither did the old Amd. Erm, I haven't tried it between 3.0 and 3.0 boxes because all my test environments currently involve on

More on The Handbook

The section "24.1. The FreeBSD Booting Process" might be misleading... With our new three stage boot loader, people are bound to hit that link thinking it will explain how does boot[012]/loader works, what's a BTX, etc... :-) -- Daniel C. Sobral(8-DCS) d...@newsguy.com

Re: more about yield() versus sched_yield()

> Another difference is that it correctly counts context switches as voluntary. Good point. The patched version calls maybe_resched(), and I'm adding the line at "<<<". (This also will let people who haven't looked at that code complain about the function interface - it doesn't bother me, macros

Re: c_caddr_t (etc)

[.] > To put it in a somewhat larger context, none of the things which have > seen people blow up recently have been all that important, and to get > people freaking out in my mailbox over the -Wall changes or a change > to style(9) is pretty damned silly. This is one aspect to John > Birrell'

Medium priority tasks...

Hey, are you REALLY sure this is a medium priority task? From the handbook: 3.Full LKM based driver support/Configuration Manager. -- Daniel C. Sobral(8-DCS) d...@newsguy.com Would you mind not shooting at the thermonuclear weapons? To Unsubscribe: send mail to

New socket code hits again! (was: Latest VM changes cause panic: page fault)

On Sun, Jan 31, 1999 at 02:27:17PM +0300, Andrey A. Chernov wrote: > Pre-new-VM kernel not cause page fault Sorry for false alarm - it seems that new socket code hits again and not new VM: #4 0xf019cc3e in trap () #5 0xf013aa20 in soclose () #6 0xf01314e2 in soo_close () #7 0xf011c456 in clo

Latest VM changes cause panic: page fault

It happens with plain UFS, I have no NFS. Pre-new-VM kernel not cause page fault -- Andrey A. Chernov a...@null.net MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message

Re: 3.0-STABLE and 4.0-CURRENT snapshots

Roman V. Palaginwrote in list.freebsd-current: > Where I can find snapshot for -stable & -current? I've tried > current.freebsd.org, but 'cd /pub/FreeBSD' says 'Permission denied'. > And there is nothing at > ftp://ftp.freebsd.org/pub/FreeBSD/release/snapshots/i386 You might give ftp7.de.free

Re: more about yield() versus sched_yield()

>While we're discussing yield here's a question. > >The difference between yield() and sched_yield() is that yield unconditionally >yields while sched_yield() won't if you are the highest priority process >and the only process in your run queue. Does anyone know the >reuirements on yield() and wou

Re: Even more interesting NFS problems..

> > Yes, to be consistent with the state of world WRT NFS. Or at least with > > the leader -- Solaris. This has been the default in 3.0-C since the > > am-utils import. > > Yeah, well, amd is a whole other ball of wax. That's clearly broken > in both 3.0-stable and 4.0-current Why is it clear

Re: more about yield() versus sched_yield()

Peter Dufault wrote: > > I've got a synch_yield() in kern_synch and a call into it from yield() > > in kern_thread that duplicates the yield() behavior for the non-RTPRIO, > > non-sched_yield() condition. synch_yield() also KASSERTS > > that p == curproc since nothing else makes sense. > > While

more about yield() versus sched_yield()

> I've got a synch_yield() in kern_synch and a call into it from yield() > in kern_thread that duplicates the yield() behavior for the non-RTPRIO, > non-sched_yield() condition. synch_yield() also KASSERTS > that p == curproc since nothing else makes sense. While we're discussing yield here's a q

Re: Network/ARP problem? Maybe pn driver?

Yust a wild guess: You could have blocked reception of ARP requests / ARP replies in your IPFW rules on one of the systems involved. Just try again with a completely open configuration (a pass all as rule 1 should work). That would explain that other systems can learn the ARP address as soon as

About /usr/mdec/cdboot

I'm using DELL's OptiPlex Gn+. This machine is supported CD-ROM Booting from ATAPI CD-ROM. In 3.0-stable and -cureent, I created CD-R disc with /usr/mdec/cdboot using mkisofs and cdrecord. When CD booting, some error messages is displayed. And I tested other machines supported atapi-cdrom

Re: LINUX clone? sched_yield?

> There's a yield() syscall that is enabled permanently. Is there any > harm in untangling it from the POSIX sched_yield()? :-) I've got a synch_yield() in kern_synch and a call into it from yield() in kern_thread that duplicates the yield() behavior for the non-RTPRIO, non-sched_yield() conditio