Re: [9fans] along the way...
is it worth using vfp when neon is around? just curious... -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T12f163bbd73cfb63-M558f1e2af20c27f2a58ccc46 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Re: [9fans] along the way...
> is it worth using vfp when neon is around? Plan 9 arm source uses "vfp" as a generic term to mean modern hardware floating point instruction set (as opposed to the old arm7500 instruction set, which I suspect has always been purely emulated since processors implementing this set were quite rare). No use has been made in Plan 9 (as far as I know) of the vector extensions which are the "v" part of vfp. I think the neon instruction set is a superset of the vfp set which 5l generates, so using vfp doesn't preclude something like a vector library with neon support. -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T12f163bbd73cfb63-Mc38b45eefa162e45c3a65ebe Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Re: [9fans] along the way...
yeah, that's what i mean. i was worried it wouldn't be a subset of neon: i.e. that they might keep neon and get rid of vfp at some point... -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T12f163bbd73cfb63-M823e9f92726c189cc0cd9465 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[9fans] /mail/lib/rewrite and net!$smtp
All, I was reviewing my mail setup this evening and I came across an old kludge to forward mail to a relay host on my network in /mail/lib/rewrite. I used a host-specific dial string rather than net!$smtp. For kicks, I reverted back to the classic behavior to try and sort out why the lookup fails and I'm hitting a brick wall (again). I've try adding smtp= entries to the sys, ipnet, and dom entries in /lib/ndb/local and nothing seems to be taking. I'm testing changes by issuing an ndb/csquery and I'm always getting the same result: % ndb/csquery /net/cs 'net!$smtp!smtp' translating net!$smtp!smtp: cs: can't translate address: dns: name does not exist I haven't found much other than a thread dating back to 2013 from fgb, which appears related but doesn't seem to have a solution that works for me. Any ideas? Steve -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T5ae49d9091a0a82e-Mcb1744719ac9a33c954539bf Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Re: [9fans] /mail/lib/rewrite and net!$smtp
What about: % ndb/csquery /net/cs 'net!$smtp!25' Or even: % ndb/csquery /net/cs 'tcp!$smtp!25' -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tf5f20e4ab86fee91-M6401d7abb306e5837d2593aa Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[9fans] Re: /mail/lib/rewrite and net!$smtp
> I haven't found much other than a thread dating back to 2013 from fgb, > which appears related but doesn't seem to have a solution that works > for me. Apologies, this was a thread from 2007 though fgb was not the original poster. After digging a little more based on one of steve's suggestions in the thread to run upas/smtp with -d, I think this makes much more sense now: % upas/smtp -d 'net!$smtp' stallion f...@bar.com expanding /net!$smtp sending /net/dns 'x.x.x.x mx' dns: dns: name does not exist mxlookup returns nothing smtp: cs: can't translate address: dns: name does not exist (net!$smtp) So it looks like upas will attempt to do an mx lookup for smtp; which means it's expecting a domain rather than the dial string of an SMTP server. After digging into the source a bit, it looks like mkdial in /sys/src/cmd/upas/smtp/mkdial.c is to blame; it also looks like it's not possible to specify a port number, which makes sense given that its relying on an mx lookup. I suppose in the end the kludge I added was the right solution after all. Go figure. Steve -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T95e65bcdc61bf064-M0415822ccd72fb76bb57b4a1 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Re: [9fans] /mail/lib/rewrite and net!$smtp
I'd start by making sure $smtp is expanded from the environment or the ndb at all. The error message: translating net!$smtp!smtp: seems to suggest it isn't. Try poking the ndb directly, like so: ndb/query ipnet 9front smtp -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tf5f20e4ab86fee91-Mdd6dae55e7871652e75699c8 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
