>
> What I notice - correct me if I am mistaken - is that any comparison between
> 9front and 9legacy seems to needle a few members (very few, there are many
> names from that community that have not participated, specifically the ones I
> know hand have long respectes, ask them) of the 9front
> Installing fossil on 9front is not really difficult.
Correct. You only need to grab the source of it from your favorite vendor,
place it into right places and build it like any other system program.
Here's a script I wrote some years ago to do exactly that:
https://hg.sr.ht/~kvik/fossil
> Thanks, I know that; I was asking where the list comes from since the
> one I remembered to be in the old wiki apparently died with it.
I pulled most of the articles into a new wiki, including the unix29 lists.
No information considered dead.
--
9fans:
Quoth Lucio De Re :
> What seems to be harped upon by the vocal defenders of 9front,
> however, is this fictional idea that there is another community, let's
> call them "9legacy", that is attempting to subvert 9front's efforts to
> gain some kind of recognition in the bigger picture.
The core
> Just pushed it to https://github.com/iru-/sam9f-unix. It might be
> outdated, but I still use it daily.
It seems that you imported two months before '^' and '_' got added
(in 758496ecaa42b5f6c17c0bd1e0f43189e50e0745).
There have been a few other changes very useful for scripting, like
the $%
> I needed recover(4) on windows, I rewrote most if it in go.
Where can the original version be found?
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T1d7bf3c39e885267-Md508afb3d00a30003d676ee0
Delivery options:
> It’s all the code that everyone is using.
> The issue is that there is some code in Plan 9 not written at
> Bell Labs which doesn't explicitly specify any license.
What actual code are you reffering to?
--
9fans: 9fans
Permalink:
> I can tell if 9front has a fixed version of ndb/dns or not myself
Other than the 96 patches to cmd/ndb logged into 9front hg repo
there's countless others pertaining to dependencies of the ndb set
that might have solved your particular issue.
FWIW I've been running ndb/dnstcp on 9front as a
fn detopicbox { ssam '
,x@\n\n-+.+\n.+\n.+\n.+\n@ g@^Permalink:
https:\/\/.+\.topicbox\.com@ g@^Delivery options: https:\/\/.+\.topicbox\.com@
d'
}
--
9fans: 9fans
Permalink:
> git/fetch git+ssh://g...@git.ff.co.za:23456/waspa/console.git
The port can be specified natively through the dialstring technology:
git/fetch git+ssh://git@net!git.ff.co.za!23456/waspa/console.git
It may be useful to add support to git9 for translating :port notation
to a
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
--
> unfortunately it doesn't look like anything is being logged
Turns out I misremembered where upas/fs logs the failure:
; upas/fs -f /imaps/imap.gmail.com/$gmail
upas/fs: opening /imaps/imap.gmail.com/$gmail: imap.gmail.com/imaps:cert for
imap.gmail.com not recognized:
Check /sys/log/mail for a fingerprint.
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/Te20476748ab5e4ba-M519efe14ca0b3cb7c3836dee
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Adding the fingerprint will work if you are lucky, once,
or maybe twice.
In my experience almost every new connection required
redoing the above -- which wasn't very fun so I ended
up forwarding gmail into a sub-mailbox under my control
and haven't looked back.
Working with their SMTP has the
> I welcome any feedback on the notion
After reading your mail I know far less about the "notion"
than I did a couple hundred years ago.
I'm invested in learning anything at all about the digital
product in the future.
-- kvik
--
9fans: 9f
15 matches
Mail list logo
