On Wed, 28 Jun 2000, Kenneth D. Merry wrote:
> FWIW, I'm in favor of a pointer argument as well. The way I implemented it
> was actually with a third argument, instead of changing the int to void.
> i.e.:
[...]
> I don't feel too strongly about it either way -- I suppose it's about the
> same
You have to declare ioctl as the next:
#define SIO_SET_MULTICAST_FILTER_IO ('s', 63)
And after that in your code mannualy via functions documented in
copy(9) and fetch(9) manpages, to access that user space structure,
user space pointer will be available for you as third arument
in your
On Wed, 28 Jun 2000, Dave Baukus wrote:
> All this talk of mbuf prompts me to point a small bug in M_PREPEND that
> was introduced somewhere between 3.3 and 4.0; maybe its also in 5.x.
>
[...]
> If m_prepend() fails then
No longer an issue in 5.0-CURRENT, and I'm looking at versi
Maybe someone on this list knows the answer...
How do you add 2 static routes to the same network through different
gateways with different metric sizes? (FBSD 4.0-RELEASE,3.3-RELEASE)
This is legal to do in routing...
Example:
# route add -net 192.168.0.0 -netmask 255.255.255.
On Wed, Jun 28, 2000 at 12:00:50 -0400, Andrew Gallatin wrote:
> Dennis writes:
> >
> > Its not really "wonderful" to those that have already implemented something
> > using the old method.
> >
>
> Speaking as somebody who maintains 3 out-of-tree network drivers & a
> bunch of local code, a
Could anybody advise me on this:
For an implementation of IGMPv3, I
had to extend the socket api
following the draft(s). I had to add
two ioctl commands:
SIO_GET_MULTICAST_FILTER and SIO_SET_MULTICAST_FILTER.
The argument is a
structure that has a variable size.
FreeBSD uses some macros, and the
On Wed, 28 Jun 2000, Andrew Gallatin wrote:
> YES! This is wonderful news.
>
> I started coding device drivers on Digital UNIX and have long missed
> this feature. I can't count the number of times I've gotten 90% of
> the way through doing something with ext mubfs & thought to myself
> "oh
On Wed, 28 Jun 2000, Dennis wrote:
> >YES! This is wonderful news.
> >
> >I started coding device drivers on Digital UNIX and have long missed
> >this feature. I can't count the number of times I've gotten 90% of
> >the way through doing something with ext mubfs & thought to myself
> >"oh hel
Thus spake Jordan K. Hubbard ([EMAIL PROTECTED]):
> > What happened to the plans to move to the TurboVision library?
> We're still working on it.
Yes, someone should encourage John Baldwin to fix that.
For example by promising some cakes or something :)
Alex
--
cat: /home/alex/.sig: No such fi
> What happened to the plans to move to the TurboVision library?
We're still working on it.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Dennis writes:
>
> Its not really "wonderful" to those that have already implemented something
> using the old method.
>
Speaking as somebody who maintains 3 out-of-tree network drivers & a
bunch of local code, all of which makes heavy use of external mbufs, I
certainly consider it to be "
>
> Its not really "wonderful" to those that have already
> implemented something using the old method.
>
Unless you get to rip out your own workarounds for the missing functionality
and get someone else to support those for you.
I think I'll call it delegation through innovation. :-)
Kees
On Mon, Jun 26, 2000 at 09:37:40AM -0700, Jordan K. Hubbard wrote:
> > In theory, this is a doddle. sysinstall already lets the user choose from
> > packages to install. In practice, I think it's a little more difficult,
> > because:
>
> I'm still wondering why the docs bits can't be, at a mini
On Mon, Jun 26, 2000 at 09:37:40AM -0700, Jordan K. Hubbard wrote:
> > In theory, this is a doddle. sysinstall already lets the user choose from
> > packages to install. In practice, I think it's a little more difficult,
> > because:
>
> I'm still wondering why the docs bits can't be, at a mini
At 10:09 AM 6/28/00 -0400, Andrew Gallatin wrote:
>
>Bosko Milekic writes:
>
> > This code includes all that was discussed in the previous Email, as
> > well as a better/actually working external storage facility for
clusters.
> > Previously, it was very difficult to allocate external stor
Bosko Milekic writes:
> This code includes all that was discussed in the previous Email, as
> well as a better/actually working external storage facility for clusters.
> Previously, it was very difficult to allocate external storage, attach it
> to the mbuf, _and_ as well maintain
New problems with 4.0-S nfsv3 client (this problems not exist with 3.4-S)
If file have write only permisson we can't append it properly, with read+write
permissons all ok, this is serious error ...
For demonstartion we use nfsserver and nfsclient mounted via nfsv3/udp:
FreeBSD 4.0-STABLE FreeBS
Christoph Sold wrote:
>
> Leif Neland wrote:
> >
> > Talking about IrDA, how much hardware is needed on a Asus P2B ?
> > Is it something which can be build from parts from the local electronics
> > dealer?
> Yes. Well, local... plan to do some shopping around.
>
> > Is a schematic available?
Leif Neland wrote:
>
> Talking about IrDA, how much hardware is needed on a Asus P2B ?
> Is it something which can be build from parts from the local electronics
> dealer?
Yes. Well, local... plan to do some shopping around.
> Is a schematic available?
c't (German computer bi-weekly) had one a
Talking about IrDA, how much hardware is needed on a Asus P2B ?
Is it something which can be build from parts from the local electronics
dealer?
Is a schematic available?
Leif
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
20 matches
Mail list logo
