From: Alan Watson <alan@oldp.astro.wisc.edu>
To: rc@hawkwind.utcs.toronto.edu
Subject: execve bug on Ultrix 4.3
Date: Wed, 26 May 1993 19:04:14 -0400 [thread overview]
Message-ID: <9305262304.AA13756@oldp.astro.wisc.edu> (raw)
Kernel #! interpretation fails on Ultrix 4.3 if the first line of the
script (including the #!, the trailing newline, and any trailing white
space) is longer than 32 characters. Compiling up with execve.c seems
to solve the problem, or at least delay it until the line is 256
characters long.
Why, oh, why is this allowed to happen in the 1990s? Sorry, I forgot:
all versions of Unix come with /dev/timemachine to take the user back
to the 1970s.
reply other threads:[~1993-05-26 23:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9305262304.AA13756@oldp.astro.wisc.edu \
--to=alan@oldp.astro.wisc.edu \
--cc=rc@hawkwind.utcs.toronto.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).