Libraries broken in -CURRENT
Hello all, I just cvsuped -CURRENT and got the following error (only the first of many): -- Rebuilding bootstrap libraries -- cd /work/src/HEAD; BISON_SIMPLE=/usr/obj/work/src/HEAD/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/work/src/HEAD/tmp/usr/libexec:/usr/obj/work/src/HEAD/tmp/usr/bin GCC_EXEC_PREFIX=/usr/obj/work/src/HEAD/tmp/usr/lib:/usr/obj/work/src/HEAD/tmp/usr/lib/ LD_LIBRARY_PATH=/usr/obj/work/src/HEAD/tmp/usr/lib LIBRARY_PATH=/usr/obj/work/src/HEAD/tmp/usr/lib:/usr/obj/work/src/HEAD/tmp/usr/lib NOEXTRADEPEND=t PATH=/usr/obj/work/src/HEAD/tmp/sbin:/usr/obj/work/src/HEAD/tmp/usr/sbin:/usr/obj/work/src/HEAD/tmp/bin:/usr/obj/work/src/HEAD/tmp/usr/bin:/sbin:/usr/sbin:/usr/X11R6/bin:.:/usr/local/bin:/usr/local/pilot/bin:/home/ust/bin/file:/home/ust/bin/sys:/home/ust/bin/misc:/home/ust/bin/dev:/sbin:/usr/sbin:/usr/X11R6/bin:.:/usr/local/bin:/usr/local/pilot/bin:/home/ust/bin/file:/home/ust/bin/sys:/home/ust/bin/misc:/home/ust/bin/dev:/home/ust/bin:/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin OBJFORMAT_PATH=/usr/obj/work/src/HEAD/tmp/usr/libexec:/usr/libexec /usr/obj/work/src/HEAD! /t! ! mp/usr/bin/make DESTDIR=/usr/obj/work/src/HEAD/tmp -f Makefile.inc1 bootstrap-libraries cd /work/src/HEAD/lib/csu/i386-elf; /usr/obj/work/src/HEAD/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/work/src/HEAD/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /usr/obj/work/src/HEAD/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install cleandir obj rm -f .depend /usr/obj/work/src/HEAD/lib/csu/i386-elf/GPATH /usr/obj/work/src/HEAD/lib/csu/i386-elf/GRTAGS /usr/obj/work/src/HEAD/lib/csu/i386-elf/GSYMS /usr/obj/work/src/HEAD/lib/csu/i386-elf/GTAGS cc -O -pipe -elf -Wall -fkeep-inline-functions -I/usr/obj/work/src/HEAD/tmp/usr/include -c /work/src/HEAD/lib/csu/i386-elf/crt1.c -o crt1.o cc -O -pipe -elf -Wall -fkeep-inline-functions -I/usr/obj/work/src/HEAD/tmp/usr/include -c /work/src/HEAD/lib/csu/i386-elf/crtbegin.c -o crtbegin.o /work/src/HEAD/lib/csu/i386-elf/crtbegin.c:32: section attributes are not supported for this target /work/src/HEAD/lib/csu/i386-elf/crtbegin.c:33: section attributes are not supported for this target *** Error code 1 (continuing) cc -O -pipe -elf -Wall -fkeep-inline-functions -I/usr/obj/work/src/HEAD/tmp/usr/include -c /work/src/HEAD/lib/csu/i386-elf/crtend.c -o crtend.o /work/src/HEAD/lib/csu/i386-elf/crtend.c:32: section attributes are not supported for this target /work/src/HEAD/lib/csu/i386-elf/crtend.c:33: section attributes are not supported for this target *** Error code 1 (continuing) Best regards --- Udo Schweigert || Voice : +49 89 636 42170 Siemens AG, Siemens CERT|| Fax: +49 89 636 48000 ZT IK 3 || email : [EMAIL PROTECTED] D-81730 Muenchen / Germany ||: [EMAIL PROTECTED] PGP fingerprint || 2A 53 F6 A6 30 59 64 02 6B C4 E0 73 B2 C9 6C E7 --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Dual-booting: FreeBSD, NetBSD and OpenBSD
On Mon, May 29, 2000 at 01:52:24 +0900, [EMAIL PROTECTED] wrote: I need to setup a machine that will boot FreeBSD, NetBSD and OpenBSD. Assume I have an insane amount of disk space. What's the best way to accomplish this? Last time I tried it, the partition ID numbers were all the same, making this difficult if not impossible. just a starter: NetBSD 1.4 and recent use different FDISK partition ID, so it is easy to share FreeBSD and NetBSD on a same disk using separate FDISK partition. OpenBSD uses 0xa6 and NetBSD 0xa9. With OpenBSD I had no problems, but the NetBSD-disklabel is also interpreted by FreeBSD resulting in some boot-messages: May 28 17:52:10 diehard /kernel: da1s1: rejecting partition in BSD label: it isn 't entirely within the slice May 28 17:52:10 diehard /kernel: da1s1: start 63, end 12048749, size 12048687 May 28 17:52:10 diehard /kernel: da1s1d: start 0, end 35843669, size 35843670 This is due to the "d" slice of NetBSD, which contains the entire disk (not only the entire NetBSD partiton which is - like in FreeBSD the "c" slice). Anyway: apart from this I have a working multi-boot-system (FreeBSD-stable, FreeBSD-current, OpenBSD, NetBSD, Linux, W*s) on multiple disks. Regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT| Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: Inode numbers in daily security output.
On Tue, Jul 11, 2000 at 15:28:45 +0100, David Malone wrote: I've just changed the daily security secipt to include the inode numbers of suid files. This means the first time you run the updated script you will see lots of files have "changed" - this is just the inclusion of the inode numbers in the listing. I think this is a very good idea. I'd like to MFC this to 4.X in a few days, but I'm not sure if I should wait 'till after 4.1 is released. Opinions? Give us at least two days with it, but I think it is too tight to 4.1 release date to get MFC'ed. Regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT| Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problem with an onboard Realtek 8139D
Hi all, with 5.1-current I have a problem with an onboard Realtek 8139D on a (very recent Fujitsu E4010D centrino laptop): after some network activity the system freezes. With 4.8-stable the NIC works flawlessly, but every 5.x-system I tried had that problem (5.0-R, 5.1-R as well as recent snapshots). Is there anything know or at least something I can do to inverstigate that. My problem is that with that laptop under -current pccards also do not work :-( so I'm stuck with the onboard NIC. Best regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 CT IC CERT, Siemens CERT | Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Ipfilter broken on -current
Hi all, since a couple of days ipfilter is broken for -current. kldload ipl.ko gives: link_elf: symbol pfil_head_get undefined And the IPFILTER option inside the kernel-config results in: cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /usr/src/sys/contrib/ipfilter/netinet/ip_fil.c /usr/src/sys/contrib/ipfilter/netinet/ip_fil.c: In function `fr_check_wrapper': /usr/src/sys/contrib/ipfilter/netinet/ip_fil.c:319: error: `PFIL_OUT' undeclared (first use in this function) /usr/src/sys/contrib/ipfilter/netinet/ip_fil.c:319: error: (Each undeclared identifier is reported only once /usr/src/sys/contrib/ipfilter/netinet/ip_fil.c:319: error: for each function it appears in.) /usr/src/sys/contrib/ipfilter/netinet/ip_fil.c: In function `iplattach': /usr/src/sys/contrib/ipfilter/netinet/ip_fil.c:376: warning: unused variable `ph_inet' /usr/src/sys/contrib/ipfilter/netinet/ip_fil.c: At top level: /usr/src/sys/contrib/ipfilter/netinet/ip_fil.c:317: warning: `fr_check_wrapper' defined but not used Best regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 CT IC CERT, Siemens CERT | Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ipfilter broken on -current
On Sat, Oct 04, 2003 at 13:01:31 +0200, Arjan van Leeuwen wrote: On Saturday 04 October 2003 11:21, Udo Schweigert wrote: Hi all, since a couple of days ipfilter is broken for -current. kldload ipl.ko gives: link_elf: symbol pfil_head_get undefined And the IPFILTER option inside the kernel-config results in: (snip) You should read /usr/src/UPDATING. Arrgs, yes I should. Anyway: it doesn't load the ipl.ko when booting and ipfilter_enable=YES. Best regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 CT IC CERT, Siemens CERT | Fax: +49 89 636 41166 D-81730 München / Germany| email : [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make kernel breakage: if_tap
On Fri, Jul 21, 2000 at 07:36:46 +0200, Leif Neland wrote: Just cvsupped: Script started on Fri Jul 21 07:12:56 2000 CEST gina/usr/src/sys/compile/GINA # make clean ... === if_tap cd: can't cd to /usr/src/sys/modules/if_tap Here too. src/sys/modules/if_tap is a completely empty dir (in the cvs tree). Seems a Makefile is missing here (or it should not be tried to build a module). Regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT| Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make package broken on -current (mtree -L problem)
Hi all,
when building a package on -current one gets:
=== Installing for bzip2-1.0.1
mtree: illegal option -- L
usage: mtree [-PUcdeinrux] [-f spec] [-K key] [-k key] [-p path] [-s seed]
[-X excludes]
*** Error code 1
Seems to be a problem in /usr/ports/Mk/bsd.port.mk:
.if ${OSVERSION} = 500010
MTREE_ARGS?=-U -f ${MTREE_FILE} -L -d -e -p
.else
MTREE_ARGS?=-U -f ${MTREE_FILE} -d -e -p
.endif
Regards
--
Udo Schweigert, Siemens AG | Voice : +49 89 636 42170
ZT IK 3, Siemens CERT| Fax: +49 89 636 41166
D-81730 Muenchen / Germany | email : [EMAIL PROTECTED]
PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: make package broken on -current (mtree -L problem)
On Tue, Jul 25, 2000 at 04:14:07 -0400, Donn Miller wrote:
Udo Schweigert wrote:
=== Installing for bzip2-1.0.1
mtree: illegal option -- L
usage: mtree [-PUcdeinrux] [-f spec] [-K key] [-k key] [-p path] [-s seed]
[-X excludes]
*** Error code 1
Seems to be a problem in /usr/ports/Mk/bsd.port.mk:
.if ${OSVERSION} = 500010
MTREE_ARGS?=-U -f ${MTREE_FILE} -L -d -e -p
.else
MTREE_ARGS?=-U -f ${MTREE_FILE} -d -e -p
.endif
Seems as if your mtree is out of date. How long has it been since
your last make world? Cvsup again and build/install mtree again
and/or do a make world.
My mtree is up to date (rev 1.15 of mtree.c). A check of the cvs-tree shows
that -L was backed out yesterday.
Regards
--
Udo Schweigert, Siemens AG | Voice : +49 89 636 42170
ZT IK 3, Siemens CERT| Fax: +49 89 636 41166
D-81730 Muenchen / Germany | email : [EMAIL PROTECTED]
PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ssh and scp fail connecting to a root account
Hello all, after a fresh build of -current openssh does not work if connecting to the root-user. For example (tested from a -stable machine, but the same from 4.1-RELEASE): --- $ ssh host -l root Last login: Fri Sep 15 16:22:48 2000 from Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT () #21: Fri Sep 15 11:59:41 CEST 2000 Welcome to FreeBSD! sshd in realloc(): error: junk pointer, too high to make sense. Connection to closed. --- (This implies that "PermitRootLogin" is set to yes in /etc/ssh/sshd_config) The only soultion is to have "UseLogin" set to yes. But nevertheless scp does never work if copying to the root account like this: --- $ scp file root@host:. select: Bad file descriptor lost connection --- The strange: both commands succeed if connecting to a non-root account. Are there any others with these problems? Any clues? Best regards. -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT| Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ssh and scp fail connecting to a root account
On Sat, Sep 16, 2000 at 00:51:51 +0800, Clive Lin wrote: On Fri, Sep 15, 2000 at 04:33:44PM +0200, Udo Schweigert wrote: sshd in realloc(): error: junk pointer, too high to make sense. Connection to closed. Hm... did you just make new ssh instead of making world or rebuilding kernel ? No, I did a complete "make world" + a new kernel (with config -r) I got exactly the same error on the day sshd upgraded. dmesg shows that sshd got signal 11 all the time. My sshd got signal 6 (ABORT) -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT| Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ssh and scp fail connecting to a root account
On Sat, Sep 16, 2000 at 04:03:32 +0100, Brian Somers wrote: On Fri, 15 Sep 2000, Udo Schweigert wrote: The strange: both commands succeed if connecting to a non-root account. Are there any others with these problems? Any clues? run sshd -d on the server, ssh -d on the client, and send me the output Hmm, I've been seeing this problem too. I ran sshd -p 1234 -d and it worked ok. I then killed the running sshd and started sshd -d and it worked too. I then ran sshd and it worked. I tried that, and it did not work for me. Same results as on port 22. Best regards. -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT| Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ssh and scp fail connecting to a root account
On Wed, Sep 20, 2000 at 04:06:24 +0100, Brian Somers wrote: On 17 Sep 2000, Jason Evans wrote: On Fri, Sep 15, 2000 at 03:40:12PM +0100, Konstantin Chuguev wrote: Udo Schweigert wrote: after a fresh build of -current openssh does not work if connecting to the root-user. For example (tested from a -stable machine, but the same from 4.1-RELEASE): Yes, I've been seeing the same thing since the checkout of the SMPng stuff... No idea why it's happening. I've seen similar things intermittently over the past 10 days, and specifically the same problem for the past three days or so. I'm pretty sure that the problems have been associated with the random device rather than the SMP work specifically. Well, the crash is apparently due to malloc flags - remove the /etc/malloc.conf link and it may work better. I've only seen this once, and when I tried to run sshd under gdb it went away, and now I can't reproduce it again. :-( Got it ! See version 1.6 of src/lib/libc/stdlib/setenv.c. This took me all night - Up for work in two hours !!! :-( Perfect! Now it also works for me. Thank you very much, Brian. Best regards. -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT| Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: entropy reseeding is totally broken
On Fri, Oct 20, 2000 at 08:48:46 +0400, Andrej Cernov wrote: In very recent -current, my entropy file writted and readed sucessfully, but I got the same fortune quote again and again right after reboot! It means that anything writted to /dev/random not reseed it but _reset_ it to the same default state. How do you shutdown your machine: a) reboot or halt b) shutdown -r now If a) the /entropy file is not updated and the existing one will be used at next reboot. Only when using shutdown the /etc/rc.shutdown file will be executed. That was a problem for me, as I often use "halt". Regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT| Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ABI is broken??
On Wed, Nov 01, 2000 at 19:17:26 +0200, Maxim Sobolev wrote: Hi, I'm not sure what exactly caused this behaviour (I can guess two potential victims: O'Brien's changes in crt stuff and recent Polstra's changes in libgcc_r), but it seems that some programs built on the previous -current from 27 October immediately segfault when I'm trying to run then on system installed from today's sources. The segfault disappeared when I recompiled affected program. With this message I'm attaching short backtrace. -Maxim #0 0x287de417 in pthread_mutex_lock () from /usr/lib/libc_r.so.4 Same for me in -stable (4.2-BETA) and python-1.6. After rebuilding the port this disappeared. My gdb showed the same error message as the quoted above. Regards. -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT| Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI and Sony laptop
On Sat, Dec 02, 2000 at 14:20:40 -0800, Nick wrote: I took the plunge. My Z505JE now runs -current. A couple of things I have observed: rebooting with other than ctrl-alt-del doesn't result in rc.shutdown being run, which means I have to whomp on the keyboard at the next reboot. Am I doing something wrong that 'shutdown' and 'reboot' don't run rc.shutdown? That seems to be intended. I also observed this behaviour some time ago because with -current the entropy file is written by the rc.shutdown script and if this is not done at shutdown the next boot will take more time. Now I use "init 0" for shutdown and "init 6" for reboot. Regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT| Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Memory corruption in CURRENT
On Thu, Aug 22, 2002 at 11:23:46 +0200, Martin Blapp wrote: That's what I thought too. I have now three different systems which show all this: 1) PIV 1,6Ghz, Intel B845DG Board, 1GB Kingston Ram, 2) PIV 2Ghz Intel B845DG Board, 1GB Kingston ECC Ram 3) PIV 2,26 Ghz Asus P4B533 Board with I845 chipset, 1GB noname Ram All running CURRENT. I also replaced in 1) and 2) the CPU, RAM. It happens both on SCSI and ATA disks. Powersupply has been changed for all 3 systems. Problem is still the same. The problem sometimes appears just after startup. CPU is still cold then. Other times it builds 6 buildworlds sucessfully, and then suddenly I see a SIG4. Only a little addition from me: I had the same problems on -stable and they only disappeared after compiling the kernel without debugging. I had the impression that it has to do with the size of the kernel (but this of course maybe wrong). After dropping -g from kernel compiling I hadn't a problem again on -stable. (At the moment I do not have -current on a P-IV, the motherboard is a Fujitsu-Siemens) Best regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 CT IC CERT, Siemens CERT | Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Release building broken for -current
Hi all, when bulding release on -current I get (since a couple of days): rm -rf /R/stage/dists mkdir -p /R/stage/dists rolling base/base tarball mtree: line 0: dumpdates: No such file or directory *** Error code 1 Stop in /usr/src/release. Somehow dumpdates didn't get installed into /R/stage/trees/base/usr/share/examples/etc Later then I got same problems for: /R/stage/trees/base/usr/share/tmac/mm/locale /R/stage/trees/base/usr/share/tmac/mm/se_locale ... and others. All the problems seem to be with files of size 0, so maybe the problem is with mtree. Hopefully this can be get fixed so a new snapshot release with the new gcc can be built. Best regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 CT IC CERT, Siemens CERT | Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Release building broken for -current
On Sun, Sep 08, 2002 at 19:05:08 +0200, John Hay wrote: when bulding release on -current I get (since a couple of days): rm -rf /R/stage/dists mkdir -p /R/stage/dists rolling base/base tarball mtree: line 0: dumpdates: No such file or directory *** Error code 1 Stop in /usr/src/release. Somehow dumpdates didn't get installed into /R/stage/trees/base/usr/share/examples/etc md5 died on zero length files. You will have to upgrade the machine or at least do a buildworld with new source before you try a release again. Yes, that fixed it. Thanks. Best regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 CT IC CERT, Siemens CERT | Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Problem with rlogin and /etc/pam.conf
Hi all, on two 4.0-CURRENT boxes (cvsuped today) I got the following response when trying to rlogin to it: # rlogin indiana assword: A typed-in password is echoed in cleartext. The only thing that helps is to comment out the second-last line in /etc/pam.conf: # other authrequiredpam_unix.so try_first_pass But this gives an error message when first using the login at the console. Any help on this? Did I miss something? Best regards and HAPPY NEW YEAR --- Udo Schweigert || Voice : +49 89 636 42170 Siemens AG, Siemens CERT|| Fax: +49 89 636 41166 ZT IK 3 || email : [EMAIL PROTECTED] D-81730 Muenchen / Germany ||: [EMAIL PROTECTED] PGP fingerprint || 2A 53 F6 A6 30 59 64 02 6B C4 E0 73 B2 C9 6C E7 --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: rlogin from 3.X to 4.0 problem...
On Wed, Jan 05, 2000 at 18:33:40 +0100, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Luigi Rizzo writes: With the 991229 shapshot, from a FreeBSD 3.3 or 3.4 machine: rlogin bsd4 assword:hey this is great! why is the initial 'P' missing, and the password echoed ? Bug in /etc/pam.conf Fixed with pam.conf version 1.4. Regards --- Udo Schweigert || Voice : +49 89 636 42170 Siemens AG, Siemens CERT|| Fax: +49 89 636 41166 ZT IK 3 || email : [EMAIL PROTECTED] D-81730 Muenchen / Germany ||: [EMAIL PROTECTED] PGP fingerprint || 2A 53 F6 A6 30 59 64 02 6B C4 E0 73 B2 C9 6C E7 --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /usr/ports/ too big?
On Thu, Feb 10, 2000 at 22:18:12 -0800, John Polstra wrote: In article [EMAIL PROTECTED], Leif Neland [EMAIL PROTECTED] wrote: Just FYI, a cvsup of ports over a single ISDN-line took 22 min on a soft-update'd disk. Something is seriously wrong over there then, because I can update my entire CVS repository in 1.5-2 minutes. And my Internet link is a wimpy 56 Kbit frame relay connection For me, located behind a 64Kbit ISDN connection (sppp), it takes 3min for the ports + 1min for src/crypto. Regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT| Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] PGP-2/5 fingerprint | 2A 53 F6 A6 30 59 64 02 6B C4 E0 73 B2 C9 6C E7 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ipfilter not broken for me
On Mon, Apr 29, 2002 at 17:45:05 +0100, Brian Somers wrote: On Sat, Apr 27, 2002 at 04:01:28PM +1000, Darren Reed wrote: In some email I received from Doug Barton, sie wrote: On Fri, 26 Apr 2002, Ruslan Ermilov wrote: =20 I tested this on i386 only with 2 days old -CURRENT (today's is broken due to the import of latest IPFilter suite) =20 I updated to the latest and greatest last night around midnight and built/installed -current just fine. What about the ipfilter import = is broken, and have you let Darren know? I haven't seen anything on the li= sts about it... =20 I have not received any email about it. I tested building all the ipfilt= er binaries and kernel after the import and came up clean. if ref5 was a bit quicker =20 That was probably a local problem on one of the Brian's fast machines where I initially attempted to finally test my patch (unsynched cvsup update?). Sorry for the false alarm, I can't check it right now anyway. Yes... I've had periods where the compiler drops cores all over the place, and other periods where things work fine. It's on a P4-1.7Ghz and has behaved like this since about last August. The only variable is the kernel - some kernels work and some don't. I've spent many 10s of hours trying to track it down, and I still have no idea what causes it - except that some kernels ``just work'' and some don't. Maybe it depends on the humidity in the room when a kernel is built or something - and I'm only half joking here ! FWIW ru, /boot/kernel/kernel seems ok now. /boot/kernel.sig/kernel isn't. I discovered the same problem here for a P4-1.7Ghz with -stable. First thing I discovered: this only happens if you have -pipe in your CFLAGS in /etc/make.conf. It seems something with pipe handling is broken on these fast machines, which makes cc fail. Currently I'm trying to figure out which commit brought that in. Probabilty is high that it has to do with ipfilter, but I'm not quite sure. Definitively it is not a problem local to Brian. Best regards Udo Schweigert -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 CT IC 3, Siemens CERT| Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CURRENT and P-IV problems
On Sat, May 04, 2002 at 21:54:08 +0200, Martin Blapp wrote: Hi all, I experiment very strange problems here at the moment with a new server. Buildworld survives about 30 secondy, the errors are SIG4 (90%) and SIG11 (10%). And I cannot compile any important programs :-/ I've exchanged all relevant parts: - Power Supply: 300W, for PIV with additional CPU supply - CPU (PIV, 2Ghz, 512K cache) - Ram with ECC correction - Board (Intel D845BG) - SCSI Card. (it happens also on ATA) We have these boards running fine here. And now to the strange part. It does not happen with STABLE. This let's me beleave that this is a CURRENT problem. Unfortunately not. Since 1 week these types of errors (cc -pipe exiting with some signal) also occurs on -stable for me with a P-IV 1.7GHz. I tried to figure out which commit to RELENG_4 introduced the problems and found that the problems began with the ipfilter update to v3.4.27. But this seems not to be the real cause, as a workaround I found (dropping -pipe from CFLAGS) has nothing to do with ipfilter. Here are some symptoms from my /var/log/messages pid 92638 (cc), uid 0: exited on signal 4 (core dumped) pid 44494 (cc), uid 0: exited on signal 10 (core dumped) pid 23068 (sed), uid 0: exited on signal 11 (core dumped) pid 19046 (egrep), uid 0: exited on signal 4 (core dumped) pid 28452 (sed), uid 0: exited on signal 11 (core dumped) pid 65784 (cpp0), uid 0: exited on signal 4 (core dumped) pid 61931 (sed), uid 0: exited on signal 10 (core dumped) pid 80953 (cc), uid 0: exited on signal 10 (core dumped) pid 32562 (cc), uid 0: exited on signal 10 (core dumped) pid 12812 (sed), uid 0: exited on signal 11 (core dumped) pid 36423 (cc), uid 0: exited on signal 10 (core dumped) pid 87631 (cc), uid 0: exited on signal 4 (core dumped) pid 58087 (sed), uid 0: exited on signal 11 (core dumped) Again: there are no hardware problems (memory, cooling, etc.) here, it is only related to some kernels. Booting a kernel which is old enough makes the system running flawlessly. Would be nice if that could be resolved before -RELEASE (but it seems to be a difficult bug to track down). Best regards Udo Schweigert -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 CT IC 3, Siemens CERT| Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
