On Wed, 15 Sep 1999 10:06:59 MST, Mike Smith wrote:
> > Actually, as with many such cases, the floppy disk driver turned out to
> > be flakey. We resolved this via private mail.
>
> Driver, or drive? The BIOS is the driver at this point in time.
Argh! Thanks. I meant the floppy drive.
Ciao,
On Wed, Sep 15, 1999 at 06:37:34PM -0400, David E. Cross wrote:
> method isn't working. FreeBSD doesn't have a gethostname _system_ call, but
> it does have the gethostname() library call (which uses sysctl(2)). Any
> ideas how to get perl to use this?
Write a small xs module?
--
Christopher Ma
On Wed, 15 Sep 1999, Warner Losh wrote:
> In message <199909151928.vaa26...@dorifer.heim3.tu-clausthal.de> Oliver
> Fromme writes:
> : It only works on two's-complement machines, though, but I'm not
> : aware of any FreeBSD port to an architecture that doesn't use
> : two's-complement numbers...
On Wed, Sep 15, 1999 at 06:37:34PM -0400, David E. Cross wrote:
> method isn't working. FreeBSD doesn't have a gethostname _system_ call, but
> it does have the gethostname() library call (which uses sysctl(2)). Any
> ideas how to get perl to use this?
Write a small xs module?
--
Christopher M
On Wed, 15 Sep 1999, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Oliver Fromme
>writes:
> : It only works on two's-complement machines, though, but I'm not
> : aware of any FreeBSD port to an architecture that doesn't use
> : two's-complement numbers...
>
> I'm not aware of any one's-co
On Wed, 15 Sep 1999, Jordan K. Hubbard wrote:
> It can go in after the freeze - it's a bit late to be asking now. :)
I was guessing as much :) I didn't specifically see anyone requesting
for these things in -STABLE, so I didn't really pay much attention to
merging these things. It makes me wonde
It can go in after the freeze - it's a bit late to be asking now. :)
> On Wed, 15 Sep 1999, Dan Nelson wrote:
>
> > RCS file: /home/ncvs/src/bin/dd/dd.c,v
> >
> > revision 1.17
> > date: 1999/06/19 19:49:32; author: green; state: Exp; lines: +25 -21
On Wed, 15 Sep 1999, Dan Nelson wrote:
> RCS file: /home/ncvs/src/bin/dd/dd.c,v
>
>
> revision 1.17
> date: 1999/06/19 19:49:32; author: green; state: Exp; lines: +25 -21
> Miscellaneous dd(1) changes: mainly fixing variable types (size_t,
> ssize_t,
On Wed, 15 Sep 1999, Jordan K. Hubbard wrote:
> It can go in after the freeze - it's a bit late to be asking now. :)
I was guessing as much :) I didn't specifically see anyone requesting
for these things in -STABLE, so I didn't really pay much attention to
merging these things. It makes me wond
It can go in after the freeze - it's a bit late to be asking now. :)
> On Wed, 15 Sep 1999, Dan Nelson wrote:
>
> > RCS file: /home/ncvs/src/bin/dd/dd.c,v
> >
> > revision 1.17
> > date: 1999/06/19 19:49:32; author: green; state: Exp; lines: +25 -21
On Wed, 15 Sep 1999, Dan Nelson wrote:
> RCS file: /home/ncvs/src/bin/dd/dd.c,v
>
> revision 1.17
> date: 1999/06/19 19:49:32; author: green; state: Exp; lines: +25 -21
> Miscellaneous dd(1) changes: mainly fixing variable types (size_t,
> ssize_t, of
In message <199909151928.vaa26...@dorifer.heim3.tu-clausthal.de> Oliver Fromme
writes:
: It only works on two's-complement machines, though, but I'm not
: aware of any FreeBSD port to an architecture that doesn't use
: two's-complement numbers...
I'm not aware of any one's-complement machine that
In message <[EMAIL PROTECTED]> Oliver Fromme writes:
: It only works on two's-complement machines, though, but I'm not
: aware of any FreeBSD port to an architecture that doesn't use
: two's-complement numbers...
I'm not aware of any one's-complement machine that was manufacture
after about 1980.
On Wed, 15 Sep 1999, Christopher Sedore wrote:
> My ideas for this are a little different than what I've seen proposed thus
> far, more along the lines of creating something that acts as both an event
> queue and a IOCP. Ideally this would be a descriptor that could be shared
> across processes
On Wed, 15 Sep 1999, Christopher Sedore wrote:
> My ideas for this are a little different than what I've seen proposed thus
> far, more along the lines of creating something that acts as both an event
> queue and a IOCP. Ideally this would be a descriptor that could be shared
> across processes
> Umm, you can edit /usr/X11R6/lib/X11/xdm/Xservers to configure xdm to
> run say /usr/config/X (which would be stored on the local machiens hard
> drive) instead of /usr/X11R6/bin/X. This is a much simpler solution.
> :) (Just symlink /usr/config/X to /usr/X11R6/bin/XF86_Whatever.)
Simpler? It
> Thanks, I figured as much. I just thought I remember being told at one
> point that gdb's thread support on FreeBSD had improved. Given a choice
> between adding thread support to GDB myself and developing my application
> on NT, which by the way has very good thread debugging support on MSVC6.0.
On 15-Sep-99 David E. Cross wrote:
> We have a very hetergenous environment here (even among the FreeBSD
> boxes).
> Each PC tends to be just a little bit different. This expecially
> causes
> problems since we wish to have XDM on each machine on boot and have X
> on a NFS partition. TO alleviat
> Umm, you can edit /usr/X11R6/lib/X11/xdm/Xservers to configure xdm to
> run say /usr/config/X (which would be stored on the local machiens hard
> drive) instead of /usr/X11R6/bin/X. This is a much simpler solution.
> :) (Just symlink /usr/config/X to /usr/X11R6/bin/XF86_Whatever.)
Simpler? I
Thanks, I figured as much. I just thought I remember being told at one
point that gdb's thread support on FreeBSD had improved. Given a choice
between adding thread support to GDB myself and developing my application
on NT, which by the way has very good thread debugging support on MSVC6.0.
I think
sorry folks, i passed this on to someone who should know..
jan
-- Forwarded message --
Date: Wed, 15 Sep 1999 17:07:33 -0400 (EDT)
From: Chris Doherty
To: f.johan.beisser
Subject: Re: does gdb on 3.3RC have thread support? (fwd)
Kip--
I'm not actually on the lists; your messa
> Thanks, I figured as much. I just thought I remember being told at one
> point that gdb's thread support on FreeBSD had improved. Given a choice
> between adding thread support to GDB myself and developing my application
> on NT, which by the way has very good thread debugging support on MSVC6.0
> Softupdates has known bugs relating to filesystem full conditions which
> I believe Kirk is working on. There isn't much you can do until then
> other then either disable softupdates or work to avoid the disk-full
> condition. The panic does not occur very frequently so working
Krzysztof Krawczyk writes:
> Could someone say me, why the maximum packetsize in ping command is 8184
> (ping -s 8184)? If I want to do a bigger packetsize than this i got
> message like this:
Look at the sysctl variable `net.inet.raw.maxdgram'.
/assar
To Unsubscribe: send mail to majord...@fr
On 15-Sep-99 David E. Cross wrote:
> We have a very hetergenous environment here (even among the FreeBSD
> boxes).
> Each PC tends to be just a little bit different. This expecially
> causes
> problems since we wish to have XDM on each machine on boot and have X
> on a NFS partition. TO allevia
> A simple question: Are USB cameras supported? Is anybody working on it?
No. Isochronous pipes are not supported yet, but work is underway.
> Oh, btw, how long can USB be extended?
Hm, the mechanical specification of the cable is confusing before
coffee. I think it was 6ft / 2m.
You'll notice
Thanks, I figured as much. I just thought I remember being told at one
point that gdb's thread support on FreeBSD had improved. Given a choice
between adding thread support to GDB myself and developing my application
on NT, which by the way has very good thread debugging support on MSVC6.0.
I thin
sorry folks, i passed this on to someone who should know..
jan
-- Forwarded message --
Date: Wed, 15 Sep 1999 17:07:33 -0400 (EDT)
From: Chris Doherty <[EMAIL PROTECTED]>
To: f.johan.beisser <[EMAIL PROTECTED]>
Subject: Re: does gdb on 3.3RC have thread support? (fwd)
Kip--
I'
> From: Krzysztof Krawczyk
> Date: 1999-09-15 13:12:21 -0700
> To: hack...@freebsd.org
> Subject: ping: sendto: Message too long
> In-reply-to:
>
> Delivered-to: freebsd-hackers@freebsd.org
> X-Sender: c...@tepsa.lame.pl
> X-Loop: FreeBSD.ORG
>
> Hi,
>
> Could someone say me, why the maximum pack
When I run my program under ddd, press Ctrl-C to return control to gdb and
then type info threads at the gdb prompt it returns nothing.
When I run it under gdb on the command line and do the same as above, gdb
dumps core.
How should I proceed? Should I grab the source for uthreads from current?
> Softupdates has known bugs relating to filesystem full conditions which
> I believe Kirk is working on. There isn't much you can do until then
> other then either disable softupdates or work to avoid the disk-full
> condition. The panic does not occur very frequently so workin
Krzysztof Krawczyk <[EMAIL PROTECTED]> writes:
> Could someone say me, why the maximum packetsize in ping command is 8184
> (ping -s 8184)? If I want to do a bigger packetsize than this i got
> message like this:
Look at the sysctl variable `net.inet.raw.maxdgram'.
/assar
To Unsubscribe: send
> > > 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, bu
> A simple question: Are USB cameras supported? Is anybody working on it?
No. Isochronous pipes are not supported yet, but work is underway.
> Oh, btw, how long can USB be extended?
Hm, the mechanical specification of the cable is confusing before
coffee. I think it was 6ft / 2m.
You'll notice
> > 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
We have a very hetergenous environment here (even among the FreeBSD boxes).
Each PC tends to be just a little bit different. This expecially causes
problems since we wish to have XDM on each machine on boot and have X
on a NFS partition. TO alleviate this we invented a simple Perl script
to repla
> From: Krzysztof Krawczyk <[EMAIL PROTECTED]>
> Date: 1999-09-15 13:12:21 -0700
> To: [EMAIL PROTECTED]
> Subject: ping: sendto: Message too long
> In-reply-to:
> <[EMAIL PROTECTED]>
> Delivered-to: [EMAIL PROTECTED]
> X-Sender: [EMAIL PROTECTED]
> X-Loop: FreeBSD.ORG
>
> Hi,
>
> Could someone sa
When I run my program under ddd, press Ctrl-C to return control to gdb and
then type info threads at the gdb prompt it returns nothing.
When I run it under gdb on the command line and do the same as above, gdb
dumps core.
How should I proceed? Should I grab the source for uthreads from current
Hi,
Could someone say me, why the maximum packetsize in ping command is 8184
(ping -s 8184)? If I want to do a bigger packetsize than this i got
message like this:
tepsa:cys:/home# ping -s 65000 127.0.0.1
PING 127.0.0.1 (127.0.0.1): 65000 data bytes
ping: sendto: Message too long
ping
> This is a multi-part message in MIME format.
Don't do this. Plain text, please.
> Hi,
> I need to send signals to a network interface I worte but I can't find
> how.
ioctl()
> I know that in some other Bsd flavours you can use the sysctl functions =
> which is part
> of the ifnet struct. In
Bakul Shah wrote in list.freebsd-hackers:
> [...]
> Let me say it another way. The bugfix should be accepted and
> another PR be filed that says there needs to be a constant
> defining the largest possible off_t value. Also note that
> traditionally Unix does not define max values for every
We have a very hetergenous environment here (even among the FreeBSD boxes).
Each PC tends to be just a little bit different. This expecially causes
problems since we wish to have XDM on each machine on boot and have X
on a NFS partition. TO alleviate this we invented a simple Perl script
to repl
When I run my program under ddd, press Ctrl-C to return control to gdb and
then type info threads at the gdb prompt it returns nothing.
When I run it under gdb on the command line and do the same as above, gdb
dumps core.
How should I proceed? Should I grab the source for uthreads from current?
> date: 1999/06/19 19:49:32; author: green; state: Exp; lines: +25 -21
> Miscellaneous dd(1) changes: mainly fixing variable types (size_t,
> ssize_t, off_t, int, u_int64_t, etc.). dd(1) should now work properly
> with REALLY big amounts of data.
>
> Should be a -stable candidate by now (3 mont
Hi,
Could someone say me, why the maximum packetsize in ping command is 8184
(ping -s 8184)? If I want to do a bigger packetsize than this i got
message like this:
tepsa:cys:/home# ping -s 65000 127.0.0.1
PING 127.0.0.1 (127.0.0.1): 65000 data bytes
ping: sendto: Message too long
pin
> > > 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, b
> > 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
Bakul Shah wrote in list.freebsd-hackers:
> [...]
> Let me say it another way. The bugfix should be accepted and
> another PR be filed that says there needs to be a constant
> defining the largest possible off_t value. Also note that
> traditionally Unix does not define max values for every
> date: 1999/06/19 19:49:32; author: green; state: Exp; lines: +25 -21
> Miscellaneous dd(1) changes: mainly fixing variable types (size_t,
> ssize_t, off_t, int, u_int64_t, etc.). dd(1) should now work properly
> with REALLY big amounts of data.
>
> Should be a -stable candidate by now (3 mon
When I run my program under ddd, press Ctrl-C to return control to gdb and
then type info threads at the gdb prompt it returns nothing.
When I run it under gdb on the command line and do the same as above, gdb
dumps core.
How should I proceed? Should I grab the source for uthreads from current?
In the last episode (Sep 15), Bakul Shah said:
> PR bin/6509 (submitted in May 1998) already has a patch to fix this
> but it was rejected because off_t was assumed by the bug
> fixer/submitter to be a quat (int64_t). I can't even get an IDE disk
> below 2G byte easily! And we are still years awa
> This is a multi-part message in MIME format.
Don't do this. Plain text, please.
> Hi,
> I need to send signals to a network interface I worte but I can't find
> how.
ioctl()
> I know that in some other Bsd flavours you can use the sysctl functions =
> which is part
> of the ifnet struct. I
In the last episode (Sep 15), Bakul Shah said:
> PR bin/6509 (submitted in May 1998) already has a patch to fix this
> but it was rejected because off_t was assumed by the bug
> fixer/submitter to be a quat (int64_t). I can't even get an IDE disk
> below 2G byte easily! And we are still years aw
Parag Patel wrote:
>
> I said:
>
> >Anyway, command-line apps have been obsolete for years, so I guess we
> >should go on and find better things to argue about. :)
>
> I guess people missed the ":)" so I'd better explain.
>
> Most computers are embedded and becoming both more ubiquitous and
>
On Wed, 15 Sep 1999, Jayson Nordwick wrote:
> I did research this weekend on high performance I/O. I looked at differerent
> approaches and to me they all appear the same (I know that I will get some
> flamage for this). The two most prominent models that I saw were IO
> Completion Ports and
>
>
> On Wed, 15 Sep 1999, Ruslan Ermilov wrote:
>
> > > The aio_* stuff (I use a custom patched version in 4.x) offers performance
> > > advantages over select() with large numbers of descriptors. In terms of
> > > efficiency, I don't have any trouble saturating full-duplex 100mbit link
> > >
Hi,
Attn AVerMedia owners of TV cards with Bt878's
(sorry - not the 848 users)
I've got the specs from AVerMedia which mean I can
finally get the Tuner Type autoselected for your cards.
If you have an AVerMedia card which is one of the newer
ones with a Bt878, can you please email me.
I do not
Parag Patel wrote:
>
> I said:
>
> >Anyway, command-line apps have been obsolete for years, so I guess we
> >should go on and find better things to argue about. :)
>
> I guess people missed the ":)" so I'd better explain.
>
> Most computers are embedded and becoming both more ubiquitous and
>
On Tue, 14 Sep 1999, Nik Clayton wrote:
> What we need is people like yourself, who are having to go through the
> learning curve, to document stuff as you're finding it out. It doesn't
> matter if your notes are a bit rough and ready, because the next person
> to use them can improve on them,
Hi,
Attn AVerMedia owners of TV cards with Bt878's
(sorry - not the 848 users)
I've got the specs from AVerMedia which mean I can
finally get the Tuner Type autoselected for your cards.
If you have an AVerMedia card which is one of the newer
ones with a Bt878, can you please email me.
I do not h
wouldn't this be also interesting to see for FreeBSD ? - anyone
with the required skills having time to have a look at it ?
t
-- forwarded message --
From: der Mouse <[EMAIL PROTECTED]>
Subject: Re: dynamically growing ffs
> Is there anything to prevent someone hacking up fsck_ffs to increase
PR bin/6509 (submitted in May 1998) already has a patch to
fix this but it was rejected because off_t was assumed by the
bug fixer/submitter to be a quat (int64_t). I can't even get
an IDE disk below 2G byte easily! And we are still years
away from zettabyte disks. So I don't see the point of
b
> > > FreeBSD write "zf_read: error".
> >
> > Your mfsroot floppy has a bad sector. Try a different floppy.
>
> Actually, as with many such cases, the floppy disk driver turned out to
> be flakey. We resolved this via private mail.
Driver, or drive? The BIOS is the driver at this point in time
Hi,
I need to send signals to a network interface I worte but I can't find how.
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.
I need to send custom directions to the interface so I can't
I think this rather belongs to -hardware...
Leif Neland wrote in list.freebsd-hackers:
> A simple question: Are USB cameras supported? Is anybody working on it?
Do you mean photo cameras (i.e. for still images) or video
cameras? Those are two completely different things.
The Kodak DC240 digit
Hi,
I need to send signals to a network
interface I worte but I can't find how.
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.
I need to send custom directions to the
interface so I
>
>
> On Wed, 15 Sep 1999, Ruslan Ermilov wrote:
>
> > > The aio_* stuff (I use a custom patched version in 4.x) offers performance
> > > advantages over select() with large numbers of descriptors. In terms of
> > > efficiency, I don't have any trouble saturating full-duplex 100mbit link
> > >
On Wed, 15 Sep 1999, Ruslan Ermilov wrote:
> > The aio_* stuff (I use a custom patched version in 4.x) offers performance
> > advantages over select() with large numbers of descriptors. In terms of
> > efficiency, I don't have any trouble saturating full-duplex 100mbit link
> > with aio routine
On Wed, 15 Sep 1999, Jayson Nordwick wrote:
> I did research this weekend on high performance I/O. I looked at differerent
> approaches and to me they all appear the same (I know that I will get some
> flamage for this). The two most prominent models that I saw were IO
> Completion Ports and S
On Wed, 15 Sep 1999, Ruslan Ermilov wrote:
> > The aio_* stuff (I use a custom patched version in 4.x) offers performance
> > advantages over select() with large numbers of descriptors. In terms of
> > efficiency, I don't have any trouble saturating full-duplex 100mbit link
> > with aio routin
> > > FreeBSD write "zf_read: error".
> >
> > Your mfsroot floppy has a bad sector. Try a different floppy.
>
> Actually, as with many such cases, the floppy disk driver turned out to
> be flakey. We resolved this via private mail.
Driver, or drive? The BIOS is the driver at this point in tim
wouldn't this be also interesting to see for FreeBSD ? - anyone
with the required skills having time to have a look at it ?
t
-- forwarded message --
From: der Mouse
Subject: Re: dynamically growing ffs
> Is there anything to prevent someone hacking up fsck_ffs to increase
> fs->fs_size and ev
On Tue, 14 Sep 1999, Nik Clayton wrote:
> What we need is people like yourself, who are having to go through the
> learning curve, to document stuff as you're finding it out. It doesn't
> matter if your notes are a bit rough and ready, because the next person
> to use them can improve on them, a
I think this rather belongs to -hardware...
Leif Neland wrote in list.freebsd-hackers:
> A simple question: Are USB cameras supported? Is anybody working on it?
Do you mean photo cameras (i.e. for still images) or video
cameras? Those are two completely different things.
The Kodak DC240 digita
PR bin/6509 (submitted in May 1998) already has a patch to
fix this but it was rejected because off_t was assumed by the
bug fixer/submitter to be a quat (int64_t). I can't even get
an IDE disk below 2G byte easily! And we are still years
away from zettabyte disks. So I don't see the point of
bl
On Tue, Sep 14, 1999 at 03:54:50PM -0700, Parag Patel wrote:
> Anyway, command-line apps have been obsolete for years, so I guess we
> should go on and find better things to argue about. :)
Heh.
So far, I've only found one GUI that I would really miss without X
Windows: SWAT in netscape.
--
Do
On Tue, Sep 14, 1999 at 03:54:50PM -0700, Parag Patel wrote:
> Anyway, command-line apps have been obsolete for years, so I guess we
> should go on and find better things to argue about. :)
Heh.
So far, I've only found one GUI that I would really miss without X
Windows: SWAT in netscape.
--
D
On Tue, 14 Sep 1999 15:53:03 -0400, John Baldwin wrote:
> > FreeBSD write "zf_read: error".
>
> Your mfsroot floppy has a bad sector. Try a different floppy.
Actually, as with many such cases, the floppy disk driver turned out to
be flakey. We resolved this via private mail.
Something to kee
On Tue, Sep 14, 1999 at 02:14:14PM -0700, Doug White wrote:
> On Tue, 14 Sep 1999, Ruslan Ermilov wrote:
>
> > > > > use_sockets yes
> > > > > same_ports yes
> > > > > #
> > > > > # machine1 redirections
> > > > > #redirect_port tcp 192.168.2.237:ssh 1.2.3.4:ssh
> > > > > #redirect_port tcp 192.1
On Tue, 14 Sep 1999 15:53:03 -0400, John Baldwin wrote:
> > FreeBSD write "zf_read: error".
>
> Your mfsroot floppy has a bad sector. Try a different floppy.
Actually, as with many such cases, the floppy disk driver turned out to
be flakey. We resolved this via private mail.
Something to ke
On Tue, Sep 14, 1999 at 04:40:37PM -0400, Christopher Sedore wrote:
>
>
> On Mon, 13 Sep 1999, Jayson Nordwick wrote:
>
> > While reading through (at least trying to... I wish there was some sort of
> > kernel documentation available, the entry fee is very high) the aio_* calls,
> > I had a few
I did research this weekend on high performance I/O. I looked at differerent
approaches and to me they all appear the same (I know that I will get some
flamage for this). The two most prominent models that I saw were IO
Completion Ports and Synchronous Events (such as the Gaurav
http://www.cs.ric
82 matches
Mail list logo
