Hello,
added to kernel config:
device iic
device iicbus
device ic
and these in case:
device iicsmb
device iicbb
device smbus
device smb
I made and installed world and kernel last night from freshly cvsupped source.
grepping dmesg
Hello.
After running this program with msdosfs mounted in /mnt, I got a
file with some garbage in skipped space. Is it a bug in my local
installation/hardware or real kernel bug?
FreeBSD xen.infosec.ru 4.8-RELEASE FreeBSD 4.8-RELEASE #0: Thu Apr 17
16:53:27 MSD 2003 [EMAIL PROTECTED]:/usr/sr
On Wed, 2 Jul 2003, David Schultz wrote:
> On Tue, Jul 01, 2003, Marc G. Fournier wrote:
> [...]
> > and I have a vmcore to work on here !! :)
>
> Yes, this does look promising. Can you look at
> *(struct lock *)0x8a4ef300 (the lock the second
> process is trying to acquire) also?
(kgdb) print *
On Wed, 2003-07-02 at 19:56, Oldach, Helge wrote:
> From: Mike Tancsa [mailto:[EMAIL PROTECTED]
> > Any chance someone can look at / commit the fix in PR 52349 before 4.9R ?
> > Its a simple fix.
>
> But unfortunately it breaks code that parses the output of netstat and
> relies on a fixed format,
On Tue, Jul 01, 2003 at 11:50:44AM -0500, Rick Flosi wrote:
> I used KUser to add a user to my system and after saving the changes I
> made KUser expired all user accounts except the newly created one.
> Does anyone know if there is a patch for KUser to fix this problem. I
> found some discussi
Oldach, Helge said:
>
> But unfortunately it breaks code that parses the output of netstat and
> relies on a fixed format, for instance phpsysinfo. I would suggest to
> re-work the patch and turn "vlan10" into "vla10" to maintain the existing
> format.
Although phpsysinfo is broken on freebsd 5.x
From: Mike Tancsa [mailto:[EMAIL PROTECTED]
> Any chance someone can look at / commit the fix in PR 52349 before 4.9R ?
> Its a simple fix.
But unfortunately it breaks code that parses the output of netstat and
relies on a fixed format, for instance phpsysinfo. I would suggest to
re-work the patch
On Tue, Jul 01, 2003, Marc G. Fournier wrote:
[...]
> and I have a vmcore to work on here !! :)
Yes, this does look promising. Can you look at
*(struct lock *)0x8a4ef300 (the lock the second
process is trying to acquire) also? It probably
points back to the first process, but we might as
well be
