head(1) speedup
can someone please check this out, it makes "head -n" about five
times faster. (also nukes a 'register', sorry :))
cvs diff: Diffing .
Index: head.c
===
RCS file: /home/ncvs/src/usr.bin/head/head.c,v
retrieving revision 1.10
diff -c -r1.10 head.c
*** head.c 28 Aug 1999 01:01:58 - 1.10
--- head.c 2 Nov 2001 08:18:07 -
***
*** 131,146
void
head(fp, cnt)
FILE *fp;
! register int cnt;
{
! register int ch;
! while (cnt && (ch = getc(fp)) != EOF) {
! if (putchar(ch) == EOF)
! err(1, "stdout");
! if (ch == '\n')
! cnt--;
! }
}
void
--- 131,147
void
head(fp, cnt)
FILE *fp;
! int cnt;
{
! char *cp;
! int error, readlen;
! while (cnt && (cp = fgetln(fp, &readlen)) != NULL) {
! error = fwrite(cp, sizeof(char), readlen, stdout);
! if (error != readlen)
! err(1, "stdout");
! cnt--;
! }
}
void
--
-Alfred Perlstein [[EMAIL PROTECTED]]
'Instead of asking why a piece of software is using "1970s technology,"
start asking why software is ignoring 30 years of accumulated wisdom.'
http://www.morons.org/rants/gpl-harmful.php3
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: ep0 driver oddity
Leo Bicknell wrote: > > I broke out a really old card to make a cheap solution work, and > now I'm confused. It's an old 3c509 ISA card, which has been set > to 0x300, irq 5. Those don't conflict, so no issue there. > > Building a kernel with "device ep0" found it, but didn't like it > because it wasn't at the default IRQ 10. So, I rebuilt a kernel > with > > device ep0 at isa? port 0x300 irq 5 > > Here's where my confusion came in, I get this in dmesg: > > ep0 at port 0x300 irq 5 on isa0 > ep0: Ethernet address 00:20:af:6a:d8:d6 > ep1: <3Com 3C509-TP EtherLink III> at port 0x300-0x30f irq 10 on isa0 > ep1: No irq?! > ep1: ep_alloc() failed! (6) > device_probe_and_attach: ep1 attach returned 6 > > ep0 seems to work ok, and there is no ep1. I'm not sure why it's > auto-looking for an additional card. If I leave the 0 off: It has been a while since I setup my 3C509 but what I remember is having to turn off PNP on the card. Kent > > device ep at isa? port 0x300 irq 5 > > config barfs, even though the default is "device ep". > > I get the feeling that if I set this via config I'd be ok, but I don't > have easy access to the console of this particular machine. > > I'm sure I'm missing something really simple, but how can I set > ep0 in the kernel config and not get an ep1 along with it? > Alternatives (eg, loader.conf or something) would be fine, I know > nothing about that. > > -- >Leo Bicknell - [EMAIL PROTECTED] - CCIE 3440 > PGP keys at http://www.ufp.org/~bicknell/ > Read TMBG List - [EMAIL PROTECTED], www.tmbg.org > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://users.owt.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ep0 driver oddity
On Thu, 1 Nov 2001, Leo Bicknell wrote: > ep0 at port 0x300 irq 5 on isa0 > ep0: Ethernet address 00:20:af:6a:d8:d6 > ep1: <3Com 3C509-TP EtherLink III> at port 0x300-0x30f irq 10 on isa0 > ep1: No irq?! > ep1: ep_alloc() failed! (6) > device_probe_and_attach: ep1 attach returned 6 Set the card to whatever settings you desire using the 3c5x9cfg util (get it from ftp.3com.com etc.) Don't use hints (if this is FreeBSD 4 or -CURRENT) -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
ep0 driver oddity
I broke out a really old card to make a cheap solution work, and now I'm confused. It's an old 3c509 ISA card, which has been set to 0x300, irq 5. Those don't conflict, so no issue there. Building a kernel with "device ep0" found it, but didn't like it because it wasn't at the default IRQ 10. So, I rebuilt a kernel with device ep0 at isa? port 0x300 irq 5 Here's where my confusion came in, I get this in dmesg: ep0 at port 0x300 irq 5 on isa0 ep0: Ethernet address 00:20:af:6a:d8:d6 ep1: <3Com 3C509-TP EtherLink III> at port 0x300-0x30f irq 10 on isa0 ep1: No irq?! ep1: ep_alloc() failed! (6) device_probe_and_attach: ep1 attach returned 6 ep0 seems to work ok, and there is no ep1. I'm not sure why it's auto-looking for an additional card. If I leave the 0 off: device ep at isa? port 0x300 irq 5 config barfs, even though the default is "device ep". I get the feeling that if I set this via config I'd be ok, but I don't have easy access to the console of this particular machine. I'm sure I'm missing something really simple, but how can I set ep0 in the kernel config and not get an ep1 along with it? Alternatives (eg, loader.conf or something) would be fine, I know nothing about that. -- Leo Bicknell - [EMAIL PROTECTED] - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/ Read TMBG List - [EMAIL PROTECTED], www.tmbg.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
pccard bridging not functioning in 4.4-RELEASE
I have two 3com 3c589 10BT pc cards. As vanilla as they come. In a previous thread, I described how a bit of pccard.conf mumbo jumbo made it possible for me to get both cards up and running in 4.3-RELEASE. It was explained to me that pccard.conf is deprecated, and that two pcmcia nics should "just work". I then asked how to do it the old way, and it was suggested: >Set the following sysctls at boot time: >hw.pcic.intr_path="1" >hw.pcic.irq="0" Unfortunately, this does not solve the problem - the second 3com pcmica card still produces the dreaded "no card in database for null null" even though it is identical to the first card that comes up just fine. I have _no preference_ about doing this with the deprecated pccard.conf method, or whatever, but I need to be able to use two 3com 3C589 cards in freeBSD 4.4. Anyone have any ideas how to get this working ? thanks, Joesh _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
ahc(4) reports PCI parity error interrupt
Hi I'm looking for comments on the following: ahc0: PCI error Interrupt at seqaddr = 0x8 ahc0: Data Parity Error Detected during address or write data phase ahc0: PCI error Interrupt at seqaddr = 0x9 ahc0: Data Parity Error Detected during address or write data phase ahc0: PCI error Interrupt at seqaddr = 0x9 ahc0: Data Parity Error Detected during address or write data phase ahc0: PCI error Interrupt at seqaddr = 0x8 ahc0: Data Parity Error Detected during address or write data phase ahc0: PCI error Interrupt at seqaddr = 0x8 I've also experienced system lockups & panics. This happens exclusively while doing: - considerable disk I/O (buildworld) via ahc0 - watching TV via fxtv on a WinTV Primio It feels like the datastream of the WinTV into the framebuffer (Matrox G200 AGP) gets in the way with the data from/to the Adaptec 29160. I ran the same systemdisk & all expansion cards in a PII-266 with Intel chipset without any issue. The K7V is rock stable as long as I keep my fingers from fxtv. Suggestions on how to analyse/workaround this issue are most welcome. Anything in the BIOS setup maybe? Wilko === background data == FreeBSD freebie.xs4all.nl 4.4-STABLE FreeBSD 4.4-STABLE #0: Thu Nov 1 23:47:04 CET 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/FREEBIE i386 Mainboard: Asus K7V (VIA based, brandnew) with Athlon 700 Also occured on a VIA based Abit KA7 (I got the Asus as the Abit died on me) SCSI: freebie# camcontrol devlist at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 3 lun 0 (pass1,cd0) dmesg: FreeBSD 4.4-STABLE #0: Thu Nov 1 23:47:04 CET 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/FREEBIE Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 700029024 Hz CPU: AMD Athlon(tm) Processor (700.03-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x621 Stepping = 1 Features=0x183f9ff AMD Features=0xc040 real memory = 268353536 (262064K bytes) avail memory = 257622016 (251584K bytes) Preloaded elf kernel "kernel" at 0xc038f000. Preloaded elf module "agp.ko" at 0xc038f09c. Pentium Pro MTRR support enabled Using $PIR table, 8 entries at 0xc00f15e0 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 agp0: mem 0xe400-0xe7ff at device 0.0 on pci0 pcib2: at device 1.0 on pci0 pci1: on pcib2 pci1: at 0.0 irq 11 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 uhci0: port 0xd400-0xd41f irq 5 at device 4.2 on pci 0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd000-0xd01f irq 5 at device 4.3 on pci 0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered xl0: <3Com 3c905-TX Fast Etherlink XL> port 0xa400-0xa43f irq 5 at device 9.0 on pci0 xl0: Ethernet address: 00:60:08:09:b7:41 miibus0: on xl0 nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcm0: port 0x8800-0x8803,0x9000-0x9003,0x9400-0x940f,0x9800-0x980f ,0xa000-0xa03f irq 15 at device 10.0 on pci0 ahc0: port 0x8400-0x84ff mem 0xe000-0x efff irq 10 at device 11.0 on pci0 aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0x8000-0x80ff mem 0xdf80-0xdf80 0fff irq 11 at device 12.0 on pci0 aic7880: Ultra Wide Channel A, SCSI Id=7, 16/255 SCBs bktr0: mem 0xe200-0xe2000fff irq 5 at device 13.0 on pci0 iicbb0: on bti2c0 iicbus0: on iicbb0 master-only iicsmb0: on iicbus0 smbus0: on iicsmb0 smb0: on smbus0 smbus1: on bti2c0 smb1: on smbus1 bktr0: Hauppauge Model 61204 AMA bktr0: Hauppauge WinCast/TV, Philips PAL I tuner. pci0: (vendor=0x109e, dev=0x0878) at 13.1 irq 5 pcib1: on motherboard pci2: on pcib1 orm0: at iomem 0xc-0xc7fff,0xc8000-0xcbfff,0xd4000-0xd47ff on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 5 flags 0x20 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Polled port unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources ad0: 29188MB [59303/16/63] at ata0-master UDMA66 Waiting 3 seconds for SCSI devices to settle Mounting
온라인 마케팅이 힘들게 느껴지십니까?
Title: Untitled Document ¾È³çÇϽʴϱî? ¼¼°è Á¦ÀÏÀÇ ÀüÀÚÄ«´Ù·Î±× Æ÷Å»»çÀÌÆ®¸¦ ¿î¿µÇÏ´Â eÄ«´Ù·Î±× ¼ÒÇÁÆ®´åÄÄÀÇ ¸¶ÄÉÆà ´ã´çÀÚ ÀÌ°æÇÏÀÔ´Ï´Ù. ±Í»çÀÇ Á¦Ç°À» ¼¼°è¿¡ ³Î¸® È«º¸/ÆǸÅÇϱâ À§ÇØ ¸¶ÄÉÆà ¹æ¾ÈÀ» ã°í °è½Å´Ù¸é º»»çÀÇ ±¹Á¦ÀûÀÎ ÆÇÃË ´ëÇà ¼ºñ½º¸¦ ÀÌ¿ëÇØ º¸½Ê½Ã¿À. -> ´º½º±â»ç Âü°í eCat ÀüÀÚÄ«´Ù·Î±×ÀÇ ÀåÁ¡ 1) ´ë¿ë·® Á¤º¸ÀÇ °æ·®È Àü¼Û ...»óÇ° 100¿©°³(W 510Çȼ¿X H 400Çȼ¿ À̹ÌÁö, A4¿ëÁö 3ÀåºÐ·®ÀÇ »óÇ°Á¤º¸)Á¦À۽à ... 1~2MB³»¿ÜÀÇ ¾ÆÁÖ ÀÛÀº ¿ë·®À̱⿡ ¸î°¡Áö ´ëÇ¥»óÇ°ÀÌ ¾Æ´Ï¶ó »óÇ°Àüü¸¦ È«º¸ ... ÇÏ½Ç ¼ö ÀÖ½À´Ï´Ù. 2) °æÁ¦¼º ...¼¹ö±¸Ãà, ȨÆäÀÌÁöµðÀÚÀκñ¿ë, À¯Áöºñ¿ëµîÀÇ Àý°¨À¸·Î Àú·ÅÇÏ°Ô ¸¶ÄÉÆÃÀ» ...ÇÒ ¼ö ÀÖ½À´Ï´Ù. ¶ÇÇÑ ¾÷µ¥ÀÌÆ® ¹«·á ¼ºñ½º·Î ¹Ý¿µ±¸Àû »ç¿ëÀÌ °¡´ÉÇÕ´Ï´Ù. 3) °í°´ ºÒ¸¸ ÇØ¼Ò ...°í°´Àº ¿ÏÀü ¹«·á·Î ¹«Á¦ÇÑÀÇ ´Ù¿î·Îµù°ú ºÎ°¡¼ºñ½º(Wish List)µîÀ» ÀÌ¿ëÇÒ ...¼ö ÀÖ½À´Ï´Ù. .¼³Ä¡ ÈÄ °í°´ ÄÄÇ»ÅÍ¿¡¼ ½ÇÇàÇϹǷΠon/off °â¿ë »ç¿ëÀÌ °¡´ÉÇÏ°í ...´Ù¿î·Îµå ½Ã°£ÀÌ ¾ø°í, °£´ÜÇÏ¸ç ´Ù¾çÇÑ ÁÖ¹®¹æ¹ýÀº °í°´¿¡°Ô µµ¿òÀ» µå¸³´Ï´Ù. * Á÷Á¢ »ç¿ëÇغ¸½Ã¸é ´õ ³î¶ó¿î ±â´ÉµéÀ» ¹ß°ßÇÏ½Ç ¼ö ÀÖ½À´Ï´Ù. ¹Ì¸®º¸±â »ùÇôٿî Á¦°ø ¼ºñ½º 1) ¹èÆ÷¿ë ÀüÀÚÄ«´Ù·Î±× Á¦ÀÛ ¼ºñ½º (eCBS) -> ÀÚ¼¼È÷ º¸±â ´Ü°¡´Â 13,000¿ø(Á¤°¡)ÀÌ¸ç »óÇ°ÀÇ °³¼ö¸¦ ±âÁØÀ¸·Î ÇÏ¿© Ã¥Á¤µË´Ï´Ù.(VATº°µµ) ...11¿ù 30ÀϱîÁö´Â 50% ÇÒÀÎµÈ ÆÄ°ÝÀûÀÎ °¡°ÝÀ¸·Î Á¦°øÇØ µå¸³´Ï´Ù. ...´Ü°¡ : 6,500¿ø (VATº°µµ) 2) ÀüÀÚÄ«´Ù·Î±× ¸¶ÄÉÆà (ÆÇÃË) ´ëÇà ¼ºñ½º (SPS) -> ÀÚ¼¼È÷ º¸±â ..."eCBS"¸¦ ÀÌ¿ëÇÏ´Â ±â¾÷¿¡°Ô Á¦°øÇÏ´Â ÆÇÃË´ëÇà ¼ºñ½º·Î½á ...º» ¼ºñ½º´Â ÀúÈñ ¸¶ÄÉÆÃÆÀ¿¡ ÀÇÇÏ¿© ¸ÅÃâÀÌ ¼º»çµÉ °æ¿ì¿¡¸¸ Àû¿ëµÇ´Â °ÍÀ̸ç ...ÃѸÅÃâ¾×ÀÇ 10%¸¦ ¼ö¼ö·á·Î ÈÄÃëÇÕ´Ï´Ù. ¹®ÀÇ»çÇ× ÀÖÀ¸½Ã¸é ¾ðÁ¦µçÁö ¿¬¶ôÁֽʽÿÀ. ¸¶ÄÉÆôã´ç : ÀÌ°æÇÏ [EMAIL PROTECTED] ÁÖ¹®Ã³ : ÀüÈ 02-523-4374 / Æѽº 02-523-4398 / ¸ÞÀÏ [EMAIL PROTECTED] ±ÍÇÏÀÇ À̸ÞÀÏÀº ÀÎÅͳݻ󿡼 ¿ì¿¬È÷ ¾Ë°Ô µÈ °ÍÀÔ´Ï´Ù. º» News letter¸¦ ¿øÄ¡ ¾ÊÀ¸½Ã¸é ¼ö½Å°ÅºÎ (Send e-mail)¸¦ ´·¯ÁֽʽÿÀ. ±Í»çÀÇ ¸¶ÄÉÆÿ¡ ³¯°³¸¦ ´Þ¾Æ µå¸®°Ú½À´Ï´Ù. .. ¼¼°è Á¦ÀÏÀÇ ÀüÀÚÄ«´Ù·Î±× ¼Ö·ç¼Ç°ú Æ÷Å»»çÀÌÆ®¸¦ ÁöÇâÇÏ´Â eÄ«´Ù·Î±×¼ÒÇÁÆ®´åÄÄ ÀÚ¼¼ÇÑ ³»¿ëÀº Homepage¸¦ ÂüÁ¶Çϼ¼¿ä.
Re: Unix Philosophers Please!
On Thu, Nov 01, 2001 at 08:29:39PM +, lg wrote: > > In short: The data is tranfered into the kernel and dropped there. > my source /usr/src/sys/i386/i386/mem.c [FreeBSD-4.3-RELEASE] > says that data doesnt transfered into kernel. I was looking into -current. Null and *random have been seprarated in -current. > kernel just do: (when you write to device with major 2, minor 2) > > c = iov->iov_len; > > iov->iov_base += c; > iov->iov_len -= c; > uio->uio_offset += c; > uio->uio_resid -= c; > > [ where iov is uio->uio_iov ] > > so data doesnt go anywhere. Sorry - you are right. No data is copied into the kernel as it would be the job of null_write() to do if needed. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Unix Philosophers Please!
> > Answer 2. All the data goes into another dimension, and comes out of > > /dev/random. > That would be so funny... I cat /dev/random, and I get your > files, as you delete them. 8-). Of course you do, it is just that the bytes are in random order. But I see that you are thinking of /dev/null as a bitbucket for files. Hmm... that means we can get rid of the unlink() given an atomic rename() syscall. mv file1 file2 dir1 et cetera et cetera et cetera /dev/null Neat! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
forwarding
hi, Im trying to use DirectConnect (peer2peer sharing) over draconian firewall (almost no ports allowed in both directions). DC uses port 411 to comunicate with nods that shows you other users and their files. I managed to make a tunell for this port. The problem is when I try to retrive any files from users. Than DC tryies to establish direct connection to user on ports from 410-415. How could I somehow 'catch' this request(SYN_SENT foo.foobar.com 41x) and forward it through ssh tunnel and back? Don't limit yourself to just one box, I also have another FreeBsd machine ready to serve. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Unix Philosophers Please!
On Wed, Oct 31, 2001 at 03:02:59PM -0600, Nicpon, John wrote:
> Please specifically define where data goes that is sent to /dev/null
That's what manpages are for - see null(4).
If you want it more specific src/sys/dev/null.c says:
[...]
static int
null_write(dev_t dev, struct uio *uio, int flag)
{
uio->uio_resid = 0;
return 0;
}
[...]
The memory which holds the data is declared as unused now and may be
overwritten at any time.
Even if the data still exists you will loose the reference to the
holding memory on return of null_write().
In short: The data is tranfered into the kernel and dropped there.
--
B.Walter COSMO-Project http://www.cosmo-project.de
[EMAIL PROTECTED] Usergroup [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: buildworld breakage during "make depend" at usr.bin/kdump
On Thu, Nov 01, 2001 at 01:36:24PM +0100, Guido van Rooij wrote:
> On Thu, Nov 01, 2001 at 01:29:50PM +0100, Dag-Erling Smorgrav wrote:
> > Guido van Rooij <[EMAIL PROTECTED]> writes:
> > > May I aks which shell you are using?
> >
> > Zsh.
>
> I am starting to wonder which sh is broken.
Neither really. First note that zsh doesn't claim to be fully compatible with
/bin/sh (or POSIX-compliant for that matter.) Secondly, zsh has a lot
of options defining how it works. In this case the option
SH_WORD_SPLIT defines which behaviour will be used. If this option is
set it will replace the newline with a space. If it is not set (which
is the default) the newline will be retained as it is.
>
> Btw there is a difference between sh and {t,}csh: in the sh case the newline
> is replaced with 1 space. In the case of the 2 others, there are 2 spaces.
--
Erik Trulsson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: buildworld breakage during "make depend" at usr.bin/kdump
On Thu, Nov 01, 2001 at 01:36:24PM +0100, Guido van Rooij wrote:
> On Thu, Nov 01, 2001 at 01:29:50PM +0100, Dag-Erling Smorgrav wrote:
> > Guido van Rooij <[EMAIL PROTECTED]> writes:
> > > May I aks which shell you are using?
> >
> > Zsh.
>
> I am starting to wonder which sh is broken.
>
> Btw there is a difference between sh and {t,}csh: in the sh case the newline
> is replaced with 1 space. In the case of the 2 others, there are 2 spaces.
And this is not an echo issue, it is a shell variable expansion issue.
Witness (using /bin/sh) :
$ foo='bar
> baz'
$ echo $foo
bar baz
$ /bin/echo $foo
bar baz
$ echo "$foo"
bar
baz
$ /bin/echo "$foo"
bar
baz
$
G'luck,
Peter
--
If I were you, who would be reading this sentence?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: buildworld breakage during "make depend" at usr.bin/kdump
On Thu, Nov 01, 2001 at 01:29:50PM +0100, Dag-Erling Smorgrav wrote:
> Guido van Rooij <[EMAIL PROTECTED]> writes:
> > May I aks which shell you are using?
>
> Zsh.
I am starting to wonder which sh is broken.
Btw there is a difference between sh and {t,}csh: in the sh case the newline
is replaced with 1 space. In the case of the 2 others, there are 2 spaces.
-Guido
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: buildworld breakage during "make depend" at usr.bin/kdump
Guido van Rooij <[EMAIL PROTECTED]> writes: > May I aks which shell you are using? Zsh. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: buildworld breakage during "make depend" at usr.bin/kdump
On Thu, Nov 01, 2001 at 12:43:21PM +0100, Dag-Erling Smorgrav wrote: > "Eugene L. Vorokov" <[EMAIL PROTECTED]> writes: > > Uhmz ? > > Your shell is broken. > Just tried it with /bin/sh, /bin/csh and /bin/tcsh and they all remove the newlines. That is a lot of broken shells. May I aks which shell you are using? -Guido To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Unix Philosophers Please!
"Nicpon, John" <[EMAIL PROTECTED]> writes: > Please specifically define where data goes that is sent to /dev/null It goes into a special data sink in the CPU where it is converted to heat which is vented through the heatsink / fan assembly. This is why CPU cooling is increasingly important; as people get used to faster processors, they become careless with their data and more and more of it ends up in /dev/null, overheating their CPUs. If you delete /dev/null (which effectively disables the CPU data sink) your CPU may run cooler but your system will quickly become constipated with all that excess data and start to behave erratically. If you have a fast network connection you can cool down your CPU by reading data out of /dev/random and sending it off somewhere; however you run the risk of overheating your network connection and / or angering your ISP, as most of the data will end up getting converted to heat by their equipment, but they generally have good cooling, so if you don't overdo it you should be OK. I hope this answers your question. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: buildworld breakage during "make depend" at usr.bin/kdump
"Eugene L. Vorokov" <[EMAIL PROTECTED]> writes: > Uhmz ? Your shell is broken. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: buildworld breakage during "make depend" at usr.bin/kdump
> > "David O'Brien" <[EMAIL PROTECTED]> writes: > > because `echo' nicely removes \n's from env vars when it prints them. > > des@des ~% foo='bar > quote> baz' > des@des ~% echo $foo > bar > baz > des@des ~% /bin/echo $foo > bar > baz > Uhmz ? bash-2.05# foo='bar > baz' bash-2.05# echo $foo bar baz bash-2.05# /bin/echo $foo bar baz bash-2.05# set |grep foo foo=$'bar\nbaz' bash-2.05# Regards, Eugene To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
