On Sat, Jul 18, 2009 at 12:57:57AM -0700, per...@pluto.rain.com wrote:
I suspect the real concern is not that the upgrade itself will
wreck something, but that the upgraded FF may do something odd
the first time it is fired up :(
That's a pretty good guess.
One hopes that backing up
Chad Perrin wrote:
On Sat, Jul 18, 2009 at 12:57:57AM -0700, per...@pluto.rain.com wrote:
I suspect the real concern is not that the upgrade itself will
wreck something, but that the upgraded FF may do something odd
the first time it is fired up :(
That's a pretty good guess.
On Sat, Jul 18, 2009 at 07:02:01PM +0200, Frank Steinborn wrote:
Chad Perrin wrote:
Unfortunately, I haven't gotten far enough to see if anything was lost,
because now Firefox 3.5.x won't start:
Fatal error 'Recurse on a private mutex.' at line 986 in file
Chad Perrin wrote:
On Sat, Jul 18, 2009 at 07:02:01PM +0200, Frank Steinborn wrote:
Chad Perrin wrote:
Unfortunately, I haven't gotten far enough to see if anything was lost,
because now Firefox 3.5.x won't start:
Fatal error 'Recurse on a private mutex.' at line 986 in
On Sat, Jul 18, 2009 at 07:17:53PM +0200, Frank Steinborn wrote:
Chad Perrin wrote:
Okay -- where do I get the sem kernel module?
It is included in FreeBSD, just type 'kldload sem' to load it. If you
want to have loaded it automatically on boot, add the following to
your
Chad Perrin wrote:
On Sat, Jul 18, 2009 at 07:17:53PM +0200, Frank Steinborn wrote:
Chad Perrin wrote:
Okay -- where do I get the sem kernel module?
It is included in FreeBSD, just type 'kldload sem' to load it. If you
want to have loaded it automatically on boot, add the
On Sat, Jul 18, 2009 at 07:28:41PM +0200, Frank Steinborn wrote:
Chad Perrin wrote:
# kldload sem
kldload: can't load sem: No such file or directory
# locate sem.ko
/boot/kernel/sysvsem.ko
/boot/kernel.GENERIC/sysvsem.ko
Chad Perrin wrote:
On Sat, Jul 18, 2009 at 07:28:41PM +0200, Frank Steinborn wrote:
Chad Perrin wrote:
# kldload sem
kldload: can't load sem: No such file or directory
# locate sem.ko
/boot/kernel/sysvsem.ko
/boot/kernel.GENERIC/sysvsem.ko
On Sat, Jul 18, 2009 at 07:48:27PM +0200, Frank Steinborn wrote:
Now this is strange... it should be available. See the sem(4) manpage.
No idea how to help from this point except to advice you to rebuild
your kernel and see if the module becomes available. It is definitely
needed for running
Chad Perrin wrote:
On Sat, Jul 18, 2009 at 07:48:27PM +0200, Frank Steinborn wrote:
Now this is strange... it should be available. See the sem(4) manpage.
No idea how to help from this point except to advice you to rebuild
your kernel and see if the module becomes available. It is
On Sat, Jul 18, 2009 at 07:53:58PM +0200, Frank Steinborn wrote:
Chad Perrin wrote:
On Sat, Jul 18, 2009 at 07:48:27PM +0200, Frank Steinborn wrote:
Now this is strange... it should be available. See the sem(4) manpage.
No idea how to help from this point except to advice you to
Chad Perrin wrote:
On Sat, Jul 18, 2009 at 07:53:58PM +0200, Frank Steinborn wrote:
Chad Perrin wrote:
On Sat, Jul 18, 2009 at 07:48:27PM +0200, Frank Steinborn wrote:
Now this is strange... it should be available. See the sem(4) manpage.
No idea how to help from this point
On Sat, Jul 18, 2009 at 08:06:58PM +0200, Frank Steinborn wrote:
Ok, now this seems to be a problem with libpthread-stuff. The problem
only exists in 6.x. Sorry that I did not mention that earlier, but it
just crossed my mind right now... However, someone is working at it.
He also mentions
Chad Perrin wrote:
I seem to have unsubscribed from freebsd-ports@ a while ago, so I can't
just respond in-thread to the www/firefox35 coredumps discussion there.
Would it be better for me to start a new thread on freebsd-ports@ rather
than continue discussing it here?
I would recommend
14 matches
Mail list logo
