On Sun, May 05, 2002 at 04:36:41AM +0200, Dag-Erling Smorgrav wrote:
modules and doesn't clobber your old 4.x modules. I asked David to
put libpam and the PAM modules in COMPAT4X, but never heard back from
him.
I guess I need clarification. Since PAM modules aren't versioned, is
there a
On Sat, May 04, 2002 at 11:16:22PM -0700, Doug Barton wrote:
Ok, I put the following in /usr/lib/compat, from my releng_4 box:
libc.so.4
libc_r.a
libc_r.so.4
libpam.a
libpam.so.1
libpam_ssh.a
There is no need for .a's in /usr/lib/compat -- think about it.
To Unsubscribe: send mail to
On Sat, 4 May 2002, David O'Brien wrote:
On Sat, May 04, 2002 at 11:16:22PM -0700, Doug Barton wrote:
Ok, I put the following in /usr/lib/compat, from my releng_4 box:
libc.so.4
libc_r.a
libc_r.so.4
libpam.a
libpam.so.1
libpam_ssh.a
There is no need for .a's in /usr/lib/compat
On Sat, May 04, 2002 at 07:49:50AM -0700, Maxim Sobolev wrote:
sobomax 2002/05/04 07:49:50 PDT
Modified files:
usr.sbin/pkg_install/info info.h main.c perform.c pkg_info.1
show.c
usr.sbin/pkg_install/lib lib.h plist.c
Log:
Add ability to
Hi all,
The problem must have been introduced after April, 3.
I've a kernel.old from this date which runs perfectly.
Maybe this can help to track the bug down.
Martin
Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED]
--
ImproWare
Hi,
I have to take back that a kernel from april 3. runs fine.
It happens there too, but few times than on recent current.
The build lives for 5 minutes, instead of 30 seconds. Then
I get a SIG4 as usual and cc crashes.
Anybody has a idea to which date I can switch back to
have my problem
Doug Barton [EMAIL PROTECTED] writes:
unable to dlopen(/usr/lib/pam_nologin.so)
[dlerror: Cannot open /usr/lib/pam_nologin.so]
adding faulty module: /usr/lib/pam_nologin.so
unable to dlopen(/usr/lib/pam_opieaccess.so)
[dlerror: Cannot open /usr/lib/pam_opieaccess.so]
adding faulty
Hmm, really strange. I can't reproduce it here. Are you sure that you have
recompiled all of pkg_install, i.e. both libraries and utilities?
-Maxim
--zYM0uCDKw75PZbzx
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On
-On [20020504 20:15], Jeroen Ruigrok/asmodai ([EMAIL PROTECTED]) wrote:
It is only here that warnings are treated as errors.
I am thinking something in the upgrade path is not 100% thought out, trying
to see what exactly, but my focus has been way more on STABLE than CURRENT,
so some more exposed
OOPS, sorry, should be fixed now. Mea culpa.
-Maxim
Hmm, really strange. I can't reproduce it here. Are you sure that you have
recompiled all of pkg_install, i.e. both libraries and utilities?
-Maxim
--zYM0uCDKw75PZbzx
Content-Type: text/plain; charset=us-ascii
Hello,
src/sbin/savecore.c has been broken today, with the commit of rev 1.59
by Bill Fenner.
It appears that a new magic value, KERNELDUMPMAGIC_CLEARED, has been
introduced but its value never #define-d in (probably)
src/sys/sys/kerneldump.h. This way, the program does not compile.
There is
Szilveszter Adam wrote:
Hello,
src/sbin/savecore.c has been broken today, with the commit of rev 1.59
by Bill Fenner.
This is fixed in revision 1.4 of src/sys/sys/kerneldump.h.
Cheers,
Maxime
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of
On 15:17+0200, May 5, 2002, Szilveszter Adam wrote:
Hello,
src/sbin/savecore.c has been broken today, with the commit of rev 1.59
by Bill Fenner.
It appears that a new magic value, KERNELDUMPMAGIC_CLEARED, has been
introduced but its value never #define-d in (probably)
I'm running current cvsupped two days ago. This time my X broke
down. It don't accept anything from keyboard. Situation is same when
using xdm or startx. I think last working world build was done two
weeks ago. XFree86-4.2.0 was built 30.3.2002 and I already tried to
built X-server from
Warning
Unable to process data:
multipart/mixed;boundary==_NextPart_000_00B7_16C07C6E.A3114E54
I've got a Seimens SpeedStream USB - Ethernet adapter that when I plug
into my laptop (built -CURRENT yesterday), it always crashes. Here's the
info:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xdeadc0e2
fault code = supervisor read, page not present
On Sun, 5 May 2002, Gordon Tetlow wrote:
I've got a Seimens SpeedStream USB - Ethernet adapter that when I plug
into my laptop (built -CURRENT yesterday), it always crashes. Here's the
info:
snip...
Of course, after a quick search, I find the thread that Joe has about the
usb subsystem.
With yesterday's -current:
lock order reversal
1st 0xcc5987a4 DIRHASH (UMA zone) @
/usr/Local/src-current/sys/vm/uma_core.c:297
2nd 0xc76c2224 PCPU 256 (UMA cpu) @
/usr/Local/src-current/sys/vm/uma_core.c:1630
FYI.
--
We have known freedom's price. We have shown freedom's power.
On Sun, 5 May 2002, Doug Barton wrote:
With yesterday's -current:
lock order reversal
1st 0xcc5987a4 DIRHASH (UMA zone) @
/usr/Local/src-current/sys/vm/uma_core.c:297
2nd 0xc76c2224 PCPU 256 (UMA cpu) @
/usr/Local/src-current/sys/vm/uma_core.c:1630
FYI.
Here's another from
On Sun, May 05, 2002 at 02:42:22PM +0200, Jeroen Ruigrok/asmodai wrote:
I definately do not call libiberty kernel related.
Nor do we, by default, advocate NO_WERROR. So in effect, we broke moving
from older versions to newer versions of CURRENT.
Can you track down what the actual cause of
On Sun, 5 May 2002, Doug Barton wrote:
With yesterday's -current:
lock order reversal
1st 0xcc5987a4 DIRHASH (UMA zone) @
/usr/Local/src-current/sys/vm/uma_core.c:297
2nd 0xc76c2224 PCPU 256 (UMA cpu) @
/usr/Local/src-current/sys/vm/uma_core.c:1630
I see the same one when I run
-On [20020506 00:30], Kris Kennaway ([EMAIL PROTECTED]) wrote:
On Sun, May 05, 2002 at 02:42:22PM +0200, Jeroen Ruigrok/asmodai wrote:
I definately do not call libiberty kernel related.
Nor do we, by default, advocate NO_WERROR. So in effect, we broke moving
from older versions to newer
On Mon, May 06, 2002 at 07:31:30AM +0200, Jeroen Ruigrok/asmodai wrote:
-On [20020506 00:30], Kris Kennaway ([EMAIL PROTECTED]) wrote:
On Sun, May 05, 2002 at 02:42:22PM +0200, Jeroen Ruigrok/asmodai wrote:
I definately do not call libiberty kernel related.
Nor do we, by default, advocate
On 5 May 2002, Dag-Erling Smorgrav wrote:
Doug Barton [EMAIL PROTECTED] writes:
unable to dlopen(/usr/lib/pam_nologin.so)
[dlerror: Cannot open /usr/lib/pam_nologin.so]
adding faulty module: /usr/lib/pam_nologin.so
unable to dlopen(/usr/lib/pam_opieaccess.so)
[dlerror: Cannot
24 matches
Mail list logo
