Re: [CFR] IPv6 support for pserver of cvs

-On [20011104 15:28], Hajimu UMEMOTO ([EMAIL PROTECTED]) wrote: >I wish to add IPv6 support to pserver of cvs. You can find the patch >from: > > http://www.imasy.or.jp/?(J?ume/ipv6/FreeBSD/cvs-ipv6.diff > >This patch is based on the patch by KAME folks. But, the patch is for >1.11 and isn'

Re: gif(4) question

[This question is more appropriate for -net IMHO] -On [20010322 03:00], David E. Cross ([EMAIL PROTECTED]) wrote: >I recently tried (for the first time) to get gif running under FreeBSD >4.3-BETA (cvsup-ed yesterday). I noticed the following: > >gifconfig gif0 inet 10.1.1.1 10.1.2.1 >ifconfig gi

Re: Debuging kernel crashes

[moved to hackers, since it is more appropriate there than in -net] [net bcc:'d] -On [20010320 07:00], Gurpratap Virdi ([EMAIL PROTECTED]) wrote: >I modified the FreeBSD 4.2 kernel and occasionally the kernel crashes. How >can I determine the line of code that caused the crash? I tried addr2line

Re: if_fxp - the real point

-On [20010314 17:38], Dennis ([EMAIL PROTECTED]) wrote: >At 06:35 AM 03/14/2001, Jeroen Ruigrok/Asmodai wrote: > >>That's what Soeren and me did. HighPoint was very forthcoming with >>documentation and as part of that synergy they put the FreeBSD Hardware >>

Re: if_fxp - the real point

-On [20010310 01:00], Lyndon Nerenberg ([EMAIL PROTECTED]) wrote: >Perhaps a first step towards leaning on the vendors for documentation >is to publically declare our support for those vendors who *do* >release documentation under reasonable terms. One way to do this >is to acknowledge those vendo

Re: Cvsup and ports

-On [20010220 02:30], Nigel Taylor ([EMAIL PROTECTED]) wrote: >I recently did a CVSUP on my ports because i wanted to install >enlightenment did a make install and recieved the following error. > >Error: your port uses an old layout. Please update it to match this >bsd.port.mk. If you have updated

Re: soft updates and qmail (RE: qmail IO problems)

-On [20010206 20:25], Andre Oppermann ([EMAIL PROTECTED]) wrote: >> ... provided that qmail calls fsync(2). > >$ cd qmail-ldap/ >$ grep fsync * | wc -l > 21 Of course that says nothing if the fsync()'s are not placed at strategic places. fsync(); fsync(); fsync(); . . . fsync(); And _then_

Re: style(9)

-On [2701 09:25], Wes Peters ([EMAIL PROTECTED]) wrote: > >Or simply get a wider editor. Seriously. Writing code in 80 columns is >an anachronism. Tastes do differ for that. Often the 80 column boundary reminds me not to use functions_which_have_crazy_long_names_with_underscores(), but be

Re: style(9)

-On [2630 19:34], Warner Losh ([EMAIL PROTECTED]) wrote: > >I personally like 4 myself, but let's not get into a stupid tab width >war were people argue about values from 2 to 6 that ends in the >resolution that 8 might not be right, but reformatting everything >would suck too bad to change it

Re: Invalidating PACK!!!

-On [2701 11:18], Mustafa Deeb ([EMAIL PROTECTED]) wrote: >(da2:ahc0:0:4:0): Invalidating pack >(da2:ahc0:0:4:0): Invalidating pack >(da2:ahc0:0:4:0): Invalidating pack >(da2:ahc0:0:4:0): SCB 0x62 - timed out while idle, SEQADDR == 0xb >(da2:ahc0:0:4:0): Queuing a BDR SCB >(da2:ahc0:0:4:0): no

Re: Fwd: socket.h and _POSIX_SOURCE

-On [2425 20:08], Arun Sharma ([EMAIL PROTECTED]) wrote: >Would it be fair to say this is a (POSIX non-compliance) bug in the >header files ? As Bruce Evans was kind enough to reassure me: sys/socket.h is not a POSIX header. 'nuff said I guess. -- Jeroen Ruigrok vd Werven/Asmodaiasmod

Re: Fwd: socket.h and _POSIX_SOURCE

-On [2420 20:02], Arun Sharma ([EMAIL PROTECTED]) wrote: >Comments ? > >$ cat test.c >#include >#include >$ cc -D_POSIX_SOURCE -c test.c >In file included from test.c:2: >/usr/include/sys/socket.h:47: syntax error before `sa_family_t' >/usr/include/sys/socket.h:47: warning: data definition h

Re: Shim Code #error needed

-On [2326 00:00], Warner Losh ([EMAIL PROTECTED]) wrote: > >However, I was thinking that it would be nice if there was something >simple to grep for to see what drivers still needed to be converted. I assume you mean PCI devices, since ISA are detailed in: /src/sys/i386/isa/isa_compat.h --

Re: Is FreeBSD dead? Well, not in theory...

-On [2312 00:00], Joe Abley ([EMAIL PROTECTED]) wrote: >On Sat, Mar 11, 2000 at 01:36:31PM -0500, Dennis wrote: >> Another point is that Open Source is virtually synonomous with "Totally >> undocumented". > >This is sillier. Exactly, and it also slightly pisses me off... Then I guess I wrot

WRT `Is FreeBSD dead?'

Could we place relocate this topic to -chat or -advocacy, since it doesn't seem that correct to be discussed on -hackers. Hackers was meant for quality technical discussion, not discussions about FUD, stupidity of people whom don't read official messages posted prior to stating things, spinning o

Re: yamaha japan relationships anyone?

-On [2221 08:00], Daniel C. Sobral ([EMAIL PROTECTED]) wrote: >No, it was wrt to Playstation, Nintendo, Sega or something like that. >M... I thinking it was probably wrt to SEGA, because there was also >a trademark dispute related to a small string. :-) An american company >tried to get a

Re: yamaha japan relationships anyone?

-On [2220 14:14], Doug Rabson ([EMAIL PROTECTED]) wrote: >On Sun, 20 Feb 2000, Karsten W. Rohrbach wrote: > >> i just messaged the guys from yamaha japan for specs on their pci audio >> chipsets to get some decent documentation to start torturing those ymf744 >> soundcards. no response. i mail

Re: IPFW / IP Filter question

-On [2203 22:43], [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote: >I would have thought you would use the tee option in ipfw for this, but >its not implemented yet according to my man pages, so I was wondering if >there was another way to do this, cause it makes traffic analysis a hell >of a lot

Re: Broken pipe

[This does _not_ belong on hackers, follow-ups set to questions] -On [2206 04:00], Alex ([EMAIL PROTECTED]) wrote: > >When I run my script,sometimes I receive next >message: > >"/usr/sbin/wanrouter: line 5 288 Broken pipe >ls $ROUTER_LOCK_DIR/ 289 Exit 1 | grep -q >wanpipe*" Ehm, the

Re: How to write a device-driver?

-On [2124 00:00], Joachim Jäckel ([EMAIL PROTECTED]) wrote: > >Here´s some information to the card I'd like to support: > >It's a Miro DC10+ Video Grabber Card for Non-Linear Video-Editing. >It uses a Siemens SAA7110, a Zoran 36060+36067 and a ADV chip to en- >and decode the video-informat

Re: Learning the FreeBSD Kernel

-On [2124 19:55], Warner Losh ([EMAIL PROTECTED]) wrote: >In message <[EMAIL PROTECTED]> Jeroen Ruigrok/Asmodai >writes: >: >As long as a device is just inb/outb (I seem to recall newbus have a >: >replacement for these) >: >: bus_space_read_#() / bus_space_wr

Re: Learning the FreeBSD Kernel

-On [2124 08:01], Chuck Robey ([EMAIL PROTECTED]) wrote: > >The problem is, you can't even find what the interfaces are. Reading the >code isn't very useful if you can't even find the right place to start >from. At least the interface points could be listed, so that someone >would know where

Re: Learning the FreeBSD Kernel

-On [2124 10:13], William A. Maniatty ([EMAIL PROTECTED]) wrote: >Is it possible to get a look at the digital Unix guides, that might be a >good starting point. Are they on line (perhaps you have a URL)? http://www.unix.digital.com/faqs/publications/dev_doc/DOCUMENTATION/HTML/Digital_UNIX_B

Re: Learning the FreeBSD Kernel

-On [2124 10:13], Daniel C. Sobral ([EMAIL PROTECTED]) wrote: >As long as a device is just inb/outb (I seem to recall newbus have a >replacement for these) bus_space_read_#() / bus_space_write_#() Where # is 1, 2, 4, or 8. But I don't think we support atomic 8 byte atomic reads and writes.

Re: Learning the FreeBSD Kernel

-On [2124 10:13], Daniel C. Sobral ([EMAIL PROTECTED]) wrote: >Bill Maniatty wrote: >> >> First we want to get the mechanism of driver installation down, then >> try our hands at writing our own driver. I fear that if we roll our own >> driver software we may find that if we have errors (not

Re: Learning the FreeBSD Kernel

-On [2124 08:01], Mike Smith ([EMAIL PROTECTED]) wrote: >> I can't agree with Mike Smith that reading the code is adequate. It >> certainly doesn't apply to newcomers, but it doesn't even apply to >> seasoned hackers like Mike: the BSD style doesn't provide for adequate >> comments, and so wh

Re: Query??

-On [2121 04:02], Saurabh Bhandari ([EMAIL PROTECTED]) wrote: >Dear Sir, Hi, >I am a M.S. student with major as Computer Science. I am doing an >independent study with my professor. I have been told that BSD drivers are >not documented at this point of time. So I would like to document the

Re: disappearing mount points after install

-On [2122 20:00], Marwan Fayed ([EMAIL PROTECTED]) wrote: >There have been two suggestions both very related, both of which I have >already considered. I thought perhaps my BIOS required a DOS partition so >I installed RedHat 6.1 to be sure. Guess what? It worked! My past recollection of slic

Re: Learning the FreeBSD Kernel

-On [2123 11:11], Greg Lehey ([EMAIL PROTECTED]) wrote: >[adding -doc, which is more appropriate for some of the questions] > >On Saturday, 22 January 2000 at 23:06:41 -0500, Bill Maniatty wrote: >> I have a student this semester in my Operating Systems class who would like >> to become a bit

Re: How to write a device-driver?

-On [2109 04:01], Joachim Jdckel ([EMAIL PROTECTED]) wrote: >Hello. Hi, >This is the first time that I try to do a hardware related programming, >(if I ever will start and finish it...) >I'm currently have no knowledge of that kind of programming, but I'd >like to learn! Welcome to the club

Re: Dell PowerEdge 2400 & RCC PCI chipset?

[ Please strip either smp or hackers on the next replies ] -On [2112 00:00], Kenneth D. Merry ([EMAIL PROTECTED]) wrote: > >Anyone have a URL for RCC? I just spend 30 minutes digging. No URL to be find. All tech forums have URL's for all participants, except for RCC (Reliance Computer Corp

Re: wchar support?

-On [19991223 12:00], Nik Clayton ([EMAIL PROTECTED]) wrote: >On Tue, Dec 21, 1999 at 08:30:21PM +0100, Jeroen Ruigrok/Asmodai wrote: >> -On [19991221 18:25], Nik Clayton ([EMAIL PROTECTED]) wrote: >> >I'm trying to compile OpenJade 1.3, a C++ application, for the Doc. Pr

Re: wchar support?

-On [19991221 18:25], Nik Clayton ([EMAIL PROTECTED]) wrote: >I'm trying to compile OpenJade 1.3, a C++ application, for the Doc. Proj. >The build fails with Bah, you beat me to it ;) >LangObj.cxx:15: wchar.h: No such file or directory >LangObj.cxx:16: wctype.h: No such file or directory >gmake[

machine/bus.h

Hi, machine/bus.h claims, in its comment section, that it supports 8 byte read/writes, but never in the whole file does it declare anything remotely akin to bus_space_read_8(). Any reason why not? The outcome of this answer will determine whether I make a patch to correct the comments or add th

Re: soundcard.h

On [19991021 12:00], Sheldon Hearn ([EMAIL PROTECTED]) wrote: >On Wed, 20 Oct 1999 22:19:29 +0200, Jeroen Ruigrok/Asmodai wrote: > >> I have a soundcard.h in both include/sys and include/machine. >> >> Which should have preference over the other, why does one simply not &

soundcard.h

Hi, just been messing with some more include files and I am curious about something. [Note: CURRENT system] I have a soundcard.h in both include/sys and include/machine. Which should have preference over the other, why does one simply not include the other. In other words, why two _exactly_ t

getopt.h

Well I searched the mailinglists and didn't really got further than discovering that unistd.h goes a little way to provide functionality which getopt.h from glibc provides. And seeing that a question of Bill early 1999 never got answered correctly. I cc:'d Bruce on this since I value his stylist

Re: On pthreads [Was: Re: I was accepted to LokiHack '99 at Atlanta Linux Showcase]

On [19991006 04:02], Brian F. Feldman ([EMAIL PROTECTED]) wrote: >What do you all think about >http://www.FreeBSD.org/~green/OpenBSD.libc_r.cancel.patch >? I isolated the set of commits that added cancelling to OpenBSD's >libc_r, and it seems (since they took it from us originally :) it >should be

On pthreads [Was: Re: I was accepted to LokiHack '99 at Atlanta Linux Showcase]

On [19991004 13:04], Daniel Eischen ([EMAIL PROTECTED]) wrote: >> Do you mean pthreads? >> >> If so, we still do not have a pthread_cancel in our libc_r which could >> greatly make things harder to implement. I think OpenBSD has one and we >> might do well to look at that one. > >We could implemen

Re: Developer assessment (was Re: A bike shed ...)

[This is only informative for others willing to participate, after this it should probably no longer hit -hackers since it's getting off topic] On [19991004 14:02], Michael Kennett ([EMAIL PROTECTED]) wrote: >Hi Jeoren, Almost ;) s/eor/ero >> I am already going to do this kind of stuff for the

Re: Developer assessment (was Re: A bike shed ...)

On [19991004 13:42], Michael Kennett ([EMAIL PROTECTED]) wrote: >This 'how-to-help-yourself' document wouldn't have to be long. But it >could contain references to the FreeBSD handbook, the FAQ, and other >stuff that people put together (eg. Gregs pages on vinum, Brian Somers >pages on ppp, + man

Re: I was accepted to LokiHack '99 at Atlanta Linux Showcase

On [19991004 11:42], Stephen Hocking ([EMAIL PROTECTED]) wrote: >I would like to point out that they use the SDL library for many of their >products. We have this in our ports section, but it does have a bug in that we >get a threads crash when doing sound & video simultaneously. The aliens demo

Re: Developer assessment (was Re: A bike shed ...)

[ snip good advice ] Now this is very good advice. I am certainly going to keep Darryl's comments somewhere for easy reference in order to make sure I at least never forget where I came from and how to treat others. I think everybody should heed this advice. -- Jeroen Ruigrok van der Werven/

Re: A bike shed (any colour will do) on greener grass...

On [19991002 20:18], Poul-Henning Kamp ([EMAIL PROTECTED]) wrote: >My last pamphlet was sufficiently well received that I was not >scared away from sending another one, and today I have the time >and inclination to do so. I am glad you took the time to write this out. I only wish more people wou

Re: umount(8) or unmount(2) ?

On [19991003 04:18], Martin Blapp ([EMAIL PROTECTED]) wrote: > >Since about 5 weeks I'm working on sanity checks and bug fixes >for umount(8), mount(8) and mount_xxx(8). Poul Henning told >me to mail to cvs-committers too, cause many clued people read it. And don't bother to read -hackers. >You'

Re: I was accepted to LokiHack '99 at Atlanta Linux Showcase

On [19991002 04:18], Jason Nordwick ([EMAIL PROTECTED]) wrote: >This wouldn't seem -hackers worthy, except I offfered to try to port >it to freebsd-current. I think the things you might need to have [the tools as they called it] might be handy to know. And I think this is more hackers material.

Re: FreeBSD driver for DPT SmartRAID V

On [19990930 08:14], Anthony Rubin ([EMAIL PROTECTED]) wrote: >With the release of the Linux driver for the DPT SmartRAID V cards I imagine >it is just a matter of time before we have a FreeBSD driver. I sent the >following message to DPT. > >>I know this may be a long shot, but here goes. What

Call for projects

Since no-one except Poul-Henning gave a start with this I thought I might try my hand at this. Given FreeBSD's rapid development over the last year a lot of things around the releases have changed. Nik Clayton and his team are doing a terrific job to keep up with the documentation. However, what

Re: submiting source code ?

* Dag-Erling Smorgrav (d...@flood.ping.uio.no) [990914 16:44]: >Jeroen Ruigrok/Asmodai writes: >> The Unix Programming Environment by Rob Pike and Ritchie Kerninghan > >Ritchie Kernighan? Who's Ritchie Kernighan? Thanks for you concern about my apparant inability to remember

Re: submiting source code ?

* Gustavo V G C Rios ([EMAIL PROTECTED]) [990910 04:14]: >I use freebsd about +- 12 months ago. I have never did any thing serious >at kernel level, nor i know anything about kernel desgin. Start with: Modern Operating Systems by Andrew S. Tanenbaum The Design and Implementation of 4.4BSD by Mar

Re: A Challenge

* Nate Williams ([EMAIL PROTECTED]) [990910 07:14]: >In any case, if you install a recent version of FreeBSD, I doubt Mr. NT >is capable of crashing FreeBSD from externally. Just make sure he >doesn't have an account on it, since it's much easier to cause Denial Of >Service attacks if you don't s

Re: A Challenge

* Nate Williams (n...@mt.sri.com) [990910 07:14]: >In any case, if you install a recent version of FreeBSD, I doubt Mr. NT >is capable of crashing FreeBSD from externally. Just make sure he >doesn't have an account on it, since it's much easier to cause Denial Of >Service attacks if you don't spen

Re: submiting source code ?

* Gustavo V G C Rios (gr...@ddsecurity.com.br) [990910 04:14]: >I use freebsd about +- 12 months ago. I have never did any thing serious >at kernel level, nor i know anything about kernel desgin. Start with: Modern Operating Systems by Andrew S. Tanenbaum The Design and Implementation of 4.4BSD b

Re: Ariel RS 2000 T1/EI card

[snip] Please people. When posting messages DON'T reply to other messages if the topic has NOTHING to do with the topic being discussed. This obviously messes up reply-to headers, makes the archives less useful as well and generally screws up threading in MUA's. Thanks. -- Jeroen Ruigrok van

Re: Ariel RS 2000 T1/EI card

[snip] Please people. When posting messages DON'T reply to other messages if the topic has NOTHING to do with the topic being discussed. This obviously messes up reply-to headers, makes the archives less useful as well and generally screws up threading in MUA's. Thanks. -- Jeroen Ruigrok van d

Re: How to go about making a compiler port

* Simon Marlow ([EMAIL PROTECTED]) [990912 13:05]: >I'd like to make a port for our Haskell compiler, GHC (see >http://research.microsoft.com/users/t-simonm/ghc). There are some subtle >problems with this: > > - GHC depends on itself. That is, you need GHC > installed in order to

Re: How to go about making a compiler port

* Simon Marlow (simon...@microsoft.com) [990912 13:05]: >I'd like to make a port for our Haskell compiler, GHC (see >http://research.microsoft.com/users/t-simonm/ghc). There are some subtle >problems with this: > > - GHC depends on itself. That is, you need GHC > installed in order

Re: CS Project

* Daniel O'Connor (docon...@gsoft.com.au) [990909 07:15]: >On 09-Sep-99 Gustavo V G C Rios wrote: >> > I would not be able to see any other proccess which i am not the >> > owner, top would indicated, only 8 proccess, for this current scenario. >> > >> > Linux already have such a facility! > >Hack

Re: CS Project

* Daniel O'Connor ([EMAIL PROTECTED]) [990909 07:15]: >On 09-Sep-99 Gustavo V G C Rios wrote: >> > I would not be able to see any other proccess which i am not the >> > owner, top would indicated, only 8 proccess, for this current scenario. >> > >> > Linux already have such a facility! > >Hack ps

Re: CFD: "bogomips" CPU performance metric

* Satoshi - Ports Wraith - Asami (as...@freebsd.org) [990903 12:14]: > * From: Jonathan Lemon > > * hw.clockrate: 132 > > * Doing this for Pentium and better systems should be trivial. Doing > * it for 486 and lower would just add a timing loop. Doing it for SMP > * would be harde

Re: CFD: "bogomips" CPU performance metric

* Satoshi - Ports Wraith - Asami ([EMAIL PROTECTED]) [990903 12:14]: > * From: Jonathan Lemon <[EMAIL PROTECTED]> > > * hw.clockrate: 132 > > * Doing this for Pentium and better systems should be trivial. Doing > * it for 486 and lower would just add a timing loop. Doing it for SM

Re: Propose mdoc fix regarding ERRORS section

* Mike Pritchard (m...@mpp.pro-ns.net) [990828 11:44]: >>Category: docs >>Synopsis: src/lib/libc/sys/*.2 misc patch pack >- first column in most ERROR lists is too narrow. Normalize their width. > >Right now we have a problem with our on-line man pages. Most were >written when the leng

Re: Propose mdoc fix regarding ERRORS section

* Mike Pritchard ([EMAIL PROTECTED]) [990828 11:44]: >>Category: docs >>Synopsis: src/lib/libc/sys/*.2 misc patch pack >- first column in most ERROR lists is too narrow. Normalize their width. > >Right now we have a problem with our on-line man pages. Most were >written when the lengt

Re: What's new in Linux 2.4

* Peter Jeremy (jere...@gsmx07.alcatel.com.au) [990804 01:13]: > Jordan recently mentioned "Wonderful World of Linux 2.4 (Second > Edition)" . > > This article makes the statement "Linux is still the only operating > system completely compatible wi

Re: What's new in Linux 2.4

* Peter Jeremy ([EMAIL PROTECTED]) [990804 01:13]: > Jordan recently mentioned "Wonderful World of Linux 2.4 (Second > Edition)" . > > This article makes the statement "Linux is still the only operating > system completely compatible with the IPv4

Re: no elf(5) man page (docs/7914)

* Wes Peters (w...@softweyr.com) [990803 10:13]: > Jeroen Ruigrok/Asmodai wrote: > > * Andy Doran (a...@netbsd.org) [990802 00:53]: > > > Wes Peters writes: > > > > NetBSD doesn't have one as of 1.4, so they may be interested in yours. > > > > ;^) &

Re: no elf(5) man page (docs/7914)

* Wes Peters ([EMAIL PROTECTED]) [990803 10:13]: > Jeroen Ruigrok/Asmodai wrote: > > * Andy Doran ([EMAIL PROTECTED]) [990802 00:53]: > > > Wes Peters writes: > > > > NetBSD doesn't have one as of 1.4, so they may be interested in yours. ;^) > > > >

Re: no elf(5) man page (docs/7914)

* Andy Doran (a...@netbsd.org) [990802 00:53]: > Wes Peters writes: > > > NetBSD doesn't have one as of 1.4, so they may be interested in yours. ;^) > > It'd be cool if Asmodai could bounce this around one of the NetBSD lists > once it's near completion. tech-toolchain@ or tech-userlevel@ would b

Re: no elf(5) man page (docs/7914)

* Andy Doran ([EMAIL PROTECTED]) [990802 00:53]: > Wes Peters writes: > > > NetBSD doesn't have one as of 1.4, so they may be interested in yours. ;^) > > It'd be cool if Asmodai could bounce this around one of the NetBSD lists > once it's near completion. tech-toolchain@ or tech-userlevel@ woul

Re: No elf(5) man page (docs/7914)

* Wes Peters (w...@softweyr.com) [990801 07:12]: > Jeroen Ruigrok/Asmodai wrote: > > > > * Nik Clayton (n...@nothing-going-on.demon.co.uk) [990730 23:37]: > > > > > > We have an a.out(5), but no elf(5) (as pointed out in docs/7914). > > > > > >

Re: No elf(5) man page (docs/7914)

* Wes Peters ([EMAIL PROTECTED]) [990801 07:12]: > Jeroen Ruigrok/Asmodai wrote: > > > > * Nik Clayton ([EMAIL PROTECTED]) [990730 23:37]: > > > > > > We have an a.out(5), but no elf(5) (as pointed out in docs/7914). > > > > > > Does anyone feel

Re: No elf(5) man page (docs/7914)

* Sheldon Hearn (sheld...@uunet.co.za) [990801 00:35]: > > > On Fri, 30 Jul 1999 23:46:26 +0200, Jeroen Ruigrok/Asmodai wrote: > > > If no-one objects I'll submit a manpage per a.out(5) style tomorrow > > for review untill it's ready for inclusion. > > A

Re: Is the _Device Driver Writers Guide_ still apropos?

* Nik Clayton (n...@freebsd.org) [990801 00:35]: > How does the attached patch grab you? I think it perfect... Now to find the time to wrote the sucker ;) -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project

Re: Is the _Device Driver Writers Guide_ still apropos?

* Nik Clayton ([EMAIL PROTECTED]) [990801 00:35]: > How does the attached patch grab you? I think it perfect... Now to find the time to wrote the sucker ;) -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project

Re: No elf(5) man page (docs/7914)

* Sheldon Hearn ([EMAIL PROTECTED]) [990801 00:35]: > > > On Fri, 30 Jul 1999 23:46:26 +0200, Jeroen Ruigrok/Asmodai wrote: > > > If no-one objects I'll submit a manpage per a.out(5) style tomorrow > > for review untill it's ready for inclusion. > > Any

Re: Is the _Device Driver Writers Guide_ still apropos?

* Nik Clayton (n...@nothing-going-on.demon.co.uk) [990730 23:37]: > -hackers, > > Is the FreeBSD Device Driver Writers Guide at > > http://www.freebsd.org/tutorials/ddwg/ddwg.html > > still correct? I know there have been changes to this area of the tree > over the past 6 months or so, but

Re: No elf(5) man page (docs/7914)

* Nik Clayton (n...@nothing-going-on.demon.co.uk) [990730 23:37]: > Hi folks, > > We have an a.out(5), but no elf(5) (as pointed out in docs/7914). > > Does anyone feel up to writing one? Saw it before, noticed it, placed on my to-do list. If no-one objects I'll submit a manpage per a.out(5) sty

Re: Is the _Device Driver Writers Guide_ still apropos?

* Nik Clayton ([EMAIL PROTECTED]) [990730 23:37]: > -hackers, > > Is the FreeBSD Device Driver Writers Guide at > > http://www.freebsd.org/tutorials/ddwg/ddwg.html > > still correct? I know there have been changes to this area of the tree > over the past 6 months or so, but I don't know ho

Re: No elf(5) man page (docs/7914)

* Nik Clayton ([EMAIL PROTECTED]) [990730 23:37]: > Hi folks, > > We have an a.out(5), but no elf(5) (as pointed out in docs/7914). > > Does anyone feel up to writing one? Saw it before, noticed it, placed on my to-do list. If no-one objects I'll submit a manpage per a.out(5) style tomorrow for

Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.h

* David Malone (dwmal...@maths.tcd.ie) [990723 18:41]: > if ((bi->bi_socktype == sep->se_socktype && > strcmp(bi->bi_service, sep->se_service) == 0) || > matchservent(bi->bi_service, sep->se_service, >

Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.h

* David Malone ([EMAIL PROTECTED]) [990723 18:41]: > if ((bi->bi_socktype == sep->se_socktype && > strcmp(bi->bi_service, sep->se_service) == 0) || > matchservent(bi->bi_service, sep->se_service, >

Re: Will FreeBSD ever see native IPv6 ??

* ito...@iijlab.net (ito...@iijlab.net) [990722 16:17]: > > >> Are you just teasing or are you serious? > >Well, according to what was discussed earlier he is serious. But from > >prolonged exposure to the kame lists I (think I) know that the FreeBSD ipv6 > >stuff is only available for 3.x and bel

Re: Will FreeBSD ever see native IPv6 ??

* [EMAIL PROTECTED] ([EMAIL PROTECTED]) [990722 16:17]: > > >> Are you just teasing or are you serious? > >Well, according to what was discussed earlier he is serious. But from > >prolonged exposure to the kame lists I (think I) know that the FreeBSD ipv6 > >stuff is only available for 3.x and be

Re: Will FreeBSD ever see native IPv6 ??

* John Hay (j...@mikom.csir.co.za) [990722 11:55]: > Are you just teasing or are you serious? Well, according to what was discussed earlier he is serious. But from prolonged exposure to the kame lists I (think I) know that the FreeBSD ipv6 stuff is only available for 3.x and below. > I searched t

Re: Will FreeBSD ever see native IPv6 ??

* John Hay ([EMAIL PROTECTED]) [990722 11:55]: > Are you just teasing or are you serious? Well, according to what was discussed earlier he is serious. But from prolonged exposure to the kame lists I (think I) know that the FreeBSD ipv6 stuff is only available for 3.x and below. > I searched thro

Re: building thread-safe Xlibs

* Francis Jordan ([EMAIL PROTECTED]) [990626 06:03]: > xc/include/Xos_r.h > > which contains definitions of same (basically, pwd.h wrappers) for various > platforms, but not FreeBSD (I guess at the time FreeBSD didn't have threads). > Unfortunately, the wrappers for other platforms are no

Re: building thread-safe Xlibs

* Francis Jordan (fran...@netscape.net) [990626 06:03]: > xc/include/Xos_r.h > > which contains definitions of same (basically, pwd.h wrappers) for various > platforms, but not FreeBSD (I guess at the time FreeBSD didn't have threads). > Unfortunately, the wrappers for other platforms are n

Re: All this and documentation too? (was: cvs commit: src/sys/isa sio.c)

* Warner Losh (i...@harmony.village.org) [990623 07:43]: > daemon.ninth-circle.org> Jeroen Ruigrok/Asmodai writes: > : Granted, we can never think of reaching a commercial level on documentating > : the internals/code which all the committers provide. > > I think that the docu

Re: All this and documentation too? (was: cvs commit: src/sys/isa sio.c)

* Warner Losh (i...@harmony.village.org) [990623 07:43]: > @daemon.ninth-circle.org> Jeroen Ruigrok/Asmodai writes: > : No documentation is worse than just a sparse manpage. > > ls /usr/share/man/man9 | egrep Oh, I wasn't implying that the newbus guys didn't docume

Re: All this and documentation too? (was: cvs commit: src/sys/isa sio.c)

* Mike Smith (m...@smith.net.au) [990622 17:38]: > > And they might, too. phk has frequently expressed a desire to either > > write documentation on existing systems, or at least help others do > > so. > > No offence meant, but we can see how much of this has actually > materialised. Hence I st

Re: All this and documentation too? (was: cvs commit: src/sys/isa sio.c)

* Mark Newton (new...@internode.com.au) [990622 17:38]: > Hellmuth Michaelis wrote: > > > > And as to the author: Writing docu while you are implementing something > > > might work in a commercial environment where you want to be able to > > > market something before it's sell-by date, but for

Re: All this and documentation too? (was: cvs commit: src/sys/isa sio.c)

* Doug Rabson (d...@nlsystems.com) [990622 20:48]: > On Tue, 22 Jun 1999, Hellmuth Michaelis wrote: > > > >From the keyboard of Nick Hibma: > > > > > And as to the author: Writing docu while you are implementing something > > > might work in a commercial environment where you want to be able to >

Re: libss

* David O'Brien (obr...@nuxi.com) [990621 10:38]: > Does anybody know what /usr/src/lib/libss/ is? There isn't a manpage for > it, and viewing the source I still can't figure out what it is other than > it came from MIT (Athena). Apparantly David it came from the SIPB at MIT and more specifically

A question about errors.

Hi, I am updating the description of intro(3) and have stumbled upon some challenges: #define EAUTH 80 /* Authentication error */ #define ENEEDAUTH 81 /* Need authenticator */ #define EOVERFLOW 84 /* Value too large to be stored in data

freebsd-hackers@freebsd.org

On 24-May-99 Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > I'm hunting around for a list of entry points in both Linux & FreeBSD's > libc. I want to find out what linux libc entry points are not found > within the BSD libc, and what entry points that are common have different > arg

RE: security: what does OpenBSD have, that FreeBSD doesn't have.

On 23-May-99 sth...@nethelp.no wrote: >> The OpenBSD team does a lot wrt auditing of the complete sourcetree, but >> then the question is: is this valid concern or is this pure paranoia. >> OpenBSD does a lot of valid changes but borders (and sometimes crosses >> that border) on paranoia, wrt code.

RE: IPv6 and -current?

On 23-May-99 Alex Zepeda wrote: > Out of a perhaps morbid curiosity, I'm somewhat interested in setting up > an IPv6 stack on my computer. From what I can tell there are two well > supported stacks. Kame and Inria, and both support 2.2.8, Kame also > supports 3.x. Has anyone tried to port either

RE: security: what does OpenBSD have, that FreeBSD doesn't have.

Hi Andreas =) On 23-May-99 Andreas Klemm wrote: > Am currently discussing FreeBSD vs. OpenBSD in private e-mail. > > What make OpenBSD so "secure" ? Or can this kind of security be > reproduced with FreeBSD ports ? I think of tools like: Ye missed one of the most important things: auditing of th

RE: Logging "promiscuous mode disabled"

On 22-May-99 Sheldon Hearn wrote: > It doesn't seem to me like it'd break anything, and I'd like to know > for sure when it's turned off -- it'd mean I don't have to count up the > number of "promiscous mode enabled" messages and make sure that that > number matches the number of applications I've

FW: Question on rename()

Could you guys please give yer own opinions on that? I will compile some of the better arguments and resend them to the Posix revision list... -FW: <990518120639.zm1...@tamarix.rdg.opengroup.org>- Date: Tue, 18 May 1999 13:06:40 +0100 From: Andrew Josey To: austin-gr...@opengroup.org Sub

  1   2   >