Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?
Date: Fri, 12 Nov 1999 17:23:21 -0800 From: "David O'Brien" <[EMAIL PROTECTED]> I assume "--ignore-binary" or "--ignore-binary-files" would be the GNU longopt. Another possibility would be to follow the example of the existing --directories=ACTION option, e.g. something like this: --binary-files=ACTION how to handle binary files ACTION is 'read', 'skip', or 'summarize' (default) -I equivalent to --binary-files=skip -a, --text equivalent to --binary-files=read To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
objformat troubles in make release
Something must have changed somewhere very recently, but I cannot see what. Make release (current on current of four or five days old) worked ok two days ago, now it stops after a few minutes over objformat not found (full output below). I've tried to set it manually (setenv OBJFORMAT=elf) and it is of course in /usr/src/release/Makefile. Any suggestion? Thanks! Marc [after "MAKEDEV all" and some little bits in /usr/src/etc:] cd /usr/src/release/.. && make installworld DESTDIR=/reserve NOMAN=1 cd /usr/src; PATH=/usr/obj/usr/src/tmp/sbin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/bin:/usr/obj/usr/src/tmp/usr/bin BISON_SIMPLE=/usr/obj/usr/src/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/obj/usr/src/tmp/usr/bin GCC_EXEC_PREFIX=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib/ LD_LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib PERL5LIB=/reserve/usr/libdata/perl/5.00503 OBJFORMAT_PATH=/usr/obj/usr/src/tmp/usr/libexec CFLAGS="-nostdinc -O -pipe" /usr/obj/usr/src/tmp/usr/bin/make -f Makefile.inc1 reinstall objformat: not found "/usr/src/Makefile.inc1", line 972: warning: "objformat" returned non-zero status echo:No such file or directory *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. Marc Schneiders [EMAIL PROTECTED] [EMAIL PROTECTED] propro4:20am up 1 day, 16:06, load average: 0.03 0.06 0.07 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: shell pipeline bug
> Simplified example:
>
> sh -c "jot 6000 | cat | head"
Not knowing what jot(1) was, I read the man page. The synopsis says:
SYNOPSIS
jot [-cnr] [-b word] [-w word] [-s string] [-p precision] [reps [begin
^
[end [s
^
...so I type in:
$ jot
usage: jot [-cnr] [-b word] [-w word] [-s string] [-p precision]
[reps [begin [end [s
^ ^
Is my understanding correct that options in square brackets are optional?
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: "man" reads /etc/rc.conf?
On Wed, 10 Nov 1999, Alexander Leidinger wrote: > On 11 Nov, Daniel C. Sobral wrote: > >> >> (102) netchild@ttyp2 > grep cat /etc/rc.conf.local > >> >> spppconfig_isp0="`cat /etc/isdn/connect.parameters`" > >^^^ > > Calling programs from any of the rc.conf files is considered evil > > and it's looked down on. > > It´s there to hide login/passwd information for i4b. But it seems like the end up as arguments to ifconfig at a later date, where a user can pull them out of ps, /proc, etc. The window there is clearly shorter than keeping it in /etc/rc.conf, but still not "secure" per se. The same goes for the use of environmental variables, which can also be listed using ps. Probably spppconfig should accept a filename with the contents as an argument, or the information via a pipe. Robert N M Watson [EMAIL PROTECTED] http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?
On Fri, Nov 12, 1999 at 08:09:24PM -0500, Alain Magloire wrote: > > Cool! :-) Would you able to reserve the option's letter and GNU-style > > long name now? I'd like to add this feature to GNU Grep 2.3 in FreeBSD. > > -a, --text > is already taken. I assume "--ignore-binary" or "--ignore-binary-files" would be the GNU longopt. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pnp and AWE64
At 04:32 PM 11/12/1999 -0800, Alex Zepeda wrote: >On Thu, 11 Nov 1999, Jim King wrote: > > > I just picked up an AWE64 to use until the Vortex2 driver is working. The > > card is detected in Win98, but unfortunately the new PnP code in -current > > (cvsup'ed this evening) doesn't seem to find this card at all. Nothing > > shows up about it in dmesg; pnpinfo shows my ISA PnP modem, but nothing at > > all about the AWE64. > >FWIW it detects my AWE64 just fine (and yes you must set the PnP OS bit to >no). This is with or without the PNPBIOS option int he kernel. It >doesn't seem to detect the integrated Yamaha sound bits though (with the >PNPBIOS bit). > >pcm1: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq >5 drq 1,5 on isa0 > >How about posting your kernel config file? Attached, in all it's glory. The relevant lines seem to be: controller pnp0 device pcm0 options PNPBIOS The PNPBIOS line doesn't make a difference for the AWE64 (although it does make some difference - all the motherboard resources show up as unknowns with it enabled). # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # #http://www.freebsd.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.ORG/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.196 1999/10/22 04:36:52 n_hibma Exp $ machine i386 #cpuI386_CPU #cpuI486_CPU #cpuI586_CPU cpu I686_CPU ident RASP maxusers64 #makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols #optionsMATH_EMULATE#Support for x87 emulation options INET#InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT#MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_ROOT#NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5000 #Be pessimistic about Joe SCSI device options UCONSOLE#Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options SOFTUPDATES options PNPBIOS # To make an SMP kernel, the next two are needed #optionsSMP # Symmetric MultiProcessor Kernel #optionsAPIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #optionsNCPU=2 # number of CPUs #optionsNBUS=4 # number of busses #optionsNAPIC=1 # number of IO APICs #optionsNINTR=24# number of INTs controller isa0 controller pnp0# PnP support for ISA #controller eisa0 controller pci0 # Floppy drives controller fdc0at isa? port IO_FD1 irq 6 drq 2 diskfd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 # IDE controller and disks controller wdc0at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff diskwd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 controller wdc1at isa? port IO_WD2 irq 15 flags 0xa0ffa0ff #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 # ATAPI devices on wdc? device wcd0#IDE CD-ROM device wfd0#IDE Floppy (e.g. LS-120) device wst0#IDE Tape (e.g. Travan) # SCSI Controllers # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. controller ncr0# NCR/S
Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?
Bonjour M. David O'Brien > On Fri, Nov 12, 1999 at 03:39:43PM -0800, Paul Eggert wrote: > >Date: Fri, 12 Nov 1999 09:08:24 -0800 > >From: "David O'Brien" <[EMAIL PROTECTED]> > > > >I want a silent ignore of binary files. > > > > It'd be reasonable to add an option to do this, after the feature > > freeze is over and 2.4 comes out. > > Cool! :-) Would you able to reserve the option's letter and GNU-style > long name now? I'd like to add this feature to GNU Grep 2.3 in FreeBSD. > -a, --text is already taken. Option letter is something rather scarce for GNU grep, but I think there's some left ;-) > Is there an alpha of 2.4 available anywhere? I wouldn't mind adding the > environmental vars support to our 2.3 also. > grep-2.3h beta released (Freeze). wget ftp://alpha.gnu.org/gnu/grep/grep-2.3h.tar.gz wget ftp://mccoy.ee.mcgill.ca/pub/alain/grep/beta/2.3/grep-2.3h.tar.gz -- au revoir, alain Aussi haut que l'on soit assis, on est toujours assis que sur son cul !!! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: egcs unstable
According to Kevin Street: > this. My xemacs has been core dumping after each build and install of > world the last couple of times I did it. I have not had time to > investigate the real cause yet. I got the same problem between 3.3-R and 3.3-STABLE as well. Recompiling fixed it. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?
Bonjour M. David O'Brien > FreeBSD's previous grep had a "-a" flag to ignore binary files. Thus I'm > trying to find a replacement for the old ``grep -al'' usage. > > > In the coming 2.4, if this is such problem for you, there is en environ > > variable, that will restore the 2.0 behaviour(everything is text) > > Not quite what I'm looking for. I want a silent ignore of binary files. > I think it should take an option to not ignore binary files. Add 2.3's > "-a" if you *really* want full greping of binary files. > Thanks, for the clarifications. It is "dommage" (too bad ?) that the changes were not sent back to gnu. -- au revoir, alain Aussi haut que l'on soit assis, on est toujours assis que sur son cul !!! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pnp and AWE64
On Thu, 11 Nov 1999, Jim King wrote: > I just picked up an AWE64 to use until the Vortex2 driver is working. The > card is detected in Win98, but unfortunately the new PnP code in -current > (cvsup'ed this evening) doesn't seem to find this card at all. Nothing > shows up about it in dmesg; pnpinfo shows my ISA PnP modem, but nothing at > all about the AWE64. FWIW it detects my AWE64 just fine (and yes you must set the PnP OS bit to no). This is with or without the PNPBIOS option int he kernel. It doesn't seem to detect the integrated Yamaha sound bits though (with the PNPBIOS bit). pcm1: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 How about posting your kernel config file? - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?
On Fri, Nov 12, 1999 at 03:39:43PM -0800, Paul Eggert wrote: >Date: Fri, 12 Nov 1999 09:08:24 -0800 >From: "David O'Brien" <[EMAIL PROTECTED]> > >I want a silent ignore of binary files. > > It'd be reasonable to add an option to do this, after the feature > freeze is over and 2.4 comes out. Cool! :-) Would you able to reserve the option's letter and GNU-style long name now? I'd like to add this feature to GNU Grep 2.3 in FreeBSD. Is there an alpha of 2.4 available anywhere? I wouldn't mind adding the environmental vars support to our 2.3 also. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
fstat(1) breakage + fix
Hi, fstat(1) should be able to take a set of filenames as arguments to limit the results of its output to the specified files. However, it doesn't work at the moment, because of the existance of udev_t. (It compares the st_dev from the stat structure used by stat(2) with in-kernel dev_t structures. As it stands, "fstat " will never produce any output other than a header.) I've attached a patch that appears reliable. Can someone review it (and possibly commit??) -- Peter. _ Get your free E-mail at http://www.ireland.com fstat.c.patch
Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?
Date: Fri, 12 Nov 1999 09:08:24 -0800 From: "David O'Brien" <[EMAIL PROTECTED]> I want a silent ignore of binary files. It'd be reasonable to add an option to do this, after the feature freeze is over and 2.4 comes out. I think it should take an option to not ignore binary files. I disagree. If I type `grep pattern file' and get no output, then I should be able to conclude that there are no instances of `pattern' in `file'. But under your proposal, I wouldn't be able to conclude that: all I would know is that either the file contained no instances, or the file was binary. This is confusing and is less useful in practice than grep 2.3's behavior. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new kernel.
Ok..in addition to my earlier post, I am NOT using Linux netscape and I built the whole system from the source code. dist/module/kernel they are all from the same source tree. The thing is I never had this kind of problem before. It was working fine then. I built the world/kernel at Tue Nov 9 20:02:29 and configuration is not that different from GENERIC except it has firewall, sound, and new ata0 controller/driver support(I am using Promise Tech. Ultra66 controller card) included. At startup, I don't even have linux module loaded up. the only modules i use at startup is vinum. If nobody else is experiencing this, maybe I will sup it again and compile everything(takes 2.5 hrs so i can't do it everyday) from the new source tree and see what happens. Thanks for your comments. On Thu, 11 Nov 1999, Alfred Perlstein wrote: > On Thu, 11 Nov 1999, Byung Yang wrote: > > > > > I supped two days ago and compiled everything. Now, if I try to launch > > netscape, the computer just freezes right up there. First, I thought it > > was the netscape, but when I was searching for a file on my computer, but > > took longer than I thought and pressed ^C, it froze again. > > > > I heard and also suspect that this has something to do with the new signal > > algorithm.. does anybody experience this? > > Yes, but... what kind of configuration do you have? Since my crystal > ball is in the shop I really have no way of dicerning what's going on. > > -Alfred > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/isa isa_common.c
Sorry, but is there any driver for YMF724 except for OSS? If so (even in some under-pre-alpha state) I'd be more than happy to test it. On Thu, 11 Nov 1999, Doug Rabson wrote: > dfr 1999/11/11 08:48:01 PST > > Modified files: > sys/isa isa_common.c > Log: > Reorganise the code so that I can add custom identify drivers dynamically > during autoconfig to support strange hardware (such as the Yamaha DS-1) > which implements 'legacy' ISA devices as well as a PCI device. This will > allow the PCI driver for the YMF724 to add the legacy devices to the ISA > bus and will allow the PnP system to automatically allocate the resources > for those devices. > > Revision ChangesPath > 1.12 +72 -2 src/sys/isa/isa_common.c > > Thanks in advance, Vladimir (who's getting sort of desperate). -- ===|=== Vladimir Kushnir | [EMAIL PROTECTED], |Powered by FreeBSD [EMAIL PROTECTED] | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pnp and AWE64
On Fri, 12 Nov 1999, Jim King wrote: > At 10:50 PM 11/11/1999 -0600, Jim King wrote: > >I just picked up an AWE64 to use until the Vortex2 driver is working. The > >card is detected in Win98, but unfortunately the new PnP code in -current > >(cvsup'ed this evening) doesn't seem to find this card at all. Nothing > >shows up about it in dmesg; pnpinfo shows my ISA PnP modem, but nothing at > >all about the AWE64. > > One more bit of info: this PC (Dell Dimension R450) has a Phoenix BIOS, > which has a setting "Plug-n-Play OS? Yes/No". Changing it from No to Yes > made the kernel find the AWE64. Unfortunately changing that setting also > made the 3C905B NIC quit working: > > xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 11 at device 13.0 on pci0 > xl0: couldn't map ports/memory > device_probe_and_attach: xl0 attach returned 6 > > Another oddity: Although the AWE64 gets picked up by the pcm driver, > pnpinfo still only shows the PnP modem - no mention of the AWE64. FreeBSD isn't a fully PnP OS since it doesn't do resource allocation for pci. You must leave the setting at No. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: shell pipeline bug
In <[EMAIL PROTECTED]>, Bruce Evans wrote: > On Fri, 12 Nov 1999, Martin Cracauer wrote: > > > In <[EMAIL PROTECTED]>, Bruce Evans wrote: > > > `man sh' now hangs when the pager is exited. This is caused by the recent > > > change to sh/eval.c > > > > My fix in 1.23 of eval.c was broken, but Steve repaired it in 1.24. > > > > Do you have 1.24? > > Yes, of course. Sorry, I can reproduce the hangs with 1.23, while I can't with 1.24. The problem is: A pipe with more data that sh's threshold for forking is and the receiving end process exits before the sending process, not consuming all of the pipe's contents. That exactly what 1.24 fixed (for me :-). Martin -- % Martin Cracauer <[EMAIL PROTECTED]> http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: shell pipeline bug
On Fri, 12 Nov 1999, Martin Cracauer wrote: > In <[EMAIL PROTECTED]>, Bruce Evans wrote: > > `man sh' now hangs when the pager is exited. This is caused by the recent > > change to sh/eval.c > > My fix in 1.23 of eval.c was broken, but Steve repaired it in 1.24. > > Do you have 1.24? Yes, of course. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?
On Thu, Nov 11, 1999 at 09:13:54PM -0500, Alain Magloire wrote: > Of course, you can. But I will join my voice to Paul and ask you not to. > This behaviour was a long standing request/grip where for example one > would do > > grep pattern * > > and have the terminal going bananas, if pattern was detected in binary What I was proposing to change was that binary files were ignored when "-l" was in affect. I was also implying that binary files should be silently ignored unless one uses the 2.3 "-a" flag. > I don't follow your logic for '-l'. whether it is grep-2.0 or grep-2.3 > They all show the filename containing a matching pattern. FreeBSD's previous grep had a "-a" flag to ignore binary files. Thus I'm trying to find a replacement for the old ``grep -al'' usage. > In the coming 2.4, if this is such problem for you, there is en environ > variable, that will restore the 2.0 behaviour(everything is text) Not quite what I'm looking for. I want a silent ignore of binary files. I think it should take an option to not ignore binary files. Add 2.3's "-a" if you *really* want full greping of binary files. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: shell pipeline bug
In <[EMAIL PROTECTED]>, Bruce Evans wrote: > `man sh' now hangs when the pager is exited. This is caused by the recent > change to sh/eval.c My fix in 1.23 of eval.c was broken, but Steve repaired it in 1.24. Do you have 1.24? Martin -- % Martin Cracauer <[EMAIL PROTECTED]> http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: egcs unstable
Marcel Moolenaar <[EMAIL PROTECTED]> writes: > After (by accident) compiling world (excluding kernel) with optimization > disabled (ie -O0) and installing the resulting binaries, xemacs (21.1.7) > coredumps with a bus error. I recompiled and reinstalled xemacs and all > was fine. Now, after building and installing world (excluding kernel > again) with optimization (ie -O), xemacs does exactly the same: core > dumps on bus error. I'll recompile xemacs again and expect it to be > solved, but something is definitely broken: xemacs should not core dump > after recompiling world with only a simple change in compiler flags. I don't believe that it's the compiler flag change that is causing this. My xemacs has been core dumping after each build and install of world the last couple of times I did it. I have not had time to investigate the real cause yet. -- Kevin Street [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?
On Fri, Nov 12, 1999 at 12:11:22AM -0800, Paul Eggert wrote: >Date: Thu, 11 Nov 1999 23:39:10 -0800 >From: "David O'Brien" <[EMAIL PROTECTED]> > >Would it be possible to either ignore binary files when "-l" is in >affect. OR to add an ignore binary file flag (like FreeBSD has in >2.x and 3.x)? > > The latter sounds reasonable, though it'd have to be spelled > differently from -a since -a is now taken. Perhaps > --skip-binary-files, by analogy with the existing --directories=skip > option? The BSD's favor one letter options. At the time -a was not used for anything. Is there a letter we could use today? I used -a almost all the time, so typing "--skip-binary-files" would have been unacceptable. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
shell pipeline bug
`man sh' now hangs when the pager is exited. This is caused by the recent change to sh/eval.c Simplified example: sh -c "jot 6000 | cat | head" hangs. This example is almost minimal. The size of the data written by the first command must be large enough to not fit in the pipe; the middle command must be there, and the last command in the pipe must exit before reading all the data. The middle command should be killed by SIGPIPE when its output pipe is closed; this output pipe should be closed when the final command exits, but this is not happening because the shell is holding it open. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: nexus_setup_intr: NULL irq resource!
Bruce Evans wrote: > On Fri, 12 Nov 1999, Peter Jeremy wrote: > > > On 1999-Nov-12 12:35:01 +1100, Mark Newton wrote: > > >The problem is that the BUS_SETUP_INTR() method for ISA seems to > > >absolutely require the specification of an IRQ, even though IRQ > > >specification is absolutely prohibited for non-master ports in > > >AST-compatible multi-port sio cards. Gah. > > This is fixed differently (directly in the driver) in nsio (dev/sio/sio.c) > rev.1.267. Both fixes are probably necessary and more or less correct. > Drivers shouldn't attempt to register null interrupts, and attempting > this probably shouldn't cause panics. > > > As an aside, why doesn't our SIO driver work with ports that don't > > have interrupts? > > Same problem. Ports that don't have interrupts give polled mode, and > the driver shouldn't attempt to register the null interrupts for polled > mode, but this was broken when the driver was converted to new-bus. > > > >I'm not completely sure that this patch does the right thing > > > > Since your patch effectively turns isa_setup_intr() into a nop for > > this case, a better patch would seem to be to skip the call to > > BUS_SETUP_INTR() (and presumably bus_alloc_resource()) at the end > > of sioattach() when you're attaching a slave SIO port. > > nsio still has the bus_alloc_resource(). This seems to be a harmless > but bogus no-op if the resource isn't there. > > Bruce I think I've got all this fixed (or closer to being fixed) in a merge of some nsio stuff back into sio.c so nsio.c can be zapped for now. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pnp and AWE64
At 10:50 PM 11/11/1999 -0600, Jim King wrote: >I just picked up an AWE64 to use until the Vortex2 driver is working. The >card is detected in Win98, but unfortunately the new PnP code in -current >(cvsup'ed this evening) doesn't seem to find this card at all. Nothing >shows up about it in dmesg; pnpinfo shows my ISA PnP modem, but nothing at >all about the AWE64. One more bit of info: this PC (Dell Dimension R450) has a Phoenix BIOS, which has a setting "Plug-n-Play OS? Yes/No". Changing it from No to Yes made the kernel find the AWE64. Unfortunately changing that setting also made the 3C905B NIC quit working: xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 11 at device 13.0 on pci0 xl0: couldn't map ports/memory device_probe_and_attach: xl0 attach returned 6 Another oddity: Although the AWE64 gets picked up by the pcm driver, pnpinfo still only shows the PnP modem - no mention of the AWE64. Jim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: nexus_setup_intr: NULL irq resource!
On Fri, 12 Nov 1999, Peter Jeremy wrote: > On 1999-Nov-12 12:35:01 +1100, Mark Newton wrote: > >The problem is that the BUS_SETUP_INTR() method for ISA seems to > >absolutely require the specification of an IRQ, even though IRQ > >specification is absolutely prohibited for non-master ports in > >AST-compatible multi-port sio cards. Gah. This is fixed differently (directly in the driver) in nsio (dev/sio/sio.c) rev.1.267. Both fixes are probably necessary and more or less correct. Drivers shouldn't attempt to register null interrupts, and attempting this probably shouldn't cause panics. > As an aside, why doesn't our SIO driver work with ports that don't > have interrupts? Same problem. Ports that don't have interrupts give polled mode, and the driver shouldn't attempt to register the null interrupts for polled mode, but this was broken when the driver was converted to new-bus. > >I'm not completely sure that this patch does the right thing > > Since your patch effectively turns isa_setup_intr() into a nop for > this case, a better patch would seem to be to skip the call to > BUS_SETUP_INTR() (and presumably bus_alloc_resource()) at the end > of sioattach() when you're attaching a slave SIO port. nsio still has the bus_alloc_resource(). This seems to be a harmless but bogus no-op if the resource isn't there. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: nexus_setup_intr: NULL irq resource!
On Fri, 12 Nov 1999, Mark Newton wrote:
> Peter Jeremy wrote:
>
> > Since your patch effectively turns isa_setup_intr() into a nop for
> > this case, a better patch would seem to be to skip the call to
> > BUS_SETUP_INTR() (and presumably bus_alloc_resource()) at the end
> > of sioattach() when you're attaching a slave SIO port.
>
> Absolutely true. :-)
Something like this should work:
Index: sio.c
===
RCS file: /home/ncvs/src/sys/isa/sio.c,v
retrieving revision 1.273
diff -u -r1.273 sio.c
--- sio.c 1999/10/28 05:06:12 1.273
+++ sio.c 1999/11/12 10:06:15
@@ -903,6 +903,7 @@
u_int flags = device_get_flags(dev);
int rid;
struct resource *port;
+ u_long junk;
rid = 0;
port = bus_alloc_resource(dev, SYS_RES_IOPORT, &rid,
@@ -1112,12 +1113,19 @@
com->pps.ppscap = PPS_CAPTUREASSERT | PPS_CAPTURECLEAR;
pps_init(&com->pps);
- rid = 0;
- com->irqres = bus_alloc_resource(dev, SYS_RES_IRQ, &rid, 0ul, ~0ul, 1,
- RF_SHAREABLE | RF_ACTIVE);
- BUS_SETUP_INTR(device_get_parent(dev), dev, com->irqres,
- INTR_TYPE_TTY | INTR_TYPE_FAST,
- siointr, com, &ih);
+ /*
+* Only setup the irq if there is one (in multiport, only the
+* master has an irq.
+*/
+ if (bus_get_resource(dev, SYS_RES_IRQ, &junk, &junk) == 0) {
+ rid = 0;
+ com->irqres = bus_alloc_resource(dev, SYS_RES_IRQ,
+&rid, 0ul, ~0ul, 1,
+RF_SHAREABLE | RF_ACTIVE);
+ BUS_SETUP_INTR(device_get_parent(dev), dev, com->irqres,
+ INTR_TYPE_TTY | INTR_TYPE_FAST,
+ siointr, com, &ih);
+ }
return (0);
}
--
Doug Rabson Mail: [EMAIL PROTECTED]
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
egcs unstable
Hi, After (by accident) compiling world (excluding kernel) with optimization disabled (ie -O0) and installing the resulting binaries, xemacs (21.1.7) coredumps with a bus error. I recompiled and reinstalled xemacs and all was fine. Now, after building and installing world (excluding kernel again) with optimization (ie -O), xemacs does exactly the same: core dumps on bus error. I'll recompile xemacs again and expect it to be solved, but something is definitely broken: xemacs should not core dump after recompiling world with only a simple change in compiler flags. I'll try out gcc-2.95.2 to see if it has the same problems... -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vga driver and signal
> > > > The only real way to do this "right" is going to be to have the X > > > > server load a KLD, which will then be able to hook the relevant > > > > interrupt(s). Any other alternative involves interrupt delivery to > > > > user-space, which is just not practical. > > > > > > Hi Mike, > > > Your idea sounds intriguing . How should we wired the KLD to > > > the X server? or how will the KLD inform the X server that it > > > has received a vertical retrace interrupt . > > > > The X server would have to load the KLD when it starts. The KLD would > > have to contain _all_ of the code that would run when the interrupt > > triggered. You would still have absolutely no latency guarantee on > > delivery of the interrupt to the KLD; you'd have to check on entry to > > the handler to see whether you weren't already too late. > > > > Basically, the whole idea is just totally screwed. You shouldn't be > > trying to do this because it just can't be done right. > > I should be trying to do this for it can have interesting applications such > as a Tivo player. Not sure what the problem with interrupt latency is ... > Can you elaborate a little bit more ? If you're talking about a specific piece of hardware whose design you are in control of, you can tweak the hardware/software combination to achieve the desired goal. The point I was trying to make was that in the _general_ case, this can't be done with software alone. You require the cooperation of hardware that just can't be obtained from your average PC. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?
Date: Thu, 11 Nov 1999 23:39:10 -0800 From: "David O'Brien" <[EMAIL PROTECTED]> Would it be possible to either ignore binary files when "-l" is in affect. OR to add an ignore binary file flag (like FreeBSD has in 2.x and 3.x)? The latter sounds reasonable, though it'd have to be spelled differently from -a since -a is now taken. Perhaps --skip-binary-files, by analogy with the existing --directories=skip option? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
