[9fans] Annyoing modified by boyd
Hey,
using legacy bell-labs plan9 (I don't know the others), I often, that converges
to always, get FILE modified by boyd since last read when editing a file on a
cifs share with acme.
The cifs main.c defines boyd as the modifying user (muid) in I2D and V2D,
which are from fs.stat.
From /sys/src/cmd/acme/exec.c:/putfile/+14
if(d!=nil runeeq(namer, nname, f-name, f-nname)){
/* f-mtime+1 because when talking over NFS it's often off by a
second */
if(f-dev!=d-dev || f-qidpath!=d-qid.path ||
f-mtime+1d-mtime){
f-dev = d-dev;
f-qidpath = d-qid.path;
f-mtime = d-mtime;
if(f-unread)
warning(nil, %s not written; file already
exists\n, name);
else
warning(nil, %s modified%s%s since last
read\n, name, d-muid[0]? by :, d-muid);
goto Rescue1;
}
}
Hmm, possibly this is another time quirk, like that one from NFS. Does anyone
know a good solution to that problem?
Regards
ikrabbe
Re: [9fans] Annyoing modified by boyd
Can you trace this a bit more into cifs? cifs is one of mine and I use it daily without problems, though I never migrated from sam to acme, so perhaps I just don't see your issue. I remember that smb/cifs does have weird timestamps some of which are only changed on 2 second boundries - though the code you show should cope happily with that. The server has its own timestamp which cifs reads at startup and uses that to convert the server's localtime to utc, but I think this time is read only once per session so that is unlikely to be the problem. Sorry if I'am a bit vague but it was 10 years ago now, but I am happy to dig if you can provide a bit more info. -Steve
[9fans] inquiry about project sponsorship outside GSoC
Greetings 9fans, I am a senior studying computer science at Tufts University. I'm interested in Plan 9 and frequently read this list. As seniors at Tufts we are required to do a year long capstone project; it's fairly open ended but must be motivated by some external sponsor. If sponsoring a group of 3 university students to do a year-long project around Plan 9 sounds cool, read on! What project we choose to do (Plan 9 or otherwise) is still up in the air, and depends on our sponsor. In the Plan 9 vein, the GSoC wiki page has a nice selection of projects that are of comparable size: http://www.plan9.bell-labs.com/wiki/plan9/gsoc-2014-ideas/index.html Some projects from that page that seem particularly intersting and in-scope: * alternative window system * create additional modules for pq * Kernel lock analyzer for amd64 kernel * Kernel lock timing analyzer for amd64 kernel * a per-processor scheduler * Implement TLS 1.2 in libsec * Add support for OAuth2 Login authentication to factotum * 9p on Arduino Yun * Teach Plan 9 to speak mDNS We're also very open to other project ideas. Your role as a sponsor would look something like this: fall semester (between now and mid-December) you would help define requirements and a deliverables timeline, and approve design documents. In the spring you would monitor progress and optionally provide support to the implementation. There are resources for in-house support at Tufts, but nobody here knows Plan 9 well enough to provide Plan 9-specific support, or clarify requirements such that the project will be useful to the community. If you are worried about the time commitment, a couple emails per month would be sufficient once we get the ball rolling (more frequent communication could be necessary at first to get us to a place where we can write and test code). If this seems at all interesting, feel free to contace me off-list. Best, Caleb Malchik
Re: [9fans] inquiry about project sponsorship outside GSoC
On Wed, 17 Sep 2014 17:33:36 -0400 Caleb Malchik cmalc...@gmail.com wrote: Your role as a sponsor would look something like this: fall semester (between now and mid-December) you would help define requirements and a deliverables timeline, and approve design documents. In the spring you would monitor progress and optionally provide support to the implementation. They used to call this mentoring. -- Svi moji e-mailovi su kriptografski potpisani. Proverite ih. All of my e-mails are cryptographically signed. Verify them. -- You don't need an AI for a robot uprising. Humans will do just fine. signature.asc Description: PGP signature
Re: [9fans] Annyoing modified by boyd
FILE modified by boyd since last read strikes me as more useful than most
error messages I see these days. My only question is what particular weapon
Boyd would have used to modify the file.
On 17 September 2014 23:18, Ingo Krabbe ikrabbe@gmail.com wrote:
Hey,
using legacy bell-labs plan9 (I don't know the others), I often, that
converges to always, get FILE modified by boyd since last read when
editing a file on a cifs share with acme.
The cifs main.c defines boyd as the modifying user (muid) in I2D and
V2D, which are from fs.stat.
From /sys/src/cmd/acme/exec.c:/putfile/+14
if(d!=nil runeeq(namer, nname, f-name, f-nname)){
/* f-mtime+1 because when talking over NFS it's often off
by a second */
if(f-dev!=d-dev || f-qidpath!=d-qid.path ||
f-mtime+1d-mtime){
f-dev = d-dev;
f-qidpath = d-qid.path;
f-mtime = d-mtime;
if(f-unread)
warning(nil, %s not written; file already
exists\n, name);
else
warning(nil, %s modified%s%s since last
read\n, name, d-muid[0]? by :, d-muid);
goto Rescue1;
}
}
Hmm, possibly this is another time quirk, like that one from NFS. Does
anyone know a good solution to that problem?
Regards
ikrabbe
