From: Michael Hansen <mmhansen@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: [9fans] 9front: /lib/ndb/local clobbered after edit w/ sam, soon following update
Date: Mon, 24 Mar 2014 23:07:12 -0700 [thread overview]
Message-ID: <CAPkKT5FTf88zctZeTeUMqoN36RqxeM6HfNzwmnUY7dv-Kt8fLA@mail.gmail.com> (raw)
Earlier today, I ran sysupdate on a Thinkpad T23 running
9front-3196.bf2df3ad17fa and rebuilt from source, as shown in the
9front wiki.
Later, I edited /lib/ndb/local with sam to specify a different ntp
server. After writing the change, closing the file, and quitting sam,
I restarted with fshalt -r.
After the restart, the machine's name had defaulted to cirno, and all
dns lookups seemed to be failing. I checked /lib/ndb/local to see if
I'd accidentally changed more than I thought, and the whole thing had
been replaced with what looked like C source I'd been looking at,
earlier. (Not the whole file, just the last ~20 lines.)
I copied another machine's /lib/ndb/local onto a flash drive, copied
it to /lib/ndb, modified it to suit the Thinkpad with sam, again, and
restarted with fshalt -r.
/lib/ndb/local got clobbered again, except this time, it was
overwritten with something having the general appearance of line
noise, heavy on unprintable characters.
I repeated the process of reconstructing /lib/ndb/local from another
box, only this time, I used ed instead of sam, and all appeared to be
well, after restarting.
Any ideas what went wrong? Trying to figure-out whether this is a DDTT
situation, or if I should worry that something got corrupted in the
update process, or that my recently installed SSD might have issues.
next reply other threads:[~2014-03-25 6:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 6:07 Michael Hansen [this message]
2014-03-25 8:38 ` cinap_lenrek
2014-03-25 8:42 ` cinap_lenrek
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=CAPkKT5FTf88zctZeTeUMqoN36RqxeM6HfNzwmnUY7dv-Kt8fLA@mail.gmail.com \
--to=mmhansen@gmail.com \
--cc=9fans@9fans.net \
/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).