> bug in the RealTek driver in 4.0 that crashes the system (more info on that in
> PR kern/17582), this is probably what you are seeing. You should either
> upgrade the driver or upgrade the whole system to 4.0.
Oops, that should of course
On Friday, July 28, 2000, Bjorn Tornqvist wrote:
> 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. PO
Howdy all,
I must have missed something very importand w.r.t threads under FreeBSD,
here's what I've come up with during the last week:
PosixThreads are userland threads - if one thread blocks on i/o the
whole process is blocked. Which makes PosixThreads rather useless.
FreeBSD Kernel-threads (
L.S.
Update on previous mail a while back. I tried the latest sym driver from
the CVS tree (into fbsd 3.3) but little has changed (haven't checked
what happens with 640MB 2048 b/s disks yet):
> 4. Formatting ufs on fbsd:
> newfs hangs (unkillable).
This now works.
> 3. ufs disk formatted on ob
Yes.. the problems were fixed a few months ago.
paul
Jim Flowers ([EMAIL PROTECTED]) wrote:
>
> I noticed in cvsuping RELENG_4 day before yesterday it came back as
> 4.1-RC. Does that also address the network stack panics?
>
> Jim Flowers <[EMAIL PROTECTED]>
> #4 ranked ISP on C|NET #1 in Oh
I noticed in cvsuping RELENG_4 day before yesterday it came back as
4.1-RC. Does that also address the network stack panics?
Jim Flowers <[EMAIL PROTECTED]>
#4 ranked ISP on C|NET #1 in Ohio
On Thu, 27 Jul 2000, Paul Saab wrote:
> There are known panics in the network stack in 4.0-RELEASE.
At 06:47 PM 7/27/00 -0500, Kim Shrier wrote:
>If I understand your question correctly, all you need to do to set up
>a ptp ethernet link is:
>
>ifconfig fxp0 inet 200.1.1.1 200.1.1.2
It *seems* like that should work, but it doesnt.
When ping from one machine to another, the receiver doesnt respo
If I understand your question correctly, all you need to do to set up
a ptp ethernet link is:
ifconfig fxp0 inet 200.1.1.1 200.1.1.2
Dennis wrote:
>
> Is it possible to have only one address on an ethernet network? the only
> way that I can get it to work is with:
>
> ifconfig fxp0 200.1.1.1
Is it possible to have only one address on an ethernet network? the only
way that I can get it to work is with:
ifconfig fxp0 200.1.1.1 netmask 255.255.255.255
route add fxp0 200.1.1.2 -interface fxp0
arp -s 200.1.1.2 ether-address
Is there a way to get such a setup to work dynamically with AR
According to Julian Stacey:
> just as today I'd use an encrypting file system on my new laptop,
> but such file system don't exist on FreeBSD unfortunately.
Ahem. Why did I sent an update for security/cfs to green a few months ago? :-)
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMA
* Jim Flowers <[EMAIL PROTECTED]> [000727 14:35] wrote:
> We have been using fbsd 4.0-RELEASE on a number of router applications
> (IPV4). Recently we have switched to new hardware and now we get fatal
> faults periodically.
>
> Typically these run with a minimum kernal using ipfw and natd and n
On Thu, 27 Jul 2000, Doug White wrote:
> On Wed, 26 Jul 2000, [Windows-1252] Nicolas Léonard wrote:
>
> > I'm trying to use the new kqueue()/kevent() syscalls in the last
> > snapshot of FreeBSD 5.0.
> > It works perfectly, except when I'm trying to use it in a multi-
> > threaded program.
> > T
> Does this indicate that my new hardware is probably not going to work with
> fbsd 4.0?
[snip]
> rl0: port 0xde00-0xdeff mem
[snip]
I notice that you use a RealTek card in your router. First of all, there is a
bug in the RealTek driver in 4.0 that crashes the system (more info on that in
PR ker
There are known panics in the network stack in 4.0-RELEASE. You should
really upgrade to 4.1-RELEASE.
paul
Jim Flowers ([EMAIL PROTECTED]) wrote:
> We have been using fbsd 4.0-RELEASE on a number of router applications
> (IPV4). Recently we have switched to new hardware and now we get fatal
>
We have been using fbsd 4.0-RELEASE on a number of router applications
(IPV4). Recently we have switched to new hardware and now we get fatal
faults periodically.
Typically these run with a minimum kernal using ipfw and natd and not much
more. 32 MB memory.
Does this indicate that my new hardw
On Wed, 26 Jul 2000, [Windows-1252] Nicolas Léonard wrote:
> I'm trying to use the new kqueue()/kevent() syscalls in the last
> snapshot of FreeBSD 5.0.
> It works perfectly, except when I'm trying to use it in a multi-
> threaded program.
> The call of kevent() by my network thread blocks the o
On Wed, 26 Jul 2000, Isaac Waldron wrote:
> I started working on a port of FreeMWare/plex86 (www.plex86.org) to FreeBSD
> yesterday, and have run into a small problem. The basic idea is that I need
> to write a kernel module that implements some ioctls for a new psuedo-device
> that will eventua
[ copying -doc because I've got a doc patch for the FAQ ... perhaps :) ]
[ On Thursday, July 27, John Baldwin wrote: ]
>
> Umm, well. First off, disklabel -B doesn't fix your MBR. fdisk does that,
> or boot0cfg if you are using boot0 to dual-boot. However, can you type
Hmmm. Must have just
"Andrew Reilly" wrote:
> Well, even if there are/were folk who want tiny disk footprints,
> and crunching everything isn't going to do the whole job, wouldn't
> a compressed filesystem be a better way to approach this? At least
> that way you'd still be able to page from the executable(s), and
>
I have a temporal solution on running CMI8330 sundcard
under FreeBSD 4.0-RELEASE. Everybody having troubles
with this soundcard, send me email and i'll send em
the patch. I'm working in the moment on making the
solution completely working and I'll release it soon.
Atanas Bachvaroff, BGR, [EMAIL
John Reynolds wrote:
>
> Hello all ... hope this is the right group for this
Umm, well. First off, disklabel -B doesn't fix your MBR. fdisk does that,
or boot0cfg if you are using boot0 to dual-boot. However, can you type
disklabel ad0 now and get useful information? Or disklabel ad0sX
Hello
I'm trying to use the new kqueue()/kevent() syscalls in the last
snapshot of FreeBSD 5.0.
It works perfectly, except when I'm trying to use it in a multi-
threaded program.
The call of kevent() by my network thread blocks the other thread.
I look in the libc_r sources and I found that thi
Dimitar Peikov wrote:
>
> Hi, hackers,
>
> I've try to use mmap() and resize the mapping. msync() syncronizes
> only the memory that was mmapped with mmap(). How can I extend the
> main file? Memory is filled correctly, but I must write extended data
> to file by hand.
You need to ext
Hi, hackers,
I've try to use mmap() and resize the mapping. msync() syncronizes only the
memory that was mmapped with mmap(). How can I extend the main file? Memory is
filled correctly, but I must write extended data to file by hand.
In my examples 'x.txt' was 11 bytes (some text); Where I'm wro
On Wed, 26 Jul 2000, Julian Stacey wrote:
> That laptop has now gone to 4.0, & aout to elf, & a 1.5G disc, so no
> incentive to do it all again to see how much FreeBSD-4 gzipped aout
> binary tree might save/waste on a whole tree. BTW I was `strip'ing
gzexe(1) is your friend :-)
Kris
--
In Go
Hello all ... hope this is the right group for this
Last night I had to re-install win98 on my IDE drive (dual-boot) and it happily
clobbered my mbr. No problem. I've had this happen before. I booted up 4.0 from
my CDs and chose the "Fixit" option from the CD-ROM.
I tried:
disklabel -B
26 matches
Mail list logo