Date: Wed, 12 Apr 2000 14:26:23 -0700 From: Marcel Moolenaar <marcel@cup.hp.com> To: "Louis A. Mamakos" <louie@TransSys.COM> Cc: Vivek Khera <khera@kciLink.com>, stable@FreeBSD.ORG Subject: Re: Acroread4 Message-ID: <38F4E9FF.CB73FD55@cup.hp.com> References: <Pine.BSF.4.21.0003271521050.30367-100000@palamas.noc.uoa.gr> <200003271358.FAA02567@cwsys.cwsent.com> <20000412090055.L64452@daemon.ninth-circle.org> <14580.35404.952873.461147@onceler.kcilink.com> <200004121844.OAA30389@whizzo.transsys.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Louis A. Mamakos" wrote: > > > >>>>> "A" == Asmodai <Jeroen> writes: > > > > >> I don't think this is a 4.0 issue. I get the same on a couple of 3.4R > > >> systems, minus the locale message. > > > > A> I can, on my 3.4-STABLE, get acroread4 to coredump time and again. > > > > I've never had acroread version 4 croak on my 3.4-STABLE system. It > > works just perfectly fine. > > I had this weird problem with acroread4 when the file being opened was > in an interesting place. That is, in /home/louie/foo.pdf, where /home/louie > was an amd mount. The same file in, say, /tmp would work fine. I > never pursued this, and don't know if that problem is related to the > one being discussed. I think that is a different problem. In your case it may be related to the mapping problem of device numbers between FreeBSD and Linux. Linux only has 16 bit device numbers (8 bit major; 8 bit minor). We have 32 bit device numbers (8 bit major; 24 bit minor). This problem most frequently pops up with NFS mounts. -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38F4E9FF.CB73FD55>