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

In message <19990129204521.a73...@znh.org> Zach Heilig writes: : On Fri, Jan 29, 1999 at 11:02:48AM -0700, Warner Losh wrote: : > Yes. I agree with that. : > if (a | b & c % d ^ e) : > should have been written as: : > if (((a | (b & (c % d))) ^ e) != 0) : : I don't know why I'm getting

*1 routines in /sys/kern

We currently have routines like fork1() and killpg1() in /sys/kern/* to implement generic functionality for actions with more than one "front-end". NetBSD has done something similar for signals, so that emulators with non-BSD signal semantics can implement their way of doing things as an emulat

Re: About to commit NTFS driver

> Looks like not. David O'Brien have just showed me points > to fix. May be he will be? Willing to, but I am waiting until I can compile it and test it under 4.0-CURRENT. (esp. since that is where it will have to be added first) -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To U

Re: SysVR4 emulator

Warner Losh wrote: > In message <199901300636.raa20...@atdot.dotat.org> Mark Newton writes: > : It's early days yet, folks -- You'll probably have trouble getting 100% > : functionality out of most things (specifically, poll() on a socket doesn't > : look like it works at the moment, so Netsca

Why doesn't Vinum start automatically?

There have been changes to rc and rc.conf lately to autostart Vinum. But on my system it does not auto load at start and I wind up manually loading the module, reading the config and mounting the volume. Any help if figuring out why this is not working would be appreciated. rc.conf now sets a va

Re: SysVR4 emulator

In message <199901300636.raa20...@atdot.dotat.org> Mark Newton writes: : It's early days yet, folks -- You'll probably have trouble getting 100% : functionality out of most things (specifically, poll() on a socket doesn't : look like it works at the moment, so Netscape doesn't work (among other : t

SysVR4 emulator

I've just committed the FreeBSD svr4 emulator, which has been built by adapting the stirling work of Christos Zoulas from the NetBSD project to FreeBSD. I hope I haven't left anything out or broken the world, but I'm sure I'll hear about it if I have :-) To use it: 1. Add "pseudo-device strea

Re: c_caddr_t

> forum. If Matt wished to make this point, he should have done so in a > less inflamitory manner especially in such a public forum. That's > been a problem lately in this forum, and I cannot express easily in > words how strongly I object to it. Fair enough - maybe everyone involved should just

Re: c_caddr_t

In message <86708.917669...@zippy.cdrom.com> "Jordan K. Hubbard" writes: : While this is true, I think the overall point he made was reasonable : considering how often Bruce has corrected others for "needless : commentary" in the commit logs and I'd be happy to see everyone follow : their own rules

Re: c_caddr_t

> Matt, get over it. bde didn't slam *YOU* in the commit messages. You > were never mentioned personally. Also, taking your complaint to > -current is not proper proceedure for handling grievances. While this is true, I think the overall point he made was reasonable considering how often Bruce

Re: c_caddr_t

It's also something that bde has slammed more than a few other people on when they do such things ["Commit messages are not for this purpose!"] so he of all people ought to know better (stern look at Bruce for getting hypocritical in his old age :). - Jordan > bde, I don't mind you removing

Re: c_caddr_t

In message <199901292317.paa84...@apollo.backplane.com> Matthew Dillon writes: : bde, I don't mind you removing c_caddr_t as long as you also fix the : warnings that it fixed, but it would have been appropriate to notify : me of what you were doing rather then slamming me in the CVS com

Re: make release - Party Time! (but not for the AXP)

> Sidestepping a bit: will there be AXP specific CDROMs in the WC > CDROM distribution? "Probably" - it's just far too early to say. - Jordan 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)

On Fri, Jan 29, 1999 at 11:02:48AM -0700, Warner Losh wrote: > Yes. I agree with that. > if (a | b & c % d ^ e) > should have been written as: > if (((a | (b & (c % d))) ^ e) != 0) I don't know why I'm getting into this, but to prove the point that this expression takes careful thou

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

< said: > Question: how many people still limit their editor windows to 80 > characters? Probably almost anyone who uses the default settings. Many people like to be able to see more than one thing on the desktop at a time. Even with a 1280x1024 display on a good 19-inch monitor, I still can't

4.0-current emacs locks up in startup

4.0-current of a few days ago. rebuilt XFree and a bunch of other stuff build emacs or emacs20 either runs fine in an x-term either freezes when started with its own window it puts up the window paints the grey menu bar freeze emacs20 stack at freeze #0 0x282c4824 in select () #1 0x28203e

Re: Network/ARP problem? Maybe pn driver?

On Fri, Jan 29, 1999 at 06:28:46PM -0500, Bill Paul wrote: > > Hmm. Running tcpdump seems to make the problem go away. The ARP > > replies show up immediately appear in the table. Clue. > > You should have tried that first. I'm sorry. I ran tcpdump on a different host precisely because I didn

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

> Question: how many people still limit their editor windows to 80 > characters? I do :-/ So that I don't write code > 80 columns. > Greg -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe

Re: Network/ARP problem? Maybe pn driver?

> I hope I'm not just being really stupid, but I think there's a problem > somewhere. If it's a configuration error on my part, then I think I'd > better take a vacation, considering what my job is supposed to be. > > Anyway, I have a machine that is exhibiting a weird network problem. > My guess

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

:> Question: how many people still limit their editor windows to 80 :> characters? : :Almost everyone in my group, since alot of development is done on :laptops with small screens, or done remotely. : :Nate I do, because if use anything larger some lines will inevitably go over and I'll ge

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

On Sat, 30 Jan 1999, Greg Lehey wrote: > of intelligibility. Consider one possible expansion > > if (((allocationfail | (IGNOREFAILUREMASK & (incount % BLKSIZE))) ^ failures) != 0) or if (((allocationfail | (IGNOREFAILUREMASK & (incount % B

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

> Question: how many people still limit their editor windows to 80 > characters? Almost everyone in my group, since alot of development is done on laptops with small screens, or done remotely. Nate To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the bod

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

> On Friday, 29 January 1999 at 9:13:39 +0100, Poul-Henning Kamp wrote: > > It would also be nice if somebody whould coerse ident to DTRT. > > I've already mentioned that I have a version of indent with DABT. > Shall I polish it up a bit? You've got my vote. > Greg > -- > See complete headers f

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

On Friday, 29 January 1999 at 11:02:48 -0700, Warner Losh wrote: >> If I were working on this code written by someone else it'd leave my >> editor looking like the top example, that's for sure. I think that >> "How easy is it to edit a piece of code and still have it do what you >> expect" is an i

Re: Network/ARP problem? Maybe pn driver?

Christopher Masto writes: > > Can you run a "tcpdump arp" on the machine that is having the problem, > > as well? This could help to determine if it's a driver problem (e.g. > > if the replies don't show up) or an ARP problem (e.g. if the replies > > do show up but arp doesn't use them). > > Good

indent (was: btokup().. patch to STYLE(9) (fwd))

On Friday, 29 January 1999 at 9:13:39 +0100, Poul-Henning Kamp wrote: > It would also be nice if somebody whould coerse ident to DTRT. I've already mentioned that I have a version of indent with DABT. Shall I polish it up a bit? Greg -- See complete headers for address, home page and phone numbe

Re: Telnet and NIS queries

On Fri, 29 Jan 1999, Maxim Sobolev wrote: > Your "problem" with telnet session is very simple - by default FreeBSD > doesn't allow anybody to login as "root" through insecure connection (see > /etc/ttys). This can be changed by editing /etc/ttys to make Pseudo *doh* Yes, it's /etc/ttys *not* log

Re: Telnet and NIS queries

On Fri, 29 Jan 1999, Tim Preece wrote: > scratch2 login: LOGIN root REFUSED (NOROOT) from scratch1.netlink on TTY > ttyp0 As long as I can remember, root logins have always been refused over network connections. If you want to login as root over a network (bad habbit, but ok for your own, privat

Re: Network/ARP problem? Maybe pn driver?

On Fri, Jan 29, 1999 at 06:02:16PM -0500, Alfred Perlstein wrote: > On Fri, 29 Jan 1999, Christopher Masto wrote: > > I hope I'm not just being really stupid, but I think there's a problem > > somewhere. If it's a configuration error on my part, then I think I'd > > better take a vacation, conside

Re: Network/ARP problem? Maybe pn driver?

Big Clue. Run "tcpdump -p" and see if the problem doesn't go away. ("tcpdump" puts the card in promiscuous mode, "tcpdump -p" does not). Bill To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message

Re: Network/ARP problem? Maybe pn driver?

Of all the gin joints in all the towns in all the world, Christopher Masto had to walk into mine and say: > On Fri, Jan 29, 1999 at 02:52:07PM -0800, Bill Fenner wrote: > > Can you run a "tcpdump arp" on the machine that is having the problem, > > as well? This could help to determine if it's a

c_caddr_t

bde, I don't mind you removing c_caddr_t as long as you also fix the warnings that it fixed, but it would have been appropriate to notify me of what you were doing rather then slamming me in the CVS commit comments. I find that sort of behavior to be highly inappropriate.

Re: Network/ARP problem? Maybe pn driver?

On Fri, Jan 29, 1999 at 02:52:07PM -0800, Bill Fenner wrote: > Can you run a "tcpdump arp" on the machine that is having the problem, > as well? This could help to determine if it's a driver problem (e.g. > if the replies don't show up) or an ARP problem (e.g. if the replies > do show up but arp d

Re: Network/ARP problem? Maybe pn driver?

Can you run a "tcpdump arp" on the machine that is having the problem, as well? This could help to determine if it's a driver problem (e.g. if the replies don't show up) or an ARP problem (e.g. if the replies do show up but arp doesn't use them). Bill To Unsubscribe: send mail to majord...@fre

Network/ARP problem? Maybe pn driver?

I hope I'm not just being really stupid, but I think there's a problem somewhere. If it's a configuration error on my part, then I think I'd better take a vacation, considering what my job is supposed to be. Anyway, I have a machine that is exhibiting a weird network problem. My guess is that ARP

Re: indent(1) and style(9) (was: btokup() macro in sys/malloc.h)

On Thu, Jan 28, 1999 at 08:01:33AM +0100, Luigi Rizzo wrote: > not speaking about vinum, but to me, the indentation of 8 char and > line length of 80 chars are almost mutually exclusive. I've managed to do this for years without much problem. When it is un-avoidable, you can always use a macro. -

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

> -Original Message- > From: Julian Elischer [mailto:jul...@whistle.com] > Sent: 29 January 1999 17:48 > To: Warner Losh > Cc: Andrew Kenneth Milton; curr...@freebsd.org > Subject: Re: btokup().. patch to STYLE(9) (fwd) > > > > > On Fri, 29 Jan 1999, Warner Losh wrote: > > > > if

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

> -Original Message- > From: Doug Rabson [mailto:d...@nlsystems.com] > Sent: 29 January 1999 10:49 > To: Sheldon Hearn > Cc: Greg Lehey; curr...@freebsd.org > Subject: Re: btokup().. patch to STYLE(9) (fwd) > > > On Fri, 29 Jan 1999, Sheldon Hearn wrote: > > On Fri, 29 Jan 1999 20:01:23

Re: About to commit NTFS driver

I should probably backport the getpbuf/relpbuf changes from -4.x to -3.x so the drivers remain reasonably portable. -Matt Matthew Dillon : :I'm quite sure it has alrea

First year of FreeBSD...

[NOTE: this article has nothing technical, but since I assume most of the developers are reading here, I'am posting this here.] Tomorrow, I will "celebrate" my 1-year anniversary with FreeBSD. When I started with fbsd, I wasn't exactly an Unix newbie. In fact, I have been using Linux and

Re: make release - Party Time! (but not for the AXP)

As Jordan K. Hubbard wrote... > > Unfortunately the AXP is still hosed :( > > Hmmm. Let me look at this - I may have failed to adjust one of the > constants for the AXP case. Sidestepping a bit: will there be AXP specific CDROMs in the WC CDROM distribution? Wilko _ ___

Re: Locked at 100% User CPU

> This code looks pretty bad, all right. It looks like it is O(N^2) > in PS_SELECT_WAIT(), especially if descriptors get randomly strewn > amoungst the threads. It also looks like it is regenerating the FDS masks > on each call completely from scratch. It also looks

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

: If I were working on this code written by someone else it'd leave my : editor looking like the top example, that's for sure. I think that : "How easy is it to edit a piece of code and still have it do what you : expect" is an important consideration, because people DO edit things. Agreed. : >

Re: Telnet and NIS queries

Dear Tim, Your "problem" with telnet session is very simple - by default FreeBSD doesn't allow anybody to login as "root" through insecure connection (see /etc/ttys). This can be changed by editing /etc/ttys to make Pseudo terminals to be "secure" (hovewer it compromises the security, you need to

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

On Fri, 29 Jan 1999, Warner Losh wrote: > > if ((a < 0) && (b < 0)) > Personally while I KNOW (after wasting a second thinking about it) that the example below is the same as that above, I ALWAYS code as above. It takes me about 1/5th the time to know what it means. > if (a < 0 &&

Telnet and NIS queries

Hi, I am having a few problems with my v.small network. I have 2 boxes both pc's, one running FreeBSD nearly current (Updated begin Jan) and the other running 3.0 release. Firstly I was able to telnet to 127.0.0.1 and log in as root, however now even this seems to be causing problems the same as

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

On Fri, 29 Jan 1999, Sheldon Hearn wrote: > > Giving folks the go-ahead to use parens as a form of documentation is > misguided and will end in tears. MHO. > Giving people the ability to quickly prove that the code matches the comments when they're upto their behinds in alligators is not going

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

On Fri, 29 Jan 1999, Sheldon Hearn wrote: > > When it comes to code, do you not agree that the trained eye knows which > operators to seek to first in an expression? I can't think of an analogy > in the English language, since one doesn't "seek to" commas, one simply > reads from left to right.

Re: panic: soaccept: !NOFDREF

On Fri, Jan 29, 1999 at 08:22:38AM -0800, Bill Fenner wrote: > Is your machine getting a lot of incoming connections? I'd like to Yes. > try to replicate this. If it's a problem for you you can try > reverting rev 1.52 of /sys/kern/uipc_socket.c . Ok, I'll revert back for a while and wait for y

Re: The future of a.out support?

#define quoting(Satoshi Asami) // That sounds fine. However, there are still people stuck with a.out // libraries out there (netscape comes to mind). Is the 3.1R installer // going to include a.out libraries as an option? Please, please... compat22 would be a historical name. :)

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

In message <199901291530.iaa06...@mt.sri.com> Nate Williams writes: : Bruce should get 50X the vote since he's the only one willing to enforce : the rules. Without Bruce the code would become inconsistant. By : over-ruling we are essentially Essentially what? I appreciate the work that bruce ha

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

In message <199901291121.vaa01...@zeus.theinternet.com.au> Andrew Kenneth Milton writes: : The only arguments I've seen for less 'punctuation' are : : a) "I" don't need them : b) "I" don't like what it looks like with them : c) There might be bugs introduced due to parens. : : Well a and b are

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." Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ h

Re: panic: soaccept: !NOFDREF

In message <19990129103757.a...@nagual.pp.ru>you write: >I saw it several times with very recent -current Is your machine getting a lot of incoming connections? I'd like to try to replicate this. If it's a problem for you you can try reverting rev 1.52 of /sys/kern/uipc_socket.c . Thanks, Bill

Re: About to commit NTFS driver

On Thu, 28 Jan 1999, Mike Smith wrote: > > > > Are there any disagrees with an idea to commit a NTFS > > driver into current: > > > > I can commit/maintain driver mentioned at > > http://www.freebsd.org/projects/ > > > > Driver is readonly, specialy developed for freebsd, > > supports most of

Re: About to commit NTFS driver

David O'Brien wrote: > > > Driver is readonly, specialy developed for freebsd, > > > supports most of NTFS's features. > > > Source is at http://iclub.nsu.ru/~semen/ntfs/ > > > > Sounds like a good idea. Do you have a reviewer? > > I'm looking at it now for 4.0-C. I'm quite sure it has already b

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

On Thu, 28 Jan 1999, Nate Williams wrote: > > > Some people when confronted by people wanting to have extra braces > > > say "change style(9)". > > > > > > Well, here is my change.. > > > > You can count my vote. > > > > I would also add a paragraph like this: > > > > If possible code should

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

> > Unless things have changed a lot, bde counts 50x most people. This > > isn't a democracy. > > It may not be a democracy, but it's also not a monarchy. :-) ... > Bruce only gets "50x the vote" on occasion by generally being the only > one to comment at all. Bruce should get 50X the vote sin

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

> As for noise, there are situations where excess punctuation is just > noise, and there are situations that benefit from more than the bare > minumum of decorations. Anyone doing kernel programming ought to know > the difference. And that is where we disagree. Style is religion, and one man

Re: Locked at 100% User CPU

On Thu, Jan 28, 1999 at 04:10:26PM -0800, Matthew Dillon wrote: > :In libc_r, I don't think the code in uthread_kern.c's > :_thread_kern_select() scales at all. > : > :As the number of network connections (TCP) to my application grows, I > :believe this routine takes longer and longer and my CPU go

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

Sheldon Hearn wrote: > > I didn't have a problem reading the sentence, even though you left out > required commas. The only thing that caused a problem was your use of > split infinitive. ;-) Split infinitive is a urban legend. It has *never* been outlawed in the english language, except for some

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

Sheldon Hearn wrote: > > As far as I see it, there are a lot of people who are saying > > "I want to use parens to improve readability" > > when what they really mean is > > "I want to use parens to obviate the need to learn operator precedence." > > I can't imagine how unnecessary parens are

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

On Fri, 29 Jan 1999, Brian Somers wrote: >[...] > But where do you draw the line in style(9) ? Dunno. Err on the side of redundancy, which cam be mechanically removed if you don't happen to like it. -- Bob Bishop +44 118 977 4017 r...@gid.co.uk fax +44 118 989 4254 To Unsubs

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

> +[ Julian Elischer ]- > | yeah but not a SINGLE person has said to not commit the patch to style(9) > | so I'm going to do it later tonight.. > | (It doesn't make extra braces MANDATORY but it does ALLOW them.) > | > | julian > | (if this doesn't b

Re: PPP (userland) troubles ?

> Would it be possible to add an exponential delay when connecting fails for > either reason? > > I just received my specified phone-bill. It filled 42 pages, with hundreds > of calls with a duration of 17 seconds. (Because my modem needs to be > software-reset; I have mentioned this before). > >

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

-BEGIN PGP SIGNED MESSAGE- On 29-Jan-99 Sheldon Hearn wrote: > When it comes to code, do you not agree that the trained eye knows which > operators to seek to first in an expression? I can't think of an analogy > in the English language, since one doesn't "seek to" commas, one simply > re

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

On Fri, Jan 29, 1999 at 12:05:04PM +0200, Sheldon Hearn wrote: > > > On Fri, 29 Jan 1999 20:01:23 +1030, Greg Lehey wrote: > > > > I can't imagine how unnecessary parens are going to improve > > > "readability" for anyone who knows his/her operator precedence. > > > > What about the others? >

Re: The future of a.out support?

*Yes, a.out execution support will be standard in FreeBSD for at least * several more years. At some point it may become an option, but that's a * long way off. *The only thing people are talking about is support for building the * system binaries in a.out. We're moving to ELF because

Re: "JAIL" code headed for -current.

I'm moving this to FreeBSD-arch, due to taking the discussion quite a bit in that direction. On Wed, Jan 27, 1999 at 11:44:35AM -0800, Sean Eric Fagan wrote: > In article > <29763.917434096.kithrup.freebsd.curr...@critter.freebsd.dk> you > write: > >The biggest impact of this is a new argument to

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

+[ Doug Rabson ]- | 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 th

Re: The future of a.out support?

>It was my understanding that the kernel would continue to support >a.out, and I think that's important. If FreeBSD can support SCO, >Linux, Solaris, BSDI, NetBSD and OpenBSD, it seems important that it >should also contain support for FreeBSD, even old, obsolete versions. > >May I assume that thi

Re: Reading a text file with BTX

Robert Nordier wrote: > > The boot manager menu, for example > > F1 FreeBSD > F2 UNIX > F5 Drive 1 > > Default: F1 Y'know, in my computer that F5 is "Drive 0", and the system will not boot unless I select it first. Selecting it, makes the OSes boot and F5 disappear. -- Da

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

On Fri, 29 Jan 1999, Sheldon Hearn wrote: > > > On Fri, 29 Jan 1999 20:01:23 +1030, Greg Lehey wrote: > > > > I can't imagine how unnecessary parens are going to improve > > > "readability" for anyone who knows his/her operator precedence. > > > > What about the others? > > I'd like to know t

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

On Fri, 29 Jan 1999 20:01:23 +1030, Greg Lehey wrote: > > I can't imagine how unnecessary parens are going to improve > > "readability" for anyone who knows his/her operator precedence. > > What about the others? I'd like to know that people who don't know operator precedence are leaving the k

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

> so far you are the first and only objector.. > which makes you outnumbered by 10 to 1 on email counts.. > I agree completely, saving a few bytes in the source code is not worth the obfuscation that results, writing correct programs is hard enough as it is, without having to suffer from obfuscat

Re: make release - Party Time! (but not for the AXP)

On Fri, 29 Jan 1999, Gary Palmer wrote: > "John W. DeBoskey" wrote in message ID > <199901271433.jaa75...@bb01f39.unx.sas.com>: > >A note of thanks to Jordan and everyone else who's been working > > on the new 4.0 code... We have our first complete processing of > > cd /usr/src && make world &

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

> >> The parans have the same function as commas in most latin alphabet >> based languages: to convey structure. > >I think you've picked the wrong analogy. The rules of the language >dictate certain cases in which commas are required. Extraneous use of >commas decreases readability. Wrong, ther

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

On Friday, 29 January 1999 at 10:27:00 +0200, Sheldon Hearn wrote: > 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

Re: nuts'n'bolts in vfs_bio

:Hello, : :as Matthew said in freebsd-current@ vfs_bio:getblk() still :needs work (B_CACHE/B_DELWRI stuff). : :Running 3.0-stable (Jan 26) it still happens that some NFS :writes seem to remain uncommited on the server. : :Is there a chance to get it into -stable before releasing :in mid February? :

Re: nuts'n'bolts in vfs_bio

:Hello, : :as Matthew said in freebsd-current@ vfs_bio:getblk() still :needs work (B_CACHE/B_DELWRI stuff). : :Running 3.0-stable (Jan 26) it still happens that some NFS :writes seem to remain uncommited on the server. : :Is there a chance to get it into -stable before releasing :in mid February? :

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

On Fri, 29 Jan 1999 09:53:08 +0100, Poul-Henning Kamp wrote: > The parans have the same function as commas in most latin alphabet > based languages: to convey structure. I think you've picked the wrong analogy. The rules of the language dictate certain cases in which commas are required. Extr

Re: cvs commit: src/sys/i386/eisa ahb.c

:Are you volunteering to review Matt's stuff? It's something I'm sure :he'd be more than happy to take you up on, Warner! :-) As usual, the :amount of work which various folks would more than love to have :reviewed outstrips the number of people willing to do such review work :in any serious way.

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

In message <88592.917598...@axl.noc.iafrica.com>, Sheldon Hearn writes: > > >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.

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

> ... Unless we're talking about modifications to existing files where > either style(9) or other systematic styles apply, in which case we > should all try to adapt our changes to that style to avoid babelized > codelayout. Absolutely. I was talking only about my own code, and code which I modi

nuts'n'bolts in vfs_bio

Hello, as Matthew said in freebsd-current@ vfs_bio:getblk() still needs work (B_CACHE/B_DELWRI stuff). Running 3.0-stable (Jan 26) it still happens that some NFS writes seem to remain uncommited on the server. Is there a chance to get it into -stable before releasing in mid February? Thanks,

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

In message <7032.917598...@zippy.cdrom.com>, "Jordan K. Hubbard" writes: >Many of us refuse to follow style(9), will NEVER follow style(9), >and to insist on it for others would be hypocritical at best. Bruce >is more of a microcosm and shouldn't be taken as indicative of general >trends. :) ...

Re: make release - Party Time! (but not for the AXP)

> Unfortunately the AXP is still hosed :( Hmmm. Let me look at this - I may have failed to adjust one of the constants for the AXP case. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message

Re: cvs commit: src/sys/i386/eisa ahb.c

:> Given that there is a good potential to introduce bugs, the age old :> "have another committer review it" would likely allay many of the :> fears that have been expressed. In the past that has been the MO for :> this group. : :Are you volunteering to review Matt's stuff? It's something I'm sur

Re: cvs commit: src/sys/i386/eisa ahb.c

> Given that there is a good potential to introduce bugs, the age old > "have another committer review it" would likely allay many of the > fears that have been expressed. In the past that has been the MO for > this group. Are you volunteering to review Matt's stuff? It's something I'm sure he'd

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

> not-so-loudly agree. Ask yourself: in the last 6 months, how many > things have been shot down and what has survived? From my point > of view, not much progress has been achieved. As far as I can see, > FreeBSD has reached critical mass and for each new developer coming > on board, one drops off

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 very much. This is _

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

> KNF is propogating what I consider to be bad practice, and that annoys me. > I'm happy to say that often they should be dropped, but to FORCE the > dropping of braces etc. with no regard to readbility is too much. I wasn't aware that KNF or style(9) actually "forced" anything so much as "suggest

Re: indent(1) and style(9) (was: btokup() macro in sys/malloc.h)

Matthew Dillon wrote: >:Judicious use of inline functions (and macros) should help move >:code to the left - and may even make it more understandable. > >More then judicious use -- inlines are an incredible advantage. Most >people don't realize that GCC will optimize constant arguments th

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

> We spend so much of our time looking up our own collective asses searching > for the meaning of life that it is no wonder FreeBSD doesn't feel like it > has a clear direction for the future. All people seem to want to do is > stomp on others who try to contribute something. I think the amount of

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

In message <6892.917596...@zippy.cdrom.com>, "Jordan K. Hubbard" writes: >> style(9) is not KNF, and never was intended to be. It's a FreeBSD style >> guide that bears similarity to KNF because that's what it used as a >> starting point. > >I think we can safely presume that Bruce has been overrul

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

> Unless things have changed a lot, bde counts 50x most people. This > isn't a democracy. It may not be a democracy, but it's also not a monarchy. :-) If recent core events have taught us anything at all, it's that nobody in core escapes being accountable to the developers at large and if the co