Re: Dangling symlink in /usr/compat/linux

2001-02-05 Thread Szilveszter Adam
Hello Doug, Sorry for the belated answer, I hit the hay in the meantime... but now, good morning to everybody outta there:-) On Sun, Feb 04, 2001 at 05:05:11PM -0800, Doug Barton wrote: > Ummm... duh. :) I confirmed this on two machines. OK I think I nailed it:-) I took a trip to the /var

Re: Broken procfs/status, related to kthreads

2001-02-05 Thread Andrzej Bialecki
On Mon, 5 Feb 2001, Bruce Evans wrote: > On Sun, 4 Feb 2001, Andrzej Bialecki wrote: > > > According to procfs(5), the status line contains several well-defined > > fields separated by spaces. However, the kernel thread names look like > > 'swi5: task queue' and 'swi1: net', which results in var

Re: buildkernel target died...

2001-02-05 Thread Doug Barton
John Indra wrote: > > Latest -CURRENT buidkernel died with this error messages: > > ===> sound/driver > ===> sound/driver/ad1816 > rm -f setdef0.c setdef1.c setdefs.h setdef0.o setdef1.o snd_ad1816.ko snd_ad1816.kld >ad1816.o @ machine symb.tmp tmp.o bus_if.h device_if.h isa_if.h pci_if.h ac97_

Re: buildkernel target died...

2001-02-05 Thread John Indra
On Mon, Feb 05, 2001 at 01:30:26AM -0800, Doug Barton wrote: >In order to follow -current you have to follow freebsd-current mailing >list and the commit logs. Cameron recently committed some new stuff, then >committed the makefile for it a little while after. This was all described >on the lists

[a.campi@inet.it: Page fault]

2001-02-05 Thread Andrea Campi
On -CURRENT I get this under different conditions, i.e. sometimes at boot as mentioned a couple of days ago, and today again at pccard extraction. I can provide other info if instructed as to what info you need. ;-) Bye, Andrea Fatal trap 12: page fault while in kernel mode fault virtua

Re: Aironet under NEWCARD

2001-02-05 Thread Andrea Campi
> > Now I'm on to that ich (i810 and 440MX) AC97 audio driver :-) Great news! And please MFC it asap ;-) Seriously, I've been using it on -STABLE for months, if you need volunteers for testing, I can help. Bye, Andrea > > Regards > > Gabriel > > On Sun, Feb 04, 2001 at 02:57:51AM +

od driver for -CURRENT

2001-02-05 Thread Trevor Johnson
I've made an attempt at an update for -CURRENT of Shunsuke Akiyama's od driver for magneto-optical disks, which I got from his archives at ftp://daemon.jp.freebsd.org/pub/FreeBSD-jp/OD/ . I have only tested it a little, but I'm able to do "tar cf /dev/od0 ..." under 4-STABLE and untar under Linux

Re: (KAME-snap 3974) Re: TI-RPC, IPv6 and NFS (was: Re: strong recommendation re: NFS)

2001-02-05 Thread Jean-Luc Richier
Dans votre courrier du 25 Jan 16:49 vous ecrivez : > In your previous mail you wrote: > > It is not impossible to support IPv6 NFS without switching to TI-RPC, > INRIA IPv6 has the code (IIRC). > >=> this code was ported to FreeBSD 4.2. I'll give more details as soon as >I am back t

Re: od driver for -CURRENT

2001-02-05 Thread Trevor Johnson
I was able to do: # mount_msdos /dev/od0 /mnt # newfs_msdos /dev/od0 # cp mozilla-win32-0.7.zip /mnt/ under FreeBSD -CURRENT, then unzip the file under Windows 95 OSR2 with no problems. However, the patched sysinstall still crashes, and neither disklabel nor newfs are w

Re: Broken procfs/status, related to kthreads

2001-02-05 Thread Mikko Tyolajarvi
In local.freebsd.current you write: >On Mon, 5 Feb 2001, Bruce Evans wrote: [...] >> I think procfs never actually implemented this. Program names may >> have spaces in them too. Of course, the line is too hard to parse if >> the first "field" has spaces in it. Only MAXCOMLEN and NAME_MAX >>

Re: Broken procfs/status, related to kthreads

2001-02-05 Thread Adrian Chadd
On Mon, Feb 05, 2001, Andrzej Bialecki wrote: > Ok, then how should this be fixed? > > We could escape the space characters with something: > > swi5:$task$queue 14 0 0 0 -1,-1 noflags 981365276,40 0,0 0,0 nochan 0 0 0,0 - > > and for command name 'my$prog': > > my$$prog 334 1 332 0 -1,-1 nofl

RE: Kernel Panic from Yesterday's CVSup

2001-02-05 Thread John Baldwin
On 05-Feb-01 Crist J. Clark wrote: > I don't recall reports of trouble with recent CURRENT, but my CVSup > from yesterday afternoon is panicing. Before I try too debug this, has > anyone been getting these or knows what I might be missing? > > Boot messages and the panic info are attached. Coul

Re: od driver for -CURRENT

2001-02-05 Thread Bernd Walter
On Mon, Feb 05, 2001 at 09:34:44AM -0500, Trevor Johnson wrote: > I've made an attempt at an update for -CURRENT of Shunsuke Akiyama's od > driver for magneto-optical disks, which I got from his archives at > ftp://daemon.jp.freebsd.org/pub/FreeBSD-jp/OD/ . I have only tested it a > little, but I

Re: od driver for -CURRENT

2001-02-05 Thread Kenneth D. Merry
On Tue, Feb 06, 2001 at 00:15:27 +0100, Bernd Walter wrote: > On Mon, Feb 05, 2001 at 09:34:44AM -0500, Trevor Johnson wrote: > > I've made an attempt at an update for -CURRENT of Shunsuke Akiyama's od > > driver for magneto-optical disks, which I got from his archives at > > ftp://daemon.jp.freeb

Re: Kernel Panic from Yesterday's CVSup

2001-02-05 Thread Jim Bloom
I have seen both a trap 12 and a trap 9 from a Friday Feb. 2 kernel. This is occuring on my laptop (AST Ascentia 810N) which I can't seem to get to create a core dump. Here is a hand transcription of what I see. Mounting root from ufs:/dev/ad0s1a pccard: card inserted, slot 0 pccard: card inser

Re: Kernel Panic from Yesterday's CVSup

2001-02-05 Thread Andrea Campi
Sorry to bother everybody, but did anybody note from my panic trace, that instruction pointer is 0xdeadc0de? Isn't that bad? :-p On Mon, Feb 05, 2001 at 08:27:19PM -0500, Jim Bloom wrote: > I have seen both a trap 12 and a trap 9 from a Friday Feb. 2 kernel. This is > occuring on my laptop (AST

Strange fopen() behaviour (was: xsane patch to maintainer)

2001-02-05 Thread Brian Somers
> Hi, > > Would you mind if I commit the attached patch for the xsane port ? > It makes sense - rather than dropping a core when fopen() fails (and > fclose() is called with a NULL arg). It happens when your home > directory isn't writable :-/ I've cc'd -current as I think something more si

Re: Strange fopen() behaviour

2001-02-05 Thread Brian Somers
> I've cc'd -current as I think something more sinister is going on. > To recap, I'm having trouble running xsane on -current from about two > days ago. fopen() is failing... > > The attached patch exposes more about what's wrong. Interestingly > enough, the file it's trying to create is in

Re: Strange fopen() behaviour (was: xsane patch to maintainer)

2001-02-05 Thread Andrea Campi
> lstat("/tmp//preview-level-0-15-b924dc",0xbfbfe894) ERR#2 'No such file or directory' ^^ surely this is not nice!! My guess is that the double slash is confusing everything... Anyway, I'm more interested in below: > @@ -2830,9 +2831,17 @@ > if (preview_make_image_path(p, siz

Re: Kernel Panic from Yesterday's CVSup

2001-02-05 Thread John Baldwin
On 06-Feb-01 Jim Bloom wrote: > I have seen both a trap 12 and a trap 9 from a Friday Feb. 2 kernel. This is > occuring on my laptop (AST Ascentia 810N) which I can't seem to get to create > a > core dump. Here is a hand transcription of what I see. > > Mounting root from ufs:/dev/ad0s1a > pcc

Re: Kernel Panic from Yesterday's CVSup

2001-02-05 Thread John Baldwin
On 06-Feb-01 Andrea Campi wrote: > Sorry to bother everybody, but did anybody note from my panic trace, > that instruction pointer is 0xdeadc0de? Isn't that bad? :-p That means it is free'd memory. One cause might be something that is free'ing its interrupt handler w/o releasing it properly. A

md, current and stable

2001-02-05 Thread Chris Knight
Howdy, Since the new md was introduced, it is not possible to build a -current snapshot on a -stable box. Are there any plans to MFC this soon? Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web

Re: Kernel Panic from Yesterday's CVSup

2001-02-05 Thread Mark Murray
John Baldwin said: > On 06-Feb-01 Andrea Campi wrote: > > > Sorry to bother everybody, but did anybody note from my panic trace, > > that instruction pointer is 0xdeadc0de? Isn't that bad? :-p > > That means it is free'd memory. One cause might be something > that is free'ing its interrupt handl

Re: od driver for -CURRENT

2001-02-05 Thread non
From: "Kenneth D. Merry" <[EMAIL PROTECTED]> Date: Mon, 5 Feb 2001 17:00:41 -0700 > I think we already have the most important functionality from the od(4) > driver in the da and cd drivers. If there are any features that are > in the od(4) driver that should be in the da(4) or cd(4) drivers, but