I once searched (in vain) for a way not to miss important thnigs in
UPDATING files. If anyone is interested, he(she) can now use my
home-grown rss 2.0 feeds. They are synced to CVS once a day.
This one for the Ports:
http://kapranoff.ru/~kappa/files/ports.UPDATING.rss20.xml
And this for RELENG_5
On Thu, Jun 23, 2005 at 01:57:32PM +0400, Alex Kapranoff wrote:
> I once searched (in vain) for a way not to miss important thnigs in
> UPDATING files. If anyone is interested, he(she) can now use my
> home-grown rss 2.0 feeds. They are synced to CVS once a day.
>
> This one for the Ports:
> http:
Edwin Groothuis wrote:
> On Thu, Jun 23, 2005 at 01:57:32PM +0400, Alex Kapranoff wrote:
>
>>I once searched (in vain) for a way not to miss important thnigs in
>>UPDATING files. If anyone is interested, he(she) can now use my
>>home-grown rss 2.0 feeds. They are synced to CVS once a day.
>>
>>Thi
On Wed, Jun 22, 2005 at 03:03:53PM +0200, Andre Oppermann wrote:
A> > Fixing this one is harder. We take la from unlocked rtentry obtained via
A> > rt_check(), or from arplookup(). The latter drops lock on rtentry, too.
A> > Then we do some work and use this la. It may have already been freed in
A>
Gleb,
> What about fixing it step by step? The patch attached to my previous message
> fixes the panic report by Jeremie, I suppose. It is race between output
> path and input path, that can occur anytime in runtime.
FYI, I compiled my kernel with your patch and I have had no panic since
then. N
On 5/27/05, Dick Davies <[EMAIL PROTECTED]> wrote:
> * Kirk Strauser <[EMAIL PROTECTED]> [0538 15:38]:
> > On Friday 27 May 2005 08:05, Dean Strik wrote:
> >
> > > I just filed PR 81555 about this. For me, it appears that cron(8) exits
> > > after a SIGPIPE when an LDAP-user does a crontab -e. Are
On Thursday 23 June 2005 04:57, Alex Kapranoff wrote:
> If anyone is interested, he(she) can now use my home-grown rss 2.0 feeds.
> They are synced to CVS once a day.
Thank you, thank you, thank you! That's an excellent idea, and pretty
obvious in retrospect.
--
Kirk Strauser
pgpEI8PAtNM3S.
Hi,
I have already installed FreeBSD 5.4 in lots of hardware, but now I
came to one that is troublig me.
It an ASUS motherboard, model P4VP-MX, with VIA8235 Chipset.
Neither the FreeBSD 5.4-RELEASE CD, nor a preinstalled hard disk can
identify the ATA disks in this computer. During
Joao Carlos Mendes Luis <[EMAIL PROTECTED]> writes:
>kernel sends some messages, "ata0-master: failure - ATA_IDENTIFY timed
>out", "ata0-master: failure - ATA_IDENTIFY timed out", and them no hard
>disk is identified, so I cannot install the system. If I boot from a
>pre-installed hard disk, i
Jonny,
When I started using FreeBSD a month or so ago I experienced the same
problem. The only workable solution
for me was to use 4.11. I corresponded with Søren Schmidt about this,
but he could find no reason for this
occurrence.
If anyone can suggest a test for me to run to gather data f
Matthias Buelow wrote:
Joao Carlos Mendes Luis <[EMAIL PROTECTED]> writes:
kernel sends some messages, "ata0-master: failure - ATA_IDENTIFY timed
out", "ata0-master: failure - ATA_IDENTIFY timed out", and them no hard
disk is identified, so I cannot install the system. If I boot from a
pre-
On 6/23/05, Matthias Buelow <[EMAIL PROTECTED]> wrote:
> Joao Carlos Mendes Luis <[EMAIL PROTECTED]> writes:
>
> >kernel sends some messages, "ata0-master: failure - ATA_IDENTIFY timed
> >out", "ata0-master: failure - ATA_IDENTIFY timed out", and them no hard
> >disk is identified, so I cannot ins
Hello,
I have driver disk for the Windows 98/Me/2000/XP of the Buffalo
WLI-PCI-G54 wireless NIC.
If possible I want to know "ndiscvt" command convert Windows driver
to FreeBSD driver module.
I don't know which version of Windows driver files need to convert to
FreeBSD driver module and how to co
libc.so.4 => /usr/lib/libc.so.4 (0x28755000)
libc_r.so.4 => /usr/lib/libc_r.so.4 (0x287ee000)
any ideas why it's doing this, and what the fix is?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-s
In the last episode (Jun 23), Kevin S. Brackett said:
> libc.so.4 => /usr/lib/libc.so.4 (0x28755000)
> libc_r.so.4 => /usr/lib/libc_r.so.4 (0x287ee000)
>
> any ideas why it's doing this, and what the fix is?
Looks fine to me:
libc.so.5 => /lib/libc.so.5 (0x2875c000)
l
On Thu, 23 Jun 2005, Dan Nelson wrote:
In the last episode (Jun 23), Kevin S. Brackett said:
libc.so.4 => /usr/lib/libc.so.4 (0x28755000)
libc_r.so.4 => /usr/lib/libc_r.so.4 (0x287ee000)
any ideas why it's doing this, and what the fix is?
Looks fine to me:
libc.so.5 => /l
On Fri, 24 Jun 2005, Kevin S. Brackett wrote:
>
> Well, the problem is when libc and libc_r are linked together, I
> recompiled without -lc and it's now fine, but not really what i'd consider
> a great fix...
I suggest you go do some research -- look in our archives and
man pages. libc is linked
Hi-diddly-ho!
Is VFS_BIO_DEBUG still supposed to work in 4.11? I'm trying to debug a
data corruption problem that could be a bug in the cd9660 file system and
thought that enabling VFS_BIO_DEBUG might help. Instead it complains a
lot about directories and character devices being VMIO'd nowadays,
Hi,
thank you, whoever fixed it and whatever it was, but -STABLE is
stable again for me. The ATA DMA timeouts have disappeared with
yesterdays kernel.
Looking at the CVS tree, I notice that there weren't many
changes to the ATA code before the problems appeared and
also when it has been fixed.
19 matches
Mail list logo
