From: steve.simon@snellwilcox.com
To: 9fans@cse.psu.edu
Subject: [9fans] lp bind strangeness
Date: Mon, 31 Mar 2003 15:22:30 +0100 [thread overview]
Message-ID: <6a90468a8fc908854eda6969e123d62a@snellwilcox.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]
Hi,
I cannot work out what is going on.
I have been using lp to print via a remote BSD printer for months.
I have added a /lib/namespace (attached) but I cannot see how
this harms anything.
NB. my /usr/local/sys/lib/lp/spooler only contains the binaries for forsyth's
smb print client.
Now when I try to print I get:
lpdspool: '/bin/rc' directory entry not found
On closer inspection the following code from /rc/bin/lp is being run:
if (~ $RESET '') {
switch ($SPOOLER) {
case -; echo spooler does not exist for $LPDEST >[1=2]
exit 'no spooler'
case *; bind -b $LPLIB/spooler /bin
if (~ $#* 0) $SPOOLER
if not $SPOOLER $*
}
}
it seems that the bind is causing /386/bin/rc to disapear from /bin.
I cannot see how this can be possible. If I change the bind -b to a bind -a
then it works as expected.
It cannot be any of my mounts as lp rebuilds /bin's mounts itself
and I have nothing mounted over /386/bin or /rc/bin for that matter.
I thought I understood union directories - obviously not :-(
-Steve
[-- Attachment #2.1: Type: text/plain, Size: 315 bytes --]
The following attachment had content that we can't
prove to be harmless. To avoid possible automatic
execution, we changed the content headers.
The original header was:
Content-Disposition: attachment; filename=namespace.local
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
[-- Attachment #2.2: namespace.local.suspect --]
[-- Type: application/octet-stream, Size: 912 bytes --]
bind -b /usr/local/386/bin /bin
bind -a /386/bin/ip /bin/ip
bind -a /386/bin/upas /bin/upas
bind -b /usr/local/rc/bin /bin
bind -a /rc/bin/service /bin/service
bind -b /usr/local/acme/bin/386 /acme/bin/386
bind -a /usr/local/386/lib /386/lib
bind -a /usr/local/386/include /386/include
bind -a /usr/local/sys/include /sys/include
bind -a /usr/local/sys/doc /sys/doc
bind -a /usr/local/sys/man/1 /sys/man/1
bind -a /usr/local/sys/lib/lp/spooler /sys/lib/lp/spooler
bind -a /usr/local/lib/font/bit/pelm /lib/font/bit/pelm
bind -a /usr/local/lib/font/bit/lucida /lib/font/bit/lucida
bind -a /usr/local/sys/lib /sys/lib
bind -c /usr/local/lib/face/48x48x4/.dict /lib/face/48x48x4/.dict
bind -a /usr/local/lib/face/48x48x4 /lib/face/48x48x4
bind -b /usr/local/mail/lib /mail/lib
bind -bc /usr/local/sys/src/9/pc /sys/src/9/pc
bind -bc /usr/local/sys/src/9/boot /sys/src/9/boot
next reply other threads:[~2003-03-31 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 14:22 steve.simon [this message]
2003-03-31 15:44 David Presotto
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=6a90468a8fc908854eda6969e123d62a@snellwilcox.com \
--to=steve.simon@snellwilcox.com \
--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).