From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] udp change
Date: Fri, 18 Apr 2003 17:13:01 -0400 [thread overview]
Message-ID: <f84f3127c5301675c24a96f2f8e7709f@plan9.bell-labs.com> (raw)
In-Reply-To: <d68cf8996622bb1f5485351419d82ccd@plan9.bell-labs.com>
[-- Attachment #1: Type: text/plain, Size: 450 bytes --]
rsc pointsout that if I don't mind taking longer to make it all work, I
can do the following:
- put out new binaries that write both "oldheaders" and "headers"
- put out new kernel with both
- put out new binaries with just "headers"
- put out new kernel with just "headers"
And we aren't left with the ++ for all time.
I may do that instead. It just means that I have to delay putting out the
new udp.c for a while. I'll do it...
[-- Attachment #2: Type: message/rfc822, Size: 1592 bytes --]
From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: [9fans] udp change
Date: Fri, 18 Apr 2003 16:49:30 -0400
Message-ID: <d68cf8996622bb1f5485351419d82ccd@plan9.bell-labs.com>
I chickened out. I was too afraid of breaking everyone's DHCP and DNS
so that they couldn't boot. I added a "headers++" control message (and removed
the "headers4" one). Look at the new /sys/include/ip.h for documentation.
After people have had time to build/boot new kernels, I'll release
new user programs that use the "headers++" stuff and eventually
phase out "headers".
prev parent reply other threads:[~2003-04-18 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 20:49 David Presotto
2003-04-18 21:13 ` David Presotto [this message]
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=f84f3127c5301675c24a96f2f8e7709f@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--cc=9fans@cse.psu.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).