Re: RE: Proposed makewhatis perl script fix
Er, could it possibly be that telnet has been hiding the error all along? It's really, really hard to see how ssh could *create* this sort of error. Barney Wolff On Sun, Feb 11, 2001 at 09:35:43AM +0100, Blaz Zupan wrote: pkg_add runs tar with the --fast-read option to extract the table of contents. When I remove the option pkg_add no longer reports broken pipes. When gunzip'ing piped to tar, and tar exits early due to the option, gunzip properly gets a 'gzip: stdout: Broken pipe' error. Maybe 'tar' was changed recently, maybe 'gunzip' was changed recently, I don't know. But it isn't a kernel problem. The kernel is doing exactly what it is supposed to be doing. A simple "cvs diff" between RELENG_4_2_0_RELEASE and RELENG_4 reveals, that gzip has not changed at all, while tar has only grown bzip2 support. As Kent suggests, ssh might be the problem. To verify, I have just logged in through telnet and done a "pkg_add gmake-3.79.1.tgz". And yes indeed, the broken pipe message disappears. So the OpenSSH 2.3.0 seems to be causing the problem. Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: [EMAIL PROTECTED], Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: uh oh - after 4 - 4.2 cvsup, no keyboard. any ideas?
:If the flags 0x100 is specified to syscons (this is now default in :GENERIC), syscons should revert to the AT keyboard when the USB :keyboard has gone. : :Kazu ok... so if we remove 'flags 0x1' from atkbd0, and leave 'flags 0x100' on sc0, and add an entry to /etc/usbd.conf to transfer control to the USB keyboard, then we will be ok? Or not? Yes, it should be OK. But, I have to check several things before we go committing things. IIRC, currently USB keyboards (for that matter, the AT keyboard too) don't have explicit /dev entries. We need to add them, otherwise usbd and kbdcontrol won't be able to refer to the newly attached USB keyboard. Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: troubles with Adaptec 29160 ULTRA160 SCSI
On Sun, Feb 11, 2001 at 09:13:59AM +0200, Danny Braniss wrote: FWIW: My 29160 works just fine with yesterdays stable. I suspect plumbing problems like Danny says Wilko i've had similar problems, in my case after changing cable/terminator the problem was fixed. danny In message [EMAIL PROTECTED]you write: }Hi, } }I've installed FreeBSD 4.2 -RELEASE and did cvsup last night to -STABLE, }then tried /stand/sysinstall and the console hung with message }"Probing devices" , in dmesg there was following information: } }Feb 10 01:27:50 arne /kernel: Untagged Q(6): 13 }Feb 10 01:27:50 arne /kernel: (sa0:ahc0:0:6:0): Queuing a BDR SCB }Feb 10 01:27:50 arne /kernel: (sa0:ahc0:0:6:0): Bus Device Reset Message }Sent }Feb 10 01:27:50 arne /kernel: (sa0:ahc0:0:6:0): no longer in timeout, }status = 34b }Feb 10 01:27:50 arne /kernel: ahc0: Bus Device Reset on A:6. 1 SCBs aborted }Feb 10 03:27:47 arne /kernel: (sa0:ahc0:0:6:0): SCB 0xd - timed out }while idle, SEQADDR == 0x4 }Feb 10 03:27:47 arne /kernel: STACK == 0x1, 0x106, 0x15e, 0x174 }Feb 10 03:27:47 arne /kernel: SXFRCTL0 == 0x80 }Feb 10 03:27:47 arne /kernel: SCB count = 230 }Feb 10 03:27:48 arne /kernel: QINFIFO entries: }Feb 10 03:27:48 arne /kernel: Waiting Queue entries: }Feb 10 03:27:49 arne /kernel: Disconnected Queue entries: 23:13 }Feb 10 03:27:49 arne /kernel: QOUTFIFO entries: }Feb 10 03:27:49 arne /kernel: Sequencer Free SCB List: 21 5 31 2 14 15 }30 28 4 18 11 17 27 22 13 12 26 9 8 25 20 1 16 0 3 24 7 10 6 29 19 }Feb 10 03:27:50 arne /kernel: Pending list: 13 }Feb 10 03:27:50 arne /kernel: Kernel Free SCB list: 77 39 61 128 125 55 }95 30 27 23 84 123 67 92 88 103 129 19 58 75 108 85 34 100 28 56 115 50 } }every 2 hours this messages repeated } }I have Adaptec 29160 ULTRA160 SCSI, IBM SCSI harddisks and HP-DAT }Streamer. } }-- }Kirill Ponomarew } } }To Unsubscribe: send mail to [EMAIL PROTECTED] }with "unsubscribe freebsd-stable" in the body of the message } To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message ---end of quoted text--- -- | / o / / _ Arnhem, The Netherlandsemail: [EMAIL PROTECTED] |/|/ / / /( (_) Bultehttp://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ata driver and HighPoint HPT370 ATA100 controller
"Matthew" == Matthew Emmerton [EMAIL PROTECTED] writes: Matthew Even though your controller supports UDMA operation, not all Matthew devices use it. Thanks, i know that ;-) Matthew A quick scan of the manual for your Plextor Matthew seems to indicate that it only operates in PIO4 mode, and not Matthew UDMA33/66/100.. What are you talking about ? I've read the Plextor manual, and there's no such an indication. -- ric Jacoboni, n il y a 1285246056 secondes. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.0 Release - 4.2-Stable should be ok ? via cvsup ?
On Sat, 10 Feb 2001, Warner Losh wrote: Yes. I've done this with Feb 4th sources on our 4.0-RELEASE firewall. Well, I'm waiting for a time to do the make installworld/installkernel since the machine isn't at my house and I'm nervous about doing it remotely since I screw 4 people if something goes wrong. I hope that's _late_ Feb 4th sources if your firewall uses ipfw: ipfw was substantially broken from 2001/02/01 20:25:09 to 2001/02/04 05:48:59 (/sys/netinet/ip_fw.c rev 1.131.2.13 is the bad version). We were upgrading our firewall around that time and were dismayed to find it wide-open after the upgrade! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: troubles with Adaptec 29160 ULTRA160 SCSI
Hi Yes, I concur. I had similar problems on an Adaptec 3985 (788x based) where I changed out a cable and the messages went away and so did the physical hanging problems I was having. Chad --On Sunday, February 11, 2001 9:13 AM +0200 Danny Braniss [EMAIL PROTECTED] wrote: i've had similar problems, in my case after changing cable/terminator the problem was fixed. danny In message [EMAIL PROTECTED]you write: }Hi, } }I've installed FreeBSD 4.2 -RELEASE and did cvsup last night to -STABLE, }then tried /stand/sysinstall and the console hung with message }"Probing devices" , in dmesg there was following information: } }Feb 10 01:27:50 arne /kernel: Untagged Q(6): 13 }Feb 10 01:27:50 arne /kernel: (sa0:ahc0:0:6:0): Queuing a BDR SCB }Feb 10 01:27:50 arne /kernel: (sa0:ahc0:0:6:0): Bus Device Reset Message }Sent }Feb 10 01:27:50 arne /kernel: (sa0:ahc0:0:6:0): no longer in timeout, }status = 34b }Feb 10 01:27:50 arne /kernel: ahc0: Bus Device Reset on A:6. 1 SCBs aborted }Feb 10 03:27:47 arne /kernel: (sa0:ahc0:0:6:0): SCB 0xd - timed out }while idle, SEQADDR == 0x4 }Feb 10 03:27:47 arne /kernel: STACK == 0x1, 0x106, 0x15e, 0x174 }Feb 10 03:27:47 arne /kernel: SXFRCTL0 == 0x80 }Feb 10 03:27:47 arne /kernel: SCB count = 230 }Feb 10 03:27:48 arne /kernel: QINFIFO entries: }Feb 10 03:27:48 arne /kernel: Waiting Queue entries: }Feb 10 03:27:49 arne /kernel: Disconnected Queue entries: 23:13 }Feb 10 03:27:49 arne /kernel: QOUTFIFO entries: }Feb 10 03:27:49 arne /kernel: Sequencer Free SCB List: 21 5 31 2 14 15 }30 28 4 18 11 17 27 22 13 12 26 9 8 25 20 1 16 0 3 24 7 10 6 29 19 }Feb 10 03:27:50 arne /kernel: Pending list: 13 }Feb 10 03:27:50 arne /kernel: Kernel Free SCB list: 77 39 61 128 125 55 }95 30 27 23 84 123 67 92 88 103 129 19 58 75 108 85 34 100 28 56 115 50 } }every 2 hours this messages repeated } }I have Adaptec 29160 ULTRA160 SCSI, IBM SCSI harddisks and HP-DAT }Streamer. } }-- }Kirill Ponomarew } } }To Unsubscribe: send mail to [EMAIL PROTECTED] }with "unsubscribe freebsd-stable" in the body of the message } To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Ports updating... Good ways?
Jim Weeks: On Thu, 8 Feb 2001, David Bushong wrote: I'll try to put a "cleanup" mode in one of these days, but it's rather nasty, since basically you have to: pkg_delete all of the versions (including the most recent), pkg_delete all of the programs that depended on older versions, reinstall/rebuild the most recent version, then rebuild the dependent packages. You don't really have to do this. You can remove the info files for the old versions from /var/db/pkg/. For instance, if you have checked pkg_info and found you have two versions of zip ie zip-2.3 and zip-2.2, simply rm -r /var/db/pkg/zip-2.2 Disagree. Consider that zip-2.2 had added a file /usr/local/where/ever which is no longer part of zip-2.3. Now you want that one cleaned up as well, don't you? Having two versions of one port installed is generally a Bad Thing as it may result in orphan files. Helge To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: uh oh - after 4 - 4.2 cvsup, no keyboard. any ideas?
:If the flags 0x100 is specified to syscons (this is now default in :GENERIC), syscons should revert to the AT keyboard when the USB :keyboard has gone. : :Kazu ok... so if we remove 'flags 0x1' from atkbd0, and leave 'flags 0x100' on sc0, and add an entry to /etc/usbd.conf to transfer control to the USB keyboard, then we will be ok? Or not? Yes, it should be OK. But, I have to check several things before we go committing things. IIRC, currently USB keyboards (for that matter, the AT keyboard too) don't have explicit /dev entries. We need to add them, otherwise usbd and kbdcontrol won't be able to refer to the newly attached USB keyboard. To work properly it has to be done at a lower level than usbd, you want it working when you boot into ddb. USB keyboards do have /dev entries, I have a cordless USB keyboard, I've been doing this insufficient hack at boot: if [ -c /dev/kbd1 ]; then cp /dev/null /dev/kbd1 2 /dev/null if [ $? = 0 ]; then /usr/sbin/kbdcontrol -k /dev/kbd1 fi fi which works for me especially since I just leave a second keyboard plugged into it. Yes, I know this is no solution. I assume there was a problem with leaving both keyboards enabled and mixing the input? That would work for me. Peter -- Peter Dufault ([EMAIL PROTECTED]) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Proposed makewhatis perl script fix
Barney Wolff [EMAIL PROTECTED] writes:
Er, could it possibly be that telnet has been hiding the error
all along? It's really, really hard to see how ssh could
*create* this sort of error.
Try the following patch (which I dug up off the Web after the previous
go-round on this problem). It seems to work.
(The indentation is wrong, I know. I had to apply the patch -l because
the HTMLization of the original mail message hosed the whitespace.)
--- /usr/src/crypto/openssh/session.c Sun Feb 4 10:01:29 2001
+++ /usr/src/crypto/openssh/session.c.PIPE_PATCHSun Feb 4 10:01:58 2001
@@ -448,8 +448,6 @@
if (s == NULL)
fatal("do_exec_no_pty: no session");
- signal(SIGPIPE, SIG_DFL);
-
session_proctitle(s);
#ifdef USE_PAM
@@ -461,6 +459,8 @@
/* Child. Reinitialize the log since the pid has changed. */
log_init(__progname, options.log_level, options.log_facility,
log_stderr);
+ signal(SIGPIPE, SIG_DFL);
+
/*
* Create a new session and process group since the 4.4BSD
* setlogin() affects the entire process group.
@@ -569,6 +569,8 @@
if ((pid = fork()) == 0) {
/* Child. Reinitialize the log because the pid has changed. */
log_init(__progname, options.log_level, options.log_facility,
log_stderr);
+
+ signal(SIGPIPE, SIG_DFL);
/* Close the master side of the pseudo tty. */
close(ptyfd);
--
Christopher Davis * [EMAIL PROTECTED] * URL:http://www.ckdhr.com/ckd/
Put location information in your DNS! URL:http://www.ckdhr.com/dns-loc/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
No Subject
subscribe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Proposed makewhatis perl script fix
Try the following patch (which I dug up off the Web after the previous go-round on this problem). It seems to work. (The indentation is wrong, I know. I had to apply the patch -l because the HTMLization of the original mail message hosed the whitespace.) Excellent, this seems to be the fix! Could a commiter please review and commit this? Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: [EMAIL PROTECTED], Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Proposed makewhatis perl script fix
In message [EMAIL PROTECTED], Kent Stewart writes: Blaz Zupan wrote: :Actually, I don't think it fixed everything. There have been ports :that also had problems with piping to tar and broken pipes. It :wouldn't surprise me if the makewhatis problem was only a little piece :of what is broken. : :Kent makewhatis is just makewhatis... it has nothing to do with tar. When you tar something up, tar writes full blocks. But when you unta r something the actual end of the archive may occur in the middle of a block. tar will close the input descriptor 'early' in this case, potentially before gunzip or uncompress manage to write the last bloc k of zeros. I also don't believe that this is the real fix - there is something fishy going on in stable. I just upgraded all of our servers from 4.2-RELEASE to 4.2-STABLE and I see the following messages upon installing *any* package: /home/blaz# pkg_add gmake-3.79.1.tgz gzip: stdout: Broken pipe tar: child returned status 1 /home/blaz# The package actually appears to install and work fine. I also noticed simil ar messages from gzip during "make" on a port, but again the port built and installed fine after that. So no, your makewhatis patch only appears to be a bandaid, but there is something going on deeper (possibly in the kernel) that was not there in 4.2-RELEASE. Were you using ssh to login on to the computers when you were doing the package/port work? That seems to be the common thread from my end. At least, the broken pipes didn't start occuring until the version of Openssh was updated. If I telnet and do my work no problem; however, if I use ssh, then I see broken pipes. Could it be some interaction between -STABLE and OpenSSH 2.3.0? I installed OpenSSH 2.3.0 on some 4.2-RELEASE systems, including the src/secure bits, and have had no broken pipes problems when using ssh. Regards, Phone: (250)387-8437 Cy SchubertFax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: [EMAIL PROTECTED] Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Proposed makewhatis perl script fix
On Sun, Feb 11, 2001 at 06:25:44 -0800, Cy Schubert wrote: So no, your makewhatis patch only appears to be a bandaid, but there is something going on deeper (possibly in the kernel) that was not there in 4.2-RELEASE. Were you using ssh to login on to the computers when you were doing the package/port work? That seems to be the common thread from my end. At least, the broken pipes didn't start occuring until the version of Openssh was updated. If I telnet and do my work no problem; however, if I use ssh, then I see broken pipes. Could it be some interaction between -STABLE and OpenSSH 2.3.0? I installed OpenSSH 2.3.0 on some 4.2-RELEASE systems, including the src/secure bits, and have had no broken pipes problems when using ssh. Well, in Russian BSD newsgroup I see complaints that even $ program | more# and press `q' while program is still running giving the same error. OTOH, I have -STABLE as of Feb 3 (i.e. with openssh 2.3.0) on my home box and I do *not* see this problem when I slogin to it from office. SY, Uwe -- [EMAIL PROTECTED] | Zu Grunde kommen http://www.ptc.spbu.ru/~uwe/| Ist zu Grunde gehen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Proposed makewhatis perl script fix
In message [EMAIL PROTECTED], "Valeriy E. Ushakov" write s: On Sun, Feb 11, 2001 at 06:25:44 -0800, Cy Schubert wrote: So no, your makewhatis patch only appears to be a bandaid, but there is something going on deeper (possibly in the kernel) that was not there in 4.2-RELEASE. Were you using ssh to login on to the computers when you were doing the package/port work? That seems to be the common thread from my end. At least, the broken pipes didn't start occuring until the version of Openssh was updated. If I telnet and do my work no problem; however, if I use ssh, then I see broken pipes. Could it be some interaction between -STABLE and OpenSSH 2.3.0? I installed OpenSSH 2.3.0 on some 4.2-RELEASE systems, including the src/secure bits, and have had no broken pipes problems when using ssh. Well, in Russian BSD newsgroup I see complaints that even $ program | more # and press `q' while program is still running giving the same error. OTOH, I have -STABLE as of Feb 3 (i.e. with openssh 2.3.0) on my home box and I do *not* see this problem when I slogin to it from office. Based upon what I've seen on this list and my own empirical evidence, I think it must be combination of conditions, e.g. -STABLE as of date and OpenSSH 2.3.0. Regards, Phone: (250)387-8437 Cy SchubertFax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: [EMAIL PROTECTED] Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: uh oh - after 4 - 4.2 cvsup, no keyboard. any ideas?
Matt Dillon ([EMAIL PROTECTED]) napisa(a): :If the flags 0x100 is specified to syscons (this is now default in :GENERIC), syscons should revert to the AT keyboard when the USB :keyboard has gone. : :Kazu ok... so if we remove 'flags 0x1' from atkbd0, and leave 'flags 0x100' on sc0, and add an entry to /etc/usbd.conf to transfer control to the USB keyboard, then we will be ok? Or not? Lemme complicate things a little bit. I have 0x0100 with sc0, no flags 0x1 with atkbd0: atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x100 and... surprise... I have console="comconsole" in my /boot/loader.conf The box has a built-in VGA card, so we've plugged in kbd/vga multiplexer, we have ttyv0 enabled in /etc/ttys and... we experience a login prompt, but no kbd response. Serial console works fine - it's still used remotely and definitely deserves its /etc/ttys entry, however it would be nice to have a possibility to play with virtual console while in server room. kbdcontrol -k /dev/kbd0 didn't help much... A whole com/at/usb keyboard, serial/vga console plus "dual console" feature and -h flags are getting a bit messy to me... Although much better than ol' Solaris /etc/system entry. -- Marcin Cieslak // [EMAIL PROTECTED] - SYSTEM Internet Provider http://www.system.pl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Proposed makewhatis perl script fix
Well, in Russian BSD newsgroup I see complaints that even $ program | more # and press `q' while program is still running giving the same error. I don't see that myself. Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: [EMAIL PROTECTED], Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.0 Release - 4.2-Stable should be ok ? via cvsup ?
In message [EMAIL PROTECTED] Andrew Gordon writes: : I hope that's _late_ Feb 4th sources if your firewall uses ipfw: ipfw was : substantially broken from 2001/02/01 20:25:09 to 2001/02/04 05:48:59 : (/sys/netinet/ip_fw.c rev 1.131.2.13 is the bad version). : : We were upgrading our firewall around that time and were dismayed to find : it wide-open after the upgrade! Yes. Since I'm on the security-officer's list still, I had planned the upgrade for a day earlier, but put things off until the fixes were committed. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
4.2 STABLE kernel broken?
-BEGIN PGP SIGNED MESSAGE- Hello, I built new world and kernels today. Trying to boot them, I always run into the following: Copyright (c) 1992-2001 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 4.2-STABLE #2: Sun Feb 11 13:16:55 CET 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ffnonwpboxes Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 501887921 Hz CPU: AMD-K6(tm) 3D processor (unknown-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX AMD Features=0x8800SYSCALL,3DNow! panic: CPU class not configured This is a K6-2 500 (on, IIRC, VIA MVP3). I haven't changed the config file since the last build (which was as smooth as always) except that I ramped up maxusers to 64. Loading an old kernel by hand works perfectly smooth. On another note: my K6-2 500 running 5-CURRENT won't boot 5-CURRENT kernels of today... Best regards, Gabriel -BEGIN PGP SIGNATURE- Version: PGP 6.0.2i iQEVAwUBOoaz1MZa2WpymlDxAQEOQAf+IKpM5kVEdSANEKWEV6qSwZ+VnbZJ8L4r Jn5ArmTDdIZMx+OqVKJZ7KhNmuZXHBX2zsCKjHalIAFwWufaDLEy0ck0MzHohvZT FGChQrE49ahKYcookgDj48uMenKqPuoYjcP30003cjLgAaP+A7Kov1qYv+Hj1Btq RAX5krT63PyTXpU9QvZs4Ql7oC6WFDPsNXdW+ljFA405dpCYhTQ2G/nJIXadl2cX vGQCGBlnNGB7DW4uTuwDkH+xYV1NVeOVDvRcQzt0jXUQAqK9WbZdbRu/XYFsKoOR uV53887JuheJqzhb+E5m1hDoGs3O0IA4nvPO5zMIMwpxo8izR86TKA== =orqF -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
sysinstall and ports for 4.2-STABBLE
Hi All, After "make world" when I started /stand/sysinstall and tryed to install ports collection, I received the following message: l User Confirmation Requested k x Warning: Can't find the `4.2-STABLE' distribution on this x x FTP server. You may need to visit a different server for x x the release you are trying to fetch or go to the Optionsx x menu and to set the release name to explicitly match what's x x available on ftp.freebsd.org (or set to "any"). x x x x Would you like to select another FTP server?x tqu x[ Yes ] No x mqj This happend for the primary site and for releng4.freebsd.org. Any help? Thanks, Rossen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 3.5-S-4.2-S: still fail w/ setresuid on miniperl
try these instructions: http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=699499+706204+/usr/local/www/db/text/2000/freebsd-stable/2806.freebsd-stable I did it once on a mail server and vowed never to do it again if I didn't have to. Basically you have to build perl separately. --clark 3.5-STABLE to 4-STABLE upgrade. miniperl, setresuid, 3.5-STABLE, RELENG_3, 4-STABLE, RELENG_4 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 3.5-S-4.2-S: still fail w/ setresuid on miniperl
On Sun, Feb 11, 2001 at 05:37:42PM +0200, Pekka Savola wrote: As a lot of others including some @FreeBSD.org people, I got: [snip] pp_hot.o(.text+0x16a1): undefined reference to `setresuid' pp_hot.o(.text+0x16d4): undefined reference to `setresgid' *** Error code 1 --- while trying to update from the latest 3.5-S to 4.2-S. Both had been CVSupped within 24h. I followed the UPDATING instructions. Have you tried to upgrade to 4.0-RELEASE first, and then to 4.2-STABLE? I've never had the problem you're having, but I've never tried to make as big a jump as you're trying to do. Chris PGP signature
Re: sysinstall and ports for 4.2-STABBLE
What you probaby need to do is either: 1. Go to "Options" in the main menu of sysinstall, and change "Release Name" to 4.2-RELEASE. THe ports are the same for the entire 4.x branch, so you will be OK 2. Use cvsup to sync your ports tree. If find this the easiest, anyway, but it's all a matter of taste. To install cvsup: cd /usr/ports/net/cvsup make all install clean You can find documentation on cvsup at http://www.freebsd.org/handbook/cvsup.htnl -Ben On Sun, Feb 11, 2001 at 11:48:23AM -0500, Rossen Raykov wrote: Hi All, After "make world" when I started /stand/sysinstall and tryed to install ports collection, I received the following message: l User Confirmation Requested k x Warning: Can't find the `4.2-STABLE' distribution on this x x FTP server. You may need to visit a different server for x x the release you are trying to fetch or go to the Optionsx x menu and to set the release name to explicitly match what's x x available on ftp.freebsd.org (or set to "any"). x x x x Would you like to select another FTP server?x tqu x[ Yes ] No x mqj This happend for the primary site and for releng4.freebsd.org. Any help? Thanks, Rossen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message PGP signature
Re: RE: Proposed makewhatis perl script fix
From the signal() manual page: When a process which has installed signal handlers forks, the child pro- cess inherits the signals. All caught signals may be reset to their de- fault action by a call to the execve(2) function; ignored signals remain ignored. So I would say that it is definitely ssh that is changing the SIGPIPE methodology. gunzip must be exiting without generating an error message with SIGPIPE is SIG_DFL. If gunzip were ever to catch the signal and report it, though, we will wind up with the errors popping up again, even if we fix ssh. For now I think ssh should be fixed. -Matt :On Sunday, February 11, 2001 03:41:48 -0500, Barney Wolff :[EMAIL PROTECTED] wrote: :+- :| Er, could it possibly be that telnet has been hiding the error :| all along? It's really, really hard to see how ssh could :| *create* this sort of error. :+---8 : :Someone mentioned earlier that sshd seemed to be setting SIGPIPE to SIG_IGN :in the child shell; that would lead to subprocesses getting EPIPE instead :of SIGPIPE, and typically the application reports the former and tar's :parent the latter, so the new error behavior would be expected. : :-- :brandon s. allbery [os/2][linux][solaris][japh] [EMAIL PROTECTED] :system administrator[WAY too many hats] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Mozilla build failure, 4-stable
At Sat, 10 Feb 2001 01:04:45 -0500, Barney Wolff wrote: Try anything BUT /usr/obj as WRKDIRPREFIX. /usr/obj/ports, for example. I found most or all ports fail to build if that specific directory is used. I have no idea why. man make and read .OBJDIR section. -- FUJISHIMA Satsuki To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
RE: 3.5-S-4.2-S: still fail w/ setresuid on miniperl
I've been having the exact same problem with the same upgrade for 3 days now. I keep cvsuping/making buildworld/etc, hoping that someone will fix it soon but it doesn't look like it's going to happen. For the amount of time I've spent so far, just trying to get it to work right, I could have formatted/re-installed/reconfigured. OF -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Pekka Savola Sent: Sunday, February 11, 2001 7:38 AM To: [EMAIL PROTECTED] Subject: 3.5-S-4.2-S: still fail w/ setresuid on miniperl Hello all, As a lot of others including some @FreeBSD.org people, I got: --- cd /usr/src/gnu/usr.bin/perl/miniperl make miniperl Extracting config.h (with variable substitutions) cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -c /usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5/minip erlmain.c ln -sf /usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5/op.c opmini.c cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -c opmini.c cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -L/usr/obj/usr/src/gnu/usr.bin/perl/miniperl/../libperl -static -o miniperl miniperlmain.o opmini.o /usr/obj/usr/src/gnu/usr.bin/perl/miniperl/../libperl/libperl.a -lm -lcrypt -lutil /usr/obj/usr/src/gnu/usr.bin/perl/miniperl/../libperl/libperl.a(pp_hot.o): In function `Perl_pp_aassign': pp_hot.o(.text+0x16a1): undefined reference to `setresuid' pp_hot.o(.text+0x16d4): undefined reference to `setresgid' *** Error code 1 --- while trying to update from the latest 3.5-S to 4.2-S. Both had been CVSupped within 24h. I followed the UPDATING instructions. make buildworld -DNOPERL works around this, of course. But shouldn't this be fixed? Or are 3.x users such a diminishing community it's not worth risking breaking the tree? For the record, I think these commits fubared the build (as 4.1-R has been reported to work): http://www.freebsd.org/cgi/cvsweb.cgi/src/gnu/usr.bin/perl/Makefil e.diff?r1=1.9r2=1.9.2.1 ITOH, I guess MFC'ing these change, it _might_ work again: http://www.freebsd.org/cgi/cvsweb.cgi/src/gnu/usr.bin/perl/Makefile.diff?r1= 1.12r2=1.13 Please Cc:. -- Pekka Savola "Tell me of difficulties surmounted, Netcore Oynot those you stumble over and fall" Systems. Networks. Security. -- Robert Jordan: A Crown of Swords To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 3.5-S-4.2-S: still fail w/ setresuid on miniperl
You have to do it from step to step. Not a one-time upgrade. Add the following option in you make.conf : NOPERL = true NOSUIDPERL = true then, you can issue 'make world' if it fails, you'll have to compile libc and install it before if you still have complains about miniperl, edit Makefiles and erase it from there Make sure you did not intstall FreeBSD 3.x with badblock scans. Otherwise after upgrade, you won't be able to boot anymore. FreeBSD 4.x is not able to handle file system marked with badblocks Nobody ever *cared* about it. So if you did use badblock scan on your file system, you'll have to install a FreeBSD 4.x from scratch Or else, stick with FreeBSD 3.x CHaiNeSS At 17:37 01-02-11 +0200, you wrote: Hello all, As a lot of others including some @FreeBSD.org people, I got: --- cd /usr/src/gnu/usr.bin/perl/miniperl make miniperl Extracting config.h (with variable substitutions) cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -c /usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5/miniperlmain.c ln -sf /usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5/op.c opmini.c cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -c opmini.c cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -L/usr/obj/usr/src/gnu/usr.bin/perl/miniperl/../libperl -static -o miniperl miniperlmain.o opmini.o /usr/obj/usr/src/gnu/usr.bin/perl/miniperl/../libperl/libperl.a -lm -lcrypt -lutil /usr/obj/usr/src/gnu/usr.bin/perl/miniperl/../libperl/libperl.a(pp_hot.o): In function `Perl_pp_aassign': pp_hot.o(.text+0x16a1): undefined reference to `setresuid' pp_hot.o(.text+0x16d4): undefined reference to `setresgid' *** Error code 1 --- while trying to update from the latest 3.5-S to 4.2-S. Both had been CVSupped within 24h. I followed the UPDATING instructions. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Mozilla build failure, 4-stable
Yes I understand the significance of /usr/obj, but not why, in detail, the port builds fail. In any case, if there are some specific directories that cause problems, perhaps bsd.port.mk should check for them and complain, rather than letting the build fail with baffling errors. Barney On Mon, Feb 12, 2001 at 07:19:56AM +0900, FUJISHIMA Satsuki wrote: At Sat, 10 Feb 2001 01:04:45 -0500, Barney Wolff wrote: Try anything BUT /usr/obj as WRKDIRPREFIX. /usr/obj/ports, for example. I found most or all ports fail to build if that specific directory is used. I have no idea why. man make and read .OBJDIR section. -- FUJISHIMA Satsuki To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
