Re: panic at shutdown
And Bill Fumerola spoke:
> On Mon, Jul 31, 2000 at 10:37:48PM -0700, R Joseph Wright wrote:
> > I just built a new world/kernel yesterday, and now I get a panic when I shut
> > down. I ran gdb on the dump:
> >
> > ..
> > There is absolutely no warranty for GDB. Type "show warranty" for details.
> > This GDB was configured as "i386-unknown-freebsd"...
> > IdlePTD 2998272
> > initial pcb at 25b1c0
> > panicstr: lockmgr: pid 1, not exclusive lock holder 0 unlocking
> > panic messages:
> > ---
> > ---
> > #0 boot (howto=256) at ../../kern/kern_shutdown.c:303
> > 303 dumppcb.pcb_cr3 = rcr3();
>
> type 'bt', this tells us just about as much as if you said
> "it crashed".
>
> though, by the panic message, this seems to be a known bug..
>
> --
> Bill Fumerola - Network Architect, BOFH / Chimes, Inc.
> [EMAIL PROTECTED] / [EMAIL PROTECTED]
Sorry :)
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
IdlePTD 2998272
initial pcb at 25b1c0
panicstr: lockmgr: pid 1, not exclusive lock holder 0 unlocking
panic messages:
---
---
#0 boot (howto=256) at ../../kern/kern_shutdown.c:303
303 dumppcb.pcb_cr3 = rcr3();
(kgdb) bt
#0 boot (howto=256) at ../../kern/kern_shutdown.c:303
#1 0xc014bd28 in poweroff_wait (junk=0xc02010a0, howto=1)
at ../../kern/kern_shutdown.c:553
#2 0xc0146af0 in lockmgr (lkp=0xc0c50a00, flags=6, interlkp=0xc87108ac,
p=0xc7d4be00) at ../../kern/kern_lock.c:382
#3 0xc01779ab in vop_stdunlock (ap=0xc7d51e48) at ../../kern/vfs_default.c:255
#4 0xc01b6ccd in ufs_vnoperate (ap=0xc7d51e48)
at ../../ufs/ufs/ufs_vnops.c:2301
#5 0xc01b1bab in ufs_inactive (ap=0xc7d51e78) at vnode_if.h:865
#6 0xc01b6ccd in ufs_vnoperate (ap=0xc7d51e78)
at ../../ufs/ufs/ufs_vnops.c:2301
#7 0xc017a726 in vput (vp=0xc8710840) at vnode_if.h:794
#8 0xc01aee87 in ffs_sync (mp=0xc0ade800, waitfor=2, cred=0xc0721700,
p=0xc026d5e0) at ../../ufs/ffs/ffs_vfsops.c:955
#9 0xc017c605 in sync (p=0xc026d5e0, uap=0x0) at ../../kern/vfs_syscalls.c:551
#10 0xc014b777 in boot (howto=0) at ../../kern/kern_shutdown.c:225
#11 0xc014b578 in reboot (p=0xc7d4be00, uap=0xc7d51f80)
at ../../kern/kern_shutdown.c:146
#12 0xc01ecd21 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
tf_edi = -1077936612, tf_esi = -1077936624, tf_ebp = -1077936836,
tf_isp = -942333996, tf_ebx = -1077936732, tf_edx = -1, tf_ecx = 4,
tf_eax = 55, tf_trapno = 7, tf_err = 2, tf_eip = 134536452, tf_cs = 31,
tf_eflags = 643, tf_esp = -1077937056, tf_ss = 47})
at ../../i386/i386/trap.c:1128
#13 0xc01e1ab5 in Xint0x80_syscall ()
#14 0x80486ee in ?? ()
#15 0x8048478 in ?? ()
#16 0x8048139 in ?? ()
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: panic at shutdown
On Mon, Jul 31, 2000 at 10:37:48PM -0700, R Joseph Wright wrote: > I just built a new world/kernel yesterday, and now I get a panic when I shut > down. I ran gdb on the dump: > > .. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-unknown-freebsd"... > IdlePTD 2998272 > initial pcb at 25b1c0 > panicstr: lockmgr: pid 1, not exclusive lock holder 0 unlocking > panic messages: > --- > --- > #0 boot (howto=256) at ../../kern/kern_shutdown.c:303 > 303 dumppcb.pcb_cr3 = rcr3(); type 'bt', this tells us just about as much as if you said "it crashed". though, by the panic message, this seems to be a known bug.. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
panic at shutdown
I just built a new world/kernel yesterday, and now I get a panic when I shut down. I ran gdb on the dump: .. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 2998272 initial pcb at 25b1c0 panicstr: lockmgr: pid 1, not exclusive lock holder 0 unlocking panic messages: --- --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:303 303 dumppcb.pcb_cr3 = rcr3(); To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sendmail 8.11.0 trouble
On Tue, 1 Aug 2000, Leif Neland wrote: > > > On Sun, 30 Jul 2000, Garrett Wollman wrote: > > > < said: > > > > >> On Sunday, July 30, 2000, Leif Neland wrote: > > > > >> > Sendmail 8.11.0 > > >> > > > >> > When invoking sendmail or newaliases I get this message: > > >> > /etc/pwd.db: Invalid argument > > >> > > > >> > Sendmail can't read /etc/pwd.db, and therefore cannot deliver any local > > >> > mail. > > >> > > > >> > Howtofixitplease? > > > > Sounds like you're using the wrong version of Berkeley DB (i.e., not > > the one in libc). Can't fathom how this could override the internal > > linkage in libc, though. > > > > There seems indeed to be a confusion of the .db's: > /etc/mail/aliases.db: MS Windows COFF Unknown CPU > /etc/pwd.db: Berkeley DB Hash file (Version 2, Little Endian, Bucket Size 4096, >Bucket Shift 12, Directory Size 256, Segment Size 256, Segment Shift 8, Overflow >Point 3, Last Freed 2, Max Bucket 7, High Mask 0xf, Low Mask 0x7, Fill Factor 32, >Number of Keys 52) > > Sendmail compiles with -DNEWDB > > I had db 2.something installed from the ports. I uninstalled it, it made > no difference. > I compile in /usr/src/sendmail-8.11.0 I nfs-mounted /usr/src and /usr/obj to an a little older current (like when I do a make installworld to the older machine) I then compiled the same sourcedir with the same options, but now I got a sendmail binary, which understands Berkley DB Hash file (version 2). Then I could "./Build install" a working sendmail on the original machine. Something on the original machine must trigger a wrong db type in sendmail build. Strange... Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sendmail 8.11.0 trouble
On Sun, 30 Jul 2000, Garrett Wollman wrote: > < said: > > >> On Sunday, July 30, 2000, Leif Neland wrote: > > >> > Sendmail 8.11.0 > >> > > >> > When invoking sendmail or newaliases I get this message: > >> > /etc/pwd.db: Invalid argument > >> > > >> > Sendmail can't read /etc/pwd.db, and therefore cannot deliver any local > >> > mail. > >> > > >> > Howtofixitplease? > > Sounds like you're using the wrong version of Berkeley DB (i.e., not > the one in libc). Can't fathom how this could override the internal > linkage in libc, though. > There seems indeed to be a confusion of the .db's: /etc/mail/aliases.db: MS Windows COFF Unknown CPU /etc/pwd.db: Berkeley DB Hash file (Version 2, Little Endian, Bucket Size 4096, Bucket Shift 12, Directory Size 256, Segment Size 256, Segment Shift 8, Overflow Point 3, Last Freed 2, Max Bucket 7, High Mask 0xf, Low Mask 0x7, Fill Factor 32, Number of Keys 52) Sendmail compiles with -DNEWDB I had db 2.something installed from the ports. I uninstalled it, it made no difference. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: randomdev entropy gathering is really weak
Mark Murray wrote: > > > Mark already stated that in *practicality*, Yarrow-BF-cbc-256 1.0 > > (I guess that's the proper name for this :-) is complex enough and > > generates good enough ouput. If you /really/ want to make the attack > > on it much harder, how about this: if you're going to read 1024 bits > > of entropy from Yarrow on /dev/random, you will request it all at once > > and block just as the old random(4) used to block; the blocking can > > occur at 256 bit intervals and sleep until there is a reseed. Waiting > > to reseed for each read will ensure a much larger amount of "real" > > entropy than it "maybe" happening at random times. > > This is a reversion to the count-entropy-and-block model which I have > been fiercely resisting (and which argument I thought I had sucessfully > defended). You argued successfully against using the old PRNG mechanism but not against the blocking bit. What is your rationale for not doing the blocking when the client actually wants a guarantee that entropy is not being re-used? > My solution is to get the entropy gathering at a high enough rate that > this is not necessary. What if you cannot guarantee that (and you cannot guarantee that in practice)? > I also agreed to _maybe_ look at a re-engineer of the "old" code in a > secure way if a decent algorithm could be found (I am reading some > papers about this ATM). Why would you if you can provide blocking with Yarrow? Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ [EMAIL PROTECTED] _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_\_| \ _|/' \/ (_)>(_) (_)(_) (_)(_)' _\o_ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sort(1) broken?
On Mon, 31 Jul 2000, Alexander Langer wrote: > Thus spake Brian Fundakowski Feldman ([EMAIL PROTECTED]): > > > I'm doubtful it's the only one of it's kind in GNU sort(1). Time for BSD > > sort(1)? > > What about BSD/OS's sort? BSD/OS userland is almost completely untouched from the 4.4BSD sources. NetBSD and OpenBSD at least work on their tools (and also use BSD sort) :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Minor problems with build/installkernel
Johan Karlsson wrote:
>
> Can you please have a look at some PRs which deals with some minor problem
> with the buldkernel/installkernel targets of Makefile.inc1 and the
> install-modules target of sys/conf/Makefile.${MACHINE}
I will. Thanks for the pointers,
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Minor problems with build/installkernel
[current cc:ed since this might be interesting]
Hi Marcel
Can you please have a look at some PRs which deals with some minor problem
with the buldkernel/installkernel targets of Makefile.inc1 and the
install-modules target of sys/conf/Makefile.${MACHINE}
I think you are the right person for this since you have done most
of the recent work with these targets.
PR 20325 http://www.freebsd.org/cgi/query-pr.cgi?pr=20325
If KERNEL=GENRIC is set in /etc/make.conf the build/installkernel
will create/install kernel as 'GENERIC'.
PR 20326 http://www.freebsd.org/cgi/query-pr.cgi?pr=20326
If DESTDIR=path_to_empty_dir installkernel will fail.
PR 20327 http://www.freebsd.org/cgi/query-pr.cgi?pr=20327
When backing-up modules ${KMODDIR} should be used instead of /modules
Thanks
Johan K
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Mozilla-M15+ipv6 package available
> On Mon, 31 Jul 2000 01:39:29 -0700 (PDT) > Kris Kennaway <[EMAIL PROTECTED]> said: kris> A few people have asked me for this, so I uploaded a package of the kris> mozilla-M15+ipv6 port from KAME to kris> http://www.freebsd.org/~kris/mozilla-M15.tgz kris> (yes, I know M16 is out, but the port isn't yet updated). kris> Install this package and you too can see the dancing kame at kris> http://www.kame.net, the current hilight of the inet6! kris> The patches aren't quite suitable for committing to the ports collection kris> because they unconditionally enable support for IPv6 which may not work on kris> 3.x machines, but if anyone is interested in looking at them then please kris> let me know. And, IPv6 support of Mozilla is heavily depend on mapped address. So, IPv6 enabled Mozilla requires IPv6 awareness of kernel even if IPv4 only access. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.imasy.org/~ume/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ppp.linkdown
Is ppp.linkdown executed before or after the link is down? I'd like to change a dyndns, but will link activity done in linkdown defeat the timeout, or start a new call? Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mozilla-M15+ipv6 package available
On Mon, Jul 31, 2000 at 01:39:29AM -0700, Kris Kennaway wrote: > A few people have asked me for this, so I uploaded a package of the > mozilla-M15+ipv6 port from KAME to ..snip.. > The patches aren't quite suitable for committing to the ports collection > because they unconditionally enable support for IPv6 which may not work on > 3.x machines, So what??? Mark it broken for 3.x. Ask Satoshi to repo-copy the mozilla port to mozilla-ipv6 and make this a real port. :-) -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mozilla-M15+ipv6 package available
At Mon, 31 Jul 2000 05:31:50 -0400, Donn Miller <[EMAIL PROTECTED]> wrote: > The last few Mozillas I tried compiling from source (on -current), I'd > get a message in xterm saying the document was fully loaded, but yet > no window would appear. It seemed like a problem with threading. > Anyone else see this? Did you rm -r ~/.mozilla first? Mozilla configuration files sometimes incompatible across milestones so it is recommended to remove it when you happened to see weird problem as such. I've been tracking mozilla since M13 on -CURRENT and it mostly compiles and runs. I can't say it runs *fine* though :-) -- FUJISHIMA Satsuki To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
PCM failures w/ latest commits
When I try to play an mp3 with either realplayer 7 or mpg123, I get Can't open /dev/dsp! But, the same exact configuration always worked before. - Donn Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Mon Jul 31 10:26:03 EDT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/CUSTOM Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 166450522 Hz CPU: Pentium/P55C (166.45-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Features=0x8001bf real memory = 62914560 (61440K bytes) avail memory = 57769984 (56416K bytes) Preloaded elf kernel "kernel" at 0xc0378000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc037809c. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pci0: at 0.0 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port 0xd000-0xd00f,0xd400-0xd403,0xd800-0xd807,0xe000-0xe003,0xe400-0xe407 irq 11 at device 1.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ed0: port 0xb800-0xb81f irq 10 at device 10.0 on pci0 ed0: address 00:c0:df:ed:0b:17, type NE2000 (16 bit) pci0: at 19.0 irq 11 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 sio2 at port 0x3e8-0x3ef irq 4 on isa0 sio2: type 16550A mse0: at port 0x23c-0x23f irq 3 on isa0 ppc0: at port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources sbc0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 pcm0: on sbc0 ad0: 3093MB [6704/15/63] at ata0-master using UDMA33 ad1: 1040MB [2114/16/63] at ata0-slave using WDMA2 acd0: CDROM at ata1-master using WDMA2
Re: perl vs. LOCALBASE, again
When discussing things like this, where the problem area has a known maintainer, I think that it's wise to include that maintainer in the discussion. Yes, FreeBSD developers are expected to read their -current mail, but in reality, the high level of noise on this list tends to make people very quick with their mailer's deletion facility. In this case, you should chat to Mark Murray <[EMAIL PROTECTED]>. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: perl vs. LOCALBASE, again
On Sun, Jul 30, 2000 at 08:45:05PM -0500, Mike Meyer wrote: > Basically, the problem is that ports that install Perl modules ignore > LOCALBASE for the perl modules. A little bit of investigation turns up > /usr/libdata/perl/5.6.0/Config.pm, which has "/usr/local" wired > through it as a prefix for nearly everything. > I suspect the ideal situation would be for the Perl module installer > to detect (how?) to try and sniff LOCALBASE out of /etc/make.conf if > this is part of a port install. If that works, use LOCALBASE. > Otherwise, use the default Config.pm values. People who want that > default to be something other than /usr/local can then change those > values themselves. IMHO, the easiest thing to do would be to modify the Config.pm itself. For example, it might look for, say, PERL_USE_PREFIX environment variable and change its %Config accordingly. Then the Makefiles in p5 ports will just set this variable to whatever LOCALBASE is, before invoking perl Makefile.PL. There is another problem with your idea, though. Such Perl modules will not be found by perl unless PERL5LIB points to the right place, i.e. your installed p5 ports will not work out of the box. That is pretty bad, and setting PERL5LIB globally will not help much since at least some people set it to their private directories without spelling PERL5LIB=$PERL5LIB:bla mantra. > Is there someone who can *fix* this? Cheers, -- Anton Berezin <[EMAIL PROTECTED]> The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sort(1) broken?
Thus spake Brian Fundakowski Feldman ([EMAIL PROTECTED]): > I'm doubtful it's the only one of it's kind in GNU sort(1). Time for BSD > sort(1)? What about BSD/OS's sort? Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: phkmalloc & pam_ssh & xdm
On 31 Jul, Daniel C. Sobral wrote:
>> pam_ssh isn't able to start ssh-agent if you use
>> ---snip---
>> xdm session sufficient pam_ssh.so
>> ---snip---
>> in /etc/pam.conf. With "malloc.conf -> aj" it seems to work.
>>
>> grep pam /var/log/messages:
>> ---snip---
>> Jul 30 00:54:04 Magelan -:0: unable to resolve symbol: pam_sm_chauthtok
>> Jul 30 00:54:05 Magelan -:0: pam_ssh: could not connect to agent
>> ---snip---
>>
>> Is someone else able to reproduce this?
>
> If that's the case, you have a bug. Not one easy to trace, though... :-(
I assume it's uninitialized memory, it didn't happen with "ln -sf AJZ
/etc/malloc.conf".
This reduces it to code after *alloc calls... or it's an unterminated
string. Ok, I give it a try...
It seems it isn't really something with PAM,
/usr/src/crypto/openssh/pam_ssh/pam_ssh.c:
---snip---
if (!(ac = ssh_get_authentication_connection())) {
syslog(LOG_ERR, "%s: could not connect to agent",
MODULE_NAME);
env_destroy(ssh_env);
return PAM_SESSION_ERR;
---snip---
and
/usr/src/crypto/openssh/authfd.c:
---snip---
int
ssh_get_authentication_socket()
{
const char *authsocket;
int sock;
struct sockaddr_un sunaddr;
[...]
sunaddr.sun_family = AF_UNIX;
strlcpy(sunaddr.sun_path, authsocket, sizeof(sunaddr.sun_path));
[...]
if (connect(sock, (struct sockaddr *) & sunaddr, sizeof(sunaddr)) < 0) {
[...]
---snip---
and
/usr/include/sys/un.h:
---snip---
struct sockaddr_un {
u_char sun_len;/* sockaddr len including null */
u_char sun_family; /* AF_UNIX */
charsun_path[104]; /* path name (gag) */
};
---snip---
sunaddr.sun_len isn't set. If I understand the APUE, it should be:
---snip---
Index: authfd.c
===
RCS file: /big/FreeBSD-CVS/src/crypto/openssh/authfd.c,v
retrieving revision 1.4
diff -u -r1.4 authfd.c
--- authfd.c2000/07/16 05:52:23 1.4
+++ authfd.c2000/07/31 12:03:52
@@ -33,7 +33,7 @@
ssh_get_authentication_socket()
{
const char *authsocket;
- int sock;
+ int sock, len;
struct sockaddr_un sunaddr;
authsocket = getenv(SSH_AUTHSOCKET_ENV_NAME);
@@ -42,6 +42,7 @@
sunaddr.sun_family = AF_UNIX;
strlcpy(sunaddr.sun_path, authsocket, sizeof(sunaddr.sun_path));
+ sunaddr.sun_len = len = SUN_LEN(&sunaddr)+1;
sock = socket(AF_UNIX, SOCK_STREAM, 0);
if (sock < 0)
@@ -52,7 +53,7 @@
close(sock);
return -1;
}
- if (connect(sock, (struct sockaddr *) & sunaddr, sizeof(sunaddr)) < 0) {
+ if (connect(sock, (struct sockaddr *) & sunaddr, len) < 0) {
close(sock);
return -1;
}
---snip---
I rebuilded libssh.a and pam_ssh.so with this patch and I didn't get the
error anymore.
I haven't rebuilded the world or anything openssh related, but I think
this should work (and because of the readability of pam_ssh.c and
authfd.c it was easy to trace only by looking at the source... it seems
using FreeBSD is the "Right Thing[TM]" :) ).
BTW.: the "pam_sm_chauthok" error isn't "xdm session" related, it's
because of "xdm account" or "xdm password" (it's not implemented in
pam_ssh).
Bye,
Alexander.
--
Loose bits sink chips.
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: sort(1) broken?
On Mon, 31 Jul 2000 07:28:09 -0400, Brian Fundakowski Feldman wrote: > key = (struct keyfield *) > xmalloc (sizeof (struct keyfield)); > + bzero(key, sizeof(*key)); Wouldn't a calloc() be exactly what's required here? Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sort(1) broken?
On Mon, 31 Jul 2000, Kris Kennaway wrote:
> The following no longer seems to work on any of my 5.0 boxes:
>
> ls -l | sort -n -k 5
>
> which should sort numerically by the size column (instead it seems to do
> the same thing as sort -n). It works correctly on 3.x and 4.x boxes.
>
> Anyone have ideas?
Sure:
{"/home/green"}$ ls -l | MALLOC_OPTIONS=AJ sort -nk5 | tail -10 | head -5
drwxr-xr-x 13 green green512 Jun 7 1999 saint-1.4
drwxr-xr-x 16 green green512 Aug 5 1999 stress
drwxr-xr-x 17 green green512 Feb 14 23:27 ioccc
drwxr-xr-x 17 green www 1536 Jul 30 18:39 public_html
drwxr-xr-x 21 green green 1024 Feb 7 1999 descent
{"/home/green"}$ ls -l | MALLOC_OPTIONS=aj sort -nk5 | tail -10 | head -5
-rwx-- 1 green green 31017984 Jan 19 2000 quake1.tar.gz
-rw-r--r-- 1 green green 32642085 Jun 25 00:31 mail.tar.gz
-rw-rw-rw- 1 green green 47845836 Jun 26 18:52 ccs12.rm
-rw-r--r-- 1 green green 52525668 Jun 5 21:30 SaberMarionetteJ-ep04.rm
-rw-r--r-- 1 green green 53822026 Jul 11 07:53 SaberMarionetteJ-ep02.rm
To fix this particular bug, the patch is:
Index: sort.c
===
RCS file: /usr2/ncvs/src/gnu/usr.bin/sort/sort.c,v
retrieving revision 1.15
diff -u -r1.15 sort.c
--- sort.c 1999/04/25 22:14:05 1.15
+++ sort.c 2000/07/31 11:26:33
@@ -1860,6 +1860,7 @@
insertkey (key);
key = (struct keyfield *)
xmalloc (sizeof (struct keyfield));
+ bzero(key, sizeof(*key));
key->eword = -1;
key->ignore = NULL;
key->translate = NULL;
I'm doubtful it's the only one of it's kind in GNU sort(1). Time for BSD
sort(1)?
> Kris
>
> --
> In God we Trust -- all others must submit an X.509 certificate.
> -- Charles Forsythe <[EMAIL PROTECTED]>
--
Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! /
[EMAIL PROTECTED]`--'
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Mozilla-M15+ipv6 package available
Kris Kennaway wrote: > > A few people have asked me for this, so I uploaded a package of the > mozilla-M15+ipv6 port from KAME to > > http://www.freebsd.org/~kris/mozilla-M15.tgz > > (yes, I know M16 is out, but the port isn't yet updated). The last few Mozillas I tried compiling from source (on -current), I'd get a message in xterm saying the document was fully loaded, but yet no window would appear. It seemed like a problem with threading. Anyone else see this? -- - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sort(1) broken?
The following no longer seems to work on any of my 5.0 boxes: ls -l | sort -n -k 5 which should sort numerically by the size column (instead it seems to do the same thing as sort -n). It works correctly on 3.x and 4.x boxes. Anyone have ideas? Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Mozilla-M15+ipv6 package available
A few people have asked me for this, so I uploaded a package of the mozilla-M15+ipv6 port from KAME to http://www.freebsd.org/~kris/mozilla-M15.tgz (yes, I know M16 is out, but the port isn't yet updated). Install this package and you too can see the dancing kame at http://www.kame.net, the current hilight of the inet6! The patches aren't quite suitable for committing to the ports collection because they unconditionally enable support for IPv6 which may not work on 3.x machines, but if anyone is interested in looking at them then please let me know. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
