Xref: utzoo comp.unix.questions:7705 comp.unix.wizards:9557 comp.unix.xenix:2519 Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mcgill-vision!mouse From: mouse@mcgill-vision.UUCP (der Mouse) Newsgroups: comp.unix.questions,comp.unix.wizards,comp.unix.xenix Subject: Re: ksh weird files Keywords: ksh shell scripts, not weird Message-ID: <1177@mcgill-vision.UUCP> Date: 22 Jun 88 17:36:41 GMT References: <5658@chinet.UUCP> <5150@ecsvax.UUCP> <494@philmds.UUCP> <1289@ark.cs.vu.nl> Organization: McGill University, Montreal Lines: 25 In article <1289@ark.cs.vu.nl>, maart@cs.vu.nl (Maarten Litmaath) writes: > In article <494@philmds.UUCP> leo@philmds.UUCP (L.J.M. de Wit) writes: >> When login or getty or whoever goes to exec the sh script, how does >> it know which command interpreter to use (I don't think it knows of >> #! lines, in fact it doesn't even know the c.i. issue) ? > The magic number #! is well-known to the KERNEL! This is system-dependent. BSD kernels (recent ones, at least) do indeed handle #! on their own; I understand that SV kernels generally do not. (I don't know about any others, eg V7/V8/V9, SIII, etc.) >> And another question: how do you display text with >> echo << END-OF-TEXT >> text here >> END-OF-TEXT As you probably discovered, you don't: you use cat instead of echo. Using echo here makes about as much sense as saying cat textfile | echo der Mouse uucp: mouse@mcgill-vision.uucp arpa: mouse@larry.mcrcim.mcgill.edu