I had blocked incoming TCP connections coming into my network using
IPFW, and I noticed that my brother was able to establish a Napster
connection, even though I had blocked it earlier.
I thought, no worries, I'll just block it at the port level.
I read a couple of articles, and noted that conne
> > I think that we can do a lot with cvsupd. I've used cvsupd to grab
> > binaries on an experimental basis and it seems to work great. I've
>
> Hmmm. Does cvsupd also move a target out of the way if it already
> exists and it's in the process of replacing it? What if the target is
> chflag'
[ Culled the list way down, and moved it to -hackers ]
> We could also look into providing an "update" command or something
> which would pull either sources or binaries over from a snapshot box
> and make the process of getting up to the branch-head a lot easier.
> It's long been on my wishlist
> [shared libgcc?]
> > If I remember right (and my memory is fuzzy for stuff that far bak)
> > there were a couple of issues.
> >
> > 1) Speed. Shared libraries are slower than static libraries (PIC
> >et. al), and the stuff in libgcc tends to be performance centric.
>
> True. But if we ju
> > At one point libgcc was shared (FreeBSD 1.*), and it caused way more
> > problems that it solved.
>
> Do you remember any details? I analyzed it pretty thoroughly (I
> thought) more than a year ago, and decided the shared library was the
> best solution.
If I remember right (and my memory i
> > We are trying to create a dynamic library of extensions to PHP 4.02.
> > This library implements a C++ class and has a C interface using the "Extern C"
> > declaration.
> > This library is linked with libstdc++.so.3 .
> >
> > If the library is called in a C program => no trouble.
> > If the l
> > > I don't know about the "bsd" or whatever way. If you're doing real
> > > parallel programming and want real performance, you'll use a test-and-set
> > > like function that uses the low-level machine instructions for same.
> >
> > That is exacly what I'm looking for! I found it to be overkil
[ CVS has screwy behavior ]
> CVS has a heuristic that does the wrong thing for this particular
> file.
[ Code and discussion deleted ]
> I hope current
> versions of CVS force the dates to be the same on an import. I
> haven't checked to see whether that's the case or not.
Suggestions like
> > You normally wouldn't mix kqueue and threads; you'd use kqueue to
> > *implement* threads. :-)
> >
> > AFAIK kqueue hasn't been made threadsafe, you'll have to bug
> > [EMAIL PROTECTED] about it. Patches gladly accepted :)
>
> I may be just being stupid but I don't understand that last sente
> > PosixThreads are userland threads - if one thread blocks on i/o the
> > whole process is blocked. Which makes PosixThreads rather useless.
>
>That is incorrect. FreeBSD's userland pthread implementation
> does not block the whole process on I/O. POSIX does not specify
> this behavior ei
> > Mike Smith wrote:
> > > gzipped binaries are actually a terrible idea; they actually *waste*
> > > space in most cases.
> >
> > Suprising, They saved space for a 200M disc in a 486 laptop with 3.[2,3,or4],
>
> No, that's the one case where they help. But people aren't trying to
> squeeze
> Besides, have you even established that dynamically linked programs
> load too slowly? I've certainly never heard any complaints along
> those lines. Furthermore I would bet that the bulk of the dynamic
> linking time comes from opening the shared libraries and mmapping
> them, and there's not
> > > Not to mention "how much memory do you really gain by unloading modules"?
> > > Considering the price of RAM these days (although not as low as
> > > it was, but I won't be spending $650 US for 16M any time soon
> > > again), the few K that unloading a bunch of modules saves won't
> > > E
> > > Just learning about this: I can see the advantages but does
> > anything use it?
> >
> > Sure, TCP uses it.
> >
> So... thinking about what this means for firewalls and natd. If we block all
> incoming ICMP's across the firewall
The moral of the story is don't block *ALL* incoming ICMP's
> I personally consider leaving the kernel module loadable intact after
> boot to be a huge, huge security hole. Loadable modules... fine, but
> once the machine goes multi-user I want to up the securelevel and
> that disables any further kld operations.
This is great for your mu
> > Because the a large percentage (majority?) of cell phones are used in
> > locations where GPS can't be used effectively (think any big city inside
> > of a car), Qualcomm is not adding GPS chipsets into their phones.
> > According to my friend, the solutions they have designed work for both
>
> All this discussion of the wonders of GSM is wonderful, but doesn't apply
> to the USA where this mandate is happening.
You mean the mandate that GPS must be part of the phone? As I said, my
friend at Qualcomm stated that GPS wasn't a requirement, but the ability
to know the location of the ph
> > > Ask him if they can still do it at 35km out (the outer limit for a normal
> > > GSM cell). That'd really spook me. 8)
> >
> > He wasn't interested in talking about it when I started asking about
> > single cell towers, so I never pressed him on the issue. Maybe he was
> > afraid that the
> > > With one tower, you're down to describing an arc along which
> > > the phone is probably located; still pretty good when it comes to finding
> > > someone.
> >
> > He seemed to imply that they could get it within 25m, even with one
> > phone. Like I said, I don't understand how, but I di
> > Plus, they can get a fix on the phone in 300ms (good to about 25m),
> > which is far faster than a GPS unit can do it. Basically, the phone is
> > 'locked on' as soon as you turn it on and it finds a cell tower. And,
> > apparently they've figured out a way to get a coarse fix on it even
> >
> > >: With 12-channel chipsets becoming common, new devices are getting quite
> > >: good at this.
> > >
> > >Yes. Most of the data I have is for 6 channel models.
> >
> > 12-chanel chipsets are overkill if you don't live more or les exactly
> > on the equator or one of the poles. Here where I
> >I disagree. I routineles pick up 10-11 satellites, and I'm about
> >half-way between the pole and the equator. Heck, I just looked, and
> >I've got 8 locked on right now.
>
> Right, 8 is the norm. When you have 10 or 11 a couple or four of them
> are so low on the horizon that they hardly
> >: With 12-channel chipsets becoming common, new devices are getting quite
> >: good at this.
> >
> >Yes. Most of the data I have is for 6 channel models.
>
> 12-chanel chipsets are overkill if you don't live more or les exactly
> on the equator or one of the poles.
I disagree. I routineles
> : That's very different from what the GPS experts at SRI tell me. They
> : start to average things out in a matter of hours, and within a week can
> : have it almost gone. However, they're also using multiple satellites,
> : which allows them to more quickly find the center.
>
> The experts h
> :SA *can* be averaged out, it has an average value of zero. But it
> :takes several days or even weeks to get into the centimeter range,
> :depending on the satelite coverage where you are.
> :
> :--
> :Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
> :[EMAIL PROTECTED] | TCP/IP s
> > This is what "Differential GPS" provides: a standard time source that
> > can be used to remove the SA meanderings from the GPS fix.
>
> If I'm understanding this correctly (with very little actual research into
> it) is that a DGPS station essentially transmits the difference between
> what
> > satellites sitting thousands of miles away in the sky. It's even more
> > impressive to see the government do something right for a change!
>
> It's much more idiotic that the government prevented it before.
>
> That just means that military use is even better already, i.e. I just
>
> Have anyone successfully configured this card on FreeBSD? I think it
> is an on board sound chip in my Dell desktop.
FWIW, the board I have in my wife's box is *very* unstable in Win98, so
we ended up sticking in a SoundBlaster-PCI board in the box and we've
not had a problem since. I can't im
> In message <[EMAIL PROTECTED]> FreeBSD MAIL writes:
> : current /root 78% pccardd -f /etc/pccard.conf.sample
> : current /root 79% Mar 27 01:27:20 current pccardd[215]: No card in database for
>""("")
> : Mar 27 01:27:20 current pccardd[215]: No card in database for ""("")
>
> This tells me t
> > I found it. The code itself is broken. I missed the lack of parens.
> >
> > if (m->m_len < sizeof(struct arphdr) &&
> > (m = m_pullup(m, sizeof(struct arphdr)) == NULL)) {
> > log(LOG_ERR, "arp: runt packet -- m_pullup failed."
> > Never mind, I missed the paren. However, I would have written the fix
> > as follow so I wouldn't have missed the fix. :)
> >
> > To each his own. :)
>
> so, with this fix, do you think i can consider the box stable enough for
> production?
I'll let Matt answer it, but based on the back-t
> I found it. The code itself is broken. I missed the lack of parens.
>
> if (m->m_len < sizeof(struct arphdr) &&
> (m = m_pullup(m, sizeof(struct arphdr)) == NULL)) {
> log(LOG_ERR, "arp: runt packet -- m_pullup failed.");
>
> > : perhaps we need some mutex mechanism?
> >
> > Yes. Right now the mutex mechanism that we have is blocking of
> > interrupts when the bit is set in the cpl. I guess I'm a little too
> > close to the mechanism and need to step back.
> >
> > You are right that I'm asking for a call that is
> >I know the WaveLAN stuff is crap
>
> Actually, I've had terrific luck with WaveLAN IEEE stuff on laptops
> for the last year or so. I'm not sure what's so bad about it?...
Agreed. WaveLAN hardware is good stuff. We deployed 200+ users in a
network, and aside from the normal problems associ
> >That's also why I am wasting my time slowly documenting the FreeBSD
> >internals in my spare time.
>
> "slowly" is the key word here. Real products are documented before they are
> in commercial use.
Really? That's very different from my experience as a commercial
software developer.
And, i
> My laptop running 3.4-RELEASE decided it doesn't want to boot.
> It was uncleanly shut down via the power switch by someone
> who thought they were shutting down a different machine.
>
> Now when it boots, running fsck gives this result:
>
> > chip0: rev 0x01 on pci0.0.0
> > chip1: rev 0x02
> > > This has the side-effect(?) that all sources checked out from the 'old'
> > > repository location have references to /local/CVSfoo whereas cvs update
> > > obviously wants to have the references to /local2/CVSfoo.
> > The simplest way is to replace content of CVS/Root files. They
> > con
> [3] The ANSI C standard, at least, contains the requirement that each
> individual system include file specified by that standard should
> be usable all by itself, without the programmer being required to
> explicitly include any OTHER system include files, prior to the one
> he/
I seem to remember someone else asking about this a couple weeks back.
Does anyone know a good place to go to buy a cheap server system? This
is a sit-in-the-corner box that is a compute-processor and a very
lightly loaded WWW server, similar to what freefall does.
I'd like to spend around $500
A co-worker is looking into buying a printer, and was wondering which
kind would be better, USB and/or parallel. (There are also some that do
both).
Parallel printers tend to load down the system when busy, but serial
devices tend to load them down even more, although USB is a whole
different an
> >Using a thread per connection has always been a bogus way of programming,
> >it's easy, but it doesn't work very well.
>
> OK, even if nobody else does, I'll bite.
Even something as lightweight as a thread is still too heavy for large
systems.
Nate
To Unsubscribe: send mail to [EMAIL PRO
> Dec 2 11:08:56 bifrost /kernel: sio0: 208 more tty-level buffer overflows (total
>3356)
>
> is appearing on our ppp machine. What are tty-level buffer overflows?
> How can I fix this? What resource is running out?
Is it safe to assume that this isn't happening on a laptop? At least
with t
> yep i have an 600E 350Mhz, 128m or RAM. The same thing happens as it hits
> 'Probing devices' The machine just hangs and becomes totally
> un-responsive.
Go back and read the mobile mailing lists for your 600E fixes. It's
discussed greatly there, and is in no way related to the 750 problems.
Is there a way to look at a compiled file to see if it was compiled as
PIC? I've got some .o files that I don't have source code to, but
before I throw them into a shlib, I need to know if they are legal to
put into one?
Thanks!
Nate
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsub
What happens when this is done? Can it ever work?
How about the reverse, where you link in PIC compiled libraries into
static (.a) libraries? Does this work?
Assuming it works (in either case) are there any performance
hits/advantages to either?
My impression from past discussions is that you
> > Could things be done in such a way that like QNX, it can
> > kill and restart a misbehaving driver? What other cool things can be
> > done?
>
> QNX doesn't do that.
Actually, in many cases it does. There are numerous advantages in a
well-designed/optimized micro-kernel that FreeBSD will n
> Does anyone know what "Bus Error" means from Netscape?
It means that the program has a bug in it that caused it to write/read
from memory that it invalid.
This can happen is you try to read from free'd memory, or write to NULL
pointers, etc.
It can also happen if a program assumes a routi
> > You bet! And we haven't even gotten to the topic of the interactive
> > package selection menu yet! :-)
>
> Let alone the Java-based GUI.
In all seriousness, given the stability of the JDK on FreeBSD *plus* the
ability to ship a FreeBSD with the JRE legally (although we don't ship
anything
> > > Not only that but perhaps reserving an amount of backing store for
> > > root may be a good idea, artificially limit the resources to several
> > > pages to enable root to actually do something in such a situation.
> >
> > Stick to the topic at hand. That's another topic again, and the top
> > Maybe, and then again, maybe not. A program is requesting memory, so
> > putting other processes to sleep *keeps* them from freeing up memory.
>
> The process that is trying to use memory is put to sleep.
Then this 'rogue' process is never allowed to free up any of it's
resources, hence the
> > > > What kind of resources are there that both cause loss of swap AND are
> > > > freed up by sleeping a process?
> > >
> > > four things i can think of:
> > >
> > > 1) Along with 'SIGDANGER' it allows the system to fix itself.
> >
> > That's another issue. Don't mix sleeping processes wit
> > What kind of resources are there that both cause loss of swap AND are
> > freed up by sleeping a process?
>
> four things i can think of:
>
> 1) Along with 'SIGDANGER' it allows the system to fix itself.
That's another issue. Don't mix sleeping processes with SIGDANGER, they
are independan
> > I know that in some other Bsd flavours you can use the sysctl functions =
> > which is part
> > of the ifnet struct. In FreeBsd I didn't find anything similiar to it.
>
> Sysctl functions aren't "part of the ifnet struct". You can define
> sysctls for your driver, if you wish, but that's the
> > I know that in some other Bsd flavours you can use the sysctl functions =
> > which is part
> > of the ifnet struct. In FreeBsd I didn't find anything similiar to it.
>
> Sysctl functions aren't "part of the ifnet struct". You can define
> sysctls for your driver, if you wish, but that's th
> The box is just going to be running NATD and IPFW, maybe DHCLIENT.
>
> Mr. NT is been told he can try and break-in, crash what ever this box
> from the internet side.
>
> I am asking for links, pointer to make sure this is configured as
> secure/solid as possible. I will be installing 3.3-STAB
> The box is just going to be running NATD and IPFW, maybe DHCLIENT.
>
> Mr. NT is been told he can try and break-in, crash what ever this box
> from the internet side.
>
> I am asking for links, pointer to make sure this is configured as
> secure/solid as possible. I will be installing 3.3-STA
> > VM doesn't do HTML/MIME very well, although I understand in later
> > versions of XEmacs they've incorporated some packages that handle things
> > better. (I'm still using XEmacs 19.16, from the dark ages...)
>
> Does it do IMAP?
It doesn't even do POP, I use fetchmail/procmailrc to get m
> > VM doesn't do HTML/MIME very well, although I understand in later
> > versions of XEmacs they've incorporated some packages that handle things
> > better. (I'm still using XEmacs 19.16, from the dark ages...)
>
> Does it do IMAP?
It doesn't even do POP, I use fetchmail/procmailrc to get
> > For what it's worth, I agree with Marcel. Version bumps should be
> > discouraged, but not totally avoided.
>
> What is the reason to not avoid the version bump?
Because if you don't have the latest/greatest library (old machines),
newer programs that are compiled against the latest/greates
> > For what it's worth, I agree with Marcel. Version bumps should be
> > discouraged, but not totally avoided.
>
> What is the reason to not avoid the version bump?
Because if you don't have the latest/greatest library (old machines),
newer programs that are compiled against the latest/greate
> > > Yes, we shouldn't version bump every time someone has a whim, ending
> > > up with 10 version bumps/week, but neither should we avoid them
> > > altogether and cause the Linux syndrome of programs refusing to work
> > > because they have the *wrong* version of glibc2.3 (or whatever)
> >
> > > Yes, we shouldn't version bump every time someone has a whim, ending
> > > up with 10 version bumps/week, but neither should we avoid them
> > > altogether and cause the Linux syndrome of programs refusing to work
> > > because they have the *wrong* version of glibc2.3 (or whatever)
> >
> > > I strongly disagree. Spitting "unresolved references" is *not* a way to
> > > tell the user that he doesn't have the right libraries.
> >
> > I strongly disagree. This is much better than version bump. After all,
> > we can add suggestion to upgrade libraries to the "unresolved references"
>
> Just to toss in my 0.02 cents, I've been using exmh for a while and
> am on one hand very satisfied with it, on the other hand it's handling
> of mime and html is not good, so I'd be very interested in discussing
> this topic too.
VM doesn't do HTML/MIME very well, although I understand in late
> > > I strongly disagree. Spitting "unresolved references" is *not* a way to
> > > tell the user that he doesn't have the right libraries.
> >
> > I strongly disagree. This is much better than version bump. After all,
> > we can add suggestion to upgrade libraries to the "unresolved references"
> Just to toss in my 0.02 cents, I've been using exmh for a while and
> am on one hand very satisfied with it, on the other hand it's handling
> of mime and html is not good, so I'd be very interested in discussing
> this topic too.
VM doesn't do HTML/MIME very well, although I understand in lat
> Nate: it's a while since I looked at VM on XEmacs. I found its
> layout cluttered and it's key sequences awkward. How configurable
> is it, really? Do you use it as it comes out of the box?
Really configurable, and no, I don't use it in an out-of-the-box
configuration.
I remap many of the ke
> Nate: it's a while since I looked at VM on XEmacs. I found its
> layout cluttered and it's key sequences awkward. How configurable
> is it, really? Do you use it as it comes out of the box?
Really configurable, and no, I don't use it in an out-of-the-box
configuration.
I remap many of the k
> > 3. Needlessly cross-posted (watch your cc lines, loser! :).
>
> On a different topic, does anyone know of a good X mailer
> (currently I am using exmh) :
>
> 1. user friendly
> 2. filtering capability
> 3. thread topic support
XEmacs + VM works very well for me, but Emacsen have a fairly la
> > 3. Needlessly cross-posted (watch your cc lines, loser! :).
>
> On a different topic, does anyone know of a good X mailer
> (currently I am using exmh) :
>
> 1. user friendly
> 2. filtering capability
> 3. thread topic support
XEmacs + VM works very well for me, but Emacsen have a fairly l
> : But, they should be PCI/non-Winmodem, as Kevin pointed out, so we
> : shouldn't need cardbus seperately from pci.
>
> Just the attachment...
Ahh, OK. I'm not familiar enough with the new code to know how exactly
it's organized. :)
Nate
To Unsubscribe: send mail to majord...@freebsd.org
w
> "Matthew N. Dodd" wrote:
> > On Sun, 5 Sep 1999, Warner Losh wrote:
> > > Might be a good time have a sys/dev/sio and have pccard, cardbus, pci
> > > and isa attachments there. Yes, I did say cardbus, since I have seen
> > > cardbus PCI modems that are NOT winmodems.
> >
> > And MCA and EISA at
> : I'd really like to see the sio driver code being able to support PCI
> : devices...
>
> Might be a good time have a sys/dev/sio and have pccard, cardbus, pci
> and isa attachments there. Yes, I did say cardbus, since I have seen
> cardbus PCI modems that are NOT winmodems.
But, they should
> : But, they should be PCI/non-Winmodem, as Kevin pointed out, so we
> : shouldn't need cardbus seperately from pci.
>
> Just the attachment...
Ahh, OK. I'm not familiar enough with the new code to know how exactly
it's organized. :)
Nate
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
> "Matthew N. Dodd" wrote:
> > On Sun, 5 Sep 1999, Warner Losh wrote:
> > > Might be a good time have a sys/dev/sio and have pccard, cardbus, pci
> > > and isa attachments there. Yes, I did say cardbus, since I have seen
> > > cardbus PCI modems that are NOT winmodems.
> >
> > And MCA and EISA a
> : I'd really like to see the sio driver code being able to support PCI
> : devices...
>
> Might be a good time have a sys/dev/sio and have pccard, cardbus, pci
> and isa attachments there. Yes, I did say cardbus, since I have seen
> cardbus PCI modems that are NOT winmodems.
But, they should
> There was such a thing in 386BSD and FreeBSD1.0
I remember no such thing doing a 'bogomips' to compare against Linux.
Certainly not in 386BSD.
Nate
>
> I certainly thing it was a worth-while thing.
> I'd try make the loop as similar to the Linux one so that they are
> comparable.
>
> On Th
> There was such a thing in 386BSD and FreeBSD1.0
I remember no such thing doing a 'bogomips' to compare against Linux.
Certainly not in 386BSD.
Nate
>
> I certainly thing it was a worth-while thing.
> I'd try make the loop as similar to the Linux one so that they are
> comparable.
>
> On T
> > I have the feeling that "Software Licensing Program" speaks .
>
> You can read about the Sun Community Source License on their web site now.
> It is the same license that brings the JDK to FreeBSD.
*NOT* As we read it (The JDK folks), the CSL doesn't allow us to release
the JDK on FreeBSD
> > I have the feeling that "Software Licensing Program" speaks .
>
> You can read about the Sun Community Source License on their web site now.
> It is the same license that brings the JDK to FreeBSD.
*NOT* As we read it (The JDK folks), the CSL doesn't allow us to release
the JDK on FreeBS
[ I'm nit-picking here, feel free to ignore ]
> Doug--- /usr/src/etc/rc Thu Aug 26 20:56:36 1999
> +++ rcFri Aug 27 09:52:39 1999
> @@ -8,24 +8,25 @@
> # and the console is the controlling terminal.
>
> # Note that almost all the user-configurable behavior is no longer in
> -
> > [...]
> > 2. value ) instead of value) for case statements
> > [...]
> >case $? in
> > - 0)
> > + 0 )
> >;;
> > - 2)
> > + 2 )
> >exit 1
> >;;
> > - 4)
> > + 4 )
> >reboot
> >echo "reboo
[ I'm nit-picking here, feel free to ignore ]
> Doug--- /usr/src/etc/rc Thu Aug 26 20:56:36 1999
> +++ rcFri Aug 27 09:52:39 1999
> @@ -8,24 +8,25 @@
> # and the console is the controlling terminal.
>
> # Note that almost all the user-configurable behavior is no longer in
>
> > [...]
> > 2. value ) instead of value) for case statements
> > [...]
> >case $? in
> > - 0)
> > + 0 )
> >;;
> > - 2)
> > + 2 )
> >exit 1
> >;;
> > - 4)
> > + 4 )
> >reboot
> >echo "rebo
> > Matt doesn't represent the FreeBSD project, and even if he rewrites
> > the VFS subsystem so he can understand it, his rewrite would face
> > considerable resistance on its way into FreeBSD. I don't think
> > there is reason to rewrite it, but there certainly are areas
> > that need fixing.
>
> > Matt doesn't represent the FreeBSD project, and even if he rewrites
> > the VFS subsystem so he can understand it, his rewrite would face
> > considerable resistance on its way into FreeBSD. I don't think
> > there is reason to rewrite it, but there certainly are areas
> > that need fixing.
>
> I had always wondered how select/poll worked (actually see the end of the
> mail to see the broader question), so I pulled up select() and family
> and started reading and chasing stuff around. I think that I fully
> understand (much praise to whoever wrote most of that, it was incredibly
> easy
> I had always wondered how select/poll worked (actually see the end of the
> mail to see the broader question), so I pulled up select() and family
> and started reading and chasing stuff around. I think that I fully
> understand (much praise to whoever wrote most of that, it was incredibly
> eas
> > FreeBSD has no kernel 'thread' support, only user level.
>
> That's not strictly true. The fact is we have both kernel and user
> threads but no mapping between the two... The kernel already
> internally use some threads.
Your definition of kernel threads and mine are obviously quite
differen
> > FreeBSD has no kernel 'thread' support, only user level.
>
> That's not strictly true. The fact is we have both kernel and user
> threads but no mapping between the two... The kernel already
> internally use some threads.
Your definition of kernel threads and mine are obviously quite
differe
> implemented at least up to 3.2-stable. How could one ensure that their
> threads in an application can be "equally" distributed to all the
> processors in FreeBSD?
You can't.
> Are there any documents on FreeBSD 3.*'s thread
> support(both kernel and user level)?
FreeBSD has no kernel 'thr
> implemented at least up to 3.2-stable. How could one ensure that their
> threads in an application can be "equally" distributed to all the
> processors in FreeBSD?
You can't.
> Are there any documents on FreeBSD 3.*'s thread
> support(both kernel and user level)?
FreeBSD has no kernel 'th
> > Matt doesn't represent the FreeBSD project, and even if he rewrites
> > the VFS subsystem so he can understand it, his rewrite would face
> > considerable resistance on its way into FreeBSD. I don't think
> > there is reason to rewrite it, but there certainly are areas
> > that need fixing.
>
> > Both struct timespec and struct timeval are major mistakes, they
> > make arithmetic on timestamps an expensive operation. Timestamps
> > should be stored as integers using an fix-point notations, for
> > instance 64bits with 32bit fractional seconds (the NTP timestamp),
> > or in the future 1
> > Matt doesn't represent the FreeBSD project, and even if he rewrites
> > the VFS subsystem so he can understand it, his rewrite would face
> > considerable resistance on its way into FreeBSD. I don't think
> > there is reason to rewrite it, but there certainly are areas
> > that need fixing.
>
> > Both struct timespec and struct timeval are major mistakes, they
> > make arithmetic on timestamps an expensive operation. Timestamps
> > should be stored as integers using an fix-point notations, for
> > instance 64bits with 32bit fractional seconds (the NTP timestamp),
> > or in the future
> : There
> : is simply no reason to assume that anything under a gnu directory is GPLd,
> : or that anything GPLd is going to be under a gnu directory (which it's not.)
>
> I'm afraid there is. It has been stated many times in the past that
> all GPL'd software resides under gnu. This is true i
> : There
> : is simply no reason to assume that anything under a gnu directory is GPLd,
> : or that anything GPLd is going to be under a gnu directory (which it's not.)
>
> I'm afraid there is. It has been stated many times in the past that
> all GPL'd software resides under gnu. This is true
> > ---Steve Tarkalson said:
> > > this is solved by one of two methods:
> > >1-) require the caller of gethostbyaddr() to supply a pointer to
> > >a hostent struct which will be filled.
> > > or 2-) the library uses thread specific storage which is re-used in
> > >each call.
>
> > ---Steve Tarkalson said:
> > > this is solved by one of two methods:
> > >1-) require the caller of gethostbyaddr() to supply a pointer to
> > >a hostent struct which will be filled.
> > > or 2-) the library uses thread specific storage which is re-used in
> > >each call.
>
101 - 200 of 278 matches
Mail list logo
