From: Anthony Martin <ality@pbrane.org>
To: 9front@9front.org
Subject: Re: [9front] this history(1) is scratched
Date: Sat, 12 Nov 2022 19:35:05 -0800 [thread overview]
Message-ID: <Y3BlG+FFjpQOMBFk@alice> (raw)
In-Reply-To: <14C5796F1CAB41005D892E08A68F9EAC@eigenstate.org>
ori@eigenstate.org once said:
> Quoth qwx@sciops.net:
> > The thing is, this change is already a few months old, and I cannot
> > imagine that the script has not worked for anyone in all of this time,
> > including when it was first pushed, or that absolutely everyone has
> > been using the old C version without noticing it. This behavior in
> > awk is surprising to me, but is not 9front-specific. What the hell is
> > going on? Can anyone else reproduce this? Any idea what I could be
> > doing wrong?
>
> ...I'm slightly embarrassed to admit that I've got the old history
> in my binds before the new one, so I didn't notice I was using the
> old one.
I think we all are. The default namespace set up by init(8) binds
/rc/bin after /$cputype/bin. A sysupdate(1) followed by a clean
build wouldn't blow away the old binary. Maybe we should detect
duplicate files in /bin and warn about them when updating.
% cat /bin/bindups
#!/bin/rc
rfork e
fs = `{cd /bin; ls | sort | uniq -d}
ds = `{ns | awk '$NF == "/bin" { print $(NF-1) }'}
>[2]/dev/null for(f in $fs) ls -ld $ds^/$f
Cheers,
Anthony
next prev parent reply other threads:[~2022-11-13 3:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 8:15 qwx
2022-11-12 11:03 ` Eckard Brauer
2022-11-12 12:16 ` Eckard Brauer
2022-11-12 18:07 ` Eckard Brauer
2022-11-12 19:13 ` ori
2022-11-12 20:32 ` Eckard Brauer
2022-11-12 20:44 ` Eckard Brauer
2022-11-12 20:53 ` Eckard Brauer
2022-11-12 21:26 ` ori
2022-11-12 22:43 ` umbraticus
2022-11-13 3:35 ` Anthony Martin [this message]
2022-11-13 23:20 ` qwx
2022-11-15 11:49 ` qwx
2022-11-15 21:59 ` qwx
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=Y3BlG+FFjpQOMBFk@alice \
--to=ality@pbrane.org \
--cc=9front@9front.org \
/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).