Re: randomdev and APM. Not working together?
If I use randomdev for ssh, then APM seem to have stopped working. This is wierd; I am running this randomdev on my Libretto, (I wrote it there), and it and APM are both fine. Am I doing something wrong? No - you are doing everything right. Can you do any debugging on this? Are you able perhaps to trace the kernel and see where it fails? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/contrib/isc-dhcp - Imported sources
-On [2629 20:03], Garrett Wollman ([EMAIL PROTECTED]) wrote: On Thu, 29 Jun 2000 10:01:25 -0700, "David O'Brien" [EMAIL PROTECTED] said: 1. Everyone uses /bin/csh (show me a box that has never had root login at least once. I can show you several boxes where first thing root did after logging in was to configure itself for a Real Shell(tm). I personally would be much happier if root's default shell were /bin/sh (as it is on all of the new non-FreeBSD boxes we have around here). Although I agree 200% with your /bin/sh statement, heck I was one of the people advocating it on -arch, I think it is time we bury this dead horse once and for all. We have had this endless discussion on -arch, -committers got rigged with it and now we're infecting -current. Please put this noise to rest. Please. -- Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai No man is good enough to govern another man without the other's consent... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Missing module in current Perl
It seems that the newly added Errno module is not in the Makefile... Thanks! I've got a collection of perl tweaks that I'll be adding later. M Index: Makefile === RCS file: /home/ncvs/src/gnu/usr.bin/perl/library/Makefile,v retrieving revision 1.2 diff -u -2 -r1.2 Makefile --- Makefile 2000/06/27 15:28:10 1.2 +++ Makefile 2000/06/30 07:46:17 @@ -1,5 +1,5 @@ # $FreeBSD: src/gnu/usr.bin/perl/library/Makefile,v 1.2 2000/06/27 15:28:10 markm Exp $ -SUBDIR= B ByteLoader DB_File Dumper DProf Peek Fcntl Glob IO SysV \ +SUBDIR= B ByteLoader DB_File Dumper DProf Errno Peek Fcntl Glob IO SysV \ NDBM_File Opcode POSIX SDBM_File Socket Hostname Syslog attrs re -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- [EMAIL PROTECTED] The Postman hits! The Postman hits! You have new mail. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Buildworld successful
Around 10am PDT yesterday, -CURRENT built and installed without an error. Thanks! Excellent to know! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: perl6 first time build problem
I say "make cleandir; make obj; make depend;" in perl directory and got: Hi Do a "make build-tools" first. I'm working on getting this done properly into cross-tools. A real "make world" will also bootstrap you properly. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
current kernel build probs
Hi all, on june 30th I ftped the current kernel tree from ftp.uk.freebsd.org to test it on my 4.0-2608-stable machine. After I setup a config file with the .hints file I did make depend (duh) and found out that config needed to be updated (RTFM) I got usr.sbin from the current tree and did just that. After that make depend rocked and I started make to build the kernel. **First I got the error that crypto/blowfish didn't exhist. I looked in my 2000608 tree and found it. I copied the ./sys/crypto directory to my current tree and god rid of that problem. **After that I ran into the problem that I got an assembly error: cc -c -xassembler-with-cpp -DLOCORE -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2../../i386/i386/bioscall.s/tmp/cca13049.s: Assembler messages:/tmp/cca13049.s:773: Error: operands given don't match any known 386instruction/tmp/cca13049.s:838: Error: operands given don't match any known 386instruction*** Error code 1Stop in /usr/src/sys/compile/GATEWAY.I did a diff between this bioscall.s from current and 2000608-stable and found there to be small differences but I don't see a problem. root@kessen / diff bioscall.old bioscall.new26c26 * $FreeBSD: src/sys/i386/i386/bioscall.s,v 1.6 1999/08/28 00:43:41 peterExp $--- * $FreeBSD: src/sys/i386/i386/bioscall.s,v 1.7 2000/05/22 17:02:53 obrienExp $68c68 lcall _bioscall_vector--- lcall *_bioscall_vector133c133 lcall _bioscall_vector /* 16-bit call */--- lcall *_bioscall_vector /* 16-bit call */hmm. I don't see a problem, maybe I used diff wrongly butcopying the bioscall.s from 2000608-stable over the current one solves the problem anyway. **Now I have another small problem;) which is that the kernelcompile quits on an miibus problem: cc -O -pipe -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I/usr/include -mpreferred-stack-boundary=2 -c/usr/src/sys/modules/mii/../../dev/mii/ukphy_subr.ccc -O -pipe -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I/usr/include -mpreferred-stack-boundary=2 -c miibus_if.cmiibus_if.c: In function `MIIBUS_READREG':miibus_if.c:27: warning: implicit declaration of function `DEVOPMETH'miibus_if.c:27: `miibus_readreg' undeclared (first use in this function)miibus_if.c:27: (Each undeclared identifier is reported only oncemiibus_if.c:27: for each function it appears in.)miibus_if.c: In function `MIIBUS_WRITEREG':miibus_if.c:38: `miibus_writereg' undeclared (first use in this function)miibus_if.c: In function `MIIBUS_STATCHG':miibus_if.c:49: `miibus_statchg' undeclared (first use in this function)miibus_if.c: In function `MIIBUS_MEDIAINIT':miibus_if.c:60: `miibus_mediainit' undeclared (first use in this function)*** Error code 1Stop in /usr/src/sys/modules/mii.*** Error code 1Stop in /usr/src/sys/modules.*** Error code 1Stop in /usr/src/sys/compile/GATEWAY. Does anyone here experience this problem too? I tried using the 2000608-stable mii sources in the current tree but this doesn't make me a happy camper either;)(aka doesn't work) My kernel config files look like this: /usr/src/sys/i386/conf/GATEWAY : machinei386identGATEWAYmaxusers10hints"GATEWAY.hints"options MAXDSIZ="(32*1024*1024)"options DFLDSIZ="(32*1024*1024)"cpuI586_CPU# aka Pentium(tm)cpuI686_CPU# aka Pentium Pro(tm)options NO_F00F_HACKoptions COMPAT_43options SYSVSHMoptions SYSVSEMoptions SYSVMSGoptions USERCONFIG#boot -c editoroptions VISUAL_USERCONFIG#visual boot -c editoroptions INET#Internet communications protocolsdeviceether#Generic Ethernetdeviceloop1#Network loopback devicedevicebpf4#Berkeley packet filteroptions TCP_COMPAT_42#emulate 4.2BSD TCP bugsoptions IPFIREWALL#firewalloptions IPFIREWALL_VERBOSE#print information about dropped packetsoptions IPFIREWALL_FORWARD#enable transparent proxy supportoptions IPFIREWALL_VERBOSE_LIMIT=100#limit verbosityoptions IPFIREWALL_DEFAULT_TO_ACCEPT#allow everything by defaultoptions IPDIVERT#divert socketsoptions IPFILTER#ipfilter supportoptions IPFILTER_LOG#ipfilter loggingoptions IPSTEALTH#support for stealth forwardingoptions TCP_DROP_SYNFIN#drop TCP packets with SYN+FINoptions TCP_RESTRICT_RST#restrict emission of TCP RSToptions FFS#Fast filesystem#optionsFFS_EXTATTR#Extended attribute supportoptions NFS_NOSERVER#Disable the NFS-server code.options CD9660#ISO 9660 filesystemoptions PROCFS#Process filesystemoptions FFS_ROOT#FFS usable as root deviceoptions SOFTUPDATESoptions QUOTA#enable disk quotasoptions RANDOMDEVoptions
/sys hierarchy
Can somebody move thing around in sys? I mean put all fs code under let say '/sys/fs' subdir. And all network protocols code under /sys/net (or netproto)? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /sys hierarchy
On Sat, Jul 01, 2000 at 06:12:51PM +0400, Ilmar S. Habibulin wrote: Can somebody move thing around in sys? I mean put all fs code under let say '/sys/fs' subdir. And all network protocols code under /sys/net (or netproto)? Why? Because you like it better? Or to confuse the h*ck out of people who are used to the current tree? -- Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try" [EMAIL PROTECTED] http://www.nlfug.nl Yoda - The Empire Strikes Back To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /sys hierarchy
On Sat, 1 Jul 2000, Wilko Bulte wrote: Can somebody move thing around in sys? I mean put all fs code under let say '/sys/fs' subdir. And all network protocols code under /sys/net (or netproto)? Why? Because you like it better? Or to confuse the h*ck out of people who are used to the current tree? I think that it would be better because kernel become be better structured that way. Now we have more that 40 subdirs in /sys, 4 fs subdirs (isofs, fs, miscfs, ufs), 3 standalone fs dirs (msdosfs, ntfs and nwfs). isofs and fs subdirs are containing only one entry each. So why not to merge all this code under one subdir /sys/fs? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
/sys hierarchy
On Sat, 1 Jul 2000 18:12:51 +0400 (MSD), "Ilmar S. Habibulin" [EMAIL PROTECTED] said: Can somebody move thing around in sys? I mean put all fs code under let say '/sys/fs' subdir. And all network protocols code under /sys/net (or netproto)? Why? What benefit would that have? -GAWollman PS: Be careful how you answer this question. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: perl6 first time build problem
On Sat, Jul 01, 2000 at 12:55:25PM +0200, Mark Murray wrote: Do a "make build-tools" first. I'm working on getting this done properly into cross-tools. I found more quick manual way: 1) building/installing libperl 2) building/installing miniperl 3) to do the rest BTW, is there a way to add CFLAGS (highly-optimized for me) when building additional perl object modules? I see something with name 'cflags' extracted now, so it can helps maybe. This problem stays too long... -- Andrey A. Chernov [EMAIL PROTECTED] http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /sys hierarchy
On Sat, 1 Jul 2000, Garrett Wollman wrote: Can somebody move thing around in sys? I mean put all fs code under let say '/sys/fs' subdir. And all network protocols code under /sys/net (or netproto)? Why? What benefit would that have? Some order, i suppose. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld ok, but kernel fails
Yes, you missed the fact that crypto is now required to build the kernel. Put cvs-crypto in your cvsup file, cvsup, and try again. ^^ Does cvs-crypto replace src-crypto? I know it is in updating, but, before 2625, src-crypto was used. tomdean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld ok, but kernel fails
Yes, you missed the fact that crypto is now required to build the kernel. Put cvs-crypto in your cvsup file, cvsup, and try again. ^^ Does cvs-crypto replace src-crypto? It is a superset, and includes other stuff. See src/share/examples/cvsup/* M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
perl standard modules not installed properly (with fix)
This is after 'make world'. Just start perl and type 'use IO::Socket;' It seems that Errno.pm is not installed, i.e. contrib/perl5/ext/Errno is not handled. Fix included below: 61_# perl use IO::Socket; Can't locate Errno.pm in @INC (@INC contains: /usr/libdata/perl/5.006/mach /usr/libdata/perl/5.006 /usr/local/lib/perl5/site_perl/5.006/mach /usr/local/lib/perl5/site_perl/5.006 /usr/local/lib/perl5/site_perl/5.006 .) at /usr/libdata/perl/5.006/mach/IO/So cket.pm line 17. --- Makefile.bakTue Jun 27 19:28:10 2000 +++ MakefileSat Jul 1 20:41:46 2000 @@ -1,6 +1,6 @@ # $FreeBSD: src/gnu/usr.bin/perl/library/Makefile,v 1.2 2000/06/27 15:28:10 markm Exp $ -SUBDIR= B ByteLoader DB_File Dumper DProf Peek Fcntl Glob IO SysV \ +SUBDIR= B ByteLoader DB_File Dumper DProf Errno Peek Fcntl Glob IO SysV \ NDBM_File Opcode POSIX SDBM_File Socket Hostname Syslog attrs re all: man3pages -- Andrey A. Chernov [EMAIL PROTECTED] http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: perl standard modules not installed properly (with fix)
This is after 'make world'. Just start perl and type 'use IO::Socket;' It seems that Errno.pm is not installed, i.e. contrib/perl5/ext/Errno is not handled. Fix included below: Thanks! I've got this and some other tweaks commit-ready; I'll do them tomorrow... M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Xbatt now fails on -current
I used to run (well I still do, but it fails) xbatt. It used to give an accurate picture of the state of my batteries. in the last week, xbatt no-longer runs. it complains that jules# xbatt xbatt: cannot open apm device (/dev/apm0 or /dev/apm): Device not configured jules# Is there something else I need to add? (I have device apm in the config file) -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000 )_.---._/ presently in: Budapest v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld ok, but kernel fails
I used the attached supfile in 6/30. I have used it for a couple of years. Now, it does not fetch all the 'blowfish collection. Is this a hole in using the individual names? I will switch to cvs-crypto. tomdean === supfile = *default host=cvsup.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix *default compress src-all src-eBones src-secure src-crypto doc-all ports-all To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld ok, but kernel fails
Hi Check /usr/src/share/examples/cvsup/* M I used the attached supfile in 6/30. I have used it for a couple of years. Now, it does not fetch all the 'blowfish collection. Is this a hole in using the individual names? I will switch to cvs-crypto. tomdean === supfile = *default host=cvsup.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix *default compress src-all src-eBones src-secure src-crypto doc-all ports-all -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /sys hierarchy
On Sat, Jul 01, 2000 at 07:14:35PM +0400, Ilmar S. Habibulin wrote: Some order, i suppose. There is plenty of order in the current system. Garrett Wollman suggested that you answer this question carefully, and you have not done that, but provide a vague summary of your beliefs. Moreover, many people are used to the current system; changing it is a fundamental, non-trivial job. This requires good reasoning. -- Will Andrews [EMAIL PROTECTED] [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /sys hierarchy
On Sat, Jul 01, 2000 at 01:26:17PM -0400, Will Andrews wrote: On Sat, Jul 01, 2000 at 07:14:35PM +0400, Ilmar S. Habibulin wrote: Some order, i suppose. There is plenty of order in the current system. Feh. Garrett Wollman suggested that you answer this question carefully, and you have not done that, but provide a vague summary of your beliefs. Yes he did. Talk to various committers and you'll see that many have ideas where files should live. There have been long threads on this issue that got nowhere. The reason things are in such a messy state is when something new is brought in, or is changed suffiently much for a repo copy the person take the chance to put the files where *they* think they should live. Vs. where there would be consistency in the /sys tree. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current kernel build probs
On Sat, Jul 01, 2000 at 03:31:04PM +0200, B.O.F.H. at kessen.yi.org wrote: on june 30th I ftped the current kernel tree from ftp.uk.freebsd.org to test it on my 4.0-2608-stable machine. Huh... you are now mixing a 5-CURRENT (ie, CVS head branch) kernel source with a 4-STABLE (ie, RELENG_4) world [in this case toolchain]. What in the world make you think this would work? cc -c -x assembler-with-cpp -DLOCORE -O -Wall -Wredundant-decls -Wnested-externs -Wst If you would do ``as -v'' you will see you have GAS version 2.9.1. /tmp/cca13049.s: Assembler messages: /tmp/cca13049.s:773: Error: operands given don't match any known 386 instruction /tmp/cca13049.s:838: Error: operands given don't match any known 386 This is because your /usr/src tree is now bogusly out of sync. I did a diff between this bioscall.s from current and 2000608-stable and found there to be small differences but I don't see a problem. Since there *is* a difference, it must be the problem. root@kessen / diff bioscall.old bioscall.new 68c68 lcall _bioscall_vector --- lcall *_bioscall_vector The ATT ASM syntax requires "*" in front of indirect calls. Unfortuneatly GAS 2.9.1 was brain damaged and doesn't understand it as it should. Goodness knows how GAS 2.9.1 figures out how to do the right thing, but it mostly does. However, 5-CURRENT now has GAS 2.10.0 as the assembler. It has been *VASTLY* improved and now accepts and adhears much more strictly to the ATT i386 ASM syntax. Without the leading "*", GAS 2.10.0 is very unhappy with the instruction. hmm. I don't see a problem, maybe I used diff wrongly but copying the bioscall.s from 2000608-stable over the current one solves the problem anyway. I REALLY have to ask what you are trying to accomplish here. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /sys hierarchy
In message [EMAIL PROTECTED], "David O'Brien" writes: On Sat, Jul 01, 2000 at 01:26:17PM -0400, Will Andrews wrote: On Sat, Jul 01, 2000 at 07:14:35PM +0400, Ilmar S. Habibulin wrote: Some order, i suppose. There is plenty of order in the current system. Feh. Garrett Wollman suggested that you answer this question carefully, and you have not done that, but provide a vague summary of your beliefs. Yes he did. Talk to various committers and you'll see that many have ideas where files should live. There have been long threads on this issue that got nowhere. The reason things are in such a messy state is when something new is brought in, or is changed suffiently much for a repo copy the person take the chance to put the files where *they* think they should live. Vs. where there would be consistency in the /sys tree. In fact, I belive there actually was a consensus for moving filesystems under /sys/fs but not for moving net*. The reason for the difference in concensus is probably that net* is a systematic prefix. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bug: kernel hangs at boot
On Fri, Jun 30, 2000 at 06:29:11AM -0700, Andrey A. Chernov wrote: On Wed, Jun 28, 2000 at 11:03:22PM -0700, Andrey A. Chernov wrote: Fresh -current kernel with fresh -current bootblocks loaded ok but hangs in boot (no diagnostics even printed, just silent hang with "/" on the screen). Kernel from Jun14 with fresh -current bootblocks (i.e. the same bootblocks) booted Ok. The reason found. I have "-O2 pipe" instead of default "-O pipe", but I have it working all the time from very beginning. Why this becomes broken? BTW, -march=pentiumpro still worked Ok -- Andrey A. Chernov [EMAIL PROTECTED] http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /sys hierarchy
Yes he did. Talk to various committers and you'll see that many have ideas where files should live. There have been long threads on this issue that got nowhere. The reason things are in such a messy state is when something new is brought in, or is changed suffiently much for a repo copy the person take the chance to put the files where *they* think they should live. Vs. where there would be consistency in the /sys tree. Talking to "various committers" will only yield various opinions and end up leading nowhere, however. Perhaps if someone were to take it upon themselves to post a detailed proposal of where things should be moved to, others could at least comment more authoritatively (and substantially) on the topic rather than just engaging in more vague hand-waving. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld ok, but kernel fails
On Sat, 1 Jul 2000, Mark Murray wrote: Yes, you missed the fact that crypto is now required to build the kernel. Put cvs-crypto in your cvsup file, cvsup, and try again. ^^ Does cvs-crypto replace src-crypto? It is a superset, and includes other stuff. See src/share/examples/cvsup/* OK, I am guilty. Did not study the cvs-all messages sufficiently in detail :-) -- Marc Schneiders --- [EMAIL PROTECTED] --- [EMAIL PROTECTED] FreeBSD unclad.freebeastie.org 5.0-CURRENT (SMP) NetBSD vax.freebeastie.org 1.4Y To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
perl, cron or sh bug
On Sat, Jul 01, 2000 at 07:00:07PM +0200, Mark Murray wrote: I've got this and some other tweaks commit-ready; I'll do them tomorrow... When running as cron job, from shell script, perl now always say this: "Can't ignore signal CHLD, forcing to default" (see perl.c) I am not shure, is this cron bug calling with ignoring SIGCHLD, sh bug, or perl bug. I think cron shouldn't call anything with SIGCHLD ignored. -- Andrey A. Chernov [EMAIL PROTECTED] http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: perl, cron or sh bug
On Sat, Jul 01, 2000 at 01:49:07PM -0700, Andrey A. Chernov wrote: On Sat, Jul 01, 2000 at 07:00:07PM +0200, Mark Murray wrote: I've got this and some other tweaks commit-ready; I'll do them tomorrow... When running as cron job, from shell script, perl now always say this: "Can't ignore signal CHLD, forcing to default" (see perl.c) I am not shure, is this cron bug calling with ignoring SIGCHLD, sh bug, or perl bug. I think cron shouldn't call anything with SIGCHLD ignored. Yes, it was in cron/do_command.c (void) signal(SIGCHLD, SIG_IGN); What about re-allowing SIGCHLD after second fork (i.e.vfork), just before execle()? Any objections? -- Andrey A. Chernov [EMAIL PROTECTED] http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: perl, cron or sh bug
On Sat, Jul 01, 2000 at 02:03:01PM -0700, Andrey A. Chernov wrote: On Sat, Jul 01, 2000 at 01:49:07PM -0700, Andrey A. Chernov wrote: On Sat, Jul 01, 2000 at 07:00:07PM +0200, Mark Murray wrote: I've got this and some other tweaks commit-ready; I'll do them tomorrow... When running as cron job, from shell script, perl now always say this: "Can't ignore signal CHLD, forcing to default" (see perl.c) I am not shure, is this cron bug calling with ignoring SIGCHLD, sh bug, or perl bug. I think cron shouldn't call anything with SIGCHLD ignored. Yes, it was in cron/do_command.c (void) signal(SIGCHLD, SIG_IGN); What about re-allowing SIGCHLD after second fork (i.e.vfork), just before execle()? Any objections? OpenBSD already have simpler fix in rev 1.7 (below). I'll think which way is better... - Set SIGCHLD to SIG_DFL not SIG_IGN to prevent "perl -w" from complaining "Can't ignore signal CHLD, forcing to default". Setting SIGCHLD to SIG_IGN means "don't provide exit status for my children" on some OSes which is not what we want--we just don't want to catch SIGCHLD since our parent does that for us. - -- Andrey A. Chernov [EMAIL PROTECTED] http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
cvs-cur.6450.gz Fatal error: Bytecount too large.
After some absence from the net (my machines were in a box between Australia Houston) I've finaaly connected up and am updating my cvs repository via CTM again. However, when I attempt to apply cvs-cur.6450.gz I get the above error. Anybody got a good one? Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true."Robert Wilensky, University of California To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: coldsync - Visor kernel panic / bug #17961
Nothing has happened so far. I have a handspring now, but lack the time currently to fix it. I'll have a go at it tomorrow if there is some time left. Nick On Tue, 27 Jun 2000, Sascha Lucky Luck wrote: Hi all, what is the story with this bug? (If you want a hand with testing patches, etc., please drop me a mail) I'm running 5.0-CURRENT (Jun 20) Hardware: Jun 26 15:34:28 bofh /kernel: usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 Jun 26 15:34:28 bofh /kernel: usb0: USB revision 1.0 Jun 26 15:34:28 bofh /kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1. 00, addr 1 Jun 26 15:34:28 bofh /kernel: uhub0: 2 ports with 2 removable, self powered Jun 26 15:34:28 bofh /kernel: uhub1: vendor 0x0698 product 0x, class 9/1, re v 1.00/0.01, addr 2 Jun 26 15:34:28 bofh /kernel: uhub1: 5 ports with 4 removable, self powered Jun 26 15:34:28 bofh /kernel: uhid0: vendor 0x0698 product 0x1786, rev 1.00/0.01 , addr 3, iclass 3/0 and the Visor: Jun 26 17:13:43 bofh /kernel: ugen0: Handspring Inc Handspring Visor, rev 1.00/1.00, addr 4 Thanks in advance, s. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
new sound card
Alright, this just bit me in the ass... I just bought a card today that says "Creative Ensoniq AudioPCI" on the box. Well, as far as I can tell this card uses the es1371 chip. Well, I did a little digging because apparently the card's pci device id wasn't in the es137x.c file. So what I did was I put it in the file, and tried to make it configure as a 1371 chip. However I got an error when I did this: pcm0: AudioPCI ES1371 port 0xe400-0xe43f irq 11 at device 9.0 on pci0 pcm0: ac97 codec invalid or not present (id == 0) The mixer would not configure with this, and the driver wouldn't attach, so I went to ac97.c and found the error message, and commented out the "return ENODEV" statement so that I could make it attach the driver and see what would happen. Well, when I did that, I got another error in addition to the 2 above: pcm0: ac97 codec reports dac not ready however, the driver attaached, and I can use the mixer devices, and I can play CD's, but pcm audio still won't play, and there are no errors on the console when I try to play mp3's or any other kind of sounds. So I guess my question is: is anyone working on getting the device with id 0x58801274 (the closest card originally listed in the file was: 0x50001274) to work? Or does anyone already have this card working? Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
more info on sound card
I managed to find a little more info on this chip in my new soundcard. It is slightly different from a regular es1371... and in linux it even get's some of its own #defines: CT5880REV_CT5880_C is it's revision. (or 0x02) and the chip says CT5880 on it. I'm assuming it's not much different, but so far in the linux driver, there are a couple of little differences between this chip and the regular 1371. If I get this working, I'll submit whatever I did to the driver to make it work, but I may need a little help here. Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Help with Linux interpreter
I was able to install the acroread4 port on my -current machine of a week or two ago. I find when I try to run acroread4 I get the following error: ELF interpreter /lib/ld-linux.so.2 not found Abort But /compat/linux/lib/ld-linux.so.2 exists and points to ld-2.1.2.so, which also exists. It was branded as SVR4, and I changed this to Linux, but that didn't help. What am I doing wrong? I reinstalled all the ports in the chain of acroread4. I've also done a rm -rf /usr/compat/linux; mkdir /usr/compat/linux (/compat - /usr/compat on my system). What other information do you need to help me? Also, I think there's a fd leak in brandelf: brandelf * ... File 'libresolv-2.1.2.so' is of brand 'Linux' (3). File 'libresolv.so.2' is of brand 'Linux' (3). brandelf: error opening file librt-2.1.2.so: Too many open files brandelf: error opening file librt.so.1: Too many open files brandelf: error opening file libtermcap.so.2: Too many open files brandelf: error opening file libtermcap.so.2.0.8: Too many open files ... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
patches for my new soundcard
I just got the soundcard to work, patches to /usr/src/sys/dev/sound/pci/ess137x.c are coming in a minute. Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
patch to be committed please?
Here is a patch with the changes I made to get my soundcard to work. It
was pretty simple, it was just a matter of one more id that needed to be
added so that the ac97 stuff could be turned on. It was trying to do a
pre-ac97 2.1 init instead of what I should have been doing. Anyway, it
works now. :-)
Here it is:
--- es137x.c.oldSun May 28 11:15:14 2000
+++ es137x.cSat Jul 1 23:22:00 2000
@@ -68,6 +68,7 @@
#define ES1370_PCI_ID 0x50001274
#define ES1371_PCI_ID 0x13711274
#define ES1371_PCI_ID2 0x13713274
+#define ES1371_PCI_ID3 0x58801274
#define ES_BUFFSIZE 4096
@@ -493,7 +494,7 @@
es-ctrl = 0;
es-sctrl = 0;
/* initialize the chips */
- if (rev == 7 || rev = 9) {
+ if (rev == 7 || rev = 9 || rev == 2) {
#define ES1371_BINTSUMM_OFF 0x07
bus_space_write_4(es-st, es-sh, ES1371_BINTSUMM_OFF, 0x20);
if (debug 0) printf("es_init rev == 7 || rev = 9\n");
@@ -724,7 +725,8 @@
device_set_desc(dev, "AudioPCI ES1370");
return 0;
} else if (pci_get_devid(dev) == ES1371_PCI_ID ||
- pci_get_devid(dev) == ES1371_PCI_ID2) {
+ pci_get_devid(dev) == ES1371_PCI_ID2 ||
+ pci_get_devid(dev) == ES1371_PCI_ID3) {
device_set_desc(dev, "AudioPCI ES1371");
return 0;
}
@@ -789,7 +791,8 @@
}
if (pci_get_devid(dev) == ES1371_PCI_ID ||
- pci_get_devid(dev) == ES1371_PCI_ID2) {
+ pci_get_devid(dev) == ES1371_PCI_ID2 ||
+ pci_get_devid(dev) == ES1371_PCI_ID3) {
if(-1 == es1371_init(es, pci_get_revid(dev))) {
device_printf(dev, "unable to initialize the card\n");
goto bad;
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
